Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/coverage/changelog.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,15 @@ Coverage changes as carriers and terminals come online. This page records what w

For product and API changes, see the [API changelog](/updates/home).

<Update label="October 14, 2026" description="Seaboard Marine added to the public carrier list">
Seaboard Marine (`SMLU`) is now listed as a public carrier, up from 36 to 37 shipping lines in the public set.

- Track Seaboard Marine by bill of lading, booking, or container number. Enter the master bill of lading without the `SMLU` prefix.
- Trailer Bridge (`TRBR`) remains the only account-enabled carrier.

No API endpoint or schema changes are required.
</Update>

<Update label="October 9, 2026" description="New Zealand terminals added">
The public terminal table now lists 138 direct integrations, up from 136 on September 15.

Expand Down
2 changes: 1 addition & 1 deletion docs/coverage/home.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ Terminal49 integrates directly with each supported shipping line and normalizes

Some carriers are live in production but not in the public default set. Contact Terminal49 to enable them on your account.

See [account-enabled carriers](/coverage/ocean-carriers#account-enabled-carriers) for Seaboard Marine (`SMLU`) and Trailer Bridge (`TRBR`).
See [account-enabled carriers](/coverage/ocean-carriers#account-enabled-carriers) for Trailer Bridge (`TRBR`).

## Supported terminals

Expand Down
4 changes: 2 additions & 2 deletions docs/coverage/ocean-carriers.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -1561,13 +1561,13 @@ SCAC `SAFM`.

## Seaboard Marine

SCAC `SMLU`. Account enablement required.
SCAC `SMLU`.

| Section | Feature | Coverage |
| --- | --- | --- |
| Tracking identifiers | Bill Of Lading | Supported |
| Tracking identifiers | Booking Number | Supported |
| Tracking identifiers | Container Number | Not supported |
| Tracking identifiers | Container Number | Supported |
| Origin | POL Name | Unknown |
| Origin | POL Locode | Unknown |
| Origin | POL Timezone | Unknown |
Expand Down
4 changes: 2 additions & 2 deletions docs/data/coverage/coverage.json
Original file line number Diff line number Diff line change
Expand Up @@ -5448,11 +5448,11 @@
"legalName": "Seaboard Marine",
"scac": "SMLU",
"alternativeScacs": [],
"access": "account",
"access": "public",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Keep SMLU gated until production access is confirmed

This value drives the generated public carrier table and downloads, but the commit's own verification notes say all-account production availability is still unconfirmed and that the last observed integration was registered with default: false and zero weight. Publishing it as public now can therefore tell customers they can submit SMLU tracking requests when their accounts may not have a usable integration; keep it account-enabled until production configuration is confirmed, or add checked-in evidence that it is enabled by default.

AGENTS.md reference: docs/AGENTS.md:L20-L20

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leaving this as is. The concern is fair, since the repo alone can't show it: the smlu.mobile migration on staging registers the integration with default: false and weight: 0.0, and production state lives in the database. But Matthew Turner (engineering) said in Slack on 2026-10-14 that the Seaboard mobile integration is "already in production for all accounts" and that it can be tracked by BL or container, which is what this change reflects. The requester has marked the PR ready on that basis. If that turns out to be wrong, reverting is a one-row change to the SMLU entry in coverage.json plus a regenerate (access back to account, containerNumber back to unsupported).


Generated by Claude Code

"features": {
"billOfLading": "supported",
"bookingNumber": "supported",
"containerNumber": "unsupported",
"containerNumber": "supported",
"polName": "unknown",
"polLocode": "unknown",
"polTimezone": "unknown",
Expand Down
122 changes: 61 additions & 61 deletions docs/data/coverage/shipping-lines.csv

Large diffs are not rendered by default.

4 changes: 2 additions & 2 deletions docs/data/coverage/shipping-lines.json
Original file line number Diff line number Diff line change
Expand Up @@ -1857,11 +1857,11 @@
"legalName": "Seaboard Marine",
"scac": "SMLU",
"alternativeScacs": [],
"access": "account",
"access": "public",
"features": {
"billOfLading": "supported",
"bookingNumber": "supported",
"containerNumber": "unsupported",
"containerNumber": "supported",
"polName": "unknown",
"polLocode": "unknown",
"polTimezone": "unknown",
Expand Down
4 changes: 2 additions & 2 deletions docs/data/coverage/shipping-lines.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -1511,13 +1511,13 @@ SCAC `SAFM`.

## Seaboard Marine

SCAC `SMLU`. Account enablement required.
SCAC `SMLU`.

| Section | Feature | Coverage |
| --- | --- | --- |
| Tracking identifiers | Bill Of Lading | Supported |
| Tracking identifiers | Booking Number | Supported |
| Tracking identifiers | Container Number | Not supported |
| Tracking identifiers | Container Number | Supported |
| Origin | POL Name | Unknown |
| Origin | POL Locode | Unknown |
| Origin | POL Timezone | Unknown |
Expand Down
4 changes: 2 additions & 2 deletions docs/snippets/data-sources/carrier-feature-data.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -164,7 +164,7 @@ export const shippingLines = [
"legalName": "Seaboard Marine",
"scac": "SMLU",
"alternativeScacs": [],
"access": "account"
"access": "public"
},
{
"name": "Sealand Americas",
Expand Down Expand Up @@ -2032,7 +2032,7 @@ export const shippingLineCoverage = {
"features": {
"billOfLading": "supported",
"bookingNumber": "supported",
"containerNumber": "unsupported",
"containerNumber": "supported",
"polName": "unknown",
"polLocode": "unknown",
"polTimezone": "unknown",
Expand Down
4 changes: 2 additions & 2 deletions docs/snippets/data-sources/coverage-data.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -235,10 +235,10 @@ export const carriers = [
"legalName": "Seaboard Marine",
"scac": "SMLU",
"alternativeScacs": [],
"access": "account",
"access": "public",
"billOfLading": true,
"bookingNumber": true,
"containerNumber": false
"containerNumber": true
},
{
"name": "Sealand Americas",
Expand Down
4 changes: 2 additions & 2 deletions tools/generate-coverage.test.mjs
Original file line number Diff line number Diff line change
Expand Up @@ -37,11 +37,11 @@ test('only approved public entities and complete feature assessments are exporte
assert.equal(data.terminals.length, 138);
assert.equal(
data.shippingLines.filter((row) => row.access === 'public').length,
36,
37,
);
assert.equal(
data.shippingLines.filter((row) => row.access === 'account').length,
2,
1,
);
assert.equal(data.railCarriers.length, 6);
assert.equal(data.featureCatalog.railCarriers.length, 13);
Expand Down
Loading