Automotive integration

Cummins EDI integration

What Cummins publishes about supplier EDI (UN/EDIFACT under its implementation guides, Sterling Web Forms or traditional EDI, the iSupplier portal) and what is typical practice, with how ECOM helps.

At a glance

Cummins integration, in three pictures

The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific Cummins program or a customer relationship.

Illustration of a factory with a conveyor carrying boxes, representing the automotive industry that Cummins operates in.
Industry. Automotive: where Cummins operates.
Workflow diagram: your ERP and warehouse systems exchange documents with Cummins through ECOM. You send DESADV, INVOIC; you receive DELFOR; CONTRL acknowledgments go both ways. Your systems ERP · warehouse · finance ECOM integration map · validate · connect · monitor Cummins DESADV INVOIC DESADV INVOIC DELFOR DELFOR CONTRL both ways
Workflow. Documents in each direction. Orange: you send. Blue: you receive. Typical, not confirmed. Shown for the program "Schedule-driven program"; the other programs are listed in the flow below.
Comparison diagram: without integration, documents are re-keyed, files are emailed and rejections are found late; with ECOM, documents are mapped to your ERP, validated and monitored, and exceptions are visible early. Without integration Orders re-keyed by hand Files emailed or uploaded Rejections found late With ECOM Documents mapped to your ERP Every file validated and monitored Exceptions visible early
Outcome. From manual handling to a monitored flow. No figures: results depend on your setup.

Talk to an EDI/API Expert about Cummins

Tell us which documents you exchange with Cummins, which ERP you run and when you need to be live. A specialist will outline the connection, mapping and testing plan. This page is a guide based on typical practice; it does not mean ECOM works with Cummins.

  • Review of Cummins' requirements with you, once you have them
  • EDI and API integration with your ERP and warehouse systems
  • Monitoring and managed service after go-live, if you want it

Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.

Takes about 30 seconds. Phone and note are optional.

Your request is about

Trading partner
Cummins

When should we talk?

Times are in your time zone. We use this to schedule the conversation.

We use your details only to respond to your request. See our privacy notice. Prefer to talk? Call Sales at 972-836-7750.

Integration and onboarding

How Cummins integration fits your systems

Your systemsERP, WMS and accounting
ECOMMapping, validation, connectivity and monitoringTraditional EDI · Sterling Web Forms · iSupplier portal
CumminsIts program, documents and requirements
  1. ConfirmConfirm your Cummins program, role and the documents it requires.
  2. MapMap each document to your ERP fields and business rules.
  3. ConnectConfigure the connection and security the program needs.
  4. TestTest against the applicable specifications and acknowledgments.
  5. Go liveGo live with monitoring, alerts and exception handling.
Typical implementation path. Exact requirements are confirmed against the applicable specifications during onboarding.

Overview

Understanding Cummins integration

Who this is for: Tier 2 and component suppliers, materials providers and logistics partners that supply Cummins, and their planning and EDI teams.

Scope: Documented by Cummins: mandatory EDIFACT EDI under its implementation guides, Sterling Web Forms or traditional EDI, the iSupplier portal, DELFOR handling and EDI invoices for UK and Mexico. Other documents and directions are typical practice.

Cummins designs and manufactures engines and power systems. ECOM's directory lists it under engines and power systems. Suppliers to a tier 1 company usually receive purchase orders and schedules, ship to its plants or distribution points, and work to its labeling and quality rules.

Cummins publishes its supplier EDI requirements. Documented by Cummins: suppliers must use EDI in UN/EDIFACT formats under Cummins implementation guides, either through Sterling Web Forms (for suppliers that are not EDI-capable) or traditional EDI, starting with the Supplier EDI Questionnaire. Portals and requirements differ by region and business unit. The rest of this page, such as the order documents and who sends what in each program, is typical practice for an automotive supplier: confirm it with Cummins eCommerce support.

