Returns and exchanges: from customer request to inspection, refund and dispatch
Two items are requested for return, only one arrives, and the customer wants a different size. Connect requests, received quantities, item condition and payments so support, warehouse and finance staff can act on the same record.
Consider a clothing retailer with an online store and physical shops. A customer wants to refund one shirt and exchange another for a larger size. Support handles the conversation, a shop accepts the parcel, the warehouse prepares the replacement and finance processes the refund. Separate messages can leave everyone uncertain about what arrived, what was refunded and whether the replacement is available.
A returns system can connect this after-sales work. Shopify documents customer requests and return processing; Microsoft Dynamics 365 documents return authorization, inspection and disposition. The capabilities below describe a possible company workflow, centred on each returned item and the customer’s next step.
Shopify — Self-serve returns and cancellations · Microsoft Dynamics 365 — Sales returns
Customers select items; support reviews the queue
After sign-in or email verification, the customer sees purchased variants, sizes, quantities and eligible items. They choose quantities, reasons and a refund or exchange, with photos where needed. Submission produces a return reference and handover instructions. An order number alone should not expose another customer’s address or purchase history.
Support filters requests awaiting information, approval or dispatch back to the store. Each record links the original order, earlier returns and attachments. Requests outside company rules go to an authorized reviewer with a recorded reason. A repeated request for the same item links to the existing case rather than creating a second refund.
Receive actual quantities before deciding what can be restocked
Shop or warehouse staff scan the return reference and compare expected line items with actual quantities, sizes or serial numbers, packaging and inspection photos. If one of two items arrives, receive that item and leave the other outstanding. Unidentified parcels or mismatched goods enter a review queue that support can resolve from the same record.
Inspection can classify goods as resalable, requiring preparation, awaiting further checks or unsellable, with a storage location. Receipt and availability for sale should be separate actions. A stained garment must not reappear as sellable merely because the return was approved. Microsoft’s documented workflow similarly separates arrival, inspection and disposition and supports split quantities.
Track replacement dispatch and refund results separately
An exchange screen should show available variants, stock location, reservation status and expiry. If the company reserves only after receiving the return, explain that during the request. When stock runs out, support offers alternatives and records the customer’s choice. Shopify currently documents reservation at return processing; requesting an exchange is not itself a reservation.
The settlement view lists original discounted amounts, exchange differences and any applicable company-policy fees by line. Finance confirms the calculation and records the payment provider’s refund reference and success or failure. A failed refund remains pending and must not trigger a completion message. The replacement links to its own dispatch record and tracking number.
Show customers progress and staff the unfinished work
The customer page can show receipt of the request, handover instructions, items received, refund progress and replacement dispatch, plus missing information. Internal staff additionally see inspection findings, payment failure details and task ownership. Shop staff may need receipt permissions without refund authority.
One reference may contain a completed refund and another item awaiting return. Queue work by the action still needed, and record who changed quantities, approved exceptions or sent updates. Product staff can review reasons by variant to investigate sizing descriptions or packaging. Customer photos should remain available only to staff who need them.
Check where updates land across the store, POS and warehouse
A Shopify community merchant reported returns updating Shopify without the corresponding change in Lightspeed/Vend. It is an individual report, not evidence that every integration fails. It does show why one successful update cannot establish agreement between systems. An integration view should identify the destination, item mapping, location, last result and retryable actions.
Test regional and warehouse settings. Shopify’s built-in return-label creation requires both the primary location and customer address to be in the US, so a Hong Kong workflow needs a separately verified carrier or uploaded-label arrangement. ShipStation documents restocking to the original Shopify fulfillment location. A different inspection warehouse needs its actual receipt recorded and an appropriate transfer. Retries must not duplicate refunds or stock movements.
Shopify Community — Return and exchange stock updates in Lightspeed/Vend · Shopify — Creating returns and exchanges · ShipStation — Restocking returned items with Shopify
Adapt inspection to clothing, electronics and wholesale
Clothing inspections may record size, tags and signs of wear; electronics may need serial numbers, accessories and test results. Wholesale returns may split cases, units and batches and require credit notes. Configure fields and disposition choices by product category rather than repeatedly typing them into support notes. If repair is needed, link a repair record while retaining the return history.
ReturnGO merchant reviews discuss self-service, languages, photos and configurable workflows; some also report needing setup help. These experiences support plausible use cases, not a claim that every company needs a replacement system. Keep useful existing functions and focus custom work on missing receipt, inspection or settlement handoffs.
Before payment, walk through a refund and an exchange in the Demo
ProApp provides a Demo before payment. For a returns system, we can plan a walkthrough using anonymous products and the company’s usual return rules, covering the customer, support, warehouse and finance steps. Agree on the screens and exceptions to show before confirming the development scope.
- Request a refund for one item and a size exchange for another; approve them and check the customer’s handover instructions.
- Receive only one item, record a stain and put it in the preparation area. Confirm the other remains outstanding and sellable stock has not increased.
- Receive the second item and try an unavailable size, a price difference and an alternative chosen by the customer. Check the replacement and tracking record.
- Simulate a refund or inventory update failure and retry it. Finance checks the refund reference, support checks the status message, and both confirm there are no duplicate actions.
Start with one product category and one receiving location
Bring an anonymous order, a typical return, current rules, receiving locations and staff permissions. Start with one product category and complete request, approval, receipt, inspection and refund or exchange. Add multiple shops, batches and repair branches afterwards. The workflow is connected when support can locate the item, the warehouse knows its destination, finance can see unresolved payments and the customer knows whether to wait or provide information.
