--- title: "Salesforce and Acumatica two-way sync for…" description: "Connect dealer quotes to accepted ERP orders while preserving project, product variant and staged-delivery context." canonical: https://www.stacksync.com/use-case/building-products-salesforce-acumatica-two-way-sync last_modified: 2026-09-21 --- Building products manufacturing # Salesforce and Acumatica two-way sync for building-products manufacturers > 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 ![Building products manufacturing systems connected through Stacksync two-way sync: Salesforce, Acumatica, NetSuite, Shopify, Dynamics 365 F&O, SQL Server](https://www.stacksync.com/images/industry-heroes/icp-building-products-800.webp) Connect dealer quotes to accepted ERP orders while preserving project, product variant and staged-delivery context. Stacksync fits building-products manufacturers whose channel teams repeatedly reconcile Salesforce opportunities with Acumatica order records. Keep requested scope separate from approved manufacturing and logistics commitments. The dealer’s accepted quote includes finishes and delivery stages that disappear when the order is reduced to one opportunity total and ship-to field. [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 Operations, channel sales and IT leaders at US building-products manufacturers with 100–1,000 employees. ### Preserve product and project meaning Keep the dealer, project, variant and selling unit distinct where the business process needs them. ### Make staged commitments visible Return line and delivery-stage status instead of suggesting the entire project shares one readiness state. ### Control revised scope Route changed finishes or destinations to the appropriate owner and validate the exact order operations during scoping. The process, end to end ## Follow the work across systems a manufacturer serves dealers ordering several finishes for phased projects. Evaluate a partially accepted quote with one changed finish and two delivery destinations, then inspect what operations accepted and what sales can safely communicate. [Salesforce connector](https://www.stacksync.com/connectors/salesforce) [Acumatica connector](https://www.stacksync.com/connectors/acumatica) [Review the integration details ↗](https://www.stacksync.com/integrations/acumatica-and-salesforce) Scope your implementation ## Bring these details to the demo - A dealer quote with multiple variants and delivery stages. - Approved customer, product and ship-to cross-references. - Owners for product changes and accepted delivery promises. 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 - [Building-products manufacturers: connect Salesforce dealer quotes to Acumatica orders](https://www.stacksync.com/blog/building-products-salesforce-acumatica-dealer-quote) How a building-products manufacturer carries accepted dealer quote lines from Salesforce into Acumatica orders and shows sales which delivery stages operations confirmed. - [Building products on Shopify: sync NetSuite bundles, pieces and saleable stock](https://www.stacksync.com/blog/building-products-netsuite-shopify-bundle-unit-sync) A NetSuite and Shopify setup for trim and other building products where the store sells bundles, the ERP counts lengths, and unfinished stock must stay off the storefront. - [Building-products manufacturing: build a Dynamics-to-SQL Server ready-to-ship view](https://www.stacksync.com/blog/building-products-dynamics-sql-server-ready-to-ship) Why a single completed flag misleads shipping, and how a Dynamics-fed SQL Server view separates production, quality release, packaging and delivery approval per release. [Explore all building products manufacturing integration and automation guides ↗](https://www.stacksync.com/industry/manufacturing/building-products) ## Common evaluation questions ### Does the project need its own ERP customer? Not necessarily. The dealer may be the sold-to customer while the project supplies delivery context. Model the actual relationship first. ### What should be demonstrated? Partial quote acceptance, a product change and a stage-specific destination update that leaves other commitments intact. ### How should the buyer assess value? Track order-preparation effort, status-checking touches and corrections caused by lost variant or delivery detail. ### Which Stacksync product comes first for Salesforce and Acumatica dealer quotes? Start with two-way sync. It carries the accepted dealer quote from Salesforce into an Acumatica order with variant, selling unit and delivery stage intact, and returns line status to the account manager. Add workflows when a changed finish or stage destination needs review by product operations or logistics before the order changes. Bring in Genies when dealer emails and marked-up forms need comparing with the quote before anyone keys an order. EDI comes last, when retailer purchase orders and revisions must carry the same variant and packaging meaning.