Item outcome
Record the approved next action for the returned item or exchange context. Any restock or inventory movement follows the organization’s configured rules.
Wexcy Returns & Refunds
Bring every return back to the original sale.
Keep the customer, order, return reason, decision, item outcome, and financial context connected—so teams can resolve what happens next without losing the history behind the sale.
The original sale
Resolve the return with the sale still in view.
A return is easier to review when the customer, order, purchased items, currency and amounts, channel, and recorded history remain part of the same context.
Customer and original order
Keep the person and the sale that set the context for the request.
Purchased items and quantities
Review what was purchased before agreeing on the next item action.
Currency and recorded amounts
Keep approved amounts understandable in the currency and values of the sale.
Channel and history
See the channel and the recorded events behind the post-sale decision.
Original Sale Return Loop
Make the reverse path clear before money or stock moves.
The request returns to the original sale, moves through a review and decision, then separates into the item outcome and the financial boundary.
- 01
Original sale
Begin from the customer, order, purchased items, and recorded commercial context.
- 02
Return request and reason
Record the reason that brings the item or sale back into review.
- 03
Review and decision
Make the approved next action clear before either outcome proceeds.
- 04
Item outcome + financial boundary
Keep the returned item decision separate from the financial execution context.
Two connected outcomes
Keep the item decision separate from the refund result.
One return can require two distinct decisions. Treating them separately keeps the post-sale record easier for operations and finance to read.
Financial outcome
Retain the approved amount, currency, execution state, and failure or retry context where supported. Provider settlement is a separate execution concern.
- Pending
- Processing
- Succeeded
- Failed
Clear execution boundary
Keep the decision clear across payment and logistics boundaries.
Wexcy keeps the original sale, request, review, and recorded outcome understandable. External execution depends on the verified configuration used by the organization.
Wexcy context
Original sale, request, reason, review, approved amount, item decision, and recorded result.
Provider execution
Movement of funds, reverse shipping, labels, collection, and external processing according to verified configuration.
A usable next conversation
Let the next conversation start with the full history.
Service and operations teams can understand what was purchased, why it came back, what was decided, and which outcome was recorded.
Returns FAQ
Questions before you set a return workflow?
Practical answers about the original sale, decisions, inventory, refunds, and policy design.
The return starts with the original sale context, keeping the customer, purchased items, reasons, and recorded decision understandable together.
No. Cancellation stops an order under its own rules. A return addresses what happens after a sale, so the two paths should not be treated as the same workflow.
The item outcome and financial outcome are separate decisions. The next action depends on your configured rules and the context of the original sale.
Do not assume that. Any inventory movement follows the configured operational rules and the decision recorded for the item.
Refund execution depends on the provider, market, and verified configuration. Wexcy can keep the business context and recorded result understandable around that boundary.
Define the relevant timeframes, conditions, reasons, approvals, and responsible owners for your market and operating model. This is a business policy decision, not a universal template.
A clearer reverse path
Keep the next return connected to the sale that started it.
Start with the order and customer context your teams need to make the next decision clear.