Manufacturer
Edits the product, rules and price lists, publishes them across the network and sees cases handled by dealers within the agreed scope.
From configuration to order in one process
JAPRIVIO CPQ connects product data, rules, price lists and the sales activity of manufacturers and their networks. Configuration retains the context of the pricing, the quote and the customer’s decision.
Product and configuration
Configuration that follows the manufacturer's rules.
Salespeople select the model, variant and equipment, while JAPRIVIO CPQ checks requirements, dependencies, exclusions and configuration completeness.
- Product dataConfiguration draws on the manufacturer’s portfolio, models, parameters and equipment.
- Rules instead of manual checksUnavailable or conflicting options are blocked, with an explanation of what needs to change.
- A ready-to-use summaryA complete configuration produces a specification ready for pricing and quoting.
We describe 3D visualisation and AI support within the scope of a specific model, as an extension rather than a feature of every product.
Price lists and pricing
Current prices where configurations and quotes are created.
We connect models, equipment and configuration rules with the right price lists and commercial terms. That keeps pricing part of the sales process.
- Assignments and discountsPrice lists are assigned to the manufacturer and dealers according to their permissions, and discounts are factored into pricing.
- Pricing of models and optionsJAPRIVIO CPQ prices models and options based on price lists, assignments and discounts.
- Working with dataPrice lists are versioned and published in a separate step. Prices can be imported and exported as CSV or XLSX files, and a new price list can start from a copy of an existing one.
CRM and sales work
Sales in a single, connected view.
An enquiry that starts with a product can progress to a customer, sales opportunity, configuration and quote without losing the process history.
- Leads and enquiriesNew enquiries enter a structured sales workflow and can be routed to the right dealer or account manager.
- Pipeline and activitiesSales opportunities, tasks and next steps form a shared work queue for the team.
- Role-based visibilityData visibility matches the user’s role and organisation.
Quote and order
The customer accepts a specific quote version.
The quote is built from the configuration and pricing, has revisions and a history, and once accepted can move on to an order.
- A controlled documentEach quote has a number, status and change history. A sent quote retains the data from the moment it was sent.
- The customer's decisionThe customer receives a link to a specific quote version and accepts it with a code sent by email.
- Proof of acceptanceThe accepted version is saved as a frozen PDF with a checksum (hash) and proof of acceptance.
- Moving to an orderAn accepted quote can become an order without recreating the specification.
Manufacturer and channels
Manufacturer, dealer, sales rep and end customer in one process
The process can involve the manufacturer, dealer, salesperson and a B2C channel. We define data access and enquiry routing for each scenario, and channels do not need to have the same scope.
Dealer
Configures and prices using the published rules and the assigned price list; sees only their own company’s data.
Sales rep
Manages their own customers, opportunities and quotes, with a task and next step on every case.
End customer (B2C)
Configures the product or sends an enquiry that reaches the right sales team.
Every perspective uses the same CPQ functions and a single product catalogue. Enquiry routing and data access are agreed for each scenario.
See each role’s scope of workEditor and administration
Draft first. Then publish.
The editor covers product options, rules and media, their publication and versions.
An administrator on the manufacturer’s side independently changes the options, rules and media of an existing model, publishes them and restores a previous version when needed.
- DraftChanges to options, rules and media are made in a draft.
- PublicationOnce checked, the draft can be published as a new version of the product data.
- RestoreA previous version can be restored as a draft.
We prepare a new model or a new type of rule together with the technical team.
Process security
Roles, data isolation and an activity trail.
Safeguards cover data access, change history and quote acceptance.
Roles and permissions
The scope of data and actions is determined by the user’s role.
Data isolation
Each organisation’s data is isolated from that of the others.
Access control
Data access is checked against the user’s account and organisation.
Activity trail
Changes and decisions in the process leave a record in the history.
Acceptance safeguards
An email code, a frozen PDF and a checksum link the customer’s decision to a specific quote version.
Implementation and integrations
An implementation scope tailored to the sales process.
We start implementation by agreeing on a specific process and the scope to be launched first.
- Data preparationWe prepare manufacturer data, configuration rules, the user structure, price lists, permissions and the agreed workflow.
- First scopeWe launch one agreed process rather than everything at once.
- TestingWe check configurations, pricing and roles on the manufacturer’s data.
- Go-liveUsers start working within the agreed scope.
- Further developmentFurther areas and extensions are added in stages.
Integrations
We select integrations to suit the customer’s environment. Analysing the connections and building them are separate scopes, agreed individually.
Configurator on the manufacturer’s website
A link, an embedded frame (iframe) and a widget are different ways of providing access, each with a different scope of work.
Want to sort out your product and pricing logic first? See JAPRIVIO Advisory
See JAPRIVIO CPQ in a sample manufacturer–dealer process.
From product configuration to an accepted quote and order.
