Trade Repository

Every document, linked to
every record it actually belongs to.

A commercial invoice isn't just "the shipment's file" — it's evidence for a party, a product classification, a license, and a filing, all at once. That cross-entity search now lives inside the unified Documents workspace, and the link layer underneath it makes a document many-to-many instead of one-to-one.

1
workspace searching every document in the account
6
linkable record types in the filter — shipment, party, product, license, license line, filing
15min
signed URL for storage-backed documents

The problem

"That invoice is somewhere on the shipment. Which shipment, I'm not sure."

"A document only lives under the shipment it was uploaded to. If it's really evidence for a party or a product, there's nowhere to say so."

One document, one home

"I know we have the manufacturer's origin declaration somewhere — I just don't know which of forty shipments it's attached to."

No cross-entity search

"We built a separate document widget for parties, another for products, another for filings — and now they all behave slightly differently."

Duplicated document UI

How Qubere addresses it

One link table. One component. One search page.

  • Any document can be linked to a shipment, party, product, license, or filing — not just the shipment it happened to arrive on.
  • Unlinking is never a delete — the link is marked inactive and the history stays, so nothing about "this used to be evidence for X" is lost.
  • Every entity detail page renders the same linked-documents panel, backed by the same API — no bespoke document UI per module.
  • The Documents workspace searches every document in the account by name, type, status, or which entity it's linked to — independent of any one shipment page — and now searches parsed document content, not just the file name.
  • A link can never be created against another tenant's record, or a record that doesn't exist — the target is verified before the link is written.

Documents workspace

Search every document in the account, filtered by what it's linked to.

Free-text search across parsed document content (not just the file name) plus shipment and client, with filters for document type, status, and "linked to" entity type. Every row shows how many entities already reference that document — so you can tell at a glance whether a file is single-purpose or shared evidence.

  • Gated on document.read; link and unlink additionally require document.update
  • Product and party master sheets are recognised on upload or email, with an Import link on the document row that opens the import with that file
  • Open a file straight from the table — no need to know which shipment it lives under first
How to demo
Collect › Trade Documents → "All documents" tab → filter "Linked to: PRODUCT" → open a document that's linked to more than one entity. "This is the same origin declaration the product record, the party record, and the filing all point back to — one file, three legitimate reasons to find it."
Documents
AC
Alice · Acme
FileTypeStatusShipmentLinked to
origin_declaration_88.pdfOrigin DeclarationverifiedSHP-0001443 entities
bol_scanned_0912.pdfBill of LadingOCR retrySHP-0001441 entity
manufacturer_affidavit_12.pdfAffidavitverified—2 entities

One link table · shared document panel

A document isn't owned by one record — it's linked to as many as apply.

A document-to-entity link records which entity, what kind of relationship (source document, supporting document, filing attachment, license evidence, origin evidence), who created it and when. The same panel renders on the party, product, and filing detail pages, and on the shipment workspace — one component, one API, no drift between them.

  • Unlink sets the link inactive and stamps who/when — the link history is never deleted
  • Pre-existing shipment-attached documents were migrated into this model, not left behind
How to demo
Open a product → scroll to Linked documents → link the same commercial invoice you just saw on the shipment. "It's the same file, now doing double duty as evidence for the product record too."
Products/Widget A400
AC
Alice · Acme
origin_declaration_88.pdfORIGIN_EVIDENCE · linked by priya@acme.com
manufacturer_affidavit_12.pdfSUPPORTING_DOCUMENT · linked by priya@acme.com
Also linked to
Shipment SHP-000144
Filing QBR-2026-3231761

Objection handling

Every hard question, answered directly.

"Can a document belong to more than one shipment?"Yes — and to a party, product, license, or filing at the same time. That's the point of the link layer: the document is the file; the links are the facts about what it's evidence for.
"If we unlink something by mistake, is it gone?"No. Unlinking marks the link inactive and records who did it and when; it never deletes the row. The history of "this was once evidence for X" survives.
"Does License get the same linked-documents panel?"Not yet — License has its own, older document mechanism, and wiring it into this shared panel is deliberately deferred pending a product decision on how the two should coexist.

The close

"One document. As many links as it actually has."

A single search surface across every document in the account, and a link layer that finally lets one file be evidence for a shipment, a party, a product, and a filing — all at once, all provable, none of it duplicated.

Next step: open the Documents workspace, filter by an entity type your team cares about, and follow one document to everything it's linked to.

Full detail: docs/apps/customs/sales/TRADE-REPOSITORY-AND-TRADE-DATA.md