I applaud your effort, and actually the fact that you've gotten as far with it as you have. I'm impressed.

But your strategy is flawed. Point of Sale has to go as smoothly as possible. Any slowdown at POS will cost you sales. There is no way that you can take a controlled picture of sufficient quality to guarantee image recognition accuracy faster than you could jot down a six digit number, and even worse, your salespeople or clerks aren't going to be even half as careful as you. This is especially true when they've got a line of frustrated customers at the counter, impatient over the notion that everything they buy has to be photographed carefully first. POS slow-downs are one of the biggest No No's in the retail environment.

If barcoding is too expensive to implement, at least just generate sku's. Printing sku labels isn't terribly difficult, and that will make inventory tracking simple, efficient, and in keeping with what clients and clerks are accustomed to.

That doesn't mean the project doesn't interest me. It really does. But the purpose for which you're applying the project is not ideal, imho.


Dave

In reply to Re: Help improving image recognition application to track store purchases. by davido
in thread Help improving image recognition application to track store purchases. by zli034

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.