adding items through headquarters vs. store operations

Hi Benjamin - you're pretty much on the right track.

Think of headquarters as a central repository of data. Create all your new items, pricing, sales, discounts, etc at headquarters and push these down to the stores using the appropriate worksheets. If an item is unique to a store, generate the 250 worksheet just for that store (optionally, do the 250 for all stores but make that item inactive at the stores that don't carry it)

- there really is no harm done if a unique item shows at a non-related store with a quantity of zero.

You can add an alias locally at a store, but you're probably better off do> Hi, would somebody be able to explain when to use headquarters to add

Correct me if I am wrong, but you would never want to create an item at a store because the sales data will not appear in HQ.

Okay. Thanks for firming that up in my mind. It seems strange (from a usability standpoint) that none of those options are blocked in SO. I guess you just have to know what you're doing. Thanks convoluted & Jason (Jason - that sounds unfortunate but probable).

Hi Benjamin

Just to agree with what the guys have already said.

In big bold loud letters...

IF USING HQ DO NOT ADD ITEMS AT STORE :)

Believe me I have had so much hassle from this being done in the past.

To answer your po> Okay. Thanks for firming that up in my mind. It seems strange (from a

We have a utility that allows you to create item at store and HQ at the same time whilst you are at store - so you can start selling it right away.

Disabling the OK button takes away the ability to adjust other things that you may WANT to adjust at the store level, like manual price adjustments, manual cost adjustments, and manual quantity adjustments. That does not seem to be a good solution in my opinion.

I will never understand why this functionality is not built into RMS SO and HQ. They can do it for global customers... Why not global items?