Main site

Electronics AI agent · Battery shipping

Lithium Battery Shipping Evidence AI Agent

Marshal what one signature has to cover — the test summary behind each cell model, the packing instruction and charge state for each consignment — and leave the declaration to a named person.

Typical delivery
4–6 weeks
Deployment
Your stack
Named declarant
Evidence held
After launch
Agent Care

What this agent does

Builds the consignment file, not the declaration

In

  1. 01

    A consignment is tendered, and a person declares that all of the applicable air transport requirements have been met.

  2. 02

    A cell model changes, and a new summary is signed — 38.3.3 requires retesting on a defined design change.

Reason

  1. 03

    A test summary is signed under 38.3.5(j); 173.185(a)(3)(x) asks only for a name and title.

  2. 04

    A distributor holds it as well: 173.185(a)(3) binds each manufacturer and subsequent distributor.

  3. 05

    A cell shipped alone has no Section II — PI 965 and PI 968 lost it in March 2022.

Decide

  1. 06

    A small cell lost its air exception in the US on 10 April 2025, under HM-215Q.

  2. 07

    A pallet under PI 966 meets the thirty-per-cent charge cap from 1 January 2026; PI 967 only advises.

Out

  1. 08

    A damaged cell moves by highway, rail or vessel only, in a Packing Group I box under twelve-millimetre marks.

  2. 09

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

Product statement

The agent assembles the consignment file and keeps every summary, mark and measurement; a named person signs the test summary, signs the Declaration and tenders the goods.

Example workflow

One consignment, cell to signature

  1. 1Consignment raisedSales order, RMA return, sample shipment or an interplant stock transfer
  2. 2Cell evidence assembledTest summaries, model numbers, watt-hour ratings and the design-change history behind each
  3. 3Consignment file builtPacking instruction, section, charge state, marks, labels and the Declaration fields
  4. 4Controls appliedMode checks, packing-instruction checks, charge-state checks and completeness confidence

No human action required

Stages 1 to 4 run unaided, and nothing is declared or tendered at any of them — the agent is assembling, and the dangerous goods lane opens at the completeness gate.

5DecisionBranches at the completeness gate
File complete

Goes to the dangerous goods manager to sign.

Anything thin

Adds a regulatory counsel read first.

Dangerous goods review

The file is held with its packing instruction, its evidence and its gaps.

Sign the Declaration · Append evidence · Send to counsel

Signed — by a named person

  1. 6Shipping and ERP records updatedOnly where write access and disclosure policy allow it
  2. 7Outcome evaluatedPacking accuracy, evidence completeness, counsel corrections and what a later audit found

Corrections

Each counsel correction is counted in the evaluation.

What should not run autonomously

Human approval stays in control

Outside the boundary — human approval required

8 items

  • Signing the Declaration for a consignment.
    • Certifying that a cell meets the 38.3 criteria.
    • Signing a test summary for a cell model.
    • Tendering a consignment to any carrier.

  • Automation boundary

    Agent acts unaided

    • ✓Assemble the cell evidence and the design-change history behind it.
    • ✓Select the packing instruction and name the section it falls in.
    • ✓Check the charge state and hold both State approvals.
    • ✓Fill the Declaration fields and hold them for signature.

    No consignment is tendered except by a named person, inside the agreed boundaries.

    • Deciding a return is damaged or defective.
    • Assuming a State of Origin or Operator approval.
    • Deciding a non-conforming cell may move at all.
  • Changes to packing rules, marks or Declaration fields.

Example output

One consignment, annotated

The FAA case of 5 September 2025 turned on undeclared shipments, one of which had caught fire in its package.

Consignment file · single tender

Illustrative example
Consignment
Cells packed with equipment
Filed as
PI 966, Section I, by cargo aircraft
Charge state
Within the cap
Evidence of record
Signed summary, 4 August 2026
Confidence
Held untendered
Held for
The dangerous goods manager, in person

As received

Taken from the signed test summary and the charge-state record — nothing here is measured by the agent.

What the file holds

  • The signed test summary
  • Packing-instruction pick
  • A331 approvals

Why no signature here

172.204(d) names who may sign, and that signature is a personal one.

What the score decides

Below the configured threshold the file picks up a counsel read before.

Action

Sign the DeclarationAppend evidenceSend to counsel

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 consignment

From the shipping order

03Evidence

Where a return becomes

Our RMA triage agent settles the claim; 173.185(f) starts here, and a 173.185(d) recycling move belongs to our producer-registration agent.

01Approved path

One signature covers all of it

