Main site

Transportation AI agent · Customs documentation

Customs-Documentation AI Agent

Gather the entry data set from your shipping documents, carry each field with the source it came from, and hand the prepared package to a licensed customs broker, who decides and files.

Typical delivery
4–6 weeks
Deployment
Your stack
Broker files
Six-digit cap
After launch
Agent Care

What this agent does

Assembles the entry data, never the entry

In

  1. 01

    Ingesting commercial invoices, packing lists and transport documents from supported forwarding, ERP or capture sources.

  2. 02

    Normalising field labels and units, and carrying each value forward with the document it was read from.

Reason

  1. 03

    Assembling the entry data set a licensed broker needs, field by field, against the documents on file.

  2. 04

    Applying the importer's product library, part numbers and prior broker decisions as context.

  3. 05

    Testing each invoice against the statutory elements and marking what the document leaves absent.

Decide

  1. 06

    Flagging any field that would decide what appears on an actual entry, and capping candidates at six digits.

  2. 07

    Routing the prepared package to the licensed customs broker for the decision and the filing.

Out

  1. 08

    Retaining the source documents, the assembled fields and the broker's decisions for the retention period.

  2. 09

    Executing write actions only inside the approval boundaries agreed during implementation.

Product statement

The agent prepares and organises; a licensed customs broker decides and files, and the software holds no customs standing of its own.

Example workflow

One entry, documents to filing

  1. 1Documents receivedCommercial invoice, packing list, transport document or forwarder file
  2. 2Fields assembledDescription, quantity, price, charges and stated origin, each with its named source
  3. 3Package preparedEntry data set, gaps, flags and confidence
  4. 4Controls appliedCompleteness checks against the statutory invoice elements, the six-digit cap, held-act checks and confidence threshold

No human action required

Stages 1 to 4 run unaided, and nothing reaches CBP at any of them — the agent is assembling, and the broker's lane opens at the confidence gate.

5DecisionBranches at the confidence threshold
High confidence

Goes to the licensed broker to decide.

Low confidence

Adds a trade-compliance read first.

Licensed broker review

The package is held with its source documents, its open questions and the confidence.

Approve · Correct · Send to compliance review

Approved — the broker files

  1. 6Broker and importer systems updatedOnly where write access and approval policy allow it
  2. 7Outcome evaluatedBroker corrections, field-level errors, CBP requests and post-entry amendments

Corrections

Every broker correction is counted in the evaluation.

What should not run autonomously

Human approval stays in control

Outside the boundary — human approval required

8 items

  • Filing an entry, an entry summary or any CBP form.
    • Deciding the classification of goods being imported.
    • Deciding country of origin for an actual shipment.
    • Appraising value or deciding a duty question.

  • Automation boundary

    Agent acts unaided

    • ✓Gather and organise the entry data set from the documents.
    • ✓Carry each field forward with the document it was read from.
    • ✓Test each invoice against the elements 19 CFR 141.86 requires.
    • ✓Hold whatever would decide what appears on an actual entry.

    Any write happens inside the boundaries agreed at implementation, never ahead of the broker.

    • Executing a power of attorney with an importer.
    • Writing, amending or reissuing a bill of lading.
    • Supplying an invoice field the document leaves blank.
  • Changes to classification, origin or scope rules.

Example output

One entry line, annotated

Everything the agent assembles is attached to the document it was read from.

Entry-preparation output · single line

Illustrative example
Shipment
Consumption entry
Goods description
Stainless-steel vacuum flasks, 500 ml, packed 24 per carton
Invoice price
$18,400.00
Classification
Six-digit candidate
Confidence
88%
Origin
Supplier's assertion, unverified

As received

Taken from the commercial invoice and the packing list — nothing on this side is written by the agent.

Source documents used

  • Commercial invoice
  • Packing list
  • Transport document

Why it stops here

It is specific to a shipment actually being imported and a person still decides.

What the score decides

Below the configured threshold the package picks up a compliance read before it.

Action

ApproveCorrectSend to compliance review

Value

Where AI adds value

The same four claims, placed at the point in the workflow where each one applies.

Where the value lands

Value 01 – 04

Every entry

From the shipping documents

03Preparation

Assemble from the documents

Draw on the documents on file, the importer's product library and prior broker decisions, inside the broker's own operation.

01Approved path

Prepare it, a broker files it

Routine entry data arrives assembled, sourced and checked for gaps.

02Human review

Hand the rest to the broker

Reasonable care stays with the importer of record — the retained record set is the evidence of it, and what a prior disclosure is built from.

04

Build an evidence trail

The entry data, the classification basis behind it and the licensed broker who filed it stay together.

Integrations

Typical integrations

