How to Restock Returned Items in Shopify Without Guessing What Came Back Sellable
A return feels finished the moment the box shows up. It isn't. Someone still has to open it, work out what's actually inside, decide what can go back on the shelf, put it back, and ideally remember why it came back so the same thing doesn't keep happening. In most stores that last stretch lives in a mix of email threads, sticky notes, and a manual inventory edit someone does "when they get a chance." Here's a cleaner way to run it, and how I built it into Pickadoodl.
Every return should answer three questions
When a return arrives, there are really only three things you need to know: what came back, why, and how much of it you can sell again. Those sound simple, but they tend to get blurred together. The customer says they sent three. The packing slip says three. One of them is cracked. So the answer to "how many do I restock?" is two, not three, and the reason for the cracked one probably belongs in a different bucket than the reason for the other two.
Where it usually goes wrong
Three failure modes show up again and again:
- The reason lives in an email. It's hard to count, so nobody can say which product or which mistake accounts for most of your returns.
- Received and restocked get treated as the same number. You add back everything the customer sent, including the damaged unit, and your available count is now wrong.
- The restock is a hand edit. Edit inventory by hand and you can add the same return twice, add it to the wrong location, or forget it entirely.
Step one: record what you received, separately from what you'll restock
On Pickadoodl's Returns page, you look up what's coming back by scanning or searching, and each returned item tracks two numbers separately: Received and To restock. Returned three and only two are sellable? Received is 3, To restock is 2. The count you restock is a deliberate decision, not an assumption.
Step two: pick a reason you can actually count
As you scan an item back in, you choose a reason from a short list instead of typing a sentence:
- Wrong item sent
- Damaged or defective
- Not as described
- Doesn't fit / wrong size
- Changed mind
- Arrived too late
- Other
You can add a short note with it, but the category is what makes returns comparable later. A list of seven choices takes a second to pick from, and it turns a pile of anecdotes into something you can sort.
Step three: restock into Shopify, once
When the return is ready, you choose a location and Pickadoodl adds the resellable units back to available inventory in Shopify. It won't restock the same return twice, and it keeps a restock history so you can see what was added, where, and when. The first time you use it, Shopify asks you to approve inventory access once. That's the only extra step.
It's a one-click add-back of returned units, not an inventory management system. It does the one job a return needs, and leaves the rest of your inventory process alone.
Read the pattern, not the pile
The real payoff comes later. Return insights shows what came back by reason, product, and variant over any date range, lets you drill into the individual records, and exports to CSV. A few ways to read it:
- "Wrong item sent" clustering on one product? That's a picking or packing problem, often a lookalike SKU or a confusing bin.
- "Not as described" on one listing? The photos or description are promising something the product doesn't deliver.
- "Doesn't fit" concentrated in one variant? Your size chart needs work.
- "Damaged or defective" across many products? Look at packaging and carrier before you blame the product.
- "Arrived too late" climbing? That's a shipping-speed or cutoff-time conversation.
None of those fixes is obvious from a stack of emails. Each one is obvious from a sorted table.
Connect it to the rest of your store
Pickadoodl adds a Return received trigger to Shopify Flow, which fires when a return is marked completed. It carries the order name, who received it, units received, units to restock, and the reasons, so you can, for example, send your team a message whenever a return includes a damaged or defective item. (I wrote more about this in the post on when Shopify Flow is the right answer.)
What it doesn't do
A few honest limits. Pickadoodl doesn't generate return shipping labels, and it isn't a full reverse-logistics system. Returns you logged before the restock feature existed stay in your history, but they can't be restocked from the app, since there's no safe way to know what was already added back by hand. Everything from here on can be.
Try it on your next return
Pickadoodl is free to start, up to 75 orders a month with the full feature set and no trial required, so you can run your next real return through it and see whether the Received versus To restock split changes how you handle it.