1. Cement ERP
  2. Features
  3. Dispatch and delivery routes
Feature · Dispatch and delivery routes

Dispatch and delivery routes

Pick reserved stock, release routes and record what each dealer stop received.

OverviewMy pick tasks
Cement ERP · Dispatch and delivery routes

My pick tasks

Pick tasks

New
Pick numberOrder lineReservationPlanned startPlanned endPicked quantity
PT-39857SOL-4606IR-2751522 Oct31 Oct500
PT-20547SOL-5259IR-8341904 Oct06 Oct340
PT-74333SOL-5964IR-1809512 Oct16 Oct530
PT-71828SOL-8569IR-1120714 Oct16 Oct690
PT-52695SOL-9039IR-1946921 Oct26 Oct750
6 of 6 records
SOL-4606Pick tasks · PT-39857
Assigned
ReservationIR-27515
Planned start22 Oct
Planned end31 Oct
Picked quantity500
Example screen with sample data

What you can do

Plan the load before the truck leaves

Dispatch starts from reserved stock. Accepted order lines hold inventory reservations against specific positions and stock layers, and the Warehouse Operator works pick tasks that tie each picked quantity to its order line. A shipment in Deliveries groups the lines leaving one warehouse for one order, with the mode (own delivery or external carrier), the carrier reference when there is one, and the title rule copied from the order.

The Warehouse Manager plans delivery routes by hand: a coordinator, an assigned operator, the source warehouse, a transport reference, a planned start and end, and route stops in a stated sequence. Each stop belongs to one shipment and keeps a snapshot of the delivery address, so a later change to the dealer’s contact details does not rewrite where the truck went. Route optimization and live vehicle tracking are outside the app.

How the work is organized

  • Release the route as a decision. A route moves from pending approval to Released only with stops, an operator, a coordinator and transport evidence, and the Warehouse Manager records the route release decision.
  • Dispatch what was picked. A shipment moves to Dispatched with dispatch evidence and a quantity no larger than the verified ready scope. Picking alone does not post cost of goods sold.
  • Record each visit separately. delivery attempts record arrival, completion and evidence at a stop. Delivery results split each shipment line into accepted, refused, failed and damaged quantities, and a correction points back to the result it replaces.

What to agree during setup

Agree which warehouses dispatch, how picking and dispatch locations are set up, and who coordinates routes. Decide when title transfers for each kind of order, at dispatch or at delivery, because title and delivered quantity are tracked separately on delivery lines. Agree what counts as delivery evidence, such as a signed delivery note or a dealer acknowledgment, and who reviews an attempt marked review required. Decide how a stop that is refused or rescheduled is resolved and who closes the route.

Check the handoff on an actual case

A route with several dealer stops leaves the plant warehouse. At one stop the dealer accepts most of the load but refuses part of it because some bags are torn. The operator records the attempt and a result with accepted and damaged quantities. The stop becomes Partial and the shipment becomes partially delivered.

The damaged quantity stays linked to the shipment line, so a return can be authorized against it and the invoice covers only the title-transferred quantity. Once every stop is Delivered, Refused, Failed or Resolved, the route can move to Completed and then Closed.

During the pilot, submit the same delivery attempt twice with the same operation key. The second submission should not add to the delivered quantity. Also try to release a route that has no stops; the release should be refused.

What your team sees

  • Delivery route schedule — routes by planned start and end, with operator, coordinator and status.
  • Routes awaiting release — routes waiting for the Warehouse Manager’s release decision.
  • Shipments in dispatch — shipments from planning through dispatch, partial delivery and exception.

Follow the work through

Review the implementation plan before connecting a carrier.

What it keeps track of

Data model
Deliveries
Actual dispatch and title/delivery state separated for partial deliveries.
Delivery 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.

Who uses it

Permissions
Warehouse Manager
, Warehouse Operator, Sales Representative.
The Warehouse Manager plans and releases routes and resolves delivery exceptions.
The Warehouse Operator picks, dispatches and records what happened at each stop.
The Sales Representative follows delivery progress for the dealers they look after.

Set up Cement ERP your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started