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

Waves out, paths sequenced, packs verified.

Orders build into waves and pick paths come out sequenced — worth the fuss, because travel time can run up to half of all picking activity. Packs are scan-verified before they seal, so a flash-sale Friday doesn’t become a mispack Monday. Shopify clients’ orders flow straight onto the floor, and tracking flows back to their store without anyone re-keying a thing — and yes, every pick and every pack just wrote its own billing event.

waves · sequenced paths · scan-verified packs · Shopify in, tracking back

04 · DISPATCH

Manifested, courier-assigned, on the clock.

Orders manifest, couriers get assigned, and the SLA clock runs where you can see it. Meanwhile each client watches their own stock and their own orders in their own portal — which is the polite way of saying they stop watching your inbox. Dispatch also closes the storage story the same way receiving opened it: out-date stamped, so the days in between are a fact, not an argument.

manifest · courier · SLA clock · client portal, not your inbox

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

THE FIRST 14 DAYS

DAY 1–3

Rate cards, clients and bin locations configured; Shopify stores connected. Your floor changes nothing yet — the setup happens off to the side.

DAY 4–10

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

DAY 11–14

Live — 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