--- title: "Prefab supplier EDI for factory and direct-site receipts" description: "Map prefab supplier EDI to the correct factory or site destination and preserve component allocation by project." canonical: https://www.stacksync.com/blog/prefab-supplier-edi-reconcile-component-orders-with-factory-receipts-and-direct-to-site-deliveries last_modified: 2026-09-18 --- # Prefab Supplier EDI: Reconcile Component Orders With Factory Receipts and Direct-to-Site Deliveries > 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 Map prefab supplier EDI to the correct factory or site destination and preserve component allocation by project. Author Alexis Favre · Co-Founder & CTO Published September 18, 2026 Read time 5 min read APP TIPS ## The operating decision Prefab supplier EDI should connect component purchase lines to the approved project requirement, supplier responses, shipment destination and actual receiving evidence. Factory receipts and direct-to-site deliveries are different flows and must not both become factory stock. Preserve item, unit, purchase-line and project references through the exchange. Procurement reviews substitutions and changed promises; the designated receiver confirms quantity and condition at the actual destination. Explore the complete [modular and prefab building supply and installation integration and automation hub](https://www.stacksync.com/industry/construction/modular-prefab-building-installation) for the systems and processes around this guide. ![Summary card: Prefab supplier EDI for factory and direct-site receipts](https://www.stacksync.com/images/blog-highlights/icp-prefab-supplier-edi-reconcile-component-orders-with-factory-receipts-and-direct-to-site-deliveries.webp) ## What this looks like in modular and prefab building supply and installation A modular manufacturer buys components for factory assembly and finishing materials that ship directly to the installation site. One supplier order includes both destinations and several project allocations. The supplier sends split shipments and invoices before all goods arrive. A useful EDI mapping identifies which receipt belongs in factory inventory, which belongs to a site delivery record and which purchase lines remain open, without marking the whole project supplied. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Component purchase line | Procurement | Keep item, unit, approved project allocation and intended destination. | | Supplier response | Supplier and buyer | Record accepted quantities, changed dates and proposed substitutions. | | Factory receipt | Warehouse | Confirm material entering factory custody and usable inventory. | | Direct-site receipt | Site receiving owner | Confirm delivered quantity and condition without creating factory stock. | ![Record ownership diagram: Component purchase line, Supplier response, Factory receipt](https://www.stacksync.com/images/blog-diagrams/icp-prefab-supplier-edi-reconcile-component-orders-with-factory-receipts-and-direct-to-site-deliveries.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Classify the destination at line level Identify whether each purchase line serves factory inventory, a project-specific factory allocation or a direct-site requirement. Keep the receiving owner attached. A single order-header address is insufficient when the supplier fulfills several destinations or project phases. 2. 02 Preserve the approved component identity Map supplier item codes to the actual approved material requirement and units. Keep substitutions visible as proposed changes. A component that appears similar in the supplier catalog still needs the qualified and commercial reviews applicable to the design and purchase. 3. 03 Process acknowledgments as promises Compare supplier acceptance, backorders and changed dates with the original purchase lines. Route differences to procurement and project planning. Do not make factory or site readiness depend on an acknowledgment as though the material were already received. 4. 04 Reconcile separate receiving paths Use shipment notices to prepare the correct receiver. Let factory receiving record factory quantities and the site owner record direct deliveries. Preserve condition holds and partial quantities so one shipment cannot inflate both factory stock and project-delivered totals. 5. 05 Match invoices to the right evidence Provide accounts payable with the purchase line and relevant factory or site receipt references. Keep unresolved receiving gaps explicit under finance's matching policy. Retain EDI transaction and destination identifiers so retransmissions and corrections can be reconciled before another ERP action is created. 6. 06 Keep factory consumption separate from site delivery A component received into the factory may later become part of a module, while a direct-site item is used during installation. Preserve those paths so the same supplier quantity does not appear both as available raw material and as delivered project scope. Production usage and site acceptance each need their own evidence. The purchasing reference connects the story, but it does not replace the distinct inventory and project events along the way. ![6-step operating sequence: Prefab supplier EDI for factory and direct-site receipts](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-prefab-supplier-edi-reconcile-component-orders-with-factory-receipts-and-direct-to-site-deliveries.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Supplier combines factory and site lines in one shipment message Use line and destination references to route each quantity to the correct receiving process. ### Direct delivery is mistakenly received into factory stock Hold the inconsistent result and route a reviewed correction with both source references. ### Component substitution affects released design Request qualified design and procurement approval before applying the changed requirement. ## What to verify before expanding - Factory and direct-site receipts remain separate. - Every quantity resolves to a purchase line and project allocation. - Supplier promises cannot appear as received material. - Duplicate transmission cannot create a second receiving or invoice action. ## 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 component purchase line example and the exception your team handles most often, for example supplier combines factory and site lines in one shipment message. - [EDI for Prefab Component Procurement and Direct-Site Delivery](https://www.stacksync.com/use-case/edi-prefab-component-procurement) - [Modular Building Manufacturers: Align Salesforce Project Configurations With NetSuite Orders and Milestones](https://www.stacksync.com/blog/modular-building-manufacturers-align-salesforce-project-configurations-with-netsuite-orders-and-milestones) - [Module Serial Numbers From Factory to Site: Connect NetSuite With a Supabase Delivery and Acceptance Register](https://www.stacksync.com/blog/module-serial-numbers-from-factory-to-site-connect-netsuite-with-a-supabase-delivery-and-acceptance-register) - [Prefab Dealer and Contractor Portals: Align HubSpot Buyer Records With Supabase Project Access](https://www.stacksync.com/blog/prefab-dealer-and-contractor-portals-align-hubspot-buyer-records-with-supabase-project-access) - [Modernize Legacy EDI Without Replacing Your ERP](https://www.stacksync.com/blog/modernize-legacy-edi-systems) - [Secure EDI Processing in Multi-Cloud Environments](https://www.stacksync.com/blog/secure-edi-processing-in-multi-cloud-environments) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Stacksync NetSuite connector and object support](https://docs.stacksync.com/two-way-sync/connectors/netsuite) - [X12 transaction sets](https://x12.org/products/transaction-sets) FAQ ## Frequently asked questions Does a direct-site delivery need a receiving record? Yes, the operating process still needs evidence of what arrived and its condition. The designated site receiver replaces the factory receiver for that flow. Do factory and direct-site lines belong on the same purchase order? They can, if the trading-partner specification and internal mapping preserve the required line-level destination and allocation detail. Validate that structure with the supplier before launch. What is the strongest prefab EDI pilot? Use an order with factory and direct-site lines, a split shipment and a changed component. Verify that inventory, project visibility and invoice matching all use the correct receiving evidence. 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) - [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 Modular Building Delivery Releases: Coordinate Site Readiness, Transport Booking, and Receiving Acceptance 5 min read read](https://www.stacksync.com/blog/modular-building-delivery-releases-coordinate-site-readiness-transport-booking-and-receiving-acceptance) [App tips Prefab Design Freeze to Factory Release: Route Approved Revisions Through Procurement and Scheduling 5 min read read](https://www.stacksync.com/blog/prefab-design-freeze-to-factory-release-route-approved-revisions-through-procurement-and-scheduling) [App tips Genies for Modular Progress-Billing Reviews: Assemble Factory Milestones, Delivery Proof, and Site Acceptance 5 min read read](https://www.stacksync.com/blog/genies-for-modular-progress-billing-reviews-assemble-factory-milestones-delivery-proof-and-site-acceptance) ## 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/)