For one pallet measuring 48 × 40 × 60 inches and weighing 400 lb including packaging: volume is 66.67 ft³, density is 6.00 lb/ft³, and the suggested density-based freight class is 125.
Before choosing a result, review what to have ready before using an NMFC calculator.
That result uses the published band of 6 to less than 8 lb/ft³. It is a density-based class estimate, not an assigned commodity item number or a freight quote. Published density bands
Read the density-based result
An NMFC density chart maps density to a freight class.
Public-source NMFC code reference
An NMFC code chart matches an item and subitem to a source record.
Thirteen class records under item 101025 only; source bulletin 1373, printed page 53. Unknown items are not assigned a class.
This section preserves the selected public-source explanation and thirteen subitem records for item 101025. It is a dated reference, not a complete or live NMFC lookup. The standalone lookup page is excluded from indexing.
Read an item result without calculating a class
An NMFC number identifies a classification item. A subitem can select a particular class and its conditions within that item. This code reference retrieves a recorded pairing; it does not measure cargo, calculate density, identify a commodity from a description or assign a class to goods outside the cited provision.
For the default example, the public source pairs item 101025, Sub 5 with Class 125 and a density interval from 6 to below 8 pounds per cubic foot. Entering only 101025 returns a subitem request, not a guessed class. The source covers household utensils and related articles, including specified boxed household and non-powered kitchen articles. It also references Item 170 and Notes 101026, 101027 and 101028. Those notes are marked unchanged in the excerpt, not reproduced in full here. This is why a matching code is a source lookup rather than permission to classify every household product alike.
Keep each batch result in its own evidence lane
Use a mixed batch when checking a spreadsheet, not to force every row into the same outcome. Paste 101025-05, 999999, NmFc 101025 SuB 08. The first entry retrieves a class record. The second is outside this reference. The third normalizes its label and retrieves Sub 8, Class 85. Treating the missing middle row as Class 85 because its neighbor matched would invent data; the export preserves that row's coverage message.
Separate four questions before using the copied output: did the text parse, did an exact source record match, does that record fit the commodity and packing, and has someone checked the current provision? A successful lookup answers only the matching question. The review checkbox is a flag for follow-up, not a declaration that the current classification is correct. It never upgrades a snapshot to a live record.
Keep the original input beside the normalized result. A seller's part number, an NMFC parent item and a class number can all look numeric in a spreadsheet. If the input is ambiguous, retain it and ask for the original item and subitem from the shipping paperwork. Do not silently strip arbitrary letters, turn a short class number into an item, or fill a missing subitem from the preceding shipment.
For a parent-only match, retain the parent result until the applicable subitem is established. The clickable subitem list is a source navigation aid. Choosing the lowest numerical class from that list would discard the density and commodity conditions that make the row meaningful. If the supporting record gives only a parent item, request the missing subitem and its basis instead of recording the first option as approved.
A cancellation record needs a different review. Item 70080 is canceled with a reference to item 101025 and otherwise applicable provisions in the cited bulletin. That reference does not select a subitem. Keep the old item, the cited destination and the unresolved applicability question together. Do not replace an old code with 101025-05 merely because it is the default example on this screen.
For an uncovered code, send the carrier or broker a short request containing the entered item, proposed subitem, shipment date, goods description and packaging state. Ask for the current provision and class used on that shipment. This is a proposed working request, not a carrier-mandated procedure. There is no need to send a screenshot of an unrelated density calculator as proof that an unrecorded code has a particular class.
Copy results with sources to keep each row's input, outcome, conditions, source link and follow-up flag together. This export deliberately says "not yet verified" for rows without a review flag. Neither state means the shipment is cleared for booking. After a current-item check, save the separate supporting reference and who reviewed it in your own shipment record; this tool does not collect or store that information.
Coverage and source version
This reference contains one class-bearing parent item, 101025, with thirteen explicit subitem-to-class pairings, and one cancellation notice for 70080. It is a selected public-document reference, not a commercial NMFC database. Numeric item descriptions, class pairings and conditions come from NMFTA Disposition Bulletin 1373, Subject 18, printed page 53, dated March 20, 2026. Retrieved October 22, 2026. Do not infer the source's issue date from its web folder name.
No subscription database was queried. Later changes to these items and the full unchanged notes have not been independently verified here. For current classification and interpretation, use NMFTA's NMFC resources or your carrier's classification assistance. This page is independent and is not an NMFTA product.
NMFC lookup questions
Is “not in this reference” the same as an invalid NMFC code?
No. It means this small public-source set has no matching class record. The code may exist elsewhere. No class is assigned from a similar-looking code or a commodity guess.
Can I enter multiple NMFC numbers at once?
Yes. Separate entries with new lines, commas or semicolons. The tool processes up to twenty entries per batch and preserves an individual outcome for every processed entry.
Does capitalization change the result?
No. Labels such as NMFC and SUB are case-insensitive. The item and subitem remain numeric: NmFc 101025 SuB 08 retrieves the same source record as 101025-08.
Why is there no single class for the parent code?
The cited item has multiple class-bearing subitems. Its parent number is not enough to select a row. This tool does not calculate a density to fill that gap.
Item 101025: thirteen public-source class records
An NMFC freight class chart compares the classes returned by that lookup.
| Item | Subitem | Class | Density · lb/ft³ |
|---|---|---|---|
| 101025 | 1 | 400 | 0 to below 1 |
| 101025 | 2 | 300 | 1 to below 2 |
| 101025 | 3 | 250 | 2 to below 4 |
| 101025 | 4 | 175 | 4 to below 6 |
| 101025 | 5 | 125 | 6 to below 8 |
| 101025 | 6 | 100 | 8 to below 10 |
| 101025 | 7 | 92.5 | 10 to below 12 |
| 101025 | 8 | 85 | 12 to below 15 |
| 101025 | 9 | 70 | 15 to below 22.5 |
| 101025 | 10 | 65 | 22.5 to below 30 |
| 101025 | 11 | 60 | 30 to below 35 |
| 101025 | 12 | 55 | 35 to below 50 |
| 101025 | 13 | 50 | 50 or more |
All thirteen pairings: NMFTA bulletin 1373, Subject 18, printed page 53, issued March 20, 2026. Referenced notes and commodity conditions still apply; the class is not inferred from an unknown item.
If the carrier invoices a higher class, the next task is to identify what changed. A different class is not, by itself, proof that the invoice is wrong.
When the invoice no longer matches your result
Start with a comparison for that shipment. The following is a proposed audit worksheet, not a carrier-required form:
| Check | Your shipment record | Carrier's revised record |
|---|---|---|
| Shipment identity | PRO number and Bill of Lading | Same shipment references |
| Packaged dimensions | Measurements and dated photos | Inspection dimensions |
| Gross weight | Weight record including packaging | Reweigh result, if any |
| Classification basis | Declared item, description and class | Revised item, provision and class |
| Billing change | Original rated charges | Revised charges and separate fees |
Ask for the inspection or reweigh record supporting the change. FedEx Freight, for example, distinguishes inspection reviews, reweigh reviews, documentation requests and fee disputes. Pick the issue that matches the discrepancy instead of sending an unexplained calculator screenshot. Billing review categories
Find the changed input before arguing about the class
Here is a hypothetical comparison using the pallet above. It is not a documented carrier dispute.
Your record shows a 60-inch packaged height. Suppose an inspection records 61 inches while length, width and weight remain unchanged. Those inputs produce 67.78 ft³ and 5.90 lb/ft³, putting the density estimate in Class 175 under the same published scale.
Now the disagreement is specific: was the finished unit 60 or 61 inches high? A photo needs to establish the packaged height, not merely show the product before wrapping. The extra inch is a question to investigate, not evidence that the carrier measured incorrectly.
If both records agree on dimensions and weight, stop treating this as a calculator error. Compare the commodity description and classification provision instead. Matching arithmetic cannot settle a disagreement about which provision applies.
Who has to produce the evidence?
"They're also very accurate with these reclassifications, and any errors aren't resolved quickly, and the burden of proof is on the shipper to prove they shipped what the carrier says they did"
one freight broker writing on an industry forum. This is a practitioner's account, not legal advice.
For an audit, work on the assumption that you must substantiate the correction you request. Assemble your shipment records and request the carrier's basis for its revision. A bare statement that the calculator returned 125 does not explain why a different measurement or commodity provision should be rejected.
The review should not be budgeted as an instant correction. Keep the case reference, submitted evidence and unresolved question together until a written outcome arrives.
Make the check repeatable on every invoice
"Checking one invoice is easy, doing it every single time is where everyone gets lazy"
one freight broker writing on an industry forum. This is a practitioner's account, not legal advice.
Checking one invoice is manageable. Repeating the check is the operating problem.
Use one audit row per shipment. Compare the original class, billed class, recorded weight and separately assessed fees each time an invoice arrives. Mark the row reviewed even when nothing changed. For a discrepancy, link the evidence packet and record who owns the next action.
A proposed status sequence is unchecked → matched or discrepancy → evidence submitted → decision received → credit verified or charge accepted. Do not mark a dispute finished merely because it was submitted. If an adjustment is approved, reconcile the resulting credit against the invoice.
The worked pallet returns Class 125 on the stated density basis. A later change belongs in a shipment-specific comparison, with the changed input or provision identified and the billing outcome tracked. That comparison is the part worth repeating on the next invoice.
To check the mass-per-volume calculation in either unit system, use the cargo density calculator and metric conversion.
When the input records match but the outputs disagree, read why freight class calculators show different results before changing the shipment record.
If you already have an item code rather than dimensions, use the NMFC item and subitem class lookup.