Part 12 ended with one record. Forty EPCs, an event time, a read point and a business step, shipping. GS1 calls it an ObjectEvent, and it’s a tidy thing.
Nobody in accounts will ever open one.
The accountant at a plant that makes hinges works in Tally, or Zoho, or SAP Business One. She posts delivery notes against sales orders. If the RFID project wants her to trust it, the event has to turn up as one of those, against the right order, with the right quantity. Or it has to not turn up at all, and tell somebody why.
From a tag to an item
The ERP doesn’t know what an EPC is. It knows items.
An SGTIN-96 EPC carries a GTIN and a serial. Part 10 took one apart: drop the serial, put the indicator digit back in front, work out the check digit, and you have the 14-digit number on the carton’s barcode. In the film it’s 10614141073464.
That number has to be somewhere in your item master. SAP Business One has a barcode field on the item. Zoho has EAN and UPC fields. In Tally it usually goes in as an alias or a part number. Whichever it is, it’s one column, and it’s worth checking before anything else, because every other step depends on it.
The serial doesn’t go in the item master. It says which carton.
From an event to a document
The event says 40 cartons of one item went out through dock door 3 at 10:42. The ERP has an open sales order for that customer, for 40 cartons of that item. Same item, same count. So the event becomes a delivery note against that order.
Each ERP calls it something different.
- TallyPrime: a Delivery Note voucher. With order processing turned on, it carries the sales order’s number, and the order stops showing those 40 as pending.
- Zoho Inventory: a package made from the sales order, then a shipment.
- SAP Business One: a Delivery, copied from the sales order, which closes the lines it covers.
Moving stock between your own godowns isn’t a sale, so it isn’t a delivery note. Tally does that with a Stock Journal, Zoho Inventory with a transfer order, SAP Business One with an Inventory Transfer. Same reads, different document.
And the serials? SAP Business One can manage an item by serial numbers, and then each serial is picked on the delivery line. Zoho Inventory tracks serials on an item if you turn it on. TallyPrime has batches, but no serial per unit as standard. So in Tally the voucher carries the quantity, and the serials stay with the event, where you can still answer “which cartons went to Deccan Hardware on the 20th?”
When the counts disagree
This is the part that matters.
Thirty-nine cartons of the right item go through the door, plus one from the staging shelf that belongs to another order. A connector can post 39 and drop the stray. It can post both lines as they came. Either way it’s wrong, and either way nobody hears about it until the customer’s GRN doesn’t match the invoice and somebody raises a credit note at month end.
So nothing posts. The difference goes to a person: one short on FG-HNG-100-SS, one FG-HNG-75-SS that isn’t on this order, and the serial of the extra one. The dispatch supervisor walks to the door. The extra carton comes off, the missing one is probably still on the shelf, and it’s sorted before the truck leaves.
Some differences are fine. Plenty of orders go out in parts, and a short shipment against one of those should post, with the balance left open. An extra carton never should. Neither should a tag whose GTIN isn’t in the item master: either the master is missing a row or a label was printed wrong, and you want to know which.
A connector that posts whatever it’s given is a faster way to make the ERP wrong.
Where this lives
IoTReady Engine sits between the reader and the ERP and does this matching: the decode, the lookup, the order match, and the exception when they disagree. How it connects to each ERP is on the Tally, Zoho and SAP pages.
You don’t need our platform to do it. You do need somebody to write these rules down before the first truck.
The voucher preview lets you check yours. Paste the reads from a real dispatch, put your own GTINs in the item master and your order lines in the order, and pick your ERP. It shows the document it would post, or the exceptions that stop it. It runs in your browser and doesn’t talk to any ERP.
The truck can wait five minutes. The credit note takes a month.