The EDI 832 is the X12 transaction set for a Price/Sales Catalog. A supplier uses it to send a buyer item identifiers, short descriptions, prices, packaging details and lead times as structured segments that the buyer's ERP loads without retyping. X12 describes it as a way to furnish or request the price of goods or services "in the form of a catalog".
Most 832s run between North American manufacturers, distributors, resellers and retailers. In Europe the same job usually goes through BMEcat files, GS1 data pools or EDIFACT, whose PRICAT message is the closest equivalent. This guide walks through the segments, an annotated example and the mapping errors that get catalogs rejected, then compares the 832 with BMEcat and GDSN.
What an 832 price/sales catalog carries, and what it leaves out
The 832 is built around items and prices. In the 004010 version, each item is one LIN loop that can carry dates, descriptions, measurements, packaging, physical details, lead times, taxes, hazardous material information and a nested CTP loop for prices, which repeats up to 100 times per item (Stedi's X12 reference). A heading area before the items holds the catalog number, currency, parties and terms that apply to the whole set.
What it does not do well is rich content. The free-form description element in a PID segment holds at most 80 characters, so a longer text goes into several PID segments; CDW's supplier guide says exactly that (CDW 832 guide). Partner guides like CDW's ask for identifiers, descriptions, pack data, prices and lead times, and nothing about images or technical features. Those usually reach the buyer some other way, such as an upload on the buyer's vendor site or a separate content file.
X12 also has related sets that show up next to the 832: the 846 Inventory Inquiry/Advice for stock levels, the 850 Purchase Order, the 856 Ship Notice/Manifest, the 879 Price Information and the 888 Item Maintenance. Some trading partners use the 888 or 879 for item setup and price changes instead of an 832, so read the partner's guide before you build anything.
The 832 segments a trading partner's guide will list
Every trading partner publishes an implementation guide that picks segments and codes from the standard. The table lists the ones you meet most often in 004010 guides, with a fragment of each as it appears in a file.
Common EDI 832 segments in the 004010 version
| ST | Transaction Set Header | Heading | Set identifier 832 and a control number | ST*832*0001 |
|---|---|---|---|---|
| BCT | Beginning Segment for Price/Sales Catalog | Heading | Catalog purpose (PC price catalog, SC sales catalog), catalog number and version, and the transaction set purpose (00 original, 04 change) | BCT*PC*FAST2026*4 |
| CUR | Currency | Heading | Currency of the prices, for the selling party | CUR*SE*USD |
| N1 | Name | Heading | Parties, such as the vendor (VN) | N1*VN*Example Fixings Inc |
| LIN | Item Identification | Detail | Up to 15 qualifier and ID pairs per item: VP vendor part, MG manufacturer part, UP UPC, EN EAN, UK GTIN-14 | LIN*1*VP*CT-4830-BK |
| G53 | Maintenance Type | Detail | What happens to the item: 001 change, 002 delete, 003 add full item detail | G53*003 |
| DTM | Date/Time Reference | Detail | Dates such as 007 effective | DTM*007*20261201 |
| PID | Product/Item Description | Detail | F for free-form text, up to 80 characters per segment, repeatable | PID*F****Cable tie... |
| MEA | Measurements | Detail | Single measurements such as length (LN), width (WD), height (HT), weight (WT) | MEA*PD*LN*300*MM |
| PO4 | Item Physical Details | Detail | Pack and size, gross weight per pack, pack dimensions with units | PO4*20*100*EA |
| LDT | Lead Time | Detail | Lead time code, quantity and time unit | LDT*AE*10*DA |
| CTP | Pricing Information | Detail (CTP loop) | Price identifier (WHL wholesale, MSR suggested retail, CON contract), unit price, quantity and unit | CTP**WHL*12.40*1*BG |
| CTT | Transaction Totals | Summary | Number of line items (LIN segments) | CTT*1 |
| SE | Transaction Set Trailer | Summary | Segment count including ST and SE, and the same control number as ST | SE*14*0001 |
Codes matter as much as segments. The same 13-digit EAN sent under the qualifier UP, which expects a 12-digit U.P.C., fails at the buyer, and a price under CTP02 RES (resale) instead of WHL (wholesale) can land in the wrong price list. The partner's guide lists the qualifiers it accepts.
One cable tie in an annotated 832
The example below is illustrative: a fictional supplier sends one item in an 004010 832, with "*" as element separator and "~" as segment terminator. The EAN is GS1's demonstration number. The ISA and GS envelope around the set is left out; the functional group code for an 832 is SC.
An 832 for one cable tie, line by line
| ST*832*0001~ | Start of an 832 with control number 0001. |
|---|---|
| BCT*PC*FAST2026*4~ | A price catalog (PC), catalog number FAST2026, version 4. |
| CUR*SE*USD~ | Prices are in US dollars, the selling party's currency. |
| N1*VN*Example Fixings Inc~ | The vendor sending the catalog. |
| LIN*1*VP*CT-4830-BK*MG*CT4830B*EN*9506000134352~ | Line 1: vendor part number, manufacturer part number and the EAN of the bag of 100. |
| DTM*007*20261201~ | The prices take effect on 1 December 2026 (CCYYMMDD). |
| PID*F****Cable tie 4.8 x 300 mm black UV-resistant~ | Free-form description, element PID05, up to 80 characters. |
| PID*F****Polyamide 6.6, bag of 100~ | A second PID continues the description. |
| PO4*20*100*EA**G*11.5*LB~ | 20 inner packs (bags) of 100 each per case; gross weight 11.5 lb per case. |
| LDT*AE*10*DA~ | Ships 10 calendar days after the purchase order arrives. |
| CTP**WHL*12.40*1*BG~ | Wholesale price USD 12.40 for 1 bag. |
| CTP**MSR*19.95*1*BG~ | Suggested retail price USD 19.95 per bag. |
| CTT*1~ | One line item (one LIN) in this set. |
| SE*14*0001~ | 14 segments from ST to SE, closing control number 0001. |
Three details carry the meaning. The LIN line identifies the item three ways, and the buyer matches on whichever qualifier it stores. The CTP lines state their own unit (BG, bag), which is why a bag price never gets confused with a case price. And the SE count of 14 covers every segment from ST to SE; Flxpoint, one platform that receives 832s, also checks that CTT01 matches the number of LIN segments (Flxpoint 832 notes).
Full catalog or change file: how 832 updates travel
Partners handle updates in two ways, and the implementation guide says which. BCT10 can mark the set as 00 original or 04 change. CDW's guide asks for DTM qualifier 007 (effective) when you send a full catalog and 128 (replacement effective) when you send a delta (CDW 832 guide).
Per item, the G53 segment states the maintenance type. The 004010 code list includes 001 change, 002 delete, 003 add full item detail, 004 withdraw item (temporary) and 005 restore item. Agree with the partner what a missing item in a full catalog means: some buyers read it as discontinued, others ignore it until a delete arrives.
If a set uses both, the item's G53 code takes precedence over BCT10 for that item (Stedi's X12 reference). That lets one change set add some items, change others and delete a few.
Price changes with effective and expiration dates
The DTM segment can sit at item level, as in the example above, or inside the CTP loop, where each price gets its own dates: qualifier 007 for the date the price takes effect and 036 for the date it expires. For a price increase, send the new price with a 007 date in the future while the current price stays valid until then. The buyer loads it ahead of time and switches on the date, instead of receiving a price that already applies.
How much notice the partner needs, and whether it accepts an effective date in the past, is set in its guide or your supplier agreement, not in the standard. Ask before the first increase, not during it.
Quantity breaks in the CTP loop
CTP04 and CTP05 hold a quantity and its unit, and X12's own example uses them as the start of a price range. A tiered price is then several CTP segments with the same price identifier and rising quantities, such as 1, 10 and 50 bags. Some partners read CTP04 as the quantity the price is for instead, so confirm which reading the guide uses before you send a second price line.
Deletes, withdrawals and restores
G53 code 002 removes an item from the buyer's catalog. For a temporary supply problem, 004 withdraws the item and 005 restores it later, which keeps the buyer's history and contract prices for that item intact. Retire a deleted vendor part number for good: a number that disappears and later returns on a different article is one of the hardest errors to trace in a buyer's ERP.
EDI 832 compared with BMEcat and GDSN
All three move product and price data from supplier to buyer, but they answer different needs. BMEcat is an XML catalog format maintained by BME; the current version is 2005.2, and BMEcat 2005 can carry several languages in one file and logistics data per product (BME). GDSN is GS1's network of certified data pools: data is loaded, registered, subscribed to, published and confirmed (GS1).
EDI 832, BMEcat 2005 and GDSN side by side
| Maintained by | X12 | BME, the German association for purchasing and logistics | GS1 |
|---|---|---|---|
| Format | Delimited segments from ST to SE | One XML catalog file | XML messages between certified data pools |
| Where you meet it | North American distributors, resellers and retailers | German-speaking and Dutch B2B trade, technical wholesale, procurement catalogs | Consumer goods retail, food and healthcare |
| How it travels | Point to point between two trading partners | File sent to a customer, data pool or procurement system | Supplier's data pool registers items in the GS1 Global Registry; the buyer's data pool subscribes |
| Product content | IDs, short text, pack data, prices, lead times | Multilingual texts in one file, ETIM or ECLASS features, images and documents, prices, logistics data | Attributes from the GS1 Global Data Model, keyed on GTIN |
| Updates | Original or change (BCT10), item maintenance codes (G53) | Transactions T_NEW_CATALOG (full catalog), T_UPDATE_PRODUCTS (each product marked new, update or delete) and T_UPDATE_PRICES | Publish, subscribe and confirm |
A manufacturer selling in both North America and Europe often serves all three from one product record: an 832 to a US distributor, a BMEcat file to a German or Dutch wholesaler and GDSN for retail. Our guides to BMEcat files and GDSN in practice cover those two routes in detail, and the punchout catalog guide covers the procurement-system route, where buyers shop your site instead of loading a file.
Seven 832 mapping errors that get a catalog rejected
Syntax errors are rare once an EDI translator is set up. Rejections usually come from mapping, where product data meets the partner's rules:
- EAN under the UPC qualifier. UP expects a 12-digit U.P.C.; a 13-digit EAN goes under EN, a case GTIN-14 under UK. The GTIN vs UPC vs EAN guide explains the differences.
- Price unit and pack unit out of step. A case price sent with unit EA is read as a price per piece. Keep each CTP unit consistent with your unit of measure conversions.
- Formatted prices. Flxpoint requires CTP03 to be a positive decimal without currency symbols or commas (Flxpoint 832 notes).
- Descriptions over 80 characters. Text longer than the PID05 limit gets cut or rejected; split it over several PID segments as the partner's guide allows.
- Missing required price types. CDW makes both its own price (C01) and the manufacturer's suggested retail price (MSR) mandatory; a file with only one fails.
- Identifiers that differ between documents. The vendor part number in the 832 must match the one in your 846 and 856 traffic with that partner, or orders and stock updates will not find the item.
- Wrong control totals. SE01 counts every segment including ST and SE, and CTT01 counts LIN segments. A hand-edited file that adds a PID without updating SE fails.
Onboarding a new 832 trading partner, step by step
Setting up an 832 with a new customer is a small project, and most of the time goes into data, not into EDI software. A typical sequence:
- Get the implementation guide. It names the X12 version, the segments and qualifiers the partner reads, the mandatory price types and whether it wants full catalogs or changes.
- Agree on identifiers. Decide which number goes under VP, whether the partner also needs MG and a UPC or EAN, and keep those numbers identical in every other document you exchange with that partner.
- Map your product data. Line up each segment and element with a field in your ERP or PIM export: units, pack quantities, weights, price types, lead times. Note every field you do not have yet.
- Fill the gaps. Missing UPCs, weights or short descriptions are product data work, and they take longer than the mapping itself.
- Send test files. The partner's translator answers each set with a 997 Functional Acknowledgment, which reports whether the file was syntactically accepted. Business errors, such as an unknown price type, usually come back by email or in the partner's portal.
- Go live with a full catalog. Start with the complete range, then switch to change files if the partner accepts them.
Keep the test files. When the partner later changes its guide, or when you add a product line with a new kind of pack, you can diff the new output against a file that was accepted.
Where a rejection shows up matters as much as the cause. The 997 only reports whether the set was syntactically accepted. Some partners also send an 824 Application Advice, which reports whether the content passed their application's edits: accepted, rejected or accepted with changes. Ask which of the two your partner sends and who on your side reads them. An 824 that nobody watches means a price change that never went live.
Getting product data ready for an 832 when your PIM has no EDI
WISEPIM does not send or receive EDI: it creates no 832, no PRICAT and no other EDI message. What a PIM can do is keep the data behind the message correct before an EDI translator or service provider maps it into the partner's layout. WISEPIM checks GTIN check digits when you save, stores manufacturer part numbers, weights and dimensions with explicit units, and exports to CSV or Excel or through Feed Hub as custom XML or a BMEcat 2005 (ETIM) file.
Quality Guard rules can then stop the errors in the list above before they reach the translator: a product without a valid GTIN, a description too long for the partner's limit, a missing weight. The field ownership behind that, which data the ERP item master writes and which the PIM adds, is covered in our item master guide.

