Industry configurator
Build vehicle-compatible kits without relying on fitment spreadsheets
Combine fitment logic, product dependencies, complete kits, and account-specific pricing in one guided configuration.
Automotive parts is broad. Mercura fits best where the sale is a configurable kit or system — not a single SKU lookup. The demo focuses on an aftermarket-style performance package because fitment, dependencies, and channel pricing are easy to see. OEM and tier programmes use the same configuration engine with different commercial rules.
Try a complete automotive parts order the way a counter rep would scope it
This is a live Mercura CPQ configurator, not a mock-up. Choose the vehicle application, select the part family and main components, add hardware to complete the kit, then work through services, compliance, and commercial terms. Parts that do not fit the selected vehicle drop out automatically. Pricing updates as you configure.
Running against a live Mercura tenant. Catalogue, fitment rules, and prices are an illustrative aftermarket example. Your own parts catalogue and channel pricing would drive production.
Fitment tree
Fitment is not just search
A catalogue filter asks which SKUs match. CPQ asks which valid combination should be sold together.
- 01
Vehicle
Year, make, model, trim, drivetrain.
- 02
Valid part family
Only families that fit this vehicle stay available.
- 03
Product options
Rotors, calipers, pads, finishes — guided choices.
- 04
Dependencies
A 6-piston caliper can force rotor, bracket, and pad family.
- 05
Kit completeness
Hardware and consumables on the same quote.
- 06
Customer pricing
Retail, dealer, or distributor price book.
- 07
Quote
Validated package ready to send.
Search vs CPQ
Vehicle filter is the start — not the quote
Keep catalogue fitment data where it belongs. Use CPQ for the commercial package.
| Layer | Question | Output |
|---|---|---|
| Vehicle filter | Which SKUs match this vehicle? | Compatible product shortlist |
| Configuration rules | Which options and dependencies are valid together? | Buildable kit |
| Complete package | What must ship with the main component? | Hardware, consumables, services |
| Price | Which account price book applies? | Channel-correct quote |
Segments
Aftermarket kits and OEM programmes are different motions
One platform can support both. The interactive demo uses an aftermarket-style kit because it is easiest to understand visually.
Aftermarket / performance
Vehicle fitment, kits, dealer pricing, and option packages — the demo path.
OEM / tier supplier
Variant codes, customer programmes, contract pricing, and BOM / component logic — same engine, different commercial model. We do not claim a single demo covers every OEM process.
Capabilities
What Mercura carries for parts and kit sales
Fitment, kits, and channel price books are product logic — these capabilities make counter and dealer quotes stay valid.
Before / after
How the kit quote gets built
Before
- Customer gives the vehicle
- Rep searches the catalogue
- Fitment table checked separately
- Kit spreadsheet for missing components
- Dealer pricing looked up last
- Quote assembled by hand
With Mercura CPQ
- Vehicle selected first
- Valid product family filtered
- Dependencies enforced while configuring
- Kit completed in the same flow
- Account pricing applied automatically
- Quote generated from the configuration
See your fitment and kit logic in Mercura
Bring vehicle applications, kit BOMs, and channel price books. We will show how they become a guided configuration dealers and counters can trust.
Request a CPQ demo