HK1148099A - Device and method for operating an interactive dispenser - Google Patents

Description

Apparatus and method for operating an interactive dispenser

Trade mark

COCA-Is a registered trademark of Coca-Cola corporation, Atlanta, Georgia, USA. Other names, symbols, patterns or logos used herein may be registered trademarks, trademarks or product names of the Coca-Cola company or other companies.

Technical Field

The present invention relates to product dispensers, and more particularly, to systems and methods for facilitating consumer-dispenser interaction.

Background

Conventional beverage dispensers may fill the beverage by combining syrup, sweetener, and/or water. Is composed ofResulting in a limited variety of beverage options and different types of syrups available. This typically results in only a limited number of branded and non-branded beverage choices being offered. By way of example, a single prior art dispenser using several syrups may offer limited options: COCA-COLA^TM、DIETCOCA-COLA^TM、SPRITE^TMAnd several other brands or non-branded beverage choices.

One problem with these types of conventional beverage dispensers is that only a limited number of beverages can be provided. Thus, conventional beverage dispensers may be limited in their ability to provide consumers with the beverage they desire. In this regard, consumers desire a broader menu of beverage selections and the ability to customize their beverages. Studies have shown that they desire even more beverage variation from traditional brands of beverages. For example, COCA-COLA is provided^TMCOCA-COLA containing lime^TM、CHERRYCOCA-COLA^TM、VANILLA COCA-COLA^TMAnd many other types of COCA-COLA^TMThe beverage changes. For a single beverage brand such as COCA-COLA^TMIt is impractical to provide all of the possible variations in conventional beverage dispensers, in part because of the limited capacity and selection capabilities of conventional beverage dispensers. They are unable to offer the consumer a full range of options that they want, i.e., offer all types of branded and non-branded beverages.

Summary of The Invention

Some or all of the above needs and/or problems are addressed by embodiments of the present invention. Certain embodiments of the invention may include systems and methods for facilitating consumer-dispenser interactions. In one embodiment, a product dispenser is provided. The product dispenser may include a user interface operable to receive consumer input and provide product selection information. Additionally, the product dispenser may include a reader configured to obtain identification information associated with a consumer. The product dispenser may include a controller in communication with the reader and the user interface and operable to execute a set of instructions operable to receive identification information associated with a consumer from the reader. The controller is further operable to execute a set of instructions operable to retrieve consumer information based at least in part on the identification information, and provide product selection information at the user interface based at least in part on the consumer information.

In another embodiment, a method for operating a product dispenser is provided. The method may include receiving identification information associated with a consumer. Additionally, the method may include retrieving consumer information based at least in part on the identification information. Further, the method may include providing product selection information at a user interface associated with the product dispenser based at least in part on the consumer information.

Further, a method for operating a product dispenser may be provided. The method may include receiving identification information associated with a consumer. Additionally, the method may include retrieving consumer information based at least in part on the identification information. Further, the method may include customizing product selection information at a user interface associated with the product dispenser based at least in part on the consumer information. Further, the method may include updating the consumer information based at least in part on the selected product.

Additional systems, methods, distributors, features and aspects may be realized through the techniques of different embodiments of the present invention. Other embodiments and aspects of the invention are described in detail herein and are considered a part of the claimed invention. Other aspects and features may be understood with reference to the detailed description and the accompanying drawings.

Brief Description of Drawings

The subject matter which is regarded as the invention is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The above and other objects, features and aspects of the present invention are apparent from the following detailed description taken in conjunction with the accompanying drawings, in which:

FIG. 1 illustrates an example system including a product dispenser and associated network according to one embodiment of this disclosure.

Fig. 2 illustrates an example of a consumer diet network (consistency network) according to an embodiment of the present invention.

FIG. 3 illustrates one embodiment of an enhanced view graphical user interface according to one embodiment of the present invention.

FIG. 4 illustrates one embodiment of a classic view graphical user interface according to one embodiment of the present invention.

FIG. 5 illustrates one embodiment of a method of transitioning between an enhanced product dispenser consumer interface and a classic product dispenser consumer interface according to one embodiment of the invention.

FIG. 6 illustrates one embodiment of a method of transitioning between an enhanced product dispenser consumer interface and a classic product dispenser consumer interface according to one embodiment of the invention.

Fig. 7-9 illustrate an embodiment of a method of performing differential pricing (differential pricing) according to an embodiment of the invention.

FIG. 10 illustrates one embodiment of a method of interacting a product dispenser with at least one data processing device in accordance with one embodiment of the present invention.

FIG. 11 illustrates one example of a method of receiving different types and/or categories of loyalty awards based at least in part on whether a consumer has dispensed a product, according to one embodiment of the invention.

Fig. 12-14 illustrate an example of a method of executing a frequent drinks program (frequency drinks program) to obtain free drinks according to an embodiment of the present invention.

15-16 illustrate an example of a method of using consumer preferences to customize user interface skins (skinning) and display digital content related to consumer interests in accordance with one embodiment of the present invention.

FIG. 17 illustrates one example of a method of a consumer providing encoded media with a recipe profile to effect a selection of a product or beverage according to one embodiment of the invention.

FIG. 18 illustrates one example of a method of using a consumer specific code to store and retrieve a list of products or beverages according to one embodiment of the present invention.

Figure 19 illustrates one embodiment of a method for enabling a consumer to attempt each of a plurality of product or beverage formulations.

The detailed description explains various embodiments of the invention, together with aspects and features, by way of example with reference to the drawings.

Detailed description of embodiments of the invention

As used herein, the terms "beverage dispenser," "product dispenser," "beverage product dispenser," "dispenser device," and "dispenser" refer to an apparatus, can, bottle, or container that dispenses a product, such as a beverage.

As used herein, the terms "product" and "beverage," and their plural forms, are used synonymously, and embodiments of the invention should not be limited in scope to the use of any one of the terms.

Turning now to more detailed portions of the drawings, an exemplary system 100 of a product dispenser according to one embodiment of the present invention is shown in FIG. 1. The present exemplary system, such as 100, may operate in a networked computer environment including at least one network in communication with a product dispenser. For example, in fig. 1, a product dispenser such as 102A is shown in communication with a communication network such as 104. In this embodiment, at least one product dispenser, such as 102A, may be connected to a consumer, customer, or other user. Other exemplary environments or systems of product dispensers according to one embodiment of the invention may include non-network configurations.

An exemplary product dispenser, such as 102A shown in fig. 1, may be a client-type device. Each product dispenser, such as 102A-102N, may be a computer or processor-based device capable of communicating with a communication network, such as 104, via a signal, such as a wireless frequency signal or a direct wired communication signal.

Each product dispenser, such as 102A, may include a processor or controller 106, an identification reader/scanner device 106A, a composition matrix 108, a computer readable medium, such as Random Access Memory (RAM)110, coupled to the processor or controller 106, and an input/output device, such as a display device 112. A processor or controller, such as 106, may execute computer-executable program instructions stored in a memory, such as 110. The computer-executable program instructions stored in the memory, such as 110, may include any number of modular applications, such as a consumer interaction engine or modules, such as 114. A consumer interaction engine or module, such as 114, may be adapted to implement various methods for consumer-dispenser interaction. Additionally, a consumer interaction engine or module, such as 114, may be adapted to receive one or more signals from one or more consumers, remote and/or local servers or data processing resources, and client type devices or wireless communication devices. Other examples of the functionality and aspects of embodiments of the consumer interaction engine or module, such as 114, are described below.

The identification reader/scanner device 106A shown in fig. 1 may be in communication with the controller 106 and may receive or otherwise obtain identification information from any number of devices or apparatuses associated with a consumer. For example, the identification reader/scanner device such as 106A may include machine-readable code technology such as bar codes, or may include any wireless communication technology such as RFID, reflected light frequency, optical, and the like.

As shown in fig. 1, a processor or controller, such as 106, may communicate with the component matrices, such as 108, to control, monitor and track the addition, flow and removal of some or all of the components to or from the matrices, such as 108. For example, the ingredient matrix may be a series of containers or accessories capable of holding or mounting to respective product ingredient packages or other product ingredient supplies. For example, product component packages such as 116A may be made as liquid pouches held in plastic ridged containers (plastic ridge containers) to allow insertion into a matrix of components such as 108. When inserted into the ingredient matrix such as 108, the bag such as 116A or pouch may be pierced by at least one associated fitment that allows the liquid in the bag such as 116A or pouch to be pumped or otherwise metered by the controller such as 106 or the matrix such as 108 and associated equipment in precise proportions to form the desired product such as a beverage. In one embodiment, one or more product component packages, such as 116A-116Q, may be inserted into a component matrix, such as 108. The component matrix such as 108 in this embodiment may hold some or all of the product component packages such as 116A-116Q. In one embodiment, one or more product packages, such as 116O, 116P, 116Q, may be supplied directly rather than in the form of a package. For example, a product package such as 116O may be a continuous supply of soda provided from a soda water source; product packages, such as 116P, may be sweeteners provided from sweetener sources, such as non-nutritive sweeteners (NNS) or High Fructose Corn Syrup (HFCS); product package, such as 116Q, may be a continuous supply of water from a faucet, purified or distilled water source. In any embodiment, the ingredients, components, or product additives may be in the form of pouches, or may be in other configurations suitable for access to the matrix of ingredients, such as 108.

In the embodiment shown in FIG. 1, a product dispenser such as 102A having a matrix of components such as 108 may include one or more machine code readers such as 118A-118Q that utilize machine code technology such as bar codes, RFID, reflected light frequencies, optical, and the like. In one embodiment, at least one machine readable code reader, such as 118A-118Q, may be associated with a location associated with an ingredient matrix, such as 108, wherein some or all of the product ingredient packages, such as 116A-116Q, may be scanned, read, or otherwise identified prior to insertion into or connection with the ingredient matrix, such as 108. In this regard, a processor or controller, such as 106, may receive or obtain information regarding some or all of the product component packages, such as 116A-116Q, and use this information to identify an optimal or other desired location within a component matrix, such as 108, within the component matrix, such as 108, to position the product component package, such as 116A. For example, data from a product component package, such as 116A, may be read, scanned, or identified from a serial number or identification code associated with the product component package, such as 116A. This data may be used alone or in association with information previously stored in at least one database described below, such as 128A-128C, or in association with data otherwise available or stored by a data processing resource or server described below, such as 126, which may identify one or more components associated with a product component package, such as 116A. In another embodiment, the data from the product component package, such as 116A, may be a component code or identifier, and may be used alone or associated with information previously stored in a database, such as 128A-128C, or with data otherwise available or stored by a data processing resource or server, such as 126, that identifies one or more components associated with the product component package, such as 116A.