ECOM maps the documents to your ERP and warehouse systems, tests them with the trading partner, monitors every file after go-live and handles partner changes, as software, as a managed service or both.

Business scenarios

Where Cummins integration gets complicated

Typical requirements—confirm with your trading partner.

Multi-tier schedule flow-down

Applies to: Schedule-driven program

A tier 1 passes customer schedules down to its suppliers. Changes upstream arrive as new releases that must be handled quickly.

How ECOM helps: ECOM carries each change through to the acknowledgment, shipment and invoice so every document reflects the latest version, and flags changes Cummins has not acknowledged.

What you gain: Shipments and invoices stay in step with the order after changes.

Sequence and kitting

Applies to: Schedule-driven program

Some programs deliver parts in sequence or in kits, which raises label and ship notice precision.

How ECOM helps: ECOM connects shipment and status documents to your ERP, WMS or TMS and shows where each one stands, so late or missing messages are seen early.

What you gain: Teams see current status, and fewer shipments are held up by missing documents.

Engineered parts and cumulative quantities

Applies to: Schedule-driven program

Engineered components move on schedules with cumulative quantity tracking. Differences between shipped and received cumulatives create disputes unless both sides use the same counts.

How ECOM helps: ECOM monitors each document and acknowledgment, flags rejected, late or mismatched ones and routes each exception to a named owner with the document history attached.

What you gain: Problems are corrected before they turn into deductions, write-offs or delayed payment.

Quality and traceability data

Applies to: Schedule-driven program

Quality programs often ask for lot or serial traceability on shipments.

How ECOM helps: ECOM maps item, price and pack data between your systems and Cummins's format and validates it before it is sent, so mismatches are caught on your side.

What you gain: Fewer rejections caused by data that does not match what Cummins has on file.

Workflows

Typical Cummins business workflows

The steps summarize the documents below. Where a step is not in Cummins' published documents, it reflects common practice.

Schedule to invoice

  1. 1Receive DELFOR delivery schedule
  2. 2Ship and send ship notice (ASN)
  3. 3Send invoice
  4. 4Reconcile cumulative quantities

Purchase order cycle (typical)

  1. 1Receive ORDERS purchase order
  2. 2Send ORDRSP response
  3. 3Deliver goods
  4. 4Invoice and reconcile

Documents and APIs

Cummins documents by program

Every document this guide names, with the program it applies to and its status. Required, optional and conditional come from Cummins' published documents cited below; documents marked general guidance are common in this industry but not confirmed for Cummins.

DocumentNameDirectionProgramStatusPurpose
DELFOR Delivery Schedule (planning and forecast) From Cummins Schedule-driven program Named; level not stated Documented by Cummins: each DELFOR fully replaces the previous one, zero quantities are not sent, and planning data must not be auto-firmed.
DESADV Despatch Advice (advance ship notice) To Cummins Schedule-driven program General guidance Cummins documents advance shipment notices (suppliers can also create them in the iSupplier portal); DESADV is the usual UN/EDIFACT message for them. Confirm the exact message and version in the Cummins implementation guide.
INVOIC Invoice To Cummins Schedule-driven program Named; level not stated Documented by Cummins for shipments to its UK and Mexico locations: invoices go by EDI to the specified receiver IDs, and the invoice number must match your financial system. Other bill-to addresses can still be paper-based.
CONTRL Syntax and Service Report Both directions Schedule-driven program General guidance Typically confirms that each interchange was received and could be read.
ORDERS Purchase Order From Cummins Purchase-order program (typical practice) General guidance Typical practice, not Cummins' published list: carries the order with items, quantities, prices and requested dates.
ORDRSP Purchase Order Response To Cummins Purchase-order program (typical practice) General guidance Typical practice, not Cummins' published list: confirms an order or reports changes to quantities, prices or dates.
DESADV Despatch Advice (advance ship notice) To Cummins Purchase-order program (typical practice) General guidance Typically tells the receiver what is on each shipment. Same message as in the schedule-driven program.
INVOIC Invoice To Cummins Purchase-order program (typical practice) General guidance Typically bills for what shipped. Cummins documents EDI invoices only for shipments to its UK and Mexico locations.
CONTRL Syntax and Service Report Both directions Purchase-order program (typical practice) General guidance Typically confirms that each interchange was received and could be read.

