THE METHOD

Five moves between the dock and the invoice.

Third-party warehousing is five disciplines run well. Binsy runs them the way your floor already works — and writes the billing record while it happens, so nothing has to be remembered later.

01 · RECEIVE

Counted at the door, stamped on the record.

The truck backs in and the GRN counts what actually arrived — not what the ASN promised, not what the client’s email implied. Pallets for the bulk client, cartons destuffed to item level for the fulfilment client, batch and expiry captured at the door for anyone who’ll need FEFO later. And the storage billing clock starts right here, with a timestamp — because “when did those pallets land” should be a lookup, not a negotiation.

GRN vs expected · batch + expiry at the door · storage clock starts: stamped

02 · PUTAWAY

Every carton gets an address. Every address has one owner.

Putaway assigns real bin locations on a floor that belongs to many clients at once — and the segregation holds at the bin, so one client’s stock never drifts into another’s count. FEFO discipline is configured per client at setup: the batch client’s rules are enforced from the first putaway, not remembered at the pick face. When a client asks where their stock is, the answer is a bin code, not a walk of the floor.

real bins · client-segregated · FEFO configured per client

03 · PICK & PACK

Picked, packed, and billed as it happens.

Orders are picked from the bins putaway assigned and packed for the client whose rate card prices them — item-level for the fulfilment client, whole pallets for the bulk client, on the same floor and in the same shift. Every pick and every pack writes its own billing event as the work happens: per order, per item, priced off that client’s card. Nobody keys pick totals off three-week-old packing slips on the 31st.

picked from real bins · per-order + per-item events · priced at the moment of work

04 · DISPATCH

Out the door, and the storage clock stops.

Dispatch closes the storage story the same way receiving opened it: the out-date is stamped on the record, so the days in between are a fact rather than an argument. When a client asks why they were billed to the 19th after shipping on the 12th, the last scan out is the answer — and the dispatch itself is one more captured event on that client’s invoice.

out-date stamped · storage clock stops · dispatch captured as an event

05 · BILL

The invoice was being written all month.

This is the step everyone else calls month-end. In Binsy, every move above already wrote its billable event against that client’s rate card — receiving at the GRN, storage by snapshot, picks and packs as they happened. Month-end becomes a review of captured events, not a reconstruction from packing slips and memory. And the kitting job someone squeezed in on the 14th? If it’s sitting unbilled, Binsy flags it before the invoice goes out.

events → rate card · review, not reconstruction · unbilled VAS flagged

HOW A START IS SCOPED

We scope the first workflow, integration requirements and implementation plan with your team. The stages are named, not dated — because what moves when depends on your floor, not on our brochure.

DISCOVER

Your client list, the rate cards as actually agreed, storage rules and surcharge terms — written down in one place, often for the first time.

DESIGN AND CONFIGURE

Clients, rate cards, bin locations and per-client rules configured. Your floor changes nothing yet — the setup happens off to the side.

VALIDATE

Parallel running. The floor works the way it always has, Binsy captures every event alongside, and you keep the old spreadsheet as the check.

IMPLEMENT AND EXPAND

Live, client by client — with the first invoice draft assembled from captured events. Compare it to what you’d have billed by hand; the difference is the leakage you’ve been carrying.

See your floor in Binsy