Scan barcode: Difference between revisions
(the bottleneck operation) |
m (Reverted edits by 119.111.124.194 (Talk); changed back to last version by Juxo) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
To '''scan barcode''' requires a powered [[barcode scanner]] and a few seconds, under one second at a typical [[checkout counter]] with trained users and a powerful scanner. This is probably the most critical of the [[performance requirements]] - if it takes too long to do [[ | To '''scan barcode''' requires a powered [[barcode scanner]] and a few seconds, under one second at a typical [[checkout counter]] with trained users and a powerful scanner. This is probably the most critical of the [[performance requirements]] - if it takes too long to do [[intrashop comparison]], it just won't be done, and every second it takes to scan is one less second to do the lookup of the [[Consumerium buying signal]]. | ||
This is going to be a very very hard problem to solve. Overall the signal to the [[worn device]] can probably take no more than three seconds to receive - unless it is to be queued up for [[in-store radio]] or [[checkout counter]] presentation, which may require diligent consumers to return products to the shelves. If they do this in some way that we support directly, and if we or a store (!) pays them to do it, say in [[frequent buyer card]] type discounts, we can actually discover exactly what purchases were disabled by [[Consumerium buying signal]], and possibly (less likely) which ones were enabled by it. | This is going to be a very very hard problem to solve. Overall the signal to the [[worn device]] can probably take no more than three seconds to receive - unless it is to be queued up for [[in-store radio]] or [[checkout counter]] presentation, which may require diligent consumers to return products to the shelves. If they do this in some way that we support directly, and if we or a store (!) pays them to do it, say in [[frequent buyer card]] type discounts, we can actually discover exactly what purchases were disabled by [[Consumerium buying signal]], and possibly (less likely) which ones were enabled by it. | ||
:This article does not portray the [[Checkout Consumerium]] functionality as originally imagined | |||
Latest revision as of 15:17, 31 July 2010
To scan barcode requires a powered barcode scanner and a few seconds, under one second at a typical checkout counter with trained users and a powerful scanner. This is probably the most critical of the performance requirements - if it takes too long to do intrashop comparison, it just won't be done, and every second it takes to scan is one less second to do the lookup of the Consumerium buying signal.
This is going to be a very very hard problem to solve. Overall the signal to the worn device can probably take no more than three seconds to receive - unless it is to be queued up for in-store radio or checkout counter presentation, which may require diligent consumers to return products to the shelves. If they do this in some way that we support directly, and if we or a store (!) pays them to do it, say in frequent buyer card type discounts, we can actually discover exactly what purchases were disabled by Consumerium buying signal, and possibly (less likely) which ones were enabled by it.
- This article does not portray the Checkout Consumerium functionality as originally imagined