Configuring Lithium Battery DG Rules in Your TMS

Configure UN 3481 lithium battery rules and state-of-charge validation in your TMS for IATA DGR 67 compliance, step by step, with a test plan.

Share

If your TMS still prints "DGR 66th Edition" on a Shipper's Declaration, your next UN 3481 shipment is one acceptance desk away from a rejection. The IATA DGR 67th Edition went into effect January 1, 2026, and the 30% state-of-charge ceiling for lithium-ion batteries packed with equipment stopped being a best practice and became a hard rule. This walkthrough is for teams whose TMS already has dangerous goods fields live, not for people shopping for new hazmat software. We're going to touch specific fields, write one validation rule, and test it before it touches a live shipment.

Why this config can't wait until your next DG audit

Because airlines are already enforcing it, and "we didn't know" isn't a defense anyone wants to test at a ramp. The 30% state of charge limit that was a recommendation in the 66th Edition is now a hard requirement for two UN numbers: UN 3481 (lithium-ion batteries packed with equipment, cells or batteries over 2.7 Wh) and UN 3556 (lithium-ion battery-powered vehicles, batteries over 100 Wh). Want to exceed that threshold? You need written approval from the state of origin and the operator's state, meaning permits, not a checkbox override in your TMS.

There's a second change that's easy to miss if your product catalog includes demo vehicles or hybrid equipment. The 67th Edition added two entries for UN 3166 covering hybrid vehicles powered by flammable liquid, so operators can properly weigh the risk of equipment carrying both an engine and a traction battery. If you ship forklifts, generators, or demo units with hybrid drivetrains, this affects your dangerous goods list mapping too.

IATA isn't being quiet about enforcement either. Compliance with the revised requirements in the 67th Edition DGR is mandatory as of January 1, 2026. That's not a grace period. That's today's rule.

Before you start: what you need

Four things, gathered before you open your TMS admin console, or you'll be configuring blind and redoing work next week.

  • Current product master data with Wh rating or state-of-charge spec for every battery-containing SKU. If your PLM or ERP doesn't carry this field today, you're not configuring a TMS rule, you're doing a data project first.
  • Admin or configuration access to your TMS's dangerous goods or hazmat module, with rights to edit validation rules, not just view them.
  • A sandbox or staging environment separate from production. You will intentionally submit a non-compliant shipment during testing, and you don't want that touching a live carrier API.
  • A current copy of DGR 67 Addendum 1 or your carriers' hazmat variation list. IATA releases addenda through the year; the first one for 2026 corrected regulatory references and amended marking rules for sodium-ion batteries under UN 3551, so don't assume the edition you installed in January is still complete in November.

The configuration steps

Seven steps, in order. Skipping the shadow-test step at the end is the single most common reason teams discover a gap after go-live instead of before it.

  1. Audit your product master for battery-containing SKUs. Tag every one with its UN number and packing group. This is tedious but it's the foundation everything else sits on. If a SKU has a cell or battery exceeding 2.7 Wh and ships packed with equipment, it's UN 3481. If it's a battery-powered vehicle over 100 Wh, it's UN 3556.
  2. Add a mandatory state-of-charge field to the DG data entry screen for any item classified under UN 3481 or UN 3556. Don't make this optional or default-populated. If your TMS supports conditional required fields (visible only when UN number equals 3481 or 3556), use that logic so the field doesn't clutter screens for non-battery SKUs.
  3. Build a validation rule that blocks tender when SOC exceeds 30%. This needs to be a hard stop, not a warning banner someone can click through. The primary threshold is that the battery's SoC must not exceed 30% of its rated capacity, or for batteries contained in equipment, the device must display a charge level of 25% or less. Code both conditions if your SKUs include devices with visible charge displays, since either one satisfies the rule.
  4. Map carrier-specific operator variations into your routing and service rules. Not every airline enforces identically. For 2026, IATA itself re-phrased some of the most common operator variations to make the language consistent from carrier to carrier, which helps, but you still need to confirm your carrier mix hasn't layered on anything stricter in its own variation list.
  5. Rebuild your DG label and Shipper's Declaration template to cite the 67th Edition instead of the 66th. The exact wording matters here. The statement "State of Charge not more than 30%, or not more than 25% displayed" must be explicitly declared in the Handling Information box (Field 18) of the Shipper's Declaration for Dangerous Goods. If your template hardcodes "66th Edition" anywhere, including in a footer, fix it now.
  6. Add the two new UN 3166 hybrid vehicle entries if you ship vehicles or demo units with dual power sources. These are advisory shipping names, so add them to your dangerous goods list as "Vehicle, flammable gas powered, hybrid" and "Vehicle, flammable liquid powered, hybrid," matching how your carriers have coded their own IMP fields.
  7. Run a shadow shipment through staging with an intentionally over-threshold SOC value, say 45%, to confirm the block fires correctly before this goes anywhere near production. This is the step teams skip when they're in a hurry. Don't skip it.

