Skip to main content

Minimum Data

Minimal Data Needed to Track a Booking in Splice Exports​

Splice Exports is designed to help logistics teams track export container bookings with precision – even when source documents vary in format or quality. To begin tracking a shipment and enabling schedule monitoring, ERD tracking, and historical visibility, Splice Exports requires just a minimum of data.

Below are the essential elements needed to initiate tracking, along with two supporting elements that enhance accuracy for certain use cases.

Required Data Fields​

1. Booking Number​

The booking number is the primary reference for each shipment.

  • Splice uses it to organize all associated records, track changes, and link documents.
  • In some cases, it allows Splice to query carriers or terminals directly for updates – such as new vessel schedules, updated receiving windows, or container status changes (e.g., rollings).
  • This identifier also allows for historical visibility across document and data changes.

2. Vessel Name​

The vessel name tells Splice Exports which ship to monitor.

  • The vessel is processed through Splice’s data cleansing operations to ensure that it matches an IMO-registered vessel.
  • Splice monitors vessel schedules across major carriers calling U.S. and Canadian ports and continuously updates your booking as those schedules change – before departure, in transit, and at destination.

This allows tracking to begin even before the container reaches the terminal.

3. Ocean Carrier​

The ocean carrier determines where Splice looks for booking and schedule data – and whose data to prioritize when updates differ.

  • Knowing the carrier ensures we connect to the correct data feed or carrier portal.
  • In cases of conflicting updates, the listed carrier helps determine which source takes priority.
  • Because of vessel-sharing agreements and alliances, Splice also monitors the schedules of related carriers – redundancy is a strength, and helps protect against missed or partial updates.

4. Port or Marine Terminal​

The port or terminal designates which point in the vessel’s rotation applies to your booking.

  • If a terminal is known, Splice will begin tracking that location immediately.
  • If only a port is provided, Splice will determine the likely terminal based on service routes, carrier practices, and vessel assignments.
  • Earliest Receiving Dates (ERDs) are sourced directly from terminals. While some carriers may provide ERDs, Splice treats the terminal as the authoritative source.

Terminal-level specificity ensures your receiving and cutoff tracking is accurate and timely.

While not required to begin tracking, the following two fields help improve accuracy and context, especially for multi-port vessel rotations and inland moves.

A. Anchor Date​

Vessels follow a global rotation, and it’s possible for a vessel to call a port multiple times – before and after a referenced booking. Without an anchor date, Splice may apply the first available vessel call in the schedule, which can lead to incorrect ERD or cutoff tracking.

  • The anchor date helps Splice determine which vessel call applies to your booking.
  • This can be any date associated with the booking—such as:
    • Estimated Time of Arrival (ETA)
    • ERD
    • Documentation Cutoff
    • Cargo Cutoff

When provided, this date ensures the system applies vessel tracking logic to the correct voyage.

B. Rail Receiving Dates​

If your shipment involves a rail move (ramp-to-port or port-to-ramp), Splice can track receiving windows at inland rail terminals across the U.S. and Canada.

To enable this functionality:

  • Include the rail terminal name or
  • Provide the FIRMS code (a unique 4-character identifier assigned by CBP)

Splice uses this information to:

  • Determine ERDs and LRDs at the correct rail terminal
  • Monitor changes in availability
  • Ensure that inland moves align with cutoffs and port departure schedules

Summary​

To begin tracking a booking in Splice Exports, provide the following required data:

  1. Booking Number
  2. Vessel Name
  3. Ocean Carrier
  4. Port or Marine Terminal

To improve accuracy and context, especially for complex routes or rail moves, we recommend also including:

  • Anchor Date
  • Rail Terminal Name or FIRMS Code

If you’re importing bookings in bulk or unsure whether your data meets these guidelines, reach out to our team for assistance. You can also continue exploring the Knowledge Center for guidance on data formats, integrations, and best practices.