In the embodiment shown in FIG. 1, a product dispenser such as 102A having an ingredient matrix such as 108 may include one or more pumps and/or valves such as 120 and 122, respectively, and a nozzle such as 124. In this embodiment, each of the pumps, such as 120, and valves, such as 122, may be controlled by the product dispenser, such as 102A. For example, a processor or controller such as 106 may be in communication with some or all of a pump such as 120 and a valve such as 122. In this regard, some or all of the pumps, such as 120, and/or valves, such as 122, may be selectively operated by a processor or controller, such as 106, to pump, meter, or otherwise obtain respective products or ingredients from certain product ingredient packages, such as 116A-116Q, to dispense a consumable product or beverage.

In one embodiment, an ingredient matrix such as 108 may have a plurality of product ingredient packages such as 116A-116Q inserted into the ingredient matrix such as 108, where each package may contain different or unique ingredients. The varying proportions of ingredients from some or all of the product ingredient packages, such as 116A-116Q, may be selectively combined to form various types of products, such as beverages, by one or more commands or instructions from a processor or controller, such as 106, to one or more pumps, such as 120, and/or valves, such as 122, associated with the ingredient matrix, such as 108. Exemplary ingredients may include, but are not limited to: seasonings, concentrates, syrups. Sweetener, water, soda, lime, vanilla, CHERRY, and any component part of a branded or non-branded beverage, such as CHERRY COCA-COLA^TM、VANILLA COCA-COLA^TM、COCA-COLA^TM、DIET COCA-COLA^TMAnd FANTA^TM。

In one embodiment, one or more product component packs such as 116A-116Q may contain a component called "pungency" that may restrict its position within a matrix of components such as 108. The spicy type ingredient may be relatively strong such that once the spicy ingredient is pumped or otherwise drawn through a particular portion of the product dispenser, such as 102A, any associated pathway, such as a conduit in the product dispenser, such as 102A, through the dispenser, such as 102A, may be permanently flavored, and any subsequent ingredients or liquids pumped or drawn through that pathway or conduit may be tainted with the flavor of the spicy type ingredient. Thus, once a spicy type ingredient is used in the ingredient matrix such as 108, the associated processor or controller such as 106 may track or otherwise store information to control or limit the replacement and/or addition of other spicy ingredients to certain locations of the ingredient matrix such as 108 to avoid mixing spicy type ingredients or cross-flavoring non-spicy ingredients to maintain product or beverage quality.

In another embodiment, one or more product component packages, such as 116A-116Q, may require shaking to keep the relevant components sufficiently mixed. In this case, the location of the component in the component matrix such as 108 may be limited to locations within the component matrix such as 108 that may be panned as may be needed and/or desired in a particular implementation.

In another embodiment, ingredients from one or more product ingredient packages, such as 116A-116Q, may be dispensed through an antimicrobial tubing and/or dispenser piece. These ingredients may include, but are not limited to: milk, dairy, soy, and/or other types and kinds of product components. In such cases, the location of the ingredients in the ingredient matrix such as 108 may be limited to locations within the ingredient matrix such as 108 that utilize appropriate antimicrobial tubing and/or dispenser components as may be needed and/or desired in particular embodiments.

In another embodiment, a one-to-one relationship may be established between a particular product ingredient package, such as 116A, and at least one pump and/or valve, such as 120 and/or 122, respectively. In some cases, utilizing more than one pump and/or valve for a single product component package, such as 116A, a relatively high volume of the component may be drawn from the package, such as 116A, in a relatively short period of time. For example, a product component package containing a sweetener, such as sweetener 116P, may utilize more than one pump and/or valve to draw a relatively high volume of the component from the package 116P in a relatively short period of time.

Returning to FIG. 1, any number of other product dispensers, such as 102A-102N, may also be in communication with a network, such as 104. In one embodiment, a communication network, such as 104 shown in FIG. 1, may be a Local Area Network (LAN). In another embodiment, the communication network may be a wireless communication network capable of transmitting voice and data signals, including image data signals or multimedia signals. Other networks may include, but are not limited to: the internet, a local area network, a Wide Area Network (WAN), a LON WORKS network, a wired network, a wireless network, or any combination thereof.

A network, such as 104 shown in fig. 1, is also shown in communication with at least one data processing resource, such as server 126, and at least one database, such as 128A. In this embodiment, a server such as 126 may be a processor-based device capable of communicating with some or all of the product dispensers such as 102A-102N via a communication network such as 104 in the form of signals such as radio frequency signals or direct wired communication signals. In addition, data processing resources or servers such as 126 may be used to assist or assist in the formulation, method of preparing a product or beverage, provide processing of operational data, perform data processing related to consumer interaction, and/or perform other data processing as may be needed and/or desired in a particular embodiment. The operational data processing may include, for example and without limitation, device status, maintenance, service alert, pre-save (predictive restore), and/or other types and kinds or types of operational data processing as may be needed and/or desired in a particular embodiment. Such consumer interaction support may include, for example and without limitation, consumer preferences, consumer product or beverage preferences, loyalty, countermeasures, prizes, media content, customization, and/or other types and kinds of consumer interaction and/or data processing support as may be required and/or desired by a particular implementation.

The server, such as 126 in fig. 1, may include a processor, such as 130, and a computer-readable medium, such as Random Access Memory (RAM)132, coupled to the processor 130. The processor such as 130 may execute computer-executable program instructions stored in the memory such as 132. The computer-executable program instructions stored in the memory, such as 132, may include any number of modular applications, such as a consumer interaction engine or module similar to 114. A consumer interaction engine or module similar to 114 may be adapted to perform different methods for consumer interaction. Additionally, a consumer interaction engine or module similar to 114 may be adapted to interact with one or more consumers and one or more servers or data processing resources. Other embodiments of the functionality and aspects of implementations of a consumer interaction engine or module similar to 114 are described below.

Through a network, such as 104 in fig. 1, some or all of the product dispensers, such as 102A-102N, may retrieve, receive, or otherwise access information stored in some or all of the databases, such as recipes, and methods of making products or beverages databases, such as 128A, operational databases, such as 128B, and consumer databases, such as 128C. In any case, the one or more databases can include product or beverage forming information, such as one or more of product or beverage formulations, recipes, and methods of product or beverage preparation. Such methods of product or beverage formulation, and preparation of a product or beverage may include a list of ingredients, a ratio of each ingredient, a list of how a consumer may customize a product or beverage, and/or other types and kinds of product or beverage formulations, and methods of product or beverage preparation as may be required and desired for a particular embodiment.

An exemplary environment or system, such as 100 shown in FIG. 1, may facilitate customer, consumer, and user interaction with product dispensers and networks. For example, and not by way of limitation, a user, such as a consumer, may make a product type selection at a product dispenser, such as 102, via an input/output device, such as display device 112. An associated processor or controller, such as 106, may assist a user in selecting a particular recipe via a display device, such as 112, to form a selected product, such as a beverage. The processor or controller such as 106 may display one or more products or beverages for selection via a display device such as 112. The user may use the display device such as 112 to select at least one of the products or beverages, for example, pressing a button set by the display device such as 112 or a button associated with the display device such as 112. A processor or controller, such as 106, may obtain the respective ingredients and/or proportions of ingredients for forming the selected product or beverage from a local memory, such as 110, or may communicate with at least one database via a network, such as 104, or may communicate with at least one data processing resource, such as server 126, to obtain the respective ingredients and/or proportions of ingredients for forming the selected product or beverage. The processor or controller, such as 106, may utilize this information to operate one or more pumps, such as 120, and/or valves, such as 122, to form and dispense a product or beverage through a nozzle, such as 124, into a cup or other container, such as 136.

In another embodiment, a user, such as a customer or package installer, may easily scan or read one or more product component packages, such as 116A-116Q, when the product component packages 116A-116Q are inserted into a component matrix, such as 108, associated with a product dispenser, such as 102A. A processor or controller such as 106 associated with the product dispenser such as 102A may identify an optimal or selected location within the composition matrix such as 108. A user, customer, or package installer can be notified via an input/output device, such as a display device, such as 112, where a particular product component package, such as 116A, will be located in a component matrix, such as 108. Embodiments of display devices may include, but are not limited to: light Emitting Diode (LED) display indicators, LCD screens, input/output (I/O) interfaces, audio interfaces, or other types and kinds of displays or indicators as may be needed and/or desired in a particular embodiment.

In one embodiment, insertion of a particular product component package, such as 116A, into a component matrix, such as 108, may be checked or otherwise verified by scanning the machine readable code on the corresponding package, such as 116A, and scanning the machine readable code located on the component matrix, such as 108, at the insertion point (shown as 118A). In this regard, the associated processor or controller, such as 106, may check or verify that the product component package, such as 116A, is properly located within the component matrix, such as 108.

In another embodiment, a cup such as 136 or other container may include identifying information such as an RFID or other machine readable tag such as 138 mounted to the cup shown in FIG. 1. In certain embodiments, the identifying information may be associated with the consumer by, for example, an RFID or other machine readable tag like 138, which is embedded in or otherwise mounted to the icon or other object. A reader, such as an RFID or other machine readable code reader, such as 140, associated with the product dispenser, such as 102A, may receive or otherwise obtain identification information from an RFID or other machine readable tag, such as 138. As shown in fig. 1, a processor or controller such as 106 associated with a product dispenser such as 102A may be in communication with an RFID or other machine readable code reader such as 140, and some or all of the identification information obtained from the RFID or other machine readable tag such as 138 may be stored or otherwise processed by the processor or controller such as 106. In this embodiment, the identification information may be embedded in machine-readable codes, bar codes, RFID, radio frequency, infrared or other form of wireless communication method or device, or other types and kinds of encoding and/or storage techniques as may be needed and desired in a particular embodiment. The RFID reader or machine-readable code reader, such as 140, may be a corresponding device that reads or receives identification information from an RFID or other machine-readable tag, such as 138, and may include an RFID read/write device, an infrared device, a magnetic card reader, a bar code reader, or other suitable reader or receiver technology as may be needed and/or desired in a particular embodiment.

