Manufacturing · Apparel, Accessories and Textiles

EDI and API Integration for Footwear Manufacturers

Footwear brands sell wide size and width ranges through specialty, department and online retailers, mostly from overseas factories. ECOM connects retailer orders, factory and importer shipments, and invoices to your ERP so size runs, cartons and pairs stay consistent.

View all manufacturing industries

What this covers

Products and business models in footwear

Products

  • Athletic, casual and dress footwear
  • Work and safety footwear
  • Boots, sandals and slippers
  • Children’s footwear

Business models

  • Brands wholesale to retailers
  • Importers working with overseas factories
  • Direct-to-consumer alongside wholesale

Scenarios

Where footwear 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.

  • Width and size grids

    The problem
    Half sizes and widths multiply items; an order for a missing size causes lost sales.
    How ECOM helps
    ECOM maps size and width grids to retailer item data (832) and flags orders for sizes your ERP does not carry.
    What you gain
    Missing sizes are found when the order posts, not after the shipment.

    Talk to an EDI/API Expert about width and size grids 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.

  • Overseas production and landed inventory

    The problem
    Factories ship by container on long lead times, so supplier shipment data drives availability.
    How ECOM helps
    ECOM maps overseas factory orders, confirmations and ship notices (850, 855, 856) into your ERP so expected inbound inventory is current.
    What you gain
    Availability promises to retailers follow inbound container timing.

    Talk to an EDI/API Expert about overseas production and landed inventory 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.

  • Carton and pair labeling

    The problem
    Retailers need carton-level contents and sometimes pair-level identification to receive.
    How ECOM helps
    ECOM builds the carton-level 856 from your pack data, with pair-level detail where the retailer asks.
    What you gain
    Retail receiving can check cartons against the notice.

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

Who you connect with

Trading relationships for footwear manufacturers

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

Specialty, department and athletic retailers
Order seasonal and replenishment styles.
Online retailers and marketplaces
Order for direct shipment.
Overseas factories and importers
Ship containers against purchase orders.
Freight forwarders and customs brokers
Move imports.
Distribution centers and 3PLs
Receive, store and ship.

Typical workflow

Where ECOM connects your systems and trading partners

The pattern below is typical for footwear 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→Footwear or department retailer 832 Price/Sales Catalog Sends item, description and price data for the customer to set up.
  2. Footwear or department retailer→Your plant and ERP 850 Purchase Order The customer order: items, quantities, prices, ship-to and requested dates.
  3. Footwear or department retailer→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
  4. Your plant and ERP→Footwear or department 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→Footwear or department retailer 856 Advance Ship Notice Carton-level style, size and pair counts.
  6. Your plant and ERP→Footwear or department retailer 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
  7. Your plant and ERP→Overseas factory or importer 850 Purchase Order Purchase orders to factories by style, size run and ship window.
  8. Overseas factory or importer→Your plant and ERP 855 Purchase Order Acknowledgment The supplier confirms quantities and dates for finished footwear from factories.
  9. Overseas factory or importer→Your plant and ERP 856 Advance Ship Notice Factory shipment notices that feed inbound inventory.
  10. Footwear or department retailer→Your plant and ERP 852 Product Activity Data Retailer sales data for reorders.
  1. Item setup

    Catalog data (832) loads styles, widths and sizes.

  2. Retail orders

    Orders (850) and changes (860) post by size run.

  3. Buy from factories

    Purchase orders (850) to factories and their shipment notices (856) feed expected inventory.

  4. Ship to retailers

    Cartons are described in the 856 by style and size.

  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 footwear manufacturers
832 Price/Sales Catalog You send Sends item, description and price data for the customer to set up.
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.
856 Advance Ship Notice You send Carton-level style, size and pair counts.
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 to factories by style, size run and ship window.
855 Purchase Order Acknowledgment (supplier side) You receive The supplier confirms quantities and dates for finished footwear from factories.
856 Advance Ship Notice (supplier side) You receive Factory shipment notices that feed inbound inventory.
852 Product Activity Data You receive Retailer sales data for reorders.

Other exchanges you may meet

  • GS1-128 carton labels
  • Forwarder and ocean carrier status feeds

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

Size runs, factories and landed stock

Availability depends on what has left the factory and arrived, not only what is in the warehouse. Supplier shipment data keeps the ERP’s expected inventory honest, so wholesale orders are confirmed against inventory that will arrive.

  • Style, color and size variants

    One style becomes dozens of items. Orders, ship notices and invoices have to carry the same style, color, size and UPC that the retailer set up, or receipts do not match.

  • Seasonal assortments

    Lines are sold months ahead and shipped in waves. Order changes, cancellations and delivery windows move constantly during a season.

  • Retailer orders and packing rules

    Department stores and mass merchants specify prepacks, carton labels and routing. Mistakes surface later as chargebacks.

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 footwear or department 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 footwear manufacturers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Factory ship notice lateExpected inbound can be flagged for review before wholesale orders are confirmed against it.
Size missing from an order's allocationThe line can be held for the account review 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 factory shipment data update our inventory forecast?

Yes. Factory ship notices, confirmations and forwarder status can post to the ERP as expected receipts. Suppliers without EDI can send files or use a browser.

How are widths represented?

As part of the item number or attributes in the retailer’s catalog. ECOM maps your size and width structure to theirs.

How are style, color and size handled in EDI documents?

Retailers identify each variant by item numbers such as UPC, so documents carry a line per variant. ECOM maps your style, color and size structure to the way each trading partner identifies items.

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