guess how many sku;s you have in your file ?

Mike Washington told me they where floored when they had well in excess of TWO MILLION sku;s in their Exploris. They found this out when they where moving the data to their new Eagle system

I was just told by Bob Miller that he tried to dump all sku;s with just the mvt code data ...so I could have a look. After 24 hours it jammed at 730,000 and was only 1/3 of the way thru .... OMG .... the issue of only having one data base without a slush file to hold the rest of the sku;s ( Like J-Con does with their Part Source file ) has to be an issue that has to addressed at some point (sooner please )

How many sku's ( part numbers ) do you have in your exploris ?

Should EXPLORIS have a SLUSH FILE ??

What is a slush file --- well in J-Con it was called the Parts Source file that we got a copy of monthly. A SLUSH FILE is a big file of all parts available that on MIGHT sell - so you have pricing and the counter staff find it seamless to sell - they don't recognize the data is not in the normal system.

EXPLORIS has no such slush file -- that means a couple of things -- your active files will become HUGE. When the Washington's moved from EXPLORIS to EAGLE they found out they had more than 2,000,000 - yeh -- two million parts in their file in Exploris. And since we are asking how you DELETE parts from Exploris -- we have an interesting situation that will become messy in a few years.

Ian from Alliston wants to point out that if you see a part that is NOT in your system - your Exploris will NOT go negative ...so when your incoming paperwork arrives --you system will ADD ONE once it adds the part number and you count will be wrong ... ouch. On top of that Ian feels the tracking is not up to J-Con standards to make things simple to see where an error occurred.

Some computer systems allow users to MODIFY their slush files ( we have experience with ACS computer ) -- so you could add X lines to your slush file --want to add FRAM filters -- why would you want to add every part number to your active files --add to the slush file and pull out IF and WHEN you have a sale. This is very handy for secondary lines - so in the example of Fram - you stock CARQUEST but that once in a while you need fram * for whatever reason) - you have all the data in your system and the staff make an easy sale without having to know prices and markup logic. Of course you have to maintain the data -- so you have to know how to use Excel and apply markup logic to their price updates ... but having first hand experience doing this for many secondary lines from 1996 thru 2003 - it can be done - easier if you have a couple of stores or large sales volume (to cost justify the job).