In another embodiment, a server or transaction processing resource such as 126 may facilitate payment or payment processing when a consumer selects and attempts to purchase a product such as a beverage at a product dispenser such as 102A. An associated processor or controller such as 106 may receive payment or related information, data transmission or other input from the consumer, for example, via a display device such as 112, before, during or after selection of a particular product or beverage. In any case, the processor or controller, such as 106, may transmit payment or related information to a server or transaction processing resource, such as 126, via a network, such as 104. The server or transaction processing resource, such as 126, may access at least one database, such as 128A-128C, or may be in communication with at least one other data processing resource, to approve or otherwise confirm payment or related information prior to accepting payment by the consumer or prior to otherwise dispensing the selected product or beverage to the consumer.

Referring to fig. 2, an exemplary consumer dietary environment or system 200 is shown. In one embodiment, one or more networked product dispensers, such as 210, may be mounted at a plurality of respective locations, such as location 202, and may be capable of communicating with one or more servers or data processing resources, such as 206, and one or more data storage devices, such as database 208, via a network 204, such as the internet or a global network. For example, the product dispenser 210 may be similar to the beverage dispenser or dispenser device 102A described in fig. 1. In one embodiment, a product dispenser such as 210 may include some or all of the following components described with respect to FIG. 1: a component matrix such as 108 having locations operable to receive one or more product component packages such as 116A-116Q, a controller such as 106, one or more package insertion detection devices or RFID readers/writers such as 118A-118Q, a pump such as 120, a valve such as 122, and a nozzle such as 124. For example, the server or data processing resource 206 may be similar to the server or data processing resource 126 described in fig. 1.

In one embodiment, one or more consumers, such as 212, may access a network, such as 104, or a consumer's dietary network, such as 204. Through the network 204, a consumer, such as 212, may register, configure consumer preferences, access corresponding accounts, receive promotions, manage loyalty accounts, and/or register other types and kinds of opportunities and services as may be needed and/or desired in a particular embodiment. In at least one embodiment, a consumer, such as 212, may choose to access the consumer's dietary network system, such as 200, and/or a product dispenser, such as 210, through any number of client-type devices, including but not limited to: personal Computers (PCs) such as 214A, data processing devices such as 214B, wireless communication devices such as 214C, and/or by way of other types and kinds of data processing, processor or client type devices. Embodiments of wireless communication device 214C may include, but are not limited to: wireless data processing device, wireless telephone, IPHONE^TM、IPOD^TMPersonal data assistant and/or POCKET PC^TM。

Referring to FIG. 3, one embodiment of an enhanced view graphical user interface 300 is shown. In one embodiment, a product dispenser, such as 210 in FIG. 2, may include at least one user interface, such as an enhanced view graphical user interface, such as 300, or a consumer interface. A user interface such as 300 may be used, for example, by a consumer such as 212 to select any number of different product or beverage types, categories, and formulations. In use, a product dispenser such as 210 having an enhanced view graphical user interface such as 300 may provide a consumer with a series of dynamically generated menus of selectable product or beverage options, wherein the consumer may locate and select a particular brand, category, type and/or party of the respective product or beverage desired. Once a particular product or beverage option is selected, the consumer may cause the corresponding product or beverage to be prepared and dispensed by the product dispenser as formulated.

Referring to FIG. 4, another embodiment of a user interface is shown. In one embodiment, a product dispenser, such as 210 in FIG. 2, may include a typical graphical user interface, such as 400. A user interface, such as 400, may be used by a consumer, such as 212, to select from a limited number of different product or beverage types, categories, and/or formulations. In use, a consumer such as 212 may more easily select a product or beverage from a limited number of product or beverage choices. Once a particular product or beverage option is selected, the consumer may cause the product dispenser to prepare and dispense the corresponding product or beverage as formulated. In some embodiments, the classic graphical user interface may also be referred to as a traditional view because it is generally similar to traditional sprinkler dispensing valve designs. Accordingly, a typical graphical user interface may be referred to as a traditional view graphical user interface.

In one embodiment, the consumer may desire fewer product or beverage selections than are displayed by a product dispenser that allows, for example, selection of a plurality of different types of products or beverages. In this case, a classic-view graphical user interface may be displayed with relatively fewer, more traditional product or beverage selections and including one or more traditional types of product or beverage selections to facilitate the consumer to interact with the product dispenser more quickly at certain times.

In another embodiment, the consumer may choose to create consumer preferences that modify the type and/or kind of brand and/or product or beverage party displayed in a user interface, such as a classic view graphical user interface, in effect creating a consumer customized classic view graphical user interface. In this particular embodiment, the consumer may create a classic view graphical user interface that is customized by the consumer. For example, when a consumer identifies himself or herself to a product dispenser, such as 210, one or more consumer preferences may be retrieved by the dispenser 210. Based at least in part on one or more consumer preferences, product dispenser 210 may display a default user interface to the consumer, which may be an enhanced view graphical user interface, a classic view graphical user interface, or a classic view graphical user interface customized by the consumer.

Fig. 5-19 are exemplary flow diagrams of various methods according to embodiments of the invention. Some or all of the illustrated methods may be implemented by a system, network, product dispenser, or any combination associated with those illustrated in fig. 1-4.

Referring to fig. 5, a method 500 for setting a product dispenser consumer interface is shown. In the embodiment illustrated in FIG. 5, a consumer may be identified and one or more consumer preferences retrieved locally and/or remotely from a server or data processing resource. A consumer interface associated with the product dispenser may be set or otherwise generated based at least in part on one or more consumer preferences.

Method 500 begins at block 502, where identifying information associated with a consumer is received. In this embodiment, a product dispenser, such as 102A in FIG. 1, may receive or otherwise obtain identification information associated with a consumer. Based at least in part on the identification information, a processor or controller, such as 106 in fig. 1, associated with the product dispenser, such as 102A, can identify the consumer. This consumer identification may be by way of RFID tags, labels, cards, PINs, and/or by other types and kinds of identification devices or methods as may be needed and/or desired in a particular embodiment.

Block 502 is followed by block 504 in which one or more consumer preferences are retrieved. In this embodiment, one or more consumer preferences or consumer information associated with the consumer may be retrieved or otherwise obtained based at least in part on the identifying information received from the consumer. In one embodiment, the consumer preferences may be stored in advance locally and/or remotely by a server or data processing resource, such as 126 in FIG. 1. A processor or controller, such as 106, associated with the product dispenser may retrieve or otherwise receive one or more consumer preferences from a server or data processing resource, such as 126.

Block 504 is followed by block 506, wherein one or more consumer preferences are used to set a default graphical user interface view. In this embodiment, a processor or controller, such as 106 in FIG. 1, may use one or more consumer preferences or consumer information received from the processor or controller, such as 106, to set or otherwise generate one or more default graphical user interface views. This default graphical user interface view may include, but is not limited to: enhanced views, classic views, customized classic views, and/or other types and/or kinds of views as may be needed and/or desired in a particular implementation.

The method 500 ends after block 506.

Referring to fig. 6, another method 600 for setting a product dispenser consumer interface is shown. In the embodiment illustrated in fig. 6, a consumer may be in data communication with the product dispenser through a consumer data processing device, and one or more consumer preferences may be retrieved locally and/or remotely from a server or data processing resource. A consumer interface associated with the product dispenser may be set or otherwise generated based at least in part on one or more consumer preferences. In this regard, this data communication may be used to select and/or customize a graphical user interface.

The method 600 begins at block 602 where identification information is received from a client type device or a wireless communication device. In this embodiment, a client-type device associated with a consumer, such as 212A in FIG. 2, may transmit identification information associated with the consumer to a product dispenser, such as 102A in FIG. 1. The client-type device may be, for example, a wired or wireless data processing device that may interact with the consumer or a product cup associated with the consumer. A product dispenser, such as 102A, may receive data, such as identification information associated with a consumer.

Block 602 is followed by block 604, wherein one or more consumer preferences are retrieved or otherwise determined. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser 102A may transmit data to a local and/or remote server or data processing resource, such as 126. Based at least in part on the data, such as the identification information, the server or data processing resource, such as 126, may retrieve or otherwise determine one or more consumer preferences or consumer information.

Block 604 is followed by block 606, wherein the one or more consumer preferences are used to set one or more default graphical user interface views. In this embodiment, a processor or controller, such as 106 in FIG. 1, may use one or more consumer preferences or consumer information received from the processor or controller, such as 106, to set or otherwise generate one or more default graphical user interface views. This default graphical user interface view may include, but is not limited to: enhanced views such as 300, classic views such as 400, customized classic views, and/or other types and/or kinds of views as may be needed and/or desired in a particular implementation.

Method 600 ends after block 606.

Referring to fig. 7-9, several embodiments of methods 700, 800, 900 of performing differential pricing are illustrated. In the embodiment illustrated in fig. 7, one or more consumer preferences or consumer information may be obtained prior to dispensing a product from the product dispenser and/or charging for the dispensed product. In this regard, consumer preferences may be used, in part, to determine the price charged for the dispensed product. This consumer preference or consumer information may be obtained by the product dispenser when the consumer identifies himself or herself to the product dispenser. Alternatively, the consumer may enter a code or other type of unique identifier to be identified, grouped, and/or otherwise assigned a price for the dispensed product. Additionally, the consumer can be in data communication with the product dispenser, and this data communication can determine, in part, a price to charge the consumer for the dispensed product.

The method 700 begins at block 702. In block 702, a consumer is identified. In this embodiment, a product dispenser, such as 102A in FIG. 1, may receive or otherwise obtain identification information associated with a consumer. Based at least in part on the identification information, a processor or controller, such as 106, associated with the product dispenser, such as 102A, can identify the consumer. The identification information may be provided by way of RFID tags, labels, cards, PINs, and/or by way of other types and kinds of identification methods as may be needed and/or desired in a particular embodiment.

