A bathroom collection should make buying easier. Yet many ranges grow one attractive product at a time until the catalogue contains overlapping sizes, isolated finishes, incompatible tops and slow-moving variants. The result is more samples, more data, more stock exposure and more ways to send the wrong component.
Range architecture is the discipline of deciding which customer needs the collection will serve, which choices deserve a stock-keeping unit (SKU), and which choices should remain configurable. It is valuable to distributors, retailers and private-label teams planning bathroom vanities, mirrors, mirror cabinets and coordinated accessories.
Begin with customers and rooms, not products
Define the target use cases before selecting models. A compact apartment bathroom, a family bathroom, a hospitality guest room and a premium renovation have different storage, size, installation and price expectations. Create a short job statement for each segment: who uses the room, what must be stored, which installation constraints recur, and what buying decision the assortment should simplify.
Use real channel information where available: search terms, quotation requests, returned-product reasons, installer questions, sell-through by size and finish, and gaps identified by account teams. Treat opinions as hypotheses until evidence supports them.
Choose the collection’s organizing logic
A range can be organized by design family, room size, construction route, price position or installation type. Select one primary logic that customers can understand. Secondary filters can help discovery, but they should not turn every combination into a separate promise.
For example, a vanity family may share its front language and handle detail across several widths, while a mirror family uses matching proportions. The assortment can then offer a small number of deliberate finish routes rather than every finish on every model.
Review the existing bathroom vanity collection, mirror formats and mirror cabinet options as product-family references. Final range decisions still require model-level feasibility, sample and commercial review.
Create a good-better-best role for each offer
Price tiers work only when each step has a clear customer reason. Define which material, storage, finish, hardware, top or mirror function changes between tiers. Avoid creating a “better” SKU that is different but not meaningfully more useful.
Document the value story in observable terms. “Two full-depth drawers with a declared plumbing zone” is clearer than “premium storage.” “Front-lit mirror with a named control behavior” is clearer than “advanced smart design.” This language helps product data, staff training and supplier specifications remain aligned.
Build a dimension ladder
Map common room widths and service constraints in the target market. Select a limited ladder of vanity sizes that covers the intended segments without clustering models too closely. Show external width, usable storage, basin arrangement, door or drawer movement and required side clearance.
Do the same for mirrors. A matching width may be appropriate in one design family, while another may need deliberate insets or a vertical format. Coordinate mirror size with tap height, lighting, power location and wall edges. A collection should provide proportion guidance without implying that one rule fits every room.
Control finish proliferation
Every finish adds samples, colour records, component matching, photography, product data, quality limits and potential stock. Score a proposed finish against customer relevance, compatibility across models, repeat-order control, component availability and differentiation from existing choices.
Use a core palette for stocked or regularly ordered options and an extended palette for project review. Define each finish through substrate, process, colour, sheen, texture, grain direction and edge treatment. Names alone are too ambiguous to support repeat orders.
Separate the platform from the options
A product platform contains the elements that should remain stable: cabinet construction, fixing interface, drawer geometry, top support, electrical layout or packaging footprint. Options are the controlled variables layered onto that platform.
| Decision | Platform candidate | Controlled option |
|---|---|---|
| Cabinet | Construction and internal geometry | Width, front style or declared finish |
| Vanity top | Support and attachment logic | Material, edge or basin arrangement |
| Mirror | Rear structure and mounting route | Size, frame finish or selected functions |
| Packaging | Protection principles and label fields | Model-specific inserts and graphics |
Platform thinking can reduce unnecessary variation, but only when changes remain technically valid. A different width, top weight or mirror component may require new structural, electrical, packing or documentation review.
Define compatibility rules
Create a matrix showing which cabinet, top, basin, tap and mirror combinations have been reviewed. Mark combinations as approved, conditional or not offered. Include dimensional interfaces, colour coordination, mounting responsibility and destination-specific limitations.
Compatibility must be based on drawings and samples, not on product names. A basin can fit a top opening but conflict with a drawer or tap. A mirror can match the width but cover the electrical point. A clear matrix prevents sales teams from building unsupported packages.
Decide what to stock and what to configure
Stock decisions should reflect demand evidence, replenishment risk, model commonality, damage exposure and obsolescence. A high-choice website does not require every combination to be physically stocked. Label configured or project-order products accurately and communicate the approval steps that affect timing.
For configured products, limit choices to a governed menu. Record option codes on quotations, drawings, purchase orders, labels and inspection documents. Free-text descriptions create avoidable errors.
Plan product data as part of the assortment
Each SKU or option needs a consistent data set: title, model code, dimensions, materials, finish, included parts, installation information, care guidance, images, drawings, package dimensions and applicable documents. Assign ownership for updates and identify the source of every technical field.
Do not copy claims between related models without verification. A change in construction, hardware, electrical configuration or packaging can make the old data inaccurate. The document verification page outlines the model-and-scope questions to apply to supporting evidence.
Test the range before launch
Build a small assortment board or digital matrix, then ask sales, service, installation and procurement teams to complete realistic customer scenarios. Can they choose a compatible package? Are key dimensions visible? Do two SKUs solve the same need? Is a missing size more important than another finish?
Sample representative platforms and risk variants, not just the most photogenic model. Review construction, finish range, interfaces, function, labels and packing. Establish which changes require a new sample or document review.
Use lifecycle rules after launch
Set a review cadence and decision rules for keeping, revising or removing SKUs. Combine sell-through with margin, returns, claims, stock age, quotation conversion and strategic role. A low-volume model may still fill an essential size gap; a high-volume model may create unacceptable service cost. Record the reasoning.
Plan transitions carefully. Identify last-order dates, replacement models, spare-part implications, website updates and customer communication. Avoid silently replacing a specification under an existing code.
Turn range logic into a sourcing brief
Use the ArcQuay product matrix to shortlist families, then document target segments, size ladder, platform rules, finishes, compatibility and anticipated quantities. When that architecture is clear, send the range brief for model-level review. A disciplined assortment makes sampling, data management and future replenishment easier to control.