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.
- Ceramics ERP
- Features
- Delivery and returns
Delivery and returns
Carry picked quantities through route, handoff and return decisions.
OverviewReturns awaiting authorization×
Ceramics ERP · Delivery and returns
New
Returns awaiting authorization
Approval conditions
| Return number | Direction | Customer | Supplier | Requested at | Reason | |
|---|---|---|---|---|---|---|
| RTR-49542 | Customer to us | CUS-184 | VND-092 | 03 Oct | Pending approval rtr-992 | |
| RTR-54184 | Us to supplier | CUS-114 | VND-156 | 06 Oct | Pending approval rtr-650 | |
| RTR-44420 | Customer to us | CUS-223 | VND-212 | 04 Oct | Pending approval rtr-906 | |
| RTR-32971 | Us to supplier | CUS-048 | VND-026 | 20 Oct | Pending approval rtr-940 | |
| RTR-48729 | Customer to us | CUS-017 | VND-043 | 19 Oct | Pending approval rtr-850 |
6 of 6 records
Pending approval rtr-992Returns · RTR-49542
Customer to usCustomerCUS-184
SupplierVND-092
Requested at03 Oct
StatusPending approval
What you can do
Keep the operating basis clear
A pick task identifies the order line, assigned operator and planned interval. Actual picked quantity stays tied to that source. The delivery records the shipment and title rule, while the route records ordered stops, assigned execution and its planned window. The warehouse manager reviews the route before it is released.
How the work is organized
A visit records an attempt and its evidence. Delivery results split a line’s accepted, refused, failed and damaged quantities. A partial result leaves a remainder to resolve; another attempt cannot duplicate units already accepted. A customer or supplier return retains its original commercial and stock source, then moves through authorization and physical disposition.
- Identity. Keep the source record, entity and accountable person attached to each step.
- Decision. Record the reviewer and the exact scope they accepted before the next action.
- Evidence. Preserve actual quantity, date and correction history when execution differs from the plan.
What to agree during setup
For a ceramics delivery, agree on the destination and evidence required at handoff. Decide whether title passes at dispatch or accepted delivery for the applicable order. Give the operator an assigned route and stable stop sequence. Agree how refused or damaged pieces are measured against the original line.
The team should choose one real pilot case and agree on its owner, decision point and exception route. Prepare the source identifiers and opening balances before importing old records. Review access with the person who will perform the work, and make the exception visible to the person who can resolve it.
Check the handoff on an actual case
Rehearse a delivery where the customer accepts part of a shipment and refuses the rest. Compare the order line, pick, dispatch and visit outcomes. Authorize a return only within the original remaining scope. Record the actual stock disposition separately from a credit or refund, and confirm the route remains open until its unresolved stop is addressed.
Check the final state against the original promise and the accepted source. The reviewer should be able to explain why a partial action left a remainder, which evidence changed it and who approved the next step. Repeat the case after a correction to make sure the original record remains traceable.
What your team sees
- Delivery schedule — Released routes and the operator responsible for the planned window.
- Returns awaiting authorization — Physical return requests waiting for an eligible decision.
Follow the work through
See the operating process and the data model to prepare the case, assign the decision and reconcile its records.
What it keeps track of
Data model- Pick tasks
- Actual picked quantities remain exclusively tied to the order and do not post COGS.
- Deliveries
- Actual dispatch and title/delivery state separated for partial deliveries.
- Delivery lines
- Actual dispatch quantities and current title-transferred/delivered portions.
- Delivery routes
- Manual route/stop sequence and assigned execution; no optimization or live tracking.
- Route stops
- Explicit stable sequence and exact order/shipment ownership.
- Delivery attempts
- Actual visit/handoff facts, separate from line outcomes and legal title.
- Delivery results
- Each attempt allocates line outcomes once; one visit may partially deliver many lines.
- Returns
- Bounded customer/supplier physical return authorization, separate from commercial credits.
- Return lines
- Exact original commercial/stock scope and actual returned quantities.
- Return dispositions
- Independent actual goods disposition without automatic credit or refund.
- Sales orders
- Customer-accepted scope plus mandatory independent commercial approval.
- Reservations
- Exclusive bounded demand claims through picking and owned transit.
Who uses it
Permissions- Warehouse Manager
- Controls route and disposition decisions.
- Warehouse Operator
- Records picking and visits.
- Sales Manager
- Reviews customer consequences; Purchasing Manager handles supplier returns.
Set up Ceramics ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.