Block 702 is followed by block 704, wherein one or more consumer preferences are obtained. In this embodiment, one or more consumer preferences or consumer information associated with the consumer may be obtained or otherwise received based at least in part on the identifying information associated with the consumer. In one embodiment, the consumer preferences may be stored in advance locally and/or remotely by a server or data processing resource, such as 126 in FIG. 1. A processor or controller, such as 106, associated with the product dispenser may obtain or otherwise receive one or more consumer preferences or consumer information from a server or data processing resource, such as 126, as may be needed and/or desired in a particular embodiment.

Block 704 is followed by block 706, wherein at least one pricing model is determined. In this embodiment, at least one pricing model may be determined or otherwise selected by a processor or controller such as 106 associated with the product dispenser such as 102A based at least in part on one or more consumer preferences. In one embodiment, the pricing model may be stored in a data storage device associated with a server or data processing resource such as 126. The pricing model may determine how much to charge the consumer for the dispensed product. This model may charge the same for all dispensed products and/or may charge different prices for different types and/or kinds of products and/or different prices for different volumes of dispensed products.

Block 706 is followed by block 708 wherein the product is dispensed from the product dispenser to the consumer. In this embodiment, the product dispenser may begin dispensing at least one product, such as a beverage, to the consumer. For example, a product, such as a beverage, may be dispensed via a nozzle associated with the product dispenser, such as nozzle 124 of the product dispenser (e.g., 102A). In other embodiments, other product configurations may be dispensed, such as cans, bottles, and packaged or otherwise packaged products.

Block 708 is followed by block 710 in which a price is determined for the dispensed product. In this embodiment, a processor or controller, such as 106, associated with the product dispenser, such as 102A, may determine a price for the dispensed product or beverage based at least in part on at least one pricing model. In some cases, a pricing model may have more than one price for a particular product or beverage, and additional data such as consumer preferences, identifying information, volume, and type of product may be used to determine the price.

Block 710 is followed by block 712, wherein the consumer is charged for the dispensed product. In this embodiment, a processor or controller such as 106 associated with the product dispenser such as 102A may charge the consumer for the dispensed product or beverage. For example, a processor or controller such as 106 associated with a product dispenser such as 102A may charge or otherwise debit an account associated with a consumer. In other embodiments, a processor or controller such as 106 associated with a product dispenser such as 102A may facilitate payment by a consumer via a user interface associated with a payment transaction device.

The method 700 ends at block 712.

Referring to FIG. 8, another method 800 for performing differential pricing is illustrated. In this embodiment, the consumer may interact with a graphical user interface associated with the product dispenser. The consumer may enter a code and/or other type and/or kind of identification as may be needed and/or desired in a particular implementation. This code or identification may be used for promotional pricing and/or for other purposes.

The method 800 begins in block 714. In block 714, the consumer interacts with a user interface associated with the product dispenser and enters a code and/or other type of identifying information. In this embodiment, the consumer may interact with a user interface, such as 112 in FIG. 1, associated with the product dispenser, such as 102A, to enter a code and/or other types or kinds of identifying information.

Block 714 is followed by block 716, wherein one or more consumer preferences are obtained. In this embodiment, one or more consumer preferences or consumer information associated with the consumer may be obtained or otherwise received based at least in part on some or all of the code and identification information entered by the consumer. In one embodiment, consumer preferences or consumer information may be stored locally and/or remotely by a server or data processing resource such as 126 in FIG. 1 in advance. A processor or controller such as 106 associated with the product dispenser may obtain or otherwise receive one or more consumer preferences from a server or data processing resource such as 126, as may be needed and/or desired in a particular embodiment.

Block 716 is followed by block 706 as described above with respect to fig. 7. Method 800 may continue as described above in fig. 7.

Referring to FIG. 9, another method 900 for performing differential pricing is illustrated. In this embodiment, the consumer may be in data communication with the product dispenser. This data communication may be used to identify consumers, determine promotional information, and/or otherwise assist in determining one or more consumer preferences, promotional preferences, and/or other types and/or kinds of preferences.

The method 900 begins at block 718, where the consumer activates the product dispenser using a client type device or a wireless communication device. In this embodiment, the consumer may interact with a client type device, such as 214A-214C in FIG. 2. Examples of client type devices may include, but are not limited to: wireless communication device, wireless telephone, IPOD^TM、IPHONE^TM、POCKET PC^TMAnd other wireless communication devices. In any case, the consumer may operate a client-type device, such as 214A-214C, which may send a signal to a nearby product dispenser. In this case, the product dispenser may be activated or otherwise set to a relatively high state in preparation for interacting with a consumer or client type device or wireless communication device. .

Block 718 is followed by block 720, wherein the one or more consumer preferences are transmitted by the consumer to the product dispenser via a client type device or a wireless communication device. In this embodiment, consumer preferences, such as those entered by the consumer or pre-stored information, may be communicated from a client-type device or wireless communication device, such as 214A-214C, to a product dispenser, such as 102A in FIG. 1.

Block 718 is followed by block 706 as described above with respect to fig. 7. Method 900 may continue as described above in fig. 7.

Referring to FIG. 10, an exemplary method 1000 for interacting with a product dispenser is provided. In the illustrated embodiment, the consumer may use a client type device or wireless communication deviceSuch as wireless communication devices, wireless telephones, IPODs^TM、IPHONE^TM、POCKET PC^TMAnd/or other types and/or kinds of wireless data processing devices that may communicate with the product dispenser. In this regard, the one or more consumer preferences may be stored on or retrieved from a client type device associated with the consumer.

In one embodiment, a consumer may use his or her client-type device or wireless communication device to buy products, exchange recipes, and receive promotional content to friends.

The method 1000 begins in block 1002. In block 1002, input is received from a consumer via a client type device, such as 214A-214C in FIG. 2. In this embodiment, a client-type device or wireless communication device, such as 214A-214C, associated with a consumer may transmit data to a product dispenser, such as 102A in FIG. 1. The client type device may be, for example, a wireless communication device, a wireless telephone, an IPOD^TM、IPHONE^TM、POCKET PC^TMAnd/or other types and/or kinds of wireless processing devices that may communicate with the product dispenser. The product dispenser, such as 102A, may receive data, such as identification information associated with the consumer, from a client-type device or a wireless communication device.

Block 1002 is followed by decision block 1004, wherein a determination is made as to whether to store the consumer preferences at the client type device or the wireless communication device. If the determination is positive, i.e., the consumer wants to store one or more consumer preferences at the client type device or the wireless communication device, the method 1000 continues to block 1006. If the determination is negative, i.e., the consumer does not want to store one or more consumer preferences at the client type device or the wireless communication device, the method 1000 continues to block 1008. In this embodiment, the consumer may make a decision to store one or more consumer preferences at a client type device or wireless communication device, such as 214A-214C. For example, a client type device or wireless communication device, such as 214A-214C, may include an option to store one or more consumer preferences in a data storage device, such as a memory associated with the client type device or wireless communication device.

At block 1006, the consumer preferences are stored at the client type device or the wireless communication device. In this embodiment, a client type device or wireless communication device, such as 214A-214C, may receive a consumer instruction to store one or more consumer preferences, and the client type device or wireless communication device, such as 214A-214C, may store the one or more consumer preferences in a data storage device, such as a memory, associated with the client type device or wireless communication device. In other embodiments, the client type device or the wireless communication device may store one or more consumer preferences in a data storage device accessible via a network, such as a database in communication with the client type device or the wireless communication device via a network.

Block 1006 is followed by decision block 1008 in which a determination is made as to whether the consumer wants to retrieve consumer preferences from a client type device or a wireless communication device. If the determination is positive, i.e., the consumer wants to retrieve one or more consumer preferences from a client type device or wireless communication device, such as 214A-214C, the method 1000 continues to block 1010. If the determination is negative, i.e., the consumer does not want to retrieve one or more consumer preferences from a client type device or wireless communication device, such as 214A-214C, the method 1000 continues to decision block 1012. In this embodiment, the consumer may determine whether to provide access to one or more consumer preferences stored on the client type device or the wireless communication device. For example, a client type device or wireless communication device may provide the prompt to the consumer, and the consumer may provide the instruction via an input device associated with the client type device or wireless communication device, such as a keypad associated with the client type device or wireless communication device, such as 214A-214C. In another embodiment, a client type device or wireless communication device may provide a prompt to the consumer, and the consumer may provide instructions, such as voice instructions, via an input device, such as a microphone, associated with the client type device or wireless communication device, such as 214A-214C. In any case, a controller or processor associated with the wireless communication device may receive the instructions and, if desired by the consumer, may provide access to one or more consumer preferences.

In block 1010, product preferences are retrieved from the client type device or the wireless communication device. In this embodiment, the one or more product preferences may be retrieved from a data storage device associated with the client type device or the wireless communication device, or via a data storage device accessible from a network after the client type device or the wireless communication device receives the instruction from the consumer. For example, a processor or controller associated with a client type device or wireless communication device, such as 214A-214C, may receive instructions from a consumer to provide access, and the controller may retrieve one or more product preferences stored in an associated data storage device, such as a memory.

Block 1010 is followed by decision block 1012, wherein a determination is made whether the consumer wants to send the product preference to an entity, such as a friend. If the determination is positive, i.e., the consumer wants to send the product preference to an entity, such as a friend, the method 1000 continues to block 1014. If the determination is negative, i.e., the consumer does not want to send the product preferences to an entity, such as a friend, the method 1000 continues to decision block 1016. In this embodiment, the consumer may determine whether to provide one or more product preferences to an entity, such as a friend. For example, a client type device or wireless communication device may provide a prompt to a consumer, and the consumer may provide instructions to provide one or more product preferences to an entity, such as a friend. The instructions may be transmitted via an input device associated with the client type device or the wireless communication device, such as a keypad associated with the client type device or the wireless communication device, such as 214A-214C. In another embodiment, a client type device or wireless communication device may provide a prompt to a consumer, and the consumer may provide an instruction, such as a voice instruction, to provide one or more product preferences to an entity, such as a friend. The instructions may be transmitted via an input device, such as a microphone, associated with the client-type device or the wireless communication device, such as 214A-214C. In any case, a controller or processor associated with a client type device or wireless communication device may receive instructions from a consumer and, if the consumer desires, may provide one or more product preferences to an entity such as a friend.

