|
Posted by convoluted on July 6, 2008, 3:40 pm
Please log in for more thread options Yes you're right, you don't want to create an item at a store because the
sales data will not appear in HQ - when I said add an alias, this involves
editing an existing item (which should have been created in hq) to add that
alias - since the alias is basically another way to list an item on a sales
transaction, the original item always gets sold based on its item lookup
code.
"Jason" wrote:
> 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.
>
>
> > 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
> > doing it in headquarters, as the new alias may eventually be needed at
> > other
> > stores that also carry that item. When you can, take advantage of how
> > headquarters can centralize item management. Also consider the
> > possibility
> > of getting some RMS training from a good, rms certified partner - the
> > money
> > spent will be well worth it.
> >
> > "benjamin.seth@gmail.com" wrote:
> >
> >> Hi, would somebody be able to explain when to use headquarters to add
> >> items vs. store operations? As a general rule, all new items should be
> >> added through headquarters and then downloaded to individual stores
> >> through worksheets, correct? If an item is added through a store, that
> >> item will not be uploaded to HQ? That's my understanding.
> >>
> >> If a store has a unique item that none of the other locations carry,
> >> can that be added through store ops. manager only without causing
> >> reporting confusions or other problems? Or do we need to write down
> >> the info. and call up HQ to have them manually add the item?
> >>
> >> Also, what about when barcodes for an item change at different
> >> locations? Is adding an alias on the store level sufficient or should
> >> the multiple barcodes be added through HQ?
> >>
> >> Or in general, if someone has some "hard & fast" rules / underlying
> >> theory that can help me gain an understanding of what should and
> >> shouldn't be done for future scenarios with HQ vs. SO ... I'd really
> >> appreciate it. Thanks!!
> >>
>
>
>
| 
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML Sitemap