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. Flxpoint now supports the 832 as a catalog-import document (internally called GIP — Get Inventory & Price), rolling out on Standard EDI V2 and live first for pharma sources such as AmerisourceBergen and Kinray.

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.

How Flxpoint actually parses the 832 (important): there is no generic 832 parser — 832/GIP is handled only by vendor parsers (AmerisourceBergen, Kinray), both built on the 846 base. Both hard-require BCT01=PC and key items on NDC. Their LIN-qualifier and CTP price-type sets diverge, so Flxpector validates the 832 leniently: envelope + BCT present + BCT01=PC + LIN pair structure, with no whitelist on BCT02 / CTP02 / LIN qualifiers. The generic SC/UP/CA + WS/NET details below are X12 reference; the "Pharma / GIP Catalog Variant" section at the bottom is the operative spec for what Flxpoint actually reads.

Frequency

Initial setup: Send a full catalog when onboarding
Updates: Send price changes or new SKUs (delta) 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., WS for 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

code

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 Purpose Code	2 ID	Required	`PC` — Flxpoint's GIP parser (AmerisourceBergen, Kinray) hard-requires `PC` here and rejects anything else (`Invalid BCT01 Catalog Purpose Code — expected 'PC'`). This is what Flxpector validates.
BCT02	Catalog Number	30 AN	Optional	Catalog identifier or version. (Generic X12 also carries purpose codes `SC`/`UP`/`CA` on the BCT segment, but Flxpoint keys on BCT01=`PC`, not those.)
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	Generic: `SK`/`UP`/`EN`. Pharma GIP (ABC/Kinray) keys on NDC — qualifier `ND` (ABC also falls back `N1`→`N4`). Flxpoint does not whitelist 832 LIN qualifiers (vendor sets diverge).
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	Generic: `WS`/`NET`/`RTL`. Flxpoint does not whitelist CTP02 — pharma sets diverge (ABC: `AWP`/`CON`/`LPR`/`MSR`/`RTL`/`WHL`/`SPE`; Kinray: `INV`/`MSR`). A non-numeric CTP03 skips the item; a blank CTP03 keeps it (price unset).
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

EDI · 004010VICS

ISA*00*          *00*          *ZZ*SUPPLIER       *ZZ*FLXPOINT       *240115*1200*U*00401*000000020*0*P*>~
GS*PI*SUPPLIER*FLXPOINT*20240115*1200*20*X*004010VICS~
ST*832*0001~
BCT*PC*CAT-2024-001***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.

Pharma / GIP Catalog Variant

Pharma distributors (AmerisourceBergen, Kinray) send a richer 832 with pricing and packaging detail. If your catalog follows this flavor:

Header: BCT01 = PC (Price Catalog). REF qualifiers seen here: ACC, FL, 2K, X9.
Parties: N1*VN (Vendor) and N1*BY (Buyer).
Item identifiers (LIN): Flxpoint matches in this qualifier priority — VN → UP → ND → MG → SK → VC → EA → UN. Send the identifier your channel keys on first.
Validity dates: DTM*092 (price start) and DTM*093 (price end).
Packaging: PO4 (e.g. 1 case / 100 each).
Pricing (CTP02 price-type qualifiers): AWP (Average Wholesale Price), CON (Contract), LPR (List), WHL (Wholesale), RTL (Retail), MSR (MSRP).

CTP03 (price) handling

CTP03 value	Result
Valid number	Price saved normally
Blank / empty	Item is kept and its quantity updates; the price is simply not saved (item is not skipped or archived).
Invalid / non-numeric	Error `Invalid CTP03 value: CTP03 (price) must be numeric` — the item is skipped.

⚠️ A blank CTP03 used to skip and archive the item. As of mid-2026 a blank price keeps the item; only an invalid (non-numeric) price skips it. Reprocess the catalog file to apply the current logic.

Known Issues & Status

Full structural validation is incremental. The 832 is supported for catalog import (GIP); Flxpector currently applies envelope + generic X12 validation and is adding deeper GIP-832 field checks as the standard finalizes. The documentation above reflects the X12 004010 standard and the current Flxpoint GIP implementation.

Known limitations under review

Extraction of secondary product identifiers (e.g. UPC) from LIN segments when multiple qualifier/value pairs are present: Flxpoint reads pairs in the qualifier-priority order above.
Deeper GIP-832 structural validation (pricing/packaging segments) is being added to Flxpector incrementally.

Something unclear?

Ask our AI assistant — it knows this spec and can explain any segment, error, or rule in plain English.