Quick answer
Prepare a multi-SKU perfume project by giving each variant a unique specification, identifying genuinely shared components, confirming quantities and recording approvals before release. A collection-level approval should not hide an unapproved scent, label or box.
This is an illustrative planning workflow, not a report of a completed customer project. The example uses three hypothetical scent variants, A, B and C, to explain the decisions a brand buyer and manufacturer need to resolve. It contains no customer results, delivery promises or claimed cost savings.
What does the illustrative project include?
Assume a brand is considering three fragrances in the same bottle format. It would like a consistent cap and box structure, with different fragrance names and artwork. This is a proposed specification for comparison, not a statement that Laeyo stocks these components or has already approved this configuration.
Create a separate line for each variant. Record its product code, scent brief, proposed fill volume, bottle reference, pump, cap, decoration, label artwork, box artwork and requested quantity. A component counts as shared only when its specification is identical and the supplier confirms that the same version can be used.
How should shared and unique components be recorded?
Use a bill of materials, or BOM, that separates physical components from their decoration and artwork.
- Bottle: identify the proposed common bottle and any variant-specific finish
- Pump and cap: record exact references and the configuration requiring approval
- Fragrance: maintain a separate reference and approval for each scent
- Label and box: distinguish a shared size or structure from different printed artwork
- Finished product: connect every component revision to the correct SKU
Do not describe all boxes as one component merely because they have the same dimensions. Different printed versions still need separate identification, quantity planning and approval.
What should be confirmed about quantity?
Laeyo’s perfume MOQ is 1,000 bottles. How that quantity can be allocated across scents, sizes or decoration variants must be confirmed for the proposed project. This example does not assume that 1,000 bottles can be split evenly across three SKUs.
Ask for the proposed finished quantity by SKU and any separate component purchase requirements. Record who owns unused customized components and how those components would be handled if the launch changes. See the multi-SKU MOQ and cost guide for the quote comparison method.
How should approvals be organized?
Give each approval a named owner, a dated reference and a clear scope. A fragrance approval establishes the agreed scent reference; it should not be treated as approval of packaging artwork. Likewise, approving an image of a bottle does not establish approval of the complete filled product.
For this example, maintain separate records for each fragrance, the assembled component configuration, each printed artwork version and the final SKU specification. Where a physical sample or test is required, agree its purpose, acceptance criteria and relationship to the production specification.
Laeyo’s sample R&D takes about three days, excluding customer confirmation, communication and shipping. That timing should not be treated as a complete sample-to-production schedule.
What belongs in the production release check?
Before authorizing production, ask the project team to reconcile:
- Approved references against the latest BOM and artwork versions
- Requested quantities against the accepted SKU allocation
- Component availability against the planned release date
- Agreed quality checks and the people responsible for approval
- Market-specific label and document requirements
- Packing instructions, destination and shipment assumptions
An unresolved item should have an owner and a decision date. If one SKU remains unapproved, discuss whether a separate release is feasible and what it changes commercially. Do not assume the rest of the collection can ship independently.
How would success be demonstrated?
For a real project, useful evidence would include the approved specification matrix, dated approval records, production release record and documented results against agreed criteria. Without those records, it would be misleading to claim a successful launch, a delivery improvement or a defect reduction.
How can a brand begin?
Send the proposed SKU list and identify which components you want to share. Laeyo supports B2B brand OEM/ODM development; product examples are development references rather than ready-stock retail offers. Review the private label process or submit a project brief. Contact [email protected] or WhatsApp +85269176570.