BCT
Beginning segment for price/sales catalog: catalog purpose and identification, and the effective date.
EDI 832: Price / Sales Catalog
A supplier’s catalog of items with descriptions, identifiers, packaging, and prices. Supplier to buyer or distributor. This page covers what the 832 is for, the segments you meet when you open one, the documents it travels with, where it tends to go wrong, and how it moves over AS2 into your systems on Files.com, which receives, parses, validates, and routes it as configuration.
No credit card required · 7-day free trial · Live in minutes
#1 MFT vendor in Gartner Peer Insights
Trusted by 4,000+ companies
Every protocol included
What The 832 Is For
The 832 is the electronic catalog. A supplier sends it to buyers so their purchasing systems carry current items, descriptions, product identifiers, pack sizes, and prices, and so that the 850s they generate reference items the supplier recognizes at prices both sides agree on.
It is sent on a schedule or whenever the catalog changes, and it can be a full replacement or a set of updates. Distributors and marketplaces depend on it to load and maintain product data at scale rather than by spreadsheet.
The Segments You Meet First
In document order, the segments that carry the 832's meaning. A partner's implementation guide says which are required and which fields each must hold.
N1
The supplier and, where the catalog is customer-specific, the buyer.
LIN
Item identification.
PID
Item description.
PO4
Item physical details: pack, size, and unit.
CTP
Pricing information: price type, unit price, and quantity breaks.
DTM
Effective and expiration dates for prices.
Where It Goes Wrong
Price effective dates that overlap, and identifier changes that break the buyer’s cross-reference between its item number and the supplier’s. A catalog that arrives as a full replacement when the buyer expected deltas can also silently drop items.
The Documents It Travels With
The 832 rarely moves alone. These are the documents that precede, answer, or settle it.
850 · Purchase Order
A buyer’s order to a supplier: the items, quantities, prices, dates, and ship-to locations.
See The 850810 · Invoice
The supplier’s bill for goods or services delivered against a purchase order.
See The 810846 · Inventory Inquiry / Advice
A supplier’s report of stock levels: on hand, available, committed, and on order.
See The 846997 · Functional Acknowledgment
The receipt that says an EDI transmission arrived and was parsed, with any syntax errors found.
See The 997How The 832 Moves On Files.com
A partner sends the 832 over AS2, SFTP, or FTPS, and it lands in that partner’s inbox folder on Files.com with the transport receipt recorded. From there it is a workflow, not a project: TransformScript parses the X12 natively into the JSON, CSV, or XML your ERP or WMS reads, content validation flags a document whose contents are wrong before anything ingests it, and an automation routes the result to the system and the people who act on it.
Outbound is the mirror image. Your system exports its record, TransformScript builds the 832 the partner’s guide specifies, and the file dropped in the partner’s outbox goes out over AS2 with automatic retries until the MDN confirms delivery. Every transmission in both directions is in the audit log, and delivery monitoring alerts when a 832 that was due never arrives. The full picture is on the EDI software page.
EDI 832 Questions
What teams ask about the 832 and how it moves on Files.com.
An EDI 832 is the X12 Price/Sales Catalog. A supplier sends it to buyers to publish and update its items, descriptions, identifiers, packaging, and prices, so purchasing systems order valid items at agreed prices.
The 832 describes what a supplier sells and at what price. The 846 reports how much of it is in stock.
Yes. Files.com is a standards-compliant RFC 4130 AS2 endpoint, and a 832 sent by a trading partner lands in that partner’s inbox folder with a signed MDN receipt returned to the sender. Partners who exchange over SFTP or FTPS connect to the same platform and the document lands in the same place.
Yes. TransformScript parses the X12 832 natively and writes the JSON, CSV, or XML your systems ingest, as a step in the workflow that fires when the document arrives. Outbound, the same engine builds a 832 from your system’s export and drops it in the partner’s outbox for delivery.
Exchange The 832 Without The Legacy Stack
Start the 7-day trial, turn AS2 on, and exchange certificates with your partner. The 832 lands in their folder, parses into the record your system reads, and every transmission carries a signed receipt.
No credit card required • Free for 7 days • Live in minutes