Short answer: Use one programme cover sheet for shared business context, then create a separate technical brief for each product category. A buyer evaluating YAMATIK power connection products and BREEZE.LUX ceiling fans can align launch timing and contacts at group level, while keeping specifications, samples, evidence and release decisions specific to each brand and model.
A multi-category sourcing programme often begins with one commercial goal: serve a new market, refresh a product range or prepare a coordinated launch. That shared goal is useful. It does not make different products technically interchangeable. OCEAN STAR GROUP is the parent group for the YAMATIK and BREEZE.LUX brands; YAMATIK focuses on electrical connection products, while BREEZE.LUX focuses on ceiling fans and fan lights. Each category needs its own product questions and approval records.
Keep shared context in one programme cover sheet
The cover sheet gives every participant the same commercial frame without flattening the technical differences. Record:
- the buyer entity, sales channel and countries under consideration;
- the intended launch window and the assumptions behind it;
- forecast ranges, clearly marked as estimates until agreed;
- brand, artwork and confidentiality rules that apply across the programme;
- the decision makers and day-to-day contacts for each category;
- shared milestone dates, dependencies and the next decision required.
Give the cover sheet a programme ID, owner and revision date. When a date or assumption changes, mark what changed and who approved it. A shared schedule should show coordination points; it should not replace the product records.
Give each category its own technical brief
Make a separate brief for the YAMATIK power connection range and the BREEZE.LUX ceiling-fan range. Each should identify the exact model or product family, the target configuration, open questions and the person responsible for approval.
For a power connection brief
Specify the destination plug system, socket layout, electrical ratings, cable requirements, switching or protection features, charging needs, installation or use context, packaging and requested documents. Ask the brand team to confirm the evidence that applies to the exact finished model and market. A component or similar-model record should not be treated as proof for a different configuration.
For a ceiling-fan brief
Describe the intended room or project, fan size and style, blade and motor preferences, lighting and control requirements, mounting context, target-market documents, branding, packaging and service expectations. List the model references and any performance targets that need review. Confirm which options are available for the selected model rather than assuming that a feature on one design applies to the full range.
Use one master timeline, with category-level release gates
A single timeline helps a buyer see whether a shared launch date is realistic. It can include brief completion, model shortlist, sample review, artwork approval, document review, order release and shipment planning. Under each milestone, keep the category owner, required evidence and decision status visible.
Do not merge two approvals just because they occur on the same day. A power connection sample and a ceiling-fan sample have different review criteria. Record each approved revision separately, and state whether a decision is final, conditional or still open. If one category is delayed, update its path without rewriting the other category's approval history.
Make gaps and assumptions easy to find
Use a short open-items register with four fields: question, category and model, owner, and due date. Label unconfirmed commercial terms, market requirements and delivery dates as assumptions. Ask for written confirmation before treating them as commitments. This makes a multi-category programme easier to review and helps prevent an answer for one product from being copied into another product's file.
A simple brief structure buyers can reuse
- Programme cover: buyer, channel, target markets, launch window, forecast assumptions and shared contacts.
- Category annex: brand, product family, model references, configuration and intended use.
- Evidence and decisions: requested documents, sample criteria, approval owner and unresolved questions.
- Commercial and timing: quantity range, packaging scope, target milestones and items awaiting confirmation.
- Change record: revision, date, decision owner and a concise description of each approved change.
Buyers can explore the YAMATIK brand overview, the BREEZE.LUX brand overview, and the group's partnership route. For detailed product requirements, send each brand a category-specific brief and ask the team to confirm model fit, evidence scope and commercial terms.
Frequently asked questions
Should a buyer use one RFQ for two different product categories?
Use one cover sheet for shared business context, but keep separate technical briefs for each category. The products have different specifications, evidence and approval questions.
What can be shared across the briefs?
Markets, channels, launch timing, forecast assumptions, brand rules and programme contacts can be shared when they genuinely apply to both. Technical requirements and product documents should remain model-specific.
Can one test report or certificate cover both categories?
Do not assume that it can. Ask the responsible team to confirm the document's model, configuration, scope, validity and destination-market relevance.
What if one category is not ready when the other is?
Keep each category's approval gates and schedule separate under the shared programme view. The buyer can then make a clear decision about sequencing without treating one category's readiness as proof for the other.
This guide is a sourcing workflow, not an engineering, certification or regulatory determination. Confirm requirements and evidence for the exact product and destination market with the responsible technical and compliance teams.