Look for repeated work, not a SKU threshold
A spreadsheet can be a sensible starting point. The warning is not a particular number of products: it is the cost of keeping several people, locations and orders in agreement. Before changing software, record the exceptions that consume your team's time.
Five signs to investigate
1. Staff check several files before promising stock. 2. A receipt is recorded twice or missed between shifts. 3. Transfers leave one location before the receiving team can confirm them. 4. Order status depends on asking a particular person. 5. Corrections lack a clear reason and reviewer. Keep examples for a normal working week; distinguish a missing process from a missing tool.
Test one end-to-end order
Use a small representative product set. Receive stock, allocate or prepare an order, record dispatch and reconcile the remaining quantity. Include a short receipt and a cancelled order. Ask who may edit each record, how corrections appear and what can be exported. A system that looks attractive but cannot explain an exception is not ready for your operation.
A practical VasKem evaluation
Bring your spreadsheet columns and one anonymised workflow to a demonstration. Agree the data preparation, import scope, training and any integration work before committing to a rollout. An account registration is not a promise of free implementation or an instant migration.