Help
Using the platform
Getting around SCMTR.io, from signing in to a filed declaration — and what to do when something does not behave the way you expected.
Check your CSN against the line’s SAM first
Why a mismatch is free to fix before the line files its SAM and an IGM amendment after it, what SCMTR.io checks at Sign & upload (the MBL PDF too), when your CSN is due and how you are reminded, which SCA changes make the line file an SAA, and how a line shares its SAM, names its forwarders and sets its cut-off.
The pending console split-ups board
The consolidators’ register of master bills whose house bills the shipping line has not yet split onto the manifest, as a public board: what each row’s “Our findings” means — still pending, partly linked, linked on customs’ record, no CSN yet, not on record, what customs’ record cannot show, how a member adds and changes their own bills, and the Excel and PDF downloads anyone can take.
CSN cut-offs from the shipping lines
What a shipping line’s CSN cut-off is and why it matters, where to find it for your vessel on the cut-off board — with the customs VCN, port VCN, rotation and VIA numbers to copy, customs’ own record of the call and what moved — which VCN goes in the CSN, how current a cut-off is, calls read from JNPA’s reports and Maersk’s lists with estimated cut-offs, and how a line publishes its own by e-mail or from its desk.
The vessel call number (VCN)
The conveyance reference on a CSN, end to end: the three places a VCN comes to you from and why you never apply for one, when the port issues it and how far ahead of arrival calls have been seen to appear, why a placeholder is not an option, which of a delay, a roll and a blanked sailing takes it away, what is checked on your behalf and what customs is actually asked, what that answer does and does not prove, and what to do for a draft and for a filing customs has already accepted.
Finding the ship you are filing for
A bill of lading names a ship; customs identifies it by number. How to find the right hull from a name, how to look a ship up with VCN search without a filing, how to tell two ships with one name apart, why a rename changes nothing on the filing, which of a feeder and a mother vessel you declare, what to put on a bill that says TBN, and what to do when the search finds nothing — or finds the ship and no IMO number at all.
Signing your filing with your DSC
Customs accepts nothing unsigned. How Sign & upload signs a filing with your DSC token through the SCMTR.io DSC Signer, how to install and update the Signer, what the authorised representative PAN is, what to do when a DSC is renewed, what the file check verifies about a signed file’s DSC, what “DSC validation failed” means, and every way signing fails with what to do about it.
Working with a shipping line filing (SAM / SDM)
Open a shipping line’s SACHM23 manifest — hundreds of bills, over a megabyte — as a searchable table, correct a line with the full editor, see what the file contradicts about itself, save it and come back — a re-dropped file reopens the saved copy, and a newer one asks before replacing it — and write it back exactly as it came — or, since 12 September 2026, sign it and file it from here, through the same gate that keeps a file from going to customs twice.
Filing a SAM or SDM with no software of your own
Build a SAM / SDM from nothing, for a bulk, tanker, break-bulk or tramp call that no liner system files for: what you need before you start (the IMO number, the VCN the terminal applies for, your ASC or ASA registration, the unpublished terminal operator code customs checks, the crew list’s e-Sanchit IRN), the order the four filings go in, when a non-containerised arrival manifest is actually due against a containerised one, the ten questions asked per bill of lading and the conventions written for you from real bulk filings — and why the app creates the manifest but customs, not the app, decides whether it is accepted.
What the app’s checks mean
Red stops the filing, amber does not. What each tier means, where it shows, what to do about the common warnings — and the two fixes the form will not accept in the obvious form.
SCMTR JSON upload
Drop a CSN, an ACK, a structural-failure response or a SAM / SDM on the CSN filing page and have it checked against the real schema, the rules for its reporting event and customs’ error list — including why pairing an ACK with its declaration is the step worth taking, and how the screen names the CSN you need and rejects one that is not it; and the free check at scmtr.io/check — what it shows without an account, the BL-tracking link under each master bill, what a signed file does and does not hold, and that signing in creates the account.
Checking a manifest against ICEGATE
Ask customs which of a manifest’s bills already carry an accepted CSN and how they compare, each difference marked Fix, Check or OK to differ — what each verdict means, why “no CSN” is not a fault, why the check paces itself, and the IEC-typed consignee codes it asks customs’ IE-code register about (a note, never a verdict) — and how to tell customs took an entry inward (SEI).
My VCNs: every filing on one vessel call
One page per VCN — one ship’s call at one port, with the rotation number beside it — where your CSNs, every SAM upload and its ACK, and the files you or customs have shown for it come together, appearing on its own the moment a filing or a kept file first names the VCN.
Why is my container held?
The VCN page’s Bills and containers board — every bill and container of yours on the ship, worst status first, with the one next step for each: CSN not on record, a difference from the manifest, an amended CSN, or ready.
Customs rejected my SAM — which bills, and why?
A SAM rejection names most lines by number only. Explain this rejection names the bill on every rejected line, compares it with the CSN it quotes, and says in one sentence whether it is a data error at all.
Amending a shipping line filing (SAA or SDA)
What a minimal amendment carries — only the lines that changed, never the whole manifest again — what amdType means, how SCMTR.io builds one from the manifest you already hold, and the sequence when a forwarder asks you to amend for their consolidation: the deletion step ICES Advisory 38/2026 publishes — “delete SAM” is the bill’s own line item, dropped and re-added, never the manifest — why a straight↔consolidated change, a consolidator PAN or a CSN reference is never an in-place update, when the jurisdictional officer has to approve it, and how an SAA or SDA is checked against the newest accepted reply kept for the call before it is sent; and seeing the manifest customs holds for your call, with no ICEGATE login to give, to check an amendment against it.
The Line desk: eDO, invoices, ePayment, Form 13
A shipping line and its customers on one master bill. The line opens its bills from its SAM and invites its customers with the arrival notice; customers give their house bills (eHBL) or CSN with each container’s destination; the line posts its own invoices, its GST e-invoice read from its QR; customers pay into the line’s own account (ePayment: by bank transfer, and online by UPI, card or net banking once the line connects its payment provider), one bill or several at once, with an approver where an organisation asks; security deposits, and detention and free days from the line’s own tariff; KYC shared once with each line, and the consignee’s authority for its customs broker; the electronic delivery order (eDO) with a QR code any CFS can check, and the CFS’s and empty yard’s marks at the gate; on exports the empty release order, each container’s VGM and its Form 13, the shipping instructions and draft BL, the BL release and the forwarding note; a forwarder’s own house DOs; TDS under the line’s own rule and its papers for payers, advances before an invoice, questions on invoices and questions to the line with a reference, receipts and payment confirmations; the line’s public tariff, its embed on the line’s website and a detention calculator; the DO’s copies to the CFS, a direct-delivery terminal and the port’s custom house; a vessel call corrected; the line’s customer list, letters and invitations; reports, Needs you and settings in five pages, the phone app, and the line’s and its customers’ own systems through the API. How a line switches it on, what it costs, and what happens if a customer leaves or the desk is paused.
Give a VGM Online to Any Shipping Line, India
A shipper, or its forwarder or customs broker, gives each container’s VGM on SCMTR.io for a booking with any shipping line, with every field the official VGM form asks, the weighbridge slip and an optional DSC. A line on the Line desk reads it on its desk; any other line is e-mailed a link that shows whether the VGM still stands. The weighbridge register and how a weighbridge applies, DG Shipping’s method 2 shippers, what is shown in amber, who else can read a VGM, and how long it is kept.
A prepared SAA, opened only with your DSC
SCMTR.io can prepare a shipping line’s SAA — a straight bill re-filed as a consolidation, a line removed whole, numbering against what customs holds — and hand it over sealed: a link that opens only with the authorised person’s DSC, shows what the SAA does but never the file, and signs and sends it from SCMTR.io after reading customs’ record once more. A CSN or a CSN amendment (SCA) can be prepared the same way; a CFS file cannot.
Support cases: one conversation with everyone
A support case is a conversation SCMTR.io support opens with the people a problem involves — the filer, the shipping line, a forwarder — read only by the people invited into it. Who can invite, what you can attach, what the e-mails say (never the message), signing a filing SCMTR.io put on the case for you, and how long a case is kept.
Replacing a CSN that has left customs’ record
When a CSN cannot simply be amended — deleted, off customs’ record, or the manifest holds the bill under a different date — Start a replacement begins a new CSN from the old one, changing only the field at fault.
Signing in
There are no passwords. Sign in with Google, with a Microsoft work account, or with an emailed link — request it on your laptop, approve it on your phone, and the laptop is what ends up signed in. What the confirmation code is for, and what to do when a link expires or never arrives.
The SCMTR.io App for iPhone and Android
The companion app for iPhone and Android: what customs said about each filing, the e-mailed ACK file recorded from the phone or straight from Mail, your Line desk bills — their papers, free days and Pay on the line’s own page — and your approvals, KYC and reports, with a draft BL, a payment or a release approved or your KYC shared, each asked first; the CSN cut-off board with reminders, BL tracking, VCN search and the assistant — what it keeps on the phone (nothing of your organisation’s), how to sign in, how to delete your account, and where to get it: the App Store for iPhone and Google Play for Android.
Use SCMTR.io with Your ERP or Job Software
SCMTR.io works beside the job software you already run: a job from any job system or ERP becomes a draft CSN — as a spreadsheet read under an import profile, or through the API — a person checks, signs and sends it, and the CSN number, CINs and customs’ reply go back by write-back sheet, events or the API. Whether SCMTR.io is an ERP (no), what happens when a job is sent twice, exports, where it is set up and what it costs.
Post Line Desk Money to Tally or Zoho Books
Line desk invoices and payments, with the TDS withheld, taken to the books you already keep — posted to your own Zoho Books organisation, or downloaded as two files made for Tally’s import or as a plain sheet for any other accounts package — for a shipping line as sales and receipts and for its customer as purchases and payments: how each is set up, what SCMTR.io reads and changes in your books, how far GST is carried, drafts or sent, whether a record is posted twice, disconnecting, and who can use it while lines are being switched on.
Events for Yard and Transport Systems
What a CFS’s, ICD’s, empty yard’s or transporter’s own system hears from SCMTR.io as it happens — customs’ reply to a CSN recorded, a bill reaching the line’s manifest, entry inward granted on a watched bill, a delivery order released, an empty release order or a Form 13 issued — each naming the filing, bill or paper that changed: pushed as signed webhooks or read from an event feed kept 30 days. SCMTR.io is not a yard or transport system; it feeds yours.
Your team, and filing for other companies
Admins, members and managers; who reports to whom; letting only signers send to ICEGATE; a person’s own ICEGATE user ID; allowing only company e-mail addresses. And for filing agents: asking a company to let you file for it or setting up one new to SCMTR.io, account leads and handlers, working inside a client, and how a company changes its agent whenever it likes while keeping every filing.
A shipping line’s organisation on SCMTR.io
For a line’s Indian agency: one organisation for one line, verified by SCMTR.io staff; publishing CSN cut-offs from inside the app; people joining by invitation or by asking from a company address or a file of the line’s (an admin decides every time); port branches whose people still read every port; View-only members; inviting a sub-agent company by its PAN; and who may file the line’s SAA — customs ties it to the company and its type (error 230) — the person and the DSC have not been seen compared; send from an ICEGATE user ID registered under the SAM’s type.
Working together on a SAM or SAA
One person on each line of a manifest, with everyone’s changes seen within seconds; Done, Checked, Send back and Waiting for papers on every line; signing that freezes the manifest; Excel load lists and BL PDFs read into lines and applied by a tick; an SAA counting only the lines it changes; saves never overwrite somebody else’s work; forwarders ask a verified line for an SAA change from their CSN page; the line’s people who may send approve; approved changes go at once or together at the times the line chooses, as one consolidated SAA signed with the line’s DSC; one SAA at a time per manifest; and a line with errors left out so it does not hold up the rest.
Using SCMTR.io
Signing in through to a filed declaration: organizations and roles, every route into a filing, what a row on the CSN filing list shows and what its badges mean, statuses, and admin abilities.
Checking files by e-mail
Send a CSN or an ICEGATE acknowledgement to the checking address and get the full check back — a CSN and its reply read together so every error names your own value, which of your filings a reply answers, a button that opens the right screen without ever recording anything, ICEGATE’s refusal e-mails, and your own checking address for forwarding ICEGATE’s replies automatically.
Bills by e-mail
E-mail a master bill of lading and its house bills and get the Sea Cargo Manifest Checklist back — what to attach, the three replies and the four steps they show, the few things you are asked (the CFS, DPD or depot; a consignee’s PAN; a missing master) and why only those, the page that asks them with no sign-in, what approving does, and what is kept.
CFS Stuffing Report and CFS Filing on ICEGATE
For a CFS, ICD, terminal or transhipper: making the stuffing report, its cancellation, the stripping report and the vehicle’s departure and arrival times (CUCHE01), the ASR (TRCHE02), the DP and AR (TRCHE01), and the gateway CFS’s import transhipment (ITP, CFCHI51, in beta) — what is checked as you type, why CN and not C, signing with your DSC, sending under your own ICEGATE API key, reading customs’ reply, the report that comes next, and Chennai customs’ list of shipping bills still waiting for a stuffing report.
E-mail from SCMTR.io
Every message the platform can send you and why you got it — sign-in links, invitations and their daily limits, CSN alerts, check reports, the notices about a filing something outside SCMTR.io has changed, the privacy-change notice, and the three you can switch off — plus what to do when one has not arrived.
Sending a CSN to the line, CFS and your customer
Emailing a CSN to the line, the CFS or your customer — a filed one with its declaration and acknowledgement attached, a draft before it goes, or a file you only checked here; what goes in the message, who is copied, pasting addresses out of Outlook, the shareable link and how to withdraw it.
After you file
The gap between "sent" and "settled": the three ways a customs outcome can reach you, what "Filed — not auto-tracked" means, why a filing with no tracking id is answered only by email to your registered ICEGATE address, how long to wait, how to record the outcome once you have it — by dropping the emailed acknowledgement onto the filing, or by hand — and what the filing page says, and what is emailed to you, when customs no longer lists the call it names. Also why the same file will not go to ICEGATE twice and how to send it anyway with a reason, what "Delivery unconfirmed" means, and what a held filing means.
Troubleshooting
Symptoms in the words someone would use to describe them, and what to do about each.
Asking for a feature
Where a suggestion goes, what happens to it, what the roadmap statuses mean, and why a signed-in vote counts for more than an anonymous one.
Looking for the regulation rather than the product?
The SCMTR reference covers fields, codes, identifiers, and rejection reasons. The filing guide is the plain-language walkthrough.