Five system groups connect to the same agent. Which of them are in scope is decided in discovery.

  • Forwarding and customs systems

    • CargoWise
    • Descartes
    • Magaya
    • e2open

  • Filing platforms

    • ABI / ACE filing software
    • Broker portals
    • service bureaux

  • Importer systems

    • SAP
    • Oracle
    • NetSuite
    • Product and part masters

Agent

Customs documentation

  • Reads the documents
  • Assembles the entry data
  • Holds for the broker

  • Documents and records

    • Email
    • document capture
    • Record archives
    • retention sets

  • Observability & evaluation

    • OpenTelemetry
    • Langfuse
    • Supported monitoring/evaluation sources

Integration availability depends on the client's existing systems and API access.

Agent controls

Six layers between the model and the entry

Controls stack inward. What the stack does not catch is set out in the map below.

L6 · Outermost — last line of defence

Inward → L1 · closest to the model

L6Rollback / safe modeNarrow the agent to data assembly when evaluation or production signals degrade.Roll back
L5Version monitoringTrack model, prompt, rule and classification-scope changes.Track
L4TraceabilityRecord the source documents, the assembled fields, the flags and the broker's decision.Record
L3Broker reviewHold the package for a named licensed broker; the hold governs release, not whether the filing is right.Gate
L2Scope guardrailsTest outputs against the six-digit cap and the held-act list; a failure returns the package. A notice on screen is not tested; the cap is.Restrict
L1Confidence thresholdsRoute low-confidence packages to a compliance read before the broker sees them.Require review
Model corePackage prepared — entry data set, open gaps, flagged fields and confidence
L1 – L2
Test whether a package may stand
L3
Puts the filing in a broker's hands
L4 – L5
Keep the entry data and the basis behind it
L6
Narrows to data assembly when signals degrade

How Nestack evaluates it

Evaluate the preparation workflow — not only the fields handed over.

Coverage runs the whole depth of the workflow, and every layer is cut by slice.

Surface — the data the broker files from

  1. E1Final-output evaluationDid every assembled field match the document it was read from?
  2. E2Step-level evaluationDid the agent use the right documents, product library and prior decisions?
  3. E3Tool evaluationDid it read and write the correct entry and the correct field?
  4. E4Confidence calibrationDo low-confidence packages actually attract more broker corrections?
  5. E5Slice evaluationHow does performance change across specific shipment types?
  6. E6Business outcomeHow many packages needed a broker correction or a post-entry amendment?

Floor — the entry the importer answers for

Failure modes

Where each failure originates in the agent

Seven ways a package goes wrong, placed by stage.

Agent lifecycle

Direction of processing →

  1. 01 · Retrieval

    1 mode

    • AJ-03

      Superseded document read

      A field is taken from an invoice that was later replaced.

    Stage gathers

    Invoice, packing list, transport document and product library

  2. 02 · Reasoning

    2 modes

    • AJ-04

      Candidate past the cap

      A candidate is extended past six digits for goods being imported.

    • AJ-06

      Assertion carried as fact

      A supplier's stated origin is passed on as though it were determined.

    Stage proposes

    Entry data set, six-digit candidates and confidence

  3. 03 · Tool / write

    2 modes

    • AJ-02

      Package released early

      A package moves on with held fields still unresolved.

    • AJ-05

      Duplicate entry data set

      The same shipment is assembled and handed over twice.

    Stage writes

    Only where write access and approval policy allow it

  4. 04 · Output

    1 mode

    • AJ-01

      Missing statutory element

      A required invoice element is absent and not flagged.

    Stage returns

    The entry data set the broker files from

  5. 05 · Change / Version

    1 mode

    • AJ-07

      Silent scope regression

      A model or rule change widens what the agent will assert.

    Stage tracks

    Model, prompt, scope rules and product-library config

  • Sev-1 · acts outside the boundary
  • Sev-2 · a wrong field reaches the broker
  • Sev-3 · source degrades, package routes to review
See the complete Transportation failure-mode catalogue

Affected slices

Overall accuracy can hide one bad cohort

Break the correction rate down by cohort before you trust it — a headline that reads acceptably is usually a few shipment types absorbing most of the rework. Nestack reports it by slice, not only in total.

Slice performance — reported separately, not only in aggregate

Illustrative example
SliceFailure rateLiftLift vs. thresholdStatus
Section 232 derivative lists9.2%3.9×Review
Mixed-material assemblies6.1%2.6×Review
New supplier, first shipment4.2%1.8×Watch
Repeat parts, product library1.4%0.6×Normal

Bar: broker-correction-rate lift vs. repeat-part baseline · scale 0–4.0× · tick marks the 2.0× review threshold

2 of 4 slices over threshold

Evidence-linked improvement

A cycle ends in a case, not a note

An apology does not close a cycle; a case the next release must pass does. That suite is what the next entry prepared for filing is measured against.

Improvement cycle · five stages

