--- title: "Equipment distributor EDI for kits and partial shipments" description: "Distributor EDI kit orders mapped to NetSuite kit definitions, with one demand line preserved across components, partial shipments and quantity revisions." canonical: https://www.stacksync.com/blog/equipment-edi-distributor-kit-order-lines last_modified: 2026-09-18 --- # Equipment EDI orders: preserve distributor kits, service lines and partial shipments > 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 One repair kit ordered by a distributor should remain one commercial line in NetSuite, even when it ships as several components or the quantity later changes. Author Alexis Favre · Co-Founder & CTO Published September 18, 2026 Read time 4 min read APP TIPS ## The operating decision Equipment manufacturers receiving distributor EDI orders should preserve the difference between a commercial kit, its required components and any associated service. Map the partner’s order and line references to the accepted ERP representation, then retain those links through revisions and partial shipments. EDI receipt does not prove that a configured kit is compatible or complete. Business validation and the partner’s agreed acknowledgment process must reflect what the supplier can actually accept. Explore the complete [industrial equipment and machinery integration and automation hub](https://www.stacksync.com/industry/manufacturing/industrial-equipment-machinery) for the systems and processes around this guide. ![Summary card: Equipment distributor EDI for kits and partial shipments](https://www.stacksync.com/images/blog-highlights/icp-equipment-edi-distributor-kit-order-lines.webp) ## What this looks like in industrial equipment and machinery A machinery business receives an aftermarket distributor order for a repair kit and a separate installation service. The ERP represents the kit using several components, one of which is unavailable. A simplistic mapping can acknowledge the full kit because its parent item exists, or accidentally count each component as another ordered kit. The intake needs an approved kit definition and a clear relationship between the distributor line and internal fulfillment records. A later quantity change must update the commercial demand without duplicating component requirements already accepted. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Distributor PO line | Customer operations | Preserve partner, PO, line and revision identity for the commercial request. | | Approved kit definition | Product operations | Maintain the applicable component relationships and version used for the accepted order. | | Service obligation | Service operations | Keep installation or other service scope distinct from physical equipment or parts quantity. | | Fulfillment relationship | Order management | Link partial internal shipments to the original commercial line without multiplying the ordered quantity. | ![Record ownership diagram: Distributor PO line, Approved kit definition, Service obligation](https://www.stacksync.com/images/blog-diagrams/icp-equipment-edi-distributor-kit-order-lines.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Agree the partner’s line conventions Review how kits, accessories and services appear in the implementation guide. Identify whether the partner expects kit-level or component-level responses. Do not infer its intended commercial grain from the way the ERP stores assemblies. 2. 02 Resolve the approved kit and compatibility Match the ordered reference to the correct kit version and any applicable equipment requirements. Present missing or conflicting references for product or service review. An active catalog item is not enough when the kit depends on a particular installed configuration. 3. 03 Represent demand and fulfillment separately Keep the commercial ordered quantity stable while linking the internal component and shipment records. Define how partial fulfillment appears in the partner response. Avoid summing component quantities into the number of kits the customer ordered. 4. 04 Apply revisions with existing commitments visible Compare changes against the accepted line and any shipped or allocated components. Route consequential changes to order management. Repeated documents should resolve the existing order and processing ledger rather than create another set of kit requirements. 5. 05 Reconcile the accepted response Prepare acknowledgments and subsequent partner messages from the recorded business outcome under the agreed process. Track response transmission separately from ERP application so a failed message delivery can be retried without recreating demand. ![5-step operating sequence: Equipment distributor EDI for kits and partial shipments](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-equipment-edi-distributor-kit-order-lines.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### One required kit component is unavailable Keep the kit’s fulfillment constraint visible and ask the owner to approve a partial or revised commitment. ### A service line arrives without a machine reference Route the missing scope to service operations rather than treating it as an ordinary stock item. ### The distributor changes a partially shipped kit order Review the remaining obligation and commercial terms; do not reverse shipped component history automatically. ## What to verify before expanding - A kit ordered once remains one commercial demand line despite several internal components. - Service obligations retain separate scope and ownership. - A repeated document cannot duplicate accepted component requirements. - The partner response reflects accepted availability and partial commitments accurately. ## 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 distributor PO line example and the exception your team handles most often, for example one required kit component is unavailable. - [Equipment manufacturers: connect Salesforce configurations to NetSuite orders](https://www.stacksync.com/blog/equipment-manufacturers-salesforce-netsuite-configured-order) - [Equipment manufacturers: connect NetSuite and Postgres machine serial history](https://www.stacksync.com/blog/equipment-manufacturers-netsuite-postgres-machine-serial-history) - [Equipment aftermarket: connect Salesforce parts quotes to Acumatica order status](https://www.stacksync.com/blog/equipment-salesforce-acumatica-aftermarket-parts-quotes) - [Human-in-the-Loop Automation: When to Escalate a Workflow to a Person](https://www.stacksync.com/blog/human-in-the-loop-automation-when-to-escalate) - [Coordinate Closed-Won Onboarding Across Salesforce and NetSuite](https://www.stacksync.com/blog/coordinate-closed-won-onboarding-across-salesforce-and-netsuite) 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 every kit be expanded automatically? Only when an approved definition and applicable version exist and the intended ERP operation is supported. Unknown or configuration-dependent kits need a review path. Why preserve the original distributor line? It is the durable reference for acknowledgments, revisions, partial shipments and later disputes even when internal fulfillment uses several records. What should the pilot include? Use a kit with a missing component, a service line, a partial shipment and a revised quantity. Reconcile commercial demand, internal records and partner responses together. 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 Equipment commissioning readiness: connect sales promises, site prerequisites and service dispatch 4 min read read](https://www.stacksync.com/blog/equipment-commissioning-readiness-workflow) [App tips Coordinate Closed-Won Onboarding Across Salesforce and NetSuite 8 min read read](https://www.stacksync.com/blog/coordinate-closed-won-onboarding-across-salesforce-and-netsuite) [App tips AI agents for equipment aftermarket requests: prepare compatible parts proposals 4 min read read](https://www.stacksync.com/blog/equipment-genie-aftermarket-part-request-guide) ## 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/)