Manufacturing · Energy Equipment

EDI and API Integration for Generator, Turbine and Engine Manufacturers

Generator, turbine and engine makers sell configured power equipment to OEMs, distributors and projects, with a large parts and service business behind each unit. ECOM connects orders, project milestones, supplier component flows, serial shipments and parts orders to your ERP.

View all manufacturing industries

What this covers

Products and business models in generator, turbine and engine

Products

  • Engine-generator sets
  • Turbines and power systems
  • Engines for vehicles and equipment
  • Parts, rebuild and service kits

Business models

  • Manufacturers selling via distributors and dealers
  • OEM engine supply
  • Project and rental power

Scenarios

Where generator, turbine and engine 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, long-lead units

    The problem
    Units carry options and long build times.
    How ECOM helps
    ECOM maps options and long-lead dates and carries revised dates into the 855. Supplier 855s and 856s for major components feed the same record.
    What you gain
    A delayed component shows up against the build date.

    Talk to an EDI/API Expert about configured, long-lead units 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.

  • Serial and parts history

    The problem
    Parts follow the unit's serial.
    How ECOM helps
    ECOM carries unit serials onto the 856 and ties parts orders to them.
    What you gain
    Parts follow the unit’s serial.

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

  • OEM engine schedules

    The problem
    OEMs release engines on schedules.
    How ECOM helps
    ECOM posts OEM engine releases (862) and compares them with the build plan, with 862 supplementing the forecast.
    What you gain
    OEM schedule changes reach the plan.

    Talk to an EDI/API Expert about OEM engine schedules Share a sample 862 Shipping Schedule, 830 Planning Schedule with Release Capability and 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 generator, turbine and engine manufacturers

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

Distributors and dealers
Order units, parts and service kits and bring configured orders.
OEMs
Order engines on release schedules.
Project and rental customers
Buy power equipment, often in project phases.
Casting, controls and electronics suppliers
Supply major components with long lead times.
Carriers
Move heavy units and parts.

Typical workflow

Where ECOM connects your systems and trading partners

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

  1. Distributor, dealer or OEM→Your plant and ERP 850 Purchase Order The customer order: items, quantities, prices, ship-to and requested dates.
  2. Distributor, dealer or OEM→Your plant and ERP 862 Shipping Schedule OEM engine release schedules.
  3. Distributor, dealer or OEM→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
  4. Your plant and ERP→Distributor, dealer or OEM 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
  5. Your plant and ERP→Distributor, dealer or OEM 856 Advance Ship Notice Engine or unit serial and configuration.
  6. Your plant and ERP→Distributor, dealer or OEM 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
  7. Distributor, dealer or OEM→Your plant and ERP 180 Return Merchandise Authorization and Notification Core and warranty returns.
  8. Your plant and ERP→Component supplier 850 Purchase Order Purchase orders for castings, controls and components with quantities and requested delivery dates.
  9. Component supplier→Your plant and ERP 855 Purchase Order Acknowledgment The supplier confirms quantities and dates for castings, controls and components.
  10. Component supplier→Your plant and ERP 856 Advance Ship Notice Component shipments with supplier serial or lot where provided, used to plan receiving against build dates.

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

  1. Take orders and schedules

    Orders (850) set units to build; OEM schedules (862) supplement them with shipping dates.

  2. Confirm

    Acknowledgments (855) restate configuration and dates.

  3. Buy components

    Supplier orders (850), confirmations (855) and ship notices (856) gate the build.

  4. Ship with serials

    Tenders (204/990) and the 856 report units and serials.

  5. Invoice and support parts

    The 810 follows shipment; parts orders and core returns (180) share the dealer connection.

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 generator, turbine and engine manufacturers
850 Purchase Order You receive The customer order: items, quantities, prices, ship-to and requested dates.
862 Shipping Schedule You receive OEM engine release schedules.
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.
856 Advance Ship Notice You send Engine or unit serial and configuration.
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 Core and warranty returns.
850 Purchase Order (supplier side) You send Purchase orders for castings, controls and components with quantities and requested delivery dates.
855 Purchase Order Acknowledgment (supplier side) You receive The supplier confirms quantities and dates for castings, controls and components.
856 Advance Ship Notice (supplier side) You receive Component shipments with supplier serial or lot where provided, used to plan receiving against build dates.

Other exchanges you may meet

  • Dealer systems
  • OEM supplier 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

Serials, configurations and parts

The serial of a unit anchors its parts and service history. Component supplier acknowledgments tell you whether promised dates are safe, and OEM engine releases arrive on their own schedules.

  • Project-based orders

    Large equipment is often sold per project, with staged shipments, long lead times and changing delivery dates.

  • Serial numbers and commissioning

    Equipment is identified by serial number for warranty, service and installation records, and customers may need serials on shipment data.

  • Distributors, installers and EPCs

    Products reach the market through distributors, installers and project contractors, each with its own ordering and reporting.

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
  • Dealer systems
  • Warehouse management
  • Service systems

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 distributor, dealer or OEM, 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 dealer 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 generator, turbine and engine manufacturers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Major component delayedA revised date on the supplier’s 855 or a late 856 can be flagged against the build date.
Core return not matched to an orderA core return with no matching parts order can be researched before a credit.

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 OEM engine schedules update our planning?

Yes. Releases load into your ERP or MRP, and planners decide how they change open requirements.

Can dealer systems connect?

Dealer systems vary, so each is scoped as its own connection to your ERP.

Is project-based ordering handled differently from stock orders?

The documents are similar, but project orders carry staged quantities and changing dates, so acknowledgments, changes and ship notices matter more. ECOM maps the project references the customer uses.

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 generator, turbine and engine 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.