3PL fulfilment WMS · by AggAiLabs
A warehouse full of other people’s goods.Billed to the last pick.
Binsy runs third-party warehouses the way they actually work: many clients on one floor, items and pallets side by side, online-store orders next to bulk inbounds — and every move writing its own billing event the moment it happens.
MULTI-CLIENT · RATE CARDS · BILLABLE EVENTS · ITEMS + PALLETS
- 38% floorMERIDIANitem-level · e-commerce · 1,204 SKUs
- 44% floorKHANNA FMCGpallet-in/out · 312 pallets
- 18% floorORBIT INDUSTRIALbatch+expiry · FEFO enforced
kitting job for ORBIT (240 units, Tue) had no billing event → rated off card, added to draft invoice · ₹4,080 not leaked
- ⚙ cycle count zone C: 2 variances flagged w/ bin history
- ⚙ FEFO alert: batch O-1189 expires in 21 days · 64 units
- ⚙ storage snapshot 06:00: 312 pallets · 3 rate cards
- ⚙ long-term surcharge rule tripped: 9 pallets >90 days
01 · THE COST CENTER WITH SHELVES
The floor does the work. The invoice forgets half of it.
Third-party warehousing bills by activity: every pallet received, every snapshot of storage, every pick, every label, every kitting job. But most 3PL invoices are reconstructed at month-end — from packing slips, spreadsheets and memory. What isn’t written down isn’t billed.
The industry has a name for the result — revenue leakage — and a published range for it. It is not small, and it compounds monthly.
FROM THE PRODUCT · ONE CLIENT’S MONTH-END, ASSEMBLED
Month-end in one screen. Every line has a receipt.
No packing-slip archaeology. The invoice assembles itself from events captured when the work happened — you review the draft, you don’t reconstruct it.
- ⚙ 6,214 events captured as the work happened · none keyed at month-end
- ⚙ 2 rate-card version changes (M12 v3→v4) applied from their effective dates
- ⚙ cycle-count variances (zone C ×2) annexed to the draft with bin history
Meridian queries one storage week — “those pallets shipped on the 12th.” The draft attaches bin history and the dispatch confirmation: last scan out on the 19th. Evidence wins arguments; goodwill credits don’t.
Binsy drafts; it never sends on its own. Ravi walked the seven lines in four minutes, approved, and the invoice went out to Meridian with the evidence attached to every line.
02 · WHERE THE MONEY HIDES
Four places 3PL revenue quietly leaks.
Binsy’s answer is structural: every operation writes a billable event against the client’s rate card as it happens. Month-end becomes a review of captured events, not an archaeology dig.
CAPTURED AT THE MOMENT OF WORK · PRICED OFF THE RATE CARD
Receiving
Pallets in, cartons in, container destuffing — counted at the GRN, priced off the client's rate card the moment goods cross the dock. If it isn't captured at receipt, it's rarely captured at all.
Storage
Per pallet, per bin, per square foot — snapshotted on schedule, not reconstructed at month-end from memory and a walk of the floor. Long-term storage surcharges applied by rule.
Pick & pack
Per order plus per item. The events accrue as the work happens; nobody keys them from packing slips on the 31st.
Value-added services
Kitting, labelling, returns processing — the charges most likely to vanish, because they happen off the standard flow. Binsy treats every VAS task as a billable event with a client and a rate.
03 · DOCK TO INVOICE
Receive. Putaway. Pick. Dispatch. Bill.
The GRN counts what actually arrived — pallets, cartons, batches with expiry. Storage billing starts here, with a timestamp nobody can argue with.
Real bins, real locations, client-segregated. FEFO clients get batch discipline at the door, not at the pick face.
Picked from real bins, packed for the client whose rate card prices it. Every pick and every pack writes its own billing event — per order, per item, at the moment of work.
The out-date is stamped as the stock leaves, so the storage days between the GRN and the dispatch are a record, not an argument.
Every step above already wrote its event. The invoice assembles itself from the record of work — reviewed by you, argued by no one.
The full method — GRN discipline, segregation, rate cards, cycle counts, and how every event reaches the invoice.
How Binsy works →04 · ONE FLOOR, MANY OWNERS
Standard WMS assumes one owner. Your floor has twelve.
Client-level segregation is the entire discipline of third-party warehousing: separate inventory that can never cross, separate rate cards, separate rules — FEFO for one client, pallet-in/pallet-out for another, item-level e-commerce fulfilment for a third — on the same racks, worked by the same team.
Software built for brands managing their own stock models none of this. Binsy models nothing else.
05 · FROM THE FLOOR
BUILT BY AGGAILABS
From the team that runs freight operations on agents.
AggAiLabs builds operational software for the logistics midmarket — the FreighAI platform runs quoting, booking, tracking and finance desks for freight forwarders. Binsy is the same philosophy pointed at the warehouse: the system should do the bookkeeping, so the floor can do the work.
THE DOCK IS OPEN
Bring one client’s rate card.Watch a month of billing capture itself.
Your clients, your floor, your rates: inbound to invoice in one walkthrough — and the leakage you’re carrying today, measured against it.