Rail ERDs and Cuts
In container shipping, efficiency and timing are paramount—especially for exports that rely on rail transport to reach seaports. Two key milestones that shape this process are the Earliest Receiving Date (ERD) and the Cut-off Date.
Rail ERDs and Cut-offs are critical checkpoints for exporters. Managing them poorly leads to fees, delays, and missed customer commitments. Managing them well builds a reliable, cost-efficient supply chain.
Splice gives shippers and logistics teams the visibility, accuracy, and tools they need to stay ahead of deadlines, coordinate across transport modes, and communicate seamlessly with partners. With direct data feeds, predictive modeling, and clear indicators in both the portal and API, Splice ensures that rail receiving dates are managed with confidence.
What Are Rail Earliest Receiving Dates (ERD) and Cut-Off Dates?
The ERD is the earliest date that a container can be delivered to a rail terminal for export. Set by the shipping line for US railroads but set by CN and CPKC for their terminals, the rail ERD keeps shipments aligned with vessel schedules, avoiding unnecessary dwell time or storage costs.
The Cut-off Date is the final day a container can be delivered to the rail terminal to ensure it loads on a train that will arrive at the marine terminal before its cut-off date.
Splice’s Rail Receiving Date Process
Please note: The rail terminal name or FIRMS code is required to align the shipment to train schedules.
Splice integrates data from multiple sources to capture and predict rail receiving dates.
-
Document Extraction
Rail ERDs and cut-offs may be included in initial booking confirmations or in updated confirmations. When these documents are sent to Splice, the platform automatically extracts the dates and applies them to the booking. -
Direct Data Feeds
Splice automatically pulls official ERD and cut-off dates directly from CN and CPKC. -
Predicted Values for U.S. Class 1 Railroads
For NS, CSX, UP, and BNSF, neither the railroads nor the ocean carriers provide direct data feeds for rail receiving dates. To fill this gap, Splice predicts ERDs and cut-offs based on vessel schedules, marine terminal receiving dates and rail schedules.
Predicted values protect against delayed or missing carrier updates. However, they may not always match the official dates published later by carriers. In the portal, predicted values are ✨ marked ✨ for clarity. In the API, these dates are explicitly denoted as predicted.
This layered approach, using terminal data, extracted confirmations, direct feeds, and predictive modeling, ensures maximum coverage and reliability, even when official data is delayed or unavailable.