Modular home configurator: steps, layout zones, rules and example total
How a modular home and prefab configurator is structured: nine steps, layout zones, example rules with automatic adjustment and a total built line by line.
Short answer: a modular home or prefab configurator has three parts: a fixed order of steps, a floor plan built from zones along the length of the house, and rules that block combinations you do not offer and adjust them visibly. The total is a sum of lines that depend on length, number of modules, perimeter or floor area. Our example configurator shows this with example values of a fictional maker; your real values later sit in one data file.
In which order does the configurator ask?
The order follows the dependencies: whatever limits later choices comes first. The example has nine steps:
| Step | Choices in the example | Limits later |
|---|---|---|
| 1 Model | 1 module (3.30 m wide) or 2 joined modules (6.60 m); length 6.0, 8.4 or 10.8 m | roof, layout, foundation |
| 2 Roof | gable, mono-pitch, flat roof with parapet | sleeping loft |
| 3 Facade | natural larch, dark charred timber, fibre-cement panels; window colour, gable glazing, roof window or rooflight, entrance door position | – |
| 4 Layout | sleeping loft or ground-floor bedroom; bathroom at the rear or front; kitchen on the front or rear wall | – |
| 5 Interior | floor, walls, kitchen fronts | – |
| 6 Technology | heat pump, solar PV panels, battery storage, water tank (no output figures) | battery only with PV |
| 7 Setup | screw piles, point foundations or chassis; preferred month | – |
| 8 Summary | every line with example prices, notes and rules | – |
| 9 Enquiry | contact fields, enquiry text, PDF | – |
Each step has a heading with one sentence on what it is about; steps 1 to 7 also carry a note where the demo reaches its limits, for example: "The maker sets the foundation for the plot."
How is the floor plan built?
The plan is not a stored picture. It is built from zones along the length of the house, from the closed end to the living end with the gable glazing:
- Sleeping zone: a ground-floor bedroom 2.5 m long (3.1 m with two modules) or, from 8.4 m length, a niche under the loft of 1.4 m (1.8 m). At 6.0 m there is no separate sleeping zone.
- Core: 1.8 m (2.3 m) with the bathroom on one long side and a 0.9 m (1.2 m) hallway on the other. Two modules add a utility room.
- Living zone: the rest, with kitchen run, sofa and table.
- Loft: above the sleeping zone and core, at least 2.6 m long, with its deck 2.2 m above the floor.
All of these sizes are example values. The advantage of zones: when the length changes, mainly the living zone grows or shrinks (at 6.0 m the niche under the loft also goes), and the cut-away, plan view, floor area and PDF are right again at once. In the default set-up (1 module, 8.4 m, gable roof, loft) the demo gives about 23 m² of floor area inside and about 9 m² of loft, both marked as example values.
To make the layout readable, the roof lifts off in the layout step, the walls are cut away and the rooms get labels. The Outside, Side, Inside and Plan views can be switched at any time; in the plan a dashed line shows where the loft sits.
Which rules does the configurator check?
The demo has four example rules of a fictional maker:
- Ground-floor bedroom only from 8.4 m length; at 6.0 m the layout keeps the loft.
- Flat roof only from 8.4 m length, and a flat roof has no loft, so the bedroom moves to the ground floor.
- Chassis with wheels only for one module up to 8.4 m; otherwise screw piles are selected.
- Battery storage only together with PV; deselecting PV deselects the battery as well.
How the rules behave matters as much as what they say. Blocked options stay visible and give the reason in red, such as "from 8.4 m length". When a choice overrides an earlier one, the configurator adjusts it and says so in a short message, for example: "A flat roof has no loft: ground-floor bedroom selected." That way no enquiry arrives for a combination your rules exclude, and nobody wonders why something changed.
How is the example total calculated?
The running total adds up lines with example prices of a fictional maker; it is not a quotation and not a Modelwright price. What is useful is its structure, because each line has its own basis:
- base price per number of modules and length,
- roof per module, cladding per metre of outside perimeter, window colour per module,
- gable glazing, roof windows per window, door position, ground-floor bedroom,
- floor per m² of floor area, walls per metre of length and module, kitchen fronts,
- each technology option on its own line,
- foundation per support point (or the chassis as one line), transport and setup per module.
The demo works out the number of support points from the length: one module at 8.4 m needs 10. In the default set-up the total comes to €90,600, labelled in the summary as a total of example prices of a fictional maker. The figure in the 3D view, the summary, the enquiry text and the PDF all come from the same function, so they always match.
What goes into the enquiry?
The summary lists every step with the choice and its example price, plus notes on rules, permits and delivery date. The enquiry form asks for name, company, email, phone, the postcode and town of the plot and a message. The enquiry text carries every line; the PDF shows the outside view, the cut-away with the roof lifted and the plan. According to the independent QA round, the PDF contains every summary row and the enquiry text matches the summary. The demo sends nothing; text and PDF are created in the browser.
Example configurator · fictional product
Tiny house & modular home configurator
Plan a tiny house or small modular home step by step: size, roof, facade, layout, technology and foundation, with the roof lifting off for a look inside and a running example total.
What does your data replace?
For your range, your module widths and lengths, wall heights, roof pitches, option lists, zones, rules and prices replace the example values. They live in one data file; geometry and interface stay. Each further cladding or floor finish is one more surface. How modular buildings are implemented, from data to loading time, is covered in Building a configurator for halls and modular buildings. The sales view is in Tiny house configurator for builders, the project process on 3D configurator development.
Frequently asked questions
Where do rules like "flat roof from 8.4 m" come from?
They are example rules of a fictional maker. Your configurator uses your own rules; what is allowed on a plot is for you, the buyer and the local building authority to settle.
Why does the demo show no output figures for the heat pump or PV?
Because sizing depends on the house and the site. The demo records technology only as a wish; the maker plans the system and the connections.
Does the flow work without prices?
Yes. Steps, rules, cut-away and enquiry work without a total. Prices are a separate layer that you can show, limit to ranges or leave out.
Sources
- Demo features: "Live in this demo" list on the tiny house and modular home configurator library page, read 15 November 2026: modelwright.de/en/library/tiny-house-configurator/
- Zones, rules, price structure and default set-up: demo source code (data.js: ZONE, LOFT, RULES, PRICE; app.js: dimsOf, supports, priceLines) and schema notes; test results: QA log of 15 November 2026, independent round, emulated devices.


