Datasheet — partner view

Your importer does the prep. You get a clean file.

CouloirIQ is the workspace importers use to structure a trade before it reaches you: requirements identified, documents collected and read, values reconciled, deadlines tracked, and every step recorded in a tamper-evident log. What arrives on your desk is a file you can work from, not a folder you have to rebuild.

The cost of an unstructured file

Most delays are made before the goods move.

A missing certificate. A weight that disagrees between invoice and bill of lading. A presentation window nobody was watching. By the time it surfaces, you are the one making the calls — and absorbing the demurrage conversation.

What changes

The exceptions arrive named.

The platform reconciles values across documents and surfaces conflicts as exceptions with both sources attached. Requirements are matched against evidence as it lands, so the gaps are visible while there is still time to close them.

The file you usually receive

Documents attached across several email threads
Figures re-typed by hand, source unknown
Certificates still outstanding, chased informally
No record of what was checked or when
Corrections agreed verbally, never written down

The file from a CouloirIQ trade

One workspace per trade, structured by corridor and commodity
Every value traced to a document, page and confidence band
Outstanding evidence listed, with supplier requests already sent
Deadlines captured as trackable facts, not diary notes
A sealed snapshot you can archive alongside the entry

Where it helps you specifically

Three things that shorten your side of the job.

Handoff

A pack, not an inbox

Broker and forwarder handoff packs are generated from the trade's structured address and identity model — country of establishment, customs and tax identifiers, consignor and consignee — instead of being retyped per shipment.

Documentary credit

Discrepancies found early

A twelve-stage lifecycle check reads the credit and the trade together, with UCP 600 framing: expiry, latest shipment date and presentation window are tracked as facts against the documents actually held.

Evidence

Suppliers upload directly

The importer sends a tokenised request; the supplier uploads from a phone with no login. Documents classify on arrival and attach themselves to the requirement they satisfy.

TwinLog — the part your compliance team will care about

Every material event on the trade is hash-chained into an append-only ledger. Integrity can be verified on demand, and when an importer proceeds past an advisory, that acceptance is recorded with it. This is evidence of due diligence and a record of decisions — not a certification of compliance, and never a substitute for your own checks.

document.uploadedfield.confirmedexception.raisedadvisory.acceptedmilestone.reachedsnapshot.sealed

Coverage and fit

Where it currently works.

OriginsWorldwide

DestinationsUK, EU, Switzerland, Türkiye, US, Canada, UAE, Saudi Arabia, Qatar, Oman — each researched individually

RegimesCustoms, SPS and phyto, ICS2 and security filings, sanctions screening, EUDR, CBAM, origin and preference, battery, food and agri, halal, species, ethical sourcing

ConfidenceEach corridor plan declares its own tier and lists what it does not know

IntegrationKeyed API with scoped permissions; webhooks across trade, document, supplier, compliance, milestone and claim events

LanguagesTen interface languages across web and mobile

What the platform will not do.

It does not quote duty rates — where an official lookup is required, it says so. It does not quote insurance premiums; it checks coverage against the trade and computes only from a rate the customer has been quoted. It does not track vessels from AIS feeds; journey stages come from documents and confirmed facts. And it never prevents a trade from moving: it advises, scores, and records the decision.