Transportation & Logistics

Trade Compliance Copilot

Designed for Compliance specialist

Let the trade compliance specialist classify goods, validate restricted-party and licensing exposure, and assemble a defensible customs declaration file where every HS code, duty rate and exemption is traceable to a binding ruling, tariff schedule note or explanatory note.

Contract TRA-03 · primary aggregate CustomsDeclaration · mode loading

Decision brief

Restricted-party and license screening: evidence ready for review

This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.

Decision signals

The evidence and control points that shape this recommendation.

Decision owner

Screening service with specialist review

The named role remains accountable for the consequential decision.

Governed evidence

6 record types

Structured records and cited text ground the recommendation.

Workflow

5 controlled stages

Each transition records its input, output, status, and audit context.

Human controls

2 approval gates

Approval gates prevent the copilot from making consequential decisions.

Business problem

An importer files a declaration covering 14 lines of lithium-ion battery modules assembled in Vietnam from Chinese cells.

Decision to make

Let the trade compliance specialist classify goods, validate restricted-party and licensing exposure, and assemble a defensible customs declaration file where every HS code, duty rate and exemption is traceable to a binding ruling, tariff schedule note or explanatory note.

Outcome to show

filedDeclaration gives Compliance specialist the evidence needed to begin the final governed business outcome, with the decision trail retained for review.

  1. 1Commercial document extraction
  2. 2Candidate heading retrieval
  3. 3Ruling and rule-of-origin grounding
  4. 4Restricted-party and license screening
  5. 5Specialist sign-off and broker filing

Step 1 of 5

Ready: Start with the business question, then use the single button above.

The output appears here immediately. More technical evidence remains available below.

System logic, GenAI, and human accountability

The demonstration keeps deterministic controls, AI assistance, and approval separate.

System logic

Source systems enforce identity, workflow order, policy filters, and record updates.

GenAI contribution

Retrieval and generation assemble relevant evidence into a cited recommendation or draft.

Human accountability

Screening service with specialist review verifies material claims and approves the consequential action.

Workflow stages

Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.

Seeded record
Loading
Document type
Loading
Container
Loading
Partition key
Loading
Current stage
Loading

API demonstration guidance

Run a stage to see its explanation, evidence, full request, and full response.

Grounded chat

Ask a question and receive an answer grounded in retrieved CustomsDeclaration evidence.

Answer and evidence

Select a starter question or enter your own.

Evidence

Domain implementation workspace

Loaded live from /api/config, /api/domain/model, and /api/domain/sample.

Domain objective
Let the trade compliance specialist classify goods, validate restricted-party and licensing exposure, and assemble a defensible customs declaration file where every HS code, duty rate and exemption is traceable to a binding ruling, tariff schedule note or explanatory note.
Primary aggregate
CustomsDeclaration
Primary container
customsDeclarations
Hierarchical key
/tenantId + /declarationId
Schema version
1

Sample scenario

An importer files a declaration covering 14 lines of lithium-ion battery modules assembled in Vietnam from Chinese cells. The copilot proposes heading 8507.60 for twelve lines, flags two lines as contested because the modules include an integrated battery management board, and cites the chapter 85 note plus a 2023 binding ruling on comparable BMS-integrated packs. Separately, a consignee screening run returns a 0.87 fuzzy match against a denied-persons entry. The specialist clears the match as a false positive with a recorded rationale, accepts the 8507.60 opinion for twelve lines, reclassifies the two contested lines after reading the cited ruling, and signs the declaration for broker filing.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
customsDeclarations Primary /tenantId + /declarationId Declaration, LineItem, ScreeningResult, ClassificationOpinion
tariffScheduleCatalog Reference /tenantId + /hsChapter TariffRuleChunk
customsRulingIndex Reference /tenantId + /rulingId BindingRulingChunk

Document types

Contract document types, their owning container, and their identifier pattern.
Type Container Partition key Identifier pattern Embedding fields
Declaration customsDeclarations /tenantId + /declarationId declaration::{declarationId} None
LineItem customsDeclarations /tenantId + /declarationId declaration::{declarationId}::line::{lineNumber} descriptionVector
TariffRuleChunk tariffScheduleCatalog /tenantId + /hsChapter tariff::{hsChapter}::{ruleDocId}::{chunkOrdinal} chunkVector
BindingRulingChunk customsRulingIndex /tenantId + /rulingId ruling::{rulingId}::{chunkOrdinal} chunkVector
ScreeningResult customsDeclarations /tenantId + /declarationId declaration::{declarationId}::screening::{partyRole}::{screeningRunId} None
ClassificationOpinion customsDeclarations /tenantId + /declarationId declaration::{declarationId}::opinion::{opinionId} rationaleVector

Query patterns