--- title: "Supplier EDI shipments to fire equipment POs and serials" description: "Connect supplier equipment shipments to project purchase lines and preserve serial evidence when the supplier transmits it." canonical: https://www.stacksync.com/blog/fire-and-security-equipment-procurement-match-supplier-edi-shipments-to-project-pos-and-serial-records last_modified: 2026-09-18 --- # Fire and Security Equipment Procurement: Match Supplier EDI Shipments to Project POs and Serial Records > 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 Connect supplier equipment shipments to project purchase lines and preserve serial evidence when the supplier transmits it. Author Alexis Favre · Co-Founder & CTO Published September 18, 2026 Read time 4 min read APP TIPS ## The operating decision Fire and security equipment EDI should link supplier documents to the project purchase order and preserve item, quantity, destination and serial or lot evidence where the partner supplies it. Do not assume every shipment message contains serial numbers. Receiving must confirm what arrived, and asset administration must validate the installed-equipment association. EDI can improve the purchasing handoff without certifying device suitability or automatically replacing the approved equipment specification. Explore the complete [fire, life-safety and security integrators integration and automation hub](https://www.stacksync.com/industry/construction/fire-life-safety-security-integrators) for the systems and processes around this guide. ![Summary card: Supplier EDI shipments to fire equipment POs and serials](https://www.stacksync.com/images/blog-highlights/icp-fire-and-security-equipment-procurement-match-supplier-edi-shipments-to-project-pos-and-serial-records.webp) ## What this looks like in fire, life-safety and security integrators An integrator orders panels, readers and accessories for several commercial sites. The distributor ships a mixed carton to a staging warehouse and another shipment directly to a project. Some device serials are in the shipment detail; others are captured at receiving. The design should reconcile the purchase quantities and retain the available serial evidence without inventing missing identifiers or attaching every device to the site named on the order header. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Project purchase line | Procurement | Retain approved item, quantity, unit and project allocation. | | Supplier shipment | Supplier | Provide shipment references and packaging or device identifiers where supported. | | Receiving record | Warehouse or site receiver | Confirm actual quantity, condition and captured device identities. | | Installed-asset association | Asset administrator | Link accepted equipment to the correct site after installation evidence is reviewed. | ![Record ownership diagram: Project purchase line, Supplier shipment, Receiving record](https://www.stacksync.com/images/blog-diagrams/icp-fire-and-security-equipment-procurement-match-supplier-edi-shipments-to-project-pos-and-serial-records.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Confirm the partner's shipment content Review the implementation guide and sample documents to determine whether serials, lots or packaging detail are available. Generic EDI capability does not guarantee those fields. Define the receiving fallback for identifiers that the supplier does not transmit. 2. 02 Preserve purchase-line allocation Carry the buyer PO and line references alongside the supplier item. Keep project and site allocation at the level needed for mixed orders. A shipment to a central warehouse may contain devices for several sites, so a header address cannot determine every final asset location. 3. 03 Route equipment changes for review Compare supplier acknowledgments and shipment items with the approved specification. A replacement model or accessory difference needs the appropriate technical and commercial review. Do not let a successful product-code match or supplier substitution automatically change the installed-system design. 4. 04 Reconcile physical receipt Have the receiving owner confirm quantities, condition and the device identifiers actually observed. Use the shipment notice to prepare that work, not to declare it complete. Keep identifiers supplied electronically distinguishable from those verified at receiving if the operating process requires that distinction. 5. 05 Hand off to asset administration After equipment is accepted and installation evidence exists, route the device-to-site association through the asset process. Preserve the purchase, shipment and receiving references so service teams can trace provenance. Test retransmissions and corrected shipment data to prevent duplicate devices or asset assignments. 6. 06 Keep received and installed inventories distinguishable Equipment accepted into a staging warehouse is not yet installed at a customer's site. Retain its custody location until the authorized installation evidence establishes the site relationship. If devices move between projects before installation, route that allocation change through the inventory and project owners. Service history should begin from a verified installation association, while purchasing provenance remains connected to the original order and receipt throughout those movements. ![6-step operating sequence: Supplier EDI shipments to fire equipment POs and serials](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-fire-and-security-equipment-procurement-match-supplier-edi-shipments-to-project-pos-and-serial-records.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Supplier omits serial numbers Capture them through the approved receiving or installation process; do not generate placeholders that look verified. ### Mixed shipment covers several projects Allocate by purchase line and reviewed receiving detail rather than the header destination alone. ### Supplier sends an alternative model Hold the affected item for qualified specification review before updating the project requirement. ## What to verify before expanding - Missing serial evidence is explicitly marked unresolved. - Each received quantity resolves to the correct purchase line. - Alternative equipment requires the designated review. - A retransmitted shipment cannot create duplicate asset identities. ## 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 project purchase line example and the exception your team handles most often, for example supplier omits serial numbers. - [Fire and Security Integrators: Align Salesforce Installed Equipment With NetSuite Customer and Service Records](https://www.stacksync.com/blog/fire-and-security-integrators-align-salesforce-installed-equipment-with-netsuite-customer-and-service-records) - [Inspection and Monitoring Contracts: Align HubSpot Renewal Status With Acumatica Billing Accounts](https://www.stacksync.com/blog/inspection-and-monitoring-contracts-align-hubspot-renewal-status-with-acumatica-billing-accounts) - [Multi-Site Alarm and Access-Control Service: Connect a Supabase Asset Register With Salesforce](https://www.stacksync.com/blog/multi-site-alarm-and-access-control-service-connect-a-supabase-asset-register-with-salesforce) - [Remove Duplicate HubSpot Contacts Fast with Stacksync](https://www.stacksync.com/blog/remove-duplicate-hubspot-contacts-fast-stacksync) - [Salesforce–NetSuite Integration: Mapping and Setup](https://www.stacksync.com/blog/the-complete-guide-to-salesforce-netsuite-integration-achieving-true-bi-directional-sync) 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 an EDI shipment prove a device was installed? No. Shipment, physical receipt and installation are separate events. Link their evidence without substituting one for another. Can serial numbers be carried in EDI? They may be, depending on the trading partner's message specification and supplied data. Validate the actual content rather than promising universal serial-level coverage. What should a security integrator test first? Test a mixed-project shipment, a direct-site delivery, an item substitution and missing serial detail. These show whether the mapping supports the way equipment actually moves through staging and installation. 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 Fire-System Inspection Follow-Ups: Route Deficiency Records to Approved Remedial Work 5 min read read](https://www.stacksync.com/blog/fire-system-inspection-follow-ups-route-deficiency-records-to-approved-remedial-work) [App tips New Security Installations: Route Customer Acceptance Before Activating Recurring Billing 5 min read read](https://www.stacksync.com/blog/new-security-installations-route-customer-acceptance-before-activating-recurring-billing) [App tips Fire and Security Handoff Exceptions: Missing Device IDs, Conflicting Site Records, and Unapproved Remediation 5 min read read](https://www.stacksync.com/blog/fire-and-security-handoff-exceptions-missing-device-ids-conflicting-site-records-and-unapproved-remediation) ## 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/)