LTL NMFC Density Based Reclassification: Carrier TMS Rating Table Rebuilds, Dimensioner Capture, and Reweigh Dispute Handling

Why Class Is Moving Toward Density

The National Motor Freight Classification, published by the National Motor Freight Traffic Association, has always rested on four transportation characteristics: density, handling, stowability, and liability. For decades many commodity items carried a single class regardless of how the shipper packaged them, which meant a pallet of loosely boxed product and a tightly packed pallet of the same product could be rated identically even though one consumed far more trailer space per pound. NMFTA has been working through a multi year docket process to move items without unusual handling, stowability, or liability characteristics onto a standard density scale, and the most visible step expanded that scale to 13 density subprovisions so the class steps are finer than the older ladder. The practical effect for an LTL carrier is that class is now something the dock measures rather than something the shipper declares.

This article describes the mechanics generally. NMFTA publishes the item level rules, the current density breakpoints, and the docket history, and the ClassIT tool shows how a specific commodity is treated today. Any carrier rebuilding a tariff should confirm the exact thresholds and effective dates with NMFTA before loading them into a rating engine, because docket cycles continue and the item an analyst memorized last year may not be the item in force when the next rate increase is filed. The systems design below is stable even as the numbers change, which is the point of building the ladder as data rather than as code.

How Density Is Calculated and How the Ladder Works

Density is weight divided by volume. The volume of a handling unit is its length multiplied by its width multiplied by its height, each in inches, divided by 1,728 to convert cubic inches to cubic feet. The dimensions include the pallet, any overhang, and any protrusion, because the carrier must plan trailer space around the actual footprint and not around the box inside it. Divide the gross weight in pounds by that cubic footage and the result is pounds per cubic foot, usually abbreviated pcf. For example, a pallet that measures 48 by 40 by 48 inches occupies 53.3 cubic feet, so a 1,066 pound pallet of that size has a density of 20 pcf, while a 400 pound pallet of the same size has a density of 7.5 pcf and will land several class steps higher.

The density scale assigns a class to each density band. The densest freight at the bottom of the ladder earns class 50, and freight so light that it is almost all air reaches class 500 at the top. Between those endpoints the ladder steps through the intermediate classes, and the 13 subprovision scale adds breaks in the middle densities where most palletized freight actually lives. The table below is an illustration of the shape of such a ladder. It is not the NMFC text. Use it to design your tables and validate your math, then populate the real breakpoints from the current NMFC.

Two design rules follow from the math. First, the TMS should calculate density from stored dimensions and weight every time rather than storing only a class, because the class is a derived value and a derived value stored alone cannot be audited. Second, rounding and unit handling must be explicit. Decide whether measurements are stored to the nearest inch or tenth of an inch, whether weight is stored to the pound, and whether density is compared to the ladder before or after rounding. Write the rule into a configuration table with an effective date, and have the rating engine read it rather than hard coding it.

Rebuilding Rating Tables and Tariffs in the TMS

A carrier tariff in the TMS is a chain of lookups: origin and destination zones, weight break, class, base rate, discount, minimum charge, accessorials, and fuel surcharge. Density based classification changes the class input to that chain, so the rebuild starts with the class to rate mapping. Every base rate table must carry a row for each class the ladder can produce, including the half classes such as 77.5 and 92.5 that older tables sometimes skipped. Carriers that rate from a published base and a customer discount should test that the discount logic handles every class and every weight break combination, because a missing row in a rate table usually surfaces as a zero charge invoice or a silent fallback to a default class.

FAK agreements, or freight all kinds, complicate the picture. A customer FAK typically says that commodities within a class range rate as a single agreed class. Under density classification the measured class of a given pallet can move from one shipment to the next, so the TMS must apply the FAK to the measured class rather than to the declared class and must log which class was measured, which class the FAK substituted, and which rate resulted. Minimum charges deserve the same treatment. When a reclass raises the class on a light shipment, the shipment may still rate at the minimum, and the correction workflow should recognize that no additional revenue is due before it generates a corrected invoice that confuses the customer.

The cleanest architecture separates the density ladder, the class to rate tables, the customer pricing overlays, and the correction rules into four distinct tables with effective and expiration dates. A tariff analyst can then stage the next NMFC docket as a future dated ladder, run a rerating simulation against last quarter's shipments, and show management the revenue and customer impact before the effective date arrives. That simulation is also the evidence base for pricing conversations. Our TMS implementation work typically builds the simulation as a stored procedure that reads historical pros, applies the candidate ladder, and writes the delta to a comparison table that pricing, sales, and billing can all query.

Certified Dimensioner Capture at the Dock

