One Load, Three Records | 3PL Software

A warehouse that stores and ships for other companies sends its monthly invoice. The customer disputes four lines. Two are for work the customer says they never ordered. Two are for work the dock says it never did. Everyone is telling the truth. The load exists three times. Once as the customer's order, once as the dock's log of what happened, and once as the invoice, typed by a third person from whichever of the first two she was given. Three records, three owners, and a monthly meeting to argue about which one is real. Everything on screen is a mock demo with sample data; no Zoho screen appears in this one until the end, because the problem is not a screen. Six minutes, three records, one rule. The customer's order says what was agreed. Receive forty pallets on the third, store them, pick and ship as web orders come in, and repack twelve of them into retail cases before the fifteenth. This record is owned by the customer and the account manager, and it is the only place the agreement lives. It is not the place to record what happened, because the customer was not on the dock. When the account manager updates it after the fact to match the invoice, the agreement is lost and the dispute has nothing to stand on. Rule one: the order owns what was agreed, and it is never edited to match what happened. The dock's log says what happened. Forty-two pallets arrived, not forty, because the trucking company split a load. Two were damaged and photographed. The repack was done on the eleventh, fourteen cases not twelve, because the customer's own web orders needed two more. And on the ninth, a rush pick was done at four in the afternoon because the customer called. None of that is on the order, and all of it is billable or arguable. It is owned by the dock supervisor, and the only place it can be recorded honestly is on the dock, at the time, by the person who did it. Written up the next morning from memory it is already wrong. The phone matters more than it sounds. A supervisor who has to walk to a terminal records the event later, and later is where the invoice dispute is born. Rule two: the dock owns what happened, recorded once, when it happens, where it happens. On a phone, in one tap, not on a clipboard that gets typed up on Friday. The invoice is where the dispute is born, because it is the only one of the three that is typed. The billing clerk has the order in one window and the dock's Friday write-up in another, and she types an invoice that is a blend of both: forty pallets received, because that is what the order said; the rush pick, because the dock mentioned it; the repack at twelve, because that is what was agreed; nothing for the damage, because it was in a photo folder nobody sent her. So the customer is billed for a rush pick they do not remember and not billed for two extra cases they did get, and the warehouse loses the damage claim. Every error is a fact that lived in one record and was retyped into another. Rule three: the invoice types nothing. It reads the order for the rates and the dock for the events, and if an event is not on the dock's record, it is not on the invoice. Put the three rules together and the dispute has nowhere to live. The rush pick on the ninth is recorded by the picker when it is done, with the time and the customer call that asked for it. The invoice reads it and applies the rush rate from the order. The customer sees the line with the time and the call reference, and either remembers the call or asks for the recording. The argument takes one minute instead of one meeting. The two damaged pallets are recorded at receiving with the photos attached. The invoice does not bill them, and the claim against the carrier is raised from the same record. The fourteen cases are recorded at repack, and the invoice bills fourteen at the order's rate, with the two web orders that caused them linked. One event, one record, one owner. Everything downstream reads. The customer's view is not a courtesy. It is the reason the meeting disappears: they see the same record the invoice was built from, at the same time the warehouse does. On Zoho this is not exotic. The customer's order and its rates live in Zoho CRM against the account. The dock records events in Zoho Inventory as receipts, picks, packs and adjustments, from a phone, at the time. The invoice is created in Zoho Books from those events at the order's rates, with the events as lines. The warehouse's own screens sit over all three, designed for a dock and a billing desk, so nobody has to know which application holds which record. That is the solution we design for warehouses and the manufacturers who use them, and the three rules are the only part that is hard. If your monthly invoice meeting is an argument about which record is real, the fix is three rules and one habit: record the event once, where it happens, by the person who did it. We design that with the warehouse and its customers in a no-risk discovery: you pay only if you go ahead. The link is below.