PIM Integration for CPQ
Washdown rating updated in Akeneo on Monday. CPQ still offers the old housing material on Wednesday. Connect your PIM to Mercura so product attributes, descriptions, and lifecycle status feed the configurator from one source.
PIM as source
Attributes feed CPQ catalog
On publish
New SKUs appear in configurator
Retired in PIM
Discontinued options hidden in CPQ
The challenge
Washdown rating updated in Akeneo on Monday. CPQ still offers the old housing material on Wednesday.
A manufacturer of checkweigher and conveyor scale systems for food packaging lines runs Akeneo as product master and Mercura for configuration and quotes. Product management publishes a revised IP rating and washdown housing material for a belt-scale series on Monday. Inside sales configures a line for a dairy plant on Wednesday and the configurator still lists the previous housing option because nobody copied the attribute change into CPQ.
Marketing retires a load-cell variant in the PIM when supply ends. Sales can still select it in Mercura until someone remembers to delete the option manually. Quote PDFs carry technical tables that contradict the datasheet the customer downloaded from the website yesterday. Product managers maintain attributes once in Akeneo and again in CPQ because the two catalogs diverged months ago.
ERP integration transmits accepted orders with BOM lines to finance and production. CRM integration updates opportunity value when quote status changes. Component libraries hold reusable modules inside CPQ. PIM integration is different: Mercura consumes product attributes, descriptions, media references, and lifecycle status from Akeneo, inriver, Salsify, Contentserv, or other PIM platforms so configuration options and quote output reflect what product management already approved in the catalog source.
Inquiry to config to price to approval to order should not quote attributes that the PIM no longer shows as current because CPQ was updated on a separate schedule.
How it works
How Mercura integrates with PIM
Product data teams map PIM attributes to Mercura product properties, configuration options, and quote template fields. On a defined schedule or on publish webhook, Mercura imports attribute values, descriptions, classifications, and lifecycle status from the PIM. New products published in the PIM appear in the Mercura catalog for configuration rules to reference. Archived or discontinued records hide or remove matching options in CPQ. Rich content from the PIM can surface in quote output where mapped. Someone must own field mapping, test imports after PIM schema changes, and review sync errors before sales uses updated data.
What's included
What PIM integration covers
- Connectors for Akeneo, inriver, Salsify, Contentserv, and others
- Attribute mapping from PIM fields to Mercura properties
- Import on schedule or webhook when records publish or change
- New SKU detection when products appear in PIM
- Lifecycle status sync hides discontinued options in CPQ
- Rich product content in quote templates where mapped
- Conflict and import error reporting for administrators
- Custom attribute support for manufacturer-specific PIM models
The difference
Product catalog before and after PIM integration
- Attribute changes maintained separately in PIM and CPQ
- Discontinued products still selectable until manual cleanup
- New launches need parallel setup in both systems
- Quote specs drift from website and datasheet content
- Product managers duplicate work across PIM and CPQ
- PIM remains source of truth for product attributes
- CPQ catalog reflects publish and retire events from PIM
- New products available for configuration after PIM publish
- Quote output uses current attribute values from import
- Administrators review mapping once, not every SKU change
Real-world application
Example workflow: checkweigher attributes from Akeneo to CPQ
A builder of checkweigher lines for food plants maintained washdown ratings, belt widths, and rejection actuator options in Akeneo. Mercura held a quarterly CSV export that product management uploaded by hand, so CPQ often lagged the website by weeks. After Mercura PIM integration mapped Akeneo attributes to configuration properties, a housing material change published Monday appeared in the configurator before inside sales opened quotes Wednesday, and retired load-cell variants disappeared from option lists when archived in the PIM.
Business impact
Why PIM integration is catalog sync, not another CPQ data entry project
PIM integration connects the system product management trusts with the system sales configures in. It complements ERP order transmission, CRM opportunity sync, component libraries, and rules-based configuration inside CPQ. Mercura does not replace your PIM workflow or become the master for marketing copy outside mapped fields. Someone must define attribute mapping and monitor import failures. If the pain is "Akeneo is current but CPQ still quotes last month's spec", PIM-to-CPQ import aligns inquiry, configuration, price, approval, and order with one product record.
See Akeneo attributes flow into a checkweigher configurator without a quarterly CSV
Book a demo and publish an attribute change in your PIM until the matching option and quote field update in Mercura.
Let’s build together.
We empower manufacturers to master product modeling, streamline quoting process, reduce errors, and ultimately deliver the tailored solutions that customers demand.