Manufacturing · Chemicals, Plastics and Rubber

EDI and API Integration for Lubricant, Grease and Petroleum Product Manufacturers

Lubricant, grease and petroleum product makers sell packaged and bulk product to distributors, fleets and industrial users, with batch tracking and mixed container sizes. ECOM connects orders, batch data, deliveries and invoices to your ERP.

View all manufacturing industries

What this covers

Products and business models in lubricant, grease and petroleum product

Products

  • Motor oils and automotive lubricants
  • Industrial lubricants and greases
  • Fuels, solvents and specialty petroleum
  • Drums, pails, totes and bulk

Business models

  • Blenders selling to distributors
  • Fleet and industrial accounts
  • Private label

Scenarios

Where lubricant, grease and petroleum product 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.

  • Mixed container sizes

    The problem
    Quarts, pails, drums, totes and bulk.
    How ECOM helps
    ECOM maps quarts, pails, drums, totes and bulk to the customer’s items and units.
    What you gain
    Container sizes post to the right item.

    Talk to an EDI/API Expert about mixed container sizes 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.

  • Batch and product data

    The problem
    Batch records and product data sheets accompany orders.
    How ECOM helps
    ECOM carries batch and product data references onto the 856 and sends test data (863) where asked.
    What you gain
    Batch records travel with the order.

    Talk to an EDI/API Expert about batch and product data 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.

  • Bulk delivery and metering

    The problem
    Bulk deliveries are metered and ticketed, and invoices have to follow the metered quantity on the ticket.
    How ECOM helps
    ECOM maps bulk delivery tickets and metered quantities into the ERP and invoice.
    What you gain
    Invoices follow the metered quantity recorded on the delivery ticket.

    Talk to an EDI/API Expert about bulk delivery and metering 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.

Who you connect with

Trading relationships for lubricant, grease and petroleum product manufacturers

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

Lubricant distributors
Order packaged product and bulk by container size.
Fleets and industrial users
Order direct for maintenance programs and bulk delivery.
Retailers and quick-lube chains
Replenish packaged oils under program rules.
Base oil and additive suppliers
Supply the inputs whose price and availability shape blends.
Tank-truck and parcel carriers
Deliver bulk and packaged product.

Typical workflow

Where ECOM connects your systems and trading partners

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

  1. Distributor or industrial user→Your plant and ERP 850 Purchase Order The customer order: items, quantities, prices, ship-to and requested dates.
  2. Distributor or industrial user→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. Distributor or industrial user→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
  4. Your plant and ERP→Distributor or industrial user 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 or industrial user 856 Advance Ship Notice Batch and container-size detail.
  6. Your plant and ERP→Distributor or industrial user 863 Report of Test Results Batch test results where asked.
  7. Your plant and ERP→Distributor or industrial user 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
  8. Your plant and ERP→Base oil and additive supplier 850 Purchase Order Purchase orders for base oils and additives with quantities and requested delivery dates.
  9. Base oil and additive supplier→Your plant and ERP 856 Advance Ship Notice Base oil and additive shipments (bulk or packaged) with batch and quantity, used to plan receiving and blending.

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), changes (860) and customer schedules (862) post by container size.

  2. Blend and fill

    Production creates batches and fills containers, recording batch data.

  3. Deliver

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

  4. Send the ship notice with batch detail

    The 856 reports batch and container size; test results (863) follow where asked.

  5. Invoice

    The 810 follows delivery.

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 lubricant, grease and petroleum product manufacturers
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 Delivery status for bulk deliveries.
856 Advance Ship Notice You send Batch and container-size detail.
863 Report of Test Results You send Batch test results where asked.
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 base oils and additives with quantities and requested delivery dates.
856 Advance Ship Notice (supplier side) You receive Base oil and additive shipments (bulk or packaged) with batch and quantity, used to plan receiving and blending.

Other exchanges you may meet

  • Distributor portals
  • Safety data sheet exchange outside EDI

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

Containers, batches and bulk delivery

Orders for the same product vary by container size, from quarts to bulk. Bulk deliveries need quantity reconciliation from the meter or ticket to the invoice, and batch records and product data sheets accompany orders.

  • 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 with process manufacturing
  • Terminal systems
  • Warehouse management
  • Distributor 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 distributor or industrial user, 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 process manufacturing and terminal 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 lubricant, grease and petroleum product manufacturers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Container size not recognized on an orderThe line can be held for review so quarts are not shipped as drums or the reverse.
Bulk ticket quantity differs from the orderThe variance can be flagged for review before invoicing.

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 delivery tickets feed invoices?

Yes. Ticket data from your terminal or dispatch system can flow into the ERP so invoices follow delivered quantities.

Does ECOM handle fuel tax reporting?

No. Tax and regulatory reporting stay with your teams. The integration carries the underlying 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 lubricant, grease and petroleum product 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.