Manufacturing · Chemicals, Plastics and Rubber

EDI and API Integration for Industrial Gas Manufacturers

Industrial gas producers supply cylinders, bulk liquid and on-site systems to industrial, medical and welding customers on delivery routes. ECOM connects customer orders, delivery tickets, cylinder movements and invoices to your ERP so deliveries, rentals and billing line up.

View all manufacturing industries

What this covers

Products and business models in industrial gas

Products

  • Oxygen, nitrogen, argon and CO2
  • Specialty and mixed gases
  • Cylinders, bulk tanks and cryogenic liquids
  • Welding supplies and equipment

Business models

  • Producers delivering by route and bulk truck
  • Packaged gas distributors
  • On-site and pipeline supply

Scenarios

Where industrial gas 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.

  • Cylinders as assets

    The problem
    Cylinders go out, come back and are rented, so movements and rental billing matter.
    How ECOM helps
    ECOM carries cylinder identifiers on deliveries and returns and maps rental billing lines.
    What you gain
    Cylinder movements and rental charges reconcile.

    Talk to an EDI/API Expert about cylinders as assets Share a sample 856 Advance Ship Notice, 861 Receiving Advice/Acceptance Certificate and 810 Invoice, or describe what goes wrong, and we will show how it would map to your ERP.

  • Route deliveries and tickets

    The problem
    Deliveries are ticketed and invoiced from the ticket.
    How ECOM helps
    ECOM maps delivery tickets into the ERP and invoices from the ticket.
    What you gain
    Invoices follow the delivered quantity on the ticket.

    Talk to an EDI/API Expert about route deliveries and tickets Share a sample 856 Advance Ship Notice and 810 Invoice, or describe what goes wrong, and we will show how it would map to your ERP.

  • Bulk quantities and telemetry

    The problem
    Bulk tank levels trigger replenishment.
    How ECOM helps
    ECOM connects replenishment signals (such as bulk tank levels) to orders where the customer shares them.
    What you gain
    Replenishment starts from the shared level.

    Talk to an EDI/API Expert about bulk quantities and telemetry Share a sample 862 Shipping Schedule and 850 Purchase Order, or describe what goes wrong, and we will show how it would map to your ERP.

Who you connect with

Trading relationships for industrial gas manufacturers

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

Industrial and manufacturing customers
Order gases and equipment and expect delivery by route or bulk truck.
Welding supply distributors
Resell packaged gases and equipment to smaller accounts.
Healthcare facilities
Order medical gases under their own requirements, handled outside this integration.
Equipment and cylinder suppliers
Supply assets whose movements and rentals you track.
Own fleet and carriers
Deliver by route and bulk truck.

Typical workflow

Where ECOM connects your systems and trading partners

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

  1. Industrial customer or distributor→Your plant and ERP 850 Purchase Order The customer order: items, quantities, prices, ship-to and requested dates.
  2. Industrial customer or distributor→Your plant and ERP 862 Shipping Schedule Standing delivery schedule for a customer's bulk or cylinder program.
  3. Industrial customer or distributor→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
  4. Your plant and ERP→Industrial customer or distributor 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
  5. Your plant and ERP→Industrial customer or distributor 856 Advance Ship Notice Delivered quantity, cylinder IDs and tickets.
  6. Your plant and ERP→Industrial customer or distributor 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
  7. Industrial customer or distributor→Your plant and ERP 861 Receiving Advice/Acceptance Certificate Customer receipt for reconciling bulk deliveries.
  8. Your plant and ERP→Equipment supplier 850 Purchase Order Purchase orders for cylinders, valves and equipment with quantities and requested delivery dates.
  9. Equipment supplier→Your plant and ERP 856 Advance Ship Notice Cylinder, valve and equipment shipments with quantity and serial where provided, used to plan receiving.
  1. Orders and standing deliveries

    Orders (850) and standing releases (862).

  2. Route and deliver

    Dispatch uses the order; delivery tickets record quantity.

  3. Delivery confirmation

    The 856 and ticket data report delivered quantity and cylinders.

  4. Invoice from tickets

    The 810 bills product, rental and delivery charges.

  5. Cylinder reconciliation

    Cylinders out and returned are reconciled.

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 gas manufacturers
850 Purchase Order You receive The customer order: items, quantities, prices, ship-to and requested dates.
862 Shipping Schedule You receive Standing delivery schedule for a customer's bulk or cylinder program.
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 Delivered quantity, cylinder IDs and tickets.
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 receipt for reconciling bulk deliveries.
850 Purchase Order (supplier side) You send Purchase orders for cylinders, valves and equipment with quantities and requested delivery dates.
856 Advance Ship Notice (supplier side) You receive Cylinder, valve and equipment shipments with quantity and serial where provided, used to plan receiving.

Other exchanges you may meet

  • Telemetry feeds for bulk tank levels (outside EDI)
  • Customer 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

Cylinders, tickets and rental billing

Cylinders are tracked assets that go out and come back. The delivery ticket, cylinder identifiers and rental charges should reconcile with the invoice, and bulk deliveries are metered and ticketed. Medical gas requirements come from the customer and applicable rules, not from the integration.

  • Batches and certificates

    Shipments are tied to production batches, and customers may expect certificates or test results with the shipment. Those documents come from quality and production systems.

  • Bulk and packaged units

    Product ships by tank car, tank truck, drum, tote, bag or pallet. Units, packaging and conversions need to agree across orders and invoices.

  • Shipping paperwork

    Safety and transport paperwork accompanies many shipments. The exchange of order and shipment data supports it; ECOM does not replace your compliance processes.

Connected systems

Systems that send and receive this data

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

  • ERP
  • Route and dispatch
  • Cylinder tracking
  • 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 industrial customer 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 and route and dispatch 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 gas manufacturers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Cylinders delivered do not match the ticketThe difference can be flagged for review so rental billing and the customer’s record stay right.
Rental charge missing from an invoiceThe invoice can be held for review until the rental line is present.

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 bulk-tank telemetry drive deliveries?

Telemetry sits outside EDI. The orders and deliveries it generates can be integrated like any others.

Does ECOM handle medical-gas regulation?

No. Regulatory compliance stays with your teams. The integration exchanges the order, delivery and invoice data.

Can batch data and test results be exchanged electronically?

Where a customer asks for batch data or test results in electronic form, it can be mapped from your quality or production system into the document or file the partner specifies. The format is set by that partner.

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 gas 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.