Your Shipments, Monitored Automatically.
StarShipper watches your active shipments and fires alerts when something needs attention — approaching ETAs, stale tracking, customs deadlines, missing documents. Configure the thresholds. Choose where notifications go.
The things that fall through the cracks
A shipment is arriving in 36 hours and the commercial invoice still hasn't come through. Customs clearance is pending but nobody realised the ETA moved forward by two days. Tracking hasn't updated in 12 hours and the vessel's gone quiet. A container has been sitting at port for three days because the N10 wasn't lodged.
These aren't edge cases. They happen every week on busy desks, and the cost is real — demurrage charges, clearance delays, missed delivery windows. The information to catch them exists in the system already. The problem is that someone has to remember to check.
StarShipper's automation engine checks for you. It evaluates every active shipment against a set of configurable rules and fires alerts through the channels you choose — in-app notifications, email, or both.
Shipments Evaluated
Every active shipment checked against your rules
Conditions Checked
ETA, tracking, customs, docs, phase progression
Alerts Dispatched
In-app notifications, email, or N10 auto-generation
Nine rules that watch what you can't
Each rule evaluates a specific condition on your active shipments. When the condition is met, the engine fires an action — a notification, an email, or in the case of N10 readiness, an automatically generated customs declaration. Every rule has a configurable cooldown to prevent the same alert from firing repeatedly.
ETA readiness alerts
When a shipment's ETA is within a configurable window (default 48 hours), the engine checks document completeness and manifest readiness. If something is missing, you get a notification with exactly what's outstanding — not a generic reminder.
Tracking gone stale
Actively tracked shipments should have regular position updates. When the gap exceeds your threshold (default 6 hours), the engine flags it. Useful for catching carrier feed outages or vessels that have gone dark.
Customs not cleared before arrival
If a shipment is arriving within 72 hours and customs clearance hasn't been lodged, the engine fires an action-required alert. Configurable — some teams want 48 hours, others want a week.
All documents received
When every expected document for a shipment has arrived — commercial invoice, B/L, packing list, certificate of origin — the engine confirms completeness. No more checking manually whether you've got everything.
Cargo at port, customs not lodged
The shipment has arrived or been discharged at the destination port, but customs is still in early stages. This is the alert that prevents demurrage charges from creeping up while paperwork sits in a queue.
Phase stuck
When a shipment hasn't progressed through its phases in a configurable number of days (default 7), the engine flags it. Catches shipments that have stalled without anyone noticing.
Documents and manifest ready
A composite check — all expected documents received and the manifest passes all readiness checks. Useful as a trigger for downstream actions like notifying your customs broker or generating declarations.
N10 auto-generation
When documents are complete, the manifest is ready, ETA is approaching, and customs hasn't been lodged yet, the engine runs a 9-field readiness check (ABN, HS codes, importer, supplier, origin, invoice number, value, currency, B/L number). If all 9 pass, an N10 draft is generated automatically.
Manifest readiness
When the manifest passes all readiness checks — port codes validated, container numbers verified, cargo descriptions matched — the engine notifies you that it's ready for submission.
Notifications where you actually see them
When a rule fires, the engine can send an in-app notification, an email, or both. In-app notifications appear in your Bridge dashboard with a direct link to the shipment. Emails include the shipment reference, what triggered the alert, and what needs attention — so you can act on it without logging in first.
For N10 readiness, the action goes further. Instead of just telling you the shipment is ready for a customs declaration, the engine generates the N10 draft automatically — pulling data from the linked commercial invoice, B/L, and packing list. You get a notification that the draft is ready to review, not that you need to start filling one out.
Action types
Your thresholds, not ours
Every rule is configurable from your automation settings page. ETA alerts default to 48 hours, but if your team needs a week's notice for FCL shipments, set it to 168 hours. Stale tracking defaults to 6 hours, but if you're tracking slow-moving breakbulk, 24 hours might make more sense. Customs warnings default to 72 hours before ETA — adjust to match your broker's turnaround time.
Rules can be enabled or disabled individually. Cooldown periods prevent the same alert from firing again until the window resets. The engine runs on a regular schedule, evaluating every active shipment across your organisation — so nothing sits unmonitored.
What you can configure
Stop checking. Start getting told.
Set up your automation rules and let the engine watch your shipments around the clock.
Customs Compliance
Validate HS codes, country of origin, declared values, and duty calculations against ABF requirements before lodgement.
Pre-Alert Lead-In
Detect incoming shipments from advance shipping notices, pre-alerts, and booking confirmations before the cargo arrives.