These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- E-commerce ERP
- Features
- Returns and inspection
Returns and inspection
Returns and inspection for the order and stock cycle.
OverviewReturns awaiting authorization×
E-commerce ERP · Returns and inspection
New
Returns awaiting authorization
Authorized waits for the warehouse manager
| Account | Sales order | Reason | Requested at | Refund amount | Status | |
|---|---|---|---|---|---|---|
| ACC-150 | SO-3796 | Damaged | 24 Oct | 330 | Requested | |
| ACC-110 | SO-2810 | Wrong item | 14 Oct | 900 | Requested | |
| ACC-120 | SO-9495 | Not as described | 25 Oct | 390 | Requested | |
| ACC-150 | SO-2518 | Changed mind | 22 Oct | 710 | Requested | |
| ACC-140 | SO-8578 | Late delivery | 03 Oct | 810 | Requested |
6 of 6 records
ACC-150Returns · RTR-76608
DamagedSales orderSO-3796
Requested at24 Oct
Refund amount330
StatusRequested
What you can do
Keep the decision attached to the record
Requested, Authorized, Received, Inspected, Refunded and Rejected are distinct return states. An authorization is permission to receive and inspect, not proof of returned stock or a completed refund. Warehouse Manager follows the return from the customer’s requested reason through authorization, actual receipt and inspection. Each returned line has a quantity and disposition. An authorized request is permission to receive the item, while a refunded state belongs after Finance Manager checks the money movement. Keep the original sales order and channel references when they are available.
How the work is organized
- Review the request. Compare the account, reason and order context before authorizing or rejecting it.
- Inspect the goods. Record the actual returned quantity and choose Restock, Refurbish, Scrap or return to vendor for each line.
- Follow the money. Finance Manager checks the refund amount and transaction separately from warehouse receipt.
What to agree during setup
Agree who may authorize a return, where returned goods are held before inspection and who chooses a line disposition. Rehearse a damaged item that should be scrapped and a request that should be rejected. If an item is restocked, verify a posted return movement at the correct warehouse. Keep any refund decision with Finance Manager and its processor transaction.
Choose a held location for returned goods until inspection is complete. On a damaged return, record the actual quantity and Scrap disposition; on a saleable return, review the Restock decision and related movement. Finance Manager should see the inspected result before handling the refund.
Check the handoff on an actual case
A customer reports a damaged item after delivery. The Warehouse Manager checks the related order and request reason, authorizes the return, then waits for actual receipt and inspection. The returned line is assigned a disposition; only an item approved for restock belongs back in available stock. Finance follows the refund through its payment transaction and settlement.
Finance Manager needs the inspected return, approved refund amount and payment context before recording a refund. Sales Manager needs the decision for the customer. A requested or authorized state alone must not make goods available or show the customer as refunded.
What your team sees
- Returns awaiting authorization — The main queue for customer return request, with its status and source context.
- Settlement variances — Related follow-up work that needs a second check.
Follow the work through
- Follow this handoff: Check the linked stages and exception path.
- Review the data model before importing open records.
What it keeps track of
Data model- Returns
- Customer return requests, inspection and refund state.
- Return lines
- Returned products, values and disposition decisions.
- Sales orders
- Accepted customer orders with stage, owner and totals.
- Accounts
- Entity-scoped customer accounting identity.
- Products
- Canonical stocked SKU for each physical product or produced kit.
- Stock movements
- Posted stock movement evidence per product, warehouse and movement kind.
- Payment transactions
- Captured charges, refunds and chargebacks per processor.
Who uses it
Permissions- Warehouse Manager
- Owns authorization, physical receipt and inspection.
- Sales Manager
- Records customer context.
- Finance Manager
- Checks the refund transaction and related settlement line.
Set up E-commerce ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.