1. Home
  2. Point-Of-Sale Software
  3. RMS should allow local editing of global customers

RMS should allow local editing of global customers

The concept that you can have global customers without being able to edit the data where the customer interacts with the store is troubling. I understand that you need to be able to handle changes at multiple locations, but take a look at 95% of the events that occur with customers and you see that 1. it is much more frequent annoying that you can't edit a customer record at tha store than 2. it is to rarely if ever have a customer that hits two stores during 1 update period with simultaneous updates (or with HQ and a customre having simultaneous updates). You punish the 95% where there is a need and no problems for 5% which still doesn't impart much pain (if it even happens) this makes no sense.

---------------- This post is a suggestion for Microsoft, and Microsoft responds to the suggestions with the most votes. To vote for this suggestion, click the "I Agree" button in the message pane. If you do not see the button, follow this link to open the suggestion in the Microsoft Web-based Newsreader and then click "I Agree" in the message pane.

formatting link
\f88e66-7d17-417a-9298-0339b69137b0&dg=microsoft.public.pos

Reply to
BlakeEH
Loading thread data ...

formatting link
\f88e66-7d17-417a-9298-0339b69137b0&dg=microsoft.public.pos

Reply to
Luminox

This feature is also part of the Retail Realm Store and HQ Utility.

formatting link
\f88e66-7d17-417a-9298-0339b69137b0&dg=microsoft.public.pos

Reply to
Afshin Alikhani

No offense to Retail Realm, who I think has done a wealth of service for the RMS community, but...

I don't understand why Microsoft doesn't just buy these add-ins from the vendors and include them in updates for everybody. That would make the support money we pay to Microsoft a whole lot more palatable. Some add-ins out there cost $1000 or more. Imagine if 1000 people buy it. That's $1M for something a couple of programmers whipped up in a month or two. More power to the vendor if they can do it, but it seems a little over-the-top when 95% of the user community wants the solution - MS should open their wax-filled ears and give it to all of us support-paying users!

Maybe they already do some of that... Not sure. There is no way I am paying hundreds or thousands of dollars for simple workarounds that should be incorporated in the product and that are typically not as seamless as they shuold be. If the add-ins were able to be better integrated such that they did not appear and operate as third-party solutions, I might reconsider.

I think the original plan was probably to get resellers to build custom add-ins for clients who really needed them. Then developers came along to address annoyances that MS was not addressing, which is exactly what happens in a free market. However, when the vast majority of users want a feature, MS should be incorporating the fixes as a customer satisfaction strategy. They seem to have just decided to defer to the developers if there is already an add-in out there, which keeps the developers in business and makes Microsoft's job much easier, but infuriates the frustrated user community.

---end soap box here---

formatting link
\f88e66-7d17-417a-9298-0339b69137b0&dg=microsoft.public.pos>

Reply to
Jason

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.