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.
- Solar Project Management
- Features
- Fulfillment and delivery
Fulfillment and delivery
Pick, dispatch and record each stop outcome.
OverviewRoute Schedule×
Solar Project Management · Fulfillment and delivery
New
Route Schedule
Delivery routes
| Route number | Coordinator | Assigned operator | Planned start | Planned end | Status | |
|---|---|---|---|---|---|---|
| DR-29824 | 16 Oct | 21 Oct | Released | |||
| DR-54397 | 14 Oct | 16 Oct | In progress | |||
| DR-24828 | 19 Oct | 23 Oct | Released | |||
| DR-21936 | 15 Oct | 24 Oct | In progress | |||
| DR-28396 | 26 Oct | 28 Oct | Released |
6 of 6 records
DR-29824Delivery routes · DR-29824
ReleasedPlanned start16 Oct
Planned end21 Oct
What you can do
Operating the module
A shipment belongs to an order and records actual dispatch. Route stops name the shipment and sequence. Delivery attempts record visits; results assign accepted, refused, failed and damaged quantities to shipment lines.
How the work is organized
- Pick. Warehouse Operator works from reserved order scope and records what is ready for dispatch.
- Route. Warehouse Manager assigns an operator, stop sequence and load evidence before releasing the route.
- Result. The operator records each visit and accepted, refused, failed or damaged line quantity.
What to agree during setup
Agree who sequences stops, who releases routes and which evidence travels with the load. Select the title rule for each order. Decide how failed, refused and damaged quantities reach an exception review and how a follow-up stop is recorded.
Check the handoff on an actual case
A warehouse dispatches two dealer orders on a planned route. The coordinator sequences stops and assigns an operator. The manager checks transport and load evidence before releasing the route. At the first stop, the dealer accepts part of a shipment and refuses the remainder. The operator records the visit and quantities; the shipment stays partly delivered and the unresolved scope can be followed.
At the second stop, the dealer is absent. Record the attempted visit and leave that shipment’s result unresolved instead of marking the whole route delivered. A later visit can use a successor stop while the original attempt remains in the history. The Warehouse Manager checks that each stop points to its shipment and that the route contains the assigned operator and transport evidence before release.
For the first dealer’s partial acceptance, compare the delivered line result with the dispatched line quantity. The remainder needs an owner for rescheduling or return review. The selected title rule matters to billing: transfer at dispatch and transfer at delivery produce different eligible invoice scope. Accountant should see only the scope supported by that rule and the actual events. Warehouse Operator records the physical result; Warehouse Manager resolves the route exception.
Before a load leaves, compare the pick with the reserved line and the actual dispatch quantity. The route coordinator should see every stop in a stable order. If a dealer refuses an item, record that outcome against its shipment line; do not merge it with goods the same dealer accepted. Warehouse Manager can then decide whether another visit or a return review is needed.
What your team sees
- Route Schedule — Released routes with operator and planned window.
- Shipments Needing Delivery Result — Dispatched shipments whose line outcome still needs recording.
Follow the work through
Follow the dealer order from commitment through recorded delivery. Use the supplier purchase when replenishment is needed, and the invoice close to trace the financial handoff. The data model helps your team prepare linked records.
What it keeps track of
Data model- Shipments
- Actual dispatch and title/delivery state separated for partial deliveries.
- Shipment lines
- Actual dispatch quantities and current title-transferred/delivered portions.
- 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.
- 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.
Who uses it
Permissions- Warehouse Manager
- , Warehouse Operator.
- The preparer records the work, and the named manager reviews the decision in the relevant entity and warehouse.
Set up Solar Project Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.