Product Configurator

A public web page where customers configure a product themselves — options, price, and an order-ready enquiry — built on your live product data.

Configurable products — windows, furniture, machines, packaging — generate endless pre-sales questions: which size, which colour, what does it cost? Each one costs a phone call and a wait. A product configurator answers by itself: the customer picks the options, sees the price update as they choose, and sends the configuration to you as an enquiry — no login, no back-and-forth, works on a phone. In Operator you describe the product and its options in plain words, and the App Builder builds the page.

What you get

A configurator page customers can open from anywhere — on your website, on a phone — no Operator account needed.
Real options and prices read from your ERP.net product data, so a price change in the instance reaches the page without editing anything.
Price calculated live as options are chosen — combinations, surcharges, and minimums follow the rules you describe.
A completed enquiry that reaches your team: stored and emailed to whoever should see it — or turned into a record in your ERP.net instance.
Your look — brand colours, logo, your wording; nothing looks like a generic form.

Example

You say: "build a configurator for our windows: frame colour, glazing, size, and opening type, with the price updating as they choose, and an enquiry form at the end." Operator asks where the options and prices come from, builds the page from your product data, and publishes it on its own address you can link from your website.

How to ask for one

Describe the product and how people choose it:

build a configurator for our packaging boxes: size, cardboard grade, print colours, and quantity, with a live price

a public page where a customer picks a door model, dimensions, and fittings, and sends the configuration as an enquiry

Useful things to mention:

The options — which choices exist, in which order, and whether some depend on others (a certain glazing only in certain sizes).
The price rules — how each option affects the price, minimum quantities, discounts for large orders.
Where options come from — from your ERP.net products, or a fixed list you type in.
What an enquiry becomes — an email to sales, a record in the instance, or both.
Whether it is public — open to anyone with the link, or only to signed-in users (for example, a dealer version with dealer prices).

What to check before approving

The prices match your real ones. Configure two or three products you know, in a private browser window (so you see it as a customer would), and compare against your price list.
The combinations make sense. Try a nonsense combination — the largest size with the cheapest grade — and check the page handles it the way you would.
The enquiry reaches someone. Send a test configuration and confirm the email arrives with all the chosen options, or that the record lands where expected.
Not too much leaves the system. The public page should receive prices for the chosen combination — not your whole price list. Ask Operator what the page sends and receives.
It works on a phone. Most customers will configure from one — check the page there, not only on a wide screen.

Changing it later

Add an option — "add matte black as a frame colour" — and the page and price rules follow.
Change the pricing — "volume discount from 50 pieces: 10% off" — and it applies to new enquiries straight away.
Add a step — "generate a PDF quotation the visitor can download" — so serious customers leave with a document.
Make a second version — a dealer page with different prices, open only to signed-in users.
Put it on your website — the page can be embedded in your existing site.

Good to know

A public page is a Pro app feature; the prices and options come from your connected ERP.net instance through a secured path — the page itself never holds your credentials.
The public address is stable — link it from your website once and it stays.
An open enquiry form will be found by automated spam; ask for a simple guard against it and keep the enquiry mailbox filterable.
Prices shown can be live from your instance, or a published list that updates on a schedule — decide and say which on the page, so customers are not surprised at order time.
A configuration sent by a customer is an enquiry, not an order — turning it into a sales order stays your decision.