If your TMS doesn't have native DG fields at all, you're looking at a bolt-on rather than a configuration change. SAP TM's hazmat rule engine and Oracle OTM both support hazardous item classification natively, though OTM requires creating a hazardous item tied to a packaged item, with the hazardous classification varying by transport mode and region. Teams running lighter platforms often layer in Labelmaster's DGIS, which pre-populates Dangerous Goods declaration fields once you type in the UN number, and integrates with the WMS, TMS, or ERP platforms teams already run. Descartes DG Office covers similar ground for multi-mode shippers. For shippers who want the DG entry built into the TMS itself rather than bolted on, Cargoson's dangerous goods entry uses UN number autocomplete to pull proper shipping names, hazard classes, and packing groups automatically, then generates the compliant declaration from that same record.

How you know it worked

Three checks, and all three need to pass, not just one. First, a test shipment with SOC above 30% gets blocked pre-tender with a clear exception message naming the field and the limit, not a generic "validation failed" error. Second, a compliant shipment generates a DG label and Shipper's Declaration that explicitly cites "67th Edition" and carries the SOC statement in Field 18. Third, if you're sending EDI or API payloads to a carrier, the hazmat segment in that payload reflects the correct SOC value and UN number, not a cached value from before you made the change.

Run all three checks on the same test shipment where possible. A rule that blocks correctly in the UI but still lets a bad payload through to the carrier API is a rule that only half works.

Failure mode: the label passes validation but gets rejected at the dock

This is the failure mode nobody budgets time for, because it looks like success right up until the carrier rejects it. Your validation rule fires correctly. SOC is under 30%. The shipment tenders fine. Then the printed Shipper's Declaration still references old edition language, or cites an operator variation that carrier updated for 2026, and the shipment gets bounced at acceptance.

IATA has actually flagged this exact pattern as a problem on its own side. IATA is concerned about the perception among air carriers that the Dangerous Goods Declaration form presented by shippers must be identical to the example shown in the Dangerous Goods Regulations, and has pushed back on rejections over formatting that doesn't affect safety. That's reassuring in theory. In practice, you still lose a day of transit time arguing it, and your warehouse team is the one fielding the angry call from the carrier's ramp agent.

The fix isn't complicated, it's just a habit you have to build. Version-control your DG document templates the same way you'd version-control a routing guide. Re-test the template, not just the validation rule, after every annual DGR edition update. And put a monthly spot-check into your DG SOP: pull five recent Shipper's Declarations at random and confirm the edition reference, the SOC statement wording, and the operator variation language all match what's current. Thirty minutes a month beats a rejected pallet sitting on a tarmac.

Keep this on your annual calendar

The DGR isn't a one-and-done update. The DGR is updated annually and all revised requirements take effect on January 1 of each new year, which means this whole exercise repeats, just with different fields next time. IATA already gives you a preview: the significant changes document includes a summary of Appendix H of the 2026 DGR, detailing changes planned for the next edition taking effect January 1, 2027. Pull that appendix now and start a running list of what your config will need to handle in roughly six weeks.

Copy this into your DG SOP before you close this out:

  • Confirm UN 3481 and UN 3556 SKUs are tagged in product master with current Wh ratings
  • Confirm the SOC field is mandatory and the 30% block is a hard stop, tested in staging
  • Confirm the DG label and Shipper's Declaration template cites the current DGR edition
  • Confirm carrier operator variations are mapped for every carrier in your routing table
  • Schedule a monthly five-declaration spot-check
  • Pull Appendix H from the current DGR edition and flag changes for next January

None of this is glamorous work. It's also the difference between a shipment that clears acceptance and one that sits on a dock while someone argues edition numbers with a ramp agent.