Switchback — the path turns at Improve and returns at Learn

  1. 01

    Detect

    Broker-correction rate rises in a shipment slice.

  2. 02

    Diagnose

    The prepared packages and the documents behind them are read side by side until the cause narrows to one.

  3. 03

    Improve

    The correction is versioned, with the entries that motivated it attached.

  4. 04

    Verify

    A failing case holds the release until it passes.

  5. 05

    Learn

    The case is added permanently, and the classification notes move with it.

  6. Learn → Detect

    The return edge. The suite the next package meets is one case longer.

Typical build scope

Twelve workstreams across six weeks

The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, documents, preparation workflow, evaluation, integration, then production validation and handover.

Workstream

Week 1Week 2Week 3Week 4Week 5Week 6

  1. 01Entry workflow discovery and boundary definition with your broker.Week 1
  2. 02Document and system assessment.Week 1, Week 2
  3. 03Product library, prior decisions and held-act mapping.Week 1, Week 2
  4. 04Document ingestion and normalisation.Week 2
  5. 05Assembly logic and source binding.Week 2, Week 3
  6. 06Confidence scoring and gap routing.Week 3
  7. 07Licensed broker review workflow.Week 3, Week 4
  8. 08Customs-platform and record integration.Week 5
  9. 09Classification and origin cases.Week 4, Week 5
  10. 10Guardrails and filing controls.Week 4
  11. 11Entry-trail instrumentation.Week 5, Week 6
  12. 12Deployment, documentation and Agent Care handover.Week 6

12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel

Final scope and sequence confirmed in discovery

Engagement tiers

What each tier includes

Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.

Capability✓ in scope · — not at this tierPilotOne importer, one brokerProductionProduction customs systemsAdvancedMultiple entities / countries
Introduced at Pilot
Preparation to your documents and rules✓✓✓
Licensed broker review✓✓✓
Preparation-accuracy baseline✓✓✓
Introduced at Production
Reporting by tariff chapter—✓✓
Broker review workflow in your systems—✓✓
Approved write-back—✓✓
Customs-platform integration—✓✓
Introduced at Advanced
Multi-programme duty rules——✓
Multi-stage compliance approvals——✓
High entry volume——✓
Multi-country entry controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build price
Confirmed after discovery based on integrations, workflow complexity, entry volume, approval controls and deployment requirements.
Separate from build
Build pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.

What we need from you

What you bring, and what we build with it

Each input maps to a piece of build scope and a week in the delivery timeline.

  1. 01Your document set and the fields your broker needs

    Document ingestion and field mapping

    Week 1

  2. 02Representative filed entries

    Preparation baseline, product-library extraction and source binding

    Week 2

  3. 03Your product library and prior broker decisions

    Product library, prior decisions and held-act mapping

    Week 1

  4. 04Access to relevant APIs, feeds or exports

    Document and system assessment, then integration setup

    Week 2

  5. 05Entries you would not want filed

    Classification cases and the evaluation suite

    Week 4

  6. 06What only a licensed broker may do

    Confidence scoring, gap routing, guardrails and filing controls

    Week 3

  7. 07Named licensed brokers to review packages

    Broker review workflow, then pilot and production validation

    Weeks 5–6

Nothing else is required

Deployment, documentation and Agent Care handover are ours.

Delivery timeline

Four phases across six weeks

Each band covers the weeks the work really takes, so week 5 carries evaluation and launch together.

Phase

W1

W2

W3

W4

W5

W6

  1. DiscoveryW1
  2. BuildW2 – W3
  3. EvaluateW4 – W5
  4. Pilot & LaunchW5 – W6

Week focus

W1Entry workflow discovery, held-act mapping and the automation boundary

W2Document integration and the preparation baseline

W3Preparation workflow, confidence logic and broker review controls

W4Evaluation suite, scope guardrails and failure-mode testing

W5Customs-platform integration, pilot entries and targeted corrections

W6One entry cycle prepared under the licensed broker, then handover

Reading the band
A bar spans only the weeks its work is named in. Week 5 carries two because that is how the work runs.
At the end of W6
Validation finishes on live entries and Agent Care assumes monitoring.
Duration
Six-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.

Next step · Transportation AI agent

Build a customs-documentation agent around your broker's filing chain.

Show us your documents, your product library and your filing chain. A licensed customs broker signs the entry, and nothing here moves that. We'll map the preparation workflow and set the boundary.

Typical delivery
4–6 weeks
Deployment
Your customs stack
Broker files
Six-digit cap
After launch
Agent Care available

Nestack Agents · Customs documentation

AGT-TR-04 · Agent Care available after launch

Build a customs-documentation agent

Four questions so the call starts from your actual setup — then pick a time that suits you.

About you
Your entries

No obligation. We’ll map the workflow, name the automation boundary and tell you if an agent is the wrong answer.