multiple stores

we are currently using rms in our museum store. Now we want to sell tickets and be able to use the system at our admissions desk. is there a way to keep items separate or does the 2nd store use the same database? would it be better to purchase another entire system so the store items would remain secure or is there a way to add the 2nd store and keep people out but still be able to have the front desk people able to get their own reports, etc. Any help would be appreciated!

Reply to
ellan b
Loading thread data ...

Are you already using a HQ environment? If so, then you would open your Front desk as an additional store and create and keep all items in HQ. What you would then do is set all store skus to a status of Inactive, and Do not Order for the Front Desk - and then all Front Desk skus to Inactive and Do Not Order for Store. When you create new skus - you can selectively issue (I use region) to specific store types. This will keep your reporting accurate - separate and together (HQ) - for each store.

If you use the same db - you will see cumulative sales - and both the Front Desk and Store will see/share each other?s skus. Not awful if you are bar-coded - but not great for HQ/SO reporting.

Does this make sense?

Reply to
jocelynp

Ellan, We have worked with a couple museums to develop a lightweight bridge between RMS and the Ticketmaster Vista program. If you are using Ticketmaster for ticketing and are interested in learning more please give our number below a call and ask for Rick Feuling, or give him an email at snipped-for-privacy@rite.us.

Reply to
rsakry

Ellan, I recently installed an RMS system in a similar application, a Zoo. We have 6 touch screen pos terminals, 2 in the gift shop and 4 in the admissions booths. The gift shop and admissions share a common database and we use departments and categories to separate the two areas. It is easy to create reports that contain just the specific areas you are interested in for sales. We print barcodes for all items in the gift shop and we began our 6 digit ILC numbering at 100000 and the codes for admissions are using a different range of ILCs so there will not be conflicts if you wish to run range reports. As an aside, we are using the customer file to track patron zip codes and it is working really well and it is good demographic reporting data. I was able to find a site on the internet that allowed me to download every zip code in Arkansas to use to set up the initial "customer file".

Regards,

Kinnard

K> we are currently using rms in our museum store. Now we want to sell tickets

Reply to
Kinnard

Reply to
ekrvcr

Retail Realm has a ticketing system built as an application on top of RMS with event planning, admission, membership, coupon and voucher handling etc... If you are interested contact me. This is a great application for Zoo, Museums, Galleries, Theme Parks, Theatre and Cinemas.

Reply to
Afshin

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.