← All case studies
Use caseA use-case guide for Chemicals & dangerous goods teams to apply to their own operation — not a specific customer story. The workflow and ContainerMath features shown are real; the figures illustrate what this use case typically targets rather than results measured from one account.
ApartIncompatible groups kept in separate containers
Every run
Segregation re-enforced on each recalculation
Grouped
Cargo tagged into keep-apart groups once
1 view
Segregation, weight and axle checks together
A use-case guide for chemical and dangerous-goods distributors: incompatible classes can't share a container, and checking a segregation table by hand on every revision is where mistakes creep in. This walks through building segregation into the load plan itself — assigning cargo to groups that must stay apart so the packing engine keeps them in separate containers automatically.
The challenge
A distributor shipping mixed chemical freight lives with a segregation table, a spreadsheet and a lot of care. The rules are unforgiving — some classes can share a container with separation, some can't share one at all — and every quantity change or new line item means re-running the check by hand. Under time pressure the manual step gets skipped, the segregation lives in a different document from the stuffing plan, and nothing enforces that the plan honors the check. One missed pair is a rejected booking or worse. This guide shows how to make the separation part of the plan instead of a review after it.
Before vs. after
Before — manual & Excel
Checked by hand, after the fact
- 1
Check the table by hand
Every mixed load was cross-checked against a printed segregation table manually — accurate when done carefully, skipped when rushed.
- 2
Re-run it on every change
A new SKU or a changed quantity invalidated the check, so the whole table had to be worked again — the step most likely to be dropped.
- 3
Keep the plan and the check apart
Segregation lived in one document and the stuffing plan in another, with nothing guaranteeing the plan actually honored the check.
- 4
Catch a missed pair late
An overlooked class pairing surfaced at booking or the terminal, not during planning — the most expensive place to find it.
- 5
Review hazards separately from weight
Segregation, payload and axle checks were done in different places, so no single view confirmed the load was compliant end to end.
After — ContainerMath
Planned in, enforced every run
- 1
Tag cargo into keep-apart groups
Incompatible cargo is assigned to segregation groups once, describing which goods must never share a container.
- 2
Let the engine keep them apart
The packing engine keeps those groups in separate containers automatically as it builds the plan — no manual placement.
- 3
Re-enforce on every recalculation
Change a quantity or add a SKU and the segregation is applied again on the next run, so it can't quietly fall out of date.
- 4
See a stow that already complies
The 3D plan reflects a load that respects the rule from the start, rather than one flagged for rework in a later review.
- 5
Review everything in one place
Segregation advisories sit alongside the weight, payload and per-axle checks, so the whole load is confirmed in a single view.
Inside ContainerMath: the parts they used
Plan-level segregation rules
Assign cargo to groups that must not mix; the packing engine keeps them in separate containers when they can't share one.
Consignment grouping
Keep items that must travel together — same shipment, PO or AWB — in the same container, the complement to keeping others apart.
Compliance & advisories
Segregation and balance findings surface next to hard axle-weight compliance checks, so nothing is reviewed in isolation.
Volume + weight tracking
CBM and payload are tracked together, so a segregated plan is still checked for fill and weight in the same pass.
My Load Plans & PDF export
Repeat lanes reload a saved, segregation-correct plan, exported as a PDF the warehouse and carrier can act on.
The results
- Incompatible cargo is kept in separate containers automatically instead of checked against a table by hand.
- Segregation is re-applied on every recalculation, so a change can't leave it out of date.
- The stow reflects the rule from the start rather than being flagged for rework in a later review.
- Segregation, weight and axle checks are reviewed together in one plan.
Plan your next container in minutes
Stop guessing in spreadsheets. Build a 3D load plan with live CBM and payload.
Try ContainerMath free →More case studies & use cases