Connectivity

How companies connect

  • Traditional EDI

    Documented by Cummins: the supplier receives and interprets EDIFACT files under the Cummins implementation guides. The Supplier EDI Questionnaire is the first onboarding step.

    From Cummins' published documents

  • Sterling Web Forms

    Documented by Cummins: a web-forms method for suppliers that are not EDI-capable, so they can still exchange the required messages.

    From Cummins' published documents

  • iSupplier portal

    Documented by Cummins: it registers suppliers to its iSupplier portal, where suppliers can also create advance shipment notices. Portal variants differ by region and business unit.

    From Cummins' published documents

Challenges

Common integration challenges

  • Schedule replacement

    Cummins says each DELFOR replaces the prior one in full and must not be auto-firmed, so planning systems must handle full replacement rather than deltas.

  • Labeling

    Labels and ship notices must agree. Details depend on your agreement with Cummins.

  • Cumulative accounting

    Cumulative quantity mismatches are a common source of disputes.

  • Multiple customers

    Each customer program may add its own variations.

  • Program-specific details

    The documents, identifiers, versions and test steps for your program are set by Cummins. ECOM works from them during mapping and testing.

Automation options for Cummins suppliers

Four ways to automate. One foundation.

ECOM helps you automate them, meet Cummins' labeling and ship notice requirements, and see what needs action. Cummins sets its program's rules; ECOM confirms which options fit yours.

PRISM Supply Chain Automation Foundation

One platform beneath every option. Use one, or combine them for different partners and documents.

Compliance and actionable visibility

Connect order processing, shipping documentation, trading partner requirements, and performance monitoring through one coordinated workflow. These capabilities help teams improve shipment accuracy, reduce manual work, address compliance risks, and respond to exceptions before they affect customers.

Discuss Your Trading Partner Requirements

Connect Cummins documents to your ERP

ECOM connects the documents you exchange with Cummins to your ERP and warehouse systems, so orders post without re-keying and ship notices and invoices come from the data you already hold.

Industry

Automotive

See how ECOM supports EDI for automotive suppliers and manufacturers.

Industry

Industrial Manufacturing

See how ECOM supports supplier schedules, shipping and invoicing for manufacturers.

Service

Fully Managed EDI

Have ECOM run your EDI connections, monitoring and partner changes.

General EDI flow

How EDI with Cummins typically works

The documents, their order and the timing are Cummins' to set. The programs below list the documents and who sends each; they are typical practice unless a source is shown.

Each program below lists its documents, who sends each one and whether the company documents it. The automation examples are written for “Schedule-driven program”.

Schedule-driven program

Reader: A tier 2 or component supplier, materials provider or logistics partner that supplies Cummins. Counterparty: Cummins (engines and power systems). Relationship: described in the company’s own pages; each document below shows its own status. Source: Cummins: Supply chain systems (supplier EDI and portal); Cummins: EDI FAQs for suppliers. Scope: Cummins suppliers working under its UN/EDIFACT implementation guides; portals and requirements differ by region and business unit.

  1. DELFOR Delivery Schedule (planning and forecast)

    From Cummins to you

    Status: Documented by the company

    Documented by Cummins: each DELFOR fully replaces the previous one, zero quantities are not sent, and planning data must not be auto-firmed.

  2. DESADV Despatch Advice (advance ship notice)

    From you to Cummins

    Status: Typical practice, not confirmed for this company

    Cummins documents advance shipment notices (suppliers can also create them in the iSupplier portal); DESADV is the usual UN/EDIFACT message for them. Confirm the exact message and version in the Cummins implementation guide.

  3. INVOIC Invoice

    From you to Cummins

    Status: Documented by the company

    Documented by Cummins for shipments to its UK and Mexico locations: invoices go by EDI to the specified receiver IDs, and the invoice number must match your financial system. Other bill-to addresses can still be paper-based.

  4. CONTRL Syntax and Service Report

    Both directions

    Status: Typical practice, not confirmed for this company

    Typically confirms that each interchange was received and could be read.

