Start with the original purchase
Identify the customer, order, item, variant and quantity. Compare the request with the business’s published return policy and any commercial agreement that applies.
AFTER THE SALE / DECISIONS
One return. Several decisions.
Connect a return to the original order item. Inspect eligibility, receipt, the stock decision and the payment outcome without treating them as one automatic event.
BUILT AROUND THE WORK
What this means
for your business.
Inspect what came back
The receiving decision needs a quantity and condition. A returned item may be sellable, damaged or awaiting review; receiving it does not automatically make it available for the next customer.
Follow the money separately
An approved return and a completed refund have different evidence. Review the correct payment action and resulting state, including partial quantities and any earlier adjustment.
THE DETAIL IN BUSINESS CONTEXT
The customer experience continues at the door.
Rates, serviceability and delivery expectations belong before the promise. After dispatch, keep tracking, support and return decisions connected to the original items.
A return is a decision
Identify the item, quantity, reason and policy before accepting it back into sellable stock.
A refund is another event
A return receipt does not automatically explain the payment outcome. Follow the configured refund and reconciliation process.
INSPECT THE RECORDS AND DECISIONS
Receipt, stock and money each need an outcome.
Use the original item and quantity to keep a partial return intelligible.
Operating concepts to inspect in your setup; this is not a wire-format schema. Exact API fields belong in the source-derived reference.
- Original order item
- The purchase the request relates to.
- Requested quantity
- The portion the customer wants to return.
- Policy decision
- The accepted or declined return under the business agreement.
- Condition
- The receiving team’s assessment of what arrived.
- Stock disposition
- The decision about sellable, damaged or unresolved goods.
- Refund result
- The recorded financial outcome, separately inspected.
If one of two items is returned
Preserve item-level quantities and review the relevant discount and delivery treatment.
If refund status is unclear
Read the actual financial result before repeating the action. A received parcel is not proof of payment reversal.
Inspect the supplied workspace.
Supplied Agora finance workspace. This capture provides interface context; the operating scenarios on this page use separately labelled sample data.
FOLLOW THE PROCESS
From the first step
to the next decision.
01
Review the request
Establish the original purchase, requested quantity, reason and policy decision.
Review the request→Receive and assess→Inspect the financial outcome
02
Receive and assess
Record the actual item and condition, then resolve the stock consequence.
Review the request→Receive and assess→Inspect the financial outcome
03
Inspect the financial outcome
Follow the configured refund process and reconcile it with the order and payment.
Review the request→Receive and assess→Inspect the financial outcome
Operating walkthrough · Review the exact configuration for your business.
A CLEARER PICTURE
Good questions.
Useful answers.
Does receiving an item automatically complete a refund?
No. Receipt, stock disposition and the payment action need their own outcomes.
Can a partial return affect the whole order?
Review the actual item quantities, discounts, delivery charges and agreement. Avoid assuming the order headline explains a partial case.
BUILD WITH AGORA
Your next chapter starts here.
Bring your business, your ambition and the questions that matter. Let’s explore what you can build with Agora.