NMFC Freight Class Classification Checking
LTL shipments are priced against an NMFC freight class that depends on density, handling difficulty, stowability and liability, not just what the product is, and getting it wrong doesn't just misprice the shipment, it triggers a carrier reclassification and reweigh after pickup that adds a surprise charge and a dispute nobody planned for. Shippers with a wide product mix, or new SKUs added regularly, often default to whatever class a similar product used last time rather than recalculating density and class per shipment, and the carrier's own reclass process, which they run for revenue reasons as much as accuracy, catches every one of those shortcuts eventually.
STARTING PRICE
From €99
Starter tier · Single-workflow automation, one core integration, fast turnaround.
Get a quote →Saves roughly 2-4 hrs/week for a shipping coordinator, plus avoided reclass fees.
How the automation works
We calculate the correct NMFC freight class for each LTL shipment from its actual dimensions and weight at time of booking, cross-checked against the product's NMFC item number and any density-based class breaks that apply, rather than reusing a class from a similar past shipment. Shipments where the class is genuinely borderline between two density tiers are flagged for a quick manual check before the BOL is generated, since a wrong class in either direction either overpays or invites a reclass. The goal is a class that matches what the carrier will calculate on their own reweigh, so there's no gap for a reclass charge to fill.
Process flow
- 01
LTL shipment booked trigger
A shipment booked as LTL triggers freight class calculation from its actual dimensions and weight entered at booking.
- 02
Calculate density and applicable class ai
Density is calculated from actual cubic dimensions and weight, then matched against the NMFC item's density-based class break table for that product category.
- 03
Cross-check NMFC item number integration
The calculated class is cross-checked against the product's assigned NMFC item number to catch a mismatch between the commodity description and the class being applied.
- 04
Flag borderline classifications ai
Shipments where density sits near a class-break boundary are flagged for manual confirmation before the BOL is finalized, since a small measurement error near a boundary changes the class.
- 05
Populate BOL with verified class output
The verified freight class and NMFC item number are populated directly onto the bill of lading, matching what the carrier's own reweigh should calculate.
- 06
Track reclass incidents output
Any carrier reclassification that still occurs after shipment is logged against the original calculated class, surfacing which product categories or shippers keep triggering reclass disputes.
Inputs
- Shipment dimensions and weight at booking
- Product NMFC item numbers
- NMFC density-based class break tables
- Historical reclass incident log
Outputs
- Calculated freight class per shipment
- BOL populated with verified class and NMFC item
- Borderline classification review queue
- Reclass incident trend report
Works with
Prefer a fully custom build instead of an off-the-shelf integration? We scope both options during your free consultation — most jobs like this one work fine on standard connectors, but higher-volume or non-standard systems sometimes need bespoke API work, reflected in the complex tier.
Where this goes wrong if you get it wrong
- Freight class depends on actual density measured at time of shipment, not a fixed class assigned to a product once and reused forever — packaging changes, partial pallets and different load configurations shift density and can move a shipment across a class break the reused class won't reflect.
- A dimension entered in the wrong unit, or a pallet height measured without accounting for overhang or irregular stacking, throws off the density calculation enough to land in the wrong class — input measurement quality matters as much as the class-break table itself.
- Carriers reclassify for revenue as much as accuracy, and a class that's technically defensible can still get challenged — keeping a record of the calculation basis (measured dimensions, NMFC item, density) for each shipment is what makes a reclass dispute winnable rather than just asserted.
- Treating class as fixed per product ignores that the same commodity can carry different classes depending on packaging and density variation between shipments — caching a class per SKU rather than recalculating per shipment will drift wrong over time as packaging changes.
Frequently asked questions
Does this replace needing to know NMFC codes?
No — it applies the correct NMFC item number and calculates the density-based class from actual shipment dimensions, reducing reliance on someone remembering or guessing the right code per product.
What happens with a borderline density calculation?
Shipments near a class-break boundary are flagged for a quick manual confirmation before the BOL is finalized, since a small measurement variance at the boundary determines which class applies.
Can this prevent all carrier reclassifications?
It significantly reduces reclass frequency by matching the carrier's own density-based calculation upfront, though a carrier's own reweigh can still occasionally differ, which is what the reclass tracking log helps identify patterns for.
Does it work for shipments with mixed commodities on one BOL?
Yes — each commodity line is classified individually, since mixed shipments can have different applicable NMFC classes per line rather than one blended class for the whole BOL.