Fishbowl: "Cannot void this sales order" — receipt already received

What triggers it

You tried to void a sales order that has activity hanging off it. One of two states is present: a pick linked to the order has reached Committed or Finished, meaning inventory has been committed or already pulled; or a receipt tied to the order has been received or reconciled, meaning goods and their cost have landed. The words “received or reconciled” in the dialog point at whichever of those two states the receipt is in. Either one takes the order past the point where it is safe to simply erase.

Why Fishbowl blocks it

A void is meant to cancel something that has not moved anything yet. Once a pick is committed or finished, real quantities have shifted and a cost layer exists. Once a receipt is received or reconciled, inventory value has posted. Voiding at that point would force Fishbowl to reverse committed inventory and remove a cost layer that other transactions may already sit on top of, and if the receipt was reconciled, to drop a record your accounting system already knows about. It refuses rather than leave your on-hand counts and inventory valuation quietly wrong.

What to do

Unwind in reverse order. First unpick or uncommit the pick so it falls back below Committed. Then unreceive or reverse the receipt. With the downstream state cleared, the void will go through. Work from the most-recent activity backward, and confirm quantities look right at each step before moving on.

If it is already reconciled or exported

If the receipt has already reconciled into QuickBooks or Xero, this is a correction, not an undo. The value is posted on the accounting side, so reverse it there with an offsetting entry or credit and keep the audit trail intact. Deleting only the Fishbowl record leaves the two systems out of sync, which is exactly the mismatch that later shows up as an unexplained inventory or COGS variance.