What shipped in October 2026
Everything that went live in October 2026, newest first, with the date it went live. The newest changes are on the changelog, and what we are building next is on the roadmap.
October 2026
- Platform
The SCMTR.io app is on Google Play for Android
Search Google Play for “SCMTR.io”, or open the link on the app’s help page. It is the same app as on the iPhone: what customs said about each filing, the e-mailed ACK file recorded from your phone, the CSN cut-off board with reminders, BL tracking, VCN search and the assistant, and it says in the app itself that it is not a government app and links the official CBIC and ICEGATE sources. Sign in with the account you use on the website. It can take a day after release for Google Play’s search to find it; the link works at once.
- Checks
An SCA that changes one bill now declares the totals customs counts
An SCA that changed one bill of a 24-line CSN and declared only that bill’s line and containers was refused with 89 and 90; the same change with the CSN’s totals was accepted. An amendment declaring only its own bills is now stopped with Set the totals to … lines and … containers, and opening an amendment from such a file sets them for you.
- Filing
An amendment with only some of the CSN’s bills now shows the right “was” values
When an amendment carries only some of a CSN’s bills — line 9 of a 24-line CSN, say — each bill is now set against the same bill in the accepted filing, by its line number. Before, it was set against whichever bill sat in the same place, so every field looked changed and the “was” note under a field named another bill’s value. Bills the amendment does not carry are still listed as not carried.
- Checks
Panvel (INPNV6): a named transhipper is no longer pointed out
Cargo to Panvel (INPNV6) is filed both with a transhipper named and with the block left blank, and customs has accepted both. The note telling you to leave the transhipper blank for an SEZ no longer appears for Panvel. Other SEZ destinations are unchanged.
- Vessels
Every call of your line, at every port, in one list
In a verified line organisation, My VCNs has a tab with every vessel call of the line — from customs’ record and the CSN cut-off board, at every port, including calls nobody has worked on yet. Each row shows the arrival, the CSN cut-off, where your SAM and SAAs stand, any open refusal, and who has worked on the call. Search by vessel, VCN, rotation or IMO number, or filter by port or office. The team chart now shows who reports to whom and each person’s office, and an invitation nobody answered shows as Expired, with Invite again.
- Checks
More vessel manifest mistakes stopped before you send, most with one press
A SAM whose every line is an update or a removal is an SAA — Make it an SAA turns it into one. An amendment marked as a fresh filing gets Make it an amendment (A). A line box with no load status, a rotation number that is not seven digits, and repeated line numbers (Number the lines 1 to N, on a new SAM) are stopped. When the bills you change are on customs’ record of another rotation for the vessel call, the check says which, and Use rotation now sets its date too. A bill typed with a letter O for a zero is corrected in one press when customs holds the right one. An itinerary leg added as new under a leg customs holds can be sent as U in one press. Build amendment takes its line total and next line number from the newest count of customs’ record, Set the totals fixes both totals at once where both are wrong, and an SAA is warned when customs refused the last one for a line it does not change. A name over its length only because of double spaces has Remove the double spaces.
- Checks
CSN checks: one-press fixes and plainer notes
On an export, a straight line whose shipping bill a house bill of another CSN on the same master bill already quotes is stopped, with Make it consolidated (C/N). A one-digit state code is written as two in one press. A master bill referenced only while customs holds it as a straight bill on another CSN, and a master bill that is a house bill on another CSN, are pointed out before you send. An empty box with a weight of 0 is pointed out, so you can leave the weight blank or check its load status. Repeated notes on many bills are shown once, with the bills they are on.
- After filing
Told when your house BL is left at the port while the line moves the bill on
Once the shipping line’s SAM is on customs’ record, if its line moves your master BL on — to an inland port or into an SEZ — while one of your house BLs is filed for local delivery at the port, the bills board shows the bill as SAM differs — check, naming the house BL and both routes, and you get one alert before the vessel arrives. The IGM has been seen to follow your house BL’s movement and destination, so the boxes may be held at the port: if the line is right, amend your CSN and then ask the line to send its line again by SAA. Before you send, Sign & upload points out the same thing, and never stops the upload for it.
- Filing
Send a line again unchanged in an SAA
When a forwarder’s CSN amendment on a bill your line carries has been accepted, the IGM can keep showing the old values until your SAA sends the line again. Build amendment now has a box for it: open the accepted SAM, change nothing, type the line’s number, and the SAA carries that line as it stands, with its containers. A number your SAM does not hold is said and not sent.
- Filing
A stuffing cancellation says when there may be nothing to cancel
When you cancel a stuffing report, its shipping bills are looked up on customs’ record, and a bill still waiting for its stuffing report is pointed out: there may be nothing to cancel, so send the stuffing report itself. A new report takes your yard’s ICEGATE ID from its last report when Settings names none, and a yard’s first report here can start from customs’ own reply you kept. A report your yard’s software sent to another customs station keeps going there, with one press to send it to the port instead, and a sender ID that is another yard’s code is pointed out.
- Checks
Manifest slips pointed out, with the fix beside them
A vessel’s container list written inside a line or a house bill is now one error, with one press that moves it where it belongs. Slips in a container number, a bill number, the VCN, the terminal, the IMO number or an Indian port code are pointed out, with the correction where there is one. An SAA that updates a line customs does not hold offers to add it as a new line instead.
- Checks
Repeated items and a wrong CSN number caught before you sign
Two items of one bill with the same HS code and the same description now stop an import CSN, and an amendment that adds one of them or changes one into a repeat. One press merges them when both are in the same kind of package and carry the same hazardous-goods code; items with different hazardous-goods codes are kept as two, with descriptions that say what each is. An amendment whose CSN number is the vessel’s rotation is stopped before you sign, with one press to use the CSN customs holds. A bill your own SAM already declares is pointed out.
- Filing
Build amendment drops and re-adds a line for you
Change whether a line is straight or consolidated, its consolidator PAN or the CSN it quotes, and Build amendment drops the line and adds it back for you, telling you the line number the bill comes back as. A line that still needs the CSN it quotes is listed, with a button to choose it.
- Platform
A reminder before an invitation expires
Someone you invite who has not answered yet gets one reminder e-mail two days before the invitation expires, with the date and the link to their invitations.
- Filing
CFS filing works the way your yard does
A new stuffing report starts with the seal type and unit your yard used last. Fill from customs’ record writes the whole bill into a container only when customs’ record names that container; where it names none yet, as is usual at a CFS until the EGM, it says the bill’s count and you type this container’s share. A second shipping bill in a box makes it LCL, with one press to keep it FCL. A unit written as the kind of package is pointed out, and a report naming an ICEGATE ID your yard’s own kept replies never went to says so. A cancellation first asks which stuffing it cancels — one of your stuffing reports, its file, or the container and PCIN typed — and builds itself from that. Customs’ reply you kept is shown on the report it answered, never on a changed version of it.
- Platform
The SCMTR.io app is on the App Store for iPhone
Search the App Store for “SCMTR.io”, or open the link on the app’s help page. It shows what customs said about each filing, records the e-mailed ACK file from your phone, keeps the CSN cut-off board with reminders, and has BL tracking, VCN search and the assistant — now in your own language too. Sign in with the account you use on the website. Android is on Google Play too, since 31 October.
- Checks
An SAA that drops a bill after entry inward, and adds nothing back, gets a note
When your SAA removes a bill’s line and customs’ record shows the vessel was granted entry inward, the Checks now point out if nothing in the same SAA adds the bill or its containers back: once the officer approves it, cargo that was landed would have no line to file a Bill of Entry against. To add house bills or change how the bill is declared, add it back in the same SAA. Nothing is said for split cargo, a bill still on another line, or a bill number corrected in the same file.
- Platform
Three more answers from the assistant, and your questions train no AI
The assistant now answers how to make a CSN with no software of your own, whether an IGM filed under SCMTR can be amended in ICES 1.5, and whether AI answers your questions and where they go. Your questions to it are not used to train AI models, and the privacy policy now says so.
- Checks
A box changed under a number customs does not hold it under is an error
When your SAA updates or removes a box on the vessel’s list under a number customs holds no box under, the Checks now show it as an error — customs refuses it with 749 — with one press to use the number customs holds the box under. If your SAM puts several boxes under one number, a box changed under that number shows a note.
- Checks
A line added back with its boxes keeps them on the vessel’s list
When your SAA drops a line and adds the bill back with the same boxes, but leaves those boxes off the vessel’s list, the error now points at the line that adds them and says to list each box again as an update, under the number customs holds it — not to add it as a new box.
- Checks
Sending an SAA agrees with its Checks on a box re-added under its old number
A box your SAA adds back under the number an earlier accepted amendment removed it from is no longer stopped at Sign & upload when the Checks panel let it pass. And Set the line total and Set the container total now appear only once customs’ record confirms the reply or count is the version it holds now — otherwise the right total is named, for you to check, without the button.
- Checks
An SAA on a SAM that numbers every box 0 is checked against all its boxes
A SAM can put every box on the vessel’s list under number 0. An SAA against such a SAM now counts each of those boxes: removing one under 0 is no longer read as a box customs holds somewhere else, and the container total it asks for counts every box, not one. A box added under 0 is a warning, not a stop.
- Filing
A house bill Build amendment adds is marked added throughout
When your SAA adds a line with its house bill, Build amendment now marks every part of the house bill as added — its transport document, measures, location and transhipper too — as ICEGATE’s own rules for each field ask, so the file it builds no longer warns about itself. Changed back later on 27/10/2026: those four parts are again left unmarked, as in the SAAs whose added lines and house bills customs’ record holds; the house bill itself and its containers, route and items are still marked added, and the Checks no longer ask for the rest.
- Vessels
More CSNs show their line’s cut-off
A CSN whose master bill is in Interasia’s own form, with its containers filed by an agency known to act for Interasia, now shows Interasia’s cut-off. An agency alone still never decides which line a CSN is due to.
- After filing
Refile on a filing that has moved on says where it stands
Refile on a filing that has since been sent again or accepted now says so in words, instead of an error page. If the filing is back to a draft, Refile opens your draft.
- Filing
CFS filing uses the whole page, and keeps customs’ answer in sight
CFS filing and the file check’s reading of a CFS report now use the page’s full width, and a report opening says so instead of showing a blank page. Customs’ answer to the last file you sent stays on the report’s fields, first in the list, until you send again. And a report reads as ready only once customs’ record has answered for every shipping bill it names — while it is being asked, or where it could not be, the report says so.
- Checks
An SAA with no rotation filled in one press, and a removed line taken whole
An SAA that leaves out the vessel call’s rotation is stopped, with Use rotation … of … to fill it from customs’ record of the VCN. Remove the line whole takes the line as customs holds it after the amendments it accepted, and says what it did; a line declared R offers Quote the CSN. BL tracking shows a bill’s SAM line and IGM line together.
- Filing
A CFS’s report reads the same in CFS filing and in the file check
Drop a CFS’s or ICD’s report on the file check and it is laid out as CFS filing lays it out, each problem on the field it is about, with a press that takes you there; the file itself — its signature, its name — has a card of its own. CFS filing opens with a tile for each state your reports are in. A file ICEGATE hands your yard now reaches you as an alert, and so does customs’ answer to a report sent from another program.
- Checks
An SCA line that quotes its own CSN by MCIN or PCIN is caught
A line of your SCA that quotes, as an earlier declaration, the MCIN or PCIN of the very CSN you are amending is now treated like one that quotes that CSN by its number: marked to fix, with the same one-press fix, where the CIN is certainly your CSN’s, and a warning where it may be another CSN’s. When customs answers an SCA, errors on lines your amendment did not send are explained as being about your CSN as customs holds it.
- Checks
Fewer false warnings on exports, and a UN number swapped with its class named
An export’s house rows are shipping bills, so the warning about a house bill dated weeks after its master no longer appears on an export. A UN number and an IMDG class written into each other’s fields are named as swapped. And a file that will not open says where it breaks in two more cases: a block closed twice, and a stray bracket between rows.
- Filing
Bills of lading to Kolkata and other ports read right
A bill whose port of discharge or place of delivery is Kolkata, Cochin, Kandla, Visakhapatnam, Tuticorin, Ennore, Kakinada, Krishnapatnam, Mormugao, Paradip, Hazira, Dhamra or Haldia is now read as that Indian port, not one abroad. Ports are read from their own box on the bill, a port written beside its caption is taken from there, and a name with another port in brackets — Kolkata (Haldia) — is left for you to choose.
- Checks
An empty container is not asked for its package count
An empty container (EMP) carries no packages, so a manifest no longer asks for its package count and a CSN shows a note rather than a stop — enter 0. A loaded container’s count is still required.
- Filing
A CFS’s reports go to ICEGATE from SCMTR.io, under your own API key
An admin saves your organisation’s ICEGATE API key in Settings, under ICEGATE API key for CFS filing — it is tried with ICEGATE first and the ICEGATE ID it files as is shown — and each report then has Sign and send to ICEGATE: you choose your certificate, check what will go, and only then is it signed and sent. The report reads With customs until customs answers; the answer comes back onto the report by itself, each refusal on its field, and reaches you as an alert. A file your own software signed can be sent too, if its signature holds, and the same report is not sent twice unless you say why. Without a key, upload the signed file through ICEGATE’s API utility as before. Sending from SCMTR.io is new: tell us how your first sends go.
- Checks
CFS filing reads more of customs’ replies, and catches a custodian code customs refuses
A refused reply’s B01 now reads as refused, with the reason beside it, and LCB04 on a stuffing report is explained as your custodian code: ten characters — your port or ICD, then the four customs registered your yard under. A code of any other length is marked red, with your yard’s published code one press away where SCMTR.io can tell which yard is yours, and the published codes for ICDs and inland CFSs are offered in CFS filing. Fill from customs’ record fills a shipping bill’s PCIN and, on a stuffing report for a bill not yet past stuffing, its packages and — for a box stuffed at the factory — its container and seal, into empty fields only. ICEGATE’s whole answer, saved as it came, opens like the reply inside it.
- Checks
A CSN destination that is not a code is marked, with the code it most likely means
A destination written as the port’s name, or a code with a letter too many, can go through at filing and still leave the CFS unable to receive the box. Such a destination is now marked red on the CSN, with the CFS’s, terminal’s or port’s code it most likely means offered under the field.
- Platform
The API and webhooks have their own page, and lists on help pages read as lists
The reference page for connecting your own system to SCMTR.io is published: what your system can do through the API — check a file, send in files and customs’ replies, read your VCNs and kept files — how to have it switched on, what stays in the app, and the details your developers need, with every webhook event. The link in Settings → API now opens it. And bulleted lists on the help and reference pages show as lists again, item by item, instead of one run-on paragraph.
- Filing
A large SAM / SDM opens faster and keeps up with your typing
On a manifest of thousands of lines worked on together, opening it, searching its lines and saving an edit no longer hold the screen: a search answers as you type, a saved edit pauses the page for a fraction of what it did, and a colleague’s change arriving on your screen no longer freezes it for half a second. A saved manifest now downloads about a fifth of its size. A very large CSN — thousands of house bills under one master — is checked several times faster, and your first lookup of the day on ICEGATE goes out at once instead of waiting its turn behind nothing.
- Platform
Pages that open faster, and no long wait on a first visit
Now and then a page took ten to twenty seconds to open on a first visit; that should no longer happen. The file check and the SAM / SDM screen load about a third less before you drop a file, and the list of CSNs, a filing’s own page and Settings load less too. BL tracking and VCN search no longer jump as the search box appears. Link previews of a shared bill, ship or pending split-ups draw faster, and the alerts bell, your bill PDFs and the guided steps’ saving are lighter on your browser, without changing what you see.
- Platform
The assistant explains one error at a time
Ask the assistant about the code on your own acknowledgement and it explains what it means and what to change, as before. Asked for every code at once, it now asks which one you got and points you to SCMTR JSON upload, which reads your own acknowledgement error by error. The reference and help pages were rewritten to say what you see and do, shorter and plainer. Questions about whether your files are kept or where your data goes are answered, with the privacy policy beside them.
- Checks
A CFS report signed by the yard’s own software reads as signed
Some yards’ own software signs their stuffing and destuffing reports differently from ICEGATE’s signing utility. Where such a signature is good for the file, the check now says so — as a warning — instead of calling it “does not match this file”. A report changed after it was signed is still an error, and so is a CSN or vessel manifest signed that way. Other warnings on a CFS file now show in amber beside an error, not as more errors.
- Checks
Fewer false stops on SAMs, an SCA that quotes itself, and the SAM line on BL tracking
A consolidated line that declares its own house bills, each with whole containers FCL under a master LCL, is no longer stopped for two load statuses; the stop stays on a line that quotes a CSN. An SCA whose lines quote the very CSN it amends as an earlier declaration is now an error, with “Keep the line as the CSN declared it” one press away. An SAA that writes the amendment type under the wrong name is caught, with the fix one press away; a manifest line declared R is noted, since a line is S or C; and a line an SAA adds quoting no CSN, where customs already holds a CSN on the bill, is noted with Quote the CSN. BL tracking now shows a bill’s SAM line beside its IGM line — an SAA addresses the SAM line. A file with a value closed by two quote marks is explained as that.
- Vessels
The manifest as it stands, on the VCN page
After a SAM and its SAAs (or an SDM and its SDAs), the call page now shows the manifest as it stands: every upload with what customs said, the lines and containers held now beside what was first filed, the totals the changes give, and each line’s history — a bill dropped and re-added under another number shown as one move. Search by bill, CIN, container or line, and download it as a spreadsheet. It is built from the files you sent, and Count what customs holds lays customs’ own record beside it.
- Vessels
One vessel call, one page
A call your CSNs named by its VCN and a manifest reply named by its rotation number could show as two calls. They are now joined by themselves once anything you hold names both, and the old address of a joined call takes you to the one it became.
- Checks
An SAA that re-points a line’s CSN reference in place is stopped
An SAA that changes which CSN a line quotes in place — rather than dropping the line and adding it back, as ICES Advisory 38/2026 requires — is now stopped: an error where the line quotes an MCIN or PCIN, a warning where it quotes a CSN by number and date, and on an SDA.
- Checks
An SAA that removes a line under another bill’s number is stopped, with the right line offered
When an SAA removes or changes a line and customs’ current record holds a different bill on that line number — often because the number came from an enquiry page that shows the IGM line, not the manifest’s — the Checks panel now says so as an error and offers the line customs holds the bill on, or says there is nothing left to remove. It is a warning where the check cannot be sure, and for an update naming a bill customs holds on no line, which may be correcting the bill number. An added line that clashes with a CSN filed under your own PAN now says to remove the bill from your own CSN first.
- Checks
Boxes re-added under their own former numbers beside new ones: a warning, not a renumbering
When one SAA adds boxes back under their own former numbers as well as new boxes past the end of the vessel’s list, the app no longer offers to renumber every added box from the end, which could take numbers other boxes hold. It warns instead: keep each box’s former number, or use one no box on the vessel’s list holds. Build from customs’ record keeps the file’s own numbers for its additions. Added boxes numbered on from an older copy of the list are still an error, with the renumbering one press away.
- Filing
Add a consolidated line with its house bills from a forwarder’s CSN file
Adding a line from a CSN can now declare the bill in the line itself — consolidated, with every house bill of the forwarder’s CSN carried field by field, your own PAN as consolidator — for a bill whose CSN customs never received. Drop the CSN file (no acknowledgement needed); what the file leaves out is asked in the same form.
- Filing
Remove one bill from a CSN amendment in one press
On a CSN amendment (SCA), each master bill now offers “Remove this bill from the CSN”: one press, asked once more, marks the bill and every house bill, item, container and route leg under it as deleted; “Keep this bill” puts each record back as it was. A bill or record the amendment itself adds is deleted as a row instead, and the CSN’s only bill points to File a deletion.
- Filing
Bills by e-mail: goods and item described alike, for teams that file them so
If your organisation’s accepted CSNs usually carry the same text as the goods description and the item description, the drafted CSN now does the same — the goods named as the item names them, rather than the bill’s full line with its package counts and “said to contain”. The bill’s own wording is shown beside the field. Other organisations keep the bill’s goods line as printed.
- Checks
The line map shows itself while customs’ record is counted
Counting what customs holds on a manifest fills the line map square by square, and the map is now shown by default as it fills; “Hide the line map” folds it for a shared screen, remembered on that browser.
- Platform
Joining your shipping line’s organisation: bring the work you did before across
If you filed for your line from your own organisation before the line’s was verified, joining the line now offers, on your Invitations page and on Settings → Line, to move that work into it in one press — the saved manifest copies and kept files that name your line’s PAN as submitter, each declaration with its signed form and customs’ reply. Anything naming another submitter, and anything that is not a filing, stays where it was. The card shows what would move before you press.
- Checks
Re-adding a bill after its line was deleted: its own line and box numbers again, and totals from customs’ count
When an SAA adds back a bill whose line an earlier SAA removed, the line and its containers may take their own former numbers again, and the app no longer stops it; where a box may still be on the vessel’s list, it is a note to check rather than an error. Count what customs holds now also works for an SAA whose own bills are no longer on the manifest, so its line and container totals are checked too. A removal that leaves out a line’s route legs is now an error, with the line sent whole from your SAM in one press, and an SAA with no rotation is an error, with the rotation customs lists for the VCN one press away. Broken files are explained more plainly: text before the opening brace, a file cut short, a value with a space at its start or end.
- Filing
No “cut-off has passed” reminder for a CSN you have only just started
A draft CSN begun after its vessel’s cut-off had already passed is now given a few hours before the reminder that the cut-off has passed is sent, so you are not mailed about the CSN you are filing that minute. Arrival dates on terminal reports that print the month first are read correctly again.
- Platform
Ask the assistant in your own language
The assistant on the website answers in Hindi, Marathi, Gujarati, Tamil, Telugu, Kannada, Malayalam, Bengali and Punjabi, in the language’s own script or typed in English letters the way you chat (“VCN kahan milega?”), and answers the same way you wrote. Codes, field names and button names stay in English. Its answers also lead with what you asked, keep CSN and shipping line questions apart, and cover more refusal codes.
- Checks
Notes for what forwarders most often amended after a CSN was accepted
A CSN now gets a note, never a block, for mistakes commonly corrected later with an SCA: a container moving on under bond to a CFS with only the station as its destination, a leg from abroad into India that is not by sea, a transhipper bond registered at another port, and a house bill dated more than a week after its master. An SCA that names a line by its IGM line number instead of the CSN’s own is pointed out too.
- Filing
Bills by e-mail: a usual destination chosen for you, and a missing bill named
When nearly all of your organisation’s accepted bills at a port went to one destination and the e-mail says nothing about it, the draft now chooses that destination already and says why — you can still change it. A draft also offers the line agent and the onward transhipper and bond usual for a bill’s line and route, after your organisation’s own record. A bill missing from a combined PDF is asked for again and then named on the draft, and an e-mail too large or complex to open gets a reply saying so.
- Platform
Sign in with Apple on Android
The Android app now offers Continue with Apple beside Google, Microsoft and the e-mail link. It opens Apple’s own sign-in page in the phone’s browser and brings you back signed in.
- Filing
Bills by e-mail: container sizes and consignee cities read more often
A draft built from an e-mailed bill now reads a container’s size the way lines print it — “40SD96”, “40’ Highcube Container”, “HC40” — where it used to leave the size blank, and takes a party’s city as the last place before the state and PIN, never a code, a PIN or a contact line. You still check every drafted value before you sign.
- Platform
The assistant shows tables as tables
When the assistant answers with a table — a help desk’s officers, a list of codes — it is now drawn as one, scrolling sideways on a phone, instead of rows of “|” characters.
- Platform
The assistant no longer writes “(Passage 9)” into its answers
Answers sometimes carried stray numbered references — “(Passage 9, Passage 10)” — that pointed nowhere the reader could see. They no longer do; where it helps, an answer names the reference page instead.
- Checks
Customs’ 754 on a vessel already inward
When customs refuses an SAA with 754 and its record shows the vessel already has entry inward, the reply now says what it most likely means: an earlier amendment is waiting for the customs officer’s approval, so ask the officer to decide it and send once when they say to, rather than re-sending.
- Checks
CSN amendments checked against the CSN you kept here, and a container named by its number and its ID
An SCA of a CSN filed somewhere else is now checked against that CSN’s file and acknowledgement, when you have checked both here — its lines, house bills, containers, items and route legs, which customs’ public record does not show. What it finds there is a note. A container updated or removed under a number your CSN holds another container under is red (251); an SCA sent as message type F is red (226); a line numbered otherwise than customs’ record holds its bill is red (318); and an export line quoting its shipping bill’s PCIN under Y is a note rather than an error.
- Checks
A SAM line declaring a bill a forwarder’s CSN already declares is pointed out (122)
When a SAM is opened, each line that declares its bill afresh (previous declaration N) is checked against customs’ public record. A bill with an accepted forwarder’s CSN turns the line red (122), with the way to quote the CSN instead — a note rather than red when the line gives no bill date or the answer is from an earlier opening.
- Checks
A manifest under another ship’s rotation, a box under another box’s number, and a CSN quoting a heading
A manifest whose rotation is not the one customs lists for its VCN is now red, with customs’ rotation one press away (a note when the answer to hand is not current). An SAA removing a box under a number customs holds another box under is red with the number customs uses; a change to such a box is a note. A consolidated line with no house bills is red on a SAM (163) and a note on a line an SAA adds, an item changed on a consolidated line quoting a CIN is red (748), a heading padded with zeros in a CSN’s HS code is a note rather than an error, and a file that begins with an invisible byte-order mark is noted.
- Sharing
A CSN or SCA prepared for you, signed with your DSC
SCMTR.io can now prepare a CSN, or a CSN amendment or deletion (SCA), and hand it over sealed, as it already did for a shipping line’s SAA: a link that opens only with the DSC of the authorised person the filing names, shows what it does but never the file, and signs and sends it from SCMTR.io. An amendment is checked against the line and sub-line numbers customs holds, and is not sent if customs’ copy of the CSN has changed since it was prepared.
- Checks
An amendment’s house bills checked against the sub-lines customs holds
Customs finds a house bill in an SCA by its sub-line number, not its bill number. An SCA that changes a house bill under a sub-line customs holds for another one is now red, with “Use sub-line N” in the form — and Check with customs on a dropped SCA catches this for a CSN filed on the ICEGATE portal too. Deleting a whole line is not affected: everything under it goes, whatever its house bills are numbered.
- Checks
Cargo for a CFS filed with the port as its destination is pointed out
A CSN for local clearance that names a CFS as its transhipper or at the end of its route, but gives the gateway port as the destination, now gets a warning on the destination port: name the CFS’s own code there, so the CFS can move the box afterwards. A CFS code in the transhipper field is no longer flagged. Never a block.
- Filing
BL PDFs read into a SAM’s lines
Drop a BL PDF on a SAM’s lines board: the bills in it are found and shown first, each is read, matched to its line or offered as a new one, and nothing goes into a line until someone ticks it. A line that quotes a CSN is checked against its BL, never filled from it.
- Filing
A SAM or SAA worked on line by line by a team
A saved SAM, SDM or SAA now opens as a board of its lines: each person takes a line, marks it Done, and a colleague who may send marks it Checked — or sends it back with a reason. A line can wait for its papers. Signing starts only when every line (or, for an amendment, every line it changes) is Checked, and freezes the SAM for everyone until customs answers or signing is stopped; what goes to ICEGATE is exactly what was signed. Nobody’s open line is written over by someone else’s save.
- Sharing
Invite someone to a support case again
A support case invitation that was missed can be sent again at once to anyone who has not opened the case yet, and the case shows how many invitations each person has had — five at most.
- Vessels
An IGM line the SAM no longer holds is not read as a second filing
After a line’s SAA drops a bill and adds it back, customs’ older IGM view can still list the bill under its old line. BL tracking now says that old line once, as one customs’ IGM still lists and the SAM no longer holds — no longer as a second filing with a red Fix against old figures.
- Checks
Counts, VCN search and the checks before sending answer again
After a change on ICEGATE’s side on 15 October, counts of a manifest stopped, VCN search said it could not reach customs for a ship with no calls, and checks before sending were skipped. They answer again. A CSN whose header names another message than SACHM22 is now stopped before it is signed.
- Checks
A refused SAA quoting the wrong kind of CIN reads as one problem, and a CSN’s route is checked against its port
When customs refuses a line with 148 — the CIN it quotes is not one customs issued for the bill — the box and route codes that come with it are now read as following from it, with how to quote the CSN instead. A CSN whose leg from abroad arrives at another Indian port than the one it is filed at, or whose first port of entry is another port, gets a note naming customs’ codes 368 and 59, and a 368 on a CSN now says to fix the itinerary. A manifest still carrying a template’s <<…>> placeholders says so first.
- Checks
An HS code customs does not know, and an SCA naming a bill under another line, are stopped before you send
A CSN whose HS code is under six digits, or a subheading no edition of the HS has, is now red with customs’ 031, and a code from an older edition is a note. An amendment that names a bill under a line number your accepted CSN gives another bill is red (318), and one press puts it on the line customs holds it under; the file checker says the same for an amendment made elsewhere. A transhipper bond that is not a number is a note, and an SAA writing its amendment type under another spelling is red with a one-press rename.
- Checks
An SAA re-adding boxes after a removal numbers them where customs’ list really ends
After boxes come off the middle of the vessel’s list, customs’ count falls but the list still runs to its old end. Building an SAA from customs’ record now numbers added boxes after the highest number the list has used, and the checks stop a file that numbers them inside the list. A house bill changed under a line that customs holds with none is named with customs’ code 318, and a count that finds nothing under the file’s submitter says who customs holds the manifest as filed by.
- Vessels
Watch for a ship nobody lists yet
When neither the CSN cut-off board nor customs’ record knows your ship, press Watch for this ship: SCMTR.io keeps watching for it for three weeks and puts its call on the board once customs lists it — search for it again later. Nothing about you is kept. A ship a port’s report lists twice for one arrival now shows as one call.
- Sharing
See where your request to the line stands, from the line’s shared SAM
On a line’s shared SAM, a BL you have already asked the line about shows where your request stands — waiting, approved, in the SAM, sent or declined — in place of the button, so the same change is not asked twice from the app or the line’s link. A change asked on a draft SAM the line has not filed yet reads as going into that SAM, not into a later SAA.
- After filing
More SAA refusal codes explained in plain words
A box on an added line that is missing from the vessel’s container list now carries customs’ own code, 104, with how an added line’s boxes go on the list. A 754 is read as customs not having linked the rotation to its IGM — something to ask the port’s SCMTR cell about, not a VCN to retype. A bill added again while customs still holds its old line is named with customs’ code 756. And a 749 on a vessel-list row names the row and where its number comes from.
- Checks
An SAA re-adding a line under a deleted line’s number is pointed to the next free number
When an SAA adds a line under a number customs no longer uses — usually the number of a line deleted earlier — the Checks panel says so and offers the next free number in one press. Building an SAA from customs’ record also says when your file’s container total is above the count, so boxes no line names, such as empties, are checked before you send.
- Checks
The count of customs’ record says what your SAA should declare, and its line map stays folded
Beside the count of what customs holds, the SAA editor now says how many lines and at least how many containers customs would hold after your amendment. The container-total check names that figure too, even when the file removes a line under a number customs holds another bill under — with the line numbers to put right first. The line map, which shows every filer’s lines, starts folded so it can stay closed on a shared screen.
- Sharing
Change requests appear without reloading, and a forwarder can ask from the line’s shared SAM
The Change requests panel in the manifest editor and the Change requests page now pick up a request asked while they are open — a colleague’s or a forwarder’s — within a minute, and the panel opens for it. A forwarder reading a line’s shared SAM inside SCMTR.io can ask the line to amend it for a BL whose CSN differs, as the line’s link already allowed.
- Platform
The DSC Signer is in the Microsoft Store
The SCMTR.io DSC Signer is now listed in the Microsoft Store, published by TAGQA Pty Ltd. Every “install the signer” button opens Microsoft’s own page, where installing shows no Windows warning and needs no administrator rights. For office PCs that block the Store, the download page keeps the signed installer, says beforehand what Windows will show and what to check, and now explains how to uninstall.
- Checks
A manifest’s errors and warnings in one Checks panel, each taking you to its field
In the SAM / SDM / SAA editor every finding — the file’s own checks, customs’ record, the CSN cross-check and the entry-inward or departure comparison — now sits in one Checks panel beside the editor, errors first, each with how to fix it and, where one exists, a one-press fix with Undo. Show opens the right line, tab and field, even far down a long manifest, and the field itself carries the error or warning mark.
- Filing
Manifest filing gets Essentials / Advanced and Guidance, as the CSN form has
The guided steps and the manifest editor share the full form’s top row: Essentials shows every field ICEGATE requires and every field already filled, Advanced shows the rest; Guidance can be full or compact; “N problems to fix” takes you to the first; and you can move between the guided steps and the editor without losing work.
- Filing
Start a SAM / SDM with the details from a manifest you already filed
Where a new SAM / SDM asks for your ICEGATE sender ID, an organisation admin can drop a manifest the organisation sent before — or pick one already opened here — see what each detail would fill, and take them in one press. Only empty settings are filled, and nothing is taken from a file filed under another business’s PAN.
- Checks
A SAM or SAA you are checking survives a reload
A manifest or its ACK opened for checking — including one checked before signing in and carried across — is named in the page’s address once it is kept, so a reload or a shared link opens it again. A file dropped on the home page by someone signed in opens straight in the checker.
- Platform
Every support case has a number to quote
Each support case has a number — “Case 1043” — shown beside its title with a copy button and in every e-mail about it. Quote it to SCMTR.io support, or type it into “Case number” on the Support page to go straight there; the number opens a case only for the people in it.
- Filing
The form beside a bill uses the whole screen
With a bill open beside the full form, the guided steps or an e-mailed checklist, the form now takes the whole width and the drawers stand beside the bill only while open; a bill you close leaves a “Show the bill” tab. The checklist button turns red while anything stops the filing, amber when only advice is left.
- Checks
An empty answer from ICEGATE is never read as “not on record”
When ICEGATE answers a lookup with an empty page, the SAM / IGM status, BL tracking, a CFS report’s shipping-bill check and the IEC lookup now say they could not check rather than “no details found” or “no bill on record”. Only customs’ own “No details found” is read as not found.
- Platform
An ICEGATE JSON on a support case opens in the file checker
A .json file attached to a support case — an ACK, a CSN, a SAM / SAA, a signed file — opens in Check your SCMTR JSON in a new tab, with its verdict and, for a signed file, its DSC check; a download button stays beside it. Other files download as before, and nothing is kept a second time.
- Platform
Support cases: one conversation with everyone a problem involves
SCMTR.io support can now open a case with the people a problem involves — the filer, the shipping line’s desk, a forwarder — and everyone writes in one thread, attaches files and sees it through in one place. You are invited by e-mail and read the case by signing in with that address; only the people in it can read it, and until someone opens it the others see only the address they were invited at. A filing SCMTR.io prepares for you can be put on the case for you to sign. A closed case is deleted two years on.
- Filing
CFS filing keeps a report exactly as written, and checks each shipping bill against customs’ record
A stuffing report made elsewhere now opens and saves in CFS filing exactly as it was written, and a signed report’s DSC signature is said in words on Check your SCMTR JSON and in CFS filing. Each shipping bill a report names is checked against customs’ shipping-bill record — and the verdict says when customs’ record could not be read, never “not on record”. The help says how to correct a report (cancel and file afresh) and how a container is reported destuffed; an amendment made elsewhere opens as the amendment it is.
- Checks
An impossible manifest total is a stop, and a pending request is read as one
A SAM / SAA voyage total that is negative, fractional or not a number is red (89 / 90) with or without customs’ record, and “set it to customs’ count” is offered only from a record customs confirms current. Error 303 and 322 on a reply are read as an amendment request already with customs — nothing re-sent moves it; after entry inward the officer approves it (ICES Advisory 37/2026) — and 319 says the same. And when ICEGATE answers a check with nothing at all, the check says it could not read the record rather than “no record”.
- Filing
The transhipper and bond the shipping line publishes for your depot, offered first
In a CSN’s transhipper box, the operator and TG bond that OOCL’s and Maersk’s published lists give for the depot are offered first, with the list’s name and date on the row — and when your master bill’s letters name the line, that line’s row leads. Name another operator or bond and an amber note says what the line publishes; nothing is refused. The wizard’s terminal codes come from ICES Advisory 01/2020.
- Filing
CFS filing for every organisation, and a CFS or transhipper file opens where it belongs
CFS filing is in the header for every organisation, and Pending split-ups sits under the “?” menu. A custodian’s or transhipper’s report (CUCHE01 / TRCHE01), or customs’ reply to one, is recognised from every door — the ACK drop, Check your SCMTR JSON, the files e-mailed to check@, the vessel-call drop — and opened where it belongs: your own report in CFS filing, a reply laid on its report, anybody else’s read in the checker with the reason.
- After filing
Arrival dates from Maersk and Hapag-Lloyd, read from the lines’ own tracking
The Arrival card and BL tracking now read Maersk and Hapag-Lloyd bills from each line’s official tracking: the ship and voyage into India and whether the date is an estimate or has happened. While a Hapag-Lloyd bill waits at a transhipment port, the card says where it is and gives no date until the line gives one. When a line’s tracking cannot answer, the card opens the line’s own page.
- Platform
A shipping line’s organisation: branches, view-only members and sub-agents
A line’s Indian agency can now run its whole team in one organisation, verified once by SCMTR.io staff. Add port branches (everyone still reads every port), make people View only — they see everything and change nothing — and invite a sub-agent company by its PAN — it reaches nothing of the line until the line confirms the company that accepted, by name. People join only when an admin says so: by invitation, or by asking from a company e-mail address or from one of the line’s manifests. A verified line publishes its CSN cut-offs from inside the app.
- Filing
Working together on one SAM or SAA, and one consolidated SAA
One person edits a saved SAM or SAA at a time; anyone else sees who, and can take it over or ask for a change — and no save overwrites somebody else’s work. Forwarders whose CSN amendment needs the line’s SAA can ask the line as they sign it, and the line sees whether customs has accepted that amended CSN before sending its SAA. The line’s people who may send approve each request (a decline always says why), apply it with one press, and choose when approved changes go: as each is approved, or gathered into one consolidated SAA at times the line sets. A second SAA on the same manifest waits up to an hour for customs’ reply to the first.
- Checks
Two SAA refusals caught before you send: 368 and 230
An SAA that moves a line quoting a CSN to a different cargo movement than customs’ record of that CSN now stops before it is sent (368) — when the file opens and again in Build amendment — and a different next port or destination is a warning: get the forwarder’s amended CSN onto customs’ record first. An SAA whose submitter type differs from the SAM’s is stopped too (230), with one press to set it right — send it from an ICEGATE ID registered under that type. A submitter PAN unlike the SAM’s, or a missing amendment type, is a warning. And an export consolidation’s load status no longer stops a send: the box may be FCL on the CSN and LCL on the line.
- Filing
Build amendment: a changed bill, after an accepted SAA, and without the SAM
A different bill typed onto a line now goes as that line removed and the new bill added under the next free number, never as an update of somebody else’s bill. An amendment built after customs accepted an earlier SAA starts from the manifest with it applied, so nothing is repeated or undone. With no SAM file here, Build from customs’ record makes removals and additions from the count of what customs holds. Before you sign, Build amendment checks every line the SAA changes, removes or adds against customs’ record, and a line that still has an error — or that customs would refuse — can be left out of this SAA, to send later.
- Filing
CFS filing: a CFS, ICD or transhipper makes, checks and signs its own SCMTR reports
Say what happened — Container stuffed, Vehicle departed — and the custodian’s report (the stuffing report, its cancellation, the stripping report, the vehicle’s departure and arrival times) or the transhipper’s (the ASR, departure and arrival, marked beta) is laid out for it, your yard and the next job number filled from your last one. A custodian’s report is checked as you type against ICEGATE’s own rules for each of its fields, and every report against customs’ published refusal codes, with one-press fixes where the fix is certain; the next container of the same bills is one press. Sign with your DSC and the file is saved under the name ICEGATE reads, for you to upload through ICEGATE’s API utility — SCMTR.io does not send it. Drop customs’ reply back and each refusal lands on the field it is about. A file your own software made opens and is checked too.
- Platform
The SCMTR.io phone app, for early testers: what customs said, the ACK file recorded from your phone, your CSN cut-offs
A companion app for iPhone and Android. Today shows what is waiting on you — approvals you can decide, CSNs customs refused, drafts whose cut-off is close. Filings shows what your organisation filed and what customs said, searchable by job number or BL. Record the e-mailed ACK file from your phone, or tap the attachment in Mail and choose “Open in SCMTR.io”; the app asks before it records. Approve a colleague’s held send, keep the CSN cut-off board with reminders a day, three hours and an hour before, and use BL tracking, VCN search and the assistant. Sign in with Google, Microsoft, an e-mailed link or, on an iPhone, Apple; delete your account from Settings. Nothing of your organisation’s is kept on the phone. The phone build is a test build with early testers — write to support@scmtr.io to join. It is not yet in the App Store or on Google Play. Corrected 28/10/2026: approving a held send is not switched on yet, so no approvals reach Today.
- Checks
Customs’ advisories 41 and 42 of 2026 on transhipment messages, explained
A new reference page reads the two ICES advisories of 7 October 2026 for custodians, CFSs and transhippers: the order the export transhipment messages are filed in and who files each, and the CFS’s three-part LCL import transhipment message with its field limits — and what neither changes for your CSN (nothing). The pages that said the CFS’s message goes through a value-added network now also give the advisory’s answer, JSON through the ICEGATE API, and say which a CFS uses is not settled.
- Filing
Bills by e-mail: bigger e-mails, slow reads tried again, unread bills named
An e-mail of bills may now be up to 35 MB, more than Gmail or Outlook will send, so a consolidation your mail app sends in one e-mail is read in one. A bill that could not be read the first time is tried again, and one still unread is named in the reply so you can send it again. A PDF holding many house bills is read up to forty bills, and the checklist shows each party’s state. An approved checklist now opens in the guided steps when the draft fits them.
- Filing
Port of receipt follows the ICD, and long suggestion lists stay open while you scroll
Filling a house bill from ICEGATE now sets the port of receipt to the station the cargo is delivered to — the ICD for inland cargo. Dragging the scrollbar of a long suggestion list no longer closes it, and every kind of line break copied from a PDF or Word file becomes a space instead of joining two words.
- Filing
Exports: a shipping bill’s PCIN goes under prior declaration S, not Y
An export straight bill that quotes its shipping bill’s PCIN with prior declaration Y is now stopped before it is sent, with the fix: set it to S. Otherwise customs may answer 389 “CIN is Not Used in Any SDM/SCX”.
- Filing
Bills by e-mail: a container’s size code follows its shipping line
A draft made from e-mailed bills now writes each container’s size code the way the box’s shipping line files it — your team’s own code for that line’s boxes first, else the code usual for the line — rather than only what the bill prints, and marks it to check. Customs compares the size with the line’s manifest, so a draft now starts from the line’s own code.
- Checks
A party code typed PPT is checked for a passport number’s shape
A consignor, consignee or notified party whose code type is PPT now gets a note when the code is not shaped like a passport number — and says so when it reads as a PAN, an IEC or a GSTIN, so the type can be put right. It is a note, never a stop. BL tracking’s expected arrival and the arrival-moved e-mails now go by India’s day, also between midnight and 05:30, and the cut-off board counts one arrival shown under two VCNs as one call.
- Filing
Bills by e-mail: you choose the CFS, marks templates kept as marks, and Shekou as your master names it
On the questions page your usual CFS is listed first but no longer chosen for you, so a CSN goes to the CFS you pick. A marks template printed on a bill (“PO NO / ARTICLE NO / COLOR / SIZE …”) is written as the marks instead of cutting the goods description short; a house bill printing Shenzhen under a master naming Shekou takes the master’s port; and a shipper printing “P.R.C.” is read as China.
- Filing
For shipping lines: an SAA we prepare, opened and signed only with your DSC — and two films
SCMTR.io can prepare a complex SAA for you — a straight bill re-filed as a consolidation quoting the forwarder’s CSN, a line removed whole — and send it to you as a link. It opens only with the DSC of the authorised person your SAM names, shows what the SAA does rather than the file, and is signed and sent from SCMTR.io after customs’ record is checked once more. Two new films show it, and the whole route for an SAA you build yourself: from the SAM customs accepted to the file uploaded to ICEGATE.
- Checks
Every problem on a house bill says which house bill it is on
The full form’s list of problems to fix, and the file checker’s findings, now name the bill above each one — “House bill 4 · <its HBL number>”, or the master B/L — so eight house bills missing an HS code no longer read as eight identical “Item 1” rows. Drafts made from e-mailed bills also leave the service terms (“CY TO CY”) and the bill’s ORIGINAL or COPY stamp out of the goods description.
- Platform
Accepting a colleague’s invitation keeps the organisation you already filed from
If you are the only member of an organisation you have used — filings, manifests, kept files, the address book, API keys, a saved portal login or its filing profile — accepting an invitation to another no longer deletes it: you stay in it and join the new one beside it, and the organisation mark in the header switches between the two. Only an organisation in which nothing was ever saved is removed when you accept.
- Filing
Bills by e-mail: the line’s PAN on every box, its sizes, and a bill sent as two files
A master bill whose number carries no line’s letters — a Maersk waybill, a TS Lines number — now gets the line’s PAN on the master and on every container, from the line the bill names as its issuer. Box sizes follow the line’s usual code. A bill sent as two files (the bill and its attached sheet of containers) is read as one, so its ports, date and VCN are no longer lost; a total that only counts the containers takes its packages from the containers’ own lines; and the container clause and the paperwork around the goods (“5*40HQ CONTAINERS S.T.C”, GSTIN and IEC lines) are left out of the description — while a bill listing each kind of goods with its own HS code keeps every kind. An HS code printed as “HSCODE”, “HS-CODE” or with a long dash is read, and a printed code that could not be read is said rather than dropped. In the full form, Combine and switch stays open until its save lands, and says why when the save is refused. Marks printed as “AS PER COMMERCIAL INVOICE” are written as the marks rather than at the head of the goods, and a container size code follows your own habit only once that habit is clear.
- Vessels
CSN cut-offs: a call being confirmed by its line shows on your CSN and in VCN search
When a line’s advisory for your CSN’s call waits for the line’s own check, your CSN page and list and VCN search now say “Being confirmed by the line”, as the board does, rather than that no line has published one. A call customs’ record names no one line for is said as that, never as a line’s; the home page’s “closing next” lists the soonest cut-offs, estimates included and marked, with each one’s time on a phone too; and an older estimate counted to the day reads “by the start of” that day everywhere it is shared.
- Checks
Amendments and exports: a bill with no amendment type named as 305, a dock’s code in the port field, and a whole-CSN deletion sent as an update
On an SCA, a bill whose own amendment type is empty now says so in customs’ words — 305, “Incorrect Message Type For Amendment” — and a 305 on an acknowledgement comes with its own fix. A customs location code such as a dock’s, given where the port’s own code belongs, now names the port to use. An SCA that removes every bill it carries under a declaration of U asks whether the whole CSN was meant: a whole-CSN deletion says D. A passport number typed in a spreadsheet batch or an e-mailed draft is typed PPT, a gross weight in MTS is read against the containers at the precision it was written, the time a file reached ICEGATE is shown in IST, and a refusal that names no reason now says what to do: stop after a second identical reply and ask the ICEGATE helpdesk.
- Filing
Shipping line filing: a CSN quoted under the wrong indicator is fixed in one press, and fewer false stops
When an SAA adds a line quoting a CSN’s CIN, SCMTR.io now checks customs’ record for what that CIN is: a straight CSN’s own PCIN is quoted by an S line, a consolidation’s MCIN by a C line, and Make this line S (or C) sets it. A container weight written as 4816.280000000001 by the software that made the file is no longer called too long, a box changed on an updated line but not restated on the vessel list is a note rather than an error, and an item row left on a removed line is pointed out whatever its flag.
- After filing
The pending split-ups board shows where the splits are stuck, reads in pages, and looks for a bill at the neighbouring customs location
Above the rows, “Where the splits are stuck” counts the pending bills so the culprits show: which line holds the most house bills and what share, how many bills customs’ record confirms stuck at the line, how many ships already have entry inward, the commonest cause, the busiest port, how long the cargo has waited, and the ships carrying most of it — tap a line, port, cause or finding to see its rows. The board reads 25 rows a page with every heading sortable and filters by port, line, cause and finding, and the view you set is in the page’s address, so a filtered page can be sent as a link. And a bill listed at a port customs holds nothing for is now looked for at the port’s neighbours, such as Kattupalli for Chennai, and the finding says where it was found and opens the lookup there.
- Filing
The port of receipt follows a corrected destination in the full form, and the port list offers the station filings use first
Change a bill’s destination in the full form and its next port of unlading and port of receipt move with it, as they already did in the guided steps, so the receipt port is not left at the old station. Typing a place with several customs stations, such as “dadri”, now offers the station most used first (ICD Dadri, INDER6) instead of the first by alphabet. And a CSN whose port of receipt is another Indian station than its next port of unlading gets an amber note: CBIC defines the port of receipt as the port of destination on the bill of lading, so use the station the shipping line’s manifest names in both.
- Platform
The pending console split-ups board: the consolidators’ register, public, read against customs’ record daily
Every master bill whose house bills the shipping line has not yet split onto its manifest, as a board at scmtr.io/pending-splits — read by anyone, downloadable as Excel or PDF, with each row added and changed only by the organisation that listed it. Each row carries Our findings, checked against customs’ public record: whether the bill still looks pending, or customs’ record shows the house bills linked. A finding, never a verdict: a row is marked resolved only by its owner or staff. Under it, SCMTR.io’s reading in plain words. It is a header pill on both headers; “Ask a question” left the header rows the same day — the corner launcher at the foot of every page is the one way in.
- Vessels
More calls on the cut-off board — and calls a line is still confirming shown as such
The board now covers more of the ships filers file for. A call a line has sent but not yet confirmed shows as “Being confirmed by the line”, with its ship and port only and no time, until the line confirms it. Three more agents’ calls now show under their own lines rather than Line not known, and a shipping line can show its own logo beside its calls by uploading it on its desk. Every cut-off stays indicative: confirm it with the shipping line.
- Vessels
The cut-off board says plainly when a cut-off is not known — and what to do
Most calls on the board have no cut-off the line has published — ships due tomorrow among them — and the board now says so plainly. Its two tabs are Cut-off known and Cut-off not known, and every call without one says what to do: “File now — ask the line” for a ship due within three days (its last foreign port is probably behind it), “File early — ask the line” otherwise, with customs’ rule or the line’s own beneath. The board opens on whichever tab holds what you searched for, so a call it holds is never answered “no match”, and it says how many calls match and where. The default view warns when ships due within three days have no known cut-off. A line whose calls all lack one opens on them, its card says “cut-off not known”, and the lines with no call on the board right now are named under the grid. On your CSN list, a CSN whose cut-off is not known says so with what to do — a CSN whose call is on the board links that call, and its reminder links it too. The board now also holds the upcoming calls customs’ record lists for the ships it knows — marked “From customs’ record”, under its line where one is known, else under Line not known — so a ship’s Cochin call is there beside its Nhava Sheva one; and VCN search says the same beside each call still to come. A closed cut-off now stays on the board until three days after its ship’s arrival. Every cut-off stays indicative: confirm it with the shipping line.
- Vessels
CSN cut-offs: your line’s own rule on a CSN, and Visakhapatnam’s calls
A CSN whose call the board does not hold now shows the published rule of the line it names — when that line wants the CSN, in its own words and linked — and a house-bill deadline is called one, never a CSN cut-off. The reminder for an unsent CSN uses the CSN’s own line, never another line’s cut-off on the same call. Calls at Visakhapatnam are now on the board, and the lists lines and ports publish are read more often. Every cut-off stays indicative: confirm it with the shipping line.
- Sharing
BL tracking and cut-off links say what they found in WhatsApp
A BL tracking link copied from the browser now previews as a card naming the bill, with the shipping line’s arrival date when the bill names its line and that line’s answer is recent. A cut-off board link previews as the call it finds, or the soonest cut-offs of one ship, line or port; a line’s own page shows its name and its open cut-offs. Share on the board sends them as text with the link.
- Checks
Tonnes and kilograms read as one weight wherever they meet, and a passport number spotted
A bill in MTS no longer fills its container with the same figure in kilograms, in the guided steps or from a bill sent by e-mail, and the house bill’s box picker adds the boxes up against the bill in kilograms. “Does customs hold this version?” and the line’s SAM comparison read 10.29 MTS and 10,290 KGS as the same weight. A code shaped like a passport number is offered the type PPT. And a file that is not valid JSON says where it breaks when it comes by e-mail or through a line’s share link too.
- Checks
A passport number is typed PPT, and a broken file says which line to fix
A party identified by passport number takes the code type PPT; any other type on the exporter (PSP, say) is stopped before you sign (039), and pointed out on the consignee or notify party. An export’s transit lines are no longer asked for a transhipper. And a file that is not valid JSON now says which line is missing its comma, or that a tab was pasted into a value.
- Filing
Shipping line filing: three more mistakes in amendment files named, and an old SAM with a new rotation spotted
A vessel container list written under a line’s field names (eqmtId where the list has equipmentId) is now one error with a one-press fix that renames the fields; before, it showed as two dozen scattered notes. A line removed as if it quoted nothing, while customs holds it quoting a PCIN or MCIN, is pointed out (724). An amendment type the guide does not list (A) is pointed out and read as an addition. And when you open a SAM or SDM, it is checked against customs’ record, so a file that is an earlier call’s manifest with its rotation changed is pointed out. Empties on no line are now one note.
- Vessels
CSN cut-offs: the lines’ India-wide rules, more calls, and the board in the app’s header
Where Maersk or CMA CGM has given no cut-off for a call, the board now shows one estimated from the line’s own published India-wide rule — the CSN at least 72 hours before arrival — marked estimated wherever it appears, and never later than the rule. Hapag-Lloyd’s rule and customs’ own, which count from the ship leaving its last foreign port, are quoted rather than dated. Calls at APM Terminals Mumbai (GTI) are on the board too. The cut-off board is in the header of the app and of the site. Every cut-off stays indicative: confirm it with the shipping line.
- Sharing
A ship’s VCNs in the WhatsApp preview
A VCN search link sent on WhatsApp now shows a card naming the ship, its VCNs and their arrival dates, with the day of customs’ list it shows — when exactly one ship matches; otherwise it stays the plain search card. Each ship on the result also has Share, which sends the VCNs as text you can copy, with the link.
- Vessels
The CSN cut-off board
scmtr.io/cutoffs gathers the CSN cut-offs shipping lines publish — from advisories a line e-mails to lines@scmtr.io from its own verified domain, and from lists lines and ports publish. Each vessel call has one page at a short address, with the cut-off and the time left in India time, the customs VCN, rotation and VIA to copy, a calendar reminder and a WhatsApp message that names the date. A cut-off worked out from a line’s published rule is marked estimated. Every CSN now shows its call’s cut-off where the board has one, and the reminder for an unsent CSN uses it. Every cut-off is indicative: confirm it with the shipping line, whose advisory is the only authority.
- After filing
Arrival from the line’s own tracking, with a countdown
A filed import’s arrival is followed on the shipping line’s own tracking where it can be read, and the CSN list counts the days to it in India time, saying whose day it is — the line’s, your team’s or customs’. When the line moves the day, the team is told. A VCN whose arrival is far from the cargo’s is pointed out.
- Filing
A bill printing several HS codes is drafted as one item, and opens in the guided steps
A bill of lading that prints two or more HS codes used to be drafted from your e-mail as one item for each code, with no package count on any of them — every item to fix by hand, and a draft the guided steps could not open. It is now drafted the way such a bill is filed: one item with the first HS code, the bill’s whole package count and a description of the goods — the bill’s own goods description where its lines read differently — and the other codes listed in a note. A draft that already has several items on a bill can go to the guided steps too: Switch to guided steps shows, bill by bill, what combining them would change, and does it only when you say so.
- Filing
Bills by e-mail: up to 40 bills, and a draft that needs less fixing
One e-mail may now carry 40 bill PDFs, up from 12 — a master with twelve or sixteen house bills used to lose the files past the twelfth. The master bill is found in a subject that lists it ahead of its house bills, and a CFS code written on its own line beside the name is read, so both are asked less often. The ship’s VCN is the call of this voyage, not an earlier call customs still lists — left blank where two calls fit — and a ship printed as “MV. NAME” is found. A PDF you send a second time is not read a second time. A party’s state comes from its own box or its city rather than from an old record, “MUMBAI - 51” is written as PIN 400051, and a shipper abroad is no longer placed in India by a six-digit postcode. An HS code a bill prints again without a count is not a second item, “CTN (OUTER)” is cartons, and house bills are listed in the order of their numbers. A master bill dated in figures only, or not dated at all, takes the date its house bills allow and is marked to check.
- Checks
An SAA removing a line is checked down to its house bills
When an SAA removes a whole line, every house bill under it and each house bill’s containers are now checked against what customs holds, not only the master’s containers. One that customs no longer holds is an error, with one press to leave it out of the SAA. For a shipping line, a line quoting one of a forwarder’s house bill PCINs, or a PCIN that no CSN under its bill carries, gets a warning (360). In an SCA, a new row is numbered after every number customs already holds, and an opened file whose vessel mode was not sea says so when it is set to 1.
- Checks
Fewer stops for what customs accepts, and two new cross-checks
A house bill whose items add up to a different package count from the bill is now a warning on an import rather than a stop, and stays an error on an export (709). A third decimal on a container weight no longer draws a note. The vessel’s mode of transport is always sea and is filled in for you. For a shipping line, a line quoting a CSN’s MCIN or PCIN that names someone other than that CSN’s filer as consolidator is an error (360). Checking a CSN or a manifest line against the bill of lading PDF now also compares each container’s size code with the box the bill prints (“1X40’OT”) and pauses on a difference — never a stop. A checklist saved as PDF is named after its master bill.
- Filing
An SCA is checked against what customs holds before it is sent
An amendment that updates or deletes a row your accepted CSN never had — a port of call, a container, an item or a house bill — is now stopped before it is sent (750), with one press to mark the row added (S). What customs holds is read from every accepted version of the CSN here. If an amendment made through other software added the row, press Customs holds it beside that row: it goes on your word, row by row, and your word is kept with the filing. An amendment now keeps every number customs holds and numbers only a new row after the highest; a new amendment made from an accepted one leaves out the rows that one deleted. A new CSN whose master bill is referenced only (R) but declared Y with a PCIN is stopped (115).
- Checks
SAA: a removed line goes whole, and three more refusals are read
Removing a line in an SAA built here now sends the whole line — every container, route leg and document marked D — so customs does not answer with 242 on its legs and 300. An SAA whose line or container total counts only its own rows while it changes a line or box numbered far above them is stopped (89, 90); a total that is merely low is a warning. A container size that differs from the CSN the line quotes is now an error for the shipping line (398) and stays a warning on the forwarder’s side. Changing the CSN, PCIN or MCIN a line quotes by an update is flagged with what customs checks the new one against.
- Checks
A box kept aboard as an empty no longer stops an SAA
When an SAA removes a line, a container no other line carries is named as one that would stay on the vessel’s list with no line, and the file could not be sent until it was marked removed. An empty being repositioned can rightly stay there, so the check now offers a second answer beside Mark it removed (D): Keep it aboard as an empty, which gives that row on the vessel’s list amendment type U and load status EMP. The stop then becomes a warning, and the container total keeps the box. Filling in a form from your address book, a bill of lading or ICEGATE now also tells you which fields were longer than customs allows and were shortened.
- Checks
Everything filled in for you now fits the field it goes into
A value the platform writes for you — from a bill of lading read off a PDF or pasted in, from a spreadsheet batch, from your address book or item templates, from customs’ own record, or from the bills you e-mail — now fits the field it lands in: plain text in the field’s own characters, cut at a word to the length customs allows — said so in a draft, a spreadsheet batch or an address-book edit — with codes, numbers and bill numbers left whole. A weight in a spreadsheet written in another unit than its row’s, or with a decimal comma, is left for you to correct rather than read wrongly. Until now a long goods description or street from a PDF went in whole and came back red for you to retype. The additional declaration’s and supporting documents’ text and numbers are now length-checked too; a number with more digits or decimals than its MIG format, and a manifest code outside the guide’s list, get an amber note. On the manifest side, the bulk-cargo form, a line built from a CSN, the fill-in dialog and the master’s name remembered for a ship are held to the manifest’s own lengths. A spreadsheet saved by Excel on Windows is read in its own encoding instead of turning every accented letter into an unreadable character.
- Filing
Bills by e-mail: the line’s agent, the size codes and "to order" bills filled in
The checklist drafted from your e-mailed bills now writes the shipping line’s agent as the consolidator PAN and the container agent on every box — from your own accepted filings for that line at that port, or the line agent usual for that line there — and your own PAN as the container agent on a straight bill. Each container’s size code is read from whichever bill prints it fullest and written in the code your own filings use; the mode of transport is sea without asking; a count written in words ("ONE CONTAINER", "SAY TWENTY-EIGHT CARTONS") is read as the number, and a total box that counts containers never gives the package kind. A bill consigned "to order" or to a bank takes its first notify party in India as the consignee and the next as the notify party — the warehouse rather than the registered office when the same company is listed twice, never a bank — and a form’s pre-printed "CONSIGNEE (TO ORDER)" heading above a real company and address no longer makes a bill "to order". A party you have filed before takes the codes you filed it under, with its name and address as the bill prints them. A notify party abroad gives way to the consignee, the goods description is the goods without the carrier’s clauses and the paperwork, a container line in the marks column is not a mark, and a Korean bill’s "KOREA" and a city that was missed are read. Far fewer values need typing by hand; what is filled in is marked to check.
- Platform
Every walkthrough film has its own page
Each of our walkthrough films now has a page at scmtr.io/films, with the film, what it shows and the reference pages beside it, so a search for the task finds the film here. The films play in YouTube’s privacy-enhanced player, and only on those pages; the privacy policy says what that player does.
- Checks
A house bill carrying its own master B/L number is flagged
A filer typed the master bill’s number into a house bill and nothing said so. The CSN check now points it out as a warning. It does not stop the filing.
- Filing
E-mail your bills of lading and get the checklist back
Send a master bill of lading and its house bills as PDFs to the bills address (shown in Settings under Bills by e-mail), and SCMTR.io reads them and e-mails you the Sea Cargo Manifest Checklist drafted from them. Where the bills leave out something only you know — which CFS the boxes go to, a consignee’s PAN or GSTIN, a missing master — one short page asks you, with no sign-in, and the checklist follows the moment you answer; what your e-mail already says (the CFS, "DPD", a PAN) is read first and never asked twice. Every reply answers under your own subject in one conversation. A person in your organisation then approves the checklist in SCMTR.io and the draft CSN opens for the usual check, sign and send. Your admin switches it on per person under Settings → Team.
- Filing
Removing a line in an SAA: its containers come off the vessel list too, and the container total says so
When an SAA removes a line, each container that line held and no other line carries is removed from the vessel’s container list too. Count what customs holds now names a box that would be left on the vessel with no line, offers Mark it removed (D) when its row is in the file with no amendment type, and asks for the container total that counts it out. Before, the total it asked for kept the box on the list. A box left out of the vessel list is no longer reported as missing from it (279).
- After filing
The EGM reply after a departure manifest is read: which shipping bills made the EGM and which did not
After an SDN, ICEGATE mails a flat file with one row per shipping bill and a letter beside it. Drop that file on Check your SCMTR JSON (it takes the .out as it comes) and SCMTR.io lists the bills customs put on the EGM and the ones it left off, laid over the lines of the SDM it answers. The SDN itself is now checked against its SDM, as an entry inward is against its SAM.
- Filing
Fetch from ICEGATE no longer reads a shipping bill’s weight in tonnes as kilograms
Customs’ shipping-bill record gives the gross weight in the bill’s own unit without saying which, and some bills are in tonnes. Fetch from ICEGATE used to fill it as kilograms. It now shows customs’ figure as given, matches it to your weight in either unit, and when they differ offers both readings for you to choose, never writing one you did not tick. It also says when a shipping bill is still waiting for stuffing.
- Checks
The seal check names 701 as well as 703
A container given different seal numbers on the bills that name it can come back refused 701, “Multiple SealNo for Equipment-Id”, as well as 703, “BL and HBL SealNo Does Not Match”. The check that stops it before you file now names both, so a refusal carrying either is easy to match to it.
- Platform
Invited to a colleague’s organisation while you have your own? Now you can accept
An invitation sent to someone who already had an organisation — usually the one their own sign-up made — used to sit unseen until it expired. Now a line under the header says who invited you, and the invitations page says what accepting does before you press: you leave your current organisation, or, if you are its only member, it is deleted with everything in it, irreversibly, after you tick that you understand and type the word. The only admin of a team is told to hand over first. Declining tells the inviter.
- Checks
Choose a CSN and its ACK together, and both open as one
On Check your SCMTR JSON, choosing the _DEC and the _ACK in one go used to be refused with “choose one file at a time”, and the SCMTR JSON upload box on CSN filing took one file only. Now both take the two together: the ACK opens with the CSN paired onto it, whichever order you chose them in — the same page, verdict and checklist as dropping the ACK first and the CSN into its box. An ACK that answers a different CSN is still refused, with the ACK left open.
- Filing
A removed line names the CIN it quotes, and a line quoting a CSN by number names your own PAN
Removing a line that quotes a PCIN by its bill reference alone can be refused 724 “CIN No Should be Provided in Prev-Decln of SAA/IM-SCA”. Build amendment now writes the prior reference on a removed line that declares an earlier declaration, the checks stop a line quoting a CIN that lacks it, and the reply story reads 724. And a line quoting a forwarder’s CSN by number and date — the shape used when no MCIN is anywhere — names the manifest’s own filer as consolidator; Add a line from a CSN writes it so, and the checks point out one naming anyone else.
- Platform
What customs and the ports published since August, in the knowledge base
The rollout article now carries each port’s notice ending supplementary IGM/EGM (Tuticorin from 13 August), the ITP and ST messages live from 21 August, JNCH’s fixed list of papers for an officer-approved amendment of empty containers or foreign transhipment cargo (Public Notice 115/2026), and Mundra adopting JNCH’s procedures. A codeless CSN refusal that repeats on resend is no longer read as load: the article says to stop sending it unchanged and read the file.
- Checks
A weight in tonnes is read as tonnes, and another port’s VCN is pointed out
A gross weight in MTS is now compared with your containers’ kilograms as tonnes, and with customs’ record — which shows an export CSN’s weight in KGS — as the same weight, so 168.3 MTS no longer reads as a difference. A gross weight under MTS that is really the containers’ kilograms is pointed out, and so is a VCN issued at another port than the one you file at. And a refusal coded 700, or naming no reason, now says plainly what to do next.
- Platform
Every date and time is shown in Indian time, marked IST
Dates and times across SCMTR.io — on the web, in e-mails and in the mobile app — are now always Indian Standard Time, and a time is marked IST, wherever your computer or phone is set. Before, a reply customs stamped at 02:00 IST could show on the day before when read from a computer set to another zone, and a few sentences quoted times in UTC.
Something you need that is not here? Tell us on the roadmap — everything on it came from someone who files under SCMTR.