Seems to me, as I have to deal with this kind of crap all the time as
well, the best way to handle it is not "hash it out".  Simply write up
and give them a document detailing the limitations and most importantly
the cost risk of what they are doing and make sure you save a copy of it
for your self.  If you can get them to sign it, thats even better.  A
lot of times with people who make mistakes like this the only way to
change their mind is to let it bite them in the ass.  And while it is
your job to point the problem out it is not your job to force them to
take your advice no matter how right you are.

Harkins, Patrick wrote:

> Well that's pretty clear then. Matt is just going to have to hash it out
> with his client.
>
> -----Original Message-----
> From: Erika L Walker-Arnold
>
> I've already done this just by shopping. I tend to buy similar things in
> different colors. They never scan them all together. "I have to scan
> each one separately because each one is a diffferent SKU number." Plus,
> when I was in retail. We did reports every week by SKU number on which
> colors sold better than others ... And when cashiers were caught
> scanning several items of different colors by scanning the first one and
> entering the number in the register - they were reprimanded.
>
> It's just not recommend practice. Period. Maybe for a mom and pop shop
> ... But any retailer worth their salt  know you separate skus based on
> color. Full stop.
>
> Outbound email scanned for viruses. (e232)
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to