--- title: "Salesforce Acumatica sync for configured assembly orders" description: "How Salesforce quotes reach Acumatica orders with the approved assembly configuration, customer requirements and later option changes kept distinct." canonical: https://www.stacksync.com/blog/electrical-manufacturers-salesforce-acumatica-configured-assemblies last_modified: 2026-09-18 --- # Electrical manufacturers: connect Salesforce assembly quotes to Acumatica orders > 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 Keep the accepted configuration version on the Acumatica order and treat an option changed after approval as a separate decision that sales can see. Author Ruben Burdin · Founder & CEO Published September 18, 2026 Read time 4 min read DATA ENGINEERING ## The operating decision Electrical manufacturers connecting Salesforce and Acumatica should preserve the approved assembly configuration, customer requirements and accepted commercial scope. Two-way sync should link the quote to its ERP order and return operational status while engineering retains authority over configuration changes. A selected catalog family or sales description does not establish every component and option needed for the build. Confirm the actual destination entities and operations before automating configured-order creation. Explore the complete [electrical and electronic components integration and automation hub](https://www.stacksync.com/industry/manufacturing/electrical-electronic-components) for the systems and processes around this guide. ![Summary card: Salesforce Acumatica sync for configured assembly orders](https://www.stacksync.com/images/blog-highlights/icp-electrical-manufacturers-salesforce-acumatica-configured-assemblies.webp) ## What this looks like in electrical and electronic components A manufacturer quotes a control assembly with optional enclosures and customer-specific connection requirements. The customer accepts the quote but changes one option in an email after the technical review. If order entry copies the opportunity’s latest description without its approved configuration version, production can receive a mixture of old engineering scope and new commercial text. A connected handoff keeps the accepted configuration, requested change and final order distinct, allowing the account manager to see what is confirmed and which decision still blocks release. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Approved assembly configuration | Application engineering | Retain the accepted option set and applicable customer requirements with their revision. | | Commercial quote line | Sales operations | Preserve selected quantities, services and terms separately from unaccepted quote alternatives. | | Configuration change request | Engineering and order management | Record later differences without replacing the accepted build automatically. | | ERP order reference | Order management | Return the accepted order and line identity with readiness and unresolved conditions. | ![Record ownership diagram: Approved assembly configuration, Commercial quote line, Configuration change request](https://www.stacksync.com/images/blog-diagrams/icp-electrical-manufacturers-salesforce-acumatica-configured-assemblies.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Identify the governing configuration Decide which engineering record defines the assembly and how the quote references it. Preserve its version and approval evidence. A product-family name can support discovery but should not be treated as the complete build specification. 2. 02 Resolve customer and line relationships Map the buying entity, ship-to and selected quote lines to the approved Acumatica model. Confirm required references and object permissions. Keep options and services distinguishable where their operational treatment differs. 3. 03 Compare the accepted quote with new instructions Show changes in options, quantities and customer requirements separately. Route technical effects to engineering and commercial effects to the authorized owner. Do not combine the price of one quote version with the specification of another silently. 4. 04 Return a meaningful readiness state Expose accepted, pending engineering and other defined states to sales. Preserve the requested delivery date separately from the operational commitment. A won opportunity should not conceal a configuration awaiting review. 5. 05 Demonstrate revision and replay behavior Use a configured quote with an option changed after approval. Apply the reviewed handoff, replay it and inspect the destination references. The demonstration should retain one order and one explicit change process rather than duplicating the assembly or rewriting its scope. ![5-step operating sequence: Salesforce Acumatica sync for configured assembly orders](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-electrical-manufacturers-salesforce-acumatica-configured-assemblies.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### The customer provides a new requirement after acceptance Retain it as a scoped change request and obtain the required technical and commercial decisions. ### Two options appear mutually inconsistent Ask application engineering to resolve the configuration; do not let the integration select one based on position or recency. ### A required component becomes unavailable Route the shortage or substitution separately. Order synchronization should not silently redesign the accepted assembly. ## What to verify before expanding - The ERP order identifies the exact approved assembly configuration. - Unaccepted quote alternatives do not become production demand. - A later technical request remains distinct from accepted scope. - Replay preserves the existing order and its configuration relationship. ## Connect this process to the rest of your operation [Explore Stacksync two-way sync](https://www.stacksync.com/two-way-sync) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real approved assembly configuration example and the exception your team handles most often, for example the customer provides a new requirement after acceptance. - [Salesforce and Acumatica two-way sync for electrical manufacturers](https://www.stacksync.com/use-case/electrical-salesforce-acumatica-two-way-sync) - [NetSuite and Postgres two-way sync for electronic-component operations](https://www.stacksync.com/use-case/electronics-netsuite-postgres-two-way-sync) - [Electronic components: connect NetSuite and Postgres revision-aware stock allocation](https://www.stacksync.com/blog/electronics-netsuite-postgres-component-revision-allocation) - [Electrical components on Shopify: map NetSuite variants, packs and order quantities](https://www.stacksync.com/blog/electrical-components-netsuite-shopify-pack-variant-orders) - [Electronic component substitutions: route evidence to engineering before changing supply](https://www.stacksync.com/blog/electronics-component-substitution-engineering-workflow) - [Acumatica Integrations: The Complete Guide](https://www.stacksync.com/blog/acumatica-integrations-guide) - [Field-Level Change Detection: The Key to Efficient Real-Time Bidirectional CRM Sync](https://www.stacksync.com/blog/field-level-change-detection-the-key-to-efficient-real-time-bidirectional-crm-sync) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Salesforce: change data capture events](https://developer.salesforce.com/docs/platform/platform-events/guide/platform-events-objects-change-data-capture.html) - [Acumatica: endpoints and contracts](https://help-2025r2.acumatica.com/%28W%285%29%29/Wiki/ShowWiki.aspx?PageID=1a9d6f7e-8546-426b-b1ff-d712fbcfbc7b&wikiname=HelpRoot_Dev_Integration) FAQ ## Frequently asked questions Can a sales configuration be released without engineering review? Only where the manufacturer’s approved process explicitly permits it for that configuration. The integration should implement the defined approval boundary. Why retain configuration version on the order? It explains what the customer accepted and what production was authorized to build, even after the catalog or quote changes. Which measure should the pilot track? Measure time to a complete order handoff, configuration clarifications and corrections found after release. Avoid judging success only by the number of records synchronized. About the author Ruben Burdin Founder & CEO Ruben Burdin is the Founder and CEO of Stacksync, the first real-time and two-way sync for enterprise data at scale. Ruben is a Y Combinator alumni with a strong background in software engineering and business. [All posts by Ruben Burdin](https://www.stacksync.com/blog/author/ruben-burdin) 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 - [integration Salesforce and Acumatica integration](https://www.stacksync.com/integrations/acumatica-and-salesforce) - [connector Salesforce integrations](https://www.stacksync.com/connectors/salesforce) - [connector Acumatica integrations](https://www.stacksync.com/connectors/acumatica) - [platform Two-way sync](https://www.stacksync.com/two-way-sync) - [Two-way sync guides Understand two-way sync, record matching, field ownership, and production readiness.](https://www.stacksync.com/blog#topic-two-way-sync) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [Data engineering Building-products manufacturers: connect Salesforce dealer quotes to Acumatica orders 4 min read read](https://www.stacksync.com/blog/building-products-salesforce-acumatica-dealer-quote) [Data engineering Equipment aftermarket: connect Salesforce parts quotes to Acumatica order status 4 min read read](https://www.stacksync.com/blog/equipment-salesforce-acumatica-aftermarket-parts-quotes) [Data engineering Salesforce and Acumatica for manufacturing: turn an approved quote into a traceable order 4 min read read](https://www.stacksync.com/blog/manufacturing-salesforce-acumatica-order-handoff) ## 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/)