In block 1014, the product preferences are sent to an entity, such as a friend. In this embodiment, the client type device or wireless communication device may communicate one or more product preferences to an entity, such as a friend, via the network. For example, a client type device or wireless communication device, such as 214A-214C in fig. 2, may communicate one or more product preferences via a network, such as 104 in fig. 1, to a client type device or wireless communication device associated with an entity, such as a client type device or wireless communication device associated with a friend.

Block 1014 is followed by block 1016 in which a determination is made as to whether the consumer wants to purchase a product for an entity, such as a friend. If the determination is positive, i.e., the consumer wants to buy a product or beverage for an entity, such as a friend, the method 1000 continues to block 1018. If the determination is negative, i.e., the consumer does not want to buy a product or beverage for an entity, such as a friend, the method 1000 proceeds to decision block 1020. In this embodiment, the consumer may determine whether to purchase a product or beverage for an entity, such as a friend. For example, a client type device or wireless communication device may provide a prompt to a consumer, and the consumer may provide instructions to buy or purchase a product or beverage for an entity, such as a friend. The instructions may be transmitted via an input device associated with the client type device or the wireless communication device, such as a keypad associated with the client type device or the wireless communication device, such as 214A-214C. In another embodiment, a client type device or wireless communication device may provide a prompt to a consumer, and the consumer may provide an instruction, such as a voice instruction, to buy or purchase a product or beverage for an entity, such as a friend. The instructions may be transmitted via an input device (such as a microphone) associated with the client-type device or the wireless communication device (such as 214A-214C). In any case, a processor or controller associated with the client type device or wireless communication device may receive instructions from the consumer to buy or purchase a product or beverage for an entity, such as a friend, if the consumer so desires.

Decision block 1016 is followed by block 1018 of purchasing a product for an entity, such as a friend. In this embodiment, a consumer may facilitate buying or purchasing a product or beverage for an entity, such as a friend, via a client type device or wireless communication device, such as 214A-214C. For example, a client-type device or wireless communication device such as 214A-214C may assist a consumer in purchasing a product or beverage on behalf of an entity such as a friend by communicating one or more purchase instructions to a product dispenser such as 102A.

Block 1018 is followed by decision block 1020, where a determination is made whether a client-type device or wireless communication device, such as 214A-214C, is to receive promotional content from a product dispenser. If the determination is positive, i.e., a client-type device or wireless communication device, such as 214A-214C, receives promotional content from the product dispenser, the method 1000 continues to block 1022. If the determination is negative, i.e., the client-type device or wireless communication device, such as 214A-214C, does not receive promotional content from the product dispenser, the method 1000 continues to decision block 1024. In this embodiment, a processor or controller associated with a client type device or wireless communication device, such as 214A-214C in FIG. 2, may determine whether to receive promotional content from a product dispenser, such as 102A in FIG. 1, or from a remote location, such as a server or data processing resource, such as 126.

Decision block 1020 is followed by block 1022 in which promotional content is received and selectively displayed. In this embodiment, promotional content may be delivered from a product dispenser, such as 102A, and selectively displayed by a client-type device or wireless communication device, such as 214A-214C, and/or a product dispenser, such as 102A.

Block 1022 is followed by decision block 1024, where it is determined whether to send a survey to the consumer. If the determination is positive, i.e., a survey is sent to the consumer, the method 1000 continues to block 1026. If the determination is negative, i.e., no survey is sent to the consumer, the method 1000 ends. In this embodiment, a processor or controller associated with the production facility, such as 106 in FIG. 1, may determine whether to send a survey to the consumer. In one embodiment, a server or data processing resource such as 126 may determine whether to send a survey to a consumer.

Decision block 1024 is followed by block 1026 in which the consumer receives a survey. In this embodiment, the survey may be sent to the consumer by a processor or controller associated with the production facility, such as controller 106 in FIG. 1. The survey may be displayed on a user interface associated with a client type device or wireless communication device, such as 214A-214C in fig. 2. In one embodiment, the survey may be displayed on a user interface associated with the product dispenser, such as user interface 112 in FIG. 1.

Block 1026 is followed by block 1208, wherein survey input is received from the consumer. In this embodiment, the survey displayed on the user interface associated with the client-type device or wireless communication device, such as 214A-214C in FIG. 2, may be completed or otherwise populated by the consumer using an associated keypad or other input device. In one embodiment, the survey displayed on the user interface associated with the product dispenser may be completed or otherwise populated by the consumer using an associated input device, such as a keypad or input pad (input pad).

Block 1028 is followed by block 1030 wherein the survey input is communicated to the data processing resource. In this embodiment, the consumer may initiate the transmission of some or all of the input for the survey to a server or data processing resource, such as 126 in FIG. 1, for storage and subsequent processing and retrieval. Following block 1030, the method 1000 ends.

Referring to fig. 11, an exemplary method 1100 of providing a loyalty award based at least in part on whether a product is dispensed. In this embodiment, each time the consumer visits the product dispenser, he or she may receive a loyalty award, such as a brand loyalty award. In this regard, the consumer may receive the brand loyalty award without purchasing the product from the product dispenser. When a consumer chooses to purchase a product from the product dispenser, the consumer may receive a product loyalty award.

The method 1100 begins at block 1102, where a consumer is identified by a product dispenser. In this embodiment, a product dispenser, such as 102A in FIG. 1, may receive or otherwise obtain identification information associated with a consumer. Based at least in part on the identification information, a processor or controller, such as 106, associated with the product dispenser, such as 102A, can identify the consumer. The identification information may be provided by an RFID tag, label, card, PIN, and/or by other types and kinds of identification methods as may be needed and/or desired in a particular embodiment. For example, the consumer may be associated with a wireless communication device, such as 214A-214C in FIG. 2, which may communicate identification information to the product dispenser when the consumer approaches the dispenser.

Block 1102 is followed by block 1104 in which the brand loyalty award is distributed to the consumer via a client type device or a wireless communication device. In this embodiment, wireless communication devices, such as 214A-214C, and product dispensers may communicate via wireless communication when a client type device or wireless communication device, such as 214A-214C in FIG. 2, is in proximity to the product dispenser. The brand loyalty award may be issued (credit) or otherwise obtained by the consumer without purchasing the product or beverage from the product dispenser. This type of loyalty award may be referred to as a "brand loyalty award" because the beverage or product is not dispensed or is otherwise purchased from the product dispenser.

Block 1104 is followed by decision block 1106, where a determination is made whether the consumer is to dispense a product. If the determination is positive, i.e., the consumer dispenses the product, the method 1100 continues to block 1108. If the determination is negative, i.e., the consumer has not dispensed a product, the method 1100 ends. In this embodiment, a processor or controller associated with a product dispenser, such as 102A in fig. 1, may determine whether a consumer dispenses a product from the product dispenser, such as 102A.

In block 1108, a product loyalty award may be distributed to the consumer via a client type device or a wireless communication device. In this embodiment, client type devices or wireless communication devices, such as 214A-214C, may assist a consumer in obtaining a loyalty award. For example, wireless communication devices, such as 214A-214C, may store product loyalty awards or otherwise credit an account associated with the consumer. In this embodiment, the loyalty award may be considered a "product loyalty award" because the product is distributed to the consumer. This loyalty award may be referred to as a "product loyalty award" and may be modified based in part on the type and/or type of product or beverage dispensed.

The method 1100 ends after block 1108.

Referring to fig. 12-13, embodiments of methods 1200, 1300 of performing a frequent beverage program to obtain free or discounted beverages are described.

In the embodiment shown in fig. 12, the regular drink program may enable the consumer to receive a regular drink reward and then redeem the reward for a free product dispensed from the product dispenser.

The method 1200 begins at block 1202. In block 1202, a consumer is identified by a product dispenser. In this embodiment, a product dispenser, such as 102A in FIG. 1, may receive or otherwise obtain identification information associated with a consumer. Based at least in part on the identification information, a processor or controller, such as 106, associated with the product dispenser, such as 102A, can identify the consumer. This consumer information may be provided by way of RFID tags, labels, cards, loyalty cards, personal identification codes, PINs, consumer wireless data processing devices, and/or by way of other types and kinds of identification devices or methods as may be required and/or desired in a particular embodiment.

Block 1202 is followed by block 1204, wherein the product dispenser tracks one or more products or beverages dispensed by the consumer. In this embodiment, a product dispenser, such as 102A in fig. 1, may generate information associated with one or more products or beverages dispensed to or dispensed by a consumer. Based at least in part on information associated with one or more products or beverages dispensed to or by a consumer, a processor or controller such as 106 associated with a product dispenser such as 102A may store the information in an associated memory or other data storage device such as 110 in fig. 1. In this manner, one or more products or beverages dispensed to or dispensed by a consumer may be tracked by the product dispenser.

Block 1204 is followed by block 1206, wherein a frequent beverage reward is assigned (assign) to the consumer based at least in part on the product or beverage type, and/or quantity of product or beverage dispensed. Based at least in part on the product or beverage type, category, and/or quantity of product or beverage dispensed to or by the consumer, a processor or controller, such as 106 in fig. 1, associated with the product dispenser, such as 102A, may determine a reward, such as a regular beverage reward, to assign to the consumer.

Block 1206 is followed by block 1208, wherein the frequent beverage reward is posted to an account selected by the consumer. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may transmit the reward data to a local and/or remote server or data processing resource, such as 126. A local and/or remote server or data processing resource such as 126 may store data associated with the constant beverage reward or other reward data in an account previously selected or otherwise designated by the consumer. In one embodiment, the account may be generated for the consumer and stored in memory associated with a local and/or remote server or data processing resource, such as 126, or in other data storage devices, such as 110. The consumer may select or otherwise designate an account to receive the reward before the reward is posted to the account. For example, a processor or controller such as 126 associated with a product dispenser such as 102A may provide the consumer with an option via a user interface such as 112 to select or otherwise designate an account to receive the reward. In another embodiment, a local and/or remote server or data processing resource, such as 126, may provide the consumer with an option via a client type device, such as 214A-214C in fig. 2, to select or otherwise designate an account to receive the reward. In any case, the consumer's input regarding the account selected to receive the prize may be stored in memory associated with a local and/or remote server or data processing resource.

