One or more of the serialized units are no longer in inventory" (Sage 50)
Sage 50 cannot complete a serialized-inventory transaction because the serial numbers it expects are missing from stock.
Sage 50 is telling you that a transaction references serial numbers the program can no longer find in inventory. The message usually appears when you post, edit, or delete a transaction that involves serialized items, such as a sales invoice, a credit note, or an inventory adjustment. In plain terms, the serial records and the quantity records have drifted out of agreement, and Sage 50 refuses to complete the posting until they match.
What the message actually means
Serialized inventory in Sage 50 tracks two things in parallel: the quantity on hand for the item, and the individual serial numbers attached to that quantity. The two should always agree. When they do not, a transaction that tries to remove or return a specific serial number fails, because the program looks up that serial number and finds it is not in stock, even if the item itself shows a positive quantity.
So the message is rarely about a missing physical unit. It is almost always about inconsistent data: a serial was sold twice, removed by an adjustment that did not update the serial list, or left behind by a transaction that was edited after the fact.
Why the mismatch happens
Common triggers include editing or deleting an old invoice after the serial numbers have moved on, importing transactions where serials and quantities were handled separately, a workstation interruption during posting, or restoring a backup that does not line up with later activity. Conversions and year-end processes can also leave serial records behind if they were interrupted partway.
Check the serial list for the item first
Open the item’s serial number list and compare it against the quantity on hand. If the item shows three in stock but only two serials, you have found the mismatch. Correcting it with a serial inventory adjustment, so the serial list matches the true count, is the safest fix and preserves your audit trail. Do this on a copy of the backup, and verify the item’s quantity and value afterwards.
Restore a backup if the damage is recent
If the message appeared suddenly after a specific posting or crash, the cleanest route is to restore the most recent backup taken before the problem. You lose whatever was entered since, so weigh that against how much re-entry is involved. If the mismatch has existed for a while, a restore may simply move you back to an older version of the same problem.
When the file needs professional attention
If the mismatch affects many items, or the serial list and quantities disagree no matter what you adjust, the underlying data needs repair rather than more adjustments. Repeatedly forcing adjustments on top of a damaged serial table tends to spread the inconsistency. Our engineers repair Sage 50 databases with exactly this kind of serial and quantity disagreement, and we can assess what is recoverable before you commit to anything. See our Sage 50 database repair service for what is involved, or contact us about your file for a free evaluation and quote.