--- title: "EDI 850 and 860 intake for component reels and revisions" description: "Validate distributor 850 orders and 860 changes against part cross-references, approved reel conversions and open NetSuite commitments before demand posts." canonical: https://www.stacksync.com/blog/electronics-edi-850-860-part-reel-revision last_modified: 2026-09-18 --- # Electronic-component EDI 850 and 860: validate part references, reels and 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 A revised part suffix and a reel unit with no conversion should stop a line for review, not become the closest item multiplied by a default count. Author Alexis Favre · Co-Founder & CTO Published September 18, 2026 Read time 4 min read APP TIPS ## The operating decision Electronic-component manufacturers receiving EDI orders should preserve the partner’s part reference, selling unit, line identity and accepted revision. Use the agreed 850/860 process to distinguish original orders from buyer changes, then validate the business meaning before updating ERP demand. A valid message does not establish that a reel quantity is known or that a component is approved for the requested application. Separate receipt, review, application and partner response so retries cannot create duplicate orders. Explore the complete [electrical and electronic components integration and automation hub](https://www.stacksync.com/industry/manufacturing/electrical-electronic-components) for the systems and processes around this guide. ![Summary card: EDI 850 and 860 intake for component reels and revisions](https://www.stacksync.com/images/blog-highlights/icp-electronics-edi-850-860-part-reel-revision.webp) ## What this looks like in electrical and electronic components A supplier receives a distributor PO for reels of a component and later a change using a revised part suffix. The ERP stores base units and the existing cross-reference applies to a different packaging definition. If the mapping strips the suffix and multiplies by a default reel count, it can accept the wrong item and quantity. The intake needs the approved partner-part relationship, applicable unit conversion and current order state. Product operations resolves identity, engineering addresses restrictions and order management accepts the resulting change. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Partner order line | Customer operations | Retain distributor, PO, line and version references through the destination mapping. | | Part cross-reference | Product operations | Preserve incoming customer and manufacturer identifiers alongside the reviewed internal item. | | Packaging definition | Product data owner | Apply only the approved reel, tray, pack or piece conversion for the relevant scope. | | Accepted change and response | Order management | Record the approved line outcome and keep response delivery separate from ERP application. | ![Record ownership diagram: Partner order line, Part cross-reference, Packaging definition](https://www.stacksync.com/images/blog-diagrams/icp-electronics-edi-850-860-part-reel-revision.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Review the partner’s actual document examples Confirm original order, change and cancellation conventions with the implementation guide. Identify how packaging units and part suffixes are represented. Do not assume that another distributor’s map captures the same commercial meaning. 2. 02 Validate identity before quantity conversion Resolve the exact product reference and required applicability. Preserve suffixes and original identifiers for review. If the mapping is uncertain, keep the line pending rather than creating a new product or selecting the closest available item. 3. 03 Use the applicable packaging rule Retain source quantity and unit with the reviewed base-unit calculation. Check its customer and effective scope. A later pack change must not reinterpret earlier accepted orders automatically. 4. 04 Compare changes with current commitments Apply an 860 request to the intended existing line and inspect allocations or shipments that constrain acceptance. Route technical or commercial changes to their owners. Keep the currently accepted order visible while the proposed revision is reviewed. 5. 05 Apply once and reconcile the response Use stable business references and processing state to recognize repeated requests. Confirm the destination result before recording application success. Build the partner response from accepted outcomes and retry transmission separately from the business update. ![5-step operating sequence: EDI 850 and 860 intake for component reels and revisions](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-electronics-edi-850-860-part-reel-revision.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### A changed suffix has no approved cross-reference Route the line to product operations and retain both the original and requested references. ### The source unit says reel but no conversion exists Keep the proposed quantity unresolved until the product owner confirms it. ### A repeated original arrives after a change Prevent the older state from undoing the accepted revision and preserve it as processing evidence. ## What to verify before expanding - The exact partner part reference remains traceable after item mapping. - Packaging conversion uses an approved scoped definition rather than a default count. - Repeated messages cannot create or reapply the same accepted demand. - A failed response transmission can be retried without another ERP update. ## 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 partner order line example and the exception your team handles most often, for example A changed suffix has no approved cross-reference. - [EDI order automation for electrical and electronic component manufacturers](https://www.stacksync.com/use-case/electronics-edi-order-part-packaging-automation) - [Electrical manufacturers: connect Salesforce assembly quotes to Acumatica orders](https://www.stacksync.com/blog/electrical-manufacturers-salesforce-acumatica-configured-assemblies) - [Electronic components: connect NetSuite and Postgres revision-aware stock allocation](https://www.stacksync.com/blog/electronics-netsuite-postgres-component-revision-allocation) - [Electrical components on Shopify: map NetSuite variants, packs and order quantities](https://www.stacksync.com/blog/electrical-components-netsuite-shopify-pack-variant-orders) - [EDI vs API Integration for Supply Chain Data (2026 Guide)](https://www.stacksync.com/blog/edi-vs-api-integration-supply-chain-data-guide) - [Field-Level Change Detection: The Key to Efficient Real-Time Bidirectional CRM Sync](https://www.stacksync.com/blog/field-level-change-detection-the-key-to-efficient-real-time-bidirectional-crm-sync) 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 Can an EDI translator decide component equivalence? It can map approved relationships and flag exceptions. Technical applicability belongs to the manufacturer’s designated engineering process. Should every corrected order create a new ERP order? Usually the mapping should preserve the original business identity and apply the approved change to the intended record. Follow the partner and ERP process rather than creating duplicates for convenience. What should the test set include? Use an original order, a reel-unit ambiguity, a part-reference change, a replay and a partially committed line. Inspect both the accepted quantities and the 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 Electronic component substitutions: route evidence to engineering before changing supply 4 min read read](https://www.stacksync.com/blog/electronics-component-substitution-engineering-workflow) [App tips Electronics AI mapping exceptions: part suffixes, packaging units and revision restrictions 4 min read read](https://www.stacksync.com/blog/electronics-genie-part-number-packaging-exceptions) [App tips AI agents for electronics order intake: resolve customer part references for review 4 min read read](https://www.stacksync.com/blog/electronics-genie-customer-part-cross-reference) ## 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/)