Stock
Adjustments and oversell cover
Selling or fitting something the count says you do not have is recorded as an oversold unit rather than pushing stock negative. The record names the item, the branch, the sale or repair it came from, the serial if there was one, and who did it.
What it does
Real shelves disagree with real systems. A part gets used without being logged, a delivery gets stocked twice, someone counts wrong.
The usual outcomes are both bad. Blocking the sale means a customer standing at the counter is turned away over a number. Letting stock go negative means the number is quietly meaningless from then on.
Fixmo does neither. The sale goes through and the shortfall is written down as its own record, with enough detail to find and fix it.
That record names the item and branch, the sale, repair or document it came from, the serial number if one was involved, and who was serving. Adjustments made deliberately are recorded too, so a correction is visible rather than looking like the count was always that way.
Every capability
| On a shortfall | The sale completes and the gap is recorded |
|---|---|
| Never | Stock is not pushed into a negative number |
| Recorded | Item, branch, source code, serial, and who was serving |
| Sources | Sales, repair part usage and document lines |
| Notification | An alert is raised when cover is applied |
| Serials | A serial covered this way is marked with when it happened |
| Adjustments | Deliberate corrections are recorded, not silent |
Questions
Why let the sale go through at all?
Because the customer is real and the number might not be. Recording the gap keeps the sale and lets you fix the count afterwards.
How do I find what needs correcting?
Each covered unit is its own record with the sale or repair code that caused it, so you can trace it back rather than hunting.
Does this apply to repairs as well as sales?
Yes. Parts fitted on a repair and lines on a document are covered the same way.