Integrations · Yard and transport systems
Events for yard and transport systems: customs’ replies, delivery orders and gate papers as they happen
Updated
SCMTR.io works beside the yard and transport software you already run. Your CFS, ICD, empty-yard or transport system is told as it happens — customs’ reply to a CSN recorded, a bill reaching the shipping line’s manifest, entry inward granted on a bill you watch, a delivery order released, an empty release order or a Form 13 issued, a container’s free days ending — each event naming the filing, bill or paper that changed. SCMTR.io is not a yard or transport system; it feeds yours.
The events a yard or a transporter acts on
What changes a gate plan or a vehicle booking, as it happens.
- A CSN sent, and customs’ reply to it recorded — accepted or refused
- A bill on your CSN reaching the shipping line’s manifest
- A bill you asked BL tracking to watch changing on customs’ record — reaching the manifest, or entry inward granted
- The shipping line giving another arrival day for a bill on your CSN
- A delivery order released on the Line desk — to the line that released it and to the customer it is released to
- An empty release order (CRO) or a container’s Form 13 issued on the Line desk
- A container’s free days ending, and an export call’s cut-offs coming near, on the Line desk
- Customs’ answer to a report your CFS or ICD filed
What an event carries
Enough to know what changed and where to read it.
- What happened, when, and the filing, bill or paper it is about, by its number
- Your system reads the rest through the API, with its own key
- An alert’s event carries the alert as your people read it in the app — its title and its text
- Only your own organisation’s filings, bills and reports
Pushed to your system, or read by it
Whichever your system can do.
- Pushed: each event sent to an address of yours as a signed webhook, as it happens
- Read: your system asks the event feed what is new since the place its last answer gave — for a system that cannot receive messages from outside
- The event feed keeps each event for 30 days, so a system switched off for a week reads the week it missed
And at the gate itself
With no system at all, a paper issued on the Line desk is checked by its QR code.
- Any DO, Form 13 or empty release order issued on the Line desk checked at your gate by its QR code, with no account needed
- A CFS or empty yard on SCMTR.io marks each container delivered, or its empty returned
- A delivery order that names your yard comes to you as the paper itself, checked by its QR code — not as an event
What stays in your yard or transport system
- Your gate register, your yard plan and your stock: SCMTR.io keeps none of them
- Your vehicles, drivers and trips: SCMTR.io books none
- Your own SCMTR reports — stuffing, stripping and the vehicle’s times — are still filed on SCMTR.io, signed with your DSC
Questions yards and transporters ask first
Read next
Is SCMTR.io a yard (WMS) or transport (TMS) system?
No. SCMTR.io plans no yard, books no vehicle and keeps no gate register. It gives your yard or transport system the news it acts on, as it happens, so nobody has to phone or retype it.
Which events can our system read?
The ones a yard or a transporter acts on: customs’ reply to a CSN recorded, a bill reaching the shipping line’s manifest, entry inward granted on a bill you watch, a delivery order released, an empty release order or a Form 13 issued, a container’s free days ending. Each is about your own organisation’s filings, bills and reports.
Our system cannot receive webhooks. Can it still read events?
Yes. It asks the event feed on its own schedule and reads what is new, oldest first: events are handed out in order, each once, a short settling time after it happens. It keeps the place the last answer gave and asks from there next time. The feed and the webhooks carry the same events, so a system that must be certain can use both, or read a stretch of the feed again.
What does an event carry?
What happened, when, and the filing, bill or paper it is about, by its number. Your system reads the rest through the API with its own key. An alert’s event carries the alert as your people read it in the app — its title and its text.
Does our CFS still file its own reports on SCMTR.io?
Yes, as before: the stuffing report, its cancellation, stripping and the vehicle’s times are prepared, checked, signed with your DSC and sent on SCMTR.io. Events are the other direction — what your own system hears.
What does it cost?
Nothing. Connect is free on every plan, like the API. The API keys, the webhooks, the event feed, the import profiles and the write-back sheet are all part of it.
Let your yard system hear it first
Filing is free — every filing feature, no caps, no card. Connect is free on every plan, like the API.