Stop Fixing Manifests After They're Rejected.
If you've ever submitted a manifest to 1-Stop, got an XML rejection, fixed it, resubmitted, and got another rejection — this is for you. StarShipper validates your manifest data before submission so you can fix everything in one pass.
The rejection loop that eats your morning
You compile carrier data — XML from CargoWise, a CUSCAR EDIFACT message, a spreadsheet someone emailed. You format it for 1-Stop and submit. Then it bounces. A bad container check digit, "Sydney" instead of AUSYD, a missing seal number on line 47.
You fix it, resubmit — and it bounces again. A different error, because 1-Stop stops at the first failure. Meanwhile the vessel is at berth, demurrage is ticking, and someone is asking why the containers aren't released.
The problem isn't that your team makes mistakes. It's that you only find out after submission — and only one error at a time.
Carrier Data In
XML, EDIFACT CUSCAR, CargoWise exports, PDF & Excel manifests
Parsed & Normalized
Port names resolved to UN/LOCODE, container numbers verified
Validated & Ready
7-point checklist passed, ready for 1-Stop submission
Validate everything before you submit
StarShipper runs the same checks that would cause a 1-Stop rejection — but before you submit, and all at once. Port names get resolved to proper UN/LOCODE codes ("Port of Brisbane" becomes AUBNE, "Shekou" becomes CNSKL), container numbers get their ISO 6346 check digits verified, and every required field is confirmed present.
You see a readiness checklist showing exactly what passes and what needs fixing. One pass, not one rejection at a time.
The 7-point readiness checklist
Check digit validation catches transposition errors before they reach the terminal.
Auto-resolves names like "Sydney" or "Port Botany" to the correct AUSYD code.
Same resolution for destination ports — 50+ ports with aliases built in.
Confirms seal numbers are present for each container.
Validates Bill of Lading number format and minimum length.
Verifies weight is present and greater than zero per container.
Confirms package count is present for the shipment.
These are the checks that cause 1-Stop rejections at Patrick and Hutchison terminals. We run them before you submit.
Built for the people doing the actual work
We built this for ops teams at liner agencies, customs brokers, and freight forwarders who deal with Australian port manifests. StarShipper handles CUSCAR and COPARN EDIFACT messages, CargoWise XML exports, and the spreadsheets and PDFs that still make up half the industry's data exchange. It knows the port codes for 50+ ports across Australia, China, Southeast Asia, Japan, Korea, and Europe — including the aliases that real people actually use.
If your week involves compiling manifest data from multiple sources and submitting it to Australian terminals — we'd like to save you the rejection loop.
Try it on your next manifest
Upload a manifest file and see the validation results before you submit to 1-Stop. No commitment — just see what it catches.