Connecting your product catalog
Before ScentXP can power your fragrance experiences — enrichment, recommendations, search, conversational discovery — it needs to know which perfumes you sell. This connection is made through a Product Feed: a structured CSV file that maps your catalog to WikiParfum’s database using EAN (barcode) codes. The Product Feed is the foundation for all ScentXP technologies. It determines which products appear in Fragrance Library, ScentBot, recommendations, and search results.Why this matters
- Recommendations stay within your catalog — users only see products they can actually buy from you
- Enrichment is automatic — once mapped, every product in your feed gets olfactive data, ingredients, imagery, and family classification
- New launches sync automatically — update your feed and the enrichment follows
- Search results are scoped — restrict search and discovery to your assortment
The system exclusively imports perfumes. Products such as deodorants, shampoos, body lotions, body sprays, body splashes, gift sets, travel sets, discovery kits, and other non-perfume items will be excluded from the feed and not imported.
How catalog mapping works
Once your Product Feed is provided:- EAN matching — each EAN in your feed is matched against WikiParfum’s database of 31,000+ perfumes
- Enrichment — matched products receive olfactive classification, ingredients, imagery, perfumer data, and more
- Scoping — recommendations and search results can be restricted to your catalog
- Sync — feed updates are reflected automatically, keeping your enriched catalog current
What you get back
Once the Product Feed is integrated, each matched product is enriched with:- Perfumer — the creator behind the fragrance
- Brand and sub-brand names
- Family and subfamily — olfactive classification
- Gender — masculine, feminine, unisex
- Launch date — year and month
- Expert reviewed — whether the perfume has been personally evaluated by a ScentXP olfactive expert (typically iconic and best-selling perfumes)
- Classification — niche, prestige, or mass
- Discontinued status
- Ingredients — full ingredient breakdown with proportions and hero flags
- Quadrification — proprietary visual representation of the fragrance’s olfactive profile
Feed submission options
Manual feed
ScentXP can manually upload the feed through the management system. This option works well when your product list doesn’t change frequently.Automatic feed
ScentXP can configure the feed to update automatically on a schedule (daily, weekly). This is ideal when your assortment changes regularly — new launches, discontinued products, seasonal rotations — and ensures your enriched catalog stays current without manual intervention. For automatic feeds, you can host the CSV file on your own infrastructure or use one provided by ScentXP:| Method | Description |
|---|---|
| Public URL | A publicly accessible URL pointing to the CSV file |
| Amazon S3 | An S3 bucket — yours or one provided by ScentXP |
| Google Cloud Storage | A GCS bucket — yours or one provided by ScentXP |
| SFTP | An SFTP server — yours or one provided by ScentXP |
Using the Product Feed in the API
Once your catalog is mapped, the WikiParfum API provides full programmatic access to your enriched catalog — including catalog-scoped search, EAN-based lookups, and filtered recommendations. See the WikiParfum API documentation for implementation details.Next steps
Feed Format
Required and optional CSV columns, custom labels, and ScentBot-specific fields.
FAQ
What is an EAN, EAN vs UPC, and why EANs are required for integration.

