BAPLIE is how a container ship tells the next terminal what is in its bay plan. At every departure the terminal or carrier sends a BAPLIE file listing each occupied position: container number, type, weight, port of discharge and special data such as dangerous goods and reefers. The next terminal uses that file to plan discharge and loading before the ship arrives.
Reading bay-row-tier positions on a printed bay plan is covered in our guide on how to read a bay plan. This guide covers the electronic version.
BAPLIE, UN/EDIFACT and SMDG
BAPLIE is a message in the UN/EDIFACT standard, the United Nations framework for
electronic data interchange. An EDIFACT message is built from segments: each starts with a three-letter
tag, data elements are separated by +, components by :, and every segment ends with an apostrophe '.
SMDG, the user group of container carriers and terminals, publishes the BAPLIE implementation guides: which segments are used, which codes apply and how to fill them in. That is why people say "BAPLIE SMDG 2.2" or "BAPLIE 3.1" rather than just "BAPLIE".
Versions 2.x and 3.x
| Aspect | BAPLIE 2.x (e.g. 2.1.1, 2.2, 2.3) | BAPLIE 3.x (e.g. 3.0, 3.1 and later releases) |
|---|---|---|
| Use in the field | Still very widespread, including many regional terminals | Increasingly used by large carriers and modern terminals |
| Structure | Centred on the stowage position, one group per occupied slot | Restructured, with more detail on equipment and cargo in the slot |
| VGM | Many partners send gross weight only | A clear place for the VGM and its verification details |
| Special data | DG, reefer and out-of-gauge available but limited | Richer DG, reefer, out-of-gauge and handling instructions |
| Compatibility | — | Not backward compatible; needs its own parser |
In practice a terminal in Indonesia may receive 2.2 from one carrier and 3.1 from another on the same day. A planning system should read both and record the version of each file.
Key segments at concept level
Below is a simple extract for one container in BAPLIE 2.x style. It is illustrative and shortened; follow the SMDG guide for the version in use for exact order and codes.
LOC+147+0140886::5'
MEA+WT++KGM:26500'
LOC+9+IDSUB'
LOC+11+IDJKT'
EQD+CN+ABCU1234560+45G1+++5'
NAD+CA+XYZ:172:20'
DGS+IMD+3+1263'
| Segment | Purpose | Meaning in the example |
|---|---|---|
| UNB/UNH, BGM, DTM | Envelope, message header, dates | Sender, recipient, creation time |
| TDT | Transport details | Vessel name or code and voyage number |
| LOC+147 | Stowage position | Bay 014, row 08, tier 86, ISO format |
| MEA | Measurements, mainly weight | 26,500 kg |
| LOC+9 / LOC+11 | Port of loading / port of discharge | Surabaya → Jakarta (UN/LOCODE) |
| EQD | Equipment details | Container ABCU1234560, ISO type 45G1, full |
| NAD | Parties, such as the container operator | Operator code XYZ |
| DGS | Dangerous goods | Class 3, UN 1263 |
| TMP / RNG, DIM | Reefer temperature, out-of-gauge dimensions | Not present in this example |
| UNT/UNZ | Message and envelope trailers | Segment count and control reference |
Bay-row-tier coding in BAPLIE
In LOC+147 the position is usually written in the seven-digit ISO 9711 format BBBRRTT: three digits for the
bay, two for the row and two for the tier. So 0140886 means bay 014, row 08, tier 86. The rules are the
same as on a printed bay-row-tier plan:
- odd bays for 20', even bays for a 40' occupying two odd bays;
- odd rows to starboard, even rows to port, 00 on the centreline;
- tiers 02, 04, 06 in the hold and 82, 84, 86 on deck.
Some carriers use their own position format; the code in LOC+147 states which format applies. Always check it before interpreting the digits.
Validating a BAPLIE file
A file that passes syntax checks is not necessarily correct. Useful checks before the file is used:
- Syntax: correct segment count in UNT, matching UNB and UNZ control references, no illegal characters.
- Positions: no duplicate slots, no 40' in an odd bay, no 20' and 40' overlapping in the same space, and every row and tier exists in the vessel profile.
- Containers: valid container check digits, known ISO type codes, weights not above maximum gross and not below tare.
- VGM: present for every full container where the version and partner agreement require it.
- Special data: DG with class and UN number, reefers with a temperature, out-of-gauge with dimensions.
- Rotation: every port of discharge appears in the ship's onward rotation.
Container numbers can be checked with the container number checker, and type codes with the ISO type code decoder.
Common problems in BAPLIE exchange
- Version not agreed. The sender uses 3.1 while the receiver reads only 2.2. Agree the version and send a test file before the service starts.
- Weight in the wrong unit. Kilograms read as tonnes, or the reverse, produce a plan that looks safe when it is not.
- A partial file treated as complete. A BAPLIE may cover the whole ship or only part of it. A terminal that treats a partial file as the full condition can miscount free space.
- Inconsistent port codes. One port may appear under different UN/LOCODEs between partners, for example a city code and a terminal code. Map these codes in the system.
- Incomplete DG data. A class without a UN number, or the reverse, makes segregation checks impossible; see dangerous goods stowage.
The message family around BAPLIE
| Message | Short purpose |
|---|---|
| MOVINS | Stowage instructions from carrier to terminal, for example slots per port of discharge |
| COPRAR | Container discharge or loading order from carrier to terminal |
| COARRI | Report of discharge or loading performed, from terminal to carrier |
| CODECO | Gate-in and gate-out report from a terminal or depot |
| VERMAS | VGM data, see VGM in vessel stowage planning |
| TANSTA | Ship tank status, useful for stability calculations |
Together they form a cycle: the plan is sent (MOVINS, COPRAR), the work is reported (COARRI, CODECO), and the final result travels to the next port (BAPLIE).
Opening BAPLIE with a free viewer
Reading raw BAPLIE in a text editor is tiring. The free BAPLIE Viewer from STOWAGE.ID reads 2.x and 3.x files directly in the browser, so the file is not sent to or stored on a server. It shows a summary per discharge port with weights, DG and reefers, a bay-by-bay view (row × tier, hold and deck), a list of validation errors and a CSV export.
For full planning, STOWAGE.ID Vessel Stowage imports BAPLIE as the starting condition and exports the new plan. STOWAGE.ID is a shore-side planning and decision-support tool; the ship's class-approved loading computer and stability booklet remain the official reference.