Keep transport indents, carrier acceptance and vehicle placement in sync

A carrier accepts an indent for three loads. At loading time, two suitable vehicles are present and the third remains unconfirmed. The dashboard shows “accepted,” so dispatch discovers the shortfall only when the remaining load is ready.

Model the request, response, equipment assignment and observed placement separately. Acceptance is a commitment to a stated version of the work; placement is evidence that an appropriate vehicle has reached the required point and passed the relevant checks.

Select a bounded dispatch flow

Start with one origin site, a small set of lanes, one vehicle requirement family and the participating carriers. Define the planning window, booking source and gate or yard evidence available. Keep unusual cargo or specialised requirements outside the pilot unless their approved process is explicitly included.

Assign the transport planner to demand and tender decisions, the carrier coordinator to response exceptions, the site supervisor to placement confirmation and the integration owner to message recovery. Required vehicle and admission checks remain with the authorised site roles.

Oracle's tender acceptance status records whether a service provider accepted a tender. It is a useful system state, but it does not record physical placement by itself. Oracle Transportation Management 26C — Tender Acceptance Status

For each load, store a stable load identifier, requirement version, origin, destination, time window, equipment requirements, quantity basis and approval. The indent header can group loads, but it should not conceal which one remains uncovered.

Three accepted loads and two placements

This illustrative indent I-900 requests three compatible vehicles for loads A, B and C at 09:00 Asia/Kolkata on 15 October 2026. Each load requires one vehicle; the example does not permit combining loads or substituting capacity merely by adding tonnage.

Acceptance coverage is 3/3, or 100%. Suitable placement coverage is 2/3, about 66.7%. One load remains at risk. Summing two vehicles' spare capacity does not resolve C unless an approved loading and service plan genuinely permits it.

At 08:50, the carrier offers substitute V-C, but its suitability review is incomplete. The state becomes “equipment proposed, checks pending,” not placed. At 09:10 the authorised site process confirms the suitable vehicle has arrived. Record that actual time and retain the original 09:00 requirement so the ten-minute delay remains visible.

The example's placement definition requires both observed arrival and the relevant suitability confirmation. If the business also wants gate arrival regardless of suitability, report it separately.

Bind every response to the requirement it answers

A carrier may accept version 2 after the planner has issued version 3 with an earlier window or different equipment need. Keep the late acceptance and mark it as referring to the superseded request. Do not silently apply it to the new version.

Use an offer identity, load identity, requirement version, provider identity, response type and event time. Distinguish a rejection, an expiry, a conditional acceptance and a withdrawal. A free-text message saying “okay” needs an authorised interpretation if it cannot be reliably tied to the offered work.

The planner should see both the current state and the unresolved communication. A new request is not accepted merely because the old request was.

Resolve the reassignment race

Suppose C's offer to Carrier X expires at 08:30 under the pilot's agreed terms. At 08:31 the planner sends an approved replacement offer to Carrier Y. At 08:32 a delayed acceptance from X arrives.

The workflow must evaluate the response against the offer's current state and governing terms. It should flag the conflict and prevent two active assignments for the same load. Preserve the delayed acceptance rather than discarding evidence that a commercial dispute may exist.

If X had accepted before expiry but the message arrived late, the event and communication evidence may require manual resolution. An integration timestamp alone cannot settle contractual commitment. The transport owner follows the agreed cancellation and acceptance rules.

Make the handoffs explicit

The TMS or planning register owns the current load requirement. The carrier channel supplies responses and proposed equipment. The gate or yard system supplies observed arrival and site decisions. Dispatch readiness consumes those facts alongside load and document readiness; it should not infer departure from placement.

Use stable operation references and store acknowledgements. If an outbound offer times out, determine whether the carrier channel received it before sending a new offer. If a cancellation is unacknowledged, show that uncertainty before awarding the load elsewhere.

Access must be checked for each carrier's offers and assignments. OWASP's object-level authorisation guidance applies when a carrier responds using an offer or load identifier. OWASP — Broken Object Level Authorization

An integration account authorised to relay a response should not be allowed to change the approved equipment requirements or mark site checks complete.

Run the pilot in shadow, then supervised operation

Create a baseline from a fixed group of loads, including late acceptance, rejection, substitution and no-show cases. Label the expected states with transport and site owners. Compare the proposed dashboard with the existing register before it drives assignments.

In supervised operation, retain planner approval for reassignment and site approval for placement. Measure acceptance coverage, suitable placement by required time, unresolved responses, conflicting commitments and manual recovery effort separately.

Acceptance should require every pilot load to resolve to a current assignment or an owned exception, with no unexplained double assignment in the test set. Set performance targets from the baseline and disclose the sample size. A clean small trial does not eliminate future carrier or communication failures.

Stop automatic reassignment if version handling or acknowledgement failures can create competing commitments. Continue the approved manual coordination process with the same load identifiers. Before restarting, reconcile open offers and cancellations with participating carriers; switching off the integration does not cancel a commitment already made.

Show the uncovered load while there is still time to act

The useful control is a clear path from demand to accepted capacity to verified placement. It exposes the load that needs intervention before dispatch treats an acceptance as a truck at the gate.

Next actions

1. Define load-level requirement, acceptance, assignment and placement states.
2. Agree response, expiry, cancellation and substitution rules with the participating owners.
3. Test old versions, delayed acceptances and repeated placement messages.
4. Reconcile all open commitments before supervised automation.

To scope an indent-to-placement pilot, describe how carriers currently accept loads, where vehicle suitability is confirmed and which late changes most often disrupt dispatch.