Manufacturing · Furniture, Furnishings and Housewares

EDI and API Integration for Home Décor, Seasonal Decoration and Candle Manufacturers

Home décor, seasonal decoration and candle makers run on seasonal programs for mass, specialty and online retailers, usually imported. ECOM connects retailer programs, factory shipments, ship notices and invoices to your ERP so tight seasonal windows are met.

View all manufacturing industries

What this covers

Products and business models in home Décor, seasonal decoration and candle

Products

  • Home accents and wall décor
  • Holiday and seasonal decorations
  • Candles and fragrance products
  • Frames, vases and gift items

Business models

  • Brands and importers selling to mass and specialty retailers
  • Private label programs
  • Gift and floral wholesale

Scenarios

Where home décor, seasonal decoration and candle 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.

  • Seasonal programs

    The problem
    Holiday and seasonal programs are ordered early and must land in stores on set dates.
    How ECOM helps
    ECOM posts early seasonal orders and changes (850, 860) and maps factory ship notices into the ERP.
    What you gain
    Stores are planned against both orders and inbound dates.

    Talk to an EDI/API Expert about seasonal programs Share a sample 850 Purchase Order, 860 Purchase Order Change Request and 856 Advance Ship Notice, or describe what goes wrong, and we will show how it would map to your ERP.

  • Fragile and mixed cartons

    The problem
    Fragile goods and assortments require accurate carton descriptions.
    How ECOM helps
    ECOM builds the 856 from your pack data so fragile and mixed cartons are described accurately.
    What you gain
    Receiving can match assortments to the notice.

    Talk to an EDI/API Expert about fragile and mixed cartons Share a sample 856 Advance Ship Notice, or describe what goes wrong, and we will show how it would map to your ERP.

  • Many small SKUs

    The problem
    Wide assortments mean many item numbers per program.
    How ECOM helps
    ECOM maintains item data for wide seasonal assortments for each retailer.
    What you gain
    Many small SKUs post to the right items.

    Talk to an EDI/API Expert about many small SKUs Share a sample 832 Price/Sales Catalog and 850 Purchase Order, or describe what goes wrong, and we will show how it would map to your ERP.

Who you connect with

Trading relationships for home décor, seasonal decoration and candle manufacturers

Typical relationships. Which of them apply, and how each one wants to connect, depends on your business.

Mass, craft and home retailers
Order seasonal programs.
Gift and floral wholesalers
Resell to small shops.
Online sellers
Direct-ship orders.
Overseas factories and wax suppliers
Produce and supply.
Forwarders and carriers
Import and distribute.

Typical workflow

Where ECOM connects your systems and trading partners

The pattern below is typical for home décor, seasonal decoration and candle manufacturers, not one partner's confirmed requirements. Each trading partner publishes its own guide; confirm the details with that partner.

  1. Your plant and ERP→Mass or specialty retailer 832 Price/Sales Catalog Sends item, description and price data for the customer to set up.
  2. Mass or specialty retailer→Your plant and ERP 850 Purchase Order Seasonal program orders with in-store dates.
  3. Mass or specialty retailer→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
  4. Your plant and ERP→Mass or specialty retailer 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
  5. Your plant and ERP→Mass or specialty retailer 856 Advance Ship Notice Carton and assortment contents.
  6. Your plant and ERP→Mass or specialty retailer 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
  7. Your plant and ERP→Overseas factory 850 Purchase Order Purchase orders for finished goods from factories with quantities and requested delivery dates.
  8. Overseas factory→Your plant and ERP 855 Purchase Order Acknowledgment The supplier confirms quantities and dates for finished goods from factories.
  9. Overseas factory→Your plant and ERP 856 Advance Ship Notice Factory carton and container detail by item and assortment against the seasonal ship window.
  1. Program setup

    You send item data (832); program orders (850) arrive in return.

  2. Factory orders

    Purchase orders (850) and factory notices (856).

  3. Receive and allocate

    Inbound inventory allocated to program orders.

  4. Ship notice

    The 856 describes cartons and assortments.

  5. 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.

DocumentDirectionWhat it carries for home décor, seasonal decoration and candle manufacturers
832 Price/Sales Catalog You send Sends item, description and price data for the customer to set up.
850 Purchase Order You receive Seasonal program orders with in-store dates.
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 Carton and assortment contents.
810 Invoice You send Bills for what was shipped, tied to the order and the ship notice.
850 Purchase Order (supplier side) You send Purchase orders for finished goods from factories with quantities and requested delivery dates.
855 Purchase Order Acknowledgment (supplier side) You receive The supplier confirms quantities and dates for finished goods from factories.
856 Advance Ship Notice (supplier side) You receive Factory carton and container detail by item and assortment against the seasonal ship window.

Other exchanges you may meet

  • Retailer routing 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

Seasons, fragile goods and assortments

Seasonal items have narrow selling windows, so a late inbound container or a ship notice that does not match the carton can leave a whole program on the dock. Fragile goods and assortments also need accurate carton descriptions.

  • Fragile and seasonal goods

    Decor and candles are fragile and ship in concentrated seasons, so order changes, packing and delivery dates need to reach the warehouse in time.

  • Scents, colors and assortments

    Items come in many scents, colors and set configurations that the retailer sets up as separate items.

  • Retailer item and carton rules

    Retailers set item numbers, carton contents and labels, and shipments that do not match them are rejected or charged back.

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
  • Forwarder portals
  • Retailer portals

Onboarding and monitoring

From first requirement to daily exception handling

  1. Confirm the requirement

    Obtain each partner's implementation guide or specification, for example from your mass or specialty retailer, and agree which documents, versions and data are in scope.

  2. Map to your systems

    Map each document to the fields in your ERP and warehouse management so the data posts without re-keying.

  3. 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.

  4. 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.

  5. 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 home décor, seasonal decoration and candle manufacturers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Container late against a seasonal dateA late factory 856 or overdue container date can be flagged to the account team.
Assortment on notice differs from cartonA comparison of the assortment on the 856 with the carton or pack data can flag a mismatch before shipment.

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.

Frequently asked questions

Can import status be integrated?

Forwarder and ocean carrier status can post to the ERP where it is provided, giving seasonal programs an earlier warning when a container will miss its date.

Do small retailers and gift shops use EDI?

Some do. Others order through gift wholesalers, portals or files, and ECOM supports that mix rather than assuming every account has EDI.

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 home décor, seasonal decoration and candle 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.