Embeddable Product Configurator
Partner portal embed loads the configurator. Product team published new rules Monday. Reseller quotes still run last week's option logic. Mercura embed puts the same rules engine inside any host UI.
The challenge
Partner portal embed loads the configurator. Product team published new rules Monday. Reseller quotes still run last week's option logic.
A manufacturer of modular cleanroom partition walls for pharmaceutical and food plants sells through a Salesforce partner community and a Shopify storefront. IT added a configurator iframe in both environments eighteen months ago. When product management retired a panel thickness option and added a new gasket kit rule, inside sales updated Mercura on Monday. Reseller quotes on Tuesday still offered the old thickness because the embed pointed at a cached product snapshot.
Channel ops maintain a spreadsheet mapping which partners run which embed version. E-commerce and partner community were built by different agencies, so rule changes require two release tickets and a QA pass each time. A reseller quotes an invalid wall height and gasket pair that inside sales blocked in CPQ last week because the portal embed never received the constraint update.
Customer self-service configurators publish step-based flows on the marketing website for prospects. Self-service CPQ gives authenticated buyers quote PDF release on their schedule. Dealer portal CPQ targets credentialed distributors with tier pricing. Embeddable product configurators are different: Mercura delivers a JavaScript embed and API so the configurator runs inside partner CRM pages, e-commerce carts, and reseller portal UI with host branding, one rules engine behind every instance, and rule updates propagating from Mercura without rebuilding each channel separately.
Inquiry to config to price to approval to order should not diverge by channel because each embed maintains its own copy of product logic.
How it works
How Mercura embeddable product configurator works
Developers add a lightweight JavaScript embed or call Mercura's API from the host application. The configurator renders inside the partner portal page, e-commerce product detail, or internal sales tool while keeping host navigation and styling. Rules, constraints, and pricing load from Mercura's central product models, so updates in Mercura reach every embed instance without redeploying separate channel configurators. SSO connects authenticated partner users; anonymous mode supports public storefront embeds. Event hooks pass completed configurations to host analytics, CRM, or order workflows. Someone must map which products each embed exposes, test host styling after Mercura catalog changes, and confirm webhook or CRM handoff carries full configuration output.
What's included
What embeddable product configurator covers
- JavaScript embed deploys configurator inside any web page or portal
- API access for custom UI built into native applications
- Single Mercura rules engine behind every embed instance
- Host branding and navigation preserved around the configurator
- SSO for authenticated partner and intranet deployments
- Anonymous mode for public e-commerce and marketing embeds
- Event hooks for host analytics and workflow integration
- Webhook or API submission of configuration output to downstream systems
The difference
Multi-channel configuration before and after Mercura embed
- Partner portal and e-commerce run different option logic
- Rule updates require multiple release cycles per channel
- Resellers quote combinations inside sales already blocked
- Channel ops track embed versions in spreadsheets
- Buyers redirected to external configuration tools
- Every embed pulls rules from the same Mercura source
- Product updates reach partner and storefront embeds together
- Invalid combinations blocked in host UI before quote submit
- Partners configure inside CRM without leaving the portal
- New channel deployments reuse embed instead of rebuilding logic
Real-world application
Example workflow: cleanroom partition embed in partner community and Shopify
A builder of modular cleanroom partitions sold through Salesforce partner community and Shopify while inside sales used Mercura CPQ. Each channel had a separate embed snapshot, so gasket kit rules updated in Mercura did not reach reseller quotes until IT redeployed both sites. After Mercura embed connected both environments to the central rules engine, product management published a panel thickness change once and partner community and storefront embeds picked up the constraint without a second release cycle.
Business impact
Why embeddable configurators are channel placement, not a replacement for buyer portals
Embeddable product configurators put configuration where partners and buyers already work without redirecting them to a separate CPQ site. They complement marketing-site self-service configurators, authenticated buyer CPQ portals, dealer portal CPQ, and distributor quoting interfaces. Mercura does not replace custom front-end development, marketplace-specific checkout flows, or channel contracts that govern who may quote which SKUs. Someone must own embed scope per host environment and test handoff after catalog changes. If the pain is "partner embed still prices last week's options after Monday's rule publish", embeddable configurators align inquiry, configuration, price, approval, and order with one Mercura source across every host UI.
See a partner community embed pick up Monday's gasket rule without a second site redeploy
Book a demo and walk an embed session in partner portal chrome until rule updates from Mercura appear in the host UI and configuration output reaches CRM.
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.