Trade Documents - Muin Docs

The trade document explorer finds your shipping and customs paperwork, shows the fields extracted from each, and exports the result.

When you’d use this

A broker asks for every customs declaration in a quarter, with declared values.
You need the bill of lading for a container and only remember the consignee.
Two declarations need comparing.
You want to check a document against a regulation.

Find a trade document

Go to Sidebar → Trade → Export → Documents.
The screen opens pre-filtered to trade document types: bill of lading, customs declaration, trade license and import permit.
Narrow it:
- The search box takes a filename or a tag:value pair.
- From date and To date limit the range.
- Type:, Status: and Tags: chips toggle on and off.
- Field Filters filters on the extracted fields.
The table shows Filename · Type · Status · Created · Updated by default. Use Columns to add extracted fields.
Click a row to preview, double-click to open the document.
Select two or more rows and Compare & Synthesize reads them together.
Export offers CSV and Excel.

What gets extracted

Two of the four preset types have extraction schemas, so only these produce extracted-field columns:

Bill of Lading: B/L Number, Shipper, Consignee, Carrier, Port of Loading, Port of Discharge (all six required), plus Goods Description, Weight and Containers.

Customs Declaration: Declaration #, Importer, Exporter, Origin Country, Goods, Declared Value, HS Codes, Duties.

Trade license and import permit have no schema today. You can still file and find them; they simply show no extracted fields. To track what a license still allows and when it runs out, add it on Licenses and attach the document there.

A commercial invoice schema also exists, for the invoice that travels with a shipment.

Running a compliance check on a document

Besides the Trade screens, a general Compliance Check can be run you run against one document, on demand, from the document itself rather than from the explorer.

It returns, per requirement: the requirement, a status of pass, fail, partial or not applicable, the evidence it found, and a recommendation, plus an overall status and a pass rate. The result is a reading aid for your team, not a determination.

You choose what it checks against: a named standard (GDPR, HIPAA, SOX, PCI DSS, ISO 27001), one of your own policy documents, a free-text description of the policy, or the default “general compliance review”. No customs or trade standard is in that list, so for a customs requirement give it your own policy document or describe the requirement in the free-text option.

What it affects

Nothing in the explorer changes a document.
A compliance check is a read: it produces a result you read, not a status on the document.
Extracted fields are what make a document findable by content, so a document that failed processing is findable only by filename.

When it goes wrong

What you see	What it means	How to clear it
“Unable to load documents” / “The document list could not be loaded. Retry, or check back shortly.”	The document service did not answer.	Click Retry.
“No documents found”	Your filters exclude everything.	Clear the type, status, tag and date filters.
A trade license or import permit with no extracted fields	Those two types have no extraction schema.	Expected. Use the standard columns, and add licenses on Trade → Export → Licenses.
An export that never downloads	The export failed, and there is no error toast for it.	Narrow the filters and try again.
A compliance check that finds nothing relevant	It ran against a standard that has nothing to say about customs.	Re-run it against your own policy document, or describe the requirement in free text.
No Documents in the Trade menu	Your role does not hold the trade documents permission, or the module is not enabled.	Ask an administrator.

Next step

Customs entries and licenses: entries tied to POs, and licenses with what they still allow.
Trade module overview: every Trade screen.
Tariff refunds: a refund package for your broker.