Storing customer goods: the day your terminal became a warehouse

It usually starts with a phone call from a customer you like. Their receiving site has moved the delivery window, the pallets cannot go in until Thursday, and there is space along the back wall of the terminal. You say yes — saying yes is a large part of why they use you.

Then it happens for four customers at once, and one stops treating it as an exception: they route goods to you on purpose, because your terminal is closer to their customers than their own storage. Somewhere in there, without anyone deciding it, your terminal became a warehouse. The goods are not the problem — terminals hold goods for a living. The problem is that transport documents describe a movement, and you are now running a business in custody, on the paperwork you happened to have lying around.

What the transport documents do not cover

A consignment note describes a journey. It names a sender, a consignee and a place of delivery, and it is discharged when the goods arrive and someone signs. It is not about the eleven days the goods spent on your floor — as far as it is concerned, those days did not happen.

So when something goes wrong — and it is rarely theft; it is a forklift, a damp corner, or a pallet released to the wrong driver — the question is: what condition were these in when you took them, and what have you done with them since? If the honest answer is a line in a dispatcher’s notebook and the memory of a phone call, you will lose that conversation regardless of who was at fault.

The goods receipt note, in plain terms

A goods receipt note records taking goods into custody. Not moving them, not selling them — holding them. It answers four questions, and it should answer them on the day, not reconstructed a fortnight later:

• Whose are they? Not who delivered them — who owns them. The two are frequently different, and the owner is who you release to and who you bill.
• What are they? Enough to identify them again: description, quantity, the unit you counted in, and weight or dimensions if those drive the charge.
• Where are they? A location in your building, not a gesture at the back wall. Whoever put them away will eventually be on holiday when somebody else needs them.
• What condition were they in? What your receiver actually observed.

That last point is where paperwork quietly turns into liability. Pre-printed phrases like received in apparent good order are an assertion about something you may not have checked. If nobody inspected the load, the note should be silent rather than reassuring — what one person genuinely saw is easier to defend than a claim to more. The same goes for value: custody is not valuation, and a value nobody declared is a number you invented and someone else will quote back to you.

Give the pallet a name you can scan

The note establishes what you hold; a label establishes which of the four similar pallets in aisle three it actually is.

A barcode does two things a written reference cannot. It removes transcription — nobody reliably types a fourteen-character reference into a phone at a dock in February — and it makes lookup a physical act rather than a search through a list. Print the code on the note as well as on the goods, and paper and pallet can always be reunited.

One honest limit: nothing makes a custody barcode unique in the world. A customer’s own label may repeat across their sites, so two consignments can carry the same code. A scan that finds two should show you both and let a person choose — silently taking the first eventually moves the wrong customer’s goods.

Release is an event, not a deletion

The informal version of release is that a driver loads the pallets and someone crosses a line off a list. What remains is a shorter list, which is not a record.

Release is an event with a date, a quantity and a reason — and the reason is almost always a booking, because the goods are leaving on a transport you planned. Tying the two together makes the custody and transport figures agree at month end without anyone reconciling them by hand: the same argument as running transport and warehouse in one system rather than two, which we wrote up separately.

Three cases decide whether release handling is any good:

• Partial collection. A customer takes 6 of 20 pallets. What remains must still be findable, still on the clock, and still part of the consignment.
• Over-collection. The booking says 20 and the driver wants 24. Refuse, and say so by name. Quietly releasing what you do not hold turns a discrepancy you could investigate today into one nobody notices for a month.
• Somebody else’s goods. If the pallets at that address belong to a different customer, that is a stale instruction, not a rounding error.

The clock: when does a day begin?

Goods arrive on Tuesday at 16:40 and are collected on Thursday at 08:10. Is that one day, two, or three?

There is no universally correct answer, which is why you need to have picked one. The common convention — a day begun is a day charged, counted in calendar days — lets a customer verify the figure from the two dates on your own paperwork, without trusting your arithmetic.

Whichever you choose, the clock must run on your organisation’s calendar, not a machine’s. If arrival times are recorded in UTC while your operation runs an hour or two ahead of it, an evening receipt lands on the previous day and the count is quietly wrong for everything booked in after 23:00. That is the difference between an invoice line a customer accepts and one they ring about.

Before you charge for storage

Storage revenue is easy to invoice and hard to defend. Answer these before the first line goes out, not after the first query comes in:

1. What is the unit? Pallet-day, square metre, weight, or a flat fee per consignment.
2. When does the clock start and stop? In words the customer can check against the receipt and release dates.
3. Is there a free period before storage begins, and does it survive a partial collection?
4. Is there a minimum charge per consignment?
5. Who is billed — the owner, or the party who delivered? Often not the same company.
6. What happens to goods nobody collects? Agree this in writing at the start. Negotiating after six months of accrued storage is negotiating from the weaker position.
7. Where does the number on the invoice come from? If someone types the days held, the figure is an opinion. If it is derived from the receipt and the release, it is evidence.

Question seven decides whether this becomes a real line of business. The rest is policy; that one is plumbing.

Start smaller than you think

You do not need a full warehouse management system to stop losing money on this. You need to know what you hold, whose it is, where it is, when it arrived and when it left — with the last of those tied to the transport that took it away. Cycle counting, replenishment and slotting belong to a warehouse that already knows what it has, and counting does not have to stop the operation when its turn comes (more on that here).

The first version can be a receipt note, a label, a location and a release. What it cannot be is a favour that nobody wrote down.

Where navichain fits

navichain handles customer goods held in custody with a sealed, barcoded goods receipt note, floor plans and locations so a pallet has an address rather than a guess, and release tied to the booking that collects it — inside the same system that planned the transport. Warehouse capability is not a separate module or a higher tier: every feature is on every plan, and you pay for scale, not capabilities. Pricing starts at 995 kr a month, billed monthly with no lock-in — the platform page shows what is in the box and the pricing page shows the full ladder.