DEV Community

challan116-ux
challan116-ux

Posted on

The EDI 832, Decoded: A Price Catalog Is the Contract Every Order Gets Judged Against

Short answer: The EDI 832 · Price/Sales Catalog is the X12 transaction a seller uses to publish what it sells and at what price — item identifiers, descriptions, units of measure, and the price basis buyers order against. It is not an order and not an invoice. Most 832 trouble is quiet: the catalog and the buyer's item master drift apart, and every downstream document — the 850 · Purchase Order, the 856 · Ship Notice, the 810 · Invoice — inherits the disagreement.

Teams obsess over orders and invoices because those are the documents that get rejected loudly. The 832 fails silently. A price that changed in the seller's system but not in the catalog the buyer loaded does not error at catalog time; it errors weeks later, as an invoice deduction nobody can trace.

What does an 832 actually carry?

An 832 carries the seller's sellable items: the buyer's and seller's item numbers, GTIN/UPC identifiers, descriptions, pack and unit-of-measure detail, and prices — list, contract, or promotional — with the effective dates and the price basis (per each, per case, per hundred) spelled out.

That price basis is where catalogs earn their keep. "12.40" is not a price until the catalog says 12.40 per what, in which pack configuration, effective from when. An 850 · Purchase Order written against a per-case price and invoiced per-each is not a partner error; it is a catalog that never made the basis unambiguous.

How is an 832 different from an 850 and an 810?

The 850 says "buy this." The 810 says "pay this." The 832 is the reference both of them are supposed to agree with before either is sent. When an invoice price is disputed, the first forensic question is not what the invoice said — it is what the catalog in effect on the order date said, and whether the buyer had loaded that version.

That is also why the 832 pairs naturally with the 832's quiet sibling problem: the buyer's item file. A catalog update only works if the receiving side actually applies it. Sellers send updated catalogs that sit unloaded in a partner's queue while orders keep being written against last quarter's prices.

What breaks most often in 832 flows?

Identifier drift. The same item carried under a seller number in the catalog, a GTIN on the order, and a buyer number on the invoice — with no maintained cross-reference — guarantees manual matching downstream. Catalogs are where the three identifiers are supposed to be bound together.

Pack and unit-of-measure mismatches. Case versus each, inner pack versus ship pack: the 832 states the selling unit, and orders that ignore it produce quantity disputes that look like pricing disputes.

Effective-date gaps. A promotional price with a start date but no loaded end date, or a new list price effective before the buyer's system applies catalog updates, creates a window where both sides are "right" and the invoice still deducts.

Partial updates treated as full catalogs. An 832 can be a full replacement or a change file. A receiver that treats a change file as the complete catalog deletes every item not in it; a receiver that treats a full file as a change keeps discontinued items orderable. The file's intent has to be explicit and honored.

No acknowledgment discipline. Catalogs are reference data, so teams skip confirming receipt and load. But an unloaded catalog is indistinguishable from an unsent one until the deductions arrive. Confirm load, not just delivery.

What does a reliable 832 workflow look like?

Bind the identifiers — seller number, buyer number, GTIN — in the catalog itself and maintain that cross-reference as data, not tribal knowledge. State the price basis and pack structure so explicitly that a new hire could price an order from the catalog alone. Version every catalog with effective dates, confirm the partner loaded it, and reconcile the first orders after each update against the new prices before the invoice cycle does it for you, with deductions.

That reconciliation step is where we focus at SignalEDI (https://signaledi.com?utm_source=devto&utm_medium=article&utm_campaign=2026-11-14) — a catalog, an order, and an invoice that agree with each other are not three separate achievements; they are one data discipline checked at three points.

FAQ

Is an 832 an order?

No. It orders nothing and bills nothing. It publishes the items and prices that later orders and invoices are written against.

Who sends the 832, the buyer or the seller?

Usually the seller — the party publishing its catalog. Some large buyers also send catalog-format files to distribute item data to their own locations or suppliers.

Why do invoice deductions trace back to the catalog?

Because the invoice is judged against the price the buyer believes was in effect, and that belief comes from the last catalog they loaded. If the loaded catalog and the seller's current prices differ, the deduction is the difference.

How often should a catalog be sent?

On every meaningful change — new items, price changes, discontinuations — with effective dates, rather than on a fixed calendar. A price change that waits for the monthly catalog run creates a month of mismatched orders.


I'm Chris, founder of SignalEDI. We build EDI and API integration for teams that would rather keep their catalogs, orders, and invoices in agreement than argue deductions — including the retail sets (832/850/856/810) in every plan.

Top comments (2)

Collapse
 
aiapikey profile image
HAOHAOnovai •

What decides disputes is not the catalog's contents but which version of it applied. Join an order to "the current catalog" and every price change silently rewrites history for orders already in flight - with quarterly updates and a 90-day order-to-invoice cycle, a quarter of your orders can be judged against a catalog that did not exist when they were placed.

Treat the catalog as effective-dated rows and join on the order's date, not on now. A price change is then an append rather than an edit, and "what was the price when this was ordered" becomes a query instead of an investigation.

That also turns the 832 into an audit artifact, not just a feed.

Collapse
 
hiredov profile image
Dov at HireDov •

Good point on the price basis. From the sourcing side, the same drift shows up before the catalog even exists: a supplier quotes "12.40" and nobody confirms per each, per carton or per hundred, which pack configuration, and what the quote is valid through. One habit that helps is writing those answers into the RFQ reply itself, so whatever lands in the catalog later has a paper trail. Then the first 832 is a copy of agreed terms instead of a fresh negotiation. Do you see buyers loading catalogs with effective-end dates, or mostly open-ended ones that get overwritten?

(Disclosure: I work on HireDov, an AI sourcing agent.)