--- title: "Zendesk to NetSuite breakage claim workflow for beverages" description: "A Zendesk to NetSuite claim workflow that ties reported bottle breakage to the actual shipment and keeps a credit and a replacement from both being issued." canonical: https://www.stacksync.com/blog/beverage-returns-workflows-route-breakage-claims-from-support-to-finance last_modified: 2026-09-21 --- # Beverage Returns Workflows: Route Breakage Claims From Support to Finance > 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 Support logs the claim in Zendesk, logistics confirms which shipment broke, and finance approves one remedy in NetSuite with the damaged bottles counted, not assumed. Author Ignacio Malpartida · GTM Engineer Published September 21, 2026 Read time 5 min read APP TIPS ## The operating decision Route beverage breakage claims using the original order, shipment, reported damaged quantity, and approved remedy. Support gathers the customer’s account, logistics reviews physical evidence, and finance controls the accepted adjustment. Keep reported breakage separate from confirmed damage and distinguish a credit from a replacement shipment. Explore the complete [beverages integration and automation hub](https://www.stacksync.com/industry/cpg/beverages) for the systems and processes around this guide. ![Summary card: Zendesk to NetSuite breakage claim workflow for beverages](https://www.stacksync.com/images/blog-highlights/icp-beverage-returns-workflows-route-breakage-claims-from-support-to-finance.webp) ## What this looks like in beverages A distributor reports six broken bottles from a case shipment and asks for a full-case credit. The support ticket includes a photo but no receiving reference. The workflow needs to establish which shipment and pack were affected, ask for missing evidence, and route the amount and remedy to the authorized owner. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Breakage claim | Support | Record claimant, order, shipment, reported quantity, unit, and requested remedy. | | Receiving evidence | Logistics | Own the available receipt, damage evidence, and confirmed affected items. | | Remedy approval | Commercial or finance owner | Specify approved bottles or cases, amount, and whether replacement or credit is authorized. | | Completed action | Finance and fulfillment | Link the accepted credit or replacement reference and prevent duplicate compensation. | ![Record ownership diagram: Breakage claim, Receiving evidence, Remedy approval](https://www.stacksync.com/images/blog-diagrams/icp-beverage-returns-workflows-route-breakage-claims-from-support-to-finance.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Identify the affected shipment Match the claim to the actual shipment and receiving location. A distributor may have several deliveries of the same beverage in one week, so product name and date alone are insufficient. 2. 02 Normalize the damage quantity Retain the original reported units and apply the approved pack conversion for comparison. Do not turn a few broken bottles into a full-case credit without the relevant policy decision. 3. 03 Review the remedy Gather the required evidence and route disputed or incomplete claims. Keep replacement and credit alternatives visible so separate teams do not independently authorize both. 4. 04 Confirm completion Read back the accepted financial or fulfillment result and communicate that exact outcome. A requested credit is not a posted credit, and a replacement request is not a shipment. 5. 05 Run a photo-only claim from Zendesk through finance before go-live Open a Zendesk ticket reporting six broken bottles with a photo and no receiving reference. The workflow should ask for the shipment or receipt number and hold the claim as unverified, without attaching the photo to any NetSuite order. Supply the reference, let logistics confirm the damage, and approve a remedy. In NetSuite, the credit memo or replacement order must state six bottles, not one case, and the claim record must show the single remedy chosen. Stop the rollout if the photo was linked to an order by product name, if the remedy shows a case, or if both a credit and a replacement exist for the ticket. ![5-step operating sequence: Zendesk to NetSuite breakage claim workflow for beverages](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-beverage-returns-workflows-route-breakage-claims-from-support-to-finance.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Photo does not identify the shipment Ask for the missing receiving reference before treating it as proof for this order. ### Replacement was already authorized Check existing remedy references before approving an additional credit. ### Claim includes several products Split the evidence by affected item and unit while retaining the parent claim. ## What to verify before expanding - The approved remedy states the exact damaged quantity and unit. - One claim cannot silently produce both a replacement and a full credit. - A photograph without a reliable shipment reference remains unverified evidence rather than confirmed damage for the selected order. - An already authorized replacement is visible before finance reviews any additional credit for the same breakage claim. ## 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 breakage claim example and the exception your team handles most often, for example photo does not identify the shipment. - [Distributor Delivery-Window Automation for Beverage Brands](https://www.stacksync.com/use-case/distributor-delivery-window-automation-for-beverage-brands) - [Beverage Distributor Order Workflows: Check Freight Thresholds and Delivery Windows](https://www.stacksync.com/blog/beverage-distributor-order-workflows-check-freight-thresholds-and-delivery-windows) - [AI Agents for Beverage Brands: Investigate Distributor Delivery Claims](https://www.stacksync.com/blog/ai-agents-for-beverage-brands-investigate-distributor-delivery-claims) - [Broken Cases and Disputed Delivery Windows: Exception Handling for Beverage Claim Agents](https://www.stacksync.com/blog/broken-cases-and-disputed-delivery-windows-exception-handling-for-beverage-claim-agents) - [Investigate Freight Invoice Disputes Across NetSuite and Postgres](https://www.stacksync.com/blog/investigate-freight-invoice-disputes-across-netsuite-and-postgres) - [Reconcile Freight Rates and Dwell Times Before Issuing Credits](https://www.stacksync.com/blog/reconcile-freight-rates-and-dwell-times-before-issuing-credits) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Stacksync Workflows quick start](https://docs.stacksync.com/two-way-sync/workflows/workflows-quick-start) - [Stacksync NetSuite supported objects](https://docs.stacksync.com/two-way-sync/connectors/netsuite) FAQ ## Frequently asked questions Does the workflow decide carrier liability? No. It assembles the claim, the shipment match, and the receiving evidence, then routes them under the policy your business has agreed. Whether the carrier, the warehouse, or the distributor bears the loss is a commercial call for the authorized decision-maker, and any recovery from a carrier runs through that carrier's own claims process outside this workflow. The routed packet gives that person the shipment and quantity facts to start from. What stops the same breakage from being credited twice? Every remedy is written against the claim ID and the shipment line, and the workflow checks NetSuite for an existing credit or replacement on that pair before it presents the approval. A second ticket about the same delivery surfaces the earlier remedy reference to the reviewer instead of opening a fresh path. Finance still sees both tickets; the guard adds visibility, it does not merge or close them. How does the finance reviewer see the claim without opening Zendesk? The approval request arrives by email through Gmail with the claim ID, the matched NetSuite shipment, the confirmed damaged quantity and unit, the photo link, and the requested remedy, so the reviewer decides from one message. The decision is written back to the claim record, and support sees the outcome on the ticket. Nobody needs a Zendesk seat to approve, and nobody edits the ticket from the finance side. 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 Zendesk integrations](https://www.stacksync.com/connectors/zendesk) - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [connector Gmail integrations](https://www.stacksync.com/connectors/gmail) - [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 AI Agents for Beverage Brands: Investigate Distributor Delivery Claims 5 min read read](https://www.stacksync.com/blog/ai-agents-for-beverage-brands-investigate-distributor-delivery-claims) [App tips Broken Cases and Disputed Delivery Windows: Exception Handling for Beverage Claim Agents 5 min read read](https://www.stacksync.com/blog/broken-cases-and-disputed-delivery-windows-exception-handling-for-beverage-claim-agents) [App tips Investigate Freight Invoice Disputes Across NetSuite and Postgres 8 min read read](https://www.stacksync.com/blog/investigate-freight-invoice-disputes-across-netsuite-and-postgres) ## 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/)