Why do Shopify refunds add inventory back in NetSuite?

Connectors sync a Shopify refund as a Cash Refund (for orders billed as Cash Sales) or a Credit Memo (for invoiced orders). When those records carry inventory item lines, NetSuite treats the items as returned and restocks them, even if the order was cancelled before shipping or the customer kept the item.

How should Shopify returns be recorded in NetSuite?

As a Return Authorization when the return is approved, an Item Receipt when the item arrives (at the location where it actually lands), and then a Credit Memo or Cash Refund created from the RMA, synced back to Shopify to release the money.

How do I stop cash refunds from restocking items in the NetSuite Connector?

Oracle documents two options under Mappings > Other Transactions > Transaction Item for Cash Refund: map the lines to a dedicated return location, or set the item quantity to 0. The first needs Multi-Location Inventory; the second loses the record of what was returned and does not work for items with inventory detail.

How should refunds for unfulfilled Shopify orders be handled in NetSuite?

Close the unfulfilled sales order lines and refund the payment without item quantities, ideally against a Customer Deposit if you bill after fulfillment. In Celigo, set a default refund location to avoid MLI_LOCATION_REQUIRED errors on lines that have no location yet.

Does Shopify say whether a refunded item is coming back?

Yes. Each refunded line has a restock type: cancel for unfulfilled lines, return for items coming back and no_restock for money-only refunds. Mapping on that value is the cleanest way to send each refund to the right NetSuite record.

Shopify Refunds in NetSuite: Stop Phantom Restocks

Contents7 sections ↓

A customer cancels before shipping, or gets a refund and keeps the item, and a week later the warehouse count is off. Inventory in NetSuite says you have units that are not on any shelf. A common cause: every Shopify refund is synced as one kind of NetSuite refund, and that refund puts the items back into stock.

Direct answer: A Shopify refund can mean three different things: an order cancelled before it shipped, a product that physically came back, or money returned while the customer keeps the item. Each needs a different record in NetSuite. Cancellations should close the order lines and refund the payment with no inventory movement. Physical returns should go Return Authorization, then Item Receipt, then the refund, so stock comes back only when it arrives. Keep-it refunds should credit the customer with no item quantity. When an integration syncs all three as a cash refund or credit memo with item lines, NetSuite restocks items that never came back. The fix is in the mapping: use Shopify's per-line restock information, a return location or zero quantity for refunds without a return, and RMAs for real returns.

Written on November 5, 2026, from Shopify's, Celigo's and Oracle's documentation, linked at the end.

What NetSuite creates for a Shopify refund

Both of the common connectors mirror NetSuite's own Refund button. The record depends on how the original order was billed:

Original order billed as	Celigo Shopify integration app creates	Oracle NetSuite Connector creates
Cash Sale	Cash Refund	Cash Refund
Invoice	Credit Memo, then a Customer Refund applied to it	Credit Memo
Customer Deposit (not yet billed)	Customer Refund against the deposit	Not covered in Oracle's FAQ

A Cash Refund or Credit Memo with inventory item lines is a return of those items as far as NetSuite is concerned. Oracle's connector documentation says it directly: when syncing refunds, "you can have NetSuite automatically restock the refunded items shown in cash refund records." That is right for a return. It is wrong for the other two cases.

The three kinds of refund, and where each should land

Case	What happened physically	Right result in NetSuite	What goes wrong if synced as a plain refund
Cancellation before shipping	Nothing left the warehouse	Close or cancel the open sales order lines; refund the payment (customer refund against the deposit, or a refund with no restock)	Stock goes up for units that were never picked
Return	The item comes back, maybe to a different location, maybe damaged	Return Authorization → Item Receipt at the location where it arrives → Credit Memo or Cash Refund → Customer Refund	Stock comes back on the refund date, at the wrong location, before anyone has checked the item
Refund without return	Customer keeps the item (damaged, late, goodwill)	Credit with no inventory quantity, coded to a returns or allowances account	Stock goes up for units the customer still has

Shopify already tells you which case you are in. Each refunded line in Shopify carries a restock type: cancel (the line was not fulfilled), return (the item is coming back) or no_restock (money only). Integrations can read it, but a mapping has to be set up to use it.

The three-step return flow

For real returns, the pattern that keeps inventory and the GL right is the one NetSuite was built around:

