Freight Intake

Dispatcher records a freight order against the customer, with its origin, destination, weight and weight unit. The promised date expresses the customer’s requested timing. These details give Transport Manager a concrete lane to plan and give Finance Officer the order context for linehaul, fuel or accessorial charges.

Customer identity matters before the order becomes transport work. Parties distinguish Customer, Carrier and Provider, with a name and contact email. Transport Manager maintains that directory so Dispatcher can select the intended customer instead of relying on a similar name in a message. The order-capture workflow raises a Requested trip for the customer lane.

• Customer context. Select the customer party and confirm the origin and destination. Use a lane description the planning team can interpret consistently when it prepares the trip and its stops.
• Weight and timing. Record the weight together with its unit and the promised date. Keep the unit visible when comparing the shipment with vehicle capacity or discussing the request with the customer.
• Planning handoff. Inspect the Requested trip raised from capture and confirm that its customer and lane match the intended order. Transport Manager then plans the vehicle, driver and trip dates.

Agree how Dispatcher records an origin or destination when a customer uses several operating sites. Decide which contact detail belongs in the customer directory and which location wording belongs on the freight order. Clear lane names reduce the chance of planning a trip to a similarly named facility.

Set the convention for weight units and promised dates before importing existing orders. A weight value without a common unit cannot be compared responsibly with a vehicle’s capacity. Also agree how the team identifies the result of order capture when several orders share the same customer lane. The dispatcher should inspect the actual generated trip before handing it to planning.

Rehearse a customer request from a regional depot to a distribution facility. Dispatcher enters the lane, shipment weight and promised date, then uses the capture action. Ask Transport Manager to identify the resulting Requested trip and verify its customer, origin and destination before assigning resources.

Repeat the exercise with another order on the same lane. The team must distinguish the intended work rather than treating a matching destination as sufficient identification. Ask Finance Officer to add a freight charge to the correct order and show that order’s weight and promise context. Keep freight-order timing separate from the recorded trip schedule when discussing a later change.

• Freight Orders by Promise — Orders whose promised date has arrived, for a review of their customer and lane context.
• Customer Directory — Customer records used during freight capture and trip planning.
• Requested Trips — Trip work ready for resource planning and dispatch approval.

Continue with freight intake and dispatch, then trip execution and delivery as the movement proceeds.