Distributionoperational

Dispatch Planning

How is an outgoing consignment planned — warehouse, gate, dates, cargo, and purpose?

Dispatch planning creates the consignment record before anything moves: which warehouse and gate, by when it must be prepared, when the cargo is picked up, how big and heavy it is, and why it is going out. Every consignment carries an automatically generated reference.

What it records

  • Gate-level departure

    The consignment names the specific warehouse gate it leaves through, from the gates registered on that warehouse.

  • Two dates, two phases

    Preparation due date and cargo picking date are separate fields driving the preparation and shipping phases.

  • Cargo declared up front

    Size and weight are recorded on the consignment, so vehicle and carrier choices are made against stated cargo.

  • Position-scoped registers

    Distribution settings templates are assigned to organization positions, giving each team its own consignment register.

  • Recorded rejections

    Sourced requests can be rejected by reference, leaving a trace instead of a silent removal.

How it works

The create screen fixes the operational facts of the movement. The source warehouse is chosen from the warehouse hierarchy and the gate from that warehouse’s registered gates. Two dates separate the work: the order preparation due date, which drives the warehouse side, and the cargo picking date, which drives the transport side. Cargo size and weight, a priority, a purpose from the reference data, a posting account, and free-text notes complete the record.

Whether a shipment is required at all is a flag — a consignment can be prepared for pickup without transport being arranged. Consignment registers are grouped under named distribution settings templates assigned to organization positions, so a site or team sees its own register with its own defaults. Rejecting a sourced request is a recorded action with the request’s reference, not a deletion.

See dispatch planning running in continON.

A guided walkthrough on a sanitized demo tenant — this capability inside its module, on the shared platform.