--- title: "Solar Equipment Change-Order Workflows | Stacksync" description: "Route equipment substitutions through technical review, customer approval and revised commercial handoffs." canonical: https://www.stacksync.com/use-case/solar-equipment-change-order-workflows last_modified: 2026-09-21 --- Solar installation and O&M services # Solar Equipment Change-Order Workflows > 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 ![Solar installation and O&M services systems connected through Stacksync two-way sync: HubSpot, Acumatica, Salesforce, NetSuite, Supabase](https://www.stacksync.com/images/industry-heroes/icp-solar-installation-service-800.webp) Coordinate proposed solar equipment swaps with the approved project scope. The workflow gathers supplier evidence, routes qualified review, records commercial consequences and prepares the permitted purchasing or billing update. Original requirements stay visible until the accepted revision is applied. Procurement finds an alternative component, but engineering, the customer and finance have not accepted the same revision. [Book a demo](https://www.stacksync.com/book-a-demo) Explore your process in a demo, or get our shared two-way sync architecture guide. When this fits ## Built for this operating problem US commercial solar installers and O&M providers with 100–1,000 employees that combine equipment supply, installation and service. ### Keep the proposed change explicit Link the original item, alternative and affected project scope under one change reference. ### Separate technical and commercial approval Qualified reviewers decide suitability; authorized commercial owners approve price, timing and scope effects. ### Reconcile downstream changes Return verified purchase or billing references and prevent repeated updates from creating duplicate handoffs. The process, end to end ## Follow the work across systems an inverter delivery delay prompts a proposed substitute. The workflow collects the specification and supplier terms, then routes the distinct technical and customer decisions before project records change. [HubSpot connector](https://www.stacksync.com/connectors/hubspot) [Acumatica connector](https://www.stacksync.com/connectors/acumatica) Scope your implementation ## Bring these details to the demo - Approved equipment baseline - Required technical reviewers - Customer change-approval rules - Purchasing and billing action scope Review [current platform pricing](https://www.stacksync.com/pricing) alongside the records, volume, and actions in your process. Use your own operating baseline to evaluate the economics. [Book a demo](https://www.stacksync.com/book-a-demo) Explore your process in a demo, or get our shared two-way sync architecture guide. From foundation to action ## One connected operating process 01 ### [Two-way sync](https://www.stacksync.com/two-way-sync) Keep shared customer, order, and operational records aligned, with clear field ownership. Explore two-way sync 02 ### [Workflows](https://www.stacksync.com/workflow-automation) Move approved work between systems, assign exceptions, and confirm the result. Explore workflows 03 ### [AI agents (Genies)](https://www.stacksync.com/ai-agents) Investigate cross-system questions, assemble the evidence, and prepare the next action. Explore ai agents (genies) 04 ### [EDI](https://www.stacksync.com/edi) Connect trading-partner documents to operational records and exception handling. Explore edi Go deeper ## Implementation guides for your team - [Solar Project Change Orders: Route Equipment Swaps Through Approval and Revised Billing](https://www.stacksync.com/blog/solar-project-change-orders-route-equipment-swaps-through-approval-and-revised-billing) Route solar equipment changes through technical review, customer scope approval and a traceable billing revision. - [Solar Service Visits: Route Confirmed Repair Completion Into O&M Billing](https://www.stacksync.com/blog/solar-service-visits-route-confirmed-repair-completion-into-o-m-billing) Connect solar O&M visit evidence to coverage and billing review without assuming every completed visit is chargeable. [Explore all solar installation and O&M services integration and automation guides ↗](https://www.stacksync.com/industry/construction/solar-installation-service) ## Common evaluation questions ### Can the workflow choose an equivalent component? It supports the qualified review; it does not make the technical suitability decision. ### What if the original equipment already shipped? Keep the shipment history and route disposition or return as a separate decision. ### Can finance review the change manually? Yes. A traceable approved-change packet is a useful first workflow boundary. ### Do we need two-way sync in place before running equipment change-order workflows? Usually, yes. The workflow needs one approved equipment baseline that HubSpot and Acumatica both reference, and two-way sync is what keeps the opportunity, project and accepted scope pointing at the same revision. With that in place, workflows route each proposed swap through qualified review and commercial approval. Genies come after, comparing installed equipment and handover evidence with the accepted substitutions for a project owner to validate. EDI is a later step for distributor acknowledgments and shipment notices on those same purchase lines.