Manufacturing · Electronics, Electrical and Security

EDI and API Integration for Smart Home and Connected Device Manufacturers

Smart home and connected device makers sell through retailers, marketplaces and distributors with frequent product refreshes and high return rates. ECOM connects item data, orders, serial-number shipments and returns to your ERP.

View all manufacturing industries

What this covers

Products and business models in smart home and connected device

Products

  • Smart speakers, hubs and displays
  • Lighting, plugs and thermostats
  • Locks, sensors and cameras
  • Accessories and bundles

Business models

  • Brands wholesale to retailers
  • Marketplace and online-first brands
  • Contract-manufactured private label

Scenarios

Where smart home and connected device 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.

  • Fast product cycles

    The problem
    New versions replace old ones quickly, so item data changes often.
    How ECOM helps
    ECOM updates item data (832) as new versions replace old ones and holds orders for discontinued items.
    What you gain
    Retailers order the current version.

    Talk to an EDI/API Expert about fast product cycles 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.

  • Bundles and promotions

    The problem
    Bundles and holiday promotions require new item numbers.
    How ECOM helps
    ECOM maps bundle and promotional items and their components.
    What you gain
    Bundles order, ship and invoice as designed.

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

  • Returns

    The problem
    Setup issues drive returns.
    How ECOM helps
    ECOM processes return authorizations (180) and links them to the original order.
    What you gain
    Setup-driven returns are researched against the sale.

    Talk to an EDI/API Expert about returns Share a sample 180 Return Merchandise Authorization and Notification, or describe what goes wrong, and we will show how it would map to your ERP.

Who you connect with

Trading relationships for smart home and connected device manufacturers

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

Big-box and online retailers
Order for stores and DCs with detailed item data requirements.
Marketplaces
Order for direct shipment under strict ship-by and tracking windows.
Distributors
Resell to smaller retailers and installers.
Contract manufacturers
Build products to your forecasts and revisions.
3PLs and carriers
Distribute, including returns processing.

Typical workflow

Where ECOM connects your systems and trading partners

The pattern below is typical for smart home and connected device 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→Retailer or marketplace 832 Price/Sales Catalog Version and bundle data as products refresh.
  2. Retailer or marketplace→Your plant and ERP 850 Purchase Order The customer order: items, quantities, prices, ship-to and requested dates.
  3. Retailer or marketplace→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
  4. Your plant and ERP→Retailer or marketplace 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
  5. Your plant and ERP→Retailer or marketplace 856 Advance Ship Notice Describes what is shipping, how it is packed and how it is labeled.
  6. Your plant and ERP→Retailer or marketplace 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
  7. Retailer or marketplace→Your plant and ERP 180 Return Merchandise Authorization and Notification Authorizations for returns.
  8. Your plant and ERP→Contract manufacturer 850 Purchase Order Purchase orders for contract-manufactured units and components with quantities and requested delivery dates.
  9. Contract manufacturer→Your plant and ERP 856 Advance Ship Notice Contract manufacturer shipments with quantity and batch or serial ranges where provided, used to plan receiving and registration.

The diagram draws the exchanges between the lanes shown. Motor-carrier and warehouse documents (940, 945) are listed in the table below with the direction each travels.

  1. Item data

    Item data (832) with versions and bundles.

  2. Orders

    Orders (850), changes (860).

  3. Ship

    Warehouse release (940/945); notice (856).

  4. Invoice

    The 810 follows.

  5. Returns

    Return authorizations (180).

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 smart home and connected device manufacturers
832 Price/Sales Catalog You send Version and bundle data as products refresh.
850 Purchase Order You receive The customer order: items, quantities, prices, ship-to and requested 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.
940 Warehouse Shipping Order You send Tells the warehouse or 3PL what to pick and ship.
945 Warehouse Shipping Advice You receive Confirms what the warehouse actually shipped.
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.
180 Return Merchandise Authorization and Notification You receive Authorizations for returns.
850 Purchase Order (supplier side) You send Purchase orders for contract-manufactured units and components with quantities and requested delivery dates.
856 Advance Ship Notice (supplier side) You receive Contract manufacturer shipments with quantity and batch or serial ranges where provided, used to plan receiving and registration.

Other exchanges you may meet

  • Marketplace APIs
  • Retailer portals

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

Versions, bundles and returns

A hardware refresh brings new item numbers and the need to control which version ships against which order. Holiday bundles are new items with components, and returns link back to the original sale so refunds and restocking are right.

  • Serial numbers and warranty

    Equipment is identified by model and serial number for warranty, service and returns, and customers may ask for serials on shipping documents.

  • Returns and repair flows

    Returns, repairs and exchanges generate their own authorizations and shipments in both directions.

  • Distributors and contract manufacturing

    Components and equipment move through distributors and contract manufacturers, with forecasts, consigned stock, price protection and ship-and-debit exchanges.

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
  • Marketplace platforms
  • Returns management

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 retailer or marketplace, 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 smart home and connected device manufacturers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Order for a retired product versionThe line can be held for review so a retailer is not shipped a version that has been replaced without agreement.
Bundle component short at pick timeThe bundle order can be held for review and the short component is shown to the team.

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 marketplaces connect to the same ERP?

Yes. Marketplaces use APIs or EDI, and all of them can post orders to the same ERP and receive acknowledgments, tracking and invoices back.

How are bundles represented?

As items with defined components in your ERP and the customer’s item data, so the order, ship notice and invoice all refer to the bundle the retailer set up.

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 smart home and connected device 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.