Guides

QAD EDI integration guide: EDI eCommerce, schedules and shippers

How manufacturers on QAD Enterprise Applications and QAD Adaptive ERP exchange schedules, ship notices and invoices with their customers.

2 min read · Updated October 19, 2026

The short answer

QAD Enterprise Applications, now part of QAD Adaptive ERP, can process EDI through its built-in EDI eCommerce functionality or through QXtend and APIs, with an integration layer handling connectivity and translation. For automotive and industrial suppliers, inbound planning and shipping schedules update customer schedules, and shippers drive outbound ship notices and invoices.

How EDI flows through QADSequence diagram for QAD. The trading partner sends a 830 and 862 schedules, 850 orders to the integration layer, which translates and validates it and update customer schedules and orders through EDI eCommerce, QXtend or APIs in QAD Adaptive ERP. In QAD, required ship schedules drive shippers; invoices follow. Shipper and invoice, and the integration layer sends the 856 ship notice and 810 invoice to the partner.How EDI flows through QADThe integration layer translates; QAD keeps the business recordsTrading partnerIntegration layerQAD830 and 862 schedules, 850 ordersTranslate and validateCross-references turn partner codes into your items and locationsUpdate customer schedules and ordersThrough EDI eCommerce, QXtend or APIs inQAD Adaptive ERPRequired ship schedules drive shippers; invoices followShipper and invoice856 ship notice and 810 invoiceInterfaces and objects as described in this guide. Your version, licensing and partner requirements decide which ones apply.
How EDI flows through QADSequence diagram for QAD. The trading partner sends a 830 and 862 schedules, 850 orders to the integration layer, which translates and validates it and update customer schedules and orders through EDI eCommerce, QXtend or APIs in QAD Adaptive ERP. In QAD, required ship schedules drive shippers; invoices follow. Shipper and invoice, and the integration layer sends the 856 ship notice and 810 invoice to the partner.How EDI flows through QADThe integration layer translates; QAD keeps thebusiness recordsTradingpartnerIntegrationlayerQAD830 and 862 schedules,850 ordersTranslate and validateCross-references turnpartner codes into youritems and locationsUpdate customerschedules and ordersThrough EDI eCommerce,QXtend or APIs in QADAdaptive ERPRequired shipschedules driveshippers; invoicesfollowShipper and invoice856 ship notice and 810invoiceInterfaces and objects as described in this guide.Your version, licensing and partner requirementsdecide which ones apply.

Read the diagram from top to bottom. QAD does not exchange X12 itself in this design: the integration layer handles the partner connection and translation, and QAD creates and posts the business records. Outbound documents are built from what QAD actually recorded.

Expand diagram Download SVG

How EDI connects to QAD

QAD is widely used by automotive, industrial, life sciences and consumer products manufacturers. Automotive suppliers in particular exchange a steady flow of schedules, ship notices and invoices with vehicle manufacturers and tier-one customers. QAD offers two broad integration paths: its built-in EDI eCommerce functionality, and QXtend and newer APIs for XML and web service integration.

Document mapping

EDI documentDirectionQAD object
830 planning scheduleInboundCustomer planning schedule
862 shipping scheduleInboundCustomer shipping schedule (required ship)
850 purchase orderInboundSales order or scheduled order
856 ship noticeOutboundShipper
810 invoiceOutboundInvoice

Schedules

Schedule-based customers send updated demand frequently. Good schedule processing:

  • Replaces the previous schedule rather than adding to it.
  • Separates firm requirements from forecast.
  • Reconciles cumulative quantities shipped and received with each customer.
  • Flags significant changes inside the frozen period for review.

Shippers and ship notices

In QAD, shippers record what was shipped, including containers and items. Automotive customers expect ship notices within minutes of departure, with container and label details that match AIAG-style or GS1-128 labels. Build ship notices from confirmed shippers and print labels from the same data.

Integration options

  • EDI eCommerce: ERP-side processing and mapping for inbound and outbound documents.
  • QXtend: XML and web service interfaces for external integration.
  • APIs in QAD Adaptive ERP: newer options for real-time scenarios.

The right choice depends on your QAD version, deployment and existing mappings.

Best practices

  • Test schedule processing with real schedule histories from each major customer.
  • Reconcile cumulative quantities regularly and after any correction.
  • Send ship notices immediately on shipper confirmation.
  • Keep customer-specific label and packaging rules documented and tested.
  • Monitor schedules, shippers and invoices daily and assign owners for exceptions.
QAD Enterprise Applications integration and implementationIntegration methods, document mappings and ECOM services for QAD Enterprise Applications.

Frequently asked questions

What is QAD EDI eCommerce?

EDI eCommerce is QAD functionality for processing inbound and outbound EDI documents with mappings maintained on the ERP side, working alongside an EDI translator for partner communication.

What is QXtend?

QXtend provides XML and web service interfaces for integrating QAD with external systems, including integration layers that translate EDI documents.

Why do cumulative quantities matter?

Automotive customers track cumulative quantities shipped and received. If supplier and customer totals disagree, schedules are misread, leading to over- or under-shipment. Reconciling cumulative quantities regularly prevents this.

Have an EDI question we did not answer?

ECOM's integration specialists can review your partners, documents and systems and recommend next steps.