Manufacturing · Building Materials and Architectural Products

EDI and API Integration for Cabinet and Architectural Millwork Manufacturers

Cabinet and millwork makers produce configured, project-based product for dealers, builders and contractors. ECOM connects configured orders, release schedules, staged shipments and invoices to your ERP so specifications and delivery dates travel with the job.

View all manufacturing industries

What this covers

Products and business models in cabinet and architectural millwork

Products

  • Kitchen and bath cabinetry
  • Architectural millwork and casework
  • Stairs, mantels and custom wood products
  • Hardware and accessories

Business models

  • Stock and semi-custom lines through dealers
  • Custom millwork for projects
  • Builder programs and multifamily

Scenarios

Where cabinet and architectural millwork 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.

  • Configured product

    The problem
    Each order has dimensions, finishes and options that must map exactly.
    How ECOM helps
    ECOM maps dimensions, finishes and options exactly into the ERP’s configured-product structure and holds orders with an unrecognized option for engineering review.
    What you gain
    Configured orders post without re-keying and bad options are found before production.

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

  • Staged project delivery

    The problem
    Deliveries follow construction schedules and change often.
    How ECOM helps
    ECOM carries revised project dates through the order, 855 and shipping plan.
    What you gain
    Staged deliveries follow the construction schedule.

    Talk to an EDI/API Expert about staged project delivery Share a sample 860 Purchase Order Change Request, 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.

  • Damage and missing pieces

    The problem
    Large item counts per job make accurate packing lists essential.
    How ECOM helps
    ECOM builds the 856 with boxes listed by room or item so installers can check a delivery.
    What you gain
    Missing pieces can be traced to the box.

    Talk to an EDI/API Expert about damage and missing pieces 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 cabinet and architectural millwork manufacturers

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

Dealers and kitchen designers
Order configured cabinets.
Builders and multifamily developers
Release by phase.
Home centers
Replenish stock lines.
Lumber, panel and hardware suppliers
Supply materials.
Freight and installation partners
Deliver to jobs.

Typical workflow

Where ECOM connects your systems and trading partners

The pattern below is typical for cabinet and architectural millwork manufacturers, not one partner's confirmed requirements. Each trading partner publishes its own guide; confirm the details with that partner.

  1. Dealer or builder→Your plant and ERP 850 Purchase Order Configured line items with room, finish and option codes.
  2. Dealer or builder→Your plant and ERP 860 Purchase Order Change Request Project changes that move dates and quantities.
  3. Your plant and ERP→Dealer or builder 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
  4. Your plant and ERP→Dealer or builder 856 Advance Ship Notice Boxes listed by room or item so installers can check the delivery.
  5. Your plant and ERP→Dealer or builder 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
  6. Your plant and ERP→Material supplier 850 Purchase Order Purchase orders for panels, hardware and components with quantities and requested delivery dates.
  7. Material supplier→Your plant and ERP 856 Advance Ship Notice Panel, door, hardware and component shipments with quantity and lot, used to plan receiving against the production schedule.

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

  1. Receive configured orders

    Orders (850) with room and item detail.

  2. Acknowledge dates

    Acknowledgments (855) with production dates.

  3. Stage releases

    Shipments tied to the project schedule (940/945, 204/990).

  4. Ship notice by room

    The 856 lists boxes by room or item.

  5. Invoice

    The 810 bills by 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 cabinet and architectural millwork manufacturers
850 Purchase Order You receive Configured line items with room, finish and option codes.
860 Purchase Order Change Request You receive Project changes that move dates and quantities.
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.
204 Motor Carrier Load Tender You send Tenders a truck shipment to a motor carrier.
990 Response to a Load Tender You receive The motor carrier’s acceptance or decline of the tender.
856 Advance Ship Notice You send Boxes listed by room or item so installers can check the delivery.
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 panels, hardware and components with quantities and requested delivery dates.
856 Advance Ship Notice (supplier side) You receive Panel, door, hardware and component shipments with quantity and lot, used to plan receiving against the production schedule.

Other exchanges you may meet

  • Dealer design software exports
  • Builder purchasing 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

Configurations and project releases

An order may be a kitchen. The room and item structure needs to survive from order to pack list so installers can check a delivery against the job.

  • Dimensions and units of measure

    Products sell by the piece, box, square foot, linear foot, pallet or bundle. Orders, ship notices and invoices must agree on units and conversions, or quantities and prices disagree.

  • Jobsite and yard delivery

    Deliveries go to branches, yards and jobsites, sometimes with delivery appointments or special equipment. Ship-to detail and carrier information are part of the exchange.

  • Distributor orders

    Most volume moves through distributors, dealers and home centers that send their own orders, changes and inventory or sales data.

Connected systems

Systems that send and receive this data

Documents are only useful when they reach the systems that run the business.

  • ERP with configurators
  • Design software
  • Warehouse management
  • Transportation 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 dealer or builder, and agree which documents, versions and data are in scope.

  2. Map to your systems

    Map each document to the fields in your ERP with configurators and design software 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 cabinet and architectural millwork manufacturers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Option code not recognizedAn option code with no match in the ERP product structure can be held for engineering review.
Missing piece reported at deliveryBox-level detail on the 856 can help trace a reported missing piece to the box concerned.

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 dealer design software feed our ERP?

Orders from design software can be integrated by API or file, depending on the software.

How are phased releases handled?

As releases against a project order; the exact mechanism depends on how the customer sends them.

How are units of measure and conversions kept consistent?

Item and unit conversions are agreed during mapping, so a quantity ordered in boxes can be shipped and invoiced in the unit the trading partner expects. They are part of the partner’s implementation guide and tested before go-live.

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 cabinet and architectural millwork 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.