Is there a maximum number of SKUs the system can handle? Is there a practical limitation and what are the factors to consider?
Does anybody know of any best practice guidelines when it comes to managing items?
The theoretical max is about 2.1 billion - I don't have the exact number memorized anymore.
Practical is a different story... Your server & registers both need to be properly configured for the number of SKUs you need. RAM is the biggest factor in that - if you have a lot of SKUs, you'd better have a lot of RAM.
At a certain point, the Item Lookup Window becomes useless, but RMS allows you to default to the "Find" window, which is much more usable for large lists.
100,000 SKUs would be considered a large number in RMS; You would probably want to start using the find window before that. If you size the hardware properly, you could theortically go well beyond that number in RMS, but you would probably be better served by a system that's designed for that environment.Glenn Adams Tiber Creek C> Is there a maximum number of SKUs the system can handle? Is there a
The limitation is in the hardware and not on RMS. SQL is scalable enough to handle those number of records.
We have an installation with 300,000 + SKUs. The trick is to properly size-up the hardware considering the number of SKUs, number of connected users, number of transactions, etc.... If i remember it right, the RAM is around 3GB or 4GB.
\Franco snipped-for-privacy@gisimplement.com
"Glenn Adams [MVP - Retail Mgmt]" wrote:
BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.