Use SCMTR.io with Your ERP or Job Software
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 Cargo Summary Notification (CSN) on SCMTR.io — sent as a spreadsheet or through the API. A person checks the draft, signs it with their own DSC and sends it to ICEGATE, and the CSN number, the CINs and customs' reply go back to the job. This is called Connect, and it is free on every plan.
SCMTR.io with your ERP or job software: Do this on SCMTR.io →
Is SCMTR.io an ERP?
No. SCMTR.io is not an ERP: it keeps no job register, no accounts ledger and no yard or transport system of its own. You keep the software you run, and SCMTR.io does the SCMTR filing beside it — it takes jobs from your software as drafts, and gives CSN numbers, CINs and customs' replies back.
If you have no job software at all, nothing changes: you start a CSN on SCMTR.io from the bill of lading, as before.
Does SCMTR.io work with my ERP or job software?
Yes, with any job system that can do one of two things: export a spreadsheet, or call an API. Nothing is built for one brand of job software, so it does not matter which you run.
Choose the way that suits what your software can do:
- A spreadsheet — the sheet your job system already exports, dropped on Batches.
- The API — your software sends each job itself, or sends the same spreadsheet.
Each way makes the same thing: a draft CSN waiting for a person.
If what you hold is the bill of lading as a PDF rather than a job in a system, see Bills by e-mail.
How does my job system send jobs to SCMTR.io?
As a sheet or as a message, whichever it can produce.
- As a sheet. Export the jobs as
.xlsxor.csv. One row is one house bill in one container; rows that share a master bill become one draft CSN. Drop the sheet on Batches and choose the import profile it is read under. - Through the API. Your developers send each job with your own job number. The answer says, job by job, whether a draft was made, was already there or was refused and why, with the link to the draft and the notes made on any value that was changed or could not be read. See the API article.
Either way you will see the new drafts together as one batch on the Batches board.
My export's columns have their own names. Do I have to rename them?
No. Tell SCMTR.io once which of your columns is which, and save it as an import profile with a name — for example one profile for each job system or branch that sends sheets. Name the column that holds your own job number too: it is what lets the CSN number find its way back to the right job.
Profiles are kept under Settings → Connect and chosen on the Batches screen. After that, a sheet read under that profile needs no matching again. One profile is your default; a sheet sent through the API with no profile named is read under it. A View-only member can read the profiles and cannot change them.
Does SCMTR.io file the CSN by itself once the job arrives?
No. Every job arrives as a draft. A person opens it, checks it, signs it with their own DSC and sends it to ICEGATE, exactly as for a CSN typed by hand. Nothing is sent to customs without a person.
What is still left to fill is seen by the person, on SCMTR.io: the draft shows it when it is opened, and Check all on the batch runs the checks over every draft at once — red must be fixed before a CSN can be sent, amber is worth a look. The API's answer does not list it.
What happens if the same job is sent twice?
Nothing new is made. A job sent again under the same job number is answered with the filing it already made, and you are told whether what you sent now differs from what you sent then.
The draft is never overwritten — someone may already have corrected it, or sent it. To start again from your job system's copy, delete the draft on SCMTR.io and send the job again.
A sheet with no job-number column has nothing to recognise a job by, so the same sheet sent twice makes its drafts twice — name that column in your import profile.
How does the CSN number get back to my job system?
Three ways, and you can use more than one:
- The write-back sheet — one row a filing: your job number, its status, the CSN number and date, and the CIN. Download it from Settings → Connect and take it into your job system. Give a Changed since day for only what changed; a sheet holds at most 5,000 filings and says so in its last row when there are more.
- Events — your system is told as it happens: a draft made, a CSN sent, customs' reply recorded. Pushed as signed webhooks, or read from the event feed by a system that cannot receive them.
- The API — your system asks for a filing by your job number and reads its state, CSN number and date, and the MCIN or PCIN customs issued.
Does it work for export CSNs?
Not yet from a job system. A job sent in becomes an import CSN draft. An export CSN is made on SCMTR.io from its shipping bill, whose details are fetched from ICEGATE.
Where do I set Connect up, and what does it cost?
Under Settings → Connect: your connections and a list of what came in and what happened to it, in words, your import profiles and the write-back sheet. API keys and webhook addresses are made by an Org Admin under Settings → API.
Connect is free on every plan, like the API.
Can I see it working before I change anything?
Yes. SCMTR.io has a demonstration job system — an invented one, with invented jobs, labelled a demonstration everywhere. In a demonstration a job is sent to SCMTR.io from it, the draft that appears is opened, and the CSN number is seen coming back on the job. Ask support@scmtr.io to show it to you.
Still stuck on this?
Ask the assistant about this page, or anything else in SCMTR filing — in English, Hinglish or your own language.
Have the file? Check it free — no sign-in
General information only — not legal or customs-compliance advice, and it may not reflect the most current ICEGATE/CBIC requirements. Verify against the official sources, or a licensed customs broker, before filing.