Supply chain collaborationPrice/sales catalog (EDI 832) Meet embedded SpicY™ AI

SPICE™ Glossary / Price/sales catalog (EDI 832)

Price/sales catalog (EDI 832)

A price/sales catalog (EDI 832) is the X12 transaction a supplier uses to send product information and pricing to a buyer, such as item identifiers, descriptions, attributes and prices.

The 832 shares the item data a buyer needs to set up and order products. Each item is identified by the supplier’s part number and usually a GTIN or UPC, with a description, unit of measure, pack configuration, dimensions and weight, and list or contract prices with effective dates. Depending on the trading partner, it may also carry attributes such as color, size or country of origin. A supplier can send a full catalog or only changes.

The 832 comes before any order is placed. It feeds new item setup at the buyer, then later price and item updates. Once items are set up, purchase orders (EDI 850) reference those identifiers, and invoices are checked against those prices. Some retailers and distributors use a data pool (GDSN) instead of, or alongside, the 832.

When catalog data is wrong, the problems appear downstream. A missing GTIN, an outdated price or a pack size that differs from what actually ships causes rejected orders, receiving errors and invoice disputes. Buyers often need attributes the 832 doesn’t carry consistently, so product data still arrives partly by spreadsheet and has to be validated and completed before it can be used.

How SPICE™ handles it

SPICE Catalog™ collects supplier product data through EDI 832, API, data pools, files, spreadsheets or web forms, validates it against your requirements, fills buyer-specific gaps and maps it to your ERP item hierarchy before approved records are published. It works alongside your PIM or MDM rather than replacing them. See vendor data and new item setup.

FAQ

Frequently asked questions

Who sends an EDI 832?

Usually the supplier or manufacturer, to its customers. Distributors also send 832s to their own customers to share items and contract prices.

What is the difference between an EDI 832 and a data pool?

The 832 is a direct, point-to-point transaction between two trading partners. A data pool in the GDSN publishes product data once, using GS1 standards, and makes it available to every subscribed recipient.