--- title: "EDI 850 and 860 for automotive firm orders and revisions" description: "An 850 and 860 process that compares each buyer change with the accepted order, resolves plant and part, and responds from the supplier’s decision." canonical: https://www.stacksync.com/blog/automotive-edi-850-860-firm-orders-revisions last_modified: 2026-09-18 --- # Automotive component EDI 850 and 860: preserve firm orders and approved revisions > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Original 850 orders, 860 change requests and partner responses stay traceable through replays, retries and engineering cutovers under the customer agreement. Author Alexis Favre · Co-Founder & CTO Published September 18, 2026 Read time 4 min read APP TIPS ## The operating decision Automotive suppliers using an agreed X12 850/860 order process should preserve original order identity, line-level revisions and business acceptance independently from transport receipt. Keep forecasting and scheduling messages under their own documented interpretation rather than treating every incoming quantity as another purchase order. Validate customer plant, part reference and engineering applicability before a revision changes accepted demand. A technically valid document does not override released production or an established customer approval boundary. Explore the complete [automotive components integration and automation hub](https://www.stacksync.com/industry/manufacturing/automotive-components) for the systems and processes around this guide. ![Summary card: EDI 850 and 860 for automotive firm orders and revisions](https://www.stacksync.com/images/blog-highlights/icp-automotive-edi-850-860-firm-orders-revisions.webp) ## What this looks like in automotive components A supplier receives an 850 for a customer plant, followed by an 860 that changes a line’s requested date and part reference. A separate planning feed also contains quantities for the same period. If the intake combines those sources without their business rules, it can double demand or replace a valid engineering revision. The useful process records the original order, compares the buyer’s change with the accepted state and routes consequential differences to planning and engineering. The response then reflects the supplier’s actual decision under the partner agreement. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Original customer order | Customer operations | Preserve partner, plant, PO and line identities before creating ERP references. | | Buyer change request | Order management | Keep the requested differences and applicable version separate from the accepted order state. | | Engineering applicability | Engineering | Resolve the requested part or revision under the approved customer-program rules. | | Processing and response ledger | Integration operations | Track receipt, validation, review, application and response delivery as separate states. | ![Record ownership diagram: Original customer order, Buyer change request, Engineering applicability](https://www.stacksync.com/images/blog-diagrams/icp-automotive-edi-850-860-firm-orders-revisions.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Confirm the actual partner process Review current implementation guidance and representative documents. Establish how original orders, changes, cancellations and business responses operate for this customer. Identify separate forecast or schedule sources so their quantities are not added to firm demand accidentally. 2. 02 Resolve plant and part context Use approved cross-references for customer sites and items. Preserve incoming values alongside resolved identifiers. Hold unknown mappings for review rather than assigning them to a default plant or the newest available part revision. 3. 03 Compare the change with committed work Identify the line-level quantity, timing and specification differences. Review existing production, allocations and shipments where relevant. Route changes outside the predefined acceptance conditions to the responsible owners and keep the current accepted commitment visible. 4. 04 Apply the accepted business update once Use stable references and an application ledger to distinguish replays from new changes. Confirm the destination outcome before marking the update applied. Reconcile an uncertain response instead of blindly creating another order or change. 5. 05 Respond from the accepted outcome Generate the agreed partner response from what the supplier actually accepted, including unresolved or rejected lines where the process allows them. Retry failed response delivery independently from the already completed ERP application. ![5-step operating sequence: EDI 850 and 860 for automotive firm orders and revisions](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-automotive-edi-850-860-firm-orders-revisions.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### The change arrives before the original is available Hold it with its references and investigate missing intake or sequence. Do not invent an original order to satisfy a processing dependency. ### A forecast contains the same quantities Keep it under its documented planning meaning and prevent double counting with the firm order. ### A requested revision crosses an engineering cutover Route applicability to engineering and planning before accepting the changed line. ## What to verify before expanding - The original order and every accepted change remain traceable. - Separate planning feeds do not automatically create duplicate firm demand. - A replay cannot reapply an already accepted revision. - Response delivery status is distinguishable from ERP application and business acceptance. ## Connect this process to the rest of your operation [Explore Stacksync EDI](https://www.stacksync.com/edi) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real original customer order example and the exception your team handles most often, for example the change arrives before the original is available. - [EDI order and revision automation for automotive component suppliers](https://www.stacksync.com/use-case/automotive-edi-order-revision-automation) - [Automotive component suppliers: connect Salesforce program awards and NetSuite demand](https://www.stacksync.com/blog/automotive-components-salesforce-netsuite-program-award-demand) - [Automotive suppliers: separate firm releases and forecasts in Dynamics and SQL Server](https://www.stacksync.com/blog/automotive-dynamics-sql-server-firm-release-forecast) - [Automotive components: connect NetSuite shipments to Postgres lot evidence](https://www.stacksync.com/blog/automotive-netsuite-postgres-lot-shipment-traceability) - [EDI for Automotive Suppliers and OEMs: Powering Real-Time Manufacturing Communication](https://www.stacksync.com/blog/edi-for-automotive-suppliers-and-oems-powering-real-time-manufacturing-communication) - [Bi-Directional Sync vs CDC Duplicates: Reliability Guide](https://www.stacksync.com/blog/bi-directional-sync-vs-cdc-duplicates-reliability-guide) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Oracle NetSuite: using external IDs](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_156334828635.html) - [X12: supply chain transaction flow](https://x12.org/flow/supply-chain) FAQ ## Frequently asked questions Do all automotive customers use 850 and 860 for the same purpose? No. Follow the actual partner agreement and implementation guide. Automotive demand processes can involve other document families whose meaning must be modeled separately. Does successful EDI transport prove schedule acceptance? No. Receipt, technical validation and business acceptance represent different states and should remain visible. What should a first customer pilot include? Use an original order, a replay, a part or date change, an out-of-sequence request and an overlapping planning source. Verify both the accepted demand and partner response. About the author Alexis Favre Co-Founder & CTO Alexis Favre is the Co-Founder and CTO of Stacksync (YC W24), the first real-time and two-way sync for enterprise data at scale. Alexis is a Y Combinator alumni with expertise in large scale data engineering. [All posts by Alexis Favre](https://www.stacksync.com/blog/author/alexis-favre) About Stacksync Stacksync powers real-time, two-way sync between CRMs, ERPs, and databases. Engineers sync data at scale and automate workflows, not dirty API plumbing. Stacksync ## Explore these integrations and topics - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [connector PostgreSQL integrations](https://www.stacksync.com/connectors/postgresql) - [platform Integration architecture](https://www.stacksync.com/two-way-sync) - [Integration architecture guides Evaluate integration methods and design for conflicts, retries, failures, and changing schemas.](https://www.stacksync.com/blog#topic-integration-architecture) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [App tips Automotive component engineering cutovers: coordinate open demand and existing inventory 4 min read read](https://www.stacksync.com/blog/automotive-engineering-cutover-open-orders-workflow) [App tips Automotive supplier delays: build recovery plans around firm customer releases 4 min read read](https://www.stacksync.com/blog/automotive-supplier-delay-firm-release-recovery) [App tips AI agents for automotive release review: assemble quantity, date and revision differences 4 min read read](https://www.stacksync.com/blog/automotive-genie-customer-release-review) ## You just read how it should work. See it run on your own data. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)