Keep Essential Oils, Fragrances and Blends Separate in Your Product Data

Separate what buyers call it from what the record says it is

A marketing name helps buyers find a product. A material category tells your team which product record and review process belong behind that name. Putting both into one title makes later mistakes easier: a floral scent name might be copied into a botanical range, or a diluted preparation might inherit text written for a different material. Keep the display name editable without allowing it to overwrite the controlled identity.

Create an unresolved category for historical rows that lack adequate information. Keep those rows available for investigation rather than forcing them into a sale-ready category. The goal is not to make every old spreadsheet look complete. It is to give your team a clear path from a legacy name to a documented, reviewed catalogue item.

Use separate fields for category, preparation and commercial variant

Start with a stable material code and a reviewed category. Add supplier code, specification version and the supporting identity description. Record whether the material is a single ingredient or a formulation, and keep declared concentration and carrier details in their own fields where they apply. A concentration value without an identified preparation and basis should remain an open question rather than a catalogue fact.

Create the sellable SKU by linking that material record to a defined pack configuration. Bottle volume, closure, artwork and set membership belong to the commercial variant. This allows several bottle sizes to share a material specification while retaining their own pack approvals. It also prevents a plain label, an existing brand and customer artwork from being mistaken for three different liquid identities.

Test the structure with explicitly hypothetical rows

The following examples are invented data rows to demonstrate a catalogue structure. They do not describe PanPan Aroma stock, formulas or confirmed specifications. In a real database, each field would point to a reviewed supplier record, and unresolved entries would block the relevant public claims.

• EX-01: display name Botanical Candidate A; category botanical essential oil candidate; identity review pending; pack bulk option pending; public release held.
• EX-02: display name Garden Scent B; category fragrance composition; formula reference F-B revision 2; botanical identity not asserted; pack configuration P-02.
• EX-03: display name Preparation C; category diluted botanical preparation; carrier and concentration awaiting confirmation; specification incomplete; public release held.
• EX-04: display name Blend D; category formulated oil blend; formula reference F-D revision 1; ingredient review pending; artwork approval separate.

Migrate old catalogue rows without laundering assumptions

Preserve the original source row, title and file reference when cleaning a legacy catalogue. Add your normalized fields next to that evidence, with a reviewer and decision date. Do not overwrite a vague source name with a polished identity and lose the distinction between what the source actually said and what the team later confirmed. Use a confidence or review-status field to make that difference visible.

Duplicate detection also needs more than a matching name. Compare supplier product codes, material specifications and preparation details before merging records. Conversely, two rows with different bottle sizes may belong to one material. Record the merge decision and retain the old references so enquiries, sample feedback and previous quotations still have somewhere to point.

Let reviewed data control pages, quotes and artwork

Agree a release checklist that covers category, identity, specification reference, image relevance and permitted wording. A product-page editor should use the approved fields rather than infer them from a photograph. If a product changes category during review, check its navigation, description, document links and artwork together. A corrected database value is useful only when the dependent outputs are corrected as well.

For a wholesale project with PanPan Aroma, identify whether you are requesting a botanical material, a fragrance direction, a diluted preparation or a finished blend. If that decision remains open, describe the intended project and ask to compare clearly identified routes. Catalogue governance supports that conversation by preserving distinctions; it does not establish current availability or approve a formula for a particular use.