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 · Fulfillment
Example screen with sample data
Fulfillment
Pick approved demand, release assigned routes and record actual delivery results.
OverviewMy Pick Tasks×
FMCG ERP · Fulfillment
New
My Pick Tasks
Pick tasks
| Pick number | Order line | Status | Planned start | Planned end | Picked quantity | |
|---|---|---|---|---|---|---|
| PT-66435 | SOL-9611 | Assigned | 27 Oct | 03 Nov | 830 | |
| PT-59479 | SOL-5097 | In progress | 05 Oct | 08 Oct | 470 | |
| PT-48078 | SOL-3751 | Picked | 14 Oct | 21 Oct | 100 | |
| PT-65850 | SOL-4783 | Partially picked | 14 Oct | 23 Oct | 570 | |
| PT-54532 | SOL-5775 | Exception | 10 Oct | 18 Oct | 280 |
6 of 6 records
SOL-9611Pick tasks · PT-66435
AssignedPlanned start27 Oct
Planned end03 Nov
Picked quantity830
What you can do
Follow the order through physical delivery
A dealer order gives the warehouse a bounded quantity and destination. Warehouse Operator picks against an assigned task and stock reservation. The picked quantity remains tied to its order line; picking alone does not establish a sale or a completed delivery. A shipment then records actual dispatch, while its title rule determines whether ownership passes at dispatch or after accepted delivery.
Warehouse Manager prepares a route with its source warehouse, coordinator, assigned operator, transport reference and stops. Route release requires a decision on the current plan. The stop order is manually set by the team. Delivery attempts capture actual arrival and completion times, and results divide shipment-line scope into accepted, refused, failed and damaged quantities.
How the work is organized
- Pick. Operators record actual picked quantity against an eligible reservation, including partial picks and exceptions.
- Dispatch. A shipment moves from ready scope into actual dispatched quantity with evidence and a bounded source.
- Visit. The operator records each attempt; line outcomes explain what the customer accepted and what remains unresolved.
What to agree during setup
Agree who assigns route operators and who reviews release. Set the warehouse and entity scope for a route before adding stops. Decide what transport evidence is required and how the team records a refused or damaged part of an order. The original dealer promise should stay available alongside the route’s planned window; changing a route time does not change that promise.
For external carriers, agree how a carrier result enters the app through verified evidence. For own delivery, train operators to record the attempt and line results even when a visit fails. A route marked complete should be supported by actual stop outcomes, not by a planned sequence alone.
Check the handoff on an actual case
Take an approved order with two lines. The first has full stock, while the second can only be picked in part. The operator records those actual quantities, and the shipment includes only verified ready scope. Warehouse Manager checks the operator, transport evidence and stops before releasing the route. Actual dispatch updates the shipment but does not claim that the dealer accepted every unit.
At the dealer, one line is accepted and the other partly refused. Record one visit and separate line outcomes. The refused quantity remains distinct from accepted delivery and is available for its proper return or correction path. For delivery-title terms, only the accepted delivered portion supports title transfer and later billing. A retry must address the unresolved remainder without counting the first successful delivery twice.
What your team sees
- Delivery Schedule — Released routes with assigned operator and planned window.
- Delivery Exceptions — Routes with unresolved execution issues.
- My Pick Tasks — Picks assigned to the current warehouse operator.
Follow the work through
Continue with dealer order to delivery and invoice to cash.
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.
- Sales orders
- Dealer-accepted scope plus mandatory independent commercial approval.
- Sales order lines
- Bounded accepted quantity/value and retained original promise.
- 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 visits.
- Warehouse Manager
- Releases routes and resolves exceptions.
- Sales Representative
- Follows the dealer commitment, while Accountant uses the resulting title evidence for billing.
Set up FMCG ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.