--- title: "Equipment RMA workflow for replacement, return and credit" description: "A warranty RMA workflow across Salesforce and NetSuite that keeps approved remedy, replacement shipment and returned-unit disposition as linked records." canonical: https://www.stacksync.com/blog/equipment-warranty-rma-replacement-return-workflow last_modified: 2026-09-18 --- # Equipment warranty RMAs: coordinate replacement, return and credit decisions > 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 Shipping a replacement should not close the return or decide the credit; each RMA obligation stays open until the owner who holds it confirms the outcome. Author Ignacio Malpartida · GTM Engineer Published September 18, 2026 Read time 4 min read APP TIPS ## The operating decision An equipment warranty RMA workflow should connect the reported failure, installed asset, approved remedy, replacement shipment and required return. Keep technical diagnosis, coverage and credit authorization separate. Automation can assemble the evidence and follow up on obligations, but creating an RMA does not prove that a returned part is eligible for credit or that a replacement fixed the machine. Close each obligation only when the responsible owner confirms its outcome. Explore the complete [industrial equipment and machinery integration and automation hub](https://www.stacksync.com/industry/manufacturing/industrial-equipment-machinery) for the systems and processes around this guide. ![Summary card: Equipment RMA workflow for replacement, return and credit](https://www.stacksync.com/images/blog-highlights/icp-equipment-warranty-rma-replacement-return-workflow.webp) ## What this looks like in industrial equipment and machinery An equipment builder sends an approved replacement drive to restore a customer’s machine before receiving the failed unit. The service case is marked resolved when the replacement ships, leaving the return untracked. Months later, finance cannot tell whether a charge or credit is due. A connected handoff preserves the installed asset, warranty decision, replacement order and expected return as related but distinct records. Service can resolve the operating problem while the returns team and finance continue the outstanding commercial obligations. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Failure and asset | Service operations | Link the symptom, machine serial and installed configuration to the original service case. | | Approved remedy | Warranty administration | Record coverage, replacement scope and any customer return obligation. | | Replacement transaction | Order management | Retain the accepted order and shipment references without using them as evidence of a completed return. | | Returned-unit disposition | Returns and finance | Track receipt, inspection and the separate decision governing a credit, charge or other resolution. | ![Record ownership diagram: Failure and asset, Approved remedy, Replacement transaction](https://www.stacksync.com/images/blog-diagrams/icp-equipment-warranty-rma-replacement-return-workflow.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Resolve the technical and coverage decisions Identify the asset and applicable part before deciding the remedy. Obtain the required warranty approval and record its scope. A service engineer’s recommendation should not silently determine financial coverage or waive a return requirement. 2. 02 Create linked obligations Represent the replacement, failed-part return and any financial disposition separately. Give each an owner and due condition. Link them to the same case so people can understand the whole remedy without assuming that every obligation shares one completion date. 3. 03 Prevent duplicate replacement action Check for existing orders and shipments against the approved remedy before creating another request. A customer follow-up about delivery should enrich the same case, not authorize another part. Retain uncertain destination responses for reconciliation before retrying. 4. 04 Follow the return through disposition Collect the return receipt and inspection outcome, then route the financial decision to its owner. A received box may contain the wrong unit or incomplete items. Preserve those exceptions instead of automatically applying the expected credit. 5. 05 Close operational and commercial work deliberately Allow service to record restored operation while keeping unresolved return or finance tasks open. Define the overall case-closure rule so the remaining obligations remain visible to the team that owns them. Review aging cases without reopening a solved technical issue unnecessarily. ![5-step operating sequence: Equipment RMA workflow for replacement, return and credit](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-equipment-warranty-rma-replacement-return-workflow.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### The returned serial differs from the expected unit Route the discrepancy to returns and service for resolution. Do not match solely by part description. ### The customer needs a second replacement Require a new supported remedy decision and link it to the prior attempt. Do not reuse the original approval without checking scope. ### The machine is repaired but the return is overdue Keep the technical resolution and return obligation separate, with follow-up handled under the approved commercial policy. ## What to verify before expanding - One approved remedy links to its replacement and return references. - Shipment of a replacement cannot close an unreceived return obligation. - Returned-unit discrepancies require disposition before financial action. - A repeated customer status inquiry creates no new replacement transaction. ## 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 failure and asset example and the exception your team handles most often, for example the returned serial differs from the expected unit. - [Commissioning-readiness automation for equipment manufacturers](https://www.stacksync.com/use-case/equipment-commissioning-readiness-automation) - [Equipment commissioning readiness: connect sales promises, site prerequisites and service dispatch](https://www.stacksync.com/blog/equipment-commissioning-readiness-workflow) - [AI agents for equipment aftermarket requests: prepare compatible parts proposals](https://www.stacksync.com/blog/equipment-genie-aftermarket-part-request-guide) - [Equipment parts AI exceptions: serial ambiguity, supersession and incomplete kits](https://www.stacksync.com/blog/equipment-genie-part-supersession-serial-exceptions) - [Coordinate Closed-Won Onboarding Across Salesforce and NetSuite](https://www.stacksync.com/blog/coordinate-closed-won-onboarding-across-salesforce-and-netsuite) - [Salesforce ERP Integration: Best Real-Time Sync Solutions in 2026](https://www.stacksync.com/blog/best-data-integration-solutions-for-salesforce-and-erp-with-real-time-sync) 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 Should the service case remain open until finance finishes? Use the business’s defined lifecycle. Separate obligation states let service record its outcome while finance and returns retain accountability for their remaining work. Can the workflow issue a credit when a return is received? Only if the approved policy and exact operation support that action. Receipt and eligibility for credit are different decisions. Which measure is meaningful? Track unresolved return obligations, duplicate replacement requests and the time from returned-unit disposition to an approved financial outcome. 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 Equipment commissioning readiness: connect sales promises, site prerequisites and service dispatch 4 min read read](https://www.stacksync.com/blog/equipment-commissioning-readiness-workflow) [App tips Coordinate Closed-Won Onboarding Across Salesforce and NetSuite 8 min read read](https://www.stacksync.com/blog/coordinate-closed-won-onboarding-across-salesforce-and-netsuite) [App tips AI agents for equipment aftermarket requests: prepare compatible parts proposals 4 min read read](https://www.stacksync.com/blog/equipment-genie-aftermarket-part-request-guide) ## 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/)