The method 1200 ends after block 1208.

Fig. 13 illustrates another method 1300 of performing a frequent beverage program to obtain free or discounted beverages. In the embodiment illustrated in FIG. 13, the consumer may receive a printed reward code, and/or other types and kinds of codes, which the consumer may later enter online to add a reward to the regular drink account. In this regard, a consumer may receive data at a product dispenser and may enter the data at a website, such as myoKEREWARDS.

The method 1300 shown in FIG. 13 begins at block 1302. At block 1310, the consumer is identified by the product dispenser. In this embodiment, a product dispenser, such as 102A in FIG. 1, may receive or otherwise obtain identification information associated with a consumer. Based at least in part on the identification information, a processor or controller such as 126 associated with the product dispenser such as 102A may identify the consumer. This consumer information may be provided by way of RFID tags, labels, cards, loyalty cards, personal identification codes, PINs, consumer wireless data processing devices, and/or by way of other types and kinds of identification devices or methods as may be required and/or desired in a particular embodiment.

Block 1302 is followed by block 1304, wherein the product dispenser tracks a product or beverage dispensed by a consumer. In this embodiment, a product dispenser, such as 102A in fig. 1, may generate information associated with one or more products or beverages dispensed to or dispensed by a consumer. Based at least in part on information associated with one or more products or beverages dispensed to or by a consumer, a processor or controller such as 126 associated with a product dispenser such as 102A may store the information in an associated memory or other data storage device such as 110. In this manner, one or more products or beverages dispensed to or dispensed by a consumer may be tracked by the product dispenser.

Block 1304 is followed by block 1306, wherein a frequent beverage award is assigned to the consumer based at least in part on the product or beverage type, the type, and/or the quantity of product or beverage dispensed. Based at least in part on the product or beverage type, category, and/or quantity of product or beverage dispensed to or by the consumer, a processor or controller, such as 126 in fig. 1, associated with the product dispenser, such as 102A, may determine a reward, such as a regular beverage reward, to assign to the consumer.

Block 1306 is followed by block 1308, wherein the award code is printed and/or otherwise transmitted to the consumer. In the illustrated embodiment, a processor or controller, such as 126 in FIG. 1, associated with the product dispenser, such as 102A, may generate or otherwise receive a reward code for delivery to the consumer. A processor or controller such as 126 may provide the reward code to the consumer via an output device such as a printer such as 134 or a user interface such as 112. In another embodiment, a local and/or remote server or data processing resource such as 126 may generate the reward code and transmit the reward code to a product dispenser such as 102A for transmission to the consumer. In another embodiment, a local and/or remote server or data processing resource, such as 126, may generate the benefit code and transmit the benefit code to a client type device, such as 214A-214C in fig. 2, via a network, such as 104, for acceptance by the consumer. In any case, the benefit code is printed and/or otherwise transmitted to the consumer.

Block 1308 is followed by block 1310, where the consumer is allowed to enter an award code online to post the regular drink award to his or her account. In the illustrated embodiment, the consumer may utilize a client-type device, such as 214A-214C in FIG. 2, to obtain online access to the website, web page, at a later date, time, and/or at a location selected by the consumer. In another embodiment, the consumer may utilize the product dispenser to access a website, web page, or other online location at a later date, time, and/or at a location selected by the consumer. In any case, the consumer may enter the reward code online via a website, web page, or other online location. A local and/or remote server or data processing resource, such as 126 in fig. 1, can receive the reward code, and the server or data processing resource, such as 126, can post a reward, such as a regular drink reward, to his or her account. A local and/or remote server or data processing resource such as 126 may store data related to frequent beverage rewards or other reward data in an account previously selected or otherwise designated by the consumer. In one embodiment, the account may be generated for the customer and stored in memory associated with local and/or remote memory or data processing resources such as 126, or in other data storage devices such as 110. The consumer may select or otherwise designate an account to receive the reward before the reward is posted to the account. For example, a processor or controller such as 106 associated with a product dispenser such as 102A may provide a customer with an option via a user interface such as 112 to select or otherwise designate an account to receive an award. In another embodiment, a local and/or remote server or data processing resource, such as 126, may provide the consumer with an option via a client type device, such as 214A-214C, to select or otherwise designate an account to receive the reward. In any case, the consumer's input regarding the selected account to receive the prize may be stored in a memory associated with a local and/or remote server or data processing resource, such as 126, or in other data storage devices, such as 110.

The method 1300 ends after block 1310.

Fig. 14 illustrates another method 1400 of performing a frequent beverage program to obtain free or discounted beverages. In the embodiment shown in fig. 14, the consumer may redeem the frequent beverage reward at the product dispenser.

The method 1400 shown in FIG. 14 begins at block 1402. In block 1420, the consumer is identified by the product dispenser. In this embodiment, a product dispenser, such as 102A in FIG. 1, may receive or otherwise obtain identification information associated with a consumer. Based at least in part on the identification information, a processor or controller, such as 106, associated with the product dispenser, such as 102A, can identify the consumer. This consumer information may be provided by way of RFID tags, labels, cards, loyalty cards, personal identification codes, PINs, consumer wireless data processing devices, and/or by way of other types and kinds of identification devices or methods as may be required and/or desired in a particular embodiment.

Block 1402 is followed by block 1404 in which the product dispenser may be in data communication with a data processing resource locally and/or remotely to obtain a consumer's frequent beverage reward status. In the illustrated embodiment, a processor or controller, such as 106 in fig. 1, associated with the product dispenser, such as 102A, may transmit the identification data to a local and/or remote server or data processing resource, such as 126. Based at least in part on the identification data, a local and/or remote server or data processing resource, such as 126, may obtain or otherwise determine a constant beverage reward status or account associated with the consumer. In one embodiment, a processor or controller such as 106 may access an associated memory or data storage device such as 110 to obtain or otherwise determine a frequent beverage reward status or an account associated with the consumer.

In one embodiment, the consumer may select or otherwise designate an account to receive and redeem the reward prior to obtaining the reward status of the account. For example, a processor or controller, such as 106 in fig. 1, associated with a product dispenser, such as 102A, may provide the consumer with an option via a user interface, such as 112, to select or otherwise designate an account to receive and redeem the reward. In another embodiment, a local and/or remote server or data processing resource, such as 126, may provide the consumer with an option via a client type device, such as 214A-214C in fig. 2, to select or otherwise designate an account to receive the reward. In any case, the consumer's input regarding the account selected to receive the reward may be stored in memory associated with a local and/or remote server or data processing resource, such as 126, or in other data storage devices, such as 110.

Block 1404 is followed by decision block 1406 in which a determination is made as to whether the consumer has sufficient rewards for the free or discounted product or beverage. If the determination is positive, i.e., the consumer has sufficient rewards for a free or discounted product or beverage, the method 1400 continues to block 1408. If the determination is negative, i.e., the consumer does not have sufficient rewards for a free or discounted product or beverage, the method 1400 ends. In the illustrated embodiment, a local and/or remote server or data processing resource, such as 126 in FIG. 1, may determine whether there is sufficient incentive for free or discounted products or beverages in an account associated with the consumer. For example, a local and/or remote server or data processing resource such as 126 may compare a threshold amount corresponding to a free or discounted product or beverage to the award amount in the account. Based at least in part on the comparison, a local and/or remote server or data processing resource, such as 126, may determine whether an account associated with the consumer has sufficient rewards for the free or discounted product or beverage.

In block 1408, the consumer is notified that he or she can redeem the frequent beverage award for a free or discounted product or beverage. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with a product dispenser, such as 102A, may generate or otherwise communicate a communication to the consumer that he or she may redeem the frequent beverage award for a free or discounted product or beverage. In another embodiment, a local and/or remote server or data care resource such as 126 may generate a communication or other input such as a message and transmit the message to a product dispenser such as 102A for transmission to a consumer. A processor or controller such as 106 associated with the product dispenser such as 102A may receive the message for delivery to the consumer. In any case, a processor or controller such as 106 associated with the product dispenser such as 102A may provide a message to the consumer via an output device such as a user interface, e.g., 112.

Block 1408 is followed by decision block 1410, wherein a determination is made as to whether the consumer wants to redeem the reward for a free or discounted product or beverage. If the determination is positive, i.e., the consumer wants to redeem the reward for a free or discounted product or beverage, the method 1400 continues to block 1412. If the determination is negative, i.e., the consumer does not want to redeem the reward for a free or discounted product or beverage, the method 1400 ends. In the illustrated embodiment of fig. 14, a processor or controller, such as 106 in fig. 1, associated with the product dispenser, such as 102A, may determine whether the consumer wants to redeem the reward for a free or discounted product or beverage. For example, a processor or controller, such as 106, may receive a consumer input or selection via a user interface, such as 112, and determine whether the input or selection corresponds to whether the consumer wants to redeem the reward.

At block 1412, the consumer is notified that the regular beverage prize has been redeemed and that the product or beverage fee is exempt or otherwise discounted. In this embodiment, information related to notifying the consumer may be sent to the consumer via a processor or controller associated with the product device, such as controller 106 in FIG. 1. Information associated with notifying the consumer may be displayed on a user interface associated with a product dispenser, such as 102A.

Block 1412 is followed by block 1414 in which the status of the usual beverage prize credits and/or amounts reflects any prize redemption. In the illustrated embodiment, a processor or controller associated with the product dispenser, such as 106 in fig. 1, may communicate with a local and/or remote server or data processing resource, such as 126, to adjust the prize total in the consumer account, such as a regular beverage prize. Additionally, a local and/or remote server or data processing resource such as 126 may change the status of the account depending on whether there is sufficient total points in the account for current or future redemption of the reward.

