--- title: "Building-products damage and shortage claim workflow" description: "Link damage and shortage claims to shipment evidence and quantities in Salesforce and NetSuite, and keep replacement approval apart from the credit call." canonical: https://www.stacksync.com/blog/building-products-damage-shortage-claim-workflow last_modified: 2026-09-18 --- # Building-products damage claims: connect shipment evidence, replacements and credit review > 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 A claim workflow for staged loads that matches dealer photographs to the right shipment, catches duplicate reports, and routes replacement and credit decisions to their owners. Author Ignacio Malpartida · GTM Engineer Published September 18, 2026 Read time 4 min read APP TIPS ## The operating decision A building-products damage or shortage workflow should connect the claim to the actual shipment, affected product and quantity, then separate replacement and financial decisions. Automate evidence collection and routing while customer service, logistics and finance retain their approval roles. A photograph supports investigation but does not by itself establish the full affected quantity or authorize a credit. Keep the customer’s requested remedy distinct from the remedy the manufacturer accepts. 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: Building-products damage and shortage claim workflow](https://www.stacksync.com/images/blog-highlights/icp-building-products-damage-shortage-claim-workflow.webp) ## What this looks like in building products manufacturing A manufacturer ships several finishes to a jobsite in staged loads. The dealer reports damaged cartons and a shortage using photographs from two deliveries. Customer service wants to replace the affected goods quickly, but the original shipment references and quantities are unclear. A connected claim packet can align the reported items with shipment and receipt evidence, identify possible duplicate claims, and present a supported proposal. The team can then approve a replacement, investigate a short shipment or decide financial treatment without issuing inconsistent remedies through different channels. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Claim request | Customer service | Retain the reported product, quantity, shipment references and requested remedy with the original evidence. | | Shipment and receipt | Logistics | Preserve dispatched quantities and available delivery evidence at the applicable line or load grain. | | Accepted remedy | Customer service and operations | Record the approved replacement or other operational resolution separately from the initial request. | | Financial disposition | Finance | Keep the approved credit, charge or denial linked to the claim without inferring it from a replacement shipment. | ![Record ownership diagram: Claim request, Shipment and receipt, Accepted remedy](https://www.stacksync.com/images/blog-diagrams/icp-building-products-damage-shortage-claim-workflow.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Resolve which delivery the claim concerns Match the customer’s references to the correct order and shipment. Separate evidence from multiple loads instead of combining it into one unexplained quantity. Ask for missing details when the photographs do not establish the applicable product or delivery. 2. 02 Reconcile the reported quantities Compare ordered, shipped, received and claimed quantities under the reviewed unit conversion. Distinguish damage from shortage because their evidence and remedies can differ. Keep uncertain quantities visible rather than automatically using the customer’s total as accepted liability. 3. 03 Check existing remedies and claims Search for earlier cases, replacement orders and credits related to the same shipment and affected goods. Link follow-up messages to the existing case. A dealer calling a second employee should not create an independent entitlement. 4. 04 Route a complete proposed resolution Present the evidence and requested action to the appropriate owners. Operations confirms replacement availability and finance approves financial treatment. A replacement may be an urgent commercial decision while the investigation continues; record that scope explicitly. 5. 05 Close the case by obligation Track the accepted replacement, return requirement and financial disposition separately. Reconcile the quantities resolved by each action so the same damage is not credited and replaced beyond the approved remedy. Keep unresolved balances assigned. ![5-step operating sequence: Building-products damage and shortage claim workflow](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-building-products-damage-shortage-claim-workflow.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Photographs show mixed finishes Ask the customer or reviewer to identify the affected variants before preparing replacement lines. ### The dealer reports the same damage twice Retain both communications on one claim and review any new evidence without duplicating the remedy. ### Replacement stock is unavailable Return an approved alternative plan to customer service. Do not substitute another finish or promise an unsupported delivery date. ## What to verify before expanding - The accepted claim quantity traces to identified products and shipment evidence. - Duplicate reports cannot create duplicate replacement or credit actions. - Operational and financial remedies have separately recorded approvals. - The final case reconciles accepted damage or shortage with the remedies actually completed. ## 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 claim request example and the exception your team handles most often, for example photographs show mixed finishes. - [Staged-delivery automation for building-products manufacturers](https://www.stacksync.com/use-case/building-products-staged-delivery-automation) - [Building-products staged deliveries: coordinate project releases without losing the original order](https://www.stacksync.com/blog/building-products-staged-jobsite-delivery-workflow) - [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 AI order exceptions: dimensions, finishes and selling units](https://www.stacksync.com/blog/building-products-genie-dimension-finish-uom-exceptions) - [Fast Shopify API Integration via Bi‑Directional Sync](https://www.stacksync.com/blog/fast-shopify-api-integration-via-bidirectional-sync) - [EDI Integration for Ecommerce: Scale Without Chargebacks](https://www.stacksync.com/blog/edi-integration-ecommerce-brands) 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) FAQ ## Frequently asked questions Can a Genie approve the claim from photos? It can organize images and related records, but acceptance criteria and commercial decisions belong to the designated owners. Ambiguous evidence should produce a focused review question. Should a replacement automatically trigger a credit? No. Follow the approved remedy. Replacements, returns and credits are distinct actions whose combination must be intentional. What tells you damage-claim handling has improved? Track evidence-gathering time, duplicate remedy attempts and claims reopened for wrong quantities or products. Faster case creation alone does not show better resolution. 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 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) [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) [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 AI order exceptions: dimensions, finishes and selling units 4 min read read](https://www.stacksync.com/blog/building-products-genie-dimension-finish-uom-exceptions) ## 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/)