Editing Retail shelf

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
The '''retail shelf''' is where a customer first encounters the [[barcode]] and other aspects of the [[product label]] (like [[nutritional information]] and any [[standard label]] included on it like "[[kosher]]" or "[[dolphin free]]").
The '''retail shelf''' is where a customer first encounters the [[barcode]] and other aspects of the [[product label]] (like [[nutritional information]] and any [[standard label]] included on it like "[[kosher]]" or "[[dolphin free]]").


Because a customer moves past many such shelves rapidly, this is probably the worst possible point to ask them to use a [[worn device]], certainly not one that they must pull off a [[belt]] or out of a [[pocket]] to use, or which is not [[handsfree]].  For these reasons the [[headset]] is the best device for delivering any detailed information at this location.  This could be done by:
This and the [[checkout counter]] are the only two guaranteed places in-store that the customer will encounter, so any [[Consumerium Service access]] should be optimized for these.  In [[friendly retail]] locations, e.g. the [[Big Carrot]] type store or [[local co-op]]s, it might be possible to augment the '''shelf''' itself, if the [[institutional buying criteria]] of that store are likely to closely match the [[individual buying criteria]] of the customer.  In that case, the [[Consumerium buying signal]]'s positive choice information becomes a definite [[price premium]] factor, and the whole store will probably be able to charge more for providing such complete profiles of what the customer is buying.
 
*[[barcode]] or [[RFID]] swiping by a [[worn device]] on the wrist which gets the cached [[Consumerium buying signal]] and plays it back into the headset;
*[[cordless callback]] initiating a call with [[cordless protocol]] and perhaps relying on [[PCS base station handoff]];
*[[cell phone]] callback with [[handsfree answer]]ing relying either on [[cell callback]] from a local server or on [[SMS message]] received handsfree and read into the headset by the phone itself, possibly via [[Python]] code.
*[[in-store radio]] which sends a [[barcode]] or [[RFID]] or [[NFC]] coded [[ID tag]] signal on a given frequency when a barcode is scanned in the store, and puts a [[Consumerium buying signal]] comment in the queue to read;
 
These would all work without taking one's hands off the product or [[shopping cart]], or one's eyes off the kids.
 
The shelf, cart or basket, and the [[checkout counter]] are the only guaranteed places in-store that the customer will encounter, so any [[Consumerium Service access]] should be optimized for these.  In [[friendly retail]] locations, e.g. the [[Big Carrot]] type store or [[local co-op]]s, it might be possible to augment the '''shelf''' itself, if the [[institutional buying criteria]] of that store are likely to closely match the [[individual buying criteria]] of the customer.  In that case, the [[Consumerium buying signal]]'s positive choice information becomes a definite [[price premium]] factor, and the whole store will probably be able to charge more for providing such complete profiles of what the customer is buying.
 
[[Category:Hardware]]
Please note that all contributions to Consumerium development wiki are considered to be released under the GNU Free Documentation License 1.3 or later (see Consumerium:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)