--- title: "Solar supplier EDI for partial panel and inverter deliveries" description: "Connect solar supplier documents to project equipment requirements and distinguish shipment, receipt and installation states." canonical: https://www.stacksync.com/blog/solar-equipment-supplier-edi-reconcile-panels-inverters-and-partial-project-deliveries last_modified: 2026-09-18 --- # Solar Equipment Supplier EDI: Reconcile Panels, Inverters, and Partial Project 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 Connect solar supplier documents to project equipment requirements and distinguish shipment, receipt and installation states. Author Alexis Favre · Co-Founder & CTO Published September 18, 2026 Read time 5 min read APP TIPS ## The operating decision Solar equipment EDI should preserve purchase lines, item references, quantities, destinations and the supplier's accepted delivery plan. Panels, inverters and dependent components may arrive in separate shipments, so keep line-level state rather than one delivered flag for the project. Use the trading partner's implementation guide for document and identifier mapping. Procurement reviews substitutions, receiving confirms actual quantities and condition, and project teams decide whether the complete installation requirement is ready. Explore the complete [solar installation and O&M services integration and automation hub](https://www.stacksync.com/industry/construction/solar-installation-service) for the systems and processes around this guide. ![Summary card: Solar supplier EDI for partial panel and inverter deliveries](https://www.stacksync.com/images/blog-highlights/icp-solar-equipment-supplier-edi-reconcile-panels-inverters-and-partial-project-deliveries.webp) ## What this looks like in solar installation and O&M services An installer orders equipment for several commercial rooftops from one distributor. Panels arrive at a staging warehouse, inverters ship directly to one project, and a required accessory remains backordered. The supplier sends separate acknowledgments and shipment notices. The EDI flow needs to retain which purchase lines serve each site and distinguish received material from a promised or dispatched quantity. Otherwise the project coordinator could release a crew while one essential line is still unresolved. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Project equipment requirement | Project and technical owners | Maintain the approved items and quantities for the accepted scope. | | Purchase line | Procurement | Link supplier item and ordered quantity to the project allocation. | | Shipment and destination | Supplier and logistics | Preserve each shipment reference and intended receiving location. | | Accepted receipt | Warehouse or site receiver | Confirm usable quantities and condition independently of the shipment notice. | ![Record ownership diagram: Project equipment requirement, Purchase line, Shipment and destination](https://www.stacksync.com/images/blog-diagrams/icp-solar-equipment-supplier-edi-reconcile-panels-inverters-and-partial-project-deliveries.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Map the approved equipment list Connect the project requirement to the buyer's purchase lines and supplier catalog identifiers. Preserve units and any required equipment grouping. A shipment item should resolve to the actual approved component, not merely a similar description in the distributor's catalog. 2. 02 Confirm partner document rules Review the supplier's supported messages, versions, identifiers and change-handling rules. Agree how backorders, substitutions and partial shipments are represented. A valid EDI document can still be commercially ambiguous if the contractor and supplier interpret a changed quantity differently. 3. 03 Route substitutions and timing changes Compare acknowledgments with the original order and flag deviations. Technical review is required for equipment suitability, while procurement and project management handle commercial and schedule consequences. The EDI response should provide evidence for those decisions rather than silently modifying the accepted project scope. 4. 04 Track warehouse and direct-site receipts Allow several shipments and receiving locations against a purchase line. Keep supplier-dispatched quantities separate from physically accepted material. Where device identifiers are supplied, retain them, but do not claim universal serial coverage or mark equipment installed based on shipping data. 5. 05 Reconcile the complete requirement Publish verified line states to the planning and finance views through supported operations. Installation coordination needs to know which required components remain missing; accounts payable needs the purchase and receipt references. Retain processing identifiers so retransmissions and corrected documents can be handled without duplicate actions. 6. 06 Keep received quantity out of installed-asset totals A project can receive replacement or spare equipment that is not installed immediately. Preserve the distinction between supplied, accepted into custody and installed quantities. EDI and receiving records can support the first two states, while installation evidence establishes the third. This avoids an inflated asset register and gives closeout reviewers a way to explain why purchase quantities differ from the equipment actually included in the customer handover. ![6-step operating sequence: Solar supplier EDI for partial panel and inverter deliveries](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-solar-equipment-supplier-edi-reconcile-panels-inverters-and-partial-project-deliveries.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Panels arrive before an essential accessory Keep the equipment requirement incomplete and identify the blocking line. ### Inverter ships to a project instead of the warehouse Assign the correct receiver and avoid adding the quantity to warehouse stock. ### Supplier changes the proposed model Hold the specification change for qualified review and commercial approval. ## What to verify before expanding - Partial deliveries remain visible at purchase-line level. - Direct-site quantities reconcile to the intended project. - Supplier substitution cannot overwrite approved equipment scope. - A technical acknowledgment cannot stand in for physical receipt. ## 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 equipment requirement example and the exception your team handles most often, for example panels arrive before an essential accessory. - [Solar Installer Customer Handoffs: Align HubSpot Opportunities With Acumatica Project Accounts](https://www.stacksync.com/blog/solar-installer-customer-handoffs-align-hubspot-opportunities-with-acumatica-project-accounts) - [Solar Fleet Ownership Changes: Align Salesforce Asset Owners With NetSuite Billing Customers](https://www.stacksync.com/blog/solar-fleet-ownership-changes-align-salesforce-asset-owners-with-netsuite-billing-customers) - [Solar Customer Portals: Connect HubSpot Milestones With Supabase Customer Access](https://www.stacksync.com/blog/solar-customer-portals-connect-hubspot-milestones-with-supabase-customer-access) - [Check Solar Installation Readiness Across Salesforce and NetSuite](https://www.stacksync.com/blog/check-solar-installation-readiness-across-salesforce-and-netsuite) - [Identify Equipment Allocation, Permit, and Crew Blockers](https://www.stacksync.com/blog/identify-equipment-allocation-permit-and-crew-blockers) 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 EDI confirm that a project is ready for installation? It supplies purchasing and logistics evidence. Readiness also requires the complete approved equipment requirement and the other site and crew decisions. Can panel and inverter serials be included? They may be available in partner messages or later receiving records. Validate the actual supplier specification and keep missing identifiers explicit rather than promising universal detail. What should the pilot include? Test multiple projects on one order, a direct-site shipment, a backorder and a corrected message. Verify that each event updates the right line without creating false project completeness. 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 Solar Service Visits: Route Confirmed Repair Completion Into O&M Billing 5 min read read](https://www.stacksync.com/blog/solar-service-visits-route-confirmed-repair-completion-into-o-m-billing) [App tips Check Solar Installation Readiness Across Salesforce and NetSuite 8 min read read](https://www.stacksync.com/blog/check-solar-installation-readiness-across-salesforce-and-netsuite) [App tips Genies for Solar Project Closeout: Assemble Serial Numbers, Completion Evidence, and Handover Records 5 min read read](https://www.stacksync.com/blog/genies-for-solar-project-closeout-assemble-serial-numbers-completion-evidence-and-handover-records) ## 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/)