Manufacturing · Metals, Machinery and Industrial Equipment

EDI and API Integration for Industrial Ceramic and Refractory Manufacturers

Industrial ceramic and refractory makers supply bricks, castables and technical ceramics to steel, glass, cement and chemical plants, often for scheduled outages. ECOM connects project orders, shape and lot data, heavy freight and invoices to your ERP.

View all manufacturing industries

What this covers

Products and business models in industrial ceramic and refractory

Products

  • Refractory bricks and shapes
  • Monolithics and castables
  • Technical ceramics
  • Installation materials

Business models

  • Manufacturers selling to plants
  • Project and shutdown supply
  • Distributors

Scenarios

Where industrial ceramic and refractory 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.

  • Outage-driven delivery

    The problem
    Deliveries are timed to plant shutdowns.
    How ECOM helps
    ECOM carries outage dates through the order, production and shipping plan and updates them when the outage moves.
    What you gain
    Deliveries stay aligned with the shutdown.

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

  • Shapes and specifications

    The problem
    Shape lists and specs are detailed.
    How ECOM helps
    ECOM carries shape lists and specifications onto the order and notice and compares shipped shapes with the order.
    What you gain
    A missing shape is flagged before the load leaves.

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

  • Heavy and fragile freight

    The problem
    Heavy, fragile shapes make pallet-level detail important for receiving, damage claims and installation planning.
    How ECOM helps
    ECOM builds the 856 at pallet level for heavy and fragile freight.
    What you gain
    Damage claims are researched against pallet detail.

    Talk to an EDI/API Expert about heavy and fragile freight Share a sample 856 Advance Ship Notice 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 industrial ceramic and refractory manufacturers

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

Steel, glass and cement plants
Order refractories for furnace relines and scheduled outages.
Installation contractors
Install products on the plant’s schedule.
Raw material suppliers
Supply alumina, magnesia and other minerals with long lead times.
Distributors
Resell standard shapes and monolithics.
Carriers
Move heavy, fragile pallets on delivery windows.

Typical workflow

Where ECOM connects your systems and trading partners

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

  1. Plant or contractor→Your plant and ERP 850 Purchase Order Shape list with quantities for an outage.
  2. Plant or contractor→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
  3. Your plant and ERP→Plant or contractor 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
  4. Your plant and ERP→Plant or contractor 856 Advance Ship Notice Shape, pallet and lot detail.
  5. Your plant and ERP→Plant or contractor 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
  6. Your plant and ERP→Raw material supplier 850 Purchase Order Purchase orders for clay, alumina and other raw materials with quantities and requested delivery dates.
  7. Raw material supplier→Your plant and ERP 856 Advance Ship Notice Raw material shipments with quantity and the supplier’s lot, used to plan receiving ahead of firing.

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 outage and project orders

    Orders (850) and changes (860) carry shape lists and outage dates.

  2. Confirm dates

    Acknowledgments (855) restate shapes and ship dates.

  3. Ship

    Tenders (204/990) and status (214) follow heavy loads.

  4. Send the ship notice by shape

    The 856 lists shapes, pallets and lots.

  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 industrial ceramic and refractory manufacturers
850 Purchase Order You receive Shape list with quantities for an outage.
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 Shape, pallet and lot detail.
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 clay, alumina and other raw materials with quantities and requested delivery dates.
856 Advance Ship Notice (supplier side) You receive Raw material shipments with quantity and the supplier’s lot, used to plan receiving ahead of firing.

Other exchanges you may meet

  • Customer procurement portals
  • Project schedules

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

Outages, shapes and pallets

A late or incorrect shape can delay a plant shutdown. Pallet and shape detail must match the shape list, and heavy, fragile loads make accurate shipment records useful if a claim arises.

  • 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
  • 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 plant or contractor, 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 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 industrial ceramic and refractory manufacturers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Shape missing from a shipmentA comparison of shipped shapes with the order’s shape list can flag a gap for review before the load leaves.
Outage date movedA changed date can be carried through the order, production and shipping plan.

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 shutdown schedules be supported?

Orders and changes reflect the dates the customer sends. The integration keeps your ERP and shipping plan updated as the outage schedule moves.

Do plants use EDI?

Some do; many use procurement portals. ECOM supports a mix.

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 industrial ceramic and refractory 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.