Which schedule owns the shipping handoff after a route change?
Operate carrier changes with a versioned handoff that distinguishes confirmed bookings from newly available options.
A new connection is not a confirmed booking
A carrier's new route or port call may create an option without confirming the schedule of an existing shipment. Shipping, inventory and transport teams can each hold a plausible but incompatible version. Truthound can check the dates and keys of the shared handoff table.
The November announcement
Maersk's November 6, 2026 Asia-Pacific update describes Asia–Europe routing and port-coverage adjustments scheduled through November. The primary evidence here is its own network announcement. Third-party market statistics should not become claims about a specific voyage.
Choose the operating version
Keep origin, destination, service, voyage, schedule version and applicability period in the shared register. Distinguish an announced option, a booking under confirmation and a confirmed booking. A familiar service name does not establish that an earlier port sequence remains current.
Different clocks have different owners
Cargo-ready time, terminal cutoff, scheduled departure and ETA are different commitments. Preserve their sources and timezones and assign who confirms each change. A ready time later than cutoff should become an exception to investigate, not a value automatically adjusted to fit.
The handoff table Truthound can check
Truthound Core Python SDK 3.3.4, operating on a prepared Polars table, provides DateOrderValidator for meaningful date pairs and MultiColumnUniqueValidator for a declared composite key. Owners define required timing relationships and whether booking state and schedule version belong in the key.
Compare the existing predicate
An existing Pandera 0.35.0 pandas schedule predicate can remain. Compare a missing cutoff, an old-version connection and timestamps from different zones. Valid date types do not establish the full handoff contract, and product documentation alone does not show equivalent results.
Do not rewrite the earlier plan
Preserve the schedule used for an earlier planning decision. When a revision arrives, identify affected bookings rather than silently replacing history. Keep the previous ETA separate from the current ETA so a delay interpretation and a planning change remain explainable.
Route each change to its owner
Different exceptions need different owners: a port change requiring carrier confirmation, warehouse cargo readiness and an arrival change affecting inventory. A revised source notice should not bulk-mark every team's action complete.
The schedule usable today
The usable schedule today is a version reconciled to current bookings and scope, not simply the newest filename. Record what the next announcement must trigger for review. That keeps expanded routing choice distinct from committed transport.
Conditions
Use authorised schedule and booking extracts with confirmed timestamp, timezone and version meanings.
Alternatives
Keep existing Pandera 0.35.0 pandas predicates under the same voyage, cutoff and timezone definitions.
Limitations
Date and key checks do not guarantee a carrier's actual departure or arrival.
Evidence
- Event checked
- Subject checked
- Modified
