Shipment planning

Transportation Planner begins with the physical movement: where the freight leaves, where it goes and what needs to travel. Shipment records keep origin address and destination address alongside ZIP information, mode, weight in pounds and freight class. Requested ship date and requested delivery date describe the request; planned delivery date records the commitment being followed. Keeping those dates distinct allows Dispatcher/Ops to explain a missed commitment without changing the original request.

The Shipments page supports searchable freight filters and a selected-shipment detail panel. A row opens the native shipment form. Its Tender Queue, In-Transit Board and POD Pending Capture toggles provide operational scopes. During setup, check those scopes against representative shipments and the person using them. Use a planned movement and a delivered movement to check that each scope brings the right work into view.

• Describe the cargo. Cargo item records retain item description, quantity, weight in pounds, freight class and package type for the contents. Review the shipment header weight against the item evidence before asking a carrier to quote. Use the hazardous-goods UN number on an item to locate the accompanying shipping documents for review.
• Keep the movement connected. Movement leg records represent a mode change or carrier handoff, with departure address, arrival address, scheduled departure and scheduled arrival. Stop records retain the stop sequence and planned or actual arrivals. A leg marked Completed and a shipment marked Delivered describe different levels of work.
• Build a load deliberately. Load records group a carrier movement, while load membership records link its shipments with stop sequence and allocated cost. Check each linked shipment and its weight before interpreting total weight in pounds or total cost. Agree the physical loading plan with the carrier before treating the grouped shipments as ready to move.

Agree how the external warehouse reference enters the shipment, or choose how planners create a manual movement. Preserve shipment number, bill-of-lading number and PRO number according to the documents actually used. Decide which freight modes and service requirements enter the pilot, and who confirms cargo weights when the warehouse and carrier disagree.

Assign cargo-item entry to an account with confirmed access. Transportation Planner owns the shipment header, and Dispatcher/Ops prepares movement legs and stops. Agree how shipment weights and freight classes enter from the packing documents. Transportation Planner and Dispatcher/Ops should open the same pilot shipment and compare the cargo details with the bill of lading. Keep the upstream reference available when a weight or destination needs correction.

Use a pallet shipment with an origin ZIP, destination ZIP, known weight and an agreed freight class. Transportation Planner creates it in Planned, verifies the contents and waits for the rate-shop result. If no contract matches, the shipment should keep its prior values and the logged reason should explain the gap. Add a second leg only if a real carrier handoff exists; examine the stop order with Dispatcher/Ops before tendering.

Compare the native form with the source documents. Use the warehouse reference to trace the upstream delivery. Confirm stock release and physical collection with the connected warehouse process before treating the freight as dispatched.

• Tender Queue — Planned or Tendered shipment details with carrier, service, applied contract and estimated cost for planning review.
• Load Planning Board — Load identities and Building, Tendered or Dispatched states for an account with confirmed load access.

Follow rating and tendering, then follow movement evidence.