EDI 832 — Price/Sales Catalog
Supplier → Flxpoint · Price and product catalog
EDI 832 — Price/Sales Catalog
Purpose
Send your full product catalog — items, prices, and availability — to Flxpoint. Originates with the Supplier, sent to Flxpoint. Used for initial catalog setup and ongoing price or product updates.
In Plain English
The 832 is your product list. Where the 846 answers "how many of each item do you have right now?", the 832 answers "what do you sell, how do you describe it, and what does it cost?". Flxpoint ingests the 832 to set up the master catalog — SKUs, descriptions, wholesale prices, category codes, pack sizes — so that when orders come in the system already knows what each item is. Partners typically send one big 832 during onboarding (a full catalog load) and then send smaller delta 832s whenever prices change or new SKUs launch. A wrong 832 creates downstream pain: incorrect pricing on PO 850s, mismatched UPCs on invoices, or catalog items that never appear in the retailer's channel because Flxpoint could not match them. The 832 is currently in evaluation at Flxpoint — initial custom implementations exist for specific partners and broader standard support is coming.
Note: The 832 is a catalog document, not an inventory update. For live inventory quantity changes use the 846. The 832 is for pricing, product details, and availability status.
Frequency
- Initial setup: Send a full catalog (BCT02 =
SC) when onboarding - Updates: Send price changes or new SKUs (BCT02 =
UP) as needed - Full refresh: Resend the complete catalog periodically to sync any gaps
Business Rules
- One 832 per catalog or catalog segment — do not mix multiple suppliers in one file
- Each CTP segment must have a valid price type code (e.g.,
WSfor wholesale) - Unit of measure must be
EA(Each) - PID segment is strongly recommended for product descriptions
- LIN identifiers must match your 850/846 identifiers (same qualifier and value)
Transaction Purpose Codes
BCT02 — Transaction Set Purpose Code
| Code | Meaning | When to Use |
|---|---|---|
SC | Specific Catalog | Full catalog transmission |
UP | Update | Partial update — new items or price changes only |
DL | Delete | Remove items from catalog |
CA | Catalog | General catalog (initial or full refresh) |
Availability Status
PO401 (in PO4 loop) or CTP product availability
Use the PID segment description or CTP availability codes to communicate stock status:
| Status | Meaning |
|---|---|
| Available | Item is in stock and available to order |
| Discontinued | Item is no longer carried — include in DL update |
| Back Order | Item temporarily unavailable |
Segment Hierarchy
ISA Interchange Header GS Group Header (GS01 = "SP") ST Transaction Set Header (ST01 = "832") BCT Beginning Segment for Price/Sales Catalog ┌─ LIN Loop (repeats per item) │ LIN Item Identification │ CTP Pricing Information │ PID Product/Item Description (recommended) │ QTY Quantity Available (optional) └─ CTT Transaction Totals (optional) SE Transaction Set Trailer GE Group Trailer IEA Interchange Trailer
Segment Specifications
ST — Transaction Set Header
| Element | Name | Length | M/O | Value/Notes |
|---|---|---|---|---|
| ST01 | Transaction Set ID Code | 3 ID | Required | 832 |
| ST02 | Transaction Set Control Number | 9 N | Required | Unique, must match SE02 |
BCT — Beginning Segment for Price/Sales Catalog
| Element | Name | Length | M/O | Value/Notes |
|---|---|---|---|---|
| BCT01 | Catalog Number | 30 AN | Required | Your catalog identifier or version number |
| BCT02 | Transaction Set Purpose Code | 2 ID | Required | SC (Specific Catalog), UP (Update), CA (Catalog) |
| BCT03 | Description | 80 AN | Optional | Catalog description |
| BCT07 | Date | 8 DT | Required | Catalog date (CCYYMMDD) |
LIN — Item Identification
| Element | Name | Length | M/O | Value/Notes |
|---|---|---|---|---|
| LIN01 | Assigned Identification | 20 AN | Required | Line item number (sequential) |
| LIN02 | Product/Service ID Qualifier | 2 ID | Required | SK (SKU), UP (UPC), or EN (EAN) |
| LIN03 | Product/Service ID | 48 AN | Required | Your item identifier |
| LIN04 | Product/Service ID Qualifier | 2 ID | Optional | Secondary identifier qualifier |
| LIN05 | Product/Service ID | 48 AN | Optional | Secondary identifier value |
CTP — Pricing Information
| Element | Name | Length | M/O | Value/Notes |
|---|---|---|---|---|
| CTP01 | Class of Trade Code | 2 ID | Optional | Leave blank if not applicable |
| CTP02 | Price Identifier Code | 3 ID | Required | WS (Wholesale), NET (Net Price), RTL (Retail) |
| CTP03 | Unit Price | 17 R | Required | Unit price — supports up to 4 decimal places |
| CTP04 | Quantity | 15 N | Optional | Quantity associated with this price |
| CTP05 | Unit of Measure | 2 ID | Required | EA (Each) |
PID — Product/Item Description
| Element | Name | Length | M/O | Value/Notes |
|---|---|---|---|---|
| PID01 | Item Description Type | 1 ID | Required | F (Free-form) or S (Structured) |
| PID02 | Product Characteristic Code | 2 ID | Optional | Leave blank for free-form |
| PID05 | Description | 80 AN | Required | Product name or description |
QTY — Quantity Available
| Element | Name | Length | M/O | Value/Notes |
|---|---|---|---|---|
| QTY01 | Quantity Qualifier | 2 ID | Required | OH (On Hand), OA (On Order), AV (Available) |
| QTY02 | Quantity | 15 N | Required | Available quantity |
| QTY03 | Unit of Measure | 2 ID | Optional | EA (Each) |
CTT — Transaction Totals
| Element | Name | Length | M/O | Value/Notes |
|---|---|---|---|---|
| CTT01 | Number of Line Items | 6 N | Required | Total count of LIN segments |
SE — Transaction Set Trailer
| Element | Name | Length | M/O | Value/Notes |
|---|---|---|---|---|
| SE01 | Number of Included Segments | 6 N | Required | Count of all segments including ST and SE |
| SE02 | Transaction Set Control Number | 9 N | Required | Must match ST02 |
Example File
ISA*00* *00* *ZZ*SUPPLIER *ZZ*FLXPOINT *240115*1200*U*00401*000000020*0*P*>~GS*SP*SUPPLIER*FLXPOINT*20240115*1200*20*X*004010VICS~ST*832*0001~BCT*CAT-2024-001*SC***20240115~LIN*1*SK*SKU-ABC123~CTP**WS*29.99*1*EA~PID*F****Blue Widget 12oz - Case of 1~QTY*OH*150*EA~LIN*2*SK*SKU-DEF456*UP*UPC-012345678901~CTP**WS*49.99*1*EA~PID*F****Pro Tool Kit - Standard Edition~QTY*OH*42*EA~LIN*3*SK*SKU-GHI789~CTP**WS*15.00*1*EA~PID*F****Cotton T-Shirt - White XL~QTY*OH*0*EA~CTT*3~SE*16*0001~GE*1*20~IEA*1*000000020~
What this file does: Sends 3 items with wholesale pricing and on-hand quantities:
- SKU-ABC123: $29.99 — 150 units on hand
- SKU-DEF456: $49.99 — 42 units (also has a UPC cross-reference)
- SKU-GHI789: $15.00 — 0 units on hand (still listed in catalog)
Common Mistakes
⚠️ The 832 is a catalog document, not inventory. Use the 846 to send daily inventory quantity updates. The 832 is for product setup, pricing, and catalog management.
⚠️ BCT07 (date) is required. Missing the date field is a common structural error that causes a 997 rejection.
⚠️ LIN identifiers must match your other transactions. If you use SK + a SKU value in your 846/856, use the same qualifier and value in the 832. Mismatched identifiers break product matching in Flxpoint.
⚠️ CTP03 unit price must be a positive decimal. Do not include currency symbols or commas. Use 29.99 not $29.99 or 29,99.
Known Issues & Status
832 schema validation is pending. Flxpector does not yet have a full 832 validation schema — official field definitions are being finalized with the integrations team. The documentation above is based on the X12 004010 standard and initial Flxpoint implementation.
Known limitations under review
- Extraction of secondary product identifiers (e.g. UPC) from
LINsegments when multiple qualifier/value pairs are present: Flxpoint is improving the parser to read all pairs, not only the first. - Full 832 structural validation (beyond envelope) will be added to Flxpector once schema sign-off is complete.
Something unclear?
Ask our AI assistant — it knows this spec and can explain any segment, error, or rule in plain English.