The method 1400 ends after block 1414.

Referring to fig. 15-16, embodiments of methods 1500, 1600 of using consumer preferences to customize user interface skins are illustrated.

Referring to FIG. 15, a method 1500 begins at block 1502 where a consumer is allowed to select a consumer graphical user interface skin and one or more consumer interests. In the illustrated embodiment of FIG. 15, the consumer may enter data via a user interface, such as 112 in FIG. 1, such as selecting one or more indicators corresponding to a particular consumer graphical user interface skin and consumer interests. The consumer graphical user interface skins may include, but are not limited to: skin, color, design, pattern, graphic, theme-based content, audio file, sound, or any other visual and/or audio configuration. For example, the consumer graphical user interface skin may include, but is not limited to: MCDONALD' S^TMColour and trademark, COCA-COLA^TMColour and trademark, THEATLANTA BRAVES^TMBaseball team colors and trademarks, and/or generally all kinds and types of organizational colors, graphics, and trademarks as may be needed and/or desired in a particular embodiment. Consumer interests may include, but are not limited to: news, weather, sports, finance, and/or other types and categories of interest, as may be needed and/or desired in a particular implementation. For example, ifThe consumer is interested in baseball and the consumer graphical user interface may be skinned with the theme of baseball. In another embodiment, if the consumer likes NASCAR^TMRacing cars, the consumer graphical user interface may be NASCAR^TMRacing themes are skin and relate to NASCAR^TMNews, weather, and sports information for racing cars may be obtained and used to populate a consumer graphical user interface.

Block 1502 is followed by block 1504 wherein one or more consumer-selected preferences and interests may be stored. In this embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may store one or more consumer-selected preferences and interests in an associated memory or data storage device, such as 110. In another embodiment, a product dispenser, such as 102A, may communicate some or all of the consumer's selected preferences and interests to a local and/or remote server or data processing resource, such as 126, for storage in an associated memory or data storage device, such as 110. In any case, one or more consumer-selected preferences or interests may be stored in an associated memory or other data storage device for subsequent retrieval and/or processing.

Method 1500 ends after block 1504.

Referring to FIG. 16, a method 1600 for utilizing one or more consumer preferences and interests to customize a graphical user interface is illustrated.

The method 1600 begins at block 1602, where a consumer is identified by a product dispenser. In this embodiment, a product dispenser, such as 102A in FIG. 1, may receive or otherwise obtain identification information associated with a consumer. Based at least in part on the identification information, a processor or controller, such as 106, associated with the product dispenser, such as 102A, can identify the consumer. The consumer identification may be by way of RFID, badge, card, loyalty card, personal identification code, PIN, consumer wireless data processing device, and/or by way of other types and kinds of identification devices or methods as may be required and/or desired in a particular embodiment.

Block 1602 is followed by block 1604, where the product dispenser obtains one or more consumer preferences and interests. In the illustrated embodiment, a processor or controller, such as 106 in fig. 1, associated with the product dispenser, such as 102A, may transmit the identification data to a local and/or remote server or data processing resource, such as 126. Based at least in part on the identification data, one or more consumer preferences and interests may be obtained or otherwise determined by a local and/or remote server or data processing resource, such as 126, which may be stored in a previously created account associated with the consumer, for example.

Block 1604 is followed by block 1606 wherein the user interface may be customized based at least in part on the consumer preferences, including customizing the interface skin and populating the interface with relevant consumer interest data. In the illustrated embodiment, a processor or controller, such as 106 in fig. 1, associated with the product dispenser, such as 102A, may receive or otherwise obtain one or more consumer preferences, and the controller, such as 106, may utilize some or all of the consumer preferences to customize the graphical user interface, such as 112, associated with the product dispenser, such as 102A. Consumer interest data may include, but is not limited to: news, weather, sports, financial, and/or other types and kinds of digital content as may be needed and/or desired in a particular implementation.

Method 1600 ends after block 1606.

Referring to FIG. 17, an exemplary method 1700 of configuring a product dispenser according to a consumer recipe is shown.

Method 1700 begins at block 1702 where identifying information or preference information associated with a consumer is received. In this embodiment, a product dispenser, such as 102A in FIG. 1, may receive or otherwise obtain identification information or preference information in the form of, for example, encoded media information provided by a consumer. The encoded media information may include, but is not limited to, information associated with one or more of the following: a recipe profile, a list of one or more product ingredients, and a product. Coded media storing coded media information may include, but is not limited to: thumb drive, memory stick, memory, data storage device, or any device or method capable of transferring data to a product dispenser. In one embodiment, a consumer may formulate one or more recipes and store the recipes on a coded media.

Block 1702 is followed by block 1704, wherein the customer's recipe profile is determined. In this embodiment, a processor or controller, such as 106 in FIG. 1, associated with a product dispenser, such as 102A, may determine a consumer formula profile based at least in part on the encoded media information provided by the consumer. The consumer formula profile may include, but is not limited to: a recipe profile, a list of one or more product ingredients, and a product.

Block 1704 is followed by block 1706, wherein the product dispenser is configured based at least in part on the consumer's recipe profile. In this embodiment, a processor or controller, such as 106 in fig. 1, associated with the product dispenser, such as 102A, may configure the product dispenser, such as 102A, to dispense a desired product by preparing any number of product component packs, valves, and pumps. In one embodiment, a consumer's recipe profile may enable a product dispenser to provide the consumer with one or more products or formulations of products that the consumer has previously stored in the recipe profile.

Block 1706 is followed by block 1708, wherein the consumer is allowed to be dispensed a product based at least in part on the consumer's recipe profile. In this embodiment, a processor or controller, such as 106 in FIG. 1, associated with a product dispenser, such as 102A, may formulate and dispense one or more products based at least in part on a consumer's recipe profile.

The method 1700 ends after block 1708.

Referring to fig. 18, an exemplary method of configuring a beverage forming dispenser according to a consumer's recipe is shown.

The method 1800 begins at block 1802, where a consumer input is received by a beverage forming dispenser. In this embodiment, a beverage forming dispenser, such as 102A in fig. 1, may receive or otherwise obtain input from a consumer, such as input from encoded media information associated with or otherwise provided by the consumer. The encoded media information may include, but is not limited to, information associated with one or more of the following: a recipe profile, one or more beverage forming ingredients, and a beverage. Coded media that may store coded media information may include, but are not limited to: a thumb drive, a memory stick, a memory, a data storage device, or any device or method capable of transmitting data to a beverage forming dispenser. In one embodiment, a consumer may formulate one or more recipes and store the recipes on a coded media prior to providing input to the beverage forming dispenser.

Block 1802 is followed by block 1804 in which a recipe profile for the consumer is determined. In this embodiment, a processor or controller, such as 106 in fig. 1, associated with the product dispenser, such as 102A, may determine a consumer recipe profile based at least in part on input from a consumer, such as input from encoded media information provided by the consumer. The consumer formula profile may include, but is not limited to: a recipe profile, one or more beverage forming ingredients, and a beverage.

Block 1804 is followed by block 1806, wherein the beverage forming dispenser is configured according to a consumer's recipe profile. In this embodiment, a processor or controller, such as 106 in fig. 1, associated with the product dispenser, such as 102A, may configure the beverage forming dispenser, such as 102A, by preparing any number of beverage forming ingredient packages, valves, and pumps for dispensing a desired beverage from or associated with a consumer's recipe profile. In one embodiment, a consumer's recipe profile may enable a beverage forming dispenser to provide the consumer with one or more beverage recipes that the consumer has previously stored in the recipe profile.

Block 1806 is followed by block 1808 wherein the beverage is allowed to be dispensed to the consumer based at least in part on the consumer's recipe profile. In this embodiment, a processor or controller, such as 106 in fig. 1, associated with the beverage forming dispenser, such as 102A, may formulate and dispense one or more beverages based at least in part on a consumer's recipe profile.

Method 1800 ends after block 1808.

Referring to FIG. 19, an exemplary method 1900 of managing a list of consumer products or beverages is shown.

Method 1900 begins at block 1902. In block 1902, a consumer is identified. In this embodiment, a product dispenser, such as 102A in FIG. 1, may receive or otherwise obtain identification information associated with a consumer. Based at least in part on the identification information, a processor or controller, such as 106, associated with the product dispenser, such as 102A, can identify the consumer. This customer identification information may be by way of RFID, badge, card, loyalty card, personal identification code, PIN, customer wireless data processing device, and/or by way of other types and kinds of identification devices or methods as may be needed and/or desired in a particular embodiment.

In one embodiment, a consumer may provide a personal identification code, such as a PIN code, to a product dispenser via a client-type device or a wireless communication device, such as 214A-214C. In other embodiments, the consumer may provide a badge or magnetic card, and/or utilize other types and/or kinds of identification, as may be needed and/or desired in a particular embodiment.

Block 1902 is followed by block 1904, wherein the consumer's past product list is retrieved. In the illustrated embodiment, a processor or controller, such as 106 in fig. 1, associated with the product dispenser, such as 102A, may transmit the identification data to a local and/or remote server or data processing resource, such as 126. Based at least in part on the identification data, a local and/or remote server or data processing resource, such as 126, may obtain or otherwise determine a past list of products associated with the consumer. In one embodiment, a processor or controller, such as 126, may access an associated memory or data storage device, such as 110, to obtain or otherwise determine a past list of products associated with a consumer. The past product list may include, but is not limited to: a historical list of some or all of the previous or past products requested, ordered, dispensed, or otherwise obtained by a particular consumer from one or more product dispensers or other types of dispensers or devices. In any case, the product dispenser may be in data communication with a server or data processing resource locally and/or remotely to obtain a past product list of the consumer.

Block 1904 is followed by block 1906, wherein the next product for the consumer to try is determined from the past product list. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may determine at least one next product for the consumer to attempt based at least in part on a past list of products associated with the consumer. For example, a comparison of relative frequencies for one or more products or product formulations may be determined, and the next product for the consumer to try may be a relatively low or relatively high frequency of appearance on a past list of products based on the particular product or product formulation. In one embodiment, the next product for the consumer to try may not appear on the past product list. In one embodiment, based at least in part on the past list of products associated with the consumer, a local and/or remote server or data processing resource, such as 126, may determine at least one next product for the consumer to try. In any case, from the past list of products, the next products for the consumer to try can be determined.