A density program is only as good as its measurements. A dimensioner is a fixed or mobile device, usually a combination of cameras or laser sensors over a scale or a forklift path, that captures the bounding box of a handling unit and its weight in a few seconds. In the United States, dimensioners used to determine charges should hold a legal for trade certification through the National Type Evaluation Program administered by the National Conference on Weights and Measures, and scales should be inspected under the applicable state weights and measures program. The certification matters because a customer who disputes a reclass will ask how the carrier measured, and a certified device with a calibration record answers that question before it becomes an argument.

The data a dimensioner produces should flow directly into the TMS through an integration rather than through a printed label that a clerk retypes. Each measurement event should record the device identifier, the certification and calibration reference, the operator or forklift, the timestamp, the pro number, the handling unit sequence, length, width, height, gross weight, computed cube, computed density, and a link to the captured images. Store the measured values on a separate record from the declared values that came from the bill of lading or the EDI 204, so the two can be compared without either overwriting the other. This separation is the single most important modeling decision in the program, because every dispute begins with the question of what the shipper said versus what the carrier found.

• Declared record - Pieces, weight, dimensions if supplied, declared class, NMFC item, source document, and who entered it.
• Measured record - Device, operator, timestamp, dimensions, weight, cube, density, derived class, and image references.
• Applied record - The class and weight actually used to rate the pro, the rule that chose them, and the user or system that applied them.
• Tolerance rule - The configured threshold below which a measured difference is logged but not billed.

Not every terminal will have a fixed dimensioner on day one. The data model should allow a manual measurement record with the same fields, flagged with the method so that reporting can distinguish certified automated capture from tape measure capture. Over time the share of pros with certified measurement becomes a program KPI in its own right, and the terminals that lag can be prioritized for equipment based on the revenue leakage their manual measurements reveal.

Reweigh and Reclass Workflows

A reweigh changes the billed weight. A reclass changes the billed class, which under density classification usually follows from a measured cube that differs from the declared or assumed cube. Both should run through one exception workflow in the TMS. When the measured record differs from the declared record beyond the configured tolerance, the system opens an inspection case tied to the pro, assigns it to the terminal or to a central inspection desk, and holds the invoice until the case closes. The inspector reviews the dimensioner images, confirms the handling unit count, checks whether the commodity carries any item specific NMFC rule that overrides the density scale, and records a disposition: confirm correction, adjust correction, or waive.

The inspection certificate is the document that leaves the building. It should be generated from the case record and should state the pro number, bill of lading reference, shipper and consignee, declared pieces, weight, dimensions, and class, measured pieces, weight, dimensions, cube, density, and class, the device and method, the inspector, the date and time, and the NMFC item and rule relied on. Attach the images. Carriers that generate this certificate automatically from structured data close disputes faster than carriers that type one in a word processor, because the structured data is identical to what the rating engine used and the customer can reconcile it line by line. The NMFC includes rules governing inspection and the carrier's right to correct weights and descriptions, and the certificate should cite the current rule item rather than a remembered number.

Timing matters as much as content. A reclass discovered at origin can often be resolved with the shipper before the freight leaves, which avoids a corrected invoice entirely. A reclass discovered at a break terminal must be documented before the freight is reloaded, because the images lose value once the pallet is buried in a linehaul trailer. Build the exception queue so that terminal supervisors see open cases by age, and set a service level that cases older than a defined number of hours escalate to a regional manager. This is a business process optimization problem as much as a software problem, and the process should be written before the screens are designed.

Dispute Packets and Customer Billing Adjustments

Customers dispute reclasses when the correction surprises them, when the evidence is thin, or when the dollar amount is large relative to the original freight bill. The dispute packet reduces all three. It contains the inspection certificate, the images, the original bill of lading, the rated original invoice, the rated corrected invoice, and a short explanation of the density calculation in plain language. The TMS should assemble the packet as a single PDF or as a secure link from the case record with one click, and the customer service representative should never need to go to a shared drive to find the image file.

Billing adjustments then follow a controlled path. The original invoice is not edited. The TMS issues a corrected invoice that references the original invoice number and the pro, shows the original and corrected charges, and carries a reason code that distinguishes reweigh, reclass, and other correction types. For customers on EDI, the corrected invoice is transmitted as an EDI 210 with the correction indicator set in the beginning segment according to the partner's implementation guide, and the detail segments should carry the corrected weight, class, and NMFC item so the customer's freight audit system can match the correction to the original. Some partners require a credit for the original and a new invoice rather than a corrected 210, and the integration should support both patterns per trading partner. Our EDI integration practice maps these partner specific variations once and tests them with real correction scenarios before go live.

