Your team blast-froze forty pallets for a new client last month. The invoice that went out shows storage and handling. It does not show the contracted charges for the blast freezing, the re-stacking after they came out, or the two after-hours receipts your supervisor waved through by text on a Saturday.
The work happened. The charge did not.
That gap is often not a pricing problem at all. It sits between the work your floor performs and the record your billing runs from, and it opens quietly, one unrecorded activity at a time.
Here are the five places it happens, why cold storage is more exposed to it than ambient warehousing, and what to make a WMS vendor prove before you buy one. Everything below comes from published warehouse terms and conditions and public cold storage rate sheets, not from a survey.
The five places cold storage revenue leaks
None of these are unusual. Each one is a normal consequence of a busy operation.
1. Value-added work performed at the dock. A supervisor solves a client’s problem in the moment. The work is real, the client is happy, and nothing generates a billable record, because the task was never a task in the system. Castellini Group ran into exactly this: their legacy WMS could not track dumping, grading, and special storage, so those services were only partly recovered. This is a process gap before it is a software gap. Even a strong billing engine only rates what the floor recorded.
If this is you: pull one client’s rate sheet against what your floor actually performed for them last month.
2. Accessorials agreed verbally and never written into the contract. A client calls at 4pm asking for a Saturday receipt. Your supervisor says yes, because that is the relationship, and the rate sheet never learns about it. Same for the emergency tempering and the extra inspection. Fixing this is contract hygiene: every accessorial your operation performs needs a rate on file, including the ones you rarely charge for.
If this is you: a client’s volume tripled and their accessorial list did not change.
3. Storage cycles drifting out of sync with the contract. A client signs on anniversary terms. Your system runs split month. Nobody notices for two quarters, because the variance is small per lot and invisible in aggregate. The invoice ends up defensible to you and wrong to them, which surfaces as a dispute rather than as an error report.
4. Rate changes that never reach the invoice. The account manager negotiates a new handling rate in March. The rate card in the system still says January. This one compounds, because the longer it runs the harder it becomes to credit or rebill cleanly.
5. Manual reconciliation between operations and accounting. When the WMS holds the activity and a spreadsheet holds the invoice, month-end becomes a transcription exercise, and transcription introduces variance in both directions. Some clients get undercharged. Some get overcharged, which costs you the relationship rather than the revenue.
If this is you: month-end takes three days and produces at least one credit memo.
Three of these five usually come down to contract discipline or a process change on the dock rather than to software. Worth working out which of yours are which before anyone goes shopping.
Why cold storage billing is more exposed than ambient
Cold storage billing introduces charge types that typically don’t apply to ambient warehousing: temperature-zone storage rates, blast freezing and tempering, and handling that varies with product condition. Storage often runs on split-month or anniversary cycles rather than calendar months. Many food products are invoiced from the weight recorded at receiving rather than a fixed case weight.
Three things make the record harder to keep straight.
More chargeable steps per pallet. Rate sheets price freezer positions above cooler positions, and cooler above dry. A pallet received into the cooler, blast-frozen overnight, then stored in the freezer has occupied all three. Which of those legs generates a charge, and at what rate, depends on that client’s contract. Blast freezing, tempering, and re-stacking after freezing have no equivalent on an ambient rate sheet. If you run three zones on one blended storage rate, that is the first place to look. Multi-zone handling is covered in more depth on our cold storage 3PL page.
Weight that varies case to case. Cases of meat, cheese, and produce differ in weight, which is what catch weight describes: a property of the goods, not a line on the invoice. Nobody bills for catch weight. They bill for case picking or handling and calculate that charge from the weight actually recorded. If the real weight never gets captured on the floor, no billing engine can rate from it afterward.
A storage clock set by contract, not by the calendar. In the warehouse terms and conditions many refrigerated warehouses publish, storage charges begin on the date the warehouse accepts care, custody, and control of the goods. Split month charges a full month on goods received between the 1st and the 15th, and a half month on goods received from the 16th. Anniversary runs from the receipt date to the same date the following month. Some operators simplify to calendar month.
The charge types on a cold storage invoice
The names vary by operator, but these are some of the most common charge types.
| Charge type | What it covers | Commonly measured by |
|---|---|---|
| Storage | Occupying space over time | Pallet position, hundredweight (CWT), cubic foot |
| Handling in / handling out | Receiving and shipping labor | Pallet, case, CWT |
| Blast freezing and tempering | Bringing product to or from temperature | Pallet, pound, hours in the blast cell |
| Case picking and order assembly | Building less-than-pallet orders | Case, line, order |
| Value-added services | Labeling, re-stacking, palletizing, kitting, inspection, repack | Unit or labor hour |
| Accessorials | After-hours receiving, detention, hazmat handling, special storage conditions | Occurrence |
| Minimums | Contract floors on storage, handling, or invoice total | Month, lot, or shipment |
What to look for in a system that handles cold storage billing
If you decide the system is the constraint, five criteria matter for cold storage specifically. They apply to any platform you evaluate, and each one maps to a leak above.
- Charges generated by the operational transaction that created them. The moment a task completes on the floor, the billable record should exist. This closes leaks one and five at the same time.
- Billing rules a business user can configure. If a new contract or a mid-year rate change needs a developer ticket, leaks two and four stay open.
- Rating built for cold storage. Zone-differentiated storage rates, and charges calculated from the weight actually recorded at receiving and picking.
- Support for the client’s real storage cycle, split month and anniversary, not calendar month only.
- A clean handoff to your accounting or ERP system, so the invoice does not get retyped on its way out.
If you are further along and comparing platforms rather than diagnosing your own billing, our cold storage WMS comparison guide covers the wider evaluation.
How to test this in a WMS demo
Bring these to any demo, and ask for them on your own contracts rather than the vendor’s sample data. If you want a fuller set to take to every vendor on your list, we keep one in the Demo Day Question Playbook.
- Set up my three most complicated client contracts, live, in this session. How long did that take, and who had to do it?
- When my team performs a value-added service on the floor, what exactly creates the billable record, and what happens if the associate skips a step?
- Show me the backup a client sees when they dispute a storage charge.
- A client’s handling rate changes on the 12th. Show me what happens to the invoices already in progress.
- Show me a lot received into the cooler, blast-frozen, then stored in the freezer. Walk me through every charge that generates.
Why some cold storage 3PLs shortlist Datex
The cold storage 3PLs that typically shortlist Datex tend to share a profile: several temperature zones, multi-client contracts that differ in structure rather than just in rate, and a meaningful share of revenue coming from value-added work.
Castellini Group, the family-owned Cincinnati 3PL running 200,000 square feet across seven temperature zones from 50°F down to minus 10°F, is leak one at scale. Chris Larson, their President and Chief Executive Officer, put the requirement plainly: “We really needed a system that had dynamic pricing components to make sure that we were fully recovering the revenue for those activities.” Castellini reports gaining flexible order management, same-day inbound handling, and real-time client visibility after moving to Footprint WMS. Those outcomes are customer-reported. Kevin Niemeier, Vice President of Technology at Nor-Am Cold Storage, describes the same pattern from the other direction: their standard billing options cover most clients, but winning certain new business depends on specific billing routines the WMS has to support.
In Footprint WMS, billing rules are configured by client, service, and contract, and accessorial codes are configurable for any value-added service. The warehouse workflow that performs the work is what opens the billable record, so charges are captured as the work happens rather than pieced together at month end. Billing rules and handling instructions live in Footprint WMS. Datex Studio, the low-code layer, handles the screens, fields, and widgets your team works in. The Customer ePortal gives clients their own view of inventory and activity, which can help resolve a storage dispute without rebuilding the supporting activity manually.
Datex may not be the right fit if you run a single ambient zone, if your client contracts are genuinely standardized, if you are looking for the lowest initial cost, or if configurability is not something your operation needs.
Where to start
If you suspect billing leakage, don’t start with a new system. Start by finding the gap.
Take one client and compare what your floor actually performed last month with what their contract says you can charge for. Look for work that wasn’t recorded, rates that weren’t applied, or billing rules that no longer match the contract.
Fix the contract and process gaps first. Then look at what’s left. If warehouse activity still has to be manually translated into billable charges, that’s the problem to put in front of a WMS vendor.
And don’t settle for a slide about billing. Bring your most complicated client contract to the demo and ask the vendor to show you how it works.
Get a Preview of Footprint WMS and see how billing works in the system. Or talk to one of our experts and bring us your most complicated client contract. We’ll walk through how Footprint WMS would handle it.
Frequently Asked Questions
Cold storage 3PLs bill across several charge families: storage, handling in and out, blast freezing and tempering, case picking, value-added services, accessorials, and contract minimums. Storage is usually rated by pallet position, hundredweight, or cubic foot. Rates commonly vary by temperature zone, since freezer space costs more to run than cooler or dry.
Split-month billing charges a full month of storage on goods received between the 1st and the 15th of a calendar month, and a half month on goods received between the 16th and the last day. It is a common storage billing structure among refrigerated warehouses, used alongside anniversary billing, which runs from each lot’s receipt date.
Storage pricing combines a rate unit, a temperature zone, and a time cycle. The rate unit is typically a pallet position, hundredweight, or cubic foot. The zone sets the rate, since freezer space costs more to operate than cooler or dry. The cycle determines when the clock starts: split month, anniversary, or calendar month.
Look for billing rules a business user can configure without a developer, charges generated automatically by the operational transaction that created them, zone-differentiated storage rates, actual-weight capture at receiving and picking, and support for split-month and anniversary cycles rather than calendar month only. A useful test is whether a completed task on the floor creates the billable record by itself.
Methodology
The billing structures described here come from published warehouse terms and conditions and public cold storage rate sheets. Customer outcomes are reported by those customers and have not been independently audited. Rates, contract terms, and platform capabilities change. Confirm the specifics against your own contracts and directly with any vendor you evaluate. Last reviewed September 2026.
