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.
A consignment is tendered, and a person declares that all of the applicable air transport requirements have been met.
02
A cell model changes, and a new summary is signed — 38.3.3 requires retesting on a defined design change.
Reason
03
A test summary is signed under 38.3.5(j); 173.185(a)(3)(x) asks only for a name and title.
04
A distributor holds it as well: 173.185(a)(3) binds each manufacturer and subsequent distributor.
05
A cell shipped alone has no Section II — PI 965 and PI 968 lost it in March 2022.
Decide
06
A small cell lost its air exception in the US on 10 April 2025, under HM-215Q.
07
A pallet under PI 966 meets the thirty-per-cent charge cap from 1 January 2026; PI 967 only advises.
Out
08
A damaged cell moves by highway, rail or vessel only, in a Packing Group I box under twelve-millimetre marks.
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
AgentHuman
1Consignment raisedSales order, RMA return, sample shipment or an interplant stock transfer
2Cell evidence assembledTest summaries, model numbers, watt-hour ratings and the design-change history behind each
3Consignment file builtPacking instruction, section, charge state, marks, labels and the Declaration fields
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▼
6Shipping and ERP records updatedOnly where write access and disclosure policy allow it
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 required8 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 boundaryAgent 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 tenderIllustrative example
Consignment
Filed as
Charge state
Evidence of record
Confidence
Held for
Cells packed with equipment
PI 966, Section I, by cargo aircraft
Within the cap
Signed summary, 4 August 2026
Held untendered
The dangerous goods manager, in person
As receivedTaken from the signed test summary and the charge-state record — nothing here is measured by the agent.
What the file holdsThe signed test summaryPacking-instruction pickA331 approvals
Why no signature here172.204(d) names who may sign, and that signature is a personal one.
ActionSign the DeclarationAppend evidenceSend to counsel
What the score decidesBelow the configured threshold the file picks up a counsel read before.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every consignmentFrom 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.
04Build 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 carrierCarrier DG systems · air waybill Freight forwarder portals
Cell and battery evidenceTest summaries · UN 38.3 reports Design-change records
Order and inventoryERP · WMS Item master · packing data
Agent
Lithium battery shipping evidence
Reads the cell Builds the file Holds for the signer
Returns and RMARMA cases · return authorisations Damage and defect flags
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 aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Damaged and defective returns
8.1%
3.6×
Review
Cells shipped alone by air
5.9%
2.6×
Review
Batteries packed with equipment
3.6%
1.6×
Watch
Batteries contained in equipment
1.5%
0.7×
Normal
Bar: counsel-correction-rate lift vs. contained-in-equipment baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 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 stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Counsel-correction rate rises in one lane.
02Diagnose
The pallet somebody tendered under a section that stopped existing in March 2022 is read back until one cause remains.
03Improve
Changes leave numbered, and the consignments behind them travel attached.
04Verify
A single failing consignment case is enough to stop the release.
05Learn
The case is kept, and the packing rules are rewritten alongside it.
Learn → DetectThe 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.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Shipping-workflow discovery and boundary definition.
02ERP, RMA and test-summary sources.
03Packing-instruction and charge-state rule mapping.
04Cell evidence ingestion and normalisation.
05Design-change and summary binding.
06Completeness scoring and counsel routing.
07Declaration signature workflow.
08Shipping and ERP integration.
09Packing and charge-state cases.
10Guardrails and declaration controls.
11Consignment-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal 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 priceConfirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.
Separate from buildBuild 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.
You bringWe build with it
01Your cell records and shipping data→Cell evidence ingestion and model mappingWeek 1
02Representative consignments and summaries→File baseline, packing selection and evidence captureWeek 2
03Your packing rules and shipping lanes→Packing-instruction, charge-state and mode mapping and the automation boundaryWeek 1
04Access to relevant APIs, feeds or exports→ERP, RMA and carrier-system assessment, then integration setupWeek 2
05Consignments you would not want declared→Packing cases and the evaluation suiteWeek 4
06What no declaration may cover→Completeness scoring, counsel routing, guardrails and signature controlsWeek 3
07A named dangerous goods manager to sign→Declaration signature workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, 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.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Shipping workflow discovery, packing mapping and the automation boundaryW2Source integration and the cell-evidence baselineW3File assembly, packing logic and signature controlsW4Evaluation suite, packing cases and failure-mode testingW5Shipping integration, pilot consignments and targeted correctionsW6One shipping quarter run under the dangerous goods manager, then Agent Care handover
Reading the bandA bar covers only the weeks its own work is named in. The doubled fifth week is real work, not padding.
At the end of W6When the consignment file validates, Agent Care picks the agent up.
DurationSix-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.
