Manufacturing · Electronics, Electrical and Security

EDI and API Integration for Transformer, Switchgear and Power Conversion Manufacturers

Transformer, switchgear and power conversion makers build long-lead, serialized equipment for utilities, contractors and industrial customers. ECOM connects project orders, schedule changes, test reports and serial-number shipments to your ERP.

View all manufacturing industries

What this covers

Products and business models in transformer, switchgear and power conversion

Products

  • Distribution and power transformers
  • Medium-voltage switchgear
  • Power supplies, inverters and drives
  • Parts and service

Business models

  • Manufacturers selling to utilities and contractors
  • Project and OEM sales
  • Distributor channel for standard products

Scenarios

Where transformer, switchgear and power conversion 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.

  • Long lead times and milestones

    The problem
    Orders run months, with milestones and dates that shift.
    How ECOM helps
    ECOM carries revised milestone dates through acknowledgments and schedule changes.
    What you gain
    Customers hear about a milestone slip from you first.

    Talk to an EDI/API Expert about long lead times and milestones Share a sample 855 Purchase Order Acknowledgment and 860 Purchase Order Change Request, or describe what goes wrong, and we will show how it would map to your ERP.

  • Test reports and serials

    The problem
    Each unit ships with test data and a serial number.
    How ECOM helps
    ECOM sends test report data (863) with the serial on the shipment.
    What you gain
    Each unit’s test data travels with its serial.

    Talk to an EDI/API Expert about test reports and serials Share a sample 863 Report of Test Results and 856 Advance Ship Notice, or describe what goes wrong, and we will show how it would map to your ERP.

  • Heavy, oversize freight

    The problem
    Equipment moves on specialized transport.
    How ECOM helps
    ECOM connects tenders and status (204, 990, 214) for oversize freight.
    What you gain
    Specialized transport is planned and tracked.

    Talk to an EDI/API Expert about heavy, oversize freight Share a sample 204 Motor Carrier Load Tender, 990 Response to a Load Tender and 214 Transportation Carrier Shipment Status Message, or describe what goes wrong, and we will show how it would map to your ERP.

Who you connect with

Trading relationships for transformer, switchgear and power conversion manufacturers

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

Utilities and cooperatives
Order under programs.
Contractors and EPC firms
Order for projects.
Industrial customers and OEMs
Order power equipment.
Electrical distributors
Stock standard products.
Specialty carriers
Haul heavy equipment.

Typical workflow

Where ECOM connects your systems and trading partners

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

  1. Utility, EPC or distributor→Your plant and ERP 850 Purchase Order The customer order: items, quantities, prices, ship-to and requested dates.
  2. Utility, EPC or distributor→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
  3. Your plant and ERP→Utility, EPC or distributor 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
  4. Your plant and ERP→Specialty carrier 204 Motor Carrier Load Tender Tenders a truck shipment to a motor carrier.
  5. Specialty carrier→Your plant and ERP 990 Response to a Load Tender The motor carrier’s acceptance or decline of the tender.
  6. Specialty carrier→Your plant and ERP 214 Transportation Carrier Shipment Status Message Shipment status events from the motor carrier.
  7. Your plant and ERP→Utility, EPC or distributor 863 Report of Test Results Unit test results sent with or before shipment where asked.
  8. Your plant and ERP→Utility, EPC or distributor 856 Advance Ship Notice Serial numbers and nameplate references per unit.
  9. Your plant and ERP→Utility, EPC or distributor 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
  1. Project orders

    Orders (850) and changes (860).

  2. Milestones

    Acknowledgments (855) restate dates.

  3. Test and ship

    Test reports (863) and tenders (204/990).

  4. Ship notice with serials

    The 856 lists units and serials.

  5. Invoice by milestone

    The 810 follows.

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 transformer, switchgear and power conversion manufacturers
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.
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.
214 Transportation Carrier Shipment Status Message You receive Shipment status events from the motor carrier.
863 Report of Test Results You send Unit test results sent with or before shipment where asked.
856 Advance Ship Notice You send Serial numbers and nameplate references per unit.
810 Invoice You send Bills for what was shipped, tied to the order and the ship notice.

Other exchanges you may meet

  • Utility procurement portals
  • Project milestone files

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

Milestones, tests and oversize freight

A unit’s order, test record, serial number and delivery must be linked. Milestone dates move, so acknowledgments with revised dates matter to project schedules, and oversize equipment needs coordinated carriers.

  • 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 with project modules
  • Quality and test systems
  • Transportation management
  • Customer 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 utility, EPC or distributor, 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 project modules and quality and test systems 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 transformer, switchgear and power conversion manufacturers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Milestone date slipping on a projectA revised date on an 855 or a schedule change can be flagged so customer service can tell the contractor first.
Test report missing at ship timeThe shipment can be held for review until the unit’s test documentation is available.

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 utility procurement portals connect?

Each portal is scoped as its own connection, since utilities differ in how they order and pay.

Does ECOM schedule oversize transport?

No. Transport planning stays with you and your carriers. The integration carries tenders, status and the related documents.

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 transformer, switchgear and power conversion 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.