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.
- Telecom ERP
- Features
- Fulfillment and delivery
Fulfillment and delivery
Pick approved order scope, dispatch verified goods and capture what each stop actually received.
OverviewMy Pick Tasks×
Telecom ERP · Fulfillment and delivery
New
My Pick Tasks
Pick tasks
| Pick number | Status | Order line | Planned start | Planned end | Picked quantity | |
|---|---|---|---|---|---|---|
| PT-40079 | Assigned | SOL-4688 | 12 Oct | 20 Oct | 330 | |
| PT-13059 | In progress | SOL-9457 | 12 Oct | 19 Oct | 350 | |
| PT-71844 | Picked | SOL-5003 | 17 Oct | 25 Oct | 80 | |
| PT-35030 | Partially picked | SOL-5283 | 14 Oct | 21 Oct | 610 | |
| PT-57268 | Exception | SOL-5011 | 03 Oct | 12 Oct | 190 |
6 of 6 records
SOL-4688Pick tasks · PT-40079
AssignedPlanned start12 Oct
Planned end20 Oct
Picked quantity330
What you can do
Work from accepted scope
Warehouse Operator picks against an eligible reservation and order line. The pick task carries an assignee, planned interval and picked quantity. A shipment links its lines to the same accepted demand. The title rule distinguishes dispatch from confirmed delivery. A ready shipment needs positive verified quantity before dispatch; a planned route by itself establishes no physical handoff.
How the work is organized
- Source. Agree the route owner, source warehouse and transport evidence before release.
- Decision. Warehouse Operator should verify the pick against the reservation and record the actual dispatched quantity.
- Evidence. For a refused line, keep the refused quantity out of accepted delivery.
What to agree during setup
Warehouse Manager releases a route with its assigned operator, source warehouse, transport reference and ordered stops. The operator records arrival and completion evidence at each stop. Accepted, refused, failed and damaged quantities are allocated to shipment lines, allowing a single visit to produce mixed outcomes. Exceptions remain open for correction or rescheduling without rewriting the original visit.
Agree the route owner, source warehouse and transport evidence before release. Warehouse Operator should verify the pick against the reservation and record the actual dispatched quantity. The route schedule helps plan work; the stop attempt and line result establish what the dealer received.
Check the handoff on an actual case
A route carries a shipment with two lines to one dealer. The first line is accepted in full; part of the second line is refused. Record one stop attempt and both line outcomes, then keep the refused portion outside delivered quantity. If title transfers on delivery, only the accepted amount becomes billable at that point. Review the remaining shipment scope before another dispatch.
For a refused line, keep the refused quantity out of accepted delivery. Review the shipment line and title rule before billing or arranging another visit. A second attempt must retain the first stop outcome and its evidence.
At dispatch, compare the ready shipment with the quantity actually picked and the stock event that removes it from the warehouse. The assigned operator follows the released route and records a separate attempt at each stop. Sales Representative can then explain the open dealer commitment using accepted delivery quantities, while Warehouse Manager resolves a failed or refused line before treating the route as complete.
What your team sees
- Delivery Schedule — Released and active routes with assigned operators and planned intervals.
- Delivery Exceptions — Routes needing follow-up after a failed or partial stop.
Follow the work through
Follow the operating process and check the data model before importing live balances.
What it keeps track of
Data model- Pick tasks
- Actual picked quantities remain exclusively tied to the order and do not post COGS.
- Shipments
- Actual dispatch and title/delivery state separated for partial deliveries.
- Shipment 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.
- Inventory reservations
- Exclusive bounded demand claims through picking and owned transit.
- Stock events
- One immutable group of stock movements and the associated journal effect.
Who uses it
Permissions- Warehouse Operator
- Picks and records handoff evidence.
- Warehouse Manager
- Controls route release.
- Sales Representative
- Follows dealer commitments.
Set up Telecom ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.