Return Authorization (RMA). Created when the return is approved, from Shopify, from a returns app (Loop, Happy Returns and similar) or by customer service. No inventory or GL impact yet.
Item Receipt against the RMA. Created when the box arrives and someone checks it. This is where you decide the location and whether the item goes back to sellable stock, a returns location or write-off.
Refund from the RMA. A Credit Memo (and Customer Refund) or Cash Refund, created from the received RMA, which then syncs to Shopify to release the money.

Oracle's own guidance for its connector matches this: if you do the RMA and receiving in NetSuite, issue the refund in NetSuite and let the connector sync it to the storefront. Celigo's integration app can also sync NetSuite refunds back to Shopify, classifying them as order refunds or RMA refunds.

The trade-off is speed: the customer gets the money after the item is received, not when the label is printed. Many brands accept that; others refund on the carrier scan. Either way, inventory should move on receipt.

Fixes inside the connector

If you can't redesign the flow now, both connectors give you ways to stop the worst of it.

Oracle NetSuite Connector (under Mappings > Other Transactions > Transaction Item, transaction type Cash Refund):

Map a return location. Create a location for returned goods and map it on cash refund lines. Refunded quantities land there, not in sellable stock. Needs Multi-Location Inventory, and inventory reports must exclude that location.
Set item quantity to 0. Simple, but you lose the record of what was returned, and it fails for items that need inventory detail (lots, serials, bins).

Celigo Shopify integration app (Settings > Refunds):

Item for custom refund adjustments. Refunds that are not tied to item lines (shipping, goodwill) post against a non-inventory item you choose.
Default refund location. Fixes the "MLI_LOCATION_REQUIRED" error on refunds of unfulfilled lines, which have no location yet; a Celigo answer on its community forum recommends this setting or a flow mapping for the location.
Flow mappings. Use the Shopify restock type to send no_restock and cancel lines to zero quantity or an adjustment item, and only return lines with item quantities.

Cancellations need their own path

Refunds before fulfillment are where most phantom stock comes from, because the connector sees a refund and the order has no fulfillment yet. Two setups avoid it:

Bill after fulfillment. Take payment as a Customer Deposit at order time and create the Cash Sale or Invoice when the order ships. A cancellation is then a closed sales order line plus a Customer Refund against the deposit. Nothing to restock.
Treat Shopify cancellations as order edits. When a line is cancelled in Shopify before it ships, close that line on the NetSuite sales order instead of creating a refund transaction with items.

If you bill at order time (a Cash Sale before shipping), NetSuite has already relieved inventory for goods still on the shelf, and every cancellation needs a correction. That is a design choice worth revisiting with your integration partner.

Inventory and Shopify never quite agree?

We audit your Shopify and NetSuite refund mappings, fix the restock logic and set up RMA-based returns in Celigo or the NetSuite Connector.

Get a refund flow audit

A quick check you can run this week

Run a saved search of Cash Refunds and Credit Memos from the last 90 days with inventory item lines and no Return Authorization in Created From.
Compare against Shopify refunds by restock type for the same period.
Every cancel or no_restock line that shows up as a NetSuite refund with item quantity is a unit of phantom stock. Count them, and you have the size of the problem and the business case for fixing it.

For the wider integration design, see how to make a Shopify and NetSuite integration scale, Shopify order management with an ERP and Shopify inventory management with NetSuite.

Sources

Refund resource: restock_type (Shopify Admin API)
Sync order refunds between NetSuite and Shopify (Celigo)
How does Celigo handle refunds for unfilled items? (Celigo community)
NetSuite Connector Refund Sync FAQ (Oracle NetSuite help center)
Stopping Cash Refunds from Restocking Refunded Items (Oracle NetSuite help center)

What clients ask before signing

Gustavo · BrokenRubik

Replies by email within 24 hours

Gustavo

Connecting a store, a 3PL or another app to NetSuite? Name the two systems and we'll reply with the approach we'd take.

Gustavo Cañete

Co-Founder & Development Director

Co-founder and Development Director at BrokenRubik overseeing technical excellence and development operations. 12+ years of experience leading NetSuite development teams and delivering complex enterprise solutions.

12+ years experienceOracle NetSuite Certified +1

NetSuite DevelopmentSuiteCommerce AdvancedTeam ManagementTechnical Leadership+2 more