Returns
Customer claim and warehouse inspection workflows, with resolutions applied to the order.
Overview
By the time someone files a return, they have already decided something went wrong. What happens next decides whether they buy from you again.
The Returns app keeps that whole sequence on the order. A claim is filed against the actual lines, limited to what is still claimable, so the same item cannot be refunded twice by two different people on two different days. Resolutions that require the goods back become an inspection for the warehouse; the ones that do not are settled straight away rather than waiting behind a parcel.
When the resolution is reached — at the claim, or after inspection — it is applied to the order in one go. That matters most on the orders that are hardest to settle fairly: the ones where a campaign applied, and what the customer keeps is no longer worth what it was when the basket qualified.
Your policy stays yours. The resolutions available to agents, and the details they capture for each one, are configuration rather than a rebuild.
What it does
-
Claim filing over HTTP
Public endpoints for creating claims against an order and listing existing ones, with lines matched automatically against the quantity still claimable.
-
Claims and RMAs as separate records
A claim captures what the customer asked for; an RMA captures what the warehouse found. Each has its own lines, states and fields.
-
Inspection only where required
Resolutions that need the goods back create an inspection task; the rest resolve at claim completion without waiting for a parcel.
-
Configurable resolution types
Refund, replace, compensate or your own — each declared with the per-resolution fields an agent should capture, without code.
-
Resolutions applied to the order
When a claim or inspection completes, the resulting effects are applied to the connected order in a single batch.
-
Stand-alone RMAs
An inspection can exist without an originating claim, for goods that arrive unannounced or recall workflows.
-
Portal extension points
Slots and warning services on the claim and RMA views, so other apps can add to them.
Apps that usually run together.
Most operations install more than one. These are the apps this one is most often paired with, because they share the same order.