Can someone explain about headquarters. Lets say I have 3 stores. 80% of the stock in each store is the same. I believe I have to pick one store as a template database? Will the other 20% of stock from each store that is not in the template database be uploaded to headquaters.
*This post is locked for comments
Jay,
You should NOT change the inventory levels at the Headquarters level.
Inventory is what I referred to as dynamic data. It should be controlled at the store level.
As the physical merchandise is received into the store (either through a purchase order, a store-to-store transfer, or a physical inventory count), the quantity at that store would upload to Headquarters.
HQ will let you view and report on the inventory levels at a given store, but you should not use HQ to control the inventory levels at the store. That is managed in Store Operations at each store.
Bill
I have the store template created but I am a bit confused about adding stock. Stock changes each season so I have new stock coming within the month. Does the Physical stock have to be added at HQ then shipped to each store.
Hi,
In a RMS HQ environment it is best to enter all items in HQ and than send the items to all the stores.
RMS HQ is suitable for a centralized HQ environment where all items management is done through HQ.
Than the individual Stores can do their purchasing and receiving for the items they want to order and keep in stock.
So in the specific Shoe example all shoes sizes will be created as individual items in HQ and sent to all 3 stores.
RMS also has Matrix capability which can be used for Style, Size, Color etc.
Hope this is helpful.
regards,
Mihir Shah
Diviasoft, Inc.
"In your situation, would each shoe size be a distinct item lookup code?"
Yes all shoes size's have different item lookup codes
Jay,
In your situation, would each shoe size be a distinct item lookup code?
If so, you would still probably want to send all item lookup codes from your Headquarters item catalog down to all stores, so they would have the item lookup code in their system.
The item catalog in HQ is what is called static data. That is stuff like the item lookup code, description, department, and category. In a multi-store environment, this static data is meant to be maintained at the Headquarters level and pushed down to the stores with worksheet 250.
The inventory for that item would be controlled at the store level. As the physical merchandise is received into the store (either through a purchase order, a store-to-store transfer, or a physical inventory count), the quantity at that store would upload to Headquarters.
The inventory quantity at the store is what is called dynamic data. It can vary from store to store. It is that quantity information that gets pushed up from the store to Headquarters.
You should not need to change the inventory on-hand from the Headquarters level. The quantities at Headquarters should be for reporting purposes only.
Bill Yater
Just read your post again "Items added or changed at a store level will NOT upload to Headquarters."
Does this mean that new stock has to be added at Headquaters?
It would be Scenario 2 - Its is a Shoe shop. The problem will be with the shoe sizes. In one store the shoe size could be between size 20-27 and the same shoe in another store could be from size 22-27. This could differ from store to store. I don't think there is anything I can do cause I have no way of knowing what each store has without comparing each. As I said 80% is the same, If one of the stores is missing a SKU it might be best to just add it at the Point of sale. Will that Sku then be added to headquaters?
When you say "80% of the stock is the same", I want to clarify which of these two scenarios you are describing.
Scenario 1: 80% of the global item catalog can be found at any and all stores, and 20% of the catalog is exclusive to certain stores.
For example, if you have a global item catalog of 1000 SKUs (what RMS calls the Item Lookup Codes), 800 of those SKUs will be carried by all of your stores. In addition, 100 SKUs are only carried in store 1, 60 of those SKUs are only carried in store 2, and 40 of those SKUs are in store 3.
Scenario 2: 80% of your inventory can be found at a given store, and 20% at another store
Example: you have 1000 SKUs, and at any given time, you have around 5000 units of inventory.
Store 1 is your “flagship store” and carries 80% of the stock (4000 units), and the other 20% is distributed among your other two stores.
Remember, when you're dealing with a multi-store environment, 100% of the item catalog must be created and maintained in Headquarters.
Once you have created your Headquarters database based on a given store (say store 1), any item lookup codes which were in your other stores but were not in store 1 will not have an associated item record in Headquarters, so they are effectively orphaned in your stores. Items added or changed at a store level will NOT upload to Headquarters.
Your template store (which you will use to create your HQ database) should contain all of the items, customers, etc which could possibly exist at any store, even if the inventory level at your store is zero.
Once you have the full item master catalog in Headquarters, you can then send the item master information for some or all of the items down to the stores (which is scenario 1).
You can even send the item master information to a store which will never carry that item in inventory. (scenario 2) The store would have the item showing in their item lookup, with a quantity of zero, but you can then do a Check Stores on it and see if there is any inventory for that item in the other stores.
Bill Yater
Blue Horseshoe Solutions, Inc
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,214
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (