Buyer-ready working document
Bathroom Product Development Brief for New Collections
Copy the template below into a document or email before asking a factory to quote or develop a collection. Complete what you know, label genuine unknowns, and attach the referenced drawings or files.
The aim is not to freeze every detail on day one. It is to give the buyer and supplier one shared record for market intent, product scope, customization, evidence, samples, quantities, packaging, and delivery.
Copy, complete, and send
Bathroom Product Development Brief Template
Use one brief for one collection or closely related product family. If categories have different compliance, tooling, packaging, or delivery needs, give each category its own product schedule beneath the main brief.
BATHROOM PRODUCT DEVELOPMENT BRIEF
Document owner:
Brief version and date:
Project / collection name:
Buyer company:
Main contact and decision team:
Requested supplier response date:
1. MARKET
Destination country or region:
Sales channel:
Target customer / user:
Project or use environment:
Target retail price:
Target wholesale / landed-cost range:
Competitor or reference products:
Planned launch window:
2. PRODUCT
Category:
Product type / model concept:
Collection size and assortment:
Target dimensions:
Installation type and site interfaces:
Material or substrate requirement:
Finish and color:
Required functions:
Must-not-change requirements:
Reference drawings, images, or samples attached:
3. CUSTOMIZATION
Existing supplier model acceptable? Yes / No / To review
New mold or tooling expected? Yes / No / To review
Logo location and method:
Packaging design:
Color or finish customization:
Hardware / component preferences:
Manuals, labels, and carton marks:
Design, tooling, and artwork ownership questions:
4. COMPLIANCE AND DOCUMENTATION
Destination market:
Applicable standards or buyer specifications:
Required certificates or test reports:
Required test conditions and acceptance criteria:
Required product markings and labels:
Electrical, water, installation, or accessibility inputs:
Required drawings, data sheets, manuals, and declarations:
Evidence must identify which model / component it covers:
5. SAMPLE AND APPROVAL PLAN
Sample type and quantity:
What the sample must prove:
Tests or inspections required:
Approval decision maker:
Feedback format:
Target approval date:
Pre-production sample required? Yes / No / To review
6. COMMERCIAL, PACKAGING, AND DELIVERY
Sample quantity:
Trial-order quantity:
Expected volume / annual forecast:
Target MOQ:
Model, size, and finish mix:
Unit packing requirement:
Master carton / wooden-frame requirement:
Barcode, label, manual, and carton-mark files:
Delivery destination:
Incoterm requested:
Required shipment date or delivery window:
Phased shipments or site restrictions:
7. ATTACHMENTS AND OPEN ITEMS
Attachment list:
Open question:
Owner:
Decision / evidence needed:
Due date:
Effect if unresolved:Do not turn guesses into specifications. Write “to review” when a field depends on supplier engineering, model selection, testing, or a commercial discussion. A visible unknown is safer than a hidden assumption.
Project and Target-Market Summary
Market inputs tell the supplier what the product must achieve commercially and where technical requirements may come from. They also stop a reference image from becoming the whole brief.
| Field | What to enter | Why the supplier needs it |
|---|---|---|
| Destination country or region | Every intended sales or installation market. | Market affects documentation, labels, connections, electrical inputs, and other review items. |
| Sales channel | Retail, distributor, e-commerce, hospitality, property project, or another defined route. | Channel shapes assortment, packing, presentation, and replenishment needs. |
| Target customer and use environment | Who uses or buys it, plus residential, hotel, public, or other conditions. | The supplier can question features that do not fit the intended user or setting. |
| Price position | Target retail price and the cost basis you use internally. | The team can discuss design, material, component, and packaging trade-offs against one commercial target. |
| Competitor references | Links, model names, photos, or samples, with notes on what to match and what to avoid. | A reference becomes useful direction instead of an ambiguous request to “make it similar.” |
| Launch window | Target launch period and any fixed buyer milestones. | The supplier can identify which decisions must be made before sampling or production planning. |
MICAWA states that product development can be coordinated around target market, positioning, price tier, assortment, and delivery requirements. Buyers preparing a private-label range can use the guidance for brands and private-label programs to define the commercial context first.
Product Scope, Positioning, and Customization
This section converts a collection idea into a product schedule. Name each category, intended model type, installation condition, dimension target, finish, function, and reference file. Do not assume that one note applies to every item in the range.
Define the product before the decoration
| Field | Complete it with | Decision it unlocks |
|---|---|---|
| Category and product type | For example, basin, toilet, vanity, faucet, shower system, bathtub, or shower screen, followed by the intended configuration. | Routes the request to the correct product and engineering discussion. |
| Collection size and assortment | Model count, size variants, finish variants, and the role of each item. | Shows whether the work is one item, a family, or a coordinated launch. |
| Dimensions and installation | Target envelope, mounting or installation type, connection points, and site interfaces. | Exposes conflicts that a styling reference alone cannot show. |
| Material, finish, and functions | Required outcome, known specification, prohibited option, or a clear request for supplier proposals. | Separates fixed requirements from areas open to engineering or sourcing options. |
| Reference files | Numbered drawings, images, samples, finish standards, and a short note explaining each reference. | Creates a traceable basis for quotations and sample reviews. |
State customization requests without assuming they are standard
Ask whether an existing supplier model can be adapted or whether new development may be needed. List the requested logo, color, finish, hardware, components, packaging, labels, and manuals as discussion inputs. MICAWA’s documented customization scope says these options, molds, components, and tooling charges require category-level confirmation.
If the design is still open, first decide whether the program fits an OEM or ODM route. The OEM versus ODM decision guide explains how design maturity and responsibility change the brief.
Required Specifications and Documentation
Do not write only “must comply with local standards.” Name the destination market, the standard or buyer specification if known, the required evidence, the test conditions, and the exact model or component that each document must cover.
| Field | What a usable entry contains | Common gap to avoid |
|---|---|---|
| Applicable requirement | Standard, regulation, tender clause, retailer specification, or internal requirement. | Treating a destination country as a complete technical specification. |
| Evidence required | Certificate, test report, declaration, drawing, data sheet, label artwork, or manual. | Accepting a company-level document as proof for an unrelated model. |
| Test and acceptance basis | Method, conditions, sample identity, pass criteria, and who reviews the result. | Using words such as “tested” without a report or acceptance rule. |
| Installation inputs | Connections, electrical supply, water conditions, clearances, fixing conditions, and interface drawings relevant to the product. | Discovering a site-interface conflict only after the appearance sample. |
| Marking and document language | Required product marks, label content, manual language, carton marks, and artwork approval route. | Leaving packaging and regulatory text until production files are due. |
Evidence rule: Keep the supplier statement, supporting file, covered model or component, issue or review date, and any limitation together. Standards participation is not the same as model-specific certification.
Sample, Approval, Packaging, Quantity, and Delivery Inputs
A supplier cannot build a useful sample plan unless the brief states what each sample must prove. An appearance sample may answer color and proportion questions, while an engineering or pre-production sample may need different acceptance criteria.
Write an approval plan, not just “sample required”
- Name the sample stage and quantity.
- List the exact questions that the sample must answer.
- Identify tests, inspections, and reference documents.
- Name the buyer-side approver and feedback format.
- State whether an approved pre-production sample is required as the production reference.
Separate commercial quantities and packing inputs
| Input | What to specify | Why it must be separate |
|---|---|---|
| Sample quantity | Units needed for design review, testing, photography, or stakeholder approval. | It is not a production-order quantity. |
| Trial order | Model and finish mix for the first commercial purchase. | It may have different packing and allocation needs from the forecast. |
| Forecast and target MOQ | Expected annual volume, order frequency, and the quantity the buyer wants the supplier to assess. | A forecast is planning information, not a confirmed order or supplier policy. |
| Packaging | Unit protection, carton or wooden-frame request, artwork, manuals, labels, barcodes, and carton marks. | Product protection and market presentation need different files and approvals. |
| Delivery | Destination, requested Incoterm, shipment window, phases, and site restrictions. | A launch date is not enough to define the requested shipment basis. |
MICAWA reports support from product development through sample production, testing and validation, and volume delivery. Exact sample policy, category MOQ, lead time, Incoterm, tooling, and packaging choices still require confirmation. The OEM and ODM engineering and sampling support page outlines the capability route and the inputs teams should prepare.
Development Brief Checklist Before You Send It
A brief is ready for supplier review when a new reader can identify the requested product, the intended market, the approval evidence, and the commercial basis without reconstructing the project from separate messages.
- Market: destination, channel, user, price position, references, and launch window are named.
- Product: category, assortment, dimensions, installation, material, finish, and functions are defined or marked for review.
- Customization: existing-model, tooling, logo, color, component, and packaging requests are visible.
- Compliance: required documents, tests, labels, and model scope are stated.
- Approval: each sample has a purpose, reviewer, criteria, and feedback route.
- Commercial: sample, trial, forecast, packing, destination, and shipment inputs are separate.
Finish with an attachment register and one open-item table. For every unresolved point, record the question, owner, evidence or decision needed, due date, and effect on the quotation or development plan.
Ask MICAWA to Review Your Bathroom Product Brief
Send the completed template with your product schedule and reference files. MICAWA’s export team can review the requested scope and identify the category-specific questions needed for a development discussion.
Submit a development brief