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.
Feature · Delivery
Example screen with sample data
Delivery
Plan routes, pick accepted demand and record actual handoff outcomes.
OverviewPick tasks in progress×
Dairy ERP · Delivery
New
Pick tasks in progress
Pick tasks
| Pick number | Order line | Assigned to | Planned start | Planned end | Picked quantity | |
|---|---|---|---|---|---|---|
| PT-84311 | SOL-1603 | 08 Oct | 14 Oct | 300 | ||
| PT-98050 | SOL-6500 | 14 Oct | 20 Oct | 790 | ||
| PT-29545 | SOL-8942 | 15 Oct | 19 Oct | 300 | ||
| PT-33739 | SOL-2596 | 13 Oct | 18 Oct | 320 | ||
| PT-65084 | SOL-8824 | 15 Oct | 24 Oct | 730 |
6 of 6 records
SOL-1603Pick tasks · PT-84311
AssignedPlanned start08 Oct
Planned end14 Oct
Picked quantity300
What you can do
Plan routes, pick accepted demand and record actual handoff outcomes
Warehouse Operator picks against the order line and its reservation. The pick task retains planned timing, assigned person and actual picked quantity. Warehouse Manager plans a route with an operator, source warehouse, transport reference and sequenced stops. Release requires a reviewed route decision. A planned stop or route cannot be treated as an actual dispatch.
The delivery records dispatched quantity, title rule and actual evidence. For dispatch terms, the issue at handoff transfers title. For delivery terms, goods remain owned in transit until accepted at the stop. Each visit records an attempt and line outcomes such as accepted, refused, failed or damaged quantity. Partial outcomes can leave the route and shipment open for another visit without losing the original order link.
A customer return starts from bounded original shipment scope. Physical receipt, disposition, commercial credit and refund remain separate decisions. Warehouse staff can hold, restock, rework or scrap actual returned quantity through the reviewed disposition path. Accountant handles the financial document. This prevents a failed stop or returned carton from automatically creating a credit or reversing unrelated delivery history.
How the work is organized
- Pick. Warehouse Operator records actual picked quantity against an accepted order line and reservation.
- Route. Warehouse Manager reviews the assigned operator, transport reference and ordered stops before route release.
- Visit. Warehouse Operator records dispatch and each actual delivery attempt; returned goods enter a separate disposition decision.
What to agree during setup
Agree transport evidence, stop sequencing, who records an attempt, and how the title rule is chosen on orders. Rehearse partial delivery and refusal before the route is used for live work. Keep the decision owner separate from the preparer for controlled releases. Use a real sample that includes a correction, so the operating team sees where the original record remains available.
Check the handoff on an actual case
Pick an accepted order, release a route and dispatch part of the line. Record one delivered quantity and one refusal. Check remaining transit or unfulfilled scope and start a bounded return only for the original line. Ask the next owner to trace the source, decision and actual event in order. Compare the remaining quantity and value after each partial action. Record the person who resolved an exception and the evidence they used.
What your team sees
- Delivery route schedule — Planned start and end times, operator and status for each route.
- Route exception board — Released or active routes whose stops need follow-up.
Follow the work through
Use delivery and returns for the operating rehearsal.
What it keeps track of
Data model- Pick tasks
- Actual picked quantities remain exclusively tied to the order and do not post COGS.
- Delivery routes
- Manual route/stop sequence and assigned execution; no optimization or live tracking.
- Route stops
- Explicit stable sequence and exact order/shipment ownership.
- 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.
Who uses it
Permissions- Warehouse Operator
- Picks and records actual attempts.
- Warehouse Manager
- Owns route release and physical return review.
- Accountant
- Handles any credit document separately from the goods outcome.
Set up Dairy ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.