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.
- Shipbuilding ERP
- Features
- Fulfillment and delivery
Fulfillment and delivery
Pick accepted quantities, dispatch shipments and record actual delivery outcomes.
OverviewMy pick tasks×
Shipbuilding ERP · Fulfillment and delivery
New
My pick tasks
Pick tasks
| Pick number | Order line | Reservation | Planned start | Planned end | Picked quantity | |
|---|---|---|---|---|---|---|
| PT-20721 | SOL-9302 | IR-54755 | 08 Oct | 14 Oct | 260 | |
| PT-93903 | SOL-5502 | IR-68884 | 05 Oct | 14 Oct | 230 | |
| PT-63341 | SOL-5093 | IR-15695 | 24 Oct | 02 Nov | 770 | |
| PT-48696 | SOL-4986 | IR-53987 | 04 Oct | 07 Oct | 590 | |
| PT-65867 | SOL-4302 | IR-81397 | 04 Oct | 07 Oct | 30 |
6 of 6 records
SOL-9302Pick tasks · PT-20721
AssignedReservationIR-54755
Planned start08 Oct
Planned end14 Oct
Picked quantity260
What you can do
Move only eligible order scope
An approved customer order and an exclusive stock reservation establish the quantity available for picking. Warehouse Operator receives an assigned pick task tied to the exact order line and inventory claim. Picking records actual quantity without booking a sale or removing title by itself. Warehouse Manager checks ready shipment scope before dispatch, including the order’s title rule and the relevant warehouse.
A shipment records actual dispatch and keeps title-transferred and delivered quantities separate on each line. With a dispatch title rule, handoff can transfer title. With a delivery title rule, owned stock remains in transit until an accepted delivered portion transfers title. The customer invoice uses the eligible title-transferred quantity, not a route’s planned quantity.
How the work is organized
- Assigned picking. A task binds one operator to an order line, reservation, window and actual picked quantity.
- Dispatch evidence. Shipment lines retain dispatched, delivered, title-transferred and returned portions.
- Delivery visit. A route stop and attempt record the actual visit; result lines divide accepted, refused, failed and damaged quantities.
What to agree during setup
Agree who releases a route, who records an attempt, and what evidence proves handoff. A delivery route needs a coordinator, operator, source warehouse, transport reference and an ordered set of stops. A planned stop remains a plan until a real attempt occurs. External carrier references and bank or customer acknowledgments come from separately configured connections, not from a local plan.
Decide how to resolve a partial visit. One stop may involve several shipment lines, and one line may need another visit. Preserve the earlier attempt and create a successor stop where rescheduling is required. The same delivered quantity cannot be credited to both visits.
Check the handoff on an actual case
Pick a partial order of stocked parts from a warehouse. The operator confirms the picked quantity, and the shipment dispatches only that bounded ready scope. Warehouse Manager releases a route with a named operator and a stop for the receiving address. At the stop, the operator records a visit that accepts most units and refuses the rest. The accepted and refused parts remain separately attributable to the shipment line.
Review the legal title rule before invoicing. For delivery title, the refused portion stays outside billed scope. Record any return or disposition as its own decision; an unsuccessful visit cannot quietly turn into a stock return, customer credit or second shipment. Compare the original order promise with actual dispatch and accepted delivery dates.
What your team sees
- My pick tasks — Warehouse Operator sees assigned physical work and remaining task status.
- Delivery schedule — The team sees released routes and their planned windows.
- Delivery exception board — Warehouse Manager reviews failed, refused and rescheduled stops.
Follow the work through
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 allocations
- Atomic claim of accepted line quantity and net/tax value across staged fulfillment/billing.
- Returns
- Bounded customer/supplier physical return authorization, separate from commercial credits.
- Return lines
- Exact original commercial/stock scope and actual returned quantities.
- Inventory reservations
- Exclusive bounded demand claims through picking and owned transit.
Who uses it
Permissions- Warehouse Operator
- Picks and records actual visits.
- Warehouse Manager
- Reviews shipment and route release.
- Sales Representative
- Follows customer commitments.
- Accountant
- Bills eligible title-transferred scope.
Set up Shipbuilding ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.