Mulit Store Prices in HQ

Hi Tom - yes, you can have different prices for the same SKU in different stores. There is a specific worksheet that adjusts the retail price of an item, you would prepare and approve this worksheet only for the store that needs the different price.

There are no regular product refreshes that take place automatically from HQ. Out of the box, everything must be done manually (by this I mean the maintenance to items such as price changes, changing reordering information, editing commission settings, etc).

What you will find is that you have the concept of "centrally maintained data" which is SKU data that is the same for all stores (such as description, itemlookupcode, department, supplier ordering data, etc) and "dynamic data" which is SKU data that can be different for different stores (as you mentioned, the price of the item, or the inventory cost of the item, price levels, or min/max)

Good luck with your HQ rollout - h> We are looking to add another Store and will be Converting from a SO

Thanks Convoluted!!

Is there any kind of document that outlines which data falls under the "centrally maintained" and "dynamic data" groupings. Also anything that explains all the different worksheets and there usage.

I am very comfortable with SO but know nothing about HQ.

Thanks,

Tom

Tom - if it's in the budget, engage an RMS certified partner for one to two days of Headquarters training. It'll get you up and running in no time, ease the transition to HQ and can be very valuable for your staff.

Here's some verbiage I pasted from the help guide that talks a little about what was mentioned - the help guide also contains detailed descriptions on the different worksheets' purpose and functionality - hope this helps....

Headquarters terminology and concepts The following key terms and concepts will help you get comfortable with Headquarters.

Centrally Maintained Data vs. Locally Originated Data vs. Store-specific Data Centrally maintained data refers to information that is owned and managed by Headquarters and stored in the Headquarters database. It includes items, departments, categories, sales and item taxes, suppliers, shipping carriers, account types, tender types, currencies, reason codes, discount schemes, weekly sales schedules, item messages, and global customers. If centrally maintained data is created or edited at a store, those changes will not be uploaded to Headquarters. This can cause discrepancies that affect reporting and inventory management, in addition to a breakdown in communications between stores.

Locally originated data refers to information that is originated and owned by remote stores. It includes sales transactions, work orders, quotes, layaways, back orders, cashiers, sales reps, local customers, purchase orders, inventory transfers, receipt journals, time clock entries, and dynamic item attributes (prices, costs, quantities, tax codes, reorder information, and serial numbers). This data is created and maintained in Store Operations and is regularly uploaded to Headquarters. At Headquarters, the information is in read-only format and cannot be edited or deleted.

Store-specific data refers to information created and maintained by remote stores. It includes store configuration and security settings, register setup, custom keyboard, custom POS buttons, net display channels, and receipt formats. The key difference between store-specific and locally originated data is that store-specific data cannot be viewed and reported on in Headquarters Manager.

For more information, see Bringing stores online.

Dynamic Data vs. Static Data Dynamic data refers to information that can be unique at each store. Some examples of dynamic data include item prices, quantities, and reorder information.

Static data is data that is the same enterprise wide. Examples of static data include item lookup codes, item descriptions, and supplier names.

"TomT" wrote: