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.
- Aerospace ERP
- Features
- Fulfillment and returns
Fulfillment and returns
Pick accepted demand, dispatch actual scope and record delivery outcomes.
OverviewPick work assigned to me×
Aerospace ERP · Fulfillment and returns
New
Pick work assigned to me
Pick tasks
| Pick number | Order line | Status | Planned start | Planned end | |
|---|---|---|---|---|---|
| PT-54668 | SOL-4917 | Assigned | 22 Oct | 29 Oct | |
| PT-48474 | SOL-4826 | In progress | 10 Oct | 13 Oct | |
| PT-48105 | SOL-1314 | Picked | 27 Oct | 04 Nov | |
| PT-71404 | SOL-8432 | Partially picked | 13 Oct | 15 Oct | |
| PT-63220 | SOL-5288 | Exception | 18 Oct | 26 Oct |
6 of 6 records
SOL-4917Pick tasks · PT-54668
AssignedPlanned start22 Oct
Planned end29 Oct
What you can do
Keep the working basis clear
A customer order has two lines, but one shipment can satisfy only part of one line. Warehouse Operator picks against the approved reservation and records actual dispatch quantity. Warehouse Manager releases a manual route with assigned operator and stops. The delivery attempt records accepted, refused or damaged quantities separately from the dispatch event.
How the work is organized
- Pick and dispatch. Warehouse Operator picks against hard reservations and records actual shipment quantity separately from the route plan.
- Route and visit. Warehouse Manager releases a staffed manual route; each visit records its own accepted, refused, failed or damaged outcome.
- Return scope. A return decision uses the original net unreturned quantity, with physical disposition kept apart from customer credit.
What to agree during setup
Agree title transfer at dispatch or delivery on the customer commitment. Name the route coordinator and operator, and agree what evidence proves each visit. A route with stops is a plan; the shipment and delivery attempt show actual work. Keep different people responsible for recording the handoff and authorizing a return.
Check the handoff on an actual case
Pick only part of an order line and dispatch that quantity. At the customer stop, record accepted and refused portions against the same delivery line. Keep the refused portion out of billable title scope where delivery is the agreed title rule. Authorize a later return only within the delivered quantity that has not already been returned.
A refused delivery can require another visit or a customer return, but those are different events. Warehouse Operator keeps the first attempt with its actual result and links a later stop where needed. Warehouse Manager compares each line outcome with the dispatched quantity before closing the route. Sales Representative can tell the customer what remains promised without counting refused units as delivered. If goods come back, record their actual quantity and condition before deciding restock, hold or another disposition. Finance then uses the original sale and return scope when considering a credit, rather than assuming the warehouse action itself settled the account.
What your team sees
- Delivery route schedule — Released routes, assigned operators and planned visit windows.
- Delivery exceptions — Shipments whose outcome needs review after dispatch.
Follow the work through
Follow dispatch and return to compare planned stops with actual line outcomes. Trace the original order and return line in the data model, then test the authority path in roles.
What it keeps track of
Data model- Pick tasks
- Actual picked quantities remain exclusively tied to the order and do not post COGS.
- Reservations
- Exclusive bounded demand claims through picking and owned transit.
- 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.
- 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.
- Approval decisions
- Authoritative human decisions independent of document lifecycle.
Who uses it
Permissions- Warehouse Operator
- Records picks, shipment and visit facts.
- Warehouse Manager
- Releases the route and reviews return authorization.
- Sales Representative
- Follows the customer commitment and communicates the remaining promise.
Set up Aerospace ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.