Skip to main content

Where We Get Data

Splice Exports combines data from multiple sources to provide a single, reliable view of your export bookings. Each data element displayed in the portal may come from a different system, such as a carrier, terminal, booking document, your team, or Splice’s own projections.

This article breaks down the specific source for each field to help users understand where data originates and why some values are more dynamic than others.

Customer-Provided Information

Some core details are provided by you, the customer. These values serve as the foundation for Splice to monitor bookings, match schedules, and collect data from other sources.

FieldSource
Booking NumberProvided by customer via upload, API, or booking document
CarrierSame as above
VesselSame as above
Departing PortSame as above
Rail TerminalSame as above (when applicable)

This information is usually extracted from booking confirmations or submitted through one of the following methods:

  • API integration
  • Regular data feeds (e.g., spreadsheet uploads)
  • Document parsing (typically via email)

Once submitted, Splice Exports uses this data to:

  • Match schedules with carrier data
  • Identify the correct terminal or rail ramp
  • Track changes in vessel or port timelines
  • Normalize naming variations through the data cleansing process (See the[ Data Cleansing article] for more.)

Accurate customer input helps ensure timely and relevant updates across the rest of the booking.

Vessel and Port Movement Data

FieldSource
Estimated ArrivalOcean carrier or terminal
Actual ArrivalOcean carrier or terminal, most often the ocean carrier

Estimated and actual arrival dates are updated continuously.

Marine Terminal Receiving Windows

FieldSource
Early Return Date (ERD)Marine terminal
Carrier ERDOcean carrier, typically from booking confirmation
Last Return Date (LRD)Ocean carrier or terminal, but Splice prioritizes carrier
Documentation CutoffBooking confirmation or ocean carrier
VGM CutoffBooking confirmation or ocean carrier

Splice treats terminal-provided ERDs as authoritative. Carriers often provide estimates, and Splice shows both when available, clearly noting the source.

Rail Movement and Ramp Data

FieldSource
Rail TerminalBooking confirmation
Rail Early Return DateBooking confirmation or rail (Canada only); Splice projection (U.S.)
Rail Cutoff DateSame as rail early return date
Rail Estimated DepartureSplice projection based on train schedules
Rail Estimated ArrivalSplice projection based on train schedules
Rail Actual ArrivalOcean carrier, as available

U.S. rail data is often unavailable in real-time. Splice fills this gap using schedule-based projections and historical trends. Canadian ramps may provide ERD and cutoff data, which Splice incorporates when available.

Why Sources Vary

Export bookings involve multiple parties — ocean carriers, terminals, railroads, and your internal systems. Not all use the same timelines or data standards.

Examples:

  • A carrier may update a cutoff, while the terminal has not yet posted the change.
  • Terminals issue ERDs based on their specific capacity and vessel schedules.
  • Rail ramps often lack standardized feeds, especially in the U.S.

Splice tracks across all sources and highlights the most reliable one for each data point.

Summary

Splice Exports aggregates data from the most authoritative and timely sources available:

  • Customers: Booking number, carrier, vessel, voyage, equipment details
  • Carriers: Schedule updates, confirmations, cutoffs
  • Terminals: ERDs and receiving windows
  • Rail Providers: Direct input (Canada)
  • Splice Projections: U.S. rail estimates based on schedules and trends

Understanding where each piece of data comes from helps you troubleshoot delays, answer customer questions, and manage bookings with confidence.

Need help validating a field? Visit the History Page for a timeline of updates and their sources—or contact us at support@splice-it.com.