A Pricing Support transaction set communicates pricing information, specifications, and cost logic between trading partners, typically exchanged in response to pricing inquiries or as part of ongoing price negotiations and updates. Suppliers send this transaction to buyers or their authorized representatives to provide detailed pricing proposals and support documentation. The SPI (Specification Identifier) segment establishes the product or service specifications being priced, while the BGN (Beginning Segment) provides context such as the transaction purpose and date. The PPL (Price Support Data) segment serves as the primary container for pricing details, enabling the sender to organize multiple pricing scenarios or product lines within a single transmission.

Consider a scenario where Acme Manufacturing requests pricing from Premier Components on high-volume steel fastener assemblies. Premier Components responds with an X12 251 transaction that includes baseline specifications via SPI, identifies Acme as the customer through the N1 loop, and then uses the PPL loop to present tiered pricing structures. Within each PPL section, Premier includes PO1 (Baseline Item Data) segments for specific fastener SKUs, QTY (Quantity) segments showing the volume breaks that trigger different unit prices, and AMT (Monetary Amount) segments detailing the extended costs for each tier. Supporting detail comes through nested PDD (Pricing Data Detail) segments, reference numbers linking to Acme’s purchase inquiries, and NTE (Note/Special Instruction) segments explaining quantity discounts or delivery conditions.