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.
- Electronics ERP
- Features
- Fulfillment and delivery
Fulfillment and delivery
Connect a picked order to actual route and line outcomes.
OverviewRoute schedule×
Electronics ERP · Fulfillment and delivery
New
Route schedule
Delivery routes
| Route number | Warehouse | Coordinator | Assigned operator | Planned start | Planned end | |
|---|---|---|---|---|---|---|
| DR-37324 | WRH-140 | 27 Oct | 04 Nov | |||
| DR-68331 | WRH-120 | 04 Oct | 06 Oct | |||
| DR-78684 | WRH-110 | 25 Oct | 27 Oct | |||
| DR-95081 | WRH-110 | 16 Oct | 20 Oct | |||
| DR-86644 | WRH-110 | 11 Oct | 13 Oct |
6 of 6 records
WRH-140Delivery routes · DR-37324
ReleasedPlanned start27 Oct
Planned end04 Nov
What you can do
Run the operating handoff
Warehouse Operator picks against a reservation linked to an accepted order line. Delivery records separate dispatch from actual arrival and title transfer. Warehouse Manager plans a route with a source warehouse, assigned operator and ordered stops, then reviews release evidence before execution.
At a stop, the operator records an actual attempt and line outcomes. A delivery can be partial: accepted, refused, failed and damaged quantities remain distinct. For dealer replenishment across several stops, a missed stop stays visible while successful lines progress toward billing.
How the work is organized
- Pick. Warehouse Operator records picked quantity against a reservation for an accepted order line.
- Dispatch. Warehouse Manager reviews ready scope and releases the route before actual dispatch.
- Outcome. Warehouse Operator records each attempt; accepted, refused, failed and damaged line quantities remain separate.
What to agree during setup
Agree the shipment title rule, source warehouse and evidence required at dispatch or customer handoff. Give each route an assigned operator, coordinator, transport reference and stops before Warehouse Manager releases it. A route plan does not itself prove delivery.
Choose an order whose lines may have different outcomes at the same stop. Tell operators how to record a partial acceptance and who reviews a failed attempt. Finance should know whether title passes at dispatch or delivery before invoicing.
Check the handoff on an actual case
Pick part of an approved line from its reservation, then create a route with a planned stop. Warehouse Manager checks the operator, warehouse and load evidence before route release. Dispatch only the verified ready quantity.
Record an attempt where the dealer accepts part of one line and refuses another part. Compare dispatched, title-transferred, delivered and returned quantities for each line. A later attempt should work only on the unresolved scope. Review a repeat attempt so the same accepted quantity cannot be allocated twice, and show Accountant the title-transferred quantity eligible for invoice.
If a delivery attempt fails, retain the original route, stop and line outcome for the next operator. A new attempt should carry only the unresolved quantity. Sales Representative can use that evidence to explain the revised promise to the dealer while Accountant checks whether any quantity has transferred title.
What your team sees
- Delivery exception board — Shipments in planning, picking, dispatch or exception states for warehouse follow-up.
- Route schedule — Released and active routes with operator, warehouse and planned times.
Follow the work through
Continue with the process and the implementation plan.
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.
- Sales allocations
- Atomic claim of accepted line quantity and net/tax value across staged fulfillment/billing.
Who uses it
Permissions- Warehouse Operator
- Picks and records outcomes.
- Warehouse Manager
- Releases routes and resolves warehouse exceptions.
- Accountant
- Reviews billable scope.
Set up Electronics ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.