Adding new stores to existing HQ

Importing the second store's inventory will be tricky. I have done it, but it was quite a procedure. I used the QSCImport utility to import into HQ, a practice which I have since been told is *not* a good idea. FWIW, it worked for me and I actually plan to do it again in one more time in the not too distant future. Always backup your store & HQ databases before any sort of import. If importing into HQ, it's probably best to stop all Store-HQ communications while you do.

Keeping the inventories separate is contrary to the very design intent of HQ. I guess it could be done, but it would be extremely difficult to manage. Every inventory worksheet would have to be tailored to a specific store. One of the major reasons for having HQ is so your stores can see each others' inventory.

Tom

"NcS" wrote:

Thanks Tom. I've used Retail Realm's Import Module for stores and am talking with them now about HQ import.

Even though each store will have different Depts/Cats. do you still think updating will be a hassel? This is my first HQ and the Docs are very difficult to understand.

The Client bought HQ and SO's from another Partner but they have bailed. I'm trying to help as much as I can but it sounds like RMS maynot work as well as OLD-Partner said. Do I understand correctly that there is no way to 'not-see' the other stores items at each stores POS?

Is there some more > Importing the second store's inventory will be tricky. I have done it, but

By design, Dept/Ctgy info is global - defined at HQ and consistent among all stores. Ditto the item table, tender types, account types and more. Look at 'Managing Enterprise Data' in the user guide/help file.

It is conceivable that you could keep one huge item table at HQ and keep subsets at the stores. This would be *really* hard to manage. For all practical purposes, I'd consider it unworkable if not downright impossible.

You can stick with local customers instead of global customers so HQ won't have much effect on the Store Ops customer tables.

The initial partner may have misrepresented RMS' capabilities. The customer may have unrealistic expectations. The customer may be better served without HQ at all - if there's no similarity between the stores, why bother with HQ? RMS is fairly inexpensive when compared to similar products. If the customer has needs beyond the scope of RMS, they may have been sold the wrong thing altogether.

Not so long ago, I was on the VAR side of the fence. It's always a special challenge to try and clean up someone else's mess. I wish you luck.

Tom

"NcS" wrote:

Hi Tom,

It's good to see you used SQImport to import into HQ. This is what we really want, as a gift / souvenieor shop we have new items almost everyday. Can please share some experiences / tips?

Regards, Jas> Importing the second store's inventory will be tricky. I have done it, but

Tom:

This is a process that I have been struggling with. I have three existing stores, each has some common items, but each has their own unique items. Would you be able to outline the steps that you took in your deployment?

Thank you in advance.

Ted Archer