172.204(c) folds classification, packaging, marking, labelling and condition into one sentence, and A331 rides on the same form.

02Human review

What the June filing is not

DOT hazmat registration under 49 CFR 107.601 keys to placarding, and a Class 9 lithium consignment carries no domestic placard.

04

Build an evidence trail

The cell, the test summary behind it and the shipper who declared stay on the consignment.

Integrations

Typical integrations

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

  • Shipping and carrier

    • Carrier DG systems
    • air waybill
    • Freight forwarder portals

  • Cell and battery evidence

    • Test summaries
    • UN 38.3 reports
    • Design-change records

  • Order and inventory

    • ERP
    • WMS
    • Item master
    • packing data

Agent

Lithium battery shipping evidence

  • Reads the cell
  • Builds the file
  • Holds for the signer

  • Returns and RMA

    • RMA cases
    • return authorisations
    • Damage and defect flags

  • Observability & evaluation

    • OpenTelemetry
    • Langfuse
    • Supported monitoring/evaluation sources

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

Agent controls

Six filters between the model and the file

Six filters in series, and each is finer than the last. What survives is set out in the map below.

L6 · Outermost — last line of defence

Inward → L1 · closest to the model

L6Rollback / safe modePull the agent back to evidence assembly only when evaluation or production signals degrade.Roll back
L5Version monitoringTrack model, prompt, packing-rule and edition changes; the March 2026 power-bank rule is cabin-only.Track
L4TraceabilityRecord the summary, the packing instruction, the charge state, the marks and each read of the file.Record
L3Signer releaseHold the file for a named human; it governs signature, and not whether the cells may fly.Gate
L2Policy guardrailsTest the file against the packing instruction, the cap and both origin and operator approvals; HM-215R is only an NPRM.Restrict
L1Confidence thresholdsRoute a thin file to a counsel read before the dangerous goods manager sees it.Require review
Model coreFile assembled — the cells, the packing instruction, the charge state and completeness
L1 – L2
Test whether a file may stand
L3
Puts the signature in a person's hands
L4 – L5
Keep the consignment and the evidence behind it
L6
Holds the consignment at undeclared when signals degrade

How Nestack evaluates it

Evaluate the whole assembly — not only the file that comes out.

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

Surface — the file an inspector reads

  1. E1Final-output evaluationDid the file record the summary that stands behind the cell?
  2. E2Step-level evaluationDid the agent pick the right packing instruction, section and mode?
  3. E3Tool evaluationDid it read and write the correct consignment and the correct cell record?
  4. E4Confidence calibrationDo low-confidence files actually attract more counsel corrections?
  5. E5Slice evaluationHow does performance change across specific shipping lanes?
  6. E6Business outcomeHow many files needed a correction before the manager signed them?

Floor — the outcome the shipper answers for

Failure modes

Where each failure originates in the agent

Seven failure modes, each placed at the stage where it starts.

Agent lifecycle

Direction of processing →

  1. 01 · Retrieval

    1 mode

    • IF-03

      Cabin rule read as cargo

      A passenger cabin rule is applied to a cargo tender.

    Stage gathers

    The cells, the summaries, the packing rules and the marks

  2. 02 · Reasoning

    2 modes

    • IF-04

      Wrong section selected

      A Section II tender is built for cells shipped alone.

    • IF-06

      Domestic form sent abroad

      A summary with no signature travels internationally.

    Stage proposes

    The section, the charge state and completeness

  3. 03 · Tool / write

    2 modes

    • IF-02

      Charge state assumed

      The cap is met on a data sheet, not a measurement.

    • IF-05

      Return routed to air

      A defective cell is booked onto an aircraft.

    Stage writes

    Only where write access and approval policy allow it

  4. 04 · Output

    1 mode

    • IF-01

      Declared, evidence unheld

      The file shows a tender but not what stood behind it.

    Stage returns

    The Declaration a person signs and a carrier reads

  5. 05 · Change / Version

    1 mode

    • IF-07

      Silent edition regression

      The mark was renamed in 2025 and the file kept the old name.

    Stage tracks

    Model, prompt, packing rules and edition dates

  • Sev-1 · a consignment leaves undeclared
  • Sev-2 · a wrong packing instruction is used
  • Sev-3 · source degrades, file holds untendered
See the complete Electronics failure-mode catalogue

Affected slices

One lane absorbs the corrections

A lane-level packing-evidence figure can read clean while one lane absorbs most of the corrections. Nestack reports the counsel-correction rate by lane, not only in total.

Slice performance — reported separately, not only in aggregate

