--- title: "Solar equipment swap approval and billing revision workflow" description: "Route solar equipment changes through technical review, customer scope approval and a traceable billing revision." canonical: https://www.stacksync.com/blog/solar-project-change-orders-route-equipment-swaps-through-approval-and-revised-billing last_modified: 2026-09-18 --- # Solar Project Change Orders: Route Equipment Swaps Through Approval and Revised Billing > 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 Route solar equipment changes through technical review, customer scope approval and a traceable billing revision. Author Ignacio Malpartida · GTM Engineer Published September 18, 2026 Read time 5 min read APP TIPS ## The operating decision A solar equipment-change workflow should connect the proposed substitution to technical review, revised commercial scope, customer authorization and the resulting purchasing or billing handoff. Keep each decision separate. A supplier offering another model does not establish technical suitability or customer approval. Preserve the original equipment requirement and approved revision so project, procurement and finance teams can see exactly what changed before they act. 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 equipment swap approval and billing revision workflow](https://www.stacksync.com/images/blog-highlights/icp-solar-project-change-orders-route-equipment-swaps-through-approval-and-revised-billing.webp) ## What this looks like in solar installation and O&M services A commercial installer learns that an ordered inverter will arrive later than planned. Procurement identifies an alternative, the technical team needs to review it, and the customer may need a revised proposal. Finance cannot simply replace the item description on the existing billable scope. A workflow can route the evidence and record the approved decision, then prepare the permitted purchasing and commercial updates under the same change reference. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Proposed equipment swap | Procurement or project manager | Identify original requirement, alternative and reason for the change. | | Technical review | Qualified technical owner | Record the accepted specification decision and any conditions. | | Commercial revision | Account and project owners | Capture price, schedule and scope effects for customer review. | | Approved change handoff | Finance and procurement | Apply only the permitted actions for the accepted revision. | ![Record ownership diagram: Proposed equipment swap, Technical review, Commercial revision](https://www.stacksync.com/images/blog-diagrams/icp-solar-project-change-orders-route-equipment-swaps-through-approval-and-revised-billing.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Start a distinct change record Create a reference connecting the original item and proposed replacement. Include the affected project, quantity, supplier evidence and reason. Do not overwrite the original equipment requirement while the proposal is under review, because other teams may still be working from the accepted baseline. 2. 02 Route technical evaluation Provide the qualified reviewer with the required specification and proposed alternative evidence. The workflow can assemble the documents and track the decision; it should not decide compatibility or compliance. Record any conditions that must travel with the accepted substitution. 3. 03 Calculate commercial consequences Have the responsible team identify changes to price, timing, quantities and other contractual commitments. Keep supplier cost changes separate from the customer-facing commercial decision. A lower supplier price does not automatically determine the revised customer charge. 4. 04 Collect approval for the actual revision Tie customer and internal approvals to the final scope version. If the proposed equipment or price changes after review, reopen the affected approval. Preserve partial decisions where only some equipment or project phases are accepted. 5. 05 Apply and reconcile downstream updates Route purchasing changes and billing revisions through verified actions and authorized owners. Store the resulting order or billing references under the change record. Confirm that the old requirement is superseded only after the accepted revision is applied, and prevent repeated triggers from creating duplicate requests. 6. 06 Preserve the decision when the swap is rejected A rejected alternative remains useful project history. Record the reason, reviewer and affected equipment requirement without replacing the active specification. Procurement can then investigate another option without repeating the same technical question. Sales should see the resulting commercial or timing issue, but the rejection itself should not automatically create a customer price change. Keep the next proposed alternative as a separate version so its approvals cannot accidentally inherit the rejected proposal's context. ![6-step operating sequence: Solar equipment swap approval and billing revision workflow](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-solar-project-change-orders-route-equipment-swaps-through-approval-and-revised-billing.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Technical approval includes conditions Keep those conditions attached to the handoff and verify the responsible team accepts them. ### Customer approves timing but not price Leave the commercial revision unresolved until the required scope and price decision exists. ### Original equipment already shipped Route the return or disposition decision separately instead of pretending the order was never placed. ## What to verify before expanding - Original and proposed equipment remain distinguishable. - Qualified review precedes the accepted specification change. - Approvals identify the exact commercial revision. - Purchasing and billing updates retain the same change reference. ## Connect this process to the rest of your operation [Explore Stacksync workflows](https://www.stacksync.com/workflow-automation) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real proposed equipment swap example and the exception your team handles most often, for example technical approval includes conditions. - [Solar Equipment Change-Order Workflows](https://www.stacksync.com/use-case/solar-equipment-change-order-workflows) - [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) - [Genies for Solar Project Closeout: Assemble Serial Numbers, Completion Evidence, and Handover Records](https://www.stacksync.com/blog/genies-for-solar-project-closeout-assemble-serial-numbers-completion-evidence-and-handover-records) - [Solar Closeout Exceptions: Missing Serial Numbers, Changed Equipment, and Incomplete Handover Evidence](https://www.stacksync.com/blog/solar-closeout-exceptions-missing-serial-numbers-changed-equipment-and-incomplete-handover-evidence) - [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 HubSpot connector and object support](https://docs.stacksync.com/two-way-sync/connectors/hubspot) - [Acumatica construction management](https://www.acumatica.com/cloud-erp-software/construction-management/) - [Stacksync event triggers](https://docs.stacksync.com/guides/event-triggers) FAQ ## Frequently asked questions Can AI choose an equivalent solar component? This workflow does not delegate that technical judgment. It organizes evidence for the qualified reviewer and routes the resulting approved decision. Does supplier acceptance authorize customer billing changes? No. Supplier and customer agreements are separate. Record the customer's approved scope and price treatment before a revised billing handoff. Which equipment swaps belong in a change-order pilot? Use a substitution with a price change, one with no customer charge change, and one rejected alternative. Verify that each follows the correct approvals and preserves the original scope. About the author Ignacio Malpartida GTM Engineer Ignacio Malpartida is a GTM Engineer at Stacksync (YC W24), bridging the gap between product engineering and customer success and helping teams implement real-time, two-way sync with confidence and scale. [All posts by Ignacio Malpartida](https://www.stacksync.com/blog/author/ignacio-malpartida) 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 HubSpot integrations](https://www.stacksync.com/connectors/hubspot) - [connector Acumatica integrations](https://www.stacksync.com/connectors/acumatica) - [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) [Data engineering Solar Installer Customer Handoffs: Align HubSpot Opportunities With Acumatica Project Accounts 5 min read read](https://www.stacksync.com/blog/solar-installer-customer-handoffs-align-hubspot-opportunities-with-acumatica-project-accounts) [App tips Distinguish Solar End Customers from Installation Partners 7 min read read](https://www.stacksync.com/blog/distinguish-solar-end-customers-from-installation-partners) [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/)