For Sanitary Ware Brands
Build a Product Portfolio Around Architecture, Not Isolated SKUs
A sanitary ware brand becomes harder to manage when every new product starts as an independent design decision. Product platforms, components, finishes and market roles should work as one portfolio.
GlimmerSanitary helps organize product programs around physical architecture, development depth, visual coordination, sample approval and repeat-production references.
Review all B2B Solutions
Brand Product Program
A coherent range needs control beyond the individual product
Product identity is created across the complete range. Structure, visual details, finish, branding and revisions need to remain connected.
Platform Architecture
Define which physical products form the foundation of the portfolio.
Visual Direction
Coordinate product shape, face, control, component and finish relationships.
Market Presentation
Connect product identification, instructions and packaging to the approved platform.
Revision Control
Keep product changes connected to the current approved reference.
Portfolio Architecture
Define product roles before expanding the model count
A brand portfolio should create meaningful choices without filling the range with visually different products that solve the same requirement.
- 01
Category Role
Identify which categories belong in the product program.
- 02
Platform Role
Choose the physical architecture that forms the core of each category.
- 03
Application Position
Define whether the product serves a different installation, function or market position.
- 04
Product Tier
Separate products when physical or functional differences justify a distinct market role.
- 05
Supporting Components
Coordinate hoses, Holders, controls, accessories and connections where relevant.
- 06
Future Expansion
Leave room for new products without creating unnecessary duplication.
Product Platform Families
Use related architecture to make the portfolio easier to understand
A product family should be connected by meaningful physical relationships rather than only by finish or photography style.
Hand Shower Family
Face architecture, control format, supported spray configuration and connection relationship.
Review categoryRain Shower Head Family
Face shape, profile, mounting format and outlet architecture.
Review categoryShower System Family
Concealed or exposed architecture, water-control structure, outlets and installation planning.
Review categoryFaucet Family
Bathroom or kitchen application, outlet architecture, control platform and specialty function.
Review category
Product Design Language
Visual consistency must remain connected to the physical product system
The same geometric language can be applied across several products only when the underlying components, controls and manufacturing relationships still work correctly.
Form Language
Review profile, proportion, edge treatment, face shape and visible housing direction.
Controls
Coordinate buttons, selectors, handles and control positions where the platform supports it.
Components
Review hoses, Holders, joints, outlets and other visible parts that appear with the main product.
Functional Boundary
Do not force visual similarity when it compromises the physical product requirement.
Design consistency should follow the approved platform rather than override functional or manufacturing requirements.
Finish Direction
Approve the finish as part of the complete product range
A finish name alone does not guarantee that unrelated components or substrates will appear identical.
Core Finish Palette
Define which visible finish directions the brand needs.
Platform Availability
Confirm which finishes are supported by each approved product platform.
Cross-Category Coordination
Review products and components that will appear together.
Approved Reference
Use a confirmed physical or project reference rather than relying only on a finish name.
Brand Presentation
The brand must remain connected from the product to the package
Brand presentation can involve product identification, labels, instructions and packaging, but the available methods depend on the physical product and project.
Product Identification
Review the supported brand position and identification method.
Labels
Define the required product and carton information.
Instructions
Prepare relevant use, installation and product information for the destination market.
Packaging
Coordinate product protection with the intended commercial presentation.
Development Depth
Choose the development route according to how much the physical product must change
Private Label
An established product fits; changes focus on supported identity, documentation, finish or packaging.
OEM
Existing architecture is suitable, but visible, component or configuration changes need review.
ODM / Custom
Deeper architecture must change, existing platforms are insufficient or tooling may need review.
Final feasibility and development depth must be confirmed after the physical requirements are reviewed.
Product Approval
The approved sample connects the brand direction to repeat production
Product Sample
Review physical architecture, visible details, components and finish.
Pre-Production Review
Align the product with branding, documentation, packaging and applicable quality requirements.
Approved Program Reference
Use the approved product and revision as the reference for manufacturing handoff.
Market Preparation
Market-facing content should follow the approved physical product
Packaging and sales claims should not describe features that are absent from the approved product or unsupported by evidence.
Product Identity
Keep model or product identification connected to the approved physical configuration.
Feature Claims
Use only functions and performance claims supported by the actual product.
Instructions
Prepare the applicable installation, use and maintenance information.
Market Requirements
Identify destination-market label or documentation requirements for review.
Package Content
Confirm the included components before finalizing product-facing information.
Revision Control
A product change must not become an undocumented new version
- 01
Current Approved Reference
Identify the physical product and revision currently approved.
- 02
Requested Change
Record the structural, functional, finish, brand or packaging change.
- 03
Impact Review
Check whether components, tooling, quality requirements or documentation are affected.
- 04
Updated Approval
Confirm the revised physical or project reference where required.
- 05
Production Release
Use only the latest approved revision for the next production order.
Production Handoff
The approved brand product must become a usable manufacturing reference
Once the product direction is approved, the relevant platform, components, finish, branding, packaging and revision must remain connected as production begins.
Product Reference
Keep the approved physical product identifiable.
Component Reference
Maintain the correct component set and interfaces.
Finish and Brand Reference
Keep the approved visual direction linked to the product.
Packaging and Revision
Use the current package and revision reference for production and repeat orders.
Brand Program Process
Keep the product portfolio connected from architecture to repeat supply
- 01
Architect
Define categories, platform roles and portfolio structure.
- 02
Coordinate
Align product language, components and finish direction.
- 03
Approve
Confirm samples, brand information and packaging.
- 04
Transfer
Connect the approved product and revision to manufacturing and quality.
- 05
Maintain
Use the current approved reference for future production and portfolio expansion.
FAQ
Brand product-program questions
How should a sanitary ware brand build a product range?
Start with categories and physical product platforms, then define meaningful product roles, component relationships, finish direction and market position before increasing the SKU count.
What is the difference between Private Label and OEM for a brand?
Private Label normally uses an established physical product and focuses on supported brand identification, documentation, finish and packaging. OEM is more appropriate when the physical product or component configuration needs meaningful modification.
Can several sanitary ware categories share the same design language?
Selected products may be coordinated through profile, face shape, controls, finish or visible component relationships, but the design direction must remain compatible with the physical and functional requirements of each product platform.
How are product changes managed after a sample has been approved?
Requested changes should be reviewed against the current approved product reference. If the change affects the physical product, components, finish, documentation or packaging, the updated configuration should be confirmed before the next production release.
Build the Product Portfolio
Send the current range, product references and development priorities
Share the product categories, current reference products, required physical changes, finish direction, branding position, destination market, expected quantity and packaging requirements. We will organize the relevant product and development path.