When a dispute ends in a concession, record the concession as its own transaction with an approver and a reason. Concessions that are silently absorbed by editing the corrected invoice hide the true cost of weak evidence, and the concession report by terminal, by device, and by customer is one of the most useful management reports the program produces.

The Data Model in Detail

The following structure has proven workable across several TMS platforms and can be adapted to whatever the carrier already runs. The pro header carries the shipper, consignee, service, and billing terms as it always has. A handling unit table records each pallet or piece group with its declared and measured records as described above. A density ladder table holds density lower bound, class, effective date, and expiration date, keyed by NMFC docket or version. A class rate table holds the base rate by lane, weight break, and class with effective dates. A customer pricing table holds FAK ranges, discounts, and minimum charges with effective dates. An inspection case table holds the case, pro, status, inspector, disposition, rule citation, and timestamps. A correction table holds original invoice, corrected invoice, reason code, financial delta, and EDI transmission status. A concession table holds disputes, approvers, and outcomes.

Index the handling unit table on pro and on measurement timestamp, because both the billing hold check and the aging report hit it constantly. Store images outside the transactional database with a durable reference, and keep a hash of each image on the measured record so that an image presented in a dispute can be proven to be the one captured at the dock. Protect the whole structure with role based access that lets inspectors create measurements but not edit tariffs, lets pricing edit tariffs but not alter measurements, and logs every change. Those controls align with the data protection expectations that larger shippers now include in carrier audits.

KPIs That Prove the Program Is Working

A density program generates a long list of possible metrics. Six carry most of the weight. Measurement coverage is the share of pros with a certified measured record, by terminal. Declaration accuracy is the share of measured pros whose declared class matched the measured class within tolerance, by customer and commodity. Correction yield is the net revenue change from reweighs and reclasses as a percentage of revenue, which should be reported with the concession rate beside it so that aggressive corrections that get reversed do not look like success. Case cycle time is the hours from case open to disposition. Dispute rate is the share of corrections disputed, and dispute win rate is the share upheld after review. Finally, EDI correction acceptance is the share of corrected 210 transmissions accepted by the partner without a manual follow up.

Report these at three levels. Terminal supervisors see coverage, cycle time, and the open case list each morning. Pricing and sales see declaration accuracy by customer so they can decide whether to re price, re educate, or require dimensions on the bill of lading. Management sees correction yield net of concessions and the trend of dispute rate, which together show whether the program is producing durable revenue or merely producing arguments. A SQL data mining engagement usually builds these views directly on the TMS database and schedules the exports so no one assembles them by hand.

Rollout Plan

Phase one is measurement without billing. For the first several weeks capture dimensions and weight on as many pros as the available equipment allows, store the measured records, compute the derived class, and compare it to the billed class without issuing corrections. This produces the evidence for everything that follows and surfaces data quality problems in the bill of lading and EDI feeds while the stakes are low. Phase two is the tariff rebuild and simulation. Load the current density ladder, complete the class rate tables, codify FAK and minimum logic, and rerate the phase one shipments to quantify the revenue and customer impact. Phase three is controlled correction. Turn on the inspection workflow for one terminal and a defined customer segment, generate certificates and corrected invoices, send EDI 210 corrections to partners who have tested them, and measure cycle time and dispute rate. Phase four is network rollout with dimensioner purchases prioritized by the revenue leakage each terminal demonstrated in phase one.

Throughout the rollout, communicate with customers before corrections arrive. A letter that explains the density scale, shows the customer their own declaration accuracy from phase one, and offers to help them provide dimensions on the bill of lading converts a billing surprise into a pricing conversation. Carriers that skip this step pay for it in dispute volume. Carriers that do it well often find that the largest customers prefer to provide accurate dimensions up front, which reduces inspection workload and improves trailer planning at the same time.

Related practice areas for this work include TMS Implementation ELD and EDI Integration SQL Data Mining Business Process Optimization. Each practice page describes scope, deliverables, and how an engagement starts with a short discovery call.

How Strong Tower Consulting Helps

Strong Tower Consulting helps LTL carriers turn density classification from a tariff memo into a working measurement, rating, and correction system inside the TMS. The engagement begins with a measurement baseline on real shipments, moves to a future dated tariff rebuild with rerating simulation, and then stands up the inspection, certificate, and EDI correction workflow with the reports that terminals, pricing, billing, and management each need. Strong Tower Consulting, LLC and Exspeedite LLC are separately organized sister companies under common ownership. That separation keeps the consulting advice vendor neutral and focused on the carrier's own operation and systems.

To discuss your terminals, your tariff structure, and the dimensioner data you already have, call 763-244-1373 and ask for Scott Elliott. A short call is enough to scope the measurement baseline and identify the tables in your TMS that the rebuild will touch.

Frequently Asked Questions