One operational story, many parts.
Configurator → frozen quote/order → BOM and work → QA → dispatch and invoice.
From configurable quotes and material requirements through builds, checks and invoices, keep the commercial decision tied to real production.
THE SIGNATURE EXPERIENCE · INTERACTIVE EXAMPLE
Change the platform dimensions. Watch the drawing and *illustrative geometric requirements* update before imagining how a real parametric product could flow to a commercial snapshot.
In a real configured product, measured adjustments can influence resources and pricing. Quotes and orders should retain the resolved commercial snapshot.
Illustrative browser-only example. No customer information, backend operations, real payments or real inventory changes.
A customer wants a made-to-order trailer with selected options. The price, configuration and resource plan should still make sense when the job reaches the workshop.
↗01 / FOLLOW THE WORK
Pick a stage. See the work, the records that enter and leave it, and the Denver's Desk modules that fit.
OPTIONS → COMMERCIAL CHOICE
Choose dimensions, valid features and pricing rules, whether the offer is simple configuration or measured parametric work.
How the system should behave Parametric calculations can use length, perimeter, area, volume and formulas. No resource effect is the same as no commercial selection.
SELECTION → SNAPSHOT
Preserve the customer-approved configuration and price on the quote or order, rather than rewriting history when product definitions change.
How the system should behave Commercial history should remain frozen beyond the transaction's draft phase; later catalogue edits are new versions, not silent rewrites.
BOM → WORKSHOP
Bring materials, processes, labour and procurement into the planned job, then track the physical production stages.
How the system should behave QA gates, movements and approvals are configured to the operation; a production plan is not proof that every item was physically consumed.
BUILD → COMMERCIAL CLOSE
Record inspections and exceptions, release goods through the agreed workflow and invoice the completed customer work.
How the system should behave Traceability and serial numbers depend on the stock/QA policy. Records need to survive cancellations and corrections.
02 / THE WHOLE PICTURE
This is why a modular ERP is different from buying five unrelated tools.
Configurator → frozen quote/order → BOM and work → QA → dispatch and invoice.
This is a modelling demonstration. Production and QA features require validation of each module's actual release state and the business's control policies.
These example pages are for design and fit review. The platform technical guide explains the wider architecture; the services card demo explains migration and implementation.
03 / MAKE IT YOURS
Start with some relevant modules, change anything that doesn't fit, and get a real quote rather than a fictional preset package.