No software to file your SAM? Build one here — bulk, tanker and break-bulk
2:56
Played in YouTube's privacy-enhanced mode. Invented data — no customer's data is shown.Watch on YouTube
Customs publishes the SACHM23 message and a place to upload it, and nothing that writes one — ICEGATE's own free data-entry utilities cover six other SCMTR messages and never this one. So for a bulk carrier, a tanker, a break-bulk or a tramp call, where no liner system produces the file, the official path has been to hand-write the JSON from the message guide.
In this film
- One question first: which ship? Give the IMO number and customs' own record fills in the call — the port, the VCN, the rotation number and date, and the expected arrival. Five things you otherwise copy off an e-mail, and five chances to file against the wrong voyage.
- Pick which of the four filings a call needs, named the way a steamer agent says them rather than by event code: the arrival manifest, entry inward, the departure manifest, the departure notification.
- Six steps, in the order you can answer them. The VCN, rotation number and date came with the call. Submitter code, PAN and carrier code are filled in from your organisation's profile in Settings — a change here is for this manifest only.
- The one thing you type is the line code: BLK, the code a bulk or tramp operator with no SCMTR line code of its own files under.
- A bill of lading is ten plain questions: the bill and its date, shipper, consignee, what the cargo is, its HS code, how many units, the weight, where it loaded, and whether it is dry bulk, liquid bulk or break-bulk.
- The other thirty fields of the line are written the way real bulk SAMs write them — the bill number used as the equipment id because break-bulk has no container number, bulk packages, metric tonnes, the hazard codes that mean none — each shown with the reason it was filled in, and none of them locked.
- The crew list is a document, not a list: upload it to e-Sanchit and put the reference here.
- The totals, the ship's own container list and every sequence number are counted from the file rather than typed, so they cannot disagree with it.
- Then it hands over to the editor, where it is checked again, signed with your DSC and uploaded.
Chapters
- 0:00Nothing writes a SAM for you
- 0:19Which ship? One IMO number
- 0:37One call needs four filings
- 0:47Six steps, and what only you know
- 1:01Filled in from your organisation's profile
- 1:12BLK — the code for a tramp operator
- 1:31Ten plain questions a bill
- 2:00The other thirty are written for you
- 2:12The crew list is a document
- 2:27Then it hands over to the editor
Read it instead
The SCMTR reference pages this film walks through — free to read, no sign-in.
- Filing a SAM or SDM when you have no software for itBuild a SAM or SDM from nothing for a bulk, tanker, break-bulk or tramp call that no liner system files for — what you need, and what to expect.
- 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, and correct a line without rebuilding it.
From SCMTR.io
SCMTR filing, checked before ICEGATE sees it
CSN, SAM / SDM and export SCX for forwarders, consol agents and shipping lines — every check before you sign.
- Check your SCMTR JSONFree, no sign-in — what customs would reject, and the fix.
- Track a B/LFree, no login — the SAM status straight from ICEGATE.
More films
- Check your SAM before you send it — every problem with its ICEGATE code
- "Delete the SAM and file an SAA" — what your customer is asking for
- Shipping line: check your SAM against every forwarder’s CSN — no need to upload again
- Sign & upload your SAM once: the confirmation that names it, and the check against a resend
- The bill that missed your SAM — put it on with an SAA, from their CSN
- Your SAM was rejected and the ACK names nothing — what to do