Skip to content

SCMTR.io for CFSs, ICDs and transhippers

SCMTR filing for CFSs, ICDs and transhippers

Updated

A CFS or ICD reports each container it stuffs, any cancellation or stripping, and the vehicle’s departure and arrival; a gateway CFS files its import transhipment of LCL cargo on to an ICD, and a transhipper its request, departure and arrival (both in beta). On SCMTR.io you say what happened, the report is laid out and checked for it, and you sign it with your DSC and send it under your ICEGATE API key — the key your organisation generates on the ICEGATE portal.

The SCMTR filings you make on SCMTR.io

  • SF

    Stuffing report

    Laid out for the container stuffed, the PCIN filled from the shipping bill, signed and sent under your ICEGATE API key

  • SFCN

    Stuffing cancellation

    Started from the stuffing report it cancels

  • ST

    Container stripped or opened

    Prepared, checked, signed and sent from the same screen

  • DT

    Vehicle departure time

    Follows on from the transhipper’s departure (DP) in one press, its CIM number carried over

  • AT

    Vehicle arrival time

    Prepared, checked, signed and sent from the same screen

  • ITP

    Import transhipment (LCL cargo on to an ICD)Beta

    Its three parts laid out from the fields customs published — the new container, each old container with its SMTP, and the import report — checked, signed and sent under your ICEGATE API key

  • ASR

    Allowed for shipment requestBeta

    One per shipping bill, started from the stuffing report

  • DP

    Departure from an inland stationBeta

    Prepared, checked, signed and sent under your ICEGATE API key

  • AR

    Arrival at the next stationBeta

    Prepared, checked, signed and sent under your ICEGATE API key

Each one prepared, checked, signed with your own DSC and sent to ICEGATE from one place.

A CFS stuffing report on SCMTR.io for one container and two shipping bills at a CFS in Nhava Sheva: the container’s number, type, seal and packages, and the report ready to sign.
A stuffing report for one container and its shipping bills, ready to sign. · Invented data.

Say what happened

Container stuffed, vehicle departed — the report follows.

  • Each report in the yard’s own words, laid out for the event
  • Start from the shipping bill: its PCIN fills itself
  • The next container of the same bills in one press, package numbers carried on
  • Each report started from the one before it: the stuffing report, the transhipper’s request for each shipping bill, the departure and the vehicle’s times

Checked as you type

Problems to fix, flagged before you sign.

  • Each shipping bill’s standing on customs’ record shown beside it
  • Container numbers, package ranges and codes checked before you sign
  • A file from your own yard software opened and checked the same way

Signed, sent, answered

Under your ICEGATE API key.

  • Signed with your DSC and sent under your ICEGATE API key, or saved for ICEGATE’s API utility
  • Customs’ reply laid on the report, field by field
  • A cancellation’s wait for the officer’s approval said in words
  • DOs naming us, for a CFS or an empty yard: the DO for its containers from every line on the Line desk, each marked delivered at the gate or its empty returned — the line and the customer see it at once — and each released DO e-mailed with its PDF to the CFS, to the terminal for a direct port delivery, and to the port’s custom house where the line gives their addresses, never a test one
  • Any DO, Form 13 or empty release order issued on the Line desk checked at your gate by its QR code — whether it holds today, its containers and the holder — with no account needed
  • Your yard or transport system told as it happens — a delivery order released, an empty release order or a Form 13 issued, a container’s free days ending — by signed webhook or from an event feed

Free for anyone, no account needed

Questions CFSs, ICDs and transhippers ask first

Read next

Can a CFS file the stuffing report (SF) on SCMTR.io?

Yes. Choose what happened, the stuffing report is laid out for it, checked as you type, signed with your DSC and sent under your ICEGATE API key — or saved for ICEGATE’s API utility.

Which CFS and transhipper reports does SCMTR.io cover?

The stuffing report, its cancellation, stripping, and the vehicle’s departure and arrival times; the gateway CFS’s import transhipment (ITP) of LCL cargo on to an ICD; and the transhipper’s allowed for shipment request, departure and arrival. The ITP and the transhipper’s reports are in beta.

Does CFS filing on SCMTR.io cost anything?

No. Filing is free: every filing feature, no caps on filings, no card.

Can our gate check a delivery order issued on SCMTR.io?

Yes. Every DO issued on the Line desk carries a QR code. Your gate scans it and sees, without an account, whether the DO holds today — its number, validity, bill, containers and where each goes, the line and the holder — never an amount or an invoice. A DO withdrawn, replaced or past its date says so. A Form 13 and an empty release order are checked the same way. A CFS or yard on SCMTR.io also sees every DO naming it and marks each container delivered.

Everyone else on the vessel call works here too

SCMTR.io is an independent filing platform for India’s Sea Cargo Manifest and Transhipment Regulations (SCMTR). Forwarders, NVOCCs and consol agents, shipping lines and steamer agents, CFSs, ICDs, transhippers and customs brokers prepare their SCMTR filings on it, check them before ICEGATE sees them, sign them with their own DSC, send them to ICEGATE and follow customs’ answer.

Everything SCMTR.io does

Your next filing, start to finish on SCMTR.io

Filing is free — every filing feature, no caps, no card.