Understand stock restoration during an order return
Release a reservation or restore on hand based on original stock handling. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goEnterprise POS → Orders
What you’ll accomplish
Release a reservation or restore on hand based on original stock handling. This section covers order search, status interpretation, fulfilment, invoice reconciliation and full compensating returns.
Follow these steps
- Go to Enterprise POS → Orders and open the workflow that matches “Understand stock restoration during an order return”. Confirm the page or record context before making a change.
- Search and open the order.
- Check channel, status, payment, fulfilment, customer, lines and totals.
- For an eligible e-commerce order, mark it fulfilled.
- For a return, enter a reason of at least three characters and create the full return.
- Where money was captured externally, process the financial refund through the original tender outside this module.
- Check stock, order status, payment marker, audit and webhooks.
Fields and options to review
- Guide focus: Release a reservation or restore on hand based on original stock handling.
- Reference and UUID
- POS or e-commerce channel
- Order, payment and fulfilment statuses
- Customer and address snapshot
- Line/tax/discount/cost snapshots
- Invoice ID and payment rows
- Return and return-line records
- Public token and idempotency key
Rules the system enforces
- Fulfilment applies to eligible e-commerce orders only.
- Reserved orders reduce reserved and on hand at fulfilment; immediately deducted orders do not deduct twice.
- Paid fulfilled orders become completed; unpaid fulfilled orders remain processing.
- The supplied return action is whole-order only.
- A return reason must contain at least three characters.
- Paid returns create a refund_due payment marker; no external tender refund is executed.
How to confirm it worked
- The specific outcome described by this guide is visible and remains tenant-scoped.
- The order register and detail page reflect the new state.
- Stock is released/restored exactly once.
- Return, audit and webhook evidence is created.
- Native invoice payment hooks can update POS payment status.
Safety checks and troubleshooting
- Verify the order is eligible before fulfil/return.
- Do not promise an automatic card/bank refund.
- Do not repeat a return after the order already became returned/refunded.
Stay within the supported module flow
Use the supplied UI, host module lifecycle and documented endpoints. Do not bypass tenant filters, permissions, CSRF, idempotency, rate limits, audit evidence or transaction checks. A stored table or field does not imply that version 1.0.0 exposes a management screen for it.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.
