1. Field of the Invention
The present invention relates to the field of traceability of consumer goods and more particularly to extending traceability to bulk merchandise through the use of a code displayed in conjunction with the bulk merchandise.
2. Description of the Prior Art
Bulk merchandise, such as certain fresh produce, can be difficult to trace back to a source once a retailer has set it out for sale. Shipping containers can carry traceability labels, but these labels are often destroyed once the bulk merchandise is removed and set out for sale. While some bulk merchandise may be large enough to accommodate a label, such as watermelons, it is either not practical or, producers have been unwilling to employ labels big enough to include traceability information. Rather, these labels are typically limited to a product lookup (PLU) code, country of origin, and a GTIN (Global Trade Item Number, a product identifier standard established by GS1) which do not provide item or lot-level traceability. Factors weighing against the adoption of larger labels to provide lot-level traceability include the expense and the visual impact. For other bulk merchandise any labeling is impractical or impossible. In some instances, such as with garlic or potatoes, adhesive labels will not adhere well. In other instances, such as with bulk grains and nuts, or bulk shrimp, the individual units are too small to label.
The present invention provides methods of associating codes at the retail shelf (hereafter, shelf codes) to bulk merchandise so that the shelf code can be used by consumers, store associates, or in-store inspectors to access information about the bulk merchandise. In an exemplary method a shelf label including a shelf code is provided in proximity to a bin for bulk merchandise. The bin is stocked with bulk merchandise from a case, where the case bears a case label including a case traceability code. Additionally, the shelf code is dynamically associated to the case code, for example, by reading the case code and the shelf code with a mobile scanning device configured to make the association. In various embodiments the method further comprises associating additional information with the shelf code which in some embodiments includes querying a database using at least some of the case code. In some embodiments, the exemplary method further comprises associating the shelf code with the bin, for instance by scanning the shelf code and a bin identification located on or near the bin.
In various embodiments, providing the shelf label includes printing the shelf label on demand, including the shelf code. In other embodiments, providing the shelf label includes receiving a pre-printed label including the shelf code and optionally further printing upon the pre-printed label. In still other embodiments, providing the shelf label includes receiving a pre-printed sticker including the shelf code, printing a label, and adhering the sticker to the label.
In various embodiments the exemplary method further comprises providing an alert to the retailer. The alert can be displayed on a mobile scanning device to indicate a potential stocking error or recall, for instance. In various embodiments the exemplary method can also further comprise displaying information proximate to the bin, such as on a display. Such information can include lot-, item-, or brand- specific information about the bulk merchandise. The display can also invite consumers to scan the shelf code with a smart phone to access further information, coupons, promotions, recipes, and so forth.
In various embodiments the exemplary method further comprises rating the appearance, condition, merchandizing location, and other quality related attributes of the bulk merchandise in the bin and associating the rating data to the shelf code, which can thus be associated with the case(s) of product that were displayed at the location(s) related to the shelf code. In further embodiments the method further comprises removing bulk merchandise from the bin. In these embodiments the method can further comprise associating the identity of the person performing the action, the time and date of the removal, and/or the amount of removed merchandise to the shelf code using the mobile scanning device. The mobile scanning device can also be used to associate quality attributes, through the use of codes for example, to the removal event to indicate the condition of the merchandise that was removed.
The present invention also provides shelf labels. An exemplary shelf label comprises a bar code comprising either a unique code that is translated into a URL, or a URL, where the URL includes a domain and an extension, and the extension specifies a shelf code. Such shelf labels can also comprise a call to action and/or information about bulk merchandise such as a country or origin and a price. In various embodiments, the bar code is a QR code and the QR code encodes the URL in the form of www.example.com/shelf_code.
The present invention also provides an item of manufacture consisting of, or consisting essentially of, a roll of stickers on a backing. Here, each sticker comprises a QR code, and each QR code encodes a different URL including the same domain but with a different extension, where each extension comprises a different shelf code. Stickers from the roll can be removed as needed and placed on labels to create shelf labels.
The present invention also provides mobile scanning devices for use in conjunction with shelf codes in retail environments. An exemplary mobile scanning device is a hand-held device comprising a bar code reader, a touchscreen display, a communication interface, and logic. The logic can provide a number of modes of operations, for example, an association mode and a quality assurance mode. In the association mode the logic is configured to prompt a retailer to associate shelf codes with case codes. In this mode, after receiving a scanned shelf code from the bar code reader, the logic is configured to display on the touchscreen a prompt to scan a case code, then configured to receive a scanned case code, associate the scanned case code to the scanned shelf code, and communicate the shelf code in association with the case code through the communication interface.
In a quality assurance mode, the mobile scanning device can be used to collect information about the quality of merchandise. In this mode the logic can be configured to, responsive to reading a shelf code, display a grading scale on the touchscreen display, receive a selection from the grading scale, receive other relevant data about product condition, location, and appearance, and associate the selection(s) with the shelf code. Similarly, when stock is removed from the bin, the logic can also be configured to, responsive to reading a shelf code, display codes on the touchscreen display that can be associated with the removal event, where the codes represent possible conditions of the merchandise being removed. The logic can be further configured to allow the user to enter the quantity being removed. The logic then associates the quantity and/or the condition codes with the shelf code.
The present invention also provides methods for a third party to make lot-specific information available to consumers. An exemplary method comprises providing a plurality of shelf codes such as to a retailer. The method further comprises receiving, with a computing system, a first case code in association with lot-specific information such as from a producer of bulk merchandise. The method further comprises receiving a shelf code in association with the first case code, such as from a retailer, where the shelf code is one of the plurality of shelf codes, and creating a web site having a URL that includes the shelf code. In various embodiments, creating the web site includes populating a template with at least some of the lot-specific information. In various embodiments the method further comprises receiving the shelf code again from the retailer, but in association with a second case code. In these embodiments the method further comprises revising the web site having the URL including the shelf code. Here, revising the web site can comprise repopulating the template or populating a new template, for example.
In various embodiments the method further comprises serving the web site, signifying a trace event. Each trace event can comprise an exchange of information with a consumer and can include receiving a quality assessment and associating the quality assessment to the first case code. Other information that can be received from the consumer in a trace event includes demographic information. Each trace event can be time stamped and is linked to a known location since the shelf code is in a known location. The method can also comprise receiving quality assessments through other channels, such as from retailers. The method optionally further comprises analyzing accumulated information from consumers, retailers, and others to provide analytics to retailers and producers.
The present invention is directed to the placement of shelf codes provided in a machine readable format, such as on a QR code, where bulk merchandise is displayed for sale in a bin. The shelf code becomes the nexus in a rich exchange of information between consumers, retailers, and the producers and packers of the bulk merchandise. A third party may provide systems and services to support the exchange of information between the parties. According to various embodiments of the present invention, producers pack bulk merchandise into cases bearing case codes and associate both lot-specific and lot-independent information to the case codes before the cases enter the supply chain, and optionally at key points in the supply chain. An exemplary example of a case code is a label that is compliant with the Produce Traceability Initiative—which contains both lot-specific information and lot-independent information such as the product description. Retailers then associate the case codes to shelf codes when stocking bins.
Consumers can access information linked to the case code by scanning the shelf code, such as with a camera of a mobile phone or other mobile device, to learn about where their food is coming from, for example. Typically, the mobile device accesses the information by connecting to a web site or web service and this connection creates a communication channel between the web site and the consumer. The communication channel allows both the retailer and the producer to reach the consumer through the web site in various ways including sharing product and harvest/packing attributes, targeted advertising, providing recipes, providing coupons, and the like. The communication channel also provides a way to collect feedback from the consumer that can be useful to either or both of the producer and retailer. Thus, survey answers can provide demographic information about the customer, and quality ratings of the bulk merchandise can demonstrate how bulk merchandise for a particular producer is perceived at a particular time and location.
In the same way that a consumer can scan the shelf code and connect to a web site from a smart phone or other mobile device, quality assurance inspectors and others can also utilize the shelf codes to establish communication channels. In some embodiments, a mobile scanning device is specially designed for use in retail operations for quality assurance and other purposes. With such a scanning device a user scans the shelf code and enters quality assessments. The data is either aggregated for a period of time and then uploaded, else the data is uploaded continuously as acquired. While a shelf code displayed in a QR code can direct consumers using smart phones to a specific web site, a specially configured scanning device can optionally read the shelf code and connect to other portals. In some embodiments, the same mobile scanning device can provide quality assurance functions and also make the associations between shelf codes and case codes. In some embodiments, the same mobile scanning device can record the time at which the produce is on the shelf, and therefore calculate the age of the product derived from the lot-specific information.
Information gathered in connection with a shelf code reading is inherently linked to the location where the shelf code is in use. The location can be entered when an association is made between a case code and a shelf code, or the logic on the scanning device can derive the location by using location services such as GPS. Such information can also be time stamped. With respect to quality assessments, producers acquire two sets of data linked to a common case code. One set of data associated with the case code is lot-specific information collected at the beginning of the supply chain, such as harvest conditions, type of seed, fertilizer applications, and so forth. The other is set of data associated with the case code shows where the merchandise went, when it was displayed for sale at the destination, how it was perceived at the destination at specific times, how much was ultimately removed from stock by the retailer, and for what reasons. Retailers can also derive valuable insights from collected data about their customers' demographics, the customers' experiences in their stores, product placement within their stores, which producers' merchandise is most highly rated, and so forth. Also, by making product information more easily accessible to consumers, retailers enhance the shopping experience for their customers.
Initially, in a step 210, the retailer provides a shelf code 100 for a bin 105. For example, the shelf code 100 can be provided on a shelf label 110. As used herein, a bin refers to a defined location for displaying bulk merchandise for sale. In various embodiments the bin 105 is identified by a serial number or code. In some of these embodiments the bin 105 is associated with the shelf code 100 by a computing system 115 and the association is stored in a database 120 in a step 220. This association is useful in some contexts, but not essential. For example, if a bin identifier for the bin 105 is associated with the shelf code 100, an electronic display 125 for the bin 105 can be updated as the contents of the bin 105 subsequently change. It will be appreciated that computing system 115 can be, for example, a personal computer (PC) or server located at a store or at a central location for a chain of stores. The computing system 115 can also be controlled by a third-party that hosts a plurality of retailers.
The shelf code 100 can be a serial number or secure serial number that is then assigned to a retail store brand. An exemplary shelf code 100 comprises 16 characters. The shelf code 100 is provided in a machine-readable format such as a bar code. A suitable bar code format for the shelf code 100 is the two-dimensional Quick Response (QR) code that can be read using the combination of camera and software available on many smart phones. In some embodiments, a QR code encodes both the shelf code 100 and a Uniform Resource Locator (URL). As discussed in greater detail below, when read by a properly configured smart phone, the URL can direct an application operating on the smart phone to connect to a web site.
The shelf label 110 can be provided in a variety of different ways. In some embodiments, the retailer prints shelf labels 110 as needed. Shelf labels 110 can comprise cardstock or adhesive-backed paper, for instance. An example of a retailer-printed shelf label 110 is illustrated by shelf label 300 in
In other embodiments, the retailer receives a pre-printed label from a third-party supplier that generates the shelf codes 100. An exemplary pre-printed label 400 is illustrated in
In still other embodiments the retailer receives a pre-printed label from a third-party supplier where the label is an adhesive-backed sticker 500 as shown in
Optionally, rather than printing or pre-printing shelf codes 100 on shelf labels 110, a shelf label 110 can comprise an electronic display that displays an image of the shelf code 100. Further still, a shelf code 100 can be encoded as a radio frequency tag (e.g. RFID or Near-field RF) used in addition to, or in place of, a printed or electronically displayed shelf code 100.
Next, in a step 230, the retailer receives bulk merchandise and stocks the bin 105 with the bulk merchandise. As used herein, bulk merchandise refers primarily to items that lack packaging having lot-level traceability information such as lot-specific codes. Bulk merchandise is described herein primarily with respect to food items, but it should be appreciated that bulk merchandise is not limited to food and can include other items sold analogously, such as nails, shampoo, OTC pharmacueticals, small toys, and so forth. Bulk merchandise may include some packaging, such as the foam mesh sleeves used to protect pears, wrappers on individual pieces of candy, and the like, but such packaging lacks lot-level traceability information that can be used to trace such an item back through the supply chain. It will be understood that the system works equally well in delivering a shopper and an inspection experience for products that are packaged in materials such as bags and clamshells that do include lot-level traceability codes.
Bulk merchandise is received by the retailer in a case 130 that includes a case label 135. The case label 135, in turn, comprises a case code that includes a Stock-Keeping Unit (SKU) identifier, such as a GS1 GTIN (Global Trade Identification Number), and a lot number, or lot code. With respect to produce, the Produce Traceability Initiative (PTI) is an initiative designed to improve traceability through the entire supply chain from the source to the point of sale. Compliance with the Initiative requires that each case 130 carry a label 135 that includes a GTIN and a lot code. Accordingly, cases 130 of produce are commonly labeled at the source with a case label 135 that includes a case code that encompasses both lot-specific information (lot code) and lot-independent information (GTIN). In some embodiments the GTIN and lot code are provided using the GS1-128 barcode. Alternatively or additionally, case codes on case labels 135 may comprise a unique serial number that is linked to SKU and production information in a remote database. It will be appreciated that other forms of bulk merchandise, other than produce, can be similarly packed at the source into cases 130 provided with case labels 135 bearing case codes.
When stocking the bin 105 in step 230, the retailer associates the shelf code 100 to one or more case codes. The association can be made by scanning both the case code from the case label 135 and the shelf code 100 with a mobile scanning device 140, such as a hand-held bar code reader, where the mobile scanning device 140 includes logic configured to make the association. In instances where the contents of more than one case 130 are used to stock the bin 105, the retailer may scan the case code from the case label 135 of each, unless some case codes are duplicative. Thus, where more than one case 130 has the same case code, the case label 135 of only one case 130 need be read. Determining whether case codes on different cases 130 are the same or different can be simplified through the use of voice codes as described in U.S. patent application Ser. No. 12/689,949 filed on Jan. 19, 2010 and entitled “Voice Code with Primary and Secondary Digits” which is incorporated herein by reference.
In various embodiments the mobile scanning device 140 employs a laser to read bar codes, while in other embodiments the mobile scanning device 140 includes an optical camera and logic configured to capture an image of a bar code and process the image to interpret the bar code. The mobile scanning device, in some embodiments, is configured with a suitable RF reader for reading radio frequency tags.
In some embodiments, the mobile scanning device 140 includes logic configured to prompt the retailer to first read a shelf code 100, and then read the case codes from the case labels 135 of the cases 130 used to stock that bin 105. If there are different case labels (e.g. different brands, different packing configurations or different lot numbers) then either a representative label would be scanned or multiple different case labels may be associated with a single shelf code, indicating mixed product. The logic then associates the shelf code 100 with each case code scanned thereafter.
In various embodiments the logic of the mobile scanning device 140 is further configured to record a time stamp in association with the shelf code 100 representing the time the shelf code 100 was read. Similarly, in various embodiments the logic of the mobile scanning device 140 is further configured to determine a location of the mobile scanning device 140 at the time the shelf code 100 was read and associate that location with the shelf code 100, and optionally calculate the distance traveled from origin to store. Location information such as GPS or cellular triangulation coordinates can be later used to link the data to a particular retail store. Alternately, each mobile scanning device 140 can have a unique identification which is associated with the records created by associating shelf codes 100 with case codes. Mobile scanning devices 140 can also include logic configured to associate a shelf code 100 with a bin identification in step 220, and logic configured to perform other functions described below, such as assessing quality and removing outdated stock.
In some embodiments the mobile scanning device 140 includes a memory device and further includes logic configured to store shelf codes 100 in association with case codes to the memory device. At a subsequent time, accumulated shelf codes 100 and associated case codes and other data can be uploaded from the memory device of the mobile scanning device 140 to the computing system 115 to be stored in the database 120. Alternatively, the mobile scanning device 140 can include a wireless interface and the shelf code 100 and associated case codes and further data can be uploaded in real-time through a wireless connection. The database 120 optionally is hosted locally, hosted by a third-party, or hosted through a cloud computing application.
It will be appreciated that although the shelf code 100 is useful to extend traceability of bulk merchandise to beyond the case 130 itself, shelf codes 100 can also be used in conjunction with merchandise that is not bulk. For example, clamshells of strawberries can include labeling that is lot-specific, but the clamshells are still packed in cases 130 with case labels 135 bearing case codes. In step 230 the retailer can still associate the case code from the case label 135 with a shelf code 100 when stocking strawberries as described above, or by scanning the shelf code 100 and then scanning one of the traceability codes on one of the clamshells. Accordingly, although the invention is described primarily with respect to bulk merchandise, the invention is not limited in scope thereto.
In a step 240 additional information is associated with the shelf code 100, for example, by associating the additional information with the existing association between the shelf code 100 and the case code. The additional information can be stored in the database 120, or alternatively, the database 120 can store a pointer to a location where the information is located in a second database 145. In some embodiments, the computing system 115 queries the second database 145 using some or all of the case code to obtain the further information. The second database 145 can comprise a GS1 Data Pool, a database maintained by the producer or manufacturer, or a third party web service, for example.
Where the case code comprises a GTIN and lot code, either the GTIN alone, or both the GTIN and lot code can be used to query the second database 145 to obtain additional information. Where the bulk merchandise comprises produce, the GTIN in the second database 145 points to such lot-independent information as the grower/shipper name, product name, variety, growing method, country of origin, product size, and grade. Lot-specific information associated with the lot code can include harvest and/or packing date, ranch or farm name, crew number, temperature at time of harvest, and so forth. It will be appreciated that some information associated to a lot code may not be accessible to a query from the computing system 115. In those embodiments where the case code comprises a unique serial number, both lot-independent and lot-specific information could be available.
In an optional step 250, an alert can be provided to the retailer. For example, if the retailer attempts to associate two different case codes with a common shelf code 100, and the case codes are associated with different products (e.g., navel oranges and blood oranges), an appropriately configured mobile scanning device 140 can alert the retailer to the conflict. Here, the alert is generated by the mobile scanning device 140, but in other instances an alert can be generated by the computing device 115 and communicated to the retailer through the mobile scanning device 140. In these embodiments the computing device 115 and mobile scanning device 140 are configured to communicate wirelessly.
As an example of an alert situation, in a first instance of step 240 a first case code associated with a shelf code 100 for a bin 105 is further associated with a date (e.g., present date, harvest, or packing date), then, in a subsequent step 230 the bin 105 is again stocked and a second case code is scanned and associated with the shelf code 100. If, in the next instance of step 240 a more recent date becomes associated with the shelf code 100, the retailer can be prompted at that time to rotate the stock to bring the older bulk merchandise forward or to remove the older bulk merchandise. Here, the identification of a date change is performed by the computing device 115 and the alert is communicated to the mobile scanning device 140.
Similarly, the information associated with the shelf code in a step 240 could pertain to a product recall or withdrawal notice for the specific lot or lots associated with the case code read in the prior step 230. In such a situation the computing device 115, upon receiving the recall notice, can communicate an alert to the mobile scanning device 140 to the recall and to remove the affected bulk merchandise. In addition, an alert could later be sent to the retailer notifying the appropriate personnel that a recall notice was posted after the product was associated with a shelf code.
In an optional step 260, information obtained in step 240 can be displayed proximate to the bin 105, such as on the display 125. Such information can be lot-independent or lot-specific, or both. For example, if the bin 105 has been associated with the shelf code 100 in step 220, then in a later step 240 lot-independent information such as the type of produce, and lot-specific information such as the country of origin and/or the name and location of the farm from which it came, can be displayed. The information displayed proximate to a bin 105 can be automatically updated as often as the bin 105 is restocked. In one embodiment, the display 125 is operated by logic controlled by a third party and a message is sent to the third party logic each time a case code is associated with a shelf code 100. The third party logic can then determine when and where to best display the new information.
In an optional step 270 the retailer can perform QA checks that include reading the shelf code 100. For example, a mobile scanning device 140 configured for performing QA can read the shelf code 100, prompt the retailer to rate the quality of the produce in the bin 105, and then associate the rating to the shelf code 100. Since the shelf code 100 is associated to the case code, the rating becomes further associated with case code. Location and time can be further associated with the rating. Exemplary methods for linking quality assessments back to lot-specific product data are provided in U.S. patent application Ser. No. 12/908,667 filed on Oct. 20, 2010 and entitled “Methods for Correlating First Mile and Last Mile Product Data” which is incorporated herein by reference.
In an optional step 280 the retailer can remove stock from the bin 105, and in this step, the shelf code 100 is read by the mobile scanning device 140 and associated with the removal. In some embodiments of the mobile scanning device 140, the device is configured to make the association by associating the shelf code 100 with a time stamp and a flag signifying removal, for instance. Once communicated to the computing device 115, the computing device 115 associates the removal with the case code(s) most recently associated with the shelf code 100. Additionally, the mobile scanning device 140 is configured, in some embodiments, to prompt the retailer to enter further information to be associated with the removal. Such information can include the quantity removed, such as a number of pieces, and a problem code that signifies the reason for the removal, such as damaged product, mold, and product aged out.
In an optional step 290, the retailer can offer incentives to consumers based on information associated with the shelf code 100 from step 230 or 240. For example, in step 230 the shelf code 100 is associated with a case code and further associated with a time stamp. After a threshold period of time the computing system 115 can make a coupon available to consumers, where the coupon is good for a limited time. A consumer that scans the shelf code 100 with a smart phone could receive the coupon, as described further below. In some embodiments, the computing system 115 is configured to provide a message on the display 125 directed consumers to scan the shelf code 100 to receive a discount coupon.
In other embodiments, rather than triggering the incentive in step 290 based on an elapsed time in the bin 105, information associated with the shelf code 100 in step 240, such as harvest date provides a basis for determining when to offer an incentive to consumers. For example, the threshold period of time can be a set number of hours or days after harvest. Further, incentives are not limited to coupons, and can include usage suggestions, for example. Thus, after a threshold period of time the computing system 115 can display a message such as “Use These Apples as a Quick Dessert Tonight—Scan this Shelf Code to Learn How” and scanning the shelf code 100 would provide a recipe to the smartphone.
Independently, in a step 620, the third party receives from a producer a case code in association with lot-specific information for bulk merchandise. The third party creates and stores a record of the case code in association with the lot-specific information. The case code and lot-specific information can be uploaded to a computing system and stored in a database such a database 145. Step 620 can optionally also comprise receiving, in association with the case code, lot-independent information such as a GTIN which may also be stored in the record. For the purposes of explaining the method 600 only one case code is considered, but it will be appreciated that in practice a plurality of case codes and associated information are provided over time to the computing system as new lots of bulk merchandise are packaged for distribution.
In a step 630 the third party receives from the retailer a shelf code 100 in association with the case code, where the shelf code 100 is one of the plurality of shelf codes 100 provided in step 610. This indicates to the third party that the shelf code 100 has been placed in service in conjunction with bulk merchandise previously associated by the producer with the case code. Accordingly, the third party stores the shelf code 100 in association with the case code, for example, by adding the shelf code 100 to the record created in step 620. Other shelf codes 100 associated with the same case code and received from the same or other retailers can also be associated with the same record created in step 620. In further embodiments, the third party receives from the retailer additional information associated with the shelf code 100, such as a price and location, which can be added to the record created in step 620 or can be maintained in a separate record for the shelf code 100. As noted previously, receiving information associated with case codes from producers in step 620 and associated with shelf codes 100 from retailers in step 630 can simply comprise receiving pointers to locations where such information is stored in other databases.
Once a shelf code 100 has been placed into service by the retailer, in a step 640 the third party creates a web site linked to a URL that includes the shelf code 100 such as www.example.com/shelf_code. Creating the web site can comprise populating a template with lot-independent and lot-specific information associated with the case code. In some embodiments, an appropriate template for the web site is selected based on the GTIN associated with the case code. In various embodiments the web site can also be populated with other information associated with the shelf code 100 by the retailer. In various embodiments the web site can also be configured to provide retailer-specific content and/or links to web sites maintained by the retailer.
It will be appreciated that step 630 can be repeated multiple times as a bin 105 is repeatedly stocked. With each iteration the step 640 can comprise recreating or updating the web site. If the retailer assigns the bin 105 to different bulk merchandise, for example, and associates the existing shelf code 100 to a new case code, the third party can retain the record already created in step 620, but flag the shelf code 100 as no longer valid. Thus, the same shelf code 100 can be associated with multiple case codes over time, but only the most recently associated case code would be tied to the web site.
In a step 650, the third party exchanges information with a consumer through the web site. Step 650 includes receiving a request for the web site and serving the web site to the consumer, providing the consumer with lot-independent and lot-specific information associated with the case code and optionally associated with the shelf code 100. In various embodiments step 650 additionally comprises receiving information in the form of a quality assessment from the consumer and storing the quality assessment in the record created in step 620. The quality assessment can also be associated with a time stamp that reflects the time that the web site was accessed. Methods for providing quality assessments with a mobile device are described in greater detail in U.S. patent application Ser. No. 12/877,467 filed on Sep. 8, 2010 and entitled “Lot Identification Codes for Packaging” which is incorporated herein by reference.
The exchange of information in step 650 can additionally comprise serving retailer or producer specific content such as in-store specials and promotions, games and contests, and so forth. The exchange of information in step 650 can additionally comprise receiving content from consumers such as comments that can be posted to a comments page for other consumers to view. Such consumer content can also be tied to social media web sites so that a consumer can share an opinion on merchandise with others.
In a step 660 analytic results are provided to the retailer, while in a step 670 analytic results are provided to the producer. Such analytics typically depend on the collection of statistically significant amounts of information over time. Analytic results provided to the retailer can include which products' shelf codes 100 were scanned by consumers most frequently, which incentives generated the greatest responses, which producers' merchandise was most highly rated, and the like. Analytic results provided to the producer can include how long does it take to get merchandise to market and how the merchandise is rated as functions of time and distance from the point of origin of the supply chain.
Returning to step 650 of
The computing system 710 can be a server, for example. In some embodiments, the computing system 710 is the same as computing system 115, while in other embodiments they are separate systems but communicate with one or more of the same databases 120, 145. The computing system 710 can record each trace event as a record including the case code, a time stamp, and optionally a location. Other demographic or personal information (such as a loyalty card number, gender or age) can also be associated with the trace event, if available. This information is valuable for understanding what products appeal to which consumers, which products generate the most curiosity amongst various demographics, and the like.
Logic described herein can comprise, for example, hardware, such as application-specific integrated circuits (ASICs), specifically designed to perform the particular described functions. Logic can also comprise firmware residing, for instance, in read only memory (ROM) or flash memory, where the firmware is programmed to perform the particular described functions. Logic can also comprise a microprocessor capable of executing software residing in a memory, for example, in random access memory (RAM), where the computer instructions embodied in the software, when executed by the microprocessor perform the particular described functions. Any combination of two or more of hardware, firmware, and software can also comprise logic. Hardware, firmware, and/or software can be embodied in hand-held devices such as smart phones running third-party applications, for example. Logic comprising hardware, firmware, and/or software can also be embodied in various types of computing systems such as servers and personal computers. It will be appreciated that such computing systems, when configured to follow specific logic embodied in their circuits or programming instructions, or both, constitute specific machines.
In the foregoing specification, the invention is described with reference to specific embodiments thereof, but those skilled in the art will recognize that the invention is not limited thereto. Various features and aspects of the above-described invention may be used individually or jointly. Further, the invention can be utilized in any number of environments and applications beyond those described herein without departing from the broader spirit and scope of the specification. The specification and drawings are, accordingly, to be regarded as illustrative rather than restrictive. It will be recognized that the terms “comprising,” “including,” and “having,” as used herein, are specifically intended to be read as open-ended terms of art.
This application is a continuation of U.S. Non-Provisional Patent Application No. 13/034,208 filed on Feb. 24, 2011 now U.S. Pat. No. 8,210,430 and entitled “Methods for Assigning Traceability Information to and Retrieving Traceability Information from a Store Shelf” which is incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
3329181 | Buss | Jul 1967 | A |
4385482 | Booth | May 1983 | A |
4526404 | Vazquez | Jul 1985 | A |
4544590 | Egan | Oct 1985 | A |
4832204 | Handy et al. | May 1989 | A |
4846504 | MacGregor et al. | Jul 1989 | A |
5136826 | Carson et al. | Aug 1992 | A |
5271642 | Jahier et al. | Dec 1993 | A |
5343529 | Goldfine et al. | Aug 1994 | A |
5360628 | Butland | Nov 1994 | A |
5361904 | Kapec et al. | Nov 1994 | A |
5478990 | Montanari et al. | Dec 1995 | A |
5486686 | Zydbel, Jr. et al. | Jan 1996 | A |
5561970 | Edie et al. | Oct 1996 | A |
5569317 | Sarada et al. | Oct 1996 | A |
5592561 | Moore | Jan 1997 | A |
5611948 | Hawkins | Mar 1997 | A |
5619416 | Kosarew | Apr 1997 | A |
5668803 | Tymes et al. | Sep 1997 | A |
5695071 | Ross et al. | Dec 1997 | A |
5768384 | Berson | Jun 1998 | A |
5793030 | Kelly, Jr. | Aug 1998 | A |
5895073 | Moore | Apr 1999 | A |
5917925 | Moore | Jun 1999 | A |
6005960 | Moore | Dec 1999 | A |
6041929 | Brunner et al. | Mar 2000 | A |
6069955 | Coppersmith et al. | May 2000 | A |
6111953 | Walker et al. | Aug 2000 | A |
6203069 | Outwater et al. | Mar 2001 | B1 |
6211789 | Oldham et al. | Apr 2001 | B1 |
6212638 | Lee et al. | Apr 2001 | B1 |
6226619 | Halperin et al. | May 2001 | B1 |
6231435 | Pilger | May 2001 | B1 |
6246778 | Moore | Jun 2001 | B1 |
6269342 | Brick et al. | Jul 2001 | B1 |
6297508 | Barmore et al. | Oct 2001 | B1 |
6308165 | Gilham | Oct 2001 | B1 |
6314337 | Marcum | Nov 2001 | B1 |
6329920 | Morrison et al. | Dec 2001 | B1 |
6342839 | Curkendall et al. | Jan 2002 | B1 |
6346885 | Curkendall | Feb 2002 | B1 |
6349292 | Sutherland et al. | Feb 2002 | B1 |
6361079 | Kirkman | Mar 2002 | B1 |
6363483 | Keshav | Mar 2002 | B1 |
6364990 | Grosskopf et al. | Apr 2002 | B1 |
6398106 | Ulvr et al. | Jun 2002 | B1 |
6409082 | Davis et al. | Jun 2002 | B1 |
6428640 | Stevens et al. | Aug 2002 | B1 |
6442276 | Doljack | Aug 2002 | B1 |
6456729 | Moore | Sep 2002 | B1 |
6473739 | Showghi et al. | Oct 2002 | B1 |
6536672 | Outwater | Mar 2003 | B1 |
6547137 | Begelfer et al. | Apr 2003 | B1 |
6591252 | Young | Jul 2003 | B1 |
6612494 | Outwater | Sep 2003 | B1 |
6664897 | Pape et al. | Dec 2003 | B2 |
6680783 | Pierce et al. | Jan 2004 | B1 |
6766324 | Carlson et al. | Jul 2004 | B2 |
6788800 | Carr et al. | Sep 2004 | B1 |
6796504 | Robinson | Sep 2004 | B2 |
6805926 | Cole et al. | Oct 2004 | B2 |
6806478 | Hatfield | Oct 2004 | B1 |
6808574 | Stevens et al. | Oct 2004 | B1 |
6859672 | Roberts et al. | Feb 2005 | B2 |
6974298 | Tanaka | Dec 2005 | B2 |
6991261 | Dronzek, Jr. et al. | Jan 2006 | B2 |
6995675 | Curkendall et al. | Feb 2006 | B2 |
6996543 | Coppersmith et al. | Feb 2006 | B1 |
7009723 | Bartholet et al. | Mar 2006 | B1 |
7013286 | Aggarwal et al. | Mar 2006 | B1 |
7040532 | Taylor et al. | May 2006 | B1 |
7043442 | Levy et al. | May 2006 | B2 |
7104450 | Khovaylo | Sep 2006 | B2 |
7152040 | Hawthorne et al. | Dec 2006 | B1 |
7207481 | Barenburg et al. | Apr 2007 | B2 |
7211163 | Kennedy | May 2007 | B2 |
7222791 | Heilper et al. | May 2007 | B2 |
7261235 | Barenburg et al. | Aug 2007 | B2 |
7277601 | Zorab et al. | Oct 2007 | B2 |
7283630 | Doljack | Oct 2007 | B1 |
7295114 | Drzaic et al. | Nov 2007 | B1 |
7321310 | Curkendall et al. | Jan 2008 | B2 |
7412461 | Sholl et al. | Aug 2008 | B2 |
7519825 | Geoffrey | Apr 2009 | B2 |
7614546 | Grant et al. | Nov 2009 | B2 |
7686513 | Knoerzer et al. | Mar 2010 | B2 |
7705735 | Pape et al. | Apr 2010 | B2 |
7714729 | Pape et al. | May 2010 | B2 |
7766240 | Grant | Aug 2010 | B1 |
7770783 | Grant et al. | Aug 2010 | B2 |
7810726 | de la Huerga | Oct 2010 | B2 |
7823768 | Self et al. | Nov 2010 | B2 |
7827058 | Mortimer | Nov 2010 | B2 |
7909239 | Grant et al. | Mar 2011 | B2 |
7992772 | Grant et al. | Aug 2011 | B2 |
8019662 | Lucas | Sep 2011 | B2 |
8108309 | Tan | Jan 2012 | B2 |
8140852 | Guenter et al. | Mar 2012 | B2 |
8152063 | Grant et al. | Apr 2012 | B1 |
8155313 | Grant | Apr 2012 | B2 |
8196827 | Grant | Jun 2012 | B1 |
8210430 | Grant et al. | Jul 2012 | B1 |
8240564 | Grant et al. | Aug 2012 | B2 |
8245927 | Grant et al. | Aug 2012 | B2 |
8261973 | Grant et al. | Sep 2012 | B2 |
20010054005 | Hook et al. | Dec 2001 | A1 |
20010056359 | Abreu | Dec 2001 | A1 |
20020004767 | Okamoto et al. | Jan 2002 | A1 |
20020131442 | Garg et al. | Sep 2002 | A1 |
20020158765 | Pape et al. | Oct 2002 | A1 |
20020178363 | Ambrogio et al. | Nov 2002 | A1 |
20030019186 | Hakansson | Jan 2003 | A1 |
20030070520 | Gawazawa | Apr 2003 | A1 |
20030080191 | Lubow et al. | May 2003 | A1 |
20030089078 | Christina | May 2003 | A1 |
20030164934 | Nishi et al. | Sep 2003 | A1 |
20030177025 | Curkendall et al. | Sep 2003 | A1 |
20030177095 | Zorab et al. | Sep 2003 | A1 |
20030185948 | Garwood | Oct 2003 | A1 |
20030221108 | Rupp | Nov 2003 | A1 |
20040065053 | Rice et al. | Apr 2004 | A1 |
20040159527 | Williamson | Aug 2004 | A1 |
20040167829 | Fujita | Aug 2004 | A1 |
20040200892 | Curkendall et al. | Oct 2004 | A1 |
20040205343 | Forth et al. | Oct 2004 | A1 |
20040230796 | Lundvall et al. | Nov 2004 | A1 |
20050004682 | Gaddis et al. | Jan 2005 | A1 |
20050038756 | Nagel | Feb 2005 | A1 |
20050097054 | Dillon | May 2005 | A1 |
20050108044 | Koster | May 2005 | A1 |
20050182695 | Lubow et al. | Aug 2005 | A1 |
20050206586 | Capurso et al. | Sep 2005 | A1 |
20050247778 | Roberts | Nov 2005 | A1 |
20050251449 | Pape et al. | Nov 2005 | A1 |
20050288947 | Mallonee et al. | Dec 2005 | A1 |
20060004907 | Pape et al. | Jan 2006 | A1 |
20060022059 | Juds | Feb 2006 | A1 |
20060054682 | de la Huerga et al. | Mar 2006 | A1 |
20060100964 | Wilde et al. | May 2006 | A1 |
20060111845 | Forbis et al. | May 2006 | A1 |
20060161443 | Rollins | Jul 2006 | A1 |
20060180661 | Grant et al. | Aug 2006 | A1 |
20060187048 | Curkendall et al. | Aug 2006 | A1 |
20060259182 | Mantell | Nov 2006 | A1 |
20060260495 | Siedlaczek | Nov 2006 | A1 |
20060266827 | Hamilton | Nov 2006 | A1 |
20060289654 | Robinson et al. | Dec 2006 | A1 |
20070001006 | Schuessler et al. | Jan 2007 | A1 |
20070051362 | Sullivan et al. | Mar 2007 | A1 |
20070119954 | Barenburg et al. | May 2007 | A1 |
20070119955 | Barenburg et al. | May 2007 | A1 |
20070170240 | Grant et al. | Jul 2007 | A1 |
20070175974 | Self et al. | Aug 2007 | A1 |
20070203724 | Farmer et al. | Aug 2007 | A1 |
20070203818 | Farmer et al. | Aug 2007 | A1 |
20070205258 | Self et al. | Sep 2007 | A1 |
20070219916 | Lucas | Sep 2007 | A1 |
20080011841 | Self et al. | Jan 2008 | A1 |
20080011843 | Barenburg et al. | Jan 2008 | A1 |
20080023472 | Brandt | Jan 2008 | A1 |
20080030348 | Pape et al. | Feb 2008 | A1 |
20080046263 | Sager et al. | Feb 2008 | A1 |
20080143094 | Goetz | Jun 2008 | A1 |
20080178197 | Pape et al. | Jul 2008 | A1 |
20080215484 | Oldham et al. | Sep 2008 | A1 |
20090242631 | Wishnatzki et al. | Oct 2009 | A1 |
20100106660 | Farmer et al. | Apr 2010 | A1 |
20100145730 | Abreu | Jun 2010 | A1 |
20110098026 | Uland | Apr 2011 | A1 |
20120037697 | Boone et al. | Feb 2012 | A1 |
Number | Date | Country |
---|---|---|
1350265 | May 2002 | CN |
2000011114 | Jan 2000 | JP |
2002140449 | May 2002 | JP |
03007252 | Jan 2003 | WO |
2006084090 | Aug 2006 | WO |
2007140018 | Jun 2007 | WO |
Entry |
---|
PCT/US08/75626 International Search Report and Written Opinion, Nov. 26, 2008. |
Secure Symbology, Inc. Business Overview, May 2008. |
Paul Chang, IBM Industry Forum 2010, Mexico Industry Event, 2010. |
PCT/US06/03768 International Search Report and Written Opinion, Jun. 12, 2008. |
“CRC: Implementation,” http://www.relisoft.com/science/CrcNaive.html, 2006. |
Yoichi Shibata et al., “Mechanism-based PKI,” Computer System Symposium 2003, vol. 2003 (15), pp. 181-186, (1998). |
Ilic, A. et al., “The Value of Sensor Information for the Management of Perishable Goods—A Simulation Study” (Jun. 4, 2008), http://www.im.ethz.ch/publications/ilic—voi—perishables—perceived—quality—0608.pdf. |
Roberti, M., “RFID Will Help Keep Perishables Fresh” (Aug. 3, 2005), RFID Journal, www.rfidjournal.com/article/view/1775. |
“Top10Produce—Fresh Face of Farming,” 2010. |
Number | Date | Country | |
---|---|---|---|
Parent | 13034208 | Feb 2011 | US |
Child | 13471181 | US |