Playbook: Product configurator website

Customers phone to ask "can I get it in this size, this colour, what does it cost?"

The problem

Configurable products — windows, furniture, machines, packages — generate endless pre-sales questions. Each one costs a salesperson a phone call and the customer a wait, and half of them never become an order.

What you end up with

A public web page where the customer chooses the options themselves, sees the price update as they choose, and sends the configuration as an enquiry that lands in your system. No login, no account, works on a phone.

What it needs

• Access level: App Builder access.
• Pro app: yes — public pages and web requests are Pro features.
• Instance: connected, if prices and options come from your product data.
• Public request: one server-side request that supplies options and prices to anonymous visitors.

Build it step by step

1. In the App Builder, start a new app:

   Build a Pro app called "Configurator". The home page must be public — no login. A visitor chooses a product family, then size, colour and accessories, and sees the total price update immediately. At the end they enter their name, email and phone and send the configuration as an enquiry.

2. Let the Builder set up the data path. Say where the numbers come from:

   Take the available options and prices from our product data. Create a public web request for it — the page must not read the instance directly.

   The Builder creates the request, and if it needs a credential it will ask you for exactly one value and open the form so you only paste it.

3. Decide what an enquiry becomes:

   When a visitor sends a configuration, store it and email it to sales@example.com with all the chosen options and the calculated price.

   If you want it in ERP instead, say so: "create an enquiry record in the instance" — that runs server-side through the same request mechanism.

4. Make it look like you:

   Use our brand colours, put the logo top-left, and make it work well on a phone.

5. Publish and copy the public address from the maximize button.

Try it

Open the public address in a private browser window — no Operator session. Configure a product, check the price, send an enquiry, and confirm it arrives. That private window is the only honest test: in your normal browser you are logged in and everything works even when it shouldn't.

Variations

• Quote instead of enquiry — generate a PDF quotation the visitor can download.
• Availability — show a simple in-stock / made-to-order indicator rather than exact quantities.
• Dealer version — a second, non-public page with dealer pricing, open only to signed-in users.
• Embedded — put the page in an iframe on your existing website.

Where it can go wrong

• Exposing too much. The public request decides what leaves your system. Return the price for the chosen combination, not the whole price list.
• Stale prices. Decide whether the page reads live prices or a published list, and say which on the page.
• Spam. An open form will be found by bots. Ask the Builder for a simple guard and keep enquiry emails filterable.
• "It asks me to log in." The page's access mode is not public, or you are testing a non-public page — see Pages.