--- title: "Manage Shopify Exchanges Through Zendesk and NetSuite" description: "Manage Shopify Exchanges Through Zendesk and NetSuite. Follow the evidence, approvals, and completion checks with a copyable Genie job description." canonical: https://www.stacksync.com/blog/manage-shopify-exchanges-through-zendesk-and-netsuite last_modified: 2026-09-21 --- # Manage Shopify Exchanges Through Zendesk and NetSuite > 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 Shopify exchange workflow should verify the original purchase, establish policy eligibility, and offer replacements that NetSuite currently shows as available. Author Ignacio Malpartida · GTM Engineer Published September 15, 2026 Updated September 21, 2026 Read time 8 min read APP TIPS ## Make the ticket the home of the exchange A Shopify exchange workflow should verify the original purchase, establish policy eligibility, and offer replacements that NetSuite currently shows as available. Customer selection and merchant approval are separate steps. Neither a request for a different size nor the presence of stock authorizes creation of the return and replacement. Keep the interaction in Zendesk. The ticket should contain the requested item, quantity, reason, original order reference, alternatives, customer choice, and the approval evidence. Use internal notes for staff decisions and the configured customer-facing ticket surface for the conversation. Do not start a separate email exchange that disconnects consent from the case. ![Inspect the request: Match the ticket to the original Shopify order and the exact units requested for exchange.; Offer actual choices: Read NetSuite availability for eligible replacement variants and present the supported sizes or colors in Zendesk.; Create and reconcile: Search for prior results, create only the approved missing records, and read back the resulting IDs.](https://www.stacksync.com/images/blog-highlights/genies-product-exchanges-guide.webp) *Inspect the request: Match the ticket to the original Shopify order and the exact units requested for exchange.; Offer actual choices: Read NetSuite availability for eligible replacement variants and present the supported sizes or colors in Zendesk.; Create and reconcile: Search for prior results, create only the approved missing records, and read back the resulting IDs.* ## Systems and prerequisites This is a workflow design to configure with Stacksync Genies and your existing systems. Connecting an application does not by itself establish the permissions, record mappings, approval routing, or operational process described here. Before enabling the job, confirm which records the Genie can read, which actions it can take, and who receives clarification or approval requests. | System or owner | Evidence and responsibility | | --- | --- | | Zendesk | Exchange request, customer choice, internal approval, and resulting order references. | | Shopify | Original purchase, return and refund history, and approved return/replacement records. | | NetSuite | Replacement variant availability by location. | | Return policy | The merchant’s current eligibility rules and any approved exception. | Required context for this workflow design. ## Assemble an exchange proposal with a clear scope Read the current return policy rather than inserting a generic thirty-day rule. Check the purchase date, item eligibility, relevant condition requirements, and prior return or refund activity for the requested units. A partial refund on another line should not automatically invalidate the whole order; a completed refund for these units needs explicit treatment before a replacement is proposed. Look up the exact replacement variants in NetSuite. A product being in stock does not mean the requested size and color are available. Present only the eligible variants supported by the stock check, with any unresolved shipping or price difference identified for review. Wait for the customer to choose. An available alternative is an option, not implied consent. ## Recheck, approve, create, and reconcile When the customer responds, confirm that the selection is unambiguous and recheck stock. Submit the specific original items, replacement variant, quantities, and any costs for merchant approval. The approval must cover both the return and replacement. If the customer changes their choice afterward, the proposal has changed and requires a fresh decision. Before creating records, search for an existing return or replacement linked to the same ticket and order lines. After creation, read back the resulting IDs and update Zendesk with the confirmed details. A successful return write followed by a replacement failure is a partial result; resume the missing operation after checking its outcome, rather than creating the return again. ## A five-step operating sequence 1. 01 Inspect the request Match the ticket to the original Shopify order and the exact units requested for exchange. Read previous ticket actions as well as order history so a request already handled by another agent does not restart the return process. 2. 02 Apply the policy Compare the request with the merchant’s actual eligibility rules and prior refunds. Document the relevant policy clause and any unresolved exception. Do not substitute a generic return window or assume a refund on another line resolves this item. 3. 03 Offer actual choices Read NetSuite availability for eligible replacement variants and present the supported sizes or colors in Zendesk. Wait for a specific customer choice. Make clear which option they selected before preparing records that would change their order. 4. 04 Obtain approval Recheck the selected variant and prepare the return-and-replacement proposal for merchant approval. Include quantity and cost changes. If the selection changes after approval, obtain a decision on the revised proposal rather than carrying the old approval forward. 5. 05 Create and reconcile Search for prior results, create only the approved missing records, and read back the resulting IDs. Update the original Zendesk ticket with confirmed order details. Keep partial success visible if one record is created while another step fails. ![Manage Shopify Exchanges Through Zendesk and NetSuite — inspect the request, then apply the policy, then offer actual choices, then obtain approval, then create and reconcile.](https://www.stacksync.com/images/blog-diagrams/genies-product-exchanges.webp) *Manage Shopify Exchanges Through Zendesk and NetSuite — inspect the request, then apply the policy, then offer actual choices, then obtain approval, then create and reconcile.* ## Illustrative workflow example A customer requests a medium blue jacket in place of a small blue jacket. Medium blue is unavailable, while medium black is available. The ticket offers medium black, waits for the customer to select it, then obtains merchant approval before creating either record. This example uses fictional records to show the decision logic. It is not a customer case study or a claim of measured results. In a live case, retain the actual record IDs and evidence behind each statement, and replace all illustrative quantities or timing assumptions with the approved operational inputs. ## What the handoff should contain A Zendesk exchange proposal containing original order lines, policy evidence, prior remedies, customer-selected variant, merchant approval, and confirmed return and replacement IDs. Keep the evidence reference, observation time, current owner, and outstanding decision with the case. A colleague taking over should be able to distinguish a proposal from a confirmed result without reading every previous message. If a source value changes while the case is waiting, recheck the affected decision before proceeding. ![Required systems feed case verification; missing evidence or decisions return to clarification before the workflow proceeds.](https://www.stacksync.com/images/blog-diagrams-mermaid/genies-product-exchanges.webp) *Required systems feed case verification; missing evidence or decisions return to clarification before the workflow proceeds.* ## Approval and completion checklist - Evaluate the merchant’s policy and prior refunds at item and quantity level. - Offer verified sizes or colors and wait for customer choice in Zendesk. - Require merchant approval before creating either return or replacement. - Recheck availability and existing records immediately before creation. ## Validate the job before enabling it Start with a small reviewed set of cases from the systems above. Include a complete case, an ambiguous match, a missing source record, and an interrupted action where the result is uncertain. Use a draft or test environment for validation and compare the output with the source records before allowing the configured production actions. For this job, the most important checks are evaluate the merchant’s policy and prior refunds at item and quantity level. Recheck availability and existing records immediately before creation. Record the expected result before the trial, then compare both the proposed action and the final evidence. A fluent message is not a passing result if it skips one of these conditions. - Exchanges created with both choice and approval recorded - Duplicate return or replacement count - Exceptions caused by stock changes after customer selection Use these as operating measures, not promised performance improvements. Establish the current baseline and review exceptions with the team that owns the process. Investigate an increase in incorrect matches, unauthorized actions, or premature closure before expanding the job’s scope. ## Give your Genie a job description Copy the job description below. It preserves the scope and decision boundaries of this use case. Configure the referenced systems, record relationships, policies, and approval owners in your workspace before enabling the job. Product exchanges · Medium Handle product exchange requests from Zendesk. Check the original Shopify order, our return policy, previous refunds, and replacement availability in NetSuite. Offer available sizes or colors and wait for the customer’s choice. Ask me to approve the return and replacement before creating them, then update the ticket with the resulting order details. Operate via Zendesk directly, not with the customer on email or so. Paste this into “Give your Genie a job description.” [Explore Stacksync Genies](https://www.stacksync.com/ai-agents). ## Apply this in personal care: return ticket and purchased configuration Personal-care exchanges add shade, size, and gift-set history to the same Shopify, support, and ERP handoff. Recover the purchased configuration before deciding a partial-set remedy, and keep warehouse disposition separate from support closure and financial completion. | Record to reconcile | Responsible owner | Rule to preserve | | --- | --- | --- | | Return ticket | Support | Retain original order and line, reported issue, requested shade, and proposed remedy. | | Purchased configuration | Order operations | Recover the historical set and component relationship used for the sale. | | Warehouse disposition | Authorized receiving owner | Own the observed item, condition, and approved disposition. | An exception to plan for: **Returned shade differs from the order**. Route the mismatch for review rather than updating the original sale to fit the return. Acceptance check for the pilot: partial-set returns preserve the original component relationship. The [personal care hub](https://www.stacksync.com/industry/cpg/personal-care) connects the broader operating context. These guides develop the specific record mappings and decisions for this application: - [Personal Care Returns Workflows Across Zendesk, NetSuite, and Extensiv](https://www.stacksync.com/blog/personal-care-returns-workflows-across-zendesk-netsuite-and-extensiv) ## Related workflow and integration guides - [Product Exchange Checks: Refunds, Stock, and Customer Choice](https://www.stacksync.com/blog/product-exchange-checks-refunds-stock-and-customer-choice) - [All Genies workflow examples](https://www.stacksync.com/ai-agents#genies-use-cases) - [When a workflow should escalate to a person](https://www.stacksync.com/blog/human-in-the-loop-automation-when-to-escalate) - [Automate Shopify Order Status Replies in Slack](https://www.stacksync.com/blog/automate-shopify-order-status-replies-in-slack) - [Build a Daily Shopify Delivery-Risk Report in Slack](https://www.stacksync.com/blog/build-a-daily-shopify-delivery-risk-report-in-slack) - [E-commerce at Scale: Sync Supabase, Shopify & NetSuite in Real-Time](https://www.stacksync.com/blog/ecommerce-supabase-shopify-netsuite-sync) - [Shopify integrations](https://www.stacksync.com/connectors/shopify) - [Zendesk integrations](https://www.stacksync.com/connectors/zendesk) ## Implementation references These first-party references document the underlying records and interfaces. The cross-system sequence, approvals, and completion rules in this article are a proposed operational configuration; validate them against your connected workspace before enabling it. - [Shopify: returns and exchanges](https://help.shopify.com/en/manual/fulfillment/managing-orders/returns) - [NetSuite: inventory availability and allocation](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_157236254323.html) - [Zendesk: ticket comments and visibility](https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_comments/) FAQ ## Frequently asked questions What does the product exchanges workflow produce? A Zendesk exchange proposal containing original order lines, policy evidence, prior remedies, customer-selected variant, merchant approval, and confirmed return and replacement IDs. What should the team verify before the job can proceed? Evaluate the merchant’s policy and prior refunds at item and quantity level. Offer verified sizes or colors and wait for customer choice in Zendesk. 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 Shopify integrations](https://www.stacksync.com/connectors/shopify) - [connector Zendesk integrations](https://www.stacksync.com/connectors/zendesk) - [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 Product Exchange Checks: Refunds, Stock, and Customer Choice 7 min read read](https://www.stacksync.com/blog/product-exchange-checks-refunds-stock-and-customer-choice) [App tips Personal Care Returns Workflows Across Zendesk, NetSuite, and Extensiv 4 min read read](https://www.stacksync.com/blog/personal-care-returns-workflows-across-zendesk-netsuite-and-extensiv) [Data engineering Shopify–NetSuite Sync for Personal Care Brands: Align Shades, Sizes, and Gift Sets 5 min read read](https://www.stacksync.com/blog/shopify-netsuite-sync-for-personal-care-brands-align-shades-sizes-and-gift-sets) ## 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/)