Technology

Building a washroom and locker configurator: data, geometry, plan view and mobile

Technical decisions for a 3D toilet cubicle and locker configurator: size tables, parametric geometry, finishes, plan view, PDF, mobile and privacy.

Short answer: a toilet cubicle and locker configurator is best built parametrically. Panels, pilasters, doors and locker carcasses are generated in the browser from your size tables, instead of loading a CAD model for every variant. Material and finish are data, the plan is drawn from the same dimensions as the 3D model, and the PDF reuses both. The hard technical questions are how a long room looks on a phone, load time, privacy, and how you keep finishes and sizes up to date yourself.

Washroom cubicle & locker configurator – preview of the example configurator
Example configurator · fictional product · example values. Loads only when you click. Open the demo page →

What data does the build need?

For a configurator with your systems we collect three kinds of material at the start:

  • Size tables: widths and depths per cubicle range, heights, floor clearance, panel thickness per material, door widths, duct wall dimensions, column widths, locker depths, tier heights and bench sizes.
  • Rules: which combinations exist, which clearances you want checked and with what wording. These rules are described in washroom cubicle configurator rules.
  • Appearance: drawings or photos of pilasters, headrails, legs, hardware, locks and edge details, plus your finish list with colour values or patterns.

Whatever exists only in your sales office's heads, we write down together. That part can take more work than the 3D geometry.

Parametric geometry or CAD models?

Cubicles and lockers are made of a few basic shapes in many sizes: panels, posts, profiles, doors, carcasses. That favours geometry generated from parameters. A run of seven cubicles is then not its own file but the same rule applied seven times.

ApproachSuitsLimits
Parametric, in the browserPanels, pilasters, doors, headrails, locker carcasses, benches, the roomDetails such as hardware are simplified
Individual parts from CAD, converted for the web (for example to glTF)Hardware, locks, legs, sanitarywareData must be reduced and stripped of know-how
Whole variants from CADA few fixed modelsHardly manageable when sizes are free

A mix is also possible: parametric panels and carcasses with a few parts from your own data. glTF, a royalty-free Khronos Group specification for transmitting and loading 3D models, is one format for those parts [1]. How STEP or IGES data becomes a web model is covered in CAD to web 3D configurator.

Our washroom cubicle and locker configurator is an example configurator with a fictional product and example values. It uses parametric geometry only: cubicles, WCs, urinals, basins, the duct wall, lockers, benches and the room are built in code for the demo, with no manufacturer CAD files. Tiles, wood grain and shadows are also generated in the browser, without image files.

How are material and finish handled?

A panel material is more than a colour. In the example each material has its own data: panel thickness (12, 13 or 18 mm), edge detail (dark core edge, colour-matched edge, solid timber lipping) and whether a grain is shown, plus a colour list per material. Panel thickness even feeds a check: the free turning circle in the large end cubicle is reduced by twice the panel thickness.

For your project, finishes arrive as a table with name, colour value or pattern and the material they belong to. Colours on screen are always approximate, and the demo says so. Your sample card remains the binding choice.

How are the plan and PDF produced?

Specifiers work with plans. So the demo has a top-down vector plan with dimension chains, door swings, turning circle and corridor, in German and English. It is drawn from the same layout data as the 3D model, and the same drawing goes into the PDF, so the model, the plan and the PDF cannot drift apart.

Two details show why this matters. First, the independent QA found that an early version dimensioned the corridor from the standard cubicles while the 3D label and the check used the deeper end cubicle; that was fixed. Second, on narrow screens the spacing of the dimension chains is set in screen pixels, and labels that do not fit are left out rather than printed on top of each other.

An obvious next step for specifiers would be a DWG or BIM object download. That is not implemented in the demo and depends on what data you are willing to release.

What do room size, mobile and load time mean here?

A washroom is long and shallow. With eight cubicles, a large end cubicle, five urinals and four basins, the example room is 15 m long or more, and on a phone it becomes small in the angled view. The demo handles this three ways: a steeper angled view on narrow screens, a camera that frames the run, urinals and vanity as separate groups, and the plan as a readable alternative. For very long rooms it cannot be solved completely.

On load and processing:

  • The demo renders only when something changes. In QA the draw-call count stayed unchanged over three idle seconds, including after the doors had opened.
  • Materials are created once and only recoloured, rather than rebuilt on every colour change.
  • Doors open as a group. Opening a single door by clicking it is not implemented in the demo.

All device tests were emulated in a headless browser at eight screen sizes from 360 to 1,440 px wide, not on physical phones.

How usable must the configurator itself be?

The usability of the configurator is a different question from the accessibility of the cubicle being planned. For the interface there are the W3C's WCAG 2.2 guidelines; among other things they set a minimum target size of 24 by 24 CSS pixels at level AA and 44 by 44 CSS pixels at the enhanced level [2]. In the demo no button was smaller than 44 px at any of the eight screen sizes tested. Users who prefer reduced motion see the doors in their end position without animation. We have not carried out a full WCAG audit of the demo.

What about privacy and third-party services?

In the demo, entries are neither sent nor stored. There are no cookies, no local storage and no requests to other servers; fonts and libraries are served from the same host. Only the names of features used are counted. In your project you decide where enquiries go and whether you use analytics; that belongs in your website's privacy policy.

How do you maintain it later?

Because sizes, ranges, finishes and check values live in tables rather than in the 3D model, new colours, an extra cubicle width or a changed limit can be added without new geometry. New components, such as another pilaster profile, do need modelling work. Before the project starts, agree who approves changes and how often your finish list changes, and put it in the specification.

Example configurator · fictional product

Washroom cubicle & locker configurator

Plan a washroom or changing room: cubicle row, end cubicle, duct wall, urinals and vanity, or locker banks with benches – with a plan view, a clearance check and a PDF enquiry.

Partitions, guarding & shelving · Dimensions and sizes · Colours · Materials and finishes

Next step

Who this kind of configurator suits is covered in locker and washroom cubicle configurator for manufacturers, and the sales process in enquiries from a washroom and locker configurator. For the project process, see custom 3D configurator development.

Frequently asked questions

Do we need CAD data?

Not necessarily. Size tables, drawings and photos are enough for parametric panels and carcasses. CAD data helps with hardware and locks.

Does it run in our existing website?

Yes, as its own page or embedded, independent of your CMS.

Which languages are possible?

The demo runs in German and English, including the plan and the PDF. Further languages are set up per project.

Sources

  1. Khronos Group, glTF – Runtime 3D Asset Delivery, read 14 November 2026: khronos.org/gltf/
  2. W3C, Web Content Accessibility Guidelines (WCAG) 2.2, success criteria 2.5.5 and 2.5.8, read 14 November 2026: w3.org/TR/WCAG22/

Read next