Manufacturing · Metals, Machinery and Industrial Equipment

EDI and API Integration for Steel, Aluminum and Primary Metal Producers

Steel, aluminum and primary metal producers sell coil, plate, bar and billet to service centers and manufacturers, with heat traceability and mill test reports on every order. ECOM connects orders, heat and coil detail, test reports, freight and invoices to your ERP.

View all manufacturing industries

What this covers

Products and business models in steel, aluminum and primary metal

Products

  • Flat-rolled coil, sheet and plate
  • Bar, rod, tube and structural shapes
  • Aluminum extrusions, sheet and ingot
  • Specialty alloys

Business models

  • Mills selling to service centers
  • Direct sales to manufacturers
  • Processors and toll operations

Scenarios

Where steel, aluminum and primary metal producers 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.

  • Heat and coil traceability

    The problem
    Every coil or bundle traces to a heat and its chemistry and test results.
    How ECOM helps
    ECOM carries heat and coil or bundle identifiers onto the 856 and test data (863) alongside.
    What you gain
    Customers can trace each coil to its heat and test results.

    Talk to an EDI/API Expert about heat and coil 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.

  • Weight, tolerance and price basis

    The problem
    Orders and invoices run on weight with tolerances and price formulas.
    How ECOM helps
    ECOM maps weight, tolerance and price-basis references into the 850, 856 and 810 and compares shipped weight with tolerance.
    What you gain
    Weight-based invoices follow what shipped.

    Talk to an EDI/API Expert about weight, tolerance and price basis Share a sample 850 Purchase Order, 856 Advance Ship Notice and 810 Invoice, or describe what goes wrong, and we will show how it would map to your ERP.

  • Rail, truck and barge freight

    The problem
    Heavy loads move by multiple modes.
    How ECOM helps
    ECOM keeps truck tenders (204/990) and other modes apart, using the right documents for each.
    What you gain
    Heavy loads move by the right mode and documents.

    Talk to an EDI/API Expert about rail, truck and barge 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 steel, aluminum and primary metal producers

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

Steel service centers
Order coil, plate and bar by grade and size and process it for end users.
Manufacturers (auto, appliance, equipment)
Send schedules and order material to specification.
Scrap, ore and alloy suppliers
Supply the raw materials mills melt and alloy.
Rail, truck and barge carriers
Move heavy loads by multiple modes.
Toll processors
Process material between steps on your behalf.

Typical workflow

Where ECOM connects your systems and trading partners

The pattern below is typical for steel, aluminum and primary metal producers, not one partner's confirmed requirements. Each trading partner publishes its own guide; confirm the details with that partner.

  1. Service center or manufacturer→Your plant and ERP 850 Purchase Order The customer order: items, quantities, prices, ship-to and requested dates.
  2. Service center or manufacturer→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. Service center or manufacturer→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
  4. Your plant and ERP→Service center or manufacturer 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
  5. Your plant and ERP→Motor carrier 204 Motor Carrier Load Tender Tenders a truck shipment to a motor carrier.
  6. Motor carrier→Your plant and ERP 990 Response to a Load Tender The motor carrier’s acceptance or decline of the tender.
  7. Motor carrier→Your plant and ERP 214 Transportation Carrier Shipment Status Message Shipment status events from the motor carrier.
  8. Your plant and ERP→Service center or manufacturer 856 Advance Ship Notice Coil or bundle ID, heat number and weight.
  9. Your plant and ERP→Service center or manufacturer 863 Report of Test Results Mill test report data for each heat.
  10. Your plant and ERP→Service center or manufacturer 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
  11. Service center or manufacturer→Your plant and ERP 861 Receiving Advice/Acceptance Certificate Customer receiving weights for reconciliation.
  1. Receive orders and schedules

    Orders (850) set grade, size and quantity; shipping schedules (862) supplement them with dates.

  2. Confirm with promised dates

    Acknowledgments (855) state ship dates that reflect the mill schedule.

  3. Ship with heat detail

    Tenders (204/990) and the 856 report coil or bundle, heat and weight.

  4. Send test results

    Test reports (863) follow where the customer asks for them electronically.

  5. Invoice by weight

    The 810 follows shipped weight and reconciles to the customer’s receipt (861).

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 steel, aluminum and primary metal producers
850 Purchase Order You receive The customer order: items, quantities, prices, ship-to and requested dates.
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.
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 Coil or bundle ID, heat number and weight.
863 Report of Test Results You send Mill test report data for each heat.
810 Invoice You send Bills for what was shipped, tied to the order and the ship notice.
861 Receiving Advice/Acceptance Certificate You receive Customer receiving weights for reconciliation.

Other exchanges you may meet

  • Rail status messages
  • Customer portals; industry-specific formats where required

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

Heats, weights and test reports

Heat numbers tie material to its chemistry and test results. The identifier on the notice and the test report must match, and shipped weight must reconcile to the invoice.

  • 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
  • Mill and quality 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 service center or manufacturer, 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 mill and quality 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 steel, aluminum and primary metal producers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Heat number missing on a coil lineThe shipment can be held for review so the customer is not sent material it cannot match to a test report.
Shipped weight outside the order toleranceA tolerance check can flag the difference for review before the invoice goes out.

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 mill test reports be exchanged electronically?

Where a customer asks and your quality system produces them, yes. The data is mapped from your records and tied to the heat on the shipment.

Does ECOM support automotive steel customers?

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

How do schedules and releases update ERP planning?

Schedules are translated and loaded to your ERP or MRP. Whether a new release replaces or adjusts open requirements is agreed with your planners and tested with real schedule changes.

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 steel, aluminum and primary metal producers

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.