Hi,
this is also a question for Dave, but maybe somebody else had this problem in the past:
CD was ordered right now......I have checked that it was sold 5 years ago on another database.
Standard procedure: After payment I will delete the item from the MS database and all other databases. That's normal and quite easy!
But why it was still in the MS database?
I did a complete physical inventory check last november/december and everything was fine (I found some problems with database <> physical inventory <> inventory list, but this was fixed from my side!)
So there is a 0.5% chance that I was still wrong and have missed a Cd, but I don't think so ;-)
I have encountered this issue and emailed Dave recently about this, though may need a follow-up as not heard yet.
I am currently at the stage of doing another physical stock check before re-uploading the database (the 4th time). I used Access and converted to Excel and manually deleted the sold items.
From what you say, sounds like we have the same methodology of uploading stock databases
Well, I use Excel direct. This is very easy :-)
I will not do a re-upload of my old inventory, I have done a lot of changes manually in the database.....but not in my list ;-)
This was an old Cd from my list (uploaded years ago)
As I work with databases from time to time, I know some weird things can happen with the data inside.....sometimes it#s not possible to track these things. Hopefully this is the only problem within my & your list :-)
I don#t want to do a new stock check in the next 2 years ;-) No problem to tell a customer that I don't have the CD anymore.....because of "strange things happen..." hehe
There is a glitch whereby if an item is reserved for a customer order it sits in limbo where it is not available for sale and is temporarily removed from your online (Musicstack) database.
If you upload your entire inventory while items are in limbo, the entries corresponding to these items are assessed as new items, since we presumably don't delete items from our offline databases until the order completes.
Currently the only way round this is to manually delete items on the online (Musicstack) database corresponding to any reserved items immediately after an upload.
I have exchanged mails with Dave about this but it's a tricky one to deal with. It can affect your fill rate though, since it may unwittingly reintroduce items that have been sold and passed through the system using all the proper processes.
Disclaimer: The words and opinions expressed on this website are those of the author(s) of the postings and do not necessarily state or reflect the views of MusicStack and/or its employees. Publication on this website should not be considered an endorsement. MusicStack and/or its employees do not express or imply any warranty or assume any legal liability or responsibility for the accuracy, completeness or usefulness of any information on this website. MusicStack and/or its employees will not be held liable for any direct or indirect loss or damage arising under this disclaimer or in connection with our website. By using our website, you accept this disclaimer in full.