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.
- Cosmetics ERP
- Features
- Delivery and returns
Delivery and returns
Separate planned stops, actual dispatch, customer outcomes and authorized returns.
OverviewRoutes awaiting release×
Cosmetics ERP · Delivery and returns
New
Routes awaiting release
Delivery routes
| Route number | Coordinator | Assigned operator | Warehouse | Planned start | Planned end | |
|---|---|---|---|---|---|---|
| DR-14951 | WRH-150 | 16 Oct | 23 Oct | |||
| DR-11073 | WRH-110 | 11 Oct | 14 Oct | |||
| DR-38395 | WRH-150 | 08 Oct | 14 Oct | |||
| DR-34892 | WRH-140 | 06 Oct | 13 Oct | |||
| DR-29599 | WRH-110 | 21 Oct | 26 Oct |
6 of 6 records
WRH-150Delivery routes · DR-14951
Pending approvalPlanned start16 Oct
Planned end23 Oct
What you can do
Carry the order to the customer
Warehouse Manager plans a route with a source warehouse, assigned operator, coordinator and ordered stops. Each stop has a planned window and a specific delivery. Route release requires transport and load evidence, an operator and a real stop count. A planned route is a work plan; the delivery record captures the actual dispatch and later customer outcome.
Pick tasks tie a picked quantity to an accepted order line and reservation. Dispatch cannot exceed verified ready scope. Delivery lines record dispatched, title-transferred and delivered quantities separately. The title rule determines whether transfer occurs at dispatch or customer delivery, which matters for stock ownership and invoice eligibility.
How the work is organized
- Plan. The route and stops set sequence, operator, warehouse and expected windows.
- Execute. Pick tasks and deliveries capture prepared and dispatched quantities.
- Resolve. Attempts, results and returns record what the customer actually accepted or refused.
One vehicle visit may partially deliver several lines. Delivery attempt evidence records the visit, while each delivery result allocates accepted, refused, failed or damaged quantity to its line. A second attempt should consume only the remaining eligible scope. If a dealer refuses a carton, the resulting stock and credit treatment require separate review.
What to agree during setup
Choose title transfer rules for the selling terms and train the team to retain actual handoff evidence. Agree who can release routes, record attempts and correct an outcome. For external carriers, identify the carrier reference and the verified event that supports delivery. Decide how failed stops are rescheduled without erasing the earlier attempt.
Returns need an original delivery or receipt scope, direction, reason and expiry of authorization. Warehouse Manager reviews physical disposition: restock, hold, rework, scrap, supplier return or return to dealer. A physical return does not by itself authorize a customer credit or refund. Finance Manager handles the separate financial decision.
Check the handoff on an actual case
Place two deliveries on a route. Release it after assigning the operator and recording transport evidence. Pick and dispatch part of a dealer order. At the first stop, record one accepted line and one refused carton. Verify that the order’s remaining quantity, delivery result and stock custody each reflect the actual event. Authorize a customer return within the original delivered scope, put the returned lot on hold and prepare the related credit separately. Repeat the same external event and verify no extra economic effect appears.
What your team sees
- Routes awaiting release — Plans needing Warehouse Manager review and assigned execution.
- Delivery exception board — Partial or exception deliveries requiring another decision.
- Returns awaiting authorization — Physical return requests and their original party.
Follow the work through
Read dealer commitment to dispatch and return to resolution. See integrations for external event evidence.
What it keeps track of
Data model- Delivery routes
- Manual route/stop sequence and assigned execution; no optimization or live tracking.
- Route stops
- Explicit stable sequence and exact order/shipment ownership.
- 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 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 allocations
- Atomic claim of accepted line quantity and net/tax value across staged fulfillment/billing.
- Stock events
- One immutable group of stock movements and the associated journal effect.
Who uses it
Permissions- Warehouse Manager
- Controls route and return decisions.
- Warehouse Operator
- Records picks, visits and physical results.
- Sales Manager
- Coordinates the dealer response.
- Finance Manager
- Decides related credits or refunds; Accountant posts the approved financial outcome.
Set up Cosmetics ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.