Hi,

Background:
We run 3 standalone Adagio systems in our 3 offices across Canada. We keep 3 separate inventories - 1 in each office. We would like to clean up these inventories as they have many inaccuracies in fields like part# and vendorpart#. Each office has approx 12,000 inventory items and we have 1,000 where the part# matches in all three offices (It likely should be more but each office makes independent decisions on how/when to put a part# into the system). The upkeep and cleanup is a huge job so we started to think of other ways to accomplish the same thing.

We have a new standalone pricing SQL database which has a large number of products that we offer for sale in all our offices (>100,000 currently). Practically we sell approx. 10 % of the products although they are not necessarily always the same ones. This database has the vendor part number along with all the pricing and costing information. The front end for this pricing database has stock information along with batch costs/dates and last 12 months of sales numbers IF it can find a part number match. Unfortunately, too many part numbers don't match due to our historical inventory management workflow.

My idea is to pick a point in time where we freeze the current adagio inventory. We then
erase all the current inventory items and import our pricing database. We would need to do adjustments for the current inventory levels (and reprint any incorrect labels) but then could move forward with 3 inventory systems that were identical.

We have a daily SQL dump and front end of our Adagio data so finding history would not be a problem.

A big advantage would be the ability to automate the process of keeping the supplier pricing current. We could export the inventory out of Adagio and confidently match the vendor part number against our pricing system.

One day we would like to be able to run 1 Adagio install for all 3 offices and this would go a long way to enable this goal.

My main concern here is running an inventory system in Adagio that has that many parts. Our Quotewerks system has no problems with this size but it is SQL based. I would be worried about slowing down any functions that deal with inventory including adding items to orders/POs along with running inventory processes.

Does anyone run an inventory this large? Any comments or concerns about implementing my idea?

Thanks for reading.

Alex

The largest inventory database I have seen contained about 500,000 items. It was from a car dealership who imported their supplier's entire parts list.

Alex:

I wouldn't recommend importing the entire parts list if you are only using a small subset of that parts list.

Why are you running three separate databases. One on a wide area network would work well and solve the problem of each office having a different part number for the same thing.