Small business outsourcing workflow guide

Design a returns and exchange desk for an assistant-run store

A returns and exchange desk that gives a small-business assistant clear eligibility rules, a safe refund limit, and a clean record for every case.

Design a returns and exchange desk for an assistant-run store

Publish the eligibility rule in customer language

Write the return window, the condition required, and the proof of purchase in the same words the customer will see on the website. The assistant should not have to interpret a policy written for lawyers. Give one example of an accepted return and one example of a refused return. A customer who understands the rule before buying is less likely to argue at the counter. Keep the policy link in every order confirmation and on the returns page.

Separate a return for a refund from an exchange and from a warranty claim, because each has a different path. A damaged item may need a photo and a supplier claim before any money moves. A change-of-mind return may need the original packaging and a receipt. The assistant should choose the path from the customer's reason and the evidence, not from the customer's tone. Record the path beside the case so the next person can follow it.

Give the assistant a safe decision range

Set a refund limit the assistant can approve without the owner, and write it as a dollar amount and a reason code. A limit without a reason code invites the assistant to fit every case into the allowed category. For amounts above the limit, the assistant prepares the case and the owner decides. Do not let the assistant approve a cash refund, a bank-detail change, or a store credit that exceeds the limit. Those actions move money and need a second pair of eyes.

When the assistant is unsure, the safe action is to hold the item and ask a specific question. A hold is better than a refusal that later turns out to be wrong. Tell the customer what is happening and when they will hear back. Record the question and the person who can answer it. A case that waits with a clear owner is different from a case that disappears.

Use a short reason-code list so the assistant does not write a different description for every case. Codes such as wrong size, damaged, not as described, changed mind, and late delivery make the monthly pattern visible. Add a free-text note only when the code cannot capture the issue. A consistent code is more useful than a long story.

Record the evidence before the item moves

For every case, capture the order number, the item, the reason, the condition, and the requested outcome. Add a photo when the condition or the damage matters, and store it with the case rather than in a personal phone. Record the date the item arrived and the date the customer contacted the business. The return window should be calculated from a documented date, not from memory. A missing date is the most common reason a simple return becomes a dispute.

If the customer returns an item in person, give them a receipt that names the case and the next step. If the item ships back, record the carrier and the tracking number. Do not refund before the item is received or the carrier confirms the return, unless the owner accepts the risk. For a high-value item, ask the owner before the return label is issued. The evidence should let a second person resolve the case without calling the customer again.

Keep the exchange stock and the refund ledger in step

An exchange is not complete when the replacement ships, because the returned item still has to be received and processed. Record whether the item goes back to stock, to the supplier, or to scrap. If it goes back to stock, check the condition and update the inventory count. A replacement shipped without a stock update creates a phantom item that distorts the next order. Reconcile the return ledger with the inventory and the payment records each week.

For a refund, record the payment method, the amount, the date, and the processor reference. A refund approved in the system but not sent to the processor is not a completed refund. The assistant should check the processor status before telling the customer the money is on the way. If the processor takes several days, say so in the customer message. A clear expectation reduces the follow-up that arrives on day two.

Check the condition of a returned item before it goes back to stock, and record who made the check. An item that is dirty, incomplete, or missing a part should not be sold as new. If the item is damaged, link it to the supplier claim or the write-off record. The stock count should reflect what can actually be sold.

Review the cases for a fix, not just a count

At the end of the month, group the cases by reason, product, and outcome. A product with repeated damage may need a packaging change, while a repeated size issue may need a better description. Ask the assistant which case took the most messages and why. Choose one change that would prevent a category of case, not just speed up the desk. Test the change for a month and compare the same reason codes.

Share the summary with the owner and the supplier when the issue belongs to them. A supplier who receives a clear photo and a case count can fix a packing problem faster than a general complaint. Keep customer names out of the supplier summary. Record the supplier response and the date the fix is expected. The returns desk is working when the same case stops coming back.

Sources and next steps

Compare this workflow with the small-business outsourcing service guides and bring a redacted source record to the scoping call.

Related guides

Free role planning call

Build a clearer work lane.

Share the role, tools, schedule, and approval needs. We will use those details to prepare a practical Philippines staffing conversation.

Contact Us