Block 1906 is followed by block 1908, wherein the consumer is prompted for information regarding products that have been determined for the consumer to try. In the illustrated embodiment, a processor or controller, such as 106 in fig. 1, associated with the product dispenser, such as 102A, may generate or otherwise communicate a communication to the consumer prompting the consumer for information associated with a product that has been determined for the consumer to attempt. The processor or controller, such as 106, may provide a message to the consumer via an output device, such as a user interface, e.g., 112. Information associated with a product that has been determined for a consumer's attempt may include, but is not limited to: product name, nutritional benefits, a description of the type or kind of product or beverage, television guide programming, television advertisements, and/or other types and/or forms of information as may be needed and/or desired in a particular embodiment. In one embodiment, a local and/or remote server or data processing resource, such as 126, may generate a communication or other output, such as a message, and transmit the message to a product dispenser, such as 102A, for communication with the consumer, prompting the consumer for information associated with a product that has been determined for the consumer to attempt. In another embodiment, a local and/or remote server or data processing resource, such as 126, may generate a communication or other output, such as a message, and transmit the message to a consumer via a network, such as 104. The consumer may receive the message via a client type device, a mobile phone, a wireless communication device, or any other device or method. A processor or controller such as 106 associated with the product dispenser such as 102A may receive the message for transmission to the consumer. In any case, the consumer is prompted for information about the product that has been determined for the consumer to try.

Block 1908 is followed by decision block 1910, where a determination is made as to whether the consumer wishes to try the product. If the determination is positive, i.e., the consumer wishes to try the suggested product, the method 1900 continues to block 1914. If the determination is negative, i.e., the consumer does not wish to attempt the suggested product, the method 1900 continues to block 1912. In the embodiment illustrated in FIG. 19, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may determine whether the consumer wants to try the product. For example, a processor or controller, such as 106, may receive a consumer input or selection via a user interface, such as 112, and determine whether the input or selection corresponds to whether the consumer wants to try the product.

In block 1912, input is received from the consumer to select a product. In the illustrated embodiment, a processor or controller, such as 106 in fig. 1, associated with the product dispenser, such as 102A, may allow a consumer to select a product. For example, after the consumer has had an opportunity to select a suggested product or a product has been determined for the consumer to try, the consumer may decide or otherwise select to try a different product in place of the suggested product. The consumer may select different products via a user interface associated with the product dispenser, such as user interface, such as 112.

Following the block 1912 is a block 1916 where the product is dispensed. In the illustrated embodiment, a processor or controller, such as 106 in fig. 1, associated with a product dispenser, such as 102A, may allow a consumer to be dispensed a desired product.

Returning to block 1914, the consumer's past product list is updated with the current selection. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with a product dispenser, such as 102A, may update a past list of products associated with a consumer with a current product selection. For example, where the consumer does not select a product that has been determined for the consumer to try, the past product list may be updated so that the consumer will no longer be provided with that particular product. In one embodiment, a local and/or remote server or data processing resource, such as 126, may update the past product list associated with the consumer with the current product selection. In any event, the consumer's past product list is updated with the current selection.

Following the block 1914 is a block 1916, which has been described above.

After block 1916, the method 1900 ends.

In one embodiment, one or more consumers may enroll to try one or more different product formulations. For example, each time a consumer identifies himself or herself to the product dispenser, the corresponding consumer's past product listing history is retrieved. Once the past product listing history is retrieved, a determination is made to provide the consumer with a product or a formulation they have not previously attempted. The consumer may select to try the suggested party or product that has been determined for the consumer to try. When a suggested product formulation or a product that has been determined for the consumer to try is assigned to the consumer, it is added to the past product list so that it will not be provided to the consumer again. In another embodiment, the past product list may be modified such that suggested product formulations or products that have been determined for the consumer to try are provided less frequently or more frequently than other products or product formulations.

The capabilities of various embodiments of the present invention can be implemented in software, firmware, hardware or some combination thereof.

As one example, one or more aspects of the present invention can be included in an article of manufacture (such as one or more computer program products) having, for instance, computer usable media. The media has embodied therein, for instance, computer readable program code means for providing and facilitating the capabilities of embodiments of the present invention. The article of manufacture can be included as a part of a computer system or sold separately. An example of a suitable article of manufacture is a consumer interaction engine or module such as 114 depicted in FIG. 1.

Additionally, at least one program storage device readable by a machine, tangibly embodying at least one program or set of instructions executable by the machine to perform the capabilities of embodiments of the present invention can be provided. One example of a suitable program storage device readable by a machine is a memory or data storage device such as 110 depicted in FIG. 1.

The flow diagrams depicted herein are just examples. There may be many variations to these diagrams or the elements (or operations) described therein without departing from the scope of the invention as claimed. For example, elements may be performed in a differing order, or elements may be added, deleted or modified. All of these variations are intended to be part of the claimed invention.

While embodiments of the invention have been described, it will be understood that those skilled in the art, both now and in the future, may make various improvements and enhancements which fall within the scope of the claims which follow. These claims should be construed to maintain the proper protection for the invention first described.

Claims (24)

1. A product dispenser (102) comprising:

a user interface (112) operable to receive consumer input and provide product selection information;

a reader (106A) configured to obtain identification information associated with a consumer; and

a controller (106) in communication with the reader and user interface and operable to execute a set of instructions to:

receiving identification information associated with a consumer from the reader (106A);

retrieving consumer information based at least in part on the identifying information; and

providing product selection information at the user interface (112) based at least in part on the consumer information.

2. The dispenser (102) of claim 1, wherein the identifying information associated with the consumer is obtainable from at least one of: a user interface associated with the product dispenser, a machine readable code, information from an RFID tag, communication from a client-type device, or communication from a wireless communication device.

3. The dispenser (102) of claim 1, wherein the controller (106) is further operable to execute a set of instructions to:

one or more consumer preferences for storage on the wireless communication device (214) are communicated.

4. The dispenser (102) of claim 1, wherein the controller (106) is further operable to execute a set of instructions to:

assigning a reward to the consumer based at least in part on the identifying information.

5. The dispenser (102) of claim 1, wherein the controller (106) is further operable to execute a set of instructions to:

assigning a reward to the consumer based at least in part on a selection of at least one product by the consumer.

6. The dispenser (102) of claim 1, wherein the controller (106) is further operable to execute a set of instructions to:

outputting a benefit code operable to be redeemed by the consumer.

7. The dispenser (102) of claim 6, wherein the reward code is redeemable for at least one of: a website, a beverage dispenser, a vending machine, a transaction terminal, a retail store, or a store.

8. The dispenser (102) of claim 1, wherein the controller (106) is further operable to execute a set of instructions to:

determining a price for the product based at least in part on the consumer information.

9. The dispenser (102) of claim 1, wherein the controller (106) is further operable to execute a set of instructions to:

receiving instructions from the consumer to redeem the reward for the product; and

the selected product is dispensed based at least in part on whether an account associated with the consumer includes a predefined amount of reward or is assigned a particular status.

10. The dispenser (102) of claim 1, wherein the controller (106) is further operable to execute a set of instructions to:

assigning a specific product to a predefined group of consumers, wherein the predefined group of consumers has previously registered to be notified of the specific product or the predefined group of consumers enters a predefined reward code.

11. The dispenser (102) of claim 1, wherein the controller (106) is further operable to execute a set of instructions to:

customizing the user interface (112), wherein the product selection information comprises at least one of: news, weather, sports, finance, or information of interest to the consumer.

12. A method for operating a product dispenser, comprising:

receiving identification information associated with a consumer;

retrieving consumer information based at least in part on the identifying information; and

providing product selection information at a user interface (112) associated with the product dispenser (102) based at least in part on the consumer information.

13. The method of claim 12, wherein receiving identification information associated with the consumer comprises at least one of: receiving information via a user interface associated with the product dispenser, scanning a machine code, receiving information from an RFID tag, receiving a communication from a client-type device, or receiving a communication from a wireless communication device.

14. The method of claim 12, further comprising:

one or more consumer preferences are transmitted to the wireless communication device.

15. The method of claim 12, further comprising:

assigning a reward to the consumer based at least in part on the identifying information.

16. The method of claim 12, further comprising:

assigning a reward to the consumer based at least in part on a selection of at least one product by the consumer.

17. The method of claim 12, further comprising:

outputting, based at least in part on the consumer information, a reward code operable to be redeemed by a consumer, wherein the reward code is redeemable at least one of: a website, a product dispenser, a vending machine, a transaction terminal, a retail store, or a store.

18. The method of claim 12, further comprising:

determining a price for the product based at least in part on the consumer information.

19. The method of claim 12, further comprising:

receiving instructions from the consumer to redeem the reward for the product; and

the selected product is dispensed based at least in part on whether an account associated with the consumer includes a predefined amount of reward or is assigned a particular status.

20. The method of claim 12, further comprising:

assigning a specific product to a predefined group of consumers, wherein the predefined group of consumers has previously registered to be notified of the specific product or the predefined group of consumers enters a predefined reward code.

21. The method of claim 12, further comprising:

customizing the user interface (112), wherein the product selection information comprises at least one of: news, weather, sports, finance, or information of interest to the consumer.

22. The dispenser (102) of claim 1 or the method of claim 12, wherein the consumer information comprises at least one of: consumer preferences, recipes, recipe lists, customized product ingredient lists, past product lists, or product lists.

23. The dispenser (102) of claim 1 or the method of claim 12, wherein the product selection information comprises at least one of: a price of a product, an option to purchase a product for another user, a survey, a list of selectable product ingredients, a formula that is only available at the product dispenser, a promotional formula, a consumer formula, a traditional beverage or product, or a customized beverage or product.

24. A method for operating a product dispenser (102), comprising:

receiving identification information associated with a consumer;

retrieving consumer information based at least in part on the identifying information;

customizing product selection information at a user interface (112) associated with the product dispenser (102) based at least in part on the consumer information; and

updating the consumer information based at least in part on the selected product.