Illustrative example
SliceFailure rateLiftLift vs. thresholdStatus
Damaged and defective returns8.1%3.6×Review
Cells shipped alone by air5.9%2.6×Review
Batteries packed with equipment3.6%1.6×Watch
Batteries contained in equipment1.5%0.7×Normal

Bar: counsel-correction-rate lift vs. contained-in-equipment baseline · scale 0–4.0× · tick marks the 2.0× review threshold

2 of 4 slices over threshold

Evidence-linked improvement

What an unreconstructable file costs

A cycle ends when the wrong packing instruction is a standing case. That suite is what the next consignment built is measured against.

Improvement cycle · five stages

Switchback — the path turns at Improve and returns at Learn

  1. 01

    Detect

    Counsel-correction rate rises in one lane.

  2. 02

    Diagnose

    The pallet somebody tendered under a section that stopped existing in March 2022 is read back until one cause remains.

  3. 03

    Improve

    Changes leave numbered, and the consignments behind them travel attached.

  4. 04

    Verify

    A single failing consignment case is enough to stop the release.

  5. 05

    Learn

    The case is kept, and the packing rules are rewritten alongside it.

  6. Learn → Detect

    The return edge. The next consignment is measured against a suite 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, sources, file assembly, evaluation, integration, then production validation and handover.

Workstream

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

  1. 01Shipping-workflow discovery and boundary definition.Week 1
  2. 02ERP, RMA and test-summary sources.Week 1, Week 2
  3. 03Packing-instruction and charge-state rule mapping.Week 1, Week 2
  4. 04Cell evidence ingestion and normalisation.Week 2
  5. 05Design-change and summary binding.Week 2, Week 3
  6. 06Completeness scoring and counsel routing.Week 3
  7. 07Declaration signature workflow.Week 3, Week 4
  8. 08Shipping and ERP integration.Week 5
  9. 09Packing and charge-state cases.Week 4, Week 5
  10. 10Guardrails and declaration controls.Week 4
  11. 11Consignment-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 lane, one packing instructionProductionProduction shipping workflowAdvancedMultiple lanes / modes
Introduced at Pilot
File assembly to your rules✓✓✓
Named-signer declaration✓✓✓
Cell-evidence baseline✓✓✓
Introduced at Production
Reporting by lane—✓✓
Signature workflow in your systems—✓✓
Approved write-back—✓✓
Shipping-system integration—✓✓
Introduced at Advanced
Multi-mode transport rules——✓
Cross-lane evidence packs——✓
High consignment volume——✓
Multi-mode declaration controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build price
Confirmed after discovery based on integrations, workflow complexity, transaction 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 cell records and shipping data

    Cell evidence ingestion and model mapping

    Week 1

  2. 02Representative consignments and summaries

    File baseline, packing selection and evidence capture

    Week 2

  3. 03Your packing rules and shipping lanes

    Packing-instruction, charge-state and mode mapping and the automation boundary

    Week 1

  4. 04Access to relevant APIs, feeds or exports

    ERP, RMA and carrier-system assessment, then integration setup

    Week 2

  5. 05Consignments you would not want declared

    Packing cases and the evaluation suite

    Week 4

  6. 06What no declaration may cover

    Completeness scoring, counsel routing, guardrails and signature controls

    Week 3

  7. 07A named dangerous goods manager to sign

    Declaration signature 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

The bars are drawn to the weeks the work really takes, and that is why the fifth one carries two.

Phase

W1

W2

W3

W4

W5

W6

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

Week focus

W1Shipping workflow discovery, packing mapping and the automation boundary

W2Source integration and the cell-evidence baseline

W3File assembly, packing logic and signature controls

W4Evaluation suite, packing cases and failure-mode testing

W5Shipping integration, pilot consignments and targeted corrections

W6One shipping quarter run under the dangerous goods manager, then Agent Care handover

Reading the band
A bar covers only the weeks its own work is named in. The doubled fifth week is real work, not padding.
At the end of W6
When the consignment file validates, Agent Care picks the agent up.
Duration
Six-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.

Next step · Electronics AI agent

Build a battery shipping agent around the one signature that covers everything.

Show us how a consignment reaches the dock today and who signs the Declaration on the next one. That signature has to survive an inspection of a package that already burnt, read back against the packing instruction, the charge state and the marks on the box.

Typical delivery
4–6 weeks
Deployment
Your shipping systems
Named declarant
Evidence held
After launch
Agent Care available

Nestack Agents · lithium battery shipping evidence

AGT-EL-15 · Agent Care available after launch

Build a battery shipping agent

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

About you
Your shipments

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