In B2B e-commerce, PIM supplies the searchable, classified product content, while ERP or a pricing engine supplies customer-specific prices and stock. PIM also defines customer assortments and feeds punchout catalogues through SAP OCI or cXML. The deciding capabilities are filterable technical attributes, assortment logic, clean ERP integration and procurement-ready exports.
B2B e-commerce needs a PIM (product information management) system to deliver the specification-level product content professional buyers search on, organised into customer-specific assortments and exported to procurement systems. Prices and stock stay in ERP or a pricing engine. The deciding capabilities are filterable technical attributes, assortment logic, clean ERP integration and punchout support.
How does B2B e-commerce change PIM requirements?
Business buyers rarely browse. They arrive with a part number, a specification or a reorder list, and they buy on contract terms. That shifts the job of product content from persuasion to precise identification.
Four differences from B2C stand out:
- Specification search. Faceted filters on voltage, diameter, material or pressure rating only work when attributes are numeric, unit-normalised and consistently classified.
- Account-specific views. Each customer may see a different assortment, product names and part numbers of their own, and contract prices.
- Order units. Packaging quantity, minimum order quantity and price unit matter as much as the product itself.
- System-to-system buying. Many large buyers order from inside SAP, Coupa or other procurement suites rather than on the webshop.
Which product data belongs in PIM and which in ERP?
Clear ownership prevents the most common B2B integration failures. The full reasoning is set out in PIM and ERP.
| Data | System of record | Delivered to the shop |
|---|---|---|
| Item number, order units, packaging quantity | ERP | Via PIM or directly |
| Technical attributes, classification, descriptions | PIM | From PIM |
| Images, datasheets, certificates | DAM or PIM | From PIM or DAM |
| Customer assortments and customer part numbers | PIM or commerce platform | From PIM or commerce platform |
| Contract prices, tiered prices, discounts | ERP or pricing engine | Real-time API call |
| Stock and delivery dates | ERP or warehouse system | Real-time API call |
The pattern is simple: slow-changing content flows from PIM in batches or events, while fast-changing commercial data is called live. Integration patterns are compared in PIM integration architecture.
How does PIM support punchout catalogues?
A punchout catalogue lets a buyer leave a procurement system, shop in the supplier's catalogue and return the basket as a requisition for approval. Two protocols dominate:
- OCI (Open Catalog Interface), developed by SAP, returns basket lines as HTTP form fields to a return address the buyer's system supplies. It is used mainly with SAP Supplier Relationship Management.
- cXML (commerce XML), created by Ariba, uses XML messages for punchout sessions and also covers purchase orders, order confirmations, ship notices and invoices.
The PIM's role is to supply clean descriptions, classification codes, units of measure and images to the punchout catalogue, and to produce static catalogue files for buyers who load content into their own procurement systems. Buyers often request classification codes such as UNSPSC or ECLASS on every line, so these mappings should live in the PIM.
What product data do B2B buyers search on?
Specification data drives findability. Distributors and manufacturers in technical sectors typically align attributes with ETIM, coordinated by ETIM International with member organisations representing 21 countries, or with ECLASS. The standards are compared in ETIM, BMEcat and ECLASS.
A practical minimum per item:
- Manufacturer name and manufacturer part number
- GTIN where one exists
- Classified technical attributes with units
- Order unit, packaging quantity and minimum order quantity
- Datasheet, certificates and safety documents
- Accessory, spare part and successor relationships
The same structured data also feeds search engines and AI assistants. The schema.org Product type supports properties such as gtin, mpn, sku and brand, and AI shopping agents rely on the same fields, as discussed in agentic commerce.
What should B2B companies test during PIM selection?
Ask vendors to show one customer-specific assortment, a customer part number mapping, a live price call from ERP alongside PIM content, and a punchout or catalogue export with classification codes. Then measure how long a new SKU takes from ERP creation to searchable listing. Shortlisted vendors can be checked side by side in the compare tool, and a lead time measured in days rather than hours usually points to manual handoffs in the integration.
Key takeaways
- B2B PIM supplies specification content and assortments, while ERP or a pricing engine supplies prices and stock.
- Numeric, unit-normalised, classified attributes are the foundation of B2B search.
- Support both SAP OCI and Ariba cXML punchout, with classification codes on every line.
- Keep customer part numbers and assortments in a governed system, usually the PIM or commerce platform.
- Test with a real customer scenario that combines PIM content and live ERP pricing.
Frequently asked questions
Should prices be managed in the PIM for B2B e-commerce?
Usually not. Customer-specific prices, contract discounts and tiered pricing change often and depend on the account, so they belong in ERP or a dedicated pricing engine. The PIM can hold price-related context such as list price, price unit, packaging quantity and minimum order quantity, which the commerce platform combines with live prices at request time.
What is the difference between OCI and cXML punchout?
Both let a buyer leave a procurement system, shop in a supplier's catalogue and return the basket as a requisition. OCI (Open Catalog Interface) was developed by SAP and returns basket items as HTTP form fields. cXML (commerce XML) was created by Ariba and uses XML messages, covering punchout sessions, purchase orders, order confirmations and invoices. Many suppliers support both.
What product data do B2B buyers need to find the right item?
Professional buyers search by specification. They need numeric technical attributes with units, classification aligned with ETIM or ECLASS, manufacturer part numbers, packaging and order units, datasheets and certificates, and accessory and successor links. Without these, faceted search fails and buyers fall back to phone and email orders.
For a PIM vendor overview and market commentary, see the independent resource PIMvendors.com.