July 2026 Updates

New Feature: Additional Location Fields in Excel Import

The Excel Import mapping page now supports mapping 11 additional location fields to your Excel columns. This lets you build BAPLIE files with a more complete location profile per container, including original ports, optional/next port waypoints, transhipment ports, terminals at load and discharge, and multiple onward PODs.

What's new

New location fields available for mapping:

Field	Description
POL Terminal	Terminal identifier at the Port of Load (added to LOC+9)
POD Terminal	Terminal identifier at the Port of Discharge (added to LOC+11)
Original POL	Original Port of Loading (LOC+76)
Optional POD	Optional Port of Discharge (LOC+97)
Next POD	Next Port of Discharge (LOC+152)
Transhipment Port	Place of Transhipment (LOC+13)
1st POD	First onward POD waypoint (LOC+64)
2nd POD	Second onward POD waypoint (LOC+68)
3rd POD	Third onward POD waypoint (LOC+70)
4th POD	Fourth onward POD waypoint (LOC+71)
5th POD	Fifth onward POD waypoint (LOC+74)

All fields are optional and hidden by default to keep the mapping page uncluttered.

How to use

Navigate to Import Excel in the left navigation and upload your Excel file as usual.
On the mapping step, look for the new toggle labeled Include additional location fields (next to the existing "Include over dimension fields" toggle).
Turn the toggle On. The Additional Locations section will expand with 11 new dropdowns.
For each field you want to populate in the generated BAPLIE, select the matching column from your Excel file. Leave any dropdown unchanged (set to "Select a Column") if you do not want to include that LOC segment.
Continue through the import as usual. Populated fields will appear in the generated BAPLIE and can be re-viewed in the Main Content grid.

Terminals: how they are written

POL Terminal and POD Terminal are not separate LOC segments — they are related location identifiers attached to the LOC+9 (Port of Load) and LOC+11 (Port of Discharge) lines. When mapped, the terminal code is appended to the same line, for example:

LOC+9+USNYC:139:6+ABC:TER:306' — POL is New York, terminal code ABC
LOC+11+NLRTM:139:6+XYZ:TER:306' — POD is Rotterdam, terminal code XYZ

9-LOC-per-container limit

BAPLIE 2.2 restricts the number of LOC segments allowed per container to a maximum of nine. The Additional Locations section now includes a live counter that displays how many location fields you have currently mapped:

Location fields mapped: X of 9 maximum per container

The counter updates automatically as you change any of the location dropdowns and includes Port of Load, Port of Discharge, Destination, plus each of the nine new additional LOC fields (POL/POD Terminals are excluded from the count because they attach to LOC+9 and LOC+11 rather than adding a new segment).

If you exceed the limit, the counter turns red and a warning message appears explaining that you must unmap one or more fields before proceeding. The Next button is blocked until the count is back at nine or fewer.

Custom mappings

Saved custom mappings automatically support the new fields. If you had a saved mapping from before this update, it will load unchanged with the Additional Locations toggle off. You can enable it, map any new fields you want, and save the mapping again to preserve your selections.

Bug Fixes

Excel export from Main Content now includes POL Terminal and POD Terminal. These columns were previously missing from the exported spreadsheet even when enabled in the column visibility settings.
Fixed the Excel Import "Issue Reading File" popup being cut off on some screens (from an earlier May 2026 fix, now confirmed working alongside the new fields).