# One-product configurator brief

Use this blank worksheet to scope one real product before expanding to a catalogue. Fill in what you know; mark unanswered questions as “to agree”.

Prepared by: ____________________
Date / brief version: ____________________
Decision owner: ____________________

## 1. Product and buyer task

- Product name and stable product ID: ____________________
- Existing product page or catalogue reference: ____________________
- Who will use this, and what must they decide? ____________________
- Choose the pilot's next step: request a quote / add to an existing cart / another agreed action: ____________________
- What is outside this first pilot? ____________________

## 2. Options and allowed combinations

Complete the [option and rule worksheet](configurator-options-rules.csv). Use your actual option IDs, not just display labels; labels can change. If IDs do not exist, agree them before integration.

- Option groups included in this pilot: ____________________
- Default selection and why it is valid: ____________________
- One valid combination, written as group ID = option ID: ____________________
- One invalid combination, written the same way: ____________________
- Why it is invalid and what the visitor should see instead: ____________________
- Who approves the option list and dependency/exclusion rules? ____________________

## 3. Price and availability

- Authoritative price source and owner (catalogue, commerce system, price list, or quote-only): ____________________
- What should the screen show if a price is not available? ____________________
- If a price is shown, which currency, tax treatment and date/version apply? ____________________
- Source of availability and lead time, if shown: ____________________
- At which step must price and availability be rechecked? ____________________

## 4. Quote or order handoff

Name the receiving system or team: ____________________
Verified destination or test endpoint: ____________________
Who owns the receiving side? ____________________

Agree the exact fields it must receive. Include only fields needed for this task:

| Field | Your field name / source | Required? |
|---|---|---|
| Product ID and SKU, if applicable | | |
| Selected option group IDs and option IDs | | |
| Quantity | | |
| Configuration reference and version | | |
| Price reference or explicit quote-only status | | |
| Contact or delivery details needed for this action | | |
| Other agreed field | | |

- What does the visitor see after a successful quote request? ____________________
- What does the visitor see if the receiving system rejects or cannot receive it? ____________________
- If the action places an order, what authoritative response confirms that order? ____________________
- What should persist when a visitor reopens or shares the configuration? ____________________

A chat link, draft message or selected product is not, by itself, confirmation that a quote request or order was received. Define the status your actual receiving system can confirm.

## 5. Assets and approval

- Available model/CAD files, photos and material references: ____________________
- Owner who can approve their use and product accuracy: ____________________
- Parts, dimensions, colours or materials that must match the physical product: ____________________
- Who approves the final appearance, and against which reference? ____________________
- Text and images that must remain usable without the 3D scene: ____________________

## 6. Pilot acceptance

Agree the target device, browser, connection and limits before testing. Record observed results; do not fill these with assumptions.

| Check | Agreed setup / expected behavior | Observed result | Accepted by / date |
|---|---|---|---|
| The valid combination is selectable and matches the visible summary | | | |
| The invalid combination is prevented or resolved with an explanation | | | |
| Reopening a shared/saved configuration restores the agreed options | | | |
| Quote/order recipient receives the exact chosen IDs and quantity | | | |
| Rejected or unavailable handoff gives a clear recoverable state | | | |
| Asset appearance matches the approved reference | | | |
| Touch and keyboard interaction work on agreed devices | | | |
| Product information and next step remain available without full 3D | | | |
| Loading and interaction meet agreed measured thresholds | | | |

Target device(s), browser version(s) and connection: ____________________
Loading and interaction thresholds, measurement method and owner: ____________________
Outstanding decisions before expanding to more products: ____________________

Bring this brief and the completed option/rule worksheet to your scoping conversation. Service context: https://virtualverse.studio/3d-web-development

Template by Virtual Verse Studio.