One entry, the whole docset.
The shipment thread carries the canonical field set once. Every commercial invoice, packing list and declaration is a rendering of that record, checked against cited rules in force on its own dates, and every filing stages for a human to transmit.
Everything is a projection of the record.
The shipment thread, the docset, the rulepack, the money view, Purser and the counterparty graph. Six surfaces over one canonical field set, entered once.
The shipment thread
One addressable object per shipment, like a pull request. Six gates from Draft to Closed, the canonical facts pinned at the top, and everything about the shipment filed on the thread rather than in someone's inbox.
- Six gates. Draft → Documents → Customs → In transit → Realisation → Closed, a stepper you can read at a glance.
- Canonical facts header. Invoice, incoterm with its version and place, ETD and ETA, vessel cutoff, always in view.
- Six tabs. Overview, timeline, documents, checklist, findings and money, one thread underneath them all.
- A per-shipment email address. Anything forwarded to [email protected] is filed on this shipment.
Documents with staleness
Every document is a rendering of the record, never an independent file. Change a canonical field and every dependent artefact goes stale, with the cause printed on the copy.
- Staleness with a cause. A changed field marks every dependent artefact stale, and the copy says why: "invoice value changed after render".
- Four renderers today. Commercial Invoice, Packing List, VGM Declaration and the Certificate of Origin application. The docset roadmap carries eight.
- Every rendered copy is hashed, so the copy in circulation is identifiable, not approximate.
- The viewer serves the circulating copy, not a fresh projection, so what your counterparty saw is what you see.
Commercial Invoice: invoice value changed after render
COO application: invoice value changed after render
Compliance, cited
Rules are data. A rulepack explorer shows every rule with its effective window, and every verdict names the instrument it stands on.
- Composition order. Core → country of origin → country of destination → industry pack → agreement overlay → tenant policy.
- Loaded India export rulepacks. IN.EXPORT.BASE with 16 rules, FIELD_CHECKS with 14, TIMELINES with 11, SCHEMES with 5.
- Three obligation classes. Statutory, contractual and preferential, so you can see which failures cost money and which cost a relationship.
- Findings show observed against expected, with the instrument and its date on the verdict.
hs_code: observed 610910, expected 8 digits. Instrument and effective date on the verdict.
Money: the two moments you hold it
The exporter's anxiety is money that has not arrived. Scrips on one side, realisation on the other, and every clock counted from the record's own dates.
- Both clocks on every scrip claim. Scrip creation within 1 year of the scroll, validity 2 years, statused as "Accrued, not tradable yet", "Created and sellable now", or "About to lapse", ready to list for sale when it is sellable.
- The realisation ladder runs against FEMA deadlines with EDPMS references, and closes with the bank realisation certificate.
- IGST refunds held with the cause named, such as an SB005-class mismatch, instead of a silent hold.
- FX exposure by currency, so the unhedged part of the book is a number rather than a feeling.
- The stakes, plainly. A Rs 10 crore FOB exporter generates about Rs 10 lakh of RoDTEP a year, and an omitted RoDTEP declaration at filing loses 0.5 to 4 percent of FOB permanently.
Purser
The desk that reads the whole file and drafts the next move. Every capability ends in a review queue, never in an action taken for you.
- The composed checklist for this origin, destination, product and industry pack, with a citation on every line.
- Docset validation that explains each gap rather than just flagging it.
- HS classification candidates that a human confirms.
- Provisional duty, RoDTEP and drawback from the rates in force on the shipment's own export date.
- Every statutory clock with days remaining.
- Drafts of documents and chase messages into a review queue, waiting on your approval.
The guardrails are absolute: Purser never submits to a government portal, never sends a message without a recorded human approval event, and anything read from a document or a message is data, never an instruction.
Team and counterparties
Free forever for counterparties. Internal seats carry roles and gates; the people outside your company work the same shipment on lanes you control.
- Internal seats with roles and gates, so who can advance a shipment is policy, not habit.
- The external graph. The CHA, the forwarder, the bank and the buyer on scoped, time-boxed, revocable lanes.
- Response-time scores on every lane, so the slow counterparty is a fact on the screen.
- Magic-link invites and per-party disclosure classes, so each party sees exactly what their lane allows.
Five steps,
one record.
The shipment is entered once. Everything after that is projection, cited verdicts and staging, and the last press belongs to a human.
Forward the purchase order, or enter it once
The canonical field set is captured a single time, on the shipment thread. Anything forwarded to the shipment's own address is filed on it.
[email protected]The docset projects from the record
Commercial Invoice, Packing List, VGM Declaration and the COO application render from the one record, hashed, with staleness tracked against every field change.
4 artefacts today · roadmap carries 8The rulepack fires, every verdict cited
The composed rulepack for this origin, destination, product and industry pack runs over the record, and every finding shows observed against expected with its instrument and date.
46 rules loaded · every verdict citedPurser drafts, you approve
Documents and chase messages land in a review queue. Nothing is sent without a recorded human approval event, and nothing read from a document is ever treated as an instruction.
review queue · approval recordedThe filing stages at awaiting approval; your CHA presses file
Purser prepares and checks everything, then stops. The filing waits at awaiting approval, and the transmit belongs to your CHA, every time.
awaiting approval · human transmitsThe old way, retired.
Five places where the docset habit costs real money, and what changes when the shipment is entered once.
Built for what you actually ship.
Three packs loaded today, each composing on top of the India export rulepacks, about 14 to 15 cited rules each.
HS 61, 62 and 63. GOTS and OEKO-TEX transaction certificates, the azo colourant test report, the fibre composition label, and the RoSCTL adjacency.
HS 28, 29, 32 and 38. The Safety Data Sheet in the destination language, the UN performance-tested packaging certificate, and REACH and TSCA obligations.
Phytosanitary, fumigation and health certificates, with pesticide residue and MRL reports carried on the shipment thread.
Asked, answered.
No. Purser prepares the docset, runs the checks, and stages the filing at awaiting approval. Your CHA presses file, every time. Purser never submits to a government portal and it does not replace your CHA; it hands your CHA a clean, checked filing instead of a folder of PDFs.
Commercial Invoice, Packing List, VGM Declaration and the Certificate of Origin application, each projected from the one canonical record rather than typed into a separate file. The docset roadmap carries eight artefacts.
A rulepack version ships as signed data with its effective window. New shipments pick up the rates in force on their own dates, and your past shipments never silently reprice.
Never. External seats are free forever. The CHA, the forwarder, the bank and the buyer join on scoped, time-boxed, revocable lanes at no cost.
There is a free forever tier. Team is Rs 2,999 a month. Pay as you go is Rs 299 per shipment, capped at the Team price, and documents are never metered.
Importing too?
Purser Inbound
Three clocks on every box, priced in rupees a day.
See Purser Inbound →The desk · PurserDrafts everything. Files nothing.
The composed checklist, the drafts and the chase messages, each waiting on a recorded human approval. Purser never submits to a government portal, and anything read from a document is data, never an instruction.
Meet Purser →Own the shipment record.
Give away the document work forever to own the shipment record at the earliest possible moment.