The storage charge stops being a number arrived at on the closing day, because the handling events that shape it are recorded as they happen on the account, so the bill is a consequence of a month of recorded activity rather than a reconstruction from memory.
Warehousing & Cold Storage
Warehouses and cold stores that hold someone else's stock and bill for occupying space and moving goods. The customer is often a brand or a distributor whose stock sits in your building, and the monthly charge is the number that decides whether the account is worth keeping.
The problem
A warehouse's cost is occupancy and movement, and its income is a bill built from a picture neither the customer nor the operator can reproduce. A pallet in a rack costs rent all month, picked twice or not, and the storage line on the monthly invoice is a rate multiplied by a pallet count that lived in somebody's head or in a spreadsheet nobody else can open. Then there is handling, which is event-driven and therefore the part that should be easy: goods in, put-down, pick, pack, despatch and a cycle count, all of which happen to people on the floor and all of which reach the invoice only if someone remembers to write them down. Add the third-party reality — the stock belongs to the customer, the building belongs to the operator, and the numbers that matter to one are invisible to the other — and the recurring problem is not a shortage of data. It is that the bill is assembled at month end by hand, and the argument it causes is always about a number neither side can show.
A working day
The billing cycle sets the schedule and it is not the warehouse's to move. In the receiving window, inbound trailers are checked against paperwork and the count either agrees with the note or it becomes a claim, and that count is the number the month's bill will be built on. Through the day, handling requests arrive and are worked in an order the floor decides, and the entries that reach the bill are whatever the person at the terminal wrote. In a cold store the day carries a second question, whether the temperature held and what happened to the stock in the affected bays — a question NoxOrigin holds no record to answer. At month end, someone counts the pallets, decides what the storage charge is, and raises the invoice the customer will question line by line. The close is a reconstruction, and the honest improvement is that events are written down as they happen so the charge becomes a consequence rather than a claim.
How NoxOrigin fits this business
Every business runs the same sequence, from first contact to money in. NoxOrigin keeps each step tied to the last: Customer → Opportunity → Quote → Project → Work → Invoice → Payment.
The steps are the same. What changes is the words you use for them, the pressure at each one, and who is responsible for it. This is how it reads for warehousing & cold storage.
The stock owner as a customer
Customer → Opportunity
A brand, distributor or supplier has to become a customer record with their contacts, the terms the storage is billed on — per pallet per month, per pallet per week, per handling event — and the entity that actually pays, which in third-party storage is often not the entity whose name is on the stock. Merge policy is a setup decision: duplicate detection flags candidates and a person reviews them, since a group books under a brand, a distributor and a parent company, and nothing merges automatically.
The storage agreement quoted
Quote
The quote is the rate card, the unit the storage is charged on, the handling rates, any minimum monthly charge, any free period, and the volume it was written for, so a change in rate or volume is a new quote rather than a rate somebody corrected in an old bill. There is no e-signature and no contract editor, so a signed storage agreement stays where the operator keeps signed agreements, and this record is what the commercial terms sit in while it runs.
The account as a live storage engagement
Project
Once the terms are accepted the account becomes the live record with the stock held, the services applied to it, and the rates those services are billed at, so a rate change, a new product line or an added service is visible as a change rather than quietly folded into next month's total. A change in rates or scope is a new quote on the same account. There is no change-request record, no milestone record and no deliverable record, and nothing here plans a bay, allocates a location or schedules labour.
The handling events on the floor
Work
The work is goods in, put-down, picking, packing, despatch and the cycle count, recorded against the account so the bill has something behind it and the next month has a base to compare against. It is a record of what a person reported, not an instruction to the floor: there is no put-away or picking logic, no wave or replenishment tasking, no bin, rack or slot management, no temperature or cold-chain log, and no third-party logistics integration. There is also no timesheet record and no payroll module, so the hours behind a shift are not measured here.
The monthly storage and handling invoice
Invoice
The invoice carries the storage period as a stated basis and the handling as its own lines, with the rate and the quantity written out so the customer can see what produced the number. Nothing here calculates occupancy: the pallet count and the event count on the invoice are numbers a person supplied, and the record's job is to hold them against the account rather than to produce them. An invoice and a payment are different records, and a correction mid-cycle is a credit note on the same account, not a rewritten bill.
The payment against the storage bill
Payment
Money arrives against a specific invoice, and in this trade it is frequently paid quarterly, by a different entity from the one holding the stock, or netted against despatch revenue rather than paid at all. Recording the payment against the invoice is what makes the cycle close. A part payment and an allocation matter because a warehouse bills on a cycle and collects irregularly, and a customer paying one cycle in full is not the same as an account that is current.
Cycle close and the honest book
Reports
Billed storage and handling against received, by customer and by cycle, with the outstanding aged from the cycle due date rather than from a generic calendar. What is not here is the warehouse's own operating picture: there is no capacity planning, no demand forecasting, no auto-purchase-order, no occupancy dashboard and no lot or batch tracking, and the purchase side sits in Commerce. There is also no expense tracking in the platform, since expenses are a Nox-Billings capability — so the rent, power and labour that decide whether a bay is worth keeping are your own figures.
What changes
What is different by next week.
A rate change, a new service, or a change in the volume the terms were written for becomes a new quote on the same account, so the customer can see what the change did to the monthly number instead of finding it in a total.
The unit the storage is billed on and the handling rates are written on the quote and carried onto the account, so an argument about the invoice is about a rate someone agreed to rather than about which spreadsheet was open.
A part payment from an entity other than the stock owner is recorded against the specific invoice with who paid, so a cycle that is genuinely disputed stays distinguishable from one that is simply late.
The person who counted the pallets, the person who raised the bill and the person who allocated the payment are three named people on the same account, which is what makes a month-end question answerable without a week of emails.
Who does what
Different people need different parts of the same information.
Everyone is looking at the same information. What changes is which part of it they are responsible for.
- Warehouse managerDecides the rates, the minimum charge and which accounts get reviewed terms, and owns the number on the monthly bill that the customer will question.
- Floor and despatchWorks the inbound, the put-down, the picking and the despatch, and records the events behind them — without holding pricing or payment permissions.
- Billing and accountsCounts the billable stock with the floor, raises the cycle invoice, records each receipt including part payments, and keeps the outstanding by customer.
- Owner or operations headDecides which accounts are worth the space they occupy, when to move a rate, and what a claim against a short count is worth settling.
What software should not decide
NoxOrigin keeps the facts. You still make the decisions.
Keeping the facts in one place ends the argument about what happened. It does not make the decisions that were always yours to make.
- Whether to bill the disputed pallet count as it stands or hold the invoice. Billing it keeps the cycle closed and starts a dispute; holding it leaves the customer invoiced late and shifts the problem to the next close. Neither is safe, which is why the count has to be a recorded event with a name on it before the argument starts.
- Whether to accept a customer whose stock is growing faster than the space. Taking the account fills the building and makes every existing customer pay for the congestion; refusing loses the volume and looks like fear. The decision is about the space, not about the customer, and it is easier when the billed and received figures for each account are readable.
- Whether to pass a power or rent cost increase to a customer mid-term. Passing it through is honest and starts a renegotiation that a warehouse does not always win; absorbing it for a cycle is a decision about which relationships the operator wants to keep, and it should be a chosen position rather than a drift.
- Whether to write off a small disputed balance to close the account or keep chasing it. Writing it off costs the amount once and ends the conversation; chasing it costs the relationship over a figure that may be smaller than the year's storage on the account.
- Whether to take a cold-chain account the operator cannot evidence. Accepting it means a promise about temperature that this system does not record, so the exposure is whatever a customer's claim turns out to be, and the answer has to come from equipment and monitoring that exist before the first pallet arrives.
Free tools
What this trade tends to ask, answered with a calculator.
Receivables aging calculator
Where the open storage and handling invoices sit by age, bucketed and totalled, so an account that pays quarterly is distinguishable from one that has stopped paying. A calculation, not a collection record.
Retail day-end reconciliation calculator
Expected against counted for a single close — useful for a daily inbound or despatch check where the written events and the floor's count disagree. A reconciliation sheet, not occupancy tracking.
Where to look next
The product areas this depends on.
Commerce
Warehouses as sites, with stock, purchasing, transfers and low-stock signals where the operator also trades its own goods — the handling events themselves are not a Commerce record.
Quotes, Billing & Finance
The storage agreement quoted with its rate card and billing unit, and the cycle invoice with the storage period and each handling event as its own line.
Multi-location business management
Sites held apart as workspaces and branches, with a consolidated view that reads from the same records rather than a monthly export — which is what makes a multi-depot cycle close comparable.
Customer Payment Tracking
What each account still owes by cycle, what has been received including part payments from another entity, and the promise recorded against the date it was made.
Automations
A prompt when a cycle invoice passes the date it was expected, and an escalation when an account is two cycles out — the point at which a storage relationship is really a credit decision.
Before you look at pricing.
Is this a warehouse management system?
No. There is no bin, rack or slot management, no put-away or picking logic, no wave or replenishment tasking, and no third-party logistics integration. It does not know what is on your floor, will not direct a picker, and will not plan a bay. What it does is record the handling events a person reported, raise the storage and handling invoice against the account, allocate the payment, and keep the customer record behind it. If your operation runs on where stock physically is, that stays with a warehouse management system.
Does it record temperature or cold-chain readings?
No. There is no temperature log, no cold-chain record, no excursion or alarm handling, and no shelf-life or expiry tracking. Monitoring and the resulting evidence stay with your equipment, your monitoring provider and your own quality records. The billing record and the compliance record are two different things, and this holds the first.
How does it calculate the monthly storage charge?
It does not calculate occupancy, and that is the honest boundary. The rate and the unit the charge is billed on are written on the quote, and the quantity on the invoice is a number a person supplied — the count you did, taken from your own records. What the system adds is that the handling events behind the bill and the payments against it are recorded on the same account, so the month's charge is traceable rather than reconstructible. There is no capacity planning and no demand forecasting, and stock movement and purchasing sit in Commerce.
Can it handle despatch, order picking, and the customer's own stock levels?
The work record holds the handling events — inbound, put-down, pick, pack, despatch, cycle count — as a record of what happened, not as a task to be given. There is no wave release, no replenishment, no allocation of stock to orders and no stock-level ledger for goods you do not own. Stock, warehouses and purchasing are a Commerce capability; if the operation needs a live stock position per bin, that is a Commerce and WMS problem, not one this solves.
What if the customer disputes the bill or pays a different entity?
A disputed amount is arithmetic, a disputed count needs a record to reconstruct against, and a disputed tax treatment is not a software problem. The events and the rate behind each line are on the account, and an invoice and a payment are separate records, so a part payment from another entity is allocated to the invoice it settles with who paid recorded on it. NoxOrigin does not determine place of supply, handle reverse charge, record TDS or TCS, generate e-invoices or e-way bills, file any return, and holds no bank connection or credentials.