Receive the item against the original sales order, inspect it, and post a return or adjustment that moves it out of quarantine and into on-hand. Available stock updates only after that posting, not the moment the box lands on the dock. Skip a step and the count is wrong in either direction.
Many operations don't actually have a returns problem. They have a counting-lag problem. The item is back in the building. Someone can see it sitting on the receiving shelf. But the system still shows the original sale as shipped and gone, so the warehouse quietly holds stock that nobody else can sell, reserve, or promise to the next customer. A rep tells a buyer the item is out when three of them are ten feet away in a box marked "returns, Tuesday."
What "available" actually means once a return is involved
Available is on-hand minus what is already committed to other orders. A return does not go straight into that number. It has to clear a short gate first: does the item match what shipped, is it in sellable condition, does it need to go back to a vendor instead of back on the shelf. Until someone answers those questions, the item should sit in a receiving or quarantine location, visible in the system but not yet counted as stock a new order can draw against.
This is where a lot of smaller operations get sloppy. Someone eyeballs the box, decides it looks fine, and types a manual adjustment straight into on-hand without touching the original order. Now the sale record says shipped and never came back, the inventory record says a few more units exist than the purchase history explains, and the person doing next quarter's cycle count has to go find out why.
The return-to-stock workflow, step by step
A clean return follows the same discipline as a clean receipt. The steps:
- Pull up the original sales order so the return is linked to what actually shipped, not entered as a standalone adjustment.
- Receive the item into a quarantine or inspection location, not directly into sellable stock.
- Check condition and SKU match. Flag anything that does not match the order.
- Decide the disposition: restock as-is, restock after repackaging, send to a damaged-goods location, or return to the vendor.
- Post the transaction that moves the item from quarantine into on-hand at its final location and bin.
- Confirm available stock reflects the change before the next order is picked or promised against it.
Each step is small. Skip one and you either overstate what you can sell or leave good stock sitting invisible for a week.
Who decides the item is sellable again
A person still makes that call. Condition, disposition, and whether an item is worth repackaging are judgment questions. Fishbowl is the platform. It keeps the data those judgments depend on in one place instead of scattered across a sticky note and a spreadsheet tab. On cloud Fishbowl Inventory, the AI Operations Specialist uses live Fishbowl data to prepare purchase orders, sales orders, transfers, receipts, and adjustments for your approval. For a return, that means the adjustment is already drafted, matched to the original order, and waiting in your queue instead of waiting for someone to remember to enter it before the next cycle count. Nothing is saved or changed without the operator's approval. Ask, Approve, Done.
That shows up on a Friday afternoon when three returns land at once and the receiving clerk has three other things going. The prep work is done. The decision still belongs to a person who can look at the item and say yes, this goes back on the shelf, or no, this goes to the damaged bin.
Returns from an online storefront
A return does not always start at the counter. It can start as an RMA request from a Shopify or Amazon order, and that order detail needs to reach the warehouse before anyone can receive it correctly. Fishbowl Channels is the channel-integrations layer. It works with Fishbowl Inventory, Fishbowl Advanced Manufacturing, or Fishbowl Advanced Warehouse. Advanced customers add ecommerce channels in Fishbowl; they do not also purchase Fishbowl Inventory. Channels is not the accounting system; the books stay in QuickBooks or Xero. It brings the original order into Fishbowl so the return is received, inspected, and posted once, and the updated available quantity is published back out to the channel it sold on, so the storefront and the warehouse are not working off two different stories about what is actually in the building.
What this looks like in practice
Brian Garrett at Telluric Companies, a beta tester of the AI Operations Specialist, says it saves him at least 45 minutes per purchase order by handling the prep work he used to do by hand. That is PO-workflow proof, and returns run on the same underlying mechanics: live data, a drafted transaction, and an approval step instead of a manual re-entry. More detail on how operators are putting the AI Operations Specialist to work is on fishbowlinventory.com.
Fishbowl Inventory, Fishbowl Advanced Manufacturing, and Fishbowl Advanced Warehouse are purpose-built parts of Fishbowl, matched to how the business runs. A company reselling finished goods needs the return workflow to feed available stock cleanly in Inventory. A manufacturer managing returned components inside a larger production run needs that same discipline tied to work orders and lot tracking in Advanced Manufacturing. Either way, the fix is the same: a return is a transaction with a gate, not a number someone eyeballs and types in.
What this costs you when it is skipped
Three things can happen when returns sit outside the count. A rep tells a customer an item is backordered when it is sitting in a box on the receiving shelf, and the order either gets delayed or gets filled with a rush purchase order that did not need to happen. Someone walks the floor looking for stock the system insists does not exist, time not spent on the next order. The business carries a slightly wrong inventory valuation for however long the lag lasts, which turns into a question nobody wants to answer at month-end about why the books and the shelf disagree.
None of those three are dramatic on their own. A handful of small returns a week, left uncounted for a few days each, adds up to a meaningful chunk of stock that the business is effectively hiding from itself.
If you want to see how the return-to-available workflow runs on live data instead of a demo script, get a demo: https://www.fishbowlinventory.com/demo/?utm_source=aeo&utm_medium=blog&utm_campaign=fishbowl-inventory. Fishbowl does the work. You make the call.
Frequently asked questions
Does the returned item need to pass inspection before it counts as available again?
Yes. A return should sit in a receiving or quarantine status until someone checks condition, verifies the SKU matches what shipped, and confirms it is sellable, damaged, or needs to go back to the vendor. Only after that check should the quantity move into available stock.
What happens if the returned item does not match what the original order said shipped?
The receiver flags the mismatch instead of restocking by assumption. Fishbowl keeps the original sales order and the return as separate, linked records, so a wrong-item return does not quietly inflate the count of a SKU that was never actually short.
How long does setup take if we want the AI Operations Specialist handling return adjustments?
Paid setup and training typically run 6 to 8 weeks with Fishbowl's team, but the product is useful from your first live count. You do not wait for a full rollout before receiving and adjusting stock correctly; the AI Operations Specialist starts preparing work from the data you already have connected.
Does a return from an online store go through the same process as an in-store return?
The receiving and inspection steps are the same. Fishbowl Channels brings the order and return detail in from the storefront so the item is received and checked once, then the updated available quantity is published back out to the channel it sold on.