--- title: "Dimension, finish and unit exceptions in AI dealer orders" description: "A Genie handles conflicting dimensions, finish codes and bundle-to-footage conversions on dealer orders by asking product operations one bounded question." canonical: https://www.stacksync.com/blog/building-products-genie-dimension-finish-uom-exceptions last_modified: 2026-09-18 --- # Building-products AI order exceptions: dimensions, finishes and selling units > 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 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. Author Ignacio Malpartida · GTM Engineer Published September 18, 2026 Read time 4 min read APP TIPS ## The operating decision Building-products AI order exceptions should identify the specific ambiguity that prevents an accurate commercial and operational handoff. Dimensions, finish codes, unit conversions and delivery-stage references can each change what the manufacturer must supply. A Genie should compare approved records and preserve the conflicting source values, then ask the responsible owner a bounded question. Similar product descriptions and apparently reasonable dimensions are not sufficient evidence to accept an order line. Explore the complete [building products manufacturing integration and automation hub](https://www.stacksync.com/industry/manufacturing/building-products) for the systems and processes around this guide. ![Summary card: Dimension, finish and unit exceptions in AI dealer orders](https://www.stacksync.com/images/blog-highlights/icp-building-products-genie-dimension-finish-uom-exceptions.webp) ## What this looks like in building products manufacturing A dealer order asks for twenty bundles of a profile, but its attached schedule lists linear footage and a handwritten finish abbreviation. The prior quote used a different length. An agent can extract all those values correctly while still producing an inconsistent order. The exception process should show the alternative interpretations and what each would mean for product selection and quantity. Product operations or customer service then resolves the intended variant and selling unit before the draft can become accepted manufacturing demand. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Dimension conflict | Product operations | Preserve requested dimensions and the applicable catalog or custom-product reference without rounding by assumption. | | Finish ambiguity | Product operations | Keep the dealer abbreviation and candidate approved finishes separate until the match is confirmed. | | Quantity conversion | Order management | Retain source quantity, selling unit and proposed base quantity with the rule used. | | Stage assignment | Customer service | Identify which products and quantities belong to each requested destination or project phase. | ![Record ownership diagram: Dimension conflict, Finish ambiguity, Quantity conversion](https://www.stacksync.com/images/blog-diagrams/icp-building-products-genie-dimension-finish-uom-exceptions.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Classify the error by its consequence Distinguish a missing field from a conflicting product choice or an unknown conversion. State which order lines cannot proceed and why. A generic low-confidence label leaves the reviewer to reconstruct the entire problem. 2. 02 Compare the current request and accepted quote Show changes in dimension, finish and quantity independently. Preserve which document supplies each value. Do not select price from one revision and product specification from another without the commercial owner accepting that combined scope. 3. 03 Ask the narrowest useful clarification Prepare a question that resolves the product or unit decision, supported by the relevant source excerpts. Follow the approved customer communication path. Avoid presenting an unapproved candidate as if the dealer already selected it. 4. 04 Apply the resolution to the correct scope Update the current draft and retain the reviewer’s decision. If the answer should become a reusable dealer cross-reference, route that master-data change separately. A one-project abbreviation should not automatically change how every dealer order is interpreted. 5. 05 Recheck the complete line After a dimension or finish is resolved, recompute the affected quantity under the approved rule and revisit price or delivery implications. A product correction may invalidate the prior quote comparison even if the original exception is now cleared. ![5-step operating sequence: Dimension, finish and unit exceptions in AI dealer orders](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-building-products-genie-dimension-finish-uom-exceptions.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### The requested dimension is outside the reviewed catalog Route the line to the custom-product or engineering process; do not round to a nearby standard size. ### The finish code matches two product families Ask for the governing product reference or approved cross-reference rather than choosing the more common result. ### The converted quantity produces an unexpected fraction Show the calculation and ask the product owner for the applicable selling and rounding rule. ## What to verify before expanding - The exception shows the source values that disagree and the lines they affect. - The approved product correction triggers review of dependent quantity and commercial fields. - A one-time dealer clarification stays scoped to the relevant case. - No unresolved dimension or finish is silently replaced with a plausible default. ## Connect this process to the rest of your operation [Explore Stacksync AI agents (Genies)](https://www.stacksync.com/ai-agents#genies-job-icp-building-products) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real dimension conflict example and the exception your team handles most often, for example the requested dimension is outside the reviewed catalog. - [AI dealer-order intake for building-products manufacturers](https://www.stacksync.com/use-case/building-products-ai-dealer-order-intake) - [AI agents for building-products dealer orders: prepare product and delivery drafts](https://www.stacksync.com/blog/building-products-genie-dealer-order-intake) - [Building-products retailer EDI: validate packaging and order revisions before acceptance](https://www.stacksync.com/blog/building-products-edi-retailer-order-packaging-revisions) - [Building-products manufacturers: connect Salesforce dealer quotes to Acumatica orders](https://www.stacksync.com/blog/building-products-salesforce-acumatica-dealer-quote) - [Build a Daily Shopify Delivery-Risk Report in Slack](https://www.stacksync.com/blog/build-a-daily-shopify-delivery-risk-report-in-slack) - [NetSuite NSIP Alternatives: A Real-Time Sync Guide](https://www.stacksync.com/blog/netsuite-nsip-alternatives-real-time-sync-guide) 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) - [Oracle NetSuite: using external IDs](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_156334828635.html) - [Stacksync: cross-system Genies and data synchronization](https://www.stacksync.com/) FAQ ## Frequently asked questions Should the agent use the previous order as the default? A prior order is useful context, but the current request may intentionally differ. Show the comparison and obtain the required approval for any assumption. Can unit conversions be automated later? Yes, after the product owner approves their item, customer and effective scope. Preserve the original unit so reviewers can audit the result. Which exception categories should be monitored? Track dimensions, finishes, units and stage assignments separately. Repeated ambiguity in one category may call for a better dealer template or reviewed cross-reference, not a more aggressive model. 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 Salesforce integrations](https://www.stacksync.com/connectors/salesforce) - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [platform AI agent operations](https://www.stacksync.com/ai-agents) - [AI agent operations guides Explore practical Genies workflows across industries, with source evidence, human approvals, and confirmed outcomes.](https://www.stacksync.com/blog#topic-ai-agent-operations) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [App tips AI agents for building-products dealer orders: prepare product and delivery drafts 4 min read read](https://www.stacksync.com/blog/building-products-genie-dealer-order-intake) [App tips Building-products damage claims: connect shipment evidence, replacements and credit review 4 min read read](https://www.stacksync.com/blog/building-products-damage-shortage-claim-workflow) [App tips Building-products staged deliveries: coordinate project releases without losing the original order 4 min read read](https://www.stacksync.com/blog/building-products-staged-jobsite-delivery-workflow) ## 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/)