Traceable Quality
Talk to us
Menu

Free tool

Voucher preview

Paste the EPCs from a dispatch and see the delivery note they would post in TallyPrime, Zoho Inventory or SAP Business One. Or the exceptions that stop it.

Your ERP

The 24 hex characters a reader shows, or urn:epc:id:sgtin:…. A CSV export works: the first field is taken as the EPC.

Try:

Item master

Put your own GTINs here to check your own reads.

Sales order SO/26-27/0412

Against
Customer
Deccan Hardware
Finished goods
ItemOrderedReadOn the document

Exceptions, for a person

    What the tags said

    EPCGTINSerialItem

    Each EPC decodes to a GTIN and a serial. The GTIN finds the item, the counts are matched to the sales order, and the event becomes a delivery note. Or an exception for a person.

    What you’re looking at

    A pallet of 40 cartons goes out through a dock door. That’s the event from part 12. This page takes its EPCs and does what a connector does before anything reaches the ERP.

    Each EPC is decoded to a GTIN and a serial, the way the EPC encoder does it. The GTIN is looked up in the item master. The count per item is matched against the sales order. If everything agrees, you see the document it would post. If anything doesn’t, nothing posts, and you see the list a person would get.

    The samples are the part 12 pallet, a bad day (one carton left behind, one from another order on the pallet), and a messy reader export with repeats, URIs, a pallet label and a tag nobody can name.

    The rules

    • A tag that doesn’t decode stops it. A header outside the GS1 range usually means someone wrote their own number into the tag. You can’t post a carton you can’t name.
    • A GTIN missing from the item master stops it. Either the master needs a row or the label was printed wrong.
    • An extra item stops it. A carton that isn’t on the order never posts, part delivery or not.
    • More than the order stops it.
    • Less than the order stops it, unless the order takes part deliveries. Then it posts what went, and the rest stays open.
    • Repeats count once. A reader reports a tag many times; an EPC is one carton however often it was heard.
    • A pallet label (SSCC) is set aside. It says which pallet, not what’s on it.

    What each ERP calls it

    TallyPrime: a Delivery Note voucher, linked to the sales order by its order number when order processing is on. Tally keeps batches but no serial per unit as standard, so the voucher carries the quantity and the serials stay with the event.

    Zoho Inventory: a package created from the sales order, then a shipment. The serials go on the package line if serial tracking is on for the item.

    SAP Business One: a Delivery, copied from the sales order as its base document. If the item is managed by serial numbers, each serial is picked on the line.

    Stock moving between your own locations isn’t a sale: that’s a Stock Journal in Tally, a transfer order in Zoho Inventory, an Inventory Transfer in SAP Business One.

    What it doesn’t do

    It doesn’t connect to your ERP or post anything. It doesn’t know your real sales orders; you type the lines in. Quantities are one carton per tag, so if your ERP stocks in pieces, multiply by the pack size. Nothing you paste leaves the browser.

    IoTReady Engine does this step for real, between the reader and the ERP. See the Tally, Zoho and SAP pages for how it connects.

    Where the numbers come from

    The EPCs use GS1’s documentation company prefix, 0614141, so they’re nobody’s real product. Decoding follows the GS1 EPC Tag Data Standard, release 2.3, and uses the same code as the EPC encoder. The rules are in src/scripts/epc-voucher.ts, with a test beside them.