Why this step decides
A configurator is often judged by its 3D model. For sales, what comes out at the end is what counts. If the enquiry is thin, the beautiful model was wasted. The summary is not an afterthought; it is the actual result.
One source for everything
The key rule: on-screen summary, enquiry text and PDF come from the same source. What the buyer confirms appears word for word in the enquiry. When versions differ, questions and disputes follow.
What belongs in it
| Block | Content |
|---|---|
| Configuration | every choice as a line, dimensions in the buyer's unit |
| Checks | passed, warning, open – with the reason |
| Parts | parts overview or bill of materials, marked as binding or indicative |
| ID | a configuration code to reopen it |
| Notes | example values, "price and feasibility to be confirmed" |
| Contact | only what is needed; data minimisation under the GDPR [2] |
Interaction
- Every line links back to the matching step.
- Changes to price or check results are announced as status messages so screen-reader users notice them [1].
- Beside the form, offer "copy text" and "download PDF" so buyers can pass the configuration on internally.
- Errors on sending appear visibly and in plain words, never only in the console.
Examples from the library
In the restroom building example one function produces the summary and the PDF, which shows a 3D view and the floor plan. In the chemical store every summary line appears word for word in the enquiry text and PDF; the sectional door adds every check result. Example configurators, fictional products, example values.
What happens next is covered under request for quote.