--- title: "AI dealer-order intake for building-products manufacturers" description: "Use a Genie to turn dealer emails and order forms into reviewable product and delivery drafts." canonical: https://www.stacksync.com/use-case/building-products-ai-dealer-order-intake last_modified: 2026-09-21 --- Building products manufacturing # AI dealer-order intake 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) Use a Genie to turn dealer emails and order forms into reviewable product and delivery drafts. Stacksync fits manufacturers where customer service spends time comparing requests with quotes, catalog variants and ERP records. The Genie should preserve source evidence and expose changed finishes, unclear units and incomplete delivery stages before acceptance. Dealer shorthand, marked-up attachments and revised quotes make every order depend on an employee reconstructing the intended product and quantity. [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. ### Prepare the complete request Collect customer PO, project, product candidates and requested delivery stages with their original evidence. ### Expose the consequential differences Compare against the accepted quote and highlight product, quantity or delivery changes for the right reviewer. ### Keep acceptance controlled Missing dimensions and unreviewed conversions remain exceptions, with execution limited to the approved destination process. The process, end to end ## Follow the work across systems a channel operations team wants to process repeat dealer formats while retaining review for custom dimensions and quote changes. Evaluate an order with a changed finish and ambiguous bundle quantity; the useful result is a focused approval packet, not an unsupported completed transaction. [Salesforce connector](https://www.stacksync.com/connectors/salesforce) [NetSuite connector](https://www.stacksync.com/connectors/netsuite) Scope your implementation ## Bring these details to the demo - Representative dealer documents and accepted quotes. - Reviewed product variants and selling-unit conversions. - A customer-service reviewer and product escalation owner. 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 - [AI agents for building-products dealer orders: prepare product and delivery drafts](https://www.stacksync.com/blog/building-products-genie-dealer-order-intake) What a dealer-order Genie should hand customer service: matched variants, side-by-side units, quote differences and delivery-stage questions, with commitments left to their owners. - [Building-products AI order exceptions: dimensions, finishes and selling units](https://www.stacksync.com/blog/building-products-genie-dimension-finish-uom-exceptions) Twenty bundles, a schedule in linear feet and a handwritten finish code: how an AI agent should surface each reading of a dealer order line instead of picking one. [Explore all building products manufacturing integration and automation guides ↗](https://www.stacksync.com/industry/manufacturing/building-products) ## Common evaluation questions ### Can it turn a takeoff into a purchase order? Only if the business explicitly establishes purchase authorization and the required review. A planning document should not become demand merely because it can be read. ### What should count as a completed outcome? A review-ready draft and an accepted ERP order are separate outcomes. Track both and preserve unresolved lines. ### How should a pilot be evaluated? Measure preparation and clarification effort, reviewer corrections and order-entry rework, including the human review required by the workflow. ### Should a Genie be the first Stacksync product for dealer-order intake? Usually not alone. Start with two-way sync so accepted quotes and product variants agree between Salesforce and NetSuite before any draft is built. Add workflows to route each intake draft to a customer-service reviewer and product operations, and to apply an approved order through a confirmed operation. Then the Genie earns its place: it reads dealer emails and marked-up forms, matches finishes and selling units against the quote, and flags missing dimensions for a reviewer. EDI comes last, when retailer purchase orders arrive as documents rather than emails.