Implementing outdoor structure configurators: geometry, rules, sun and mobile
How configurators for pergolas, carports, shelters, canopies and louvres are built: parametric geometry, rule tables, a sun model, motion and mobile.
Short answer: covered outdoor structures are parametric product families: the same profiles, posts and panels in many widths, depths and roof forms. A configurator for them is best built from rules and size tables, not from one model file per size. Three further building blocks keep coming up in this group: a sun model for shade, motion for opening and rotating, and a firm boundary at structure and loads. Our seven example configurators show three ways of building this, and you can read from them what suits your product.
Which approaches do the examples show?
All examples are Modelwright example configurators with fictional products, example values and our own geometry. They come from three generations and are built differently.
One engine, one product file
The glass room configurator and the pergola configurator use the same build: an engine (in its own variant for the pergola) that draws generic parts: profiles, posts, panels, tracks, dimension lines. Everything specific to the product sits in one file per product: sizes with limits and steps, options, nominal profile sizes, and rules as small functions, such as the number of sliding panels or posts. The summary beside the model uses the same rules. For a manufacturer this means a similar product is mainly a new file, not a new configurator. This older generation has English controls and no enquiry; we make no claims about it on phones.
A procedural single model
The carport configurator generates its model entirely in code: three structural layouts for timber, steel and aluminium, three roof forms, walls, a storage room and a view that shows only the structure. It is a 3D product view with rules, but without a summary or an enquiry. On phones the control dock currently covers a large part of the model; a fix is prepared but not live.
Data and application kept apart
The shelter, canopy and brise-soleil demos belong to the newest generation. Product data, texts and example rules sit in a data file; geometry, checks and the PDF in the application. All lengths are stored as whole millimetres; in the shelter and the canopy, metres or feet and inches are display only. The review, the enquiry text and the PDF are built from the same rows. According to its library page, the pool enclosure configurator also offers enquiry text, a PDF and a choice of feet and inches or millimetres.
Build parametrically or export CAD?
For covered structures, parametric geometry is usually the better foundation. A louvred roof 4.5 m wide uses the same parts as one 7 m wide, only in other lengths and quantities. When the model is generated from your size tables, every valid size is drawn correctly straight away, and files stay small because repeated parts are loaded once and then multiplied.
Your CAD data still matters for profile sections, brackets, connection details and proportions. How STEP data becomes a web model, and what is lost on the way, is covered in CAD to web 3D configurator. The louvres make the point clearly: the demo computes its four blade profiles from simple formulas. In your configurator the real profile outlines from your catalogue would sit there, and the same outlines would drive the shading calculation.
How is a sun model built in?
Two examples use a sun model, but for different questions:
- Canopies and shade sails: shade on the ground. Every roof face is projected along the sun direction onto the ground and counted in a grid. The result is the shaded area in m² and the share of the covered area in shade, for three seasons in solar time.
- Louvres on a facade: shade on the glass. For points on each pane, the configurator tests whether the ray towards the sun is blocked by a blade. The result is the share of the window in shade, for the 21st of each month, labelled as an example calculation.
Both share the core: the sun position from latitude, date, time and orientation. Both share the limit too: they count direct sun only and make no statement on energy, glare or indoor climate. If you plan such a feature, decide early which question your buyers ask, and write the limit visibly into the configurator and the PDF.
How is motion handled?
Many outdoor structures sell on a movement: the glass room's sliding front opens in percentage steps, the pool enclosure opens its roof with a button or slider, louvres rotate with the sun or play through a whole day. Technically these are states of the model driven by a slider or a button. Two things matter. First, the motion only shows what the product can do; the rule that limits the motion belongs in the checks too. Second, the newer demos respect the system setting to reduce motion and then switch without animation.
How do you maintain rules and sizes?
In every example, limits and rules live in one place, not scattered across the model. Examples from the demos, all with example values:
- Pergola: one constant for the largest post spacing, from which the post count follows.
- Carport: size ranges, the width from which it becomes a double carport, and the minimum depth with a storage room.
- Shelter: a table of cycle racks with pitch and space needs, from which capacity and fit checks follow.
- Canopy: a table of which roof type goes with which mounting and roofing.
- Louvres: profiles with their depths and an example rule for the spacing of rotating blades.
In your project, your tables replace these example values. If a module size changes later or a colour is added, you change one table, and the model, checks, summary and PDF follow.
Where is the line on structure and loads?
A configurator for covered structures must not pretend to be a structural design. A post spacing or span in the configurator is a product rule from your documents, not a calculation. Site-dependent loads, foundations and the structure are confirmed by the manufacturer and their structural engineer; permission questions are for the client and the local authority. What you can build in: only the sizes you release for a site, and a note saying who carries out the design. The louvre demo shows the pattern: when the span exceeds an example limit, it adds an intermediate support and says so in the review, as an example rule.
Phones, loading, accessibility and privacy
- Loading: on the library pages, the 3D only starts on a click. The shelter and canopy do not redraw while idle; we measured zero draw calls over several seconds in a test browser.
- Phones and tablets: the newer demos were checked in independent reviews at five to nine emulated screen sizes with controls of at least 44 px, not on real devices. For the older generation and the carport we make no phone claims.
- No 3D available: the glass room then shows a notice, and every option and the summary keep working.
- Accessibility: minimum target sizes, keyboard use and text alternatives belong in the brief, not in a later fix.
- Privacy: the shelter and canopy load no external resources, set no cookies or local storage and, where they count usage at all, record only the names of the controls used.
Three examples of the newest generation
Example configurator · fictional product
Modular shelter configurator
A modular shelter for bikes, waiting passengers, smokers or bins: choose the use, set bays, depth and height, pick roof, walls and fit-out – with live capacity, fit checks and a PDF enquiry.
Example configurator · fictional product
Canopy & shade structure configurator
Plan a canopy for a school, walkway, entrance or play area: choose the roof type, size, bays, roofing and colour – then move the sun and see how much shade it casts, and when.
Example configurator · fictional product
Brise-soleil & louvre configurator
Plan facade louvres: choose horizontal or vertical blades, profile, depth, spacing, fixed or motorised rotating blades, mounting and finish – then move the sun with the sun-path slider and see the shadow travel across the glass and the share of the window shaded (example calculation).
Next step
Collect your size tables, profile sections, colour card and the rules your sales office currently keeps in its head. That becomes the data file everything else follows. Who receives the enquiry afterwards is covered in outdoor structure configurators: enquiries and dealers; the project itself in custom 3D configurator development.
Frequently asked questions
Do we need CAD data?
Not necessarily. Size tables, drawings and photos are often enough; we use CAD for profiles and details when it suits the web.
Can several product lines share one configurator?
Yes, if they share components. The shelter shows four uses from one kit; for very different products, separate data files are clearer.
Can we maintain sizes and colours ourselves?
A self-maintenance editor is not part of our standard offer. Because rules and sizes live in tables, changes are small and quick to make.
Sources
- Demo features: the "Live in this demo" lists on each library page, read 14 November 2026: modelwright.de/en/library/


