Manufacturing · Beauty, Personal Care and Household Products
EDI and API Integration for Fragrance and Perfume Manufacturers
Fragrance houses sell luxury and mass fragrances through department stores, specialty chains and travel retail, with gift sets in holiday peaks. ECOM connects retailer orders, set assembly data, ship notices and invoices to your ERP.
What this covers
Products and business models in fragrance and perfume
Products
- Prestige and mass fragrances
- Gift sets and travel sizes
- Body mists and home fragrance
- Testers and display units
Business models
- Brands and licensed fragrance houses
- Contract fragrance manufacturing
- Wholesale plus online
Scenarios
Where fragrance and perfume manufacturers lose time and margin
Recurring problems for this kind of business, how ECOM connects the systems and documents involved, and what you gain. Bring your own example and we will work through it with you.
-
Holiday gift set peaks
- The problem
- Most volume lands in a few weeks, with sets assembled from components that must be on hand.
- How ECOM helps
- ECOM maps gift-set orders to component availability in the ERP and maps supplier 855s and 856s for components.
- What you gain
- Planners see whether components for a set are on the way before committing to a ship date.
Talk to an EDI/API Expert about holiday gift set peaks Share a sample 850 Purchase Order, 855 Purchase Order Acknowledgment and 856 Advance Ship Notice, or describe what goes wrong, and we will show how it would map to your ERP.
-
Strict channel control
- The problem
- Prestige brands manage which retailers sell which items, so item setup and allocation matter.
- How ECOM helps
- ECOM maps retailer item setup and your allocation rules so orders from each channel are checked against what that channel may order.
- What you gain
- Orders outside the channel plan are held for review.
Talk to an EDI/API Expert about strict channel control Share a sample 832 Price/Sales Catalog, 850 Purchase Order and 846 Inventory Inquiry/Advice, or describe what goes wrong, and we will show how it would map to your ERP.
-
Flammable and regulated shipping
- The problem
- Fragrance shipping carries carrier and regulatory handling rules that appear on shipping paperwork.
- How ECOM helps
- ECOM carries hazard handling data from your logistics systems onto shipping paperwork where the carrier or customer asks.
- What you gain
- Shipping paperwork carries the handling data your logistics team maintains.
Talk to an EDI/API Expert about flammable and regulated shipping Share a sample 856 Advance Ship Notice and 945 Warehouse Shipping Advice, or describe what goes wrong, and we will show how it would map to your ERP.
Who you connect with
Trading relationships for fragrance and perfume manufacturers
Typical relationships. Which of them apply, and how each one wants to connect, depends on your business.
- Department stores and specialty chains
- Order launches and sets.
- Travel retail and duty-free operators
- Order for airports and ports.
- Online retailers
- Order for direct shipment.
- Component suppliers
- Glass, caps and cartons with long lead times.
- Carriers and 3PLs
- Handle regulated shipping.
Partner guides: Retailer guides · eCommerce and marketplace guides · 3PL and logistics guides
Typical workflow
Where ECOM connects your systems and trading partners
The pattern below is typical for fragrance and perfume manufacturers, not one partner's confirmed requirements. Each trading partner publishes its own guide; confirm the details with that partner.
- Your plant and ERP→Department or specialty retailer 832 Price/Sales Catalog Sends item, description and price data for the customer to set up.
- Department or specialty retailer→Your plant and ERP 850 Purchase Order Orders matched against allocation for launches and sets.
- Department or specialty retailer→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
- Your plant and ERP→Department or specialty retailer 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
- Your plant and ERP→Department or specialty retailer 856 Advance Ship Notice Describes what is shipping, how it is packed and how it is labeled.
- Your plant and ERP→Department or specialty retailer 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
- Your plant and ERP→Component supplier 850 Purchase Order Glass, closure, carton and set components.
- Component supplier→Your plant and ERP 855 Purchase Order Acknowledgment The supplier confirms quantities and dates for bottles, caps and fragrance components.
- Component supplier→Your plant and ERP 856 Advance Ship Notice Bottle, cap, pump and fragrance-oil shipments with quantity and lot, used to plan receiving ahead of a set or filling date.
- Your plant and ERP→Department or specialty retailer 846 Inventory Inquiry/Advice Available inventory for holiday programs.
Launch and set setup
Item data (832) covers fragrances, sizes and sets.
Allocate and take orders
Orders (850) post against allocations; changes (860) follow.
Assemble sets
Component purchasing (850) and supplier notices (856) support set assembly.
Ship notice
The 856 describes cartons and sets.
Invoice
The 810 follows shipment.
EDI and API exchanges
The documents behind the workflow
X12 transaction sets typical for this workflow, with what each carries here. Select a code for the full transaction reference.
| Document | Direction | What it carries for fragrance and perfume manufacturers |
|---|---|---|
| 832 Price/Sales Catalog | You send | Sends item, description and price data for the customer to set up. |
| 850 Purchase Order | You receive | Orders matched against allocation for launches and sets. |
| 860 Purchase Order Change Request | You receive | Changes to open orders: quantities, dates or cancellations. |
| 855 Purchase Order Acknowledgment | You send | The order acknowledgment: confirms the order or reports differences from what was requested, including dates. |
| 856 Advance Ship Notice | You send | Describes what is shipping, how it is packed and how it is labeled. |
| 810 Invoice | You send | Bills for what was shipped, tied to the order and the ship notice. |
| 850 Purchase Order (supplier side) | You send | Glass, closure, carton and set components. |
| 855 Purchase Order Acknowledgment (supplier side) | You receive | The supplier confirms quantities and dates for bottles, caps and fragrance components. |
| 856 Advance Ship Notice (supplier side) | You receive | Bottle, cap, pump and fragrance-oil shipments with quantity and lot, used to plan receiving ahead of a set or filling date. |
| 846 Inventory Inquiry/Advice | You send | Available inventory for holiday programs. |
Other exchanges you may meet
- Retailer portals
- GS1 labels
Where a trading partner offers an API, a portal or file exchange instead of EDI, ECOM scopes that connection alongside the EDI ones. Functional acknowledgments (997 or 999) report validation results, including rejection; they do not prove business acceptance or ERP posting. Which acknowledgments and business responses each partner expects is confirmed with that partner.
Operational detail
Allocation, sets and regulated shipping
Allocation and set assembly are planning decisions in the ERP. The integration brings in orders in a form the allocation logic can use, and returns confirmations and ship notices that reflect assembled quantities. Shipping classification and paperwork stay with your logistics team.
Variants, sizes and multipacks
Personal care and household lines have many shades, scents, sizes and multipacks. Item setup with retailers has to match what orders, ship notices and invoices carry.
Batch and date codes
Many products carry batch or date codes. Where a customer asks for them on shipping documents, they come from the production or warehouse system.
Promotions and displays
Retailers order promotional displays and seasonal sets that ship on specific dates. Orders and changes need to reach the plant in time.
Connected systems
Systems that send and receive this data
Documents are only useful when they reach the systems that run the business.
- ERP
- Warehouse management
- Retailer portals
- Packaging suppliers
ERP integration guides: SAP S/4HANA · Oracle NetSuite · Microsoft Dynamics 365 Business Central · Infor CloudSuite Industrial (SyteLine) · Epicor Kinetic · SAP Business One · All ERP guides
Onboarding and monitoring
From first requirement to daily exception handling
Confirm the requirement
Obtain each partner's implementation guide or specification, for example from your department or specialty retailer, and agree which documents, versions and data are in scope.
Map to your systems
Map each document to the fields in your ERP and warehouse management so the data posts without re-keying.
Test with the partner
Exchange test documents and review the results with the partner before go-live, including changes, cancellations and error cases, not only the simple order.
Validate, acknowledge and monitor
A 997 or 999 reports the validation result of the document as received, including rejection; it does not show that the business accepted the content or that your ERP posted it. Business responses are separate: an 855 for orders, an 824 for application errors. Monitoring can show what is late, missing or rejected, once it is set up with you.
Resolve exceptions
Which failures and late documents are watched, who is alerted and how each is resolved are agreed during onboarding. Rejected or unacknowledged documents can then go to the people who can fix them, with the document and the reason in view.
Example exceptions for fragrance and perfume manufacturers
| Exception | Example handling, once configured |
|---|---|
| Order exceeds allocation | An order above the allocation set in the ERP can be held for review. |
| Component delay affects a set date | A late supplier 856 or missing confirmation can be flagged against the set date. |
Illustrative examples of exceptions a team in this industry may need to review. Each check compares data from your ERP, WMS, trading partner documents or scans, where those are available. Which conditions are checked, who is alerted and what happens next are configured with you during onboarding. This is not a screenshot of a live system or a list of built-in checks.
How ECOM helps
ECOM products and services that apply
Each partner connects in the way it can support. These products cover the connections and visibility manufacturers need most.
-
PRISM-EDI
Exchange of schedules, orders, ship notices and invoices with customers and suppliers in X12 or EDIFACT, translated to and from your ERP.
-
PRISM-WebEDI
Browser-based purchase orders, acknowledgments, ship notices and invoices for suppliers without EDI systems.
-
PRISM-SmartConvert
Supplier confirmations, invoices and customer orders that arrive as PDFs, emails or scans converted into ERP-ready data.
-
PRISM-SCV
Monitoring of transactions and exceptions across customer and supplier documents.
Services: Trading partner onboarding · ERP integration · API integration · Fully managed EDI · Supply chain visibility · Mapping and translation
Frequently asked questions
Does ECOM handle hazardous shipping paperwork?
No. Classification and shipping paperwork for flammable products are your logistics team’s responsibility. The integration carries the order and shipment data your partners exchange; it does not replace those processes.
Can travel retail be integrated?
Travel retail operators vary in how they order, so ECOM scopes each operator’s order and ship-notice method separately and connects it to the same ERP data as your department store and specialty retail accounts.
Do retailers send promotional and replenishment orders differently?
Often both arrive as purchase orders, but promotional orders are tied to dates and quantities that change. Retailer guides define how promotions, changes and cancellations are sent, and ECOM confirms the rules per partner.
Do you need our trading partner's implementation guide to start?
It helps, but you can start without one. Tell us who you trade with and which systems you run, and we will help obtain and review each partner's requirements. The guide, not this page, decides the exact documents, versions and rules for that partner.
Talk to an EDI/API expert about fragrance and perfume manufacturers
Share your trading partners, your ERP, a sample document or the problem that keeps recurring. A completed specification is not needed: a partner guide, a rejected document or a description of the issue is enough to start.