Purchase-order program (typical practice)

Reader: A tier 2 or component supplier, materials provider or logistics partner that supplies Cummins. Counterparty: Cummins (engines and power systems). Relationship: typical practice, not confirmed for this company.

  1. ORDERS Purchase Order

    From Cummins to you

    Status: Typical practice, not confirmed for this company

    Typical practice, not Cummins' published list: carries the order with items, quantities, prices and requested dates.

  2. ORDRSP Purchase Order Response

    From you to Cummins

    Status: Typical practice, not confirmed for this company

    Typical practice, not Cummins' published list: confirms an order or reports changes to quantities, prices or dates.

  3. DESADV Despatch Advice (advance ship notice)

    From you to Cummins

    Status: Typical practice, not confirmed for this company

    Typically tells the receiver what is on each shipment. Same message as in the schedule-driven program.

  4. INVOIC Invoice

    From you to Cummins

    Status: Typical practice, not confirmed for this company

    Typically bills for what shipped. Cummins documents EDI invoices only for shipments to its UK and Mexico locations.

  5. CONTRL Syntax and Service Report

    Both directions

    Status: Typical practice, not confirmed for this company

    Typically confirms that each interchange was received and could be read.

Working from Cummins' published specification?

Tell ECOM which program and documents apply to you. We read the published specification with you, map it to your systems and test against it. Do not send passwords or EDI identifiers with your request.

Next step

Get help with your Cummins program

Each request goes to an ECOM EDI specialist with Cummins' name attached, so the reply starts from your program.

  • Review Cummins' requirements

    Send us Cummins' guide or your program details; we explain the documents, rules and options for meeting them.

    Request a requirements review
  • Connect Cummins to your ERP

    Orders in, ship notices and invoices out, from the ERP and warehouse systems you already run.

    Discuss ERP integration
  • Testing and certification

    Build, test and certify each Cummins document, then go live with monitoring from the first file.

    Plan testing and certification
  • Shipping labels and ASNs

    Labels and ship notices that match Cummins' rules, to help avoid receiving problems and compliance deductions.

    Review shipping compliance

Cummins integration FAQs

Does Cummins use EDI with suppliers?

Yes. Cummins states that all suppliers must use EDI, in UN/EDIFACT formats under its implementation guides, through Sterling Web Forms or traditional EDI. Details differ by region and business unit.

Can ECOM help a tier 2 supplier?

Yes. ECOM maps schedules, ship notices and invoices between a customer's format and your ERP and monitors every file. This page does not indicate a relationship with Cummins.

Which EDI documents are typical for an automotive supplier?

Cummins documents delivery schedules (DELFOR), advance shipment notices and, for UK and Mexico shipments, invoices. Order and order-response messages (ORDERS, ORDRSP) are typical practice, not Cummins' published list.

How does onboarding with Cummins usually work?

Cummins documents the first step: complete the Supplier EDI Questionnaire, then follow the Cummins implementation guides for your region and business unit. Mapping, testing and go-live timing depend on your ERP and Cummins test cycles.

Does this guide mean Cummins endorses ECOM?

No. This is an independent integration guide. It does not indicate an endorsement, partnership or approval by Cummins.

Sources and accuracy

This guide summarizes publicly available information as of November 2026. Cummins sets its own requirements and can change them at any time; your Cummins implementation guide, supplier portal or account contact is the authoritative source for your program.

Request Cummins integration assistance

Tell us about your Cummins program, documents and ERP. We will outline the connection, mapping and testing plan.