Obsidian Veil is a launch-ready, 3-SKU fragrance framework for a founder or team building a boutique fragrance house. It includes the identity, range structure, scent-direction briefs, 50ml bottle and packaging direction, launch imagery, sonic identity, documentation, and a working storefront prototype.
Acquire it as Obsidian Veil, or use it as a white-label chassis for your own house. Rebrand the storefront through a single configuration file, adapt the editable packaging placeholders, and take the system forward with your own production partners.
What you receive
One private 28-file archive containing:
Brand system: logo lockups, monogram, typography pairing, colour tokens, usage notes, and palette JSON
3-SKU range: For Him, For Her, and For Them, each built around a 50ml Eau de Parfum concept
Scent direction cards: starter olfactive direction for each SKU, with mood, key accords, suggested note pyramid, and benchmark references
Bottle and packaging direction: 50ml bottle family, outer cartons, tester/display structure, and SVG dielines for the bottle, outer carton, and tester card
Product and editorial imagery: 3 SKU product stills and 3 framework/editorial images
Launch media: 2 hero loops, 3 social clips, and a 72-second sonic identity master
Storefront prototype: a high-fidelity React, Vite, TypeScript, Tailwind, and Framer Motion storefront shell, with landing, range, product, framework, documentation, and enquiry pages
Rebrand configuration: theme.config.ts and palette.json, wired to the storefront's brand, colour, typography, and CTA system
Documentation: README, rebrand checklist, typography and component map, deployment guide, asset inventory, and licensing information
Handover: a license document and recorded walkthrough
Two ways to deploy
Launch as Obsidian Veil
Keep the name, identity, sonic signature, and visual world. Trademark clearance and filing remain your responsibility in your chosen territory.
Rename as your own house
Use the framework as a white-label chassis. Change the brand name through the configuration file and editable dieline placeholders, while keeping the range structure and creative direction intact.
License and ownership
The framework is licensed to one owner for development and launch of a single fragrance brand. You may modify, adapt, and rebrand the creative assets for that brand. Raw framework files may not be resold or sublicensed.
Once acquired, Obsidian Veil is retired from public sale.
Important production notes
This is a creative and strategic framework, not finished manufactured stock. Scent direction cards are starter briefs, not certified final formulas.
Final formulation, safety testing, IFRA and allergen review, stability testing, compliance, supplier sourcing, manufacturing, inventory, fulfilment, labelling approval, jurisdictional registration, payment setup, and commercial font licensing remain the buyer's responsibility. Final technical packaging requirements must be confirmed with the buyer's chosen suppliers.
Optional support
IP and transition advisory, including name and domain setup or an introduction to a formal IP protection service, can be quoted separately. Advisory is coordination only and is not legal advice.
Obsidian Veil is a launch-ready, 3-SKU fragrance framework for a founder or team building a boutique fragrance house. It includes the identity, range structure, scent-direction briefs, 50ml bottle and packaging direction, launch imagery, sonic identity, documentation, and a working storefront prototype.
Acquire it as Obsidian Veil, or use it as a white-label chassis for your own house. Rebrand the storefront through a single configuration file, adapt the editable packaging placeholders, and take the system forward with your own production partners.
What you receive
One private 28-file archive containing:
Brand system: logo lockups, monogram, typography pairing, colour tokens, usage notes, and palette JSON
3-SKU range: For Him, For Her, and For Them, each built around a 50ml Eau de Parfum concept
Scent direction cards: starter olfactive direction for each SKU, with mood, key accords, suggested note pyramid, and benchmark references
Bottle and packaging direction: 50ml bottle family, outer cartons, tester/display structure, and SVG dielines for the bottle, outer carton, and tester card
Product and editorial imagery: 3 SKU product stills and 3 framework/editorial images
Launch media: 2 hero loops, 3 social clips, and a 72-second sonic identity master
Storefront prototype: a high-fidelity React, Vite, TypeScript, Tailwind, and Framer Motion storefront shell, with landing, range, product, framework, documentation, and enquiry pages
Rebrand configuration: theme.config.ts and palette.json, wired to the storefront's brand, colour, typography, and CTA system
Documentation: README, rebrand checklist, typography and component map, deployment guide, asset inventory, and licensing information
Handover: a license document and recorded walkthrough
Two ways to deploy
Launch as Obsidian Veil
Keep the name, identity, sonic signature, and visual world. Trademark clearance and filing remain your responsibility in your chosen territory.
Rename as your own house
Use the framework as a white-label chassis. Change the brand name through the configuration file and editable dieline placeholders, while keeping the range structure and creative direction intact.
License and ownership
The framework is licensed to one owner for development and launch of a single fragrance brand. You may modify, adapt, and rebrand the creative assets for that brand. Raw framework files may not be resold or sublicensed.
Once acquired, Obsidian Veil is retired from public sale.
Important production notes
This is a creative and strategic framework, not finished manufactured stock. Scent direction cards are starter briefs, not certified final formulas.
Final formulation, safety testing, IFRA and allergen review, stability testing, compliance, supplier sourcing, manufacturing, inventory, fulfilment, labelling approval, jurisdictional registration, payment setup, and commercial font licensing remain the buyer's responsibility. Final technical packaging requirements must be confirmed with the buyer's chosen suppliers.
Optional support
IP and transition advisory, including name and domain setup or an introduction to a formal IP protection service, can be quoted separately. Advisory is coordination only and is not legal advice.