Manufacturing · Metals, Machinery and Industrial Equipment

EDI and API Integration for Foundry, Casting, Forging and Fabricated Metal Manufacturers

Foundries, forgers and fabricated metal makers supply parts to OEM schedules with material and revision traceability. ECOM connects customer forecasts and releases, material purchasing, lot-traceable shipments and invoices to your ERP.

View all manufacturing industries

What this covers

Products and business models in foundry, casting, forging and fabricated metal

Products

  • Iron, steel and aluminum castings
  • Forgings and stampings
  • Machined and welded fabrications
  • Powder metal and specialty parts

Business models

  • Foundries and forges supplying OEMs
  • Job shops and contract fabricators
  • Tier-2 suppliers

Scenarios

Where foundry, casting, forging and fabricated metal 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.

  • Releases change plans

    The problem
    OEM releases arrive weekly or daily and drive melt and machining.
    How ECOM helps
    ECOM posts OEM releases (862) as they arrive and compares them with the melt and machining plan.
    What you gain
    Schedule changes reach planning when they arrive.

    Talk to an EDI/API Expert about releases change plans 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.

  • Heat and revision traceability

    The problem
    Parts trace to heat and drawing revision.
    How ECOM helps
    ECOM carries heat and drawing revision onto the 856 and label data.
    What you gain
    Parts trace to heat and revision.

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

  • Outside processing

    The problem
    Heat treat, plating and machining add subcontract steps.
    How ECOM helps
    ECOM exchanges documents with outside processors (850, 856) for heat treat, plating and machining.
    What you gain
    Subcontract steps are visible in the order record.

    Talk to an EDI/API Expert about outside processing 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.

Who you connect with

Trading relationships for foundry, casting, forging and fabricated metal manufacturers

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

OEM and tier-one customers
Send forecasts and releases, with label, packaging and traceability rules.
Scrap, alloy and metal suppliers
Supply the metals melted and forged.
Heat treat and plating vendors
Process parts between steps and affect lead time.
Tooling and pattern shops
Supply patterns and dies that gate new parts.
Carriers
Ship parts to customer plants.

Typical workflow

Where ECOM connects your systems and trading partners

The pattern below is typical for foundry, casting, forging and fabricated metal manufacturers, not one partner's confirmed requirements. Each trading partner publishes its own guide; confirm the details with that partner.

  1. OEM or tier-1 customer→Your plant and ERP 830 Planning Schedule with Release Capability Customer forecast for melt and machining planning.
  2. OEM or tier-1 customer→Your plant and ERP 862 Shipping Schedule Supplements the 830: shipping and delivery quantities and dates that, under the partner’s rules, supersede the applicable shipping information in the 830. It does not replace the 830 or, on its own, authorize production resources.
  3. OEM or tier-1 customer→Your plant and ERP 850 Purchase Order The customer order: items, quantities, prices, ship-to and requested dates.
  4. OEM or tier-1 customer→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
  5. Your plant and ERP→OEM or tier-1 customer 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
  6. Your plant and ERP→OEM or tier-1 customer 856 Advance Ship Notice Heat, lot and label identifiers per container.
  7. Your plant and ERP→OEM or tier-1 customer 863 Report of Test Results Material or test results where the customer asks.
  8. Your plant and ERP→OEM or tier-1 customer 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
  9. Your plant and ERP→Metal supplier 850 Purchase Order Purchase orders for ingot, bar, billet and scrap with quantities and requested delivery dates.
  10. Metal supplier→Your plant and ERP 855 Purchase Order Acknowledgment The supplier confirms quantities and dates for ingot, bar, billet and scrap.
  11. Metal supplier→Your plant and ERP 856 Advance Ship Notice Metal loads with heat or lot identifiers, used to match incoming material to certifications and production.
  1. Receive forecasts and releases

    Forecasts (830) inform melt and machining plans; shipping schedules (862) supplement them with delivery dates.

  2. Buy metal and outside services

    Orders (850) and supplier notices (856) support material and subcontract steps.

  3. Produce with traceability

    Heat, lot and revision are recorded as parts move.

  4. Send the ship notice and labels

    The 856 reports lots and label identifiers per container.

  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 foundry, casting, forging and fabricated metal manufacturers
830 Planning Schedule with Release Capability You receive Customer forecast for melt and machining planning.
862 Shipping Schedule You receive Supplements the 830: shipping and delivery quantities and dates that, under the partner’s rules, supersede the applicable shipping information in the 830. It does not replace the 830 or, on its own, authorize production resources.
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 Heat, lot and label identifiers per container.
863 Report of Test Results You send Material or test results where the customer asks.
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 ingot, bar, billet and scrap with quantities and requested delivery dates.
855 Purchase Order Acknowledgment (supplier side) You receive The supplier confirms quantities and dates for ingot, bar, billet and scrap.
856 Advance Ship Notice (supplier side) You receive Metal loads with heat or lot identifiers, used to match incoming material to certifications and production.

Other exchanges you may meet

  • Customer supplier portals
  • Customer-specific label standards

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

Releases, heats and outside processing

Heat and revision data follow a part through melt, machining and outside processes, and appear on the notice and label. Release changes inside the lead time are the main planning stress.

  • Forecasts, schedules and releases

    Customers send forecasts and firm releases that change plans. How they update requirements in the ERP is a planning decision as much as an integration one.

  • Components and supplier collaboration

    Finished equipment depends on many purchased components. Orders, acknowledgments and ship notices to and from suppliers keep builds on schedule.

Connected systems

Systems that send and receive this data

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

  • ERP with MRP
  • Quality management
  • Shop floor
  • 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 OEM or tier-1 customer, 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 MRP and quality 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 foundry, casting, forging and fabricated metal manufacturers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Release change inside the lead timeThe change can be flagged for review to planners and purchasing so melt and machining schedules can be reviewed.
Drawing revision on the order does not match productionThe order can be held for review so parts are not made to a superseded drawing.

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 forecasts and releases update our MRP?

Yes. They load into your ERP or MRP, and planners decide how a new release changes open requirements.

Do you support automotive suppliers?

Yes, working from each customer’s published requirements. See the automotive page for how OEM schedules, labels and ship notices are handled.

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 foundry, casting, forging and fabricated metal 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.