HK1148098B - Systems and methods for facilitating consumer-dispenser interactions - Google Patents

Description

System and method for facilitating consumer interaction with a dispenser

Trade mark

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

Technical Field

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

Background

Conventional beverage dispensers may fill a beverage by combining syrup, sweetener, and/or water. To create a limited variety of beverage options, different types of syrups may be provided. Typically, this results in the ability to offer a limited number of branded and non-branded beverage options. For example, a single prior art dispenser using several different types of syrups may be able to provide COCA-COLA^TM、DIETCOCA-COLA^TM、SPRITE^TMAnd several other branded 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. As such, conventional beverage dispensers are limited in their ability to provide consumers with the beverage they desire. In this regard, consumers desire a richer menu of beverage choices and the ability to customize their beverages. Studies have shown that they require more beverage variation, even for traditional brands of beverages. For example, COCA-COLA is provided^TMCOCA-COLA containing lime^TM、CHERRY COCA-COLA^TM、VANILLA COCA-COLA^TMAnd many other types of COCA-COLA^TMThe beverage changes. In part due to the limited capacity and selection function of conventional beverage dispensers, such as the COCA-COLA in conventional beverage dispensers^TMIs impractical to provide all possible variations. It does not provide the consumer with a complete selection of brands and non-brands of beverages that the consumer wants, i.e., all types.

Summary of The Invention

Some or all of the above needs and/or problems may be addressed by embodiments of the present invention. Certain embodiments of the invention may include systems and methods for facilitating consumer interaction with a dispenser. In one embodiment, a product dispenser is provided. The product dispenser may include a reader configured to read machine readable items (machine readable items). Additionally, the product dispenser may include a controller in communication with the reader, and the controller may be operable to execute a set of instructions to receive information from a machine-readable item associated with the consumer via the reader. Additionally, the controller is further operable to execute a set of instructions to configure the at least one feature based at least in part on information from the machine readable item and dispense the product.

In one embodiment, a method for operating a product dispenser may be provided. The method may include receiving information from a machine readable item associated with a consumer. Additionally, the method may include configuring at least one characteristic based at least in part on information from the machine readable item. Further, the method may include dispensing the product.

In another embodiment, a method for operating a product dispenser may be provided. The method may include receiving product selection information from a consumer. Additionally, the method may include providing promotional information to the consumer based at least in part on the product selection information. Additionally, the method may include dispensing the product.

In yet another embodiment, a method for operating a product dispenser may be provided. The method may include receiving information associated with a consumer. Based at least in part on the information associated with the consumer, the method may identify whether a business partner associated with the consumer exists. Additionally, the method may include dispensing the product based on the determination of whether the business partner is present.

Additional systems, methods, distributors, features and aspects may be realized through the techniques of various 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 description and the drawings.

Brief description of the 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 foregoing and other objects, features, and aspects of the 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 in accordance with an embodiment of the present invention.

Fig. 2 illustrates an example of a consumer dietary network (refreshment network) in accordance with an embodiment of the present invention.

FIG. 3 illustrates an example of an enhanced view graphical user interface in accordance with an embodiment of the present invention.

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

Fig. 5-6 illustrate an exemplary method of allowing a consumer to select a product side and portion size (contribution size) and implement a promotional offer (promotional offer) according to an embodiment of the invention.

FIG. 7 illustrates an exemplary method of scanning machine-readable icons to configure a product dispenser in accordance with embodiments of the present invention.

FIG. 8 illustrates one exemplary method of allowing a consumer to order a product and then scan a machine readable item on a product dispenser to effect order completion by the product dispenser, in accordance with embodiments of the present invention.

FIG. 9 illustrates an example method of limiting the number of refill times for a product, in accordance with an embodiment of the present invention.

FIG. 10 illustrates an example method of combining promotional offers for a phone card and/or wireless phone with product transactions, in accordance with embodiments of the present invention.

FIG. 11 illustrates an example method of combining promotional offers associated with products from a product dispenser, in accordance with an embodiment of the present invention.

FIG. 12 illustrates an example method of allocating free products to a consumer while the consumer pays for Internet access in accordance with an embodiment of the present invention.

FIG. 13 illustrates an example method of a consumer using a product dispenser and adjusting a business partner account to pay for a product in accordance with an embodiment of the present invention.

FIG. 14 illustrates an exemplary method of using portion control for a child-sized and sample-sized cup in accordance with an embodiment of the present invention.

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 forming dispenser," "product dispenser," "beverage dispenser," "dispenser apparatus," and "dispenser" refer to an apparatus that dispenses a product, such as a beverage, can, bottle, or container.

As used herein, the terms "product" and "beverage" and plural forms thereof are used synonymously, and embodiments of the invention should not be limited in scope by the use of either term.

Turning now to a more detailed illustration, an example system 100 for a product dispenser according to an embodiment of the present invention is shown in FIG. 1. The example system, e.g., 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, e.g., 102A, is shown in communication with a communication network, e.g., 104. In this embodiment, at least one product dispenser, such as 102A, may interface with a consumer, customer, or other user. Other example environments or systems for product dispensers according to embodiments of the present invention may include non-network configurations.

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

Each product dispenser, e.g., 102A, may include a processor or controller 106, an identification reader/scanner device 106A, an ingredient matrix (ingredient matrix)108, a computer readable medium, e.g., Random Access Memory (RAM)110, coupled to the processor or controller 106, and an input/output device, e.g., a display device 112. The processor or controller, e.g., 106, may execute computer-executable program instructions stored in a memory, e.g., 110. The computer-executable program instructions stored in the memory, e.g., 110, may include any number of modular applications, e.g., consumer interaction engines or modules, e.g., 114. The consumer interaction engine or module, such as 114, may be adapted to implement various methods of consumer-dispenser interaction. Additionally, the consumer interaction engine or module, e.g., 114, may be adapted to receive one or more signals from one or more consumers, remote and/or local servers or data processing resources, as well as client type devices or wireless communication devices. Other examples of functions and aspects of embodiments of the consumer interaction engine or module, e.g., 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 devices 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, e.g., 106, may communicate with a component matrix, e.g., 108, to control, monitor and track the addition, flow and removal of some or all of the components to or from the matrix, e.g., 108. The ingredient matrix may be, for example, a series of containers or fixtures capable of receiving or mounting to individual product ingredient packages or other product ingredient supplies. For example, the product component packs, e.g., 116A, may be fabricated as liquid pouches secured in plastic ridged containers to allow insertion into the component matrix, e.g., 108. When inserted into the ingredient matrix, e.g., 108, the bag, e.g., 116A, or pouch, may be pierced by at least one associated fitment, which allows the liquid within the bag, e.g., 116A, or pouch, to be pumped out, or otherwise metered by the controller, e.g., 106, or matrix, e.g., 108, and associated equipment in precise proportions to form a desired product, e.g., a beverage. In one embodiment, one or more product component packages, e.g., 116A-116Q, may be inserted into a component matrix, e.g., 108. In this embodiment, the ingredient matrix, e.g., 108, may secure some or all of the product ingredient packages, e.g., 116A-116Q. In one embodiment, one or more product packages, e.g., 116O, 116P, 116Q, may be supplied directly rather than in package form. For example, a product package such as 116O may be a continuous supply of carbonated water provided by a carbonated water source; product packages such as 116P may be sweeteners provided by sweetener sources, such as non-nutritive sweeteners (NNS) or High Fructose Corn Syrup (HFCS); and 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, compositions, or product additives may be in the form of pouches, or may be in other configurations suitable for access by a matrix of ingredients, such as 108.

In the embodiment shown in FIG. 1, a product dispenser, e.g., 102A, having a matrix of ingredients, e.g., 108, may include one or more machine code readers, e.g., 118A-118Q, using machine code technology, e.g., bar codes, RFID, reflected light frequencies, optical, etc. In one embodiment, at least one machine readable code reader, e.g., 118A-118Q, may be associated with a location associated with an ingredient matrix, e.g., 108, wherein some or all product ingredient packages, e.g., 116A-116Q, may be scanned, read, or otherwise identified prior to being inserted into or connected to the ingredient matrix, e.g., 108. In this regard, a processor or controller, e.g., 106, may receive or retrieve information related to some or all of the product component packages, e.g., 116A-116Q, and use such information to identify an optimal or other desired location in the component matrix, e.g., 108, for placement of the product component package, e.g., 116A, in the component matrix, e.g., 108. For example, data from a product component package, e.g., 116A, may be read, scanned, or identified from a serial number or identification code associated with the product component package, e.g., 116A. Such data may be used alone or in association with information previously stored in at least one database, such as 128A-128C described below, or in association with data that may be otherwise acquired or stored by a data processing resource or server, such as 126, described below, which may identify one or more ingredients associated with a product ingredient package, such as 116A, for example. In another example, the data from the product component package, e.g., 116A, can be a component code or identifier, and can be used alone or associated with information previously stored in a database, e.g., 128A-128C described below, or with data that can be otherwise acquired or stored by a data processing resource or server, e.g., 126, that can identify one or more components associated with the product component package, e.g., 116A.

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

In one embodiment, an ingredient matrix, e.g., 108, may have a plurality of product ingredient packages, e.g., 116A-116Q, inserted therein, wherein each package may contain a different or unique ingredient. Through the slaveVarious ratios of ingredients from some or all of the product ingredient packages, e.g., 116A-116Q, may be selectively combined by a processor or controller, e.g., 106, to one or more commands or instructions to one or more pumps, e.g., 120, and/or valves, e.g., 122, associated with the ingredient matrix, e.g., 108, to form various types of products, e.g., beverages. Example ingredients may include, but are not limited to, flavorings, concentrates, syrups, sweeteners, water, carbonated water, lime flavorings, vanilla flavorings, CHERRY flavorings, and branded or non-branded beverages such as CHERRY COCA-COLA^TM、VANILLA COCA-COLA^TM、COCA-COLA^TM、DIET COCA-COLA^TMAnd FANTA^TMAny of the component parts of (a).

In one embodiment, one or more product component packs, e.g., 116A-116Q, can contain components known as "pungency" (which can limit their placement in a matrix of components, e.g., 108). The spicy component may be relatively strong such that once the spicy component is pumped or drawn through a particular portion of the product dispenser, e.g., 102A, any associated pathway through the dispenser, e.g., 102A, such as a tube in the product dispenser, e.g., 102A, may be permanently flavored and any subsequent component or fluid pumped or drawn through the pathway or tube may be tainted with the flavor of the spicy component. Thus, once a spicy type ingredient is used in an ingredient matrix such as 108, an associated processor or controller such as 106 may track or otherwise store information that controls or limits the replacement and/or addition of other spicy ingredients to certain locations in the ingredient matrix such as 108 to avoid mixing spicy type ingredients or staining non-spicy ingredients to maintain the quality of the product or beverage.

In another embodiment, one or more product component packs, e.g., 116A-116Q, may require shaking to keep the relevant components well mixed. In such a case, the location of such components in the component matrix, e.g., 108, may be limited to locations in the component matrix, e.g., 108, that may be needed and/or desired to be panned 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 tube or dispenser piece. Such ingredients may include, but are not limited to, milk, dairy products, soy sauce, and/or other types and kinds of product ingredients. In such cases, the location of such components in the component matrix, e.g., 108, may be limited to the location of the appropriate antimicrobial tubes and/or dispenser parts in the component matrix, e.g., 108, as may be needed and/or desired with a particular implementation.

In yet another embodiment, a one-to-one relationship may be established between a particular product component package, e.g., 116A, and at least one pump and/or valve, e.g., 120 and/or 122, respectively. In some cases, the use of more than one pump and/or valve for a single product ingredient package, e.g., 116A, may draw a relatively high volume of the ingredient from the package, e.g., 116A, in a relatively short period of time. For example, a product component package containing a sweetener, such as sweetener e.g., 116P, may use 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, e.g., 102A-102N, may also be in communication with a network, e.g., 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 both a sound signal and a data signal including an image data signal or a multimedia signal. Other networks may include, but are not limited to, the internet, a Local Area Network (LAN), a Wide Area Network (WAN), a LON WORKS network, a wired network, a wireless network, or any combination thereof.

The network, e.g., 104 in FIG. 1, is also shown in communication with at least one data processing resource, e.g., server 126, and at least one database, e.g., 128A. In this embodiment, the server, e.g., 126, may be a processor-based device capable of communicating with some or all of the product dispensers, e.g., 102A-102N, via the communication network, e.g., 104, in signals, e.g., radio frequency signals or direct wired communication signals. Additionally, data processing resources or servers such as 126 may be used to assist or facilitate recipes, formulations, methods of making products or beverages, provide operational data processing, perform data processing related to consumer interaction, and/or perform other data processing as may be needed and/or desired in a particular embodiment. Such operational data processing may include, for example and without limitation, device status, maintenance, service reminders, pre-restore (predictive restore), and/or other types and kinds 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, customizations, and/or other types and kinds of consumer interaction and/or data processing support that may be needed and/or desired for a particular implementation.

The server, e.g., 126 in fig. 1, may include a processor, e.g., 130, and a computer-readable medium, e.g., Random Access Memory (RAM)132, coupled to the processor 130. The processor, e.g., 130, may execute computer-executable program instructions stored in the memory, e.g., 132. The computer-executable program instructions stored in the memory, e.g., 132, may include any number of modular applications, e.g., a consumer interaction engine or module similar to 114. A consumer interaction engine or module similar to 114 may be adapted to implement various methods of 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 examples of the functionality and aspects of embodiments of the 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 databases, such as databases of recipes, and methods of making products or beverages, 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 product or beverage formulation, and method of making the product or beverage. Such product or beverage formulations, methods of making products or beverages can include ingredient lists, ratios of each ingredient, lists of how the product or beverage can be customized by the consumer, and/or other types and kinds of product or beverage formulations, methods of making products or beverages that may be needed and/or desired for a particular implementation.

An example 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 without limitation, a user, such as a consumer, may make a product or beverage type selection on a product dispenser, such as 102A, via an input/input device, such as display device 112. An associated processor or controller, e.g., 106, may facilitate user selection of a particular recipe to form a selected product, e.g., a beverage, via a display device, e.g., 112. The processor or controller, e.g., 106, may display one or more products or beverages for selection via a display device, e.g., 112. A user may use the display device, e.g., 112, to select at least one product or beverage, e.g., by pressing a button provided by or associated with the display device, e.g., 112. The processor or controller, e.g., 106, may retrieve information from a local memory, e.g., 110, or may communicate with at least one database, e.g., 104, over a network, e.g., or may communicate with at least one data processing resource, e.g., server 126, to retrieve the respective ingredients and/or proportions of ingredients used to form the selected product or beverage. The processor or controller, e.g., 106, may use the information to operate one or more pumps, e.g., 120, and/or valves, e.g., 122, to form and dispense a product or beverage through a nozzle, e.g., 124, into a cup or other container, e.g., 136.

In another embodiment, a user, such as a customer or package installer, may assist in scanning or reading one or more product component packages, such as 116A-116Q, as the packages 116A-116Q are inserted into the component matrix, such as 108, associated with the product dispenser, such as 102A. A processor or controller, e.g., 106, associated with the product dispenser, e.g., 102A, may identify the best or selected location in the composition matrix, e.g., 108. A user, customer, or package installer may know where a particular product component package, e.g., 116A, may be placed in a component matrix, e.g., 108, by way of an input/output device, e.g., a display device, e.g., 112. Examples 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, e.g., 116A, into an ingredient matrix, e.g., 108, may be checked or otherwise verified by scanning the machine-readable code on the corresponding package, e.g., 116A, and scanning the machine-readable code located on the ingredient matrix, e.g., 108, at the insertion point (shown as 118A). In this regard, the associated processor or controller, e.g., 106, may check or verify that the product component package, e.g., 116A, is properly placed in the component matrix, e.g., 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 shown in FIG. 1 mounted on the cup. In some embodiments, the identifying information may be associated with the consumer by, for example, an RFID or other machine readable tag similar to 138 contained or otherwise attached to an icon or other object. A reader, such as an RFID or other machine readable code reader, e.g., 140, associated with the product dispenser, e.g., 102A, may receive or otherwise obtain identification information from an RFID or other machine readable tag similar to 138. As shown in fig. 1, a processor or controller, e.g., 106, associated with a product dispenser, e.g., 102A, may be in communication with an RFID or other machine readable reader, e.g., 140, and some or all of the identification information obtained from the RFID or other machine readable tag, e.g., 138, may be stored or otherwise processed by the processor or controller, e.g., 106. In this embodiment, the identification information may be embedded in a machine readable code, bar code, RFID, radio frequency, infrared or other wireless communication method or device, or other types and kinds of encoding and/or storage techniques as may be needed and/or desired in a particular embodiment. The RFID readers or machine-readable code readers such as 140 may be respective devices that read or receive identification information from RFID or other machine-readable tags such as 138, and may include RFID read/write devices, infrared devices, magnetic card readers, bar code readers, or other suitable reader or receiver technology as may be needed and/or desired in a particular implementation.

In yet another embodiment, a server or transaction processing resource, such as 126, may facilitate payment or payment processing when a consumer selects and attempts to pay for a product, such as a beverage, on a product dispenser, such as 102A. The associated processor or controller, e.g., 106, may receive the consumer's payment or related information before, during, or after selection of a particular product or beverage, e.g., by way of a display device, e.g., 112, data transmission, or other input. In any case, the processor or controller, e.g., 106, may transmit payment or related information to a server or transaction processing source, e.g., 126, over a network, e.g., 104. The server or transaction processing source, 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 authorize or otherwise confirm payment or related information prior to accepting payment from or otherwise dispensing a selected product or beverage for a consumer.

Referring to fig. 2, an example consumer dietary environment or system 200 is illustrated. In one embodiment, one or more networked product dispensers, such as 210, may be installed in a plurality of respective locations, such as location 202, respectively, and may communicate with a server or data processing resource, 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. By way of example, the product dispenser 210 may be similar to the beverage dispenser or dispenser device depicted in FIG. 1 as 102A. In one example, a product dispenser, such as 210, may include some or all of the following components with respect to FIG. 1: an ingredient matrix, e.g., 108, having locations operable to receive one or more packages of product ingredients, e.g., 116A-116Q, a controller, e.g., 106, one or more package insertion detection devices or RFID readers/writers, e.g., 118A-118Q, a pump, e.g., 120, a valve, e.g., 122, and a nozzle, e.g., 124. By way of further example, the server or data processing resource 206 may be similar to the server or data processing resource depicted as 126 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, the consumer, e.g., 212, may register, set consumer preferences, access corresponding accounts, receive promotions, manage loyalty accounts (loyaltyccount), and/or register for 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 network 104, or a consumer's dietary network system, such as 200, and/or a product dispenser, such as 210, by 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 other types and kinds of data processing, processor-based, or client-type devices. Examples of wireless communication devices may include, but are not limited to, wireless data processing devices, wireless telephones, mobile telephones, IPHONEs^TM、IPOD^TMPersonal data assistant, and/or POCKET PC^TM。

Referring to FIG. 3, an example of an enhanced view graphical user interface 300 is illustrated. In one illustrated 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. The user interface, e.g., 300, can be used, e.g., by a consumer, e.g., 212, to select any number of different product or beverage types, categories, and formulations. In use, a product dispenser, e.g., 210, with an enhanced view graphical user interface, e.g., 300, can provide a consumer with selectable product or beverage options in a series of dynamically generated menus, wherein the consumer can locate and select a specific brand, category, type and/or formulation of a desired corresponding product or beverage. Once a particular product or beverage option is selected, the consumer may cause the corresponding product or beverage to be dispensed and dispensed by the product dispenser.

Referring to FIG. 4, another example of a user interface is shown. In one embodiment, a product dispenser, such as 210 in FIG. 2, may include a classic view graphical user interface, such as 400. The user interface, e.g., 400, may be used by a consumer, e.g., 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 corresponding product or beverage to be dispensed and dispensed by the product dispenser. In some embodiments, a classic type graphical user interface may also be referred to as a traditional view because it generally resembles a traditional sprinkler dispensing valve design. Thus, a classic type of 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 selection, for example, of a plurality of different types of products or beverages. In such cases, a classic view graphical user interface may be displayed having relatively fewer, more traditional product or beverage selections, and including one or more traditional types of product or beverage selections, to facilitate and sometimes expedite consumer interaction with the product dispenser.

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, essentially creating a consumer customized classic view graphical user interface. In this particular embodiment, the consumer may create a consumer customized classic view graphical user interface. 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-14 are example 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 of the related components shown in fig. 1-4.

Referring to fig. 5-6, example methods 500, 600 of consumer interaction with a dispenser are illustrated. In the embodiment shown in FIG. 5, the product dispenser may allow a consumer to select a product side and portion size, and the dispenser may implement a promotional advantage. The method 500 begins at block 502. At block 502, input from a consumer is received to select a product formulation on a product dispenser. In the embodiment shown in FIG. 5, the consumer may enter data via a user interface, such as 112 in FIG. 1, such as selection of an indicator corresponding to a product formulation, such as DIET CHERRY COKE^TM. In other embodiments, other products or product parties may be selected by the consumer, or other data associated with one or more product selections or parties may be entered by the consumer. For example, a consumer may enter data corresponding to one or more product ingredients, such as sweeteners, vitamins, or other components of a product formulation. In one embodiment, product selection may be accomplished by way of a graphical user interface associated with the product dispenser.

In block 504 following block 502, input from the consumer is received to select a portion size. In the illustrated embodiment, the consumer may enter data, such as a selection of an indicator corresponding to a serving size, such as 10 fluid ounces, through a user interface, such as 112 in FIG. 1. Portion size selections may include, but are not limited to, any number of fluid ounces, depending on product size specifications such as child, small, medium, large, extra large, and/or according to other methods as needed and/or desired in a particular embodiment. In other embodiments, other serving sizes may be selected by the consumer, or other data associated with one or more serving sizes may be entered by the consumer.

In block 506 following block 504, input from the consumer is received to pay for the selected product. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may prompt the consumer to pay for the selected product. For example, a processor or controller such as 106 may prompt the consumer to pay by any monetary or financial transaction device or method, such as a method of receiving a credit or debit card or account number. Payment for the selected product may be through a cashless or currency-based transaction. In one embodiment, the consumer may be provided with the option to pay for the product via a client type device or a wireless communication device, such as 214A-214C in FIG. 2. In this particular embodiment, the consumer may pay for the selected product by authorizing payment via a client type device or wireless communication device, e.g., 214A-214C, which may be received by the associated network, e.g., 104. In any event, the consumer is allowed to pay for the selected product.

In block 508, following block 506, the product is dispensed. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may allow the consumer to dispense the product they desire.

The method 500 ends after block 508.

In one embodiment, the consumer may select a product formulation and portion size and a promotional offer may be implemented. For example, the consumer may select a product formulation and a portion size, where the portion size is the volume (typically small, medium, or large) desired by the consumer. The consumer may then be allowed to pay for the product.

In another embodiment, in addition to allowing the consumer to select product side and portion size, promotional offers may be provided to the consumer based in part on the consumer's selection. In this regard, consumers may be provided the option of increasing the size of the product they want or changing the selected party to a new party.

FIG. 6 illustrates another method 600 of a consumer interacting with a dispenser. The method 600 begins at block 602. At block 602, input from a consumer is received to select a product formulation on a product dispenser. In the embodiment shown in FIG. 6, the consumer may enter data via a user interface, such as 112 in FIG. 1, for example, selecting and product formulation, such as DIET CHERRY COKE^TMA corresponding indicator. In other embodiments, other products or product parties may be selected by the consumer, or other data associated with one or more product selections or parties may be entered by the consumer. For example, a consumer may enter data corresponding to one or more product ingredients, such as sweeteners, vitamins, or other components of a product formulation. In one embodiment, product selection may be accomplished through a graphical user interface associated with the product dispenser.

In block 604 following block 602, input from the consumer is received to select a portion size. In the illustrated embodiment, the consumer may enter data, such as a selection of an indicator corresponding to a portion size, such as 10 fluid ounces, through a user interface, such as 112 in fig. 1. Portion size selections may include, but are not limited to, any number of fluid ounces, depending on product size specifications such as child, small, medium, large, extra large, and/or according to other methods as may be needed and/or desired in a particular embodiment. In other embodiments, other serving sizes may be selected by the consumer, or other data associated with one or more serving sizes may be entered by the consumer.

In block 606 following block 604, the consumer is alerted to the promotional offer based at least in part on the selected product and/or the selected portion size. 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 transmit a communication to the consumer to prompt the consumer for a promotional offer based at least in part on the selected product and/or the selected portion size. For example, the processor or controller, e.g., 106, may provide the message and associated prompts to the consumer via an output device, e.g., a user interface, e.g., as 112. 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 product dispenser, such as 102A, for communication with a consumer. A processor or controller, e.g., 106, associated with the product dispenser, e.g., 102A, can receive the message to communicate with the consumer. In any case, the consumer is prompted with a promotional offer based at least in part on the selected product and/or the selected serving size.

In block 608 following block 606, a determination is made as to whether the consumer accepts the promotional offer. If the determination is positive, that is, the consumer accepts the promotional offer, the method 600 continues to block 610. If the determination is negative, that is, the consumer does not accept the promotional offer, the method 600 continues to block 612. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may determine whether the consumer accepts the promotional offer. For example, a processor or controller, such as 106, may receive consumer input or selections via a user interface, such as 112, and determine whether the input or selection corresponds to whether the consumer accepts promotional offers.

At block 610, the product type and/or variety of the party and/or portion size of the product is adjusted based on the promotional offer accepted by the consumer. In the illustrated embodiment, a processor or controller, e.g., 106 in FIG. 1, associated with the product dispenser, e.g., 102A, may adjust the manufacturer's product type and/or portion size of the product based at least in part on the promotional offer accepted by the consumer.

Block 612 following block 610 is described in detail below.

At block 612, input from the consumer is received for payment of the selected product. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may prompt the consumer to pay for the selected product. For example, a processor or controller such as 106 may prompt the consumer to pay by any monetary or financial transaction device or method, such as a method of receiving a credit or debit card or account number. Payment for the selected product may be through a cashless or currency-based transaction. In one embodiment, the consumer may be provided with an option to pay for the product via a client type device or a wireless communication device, such as 214A-214C in FIG. 2. In this particular embodiment, the consumer may pay for the selected product by authorizing payment via the client device or wireless communication device, e.g., 214A-214C, and the payment may be received over the associated network, e.g., 104. In any event, the consumer is allowed to pay for the selected product.

In block 614, following block 612, the price is adjusted based on the promotional offer accepted 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, can adjust the price for the selected product based at least in part on the promotional benefits accepted by the consumer.

In block 616, following block 614, the product is dispensed. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may allow the consumer to dispense the product they desire.

The method 600 ends after block 616.

In one embodiment, once the consumer makes a selection of a product formulation and portion size, a promotional offer based on the consumer's selection may be determined. In this regard, the consumer may be prompted with a promotional offer to request the consumer's response before allowing the product to be dispensed. Such promotions may include, but are not limited to, promotions to increase portions, change selected product formulations, and/or other types and/or kinds of promotions as needed and/or desired in a particular embodiment.

Referring to fig. 7, an example method 700 of scanning a machine-readable icon to configure a product dispenser is provided. The method 700 begins at block 702 where a machine-readable item or icon is read or scanned at block 702. In this embodiment, a consumer may scan a machine readable item or icon near a product dispenser, such as 102A in fig. 1, which may be configured to detect the presence of the machine readable item or icon, or otherwise receive information associated with the presence of the machine readable item or icon. The machine readable items or icons may include any number of wireless technologies including, but not limited to, RFID, radio frequency, infrared, or other wireless communication methods as may be needed and/or desired in a particular embodiment. Machine readable items or icons may be placed on, for example, product packaging, printed advertisements, RFID tags, wireless data processing devices, and/or other types and/or kinds of items as may be needed and/or desired in a particular embodiment.

In block 704, following block 702, the product dispenser is configured based at least in part on information associated with the machine readable item or icon that was scanned or read. In this embodiment, a processor or controller associated with the product dispenser, such as the controller 106 in FIG. 1, may receive or otherwise obtain information associated with the machine readable item or icon. Based at least in part on the information associated with the machine readable item or icon, the processor or controller, e.g., 106, the product dispenser, e.g., 102A, may configure one or more dispenser parameters. Dispenser parameters may include, but are not limited to, product type, serving size, and price, such as free drinks.

In block 706 following block 704, the product type and/or type, portion size and/or price is set. In this embodiment, a processor or controller associated with the product dispenser, such as controller 106 in fig. 1, may set one or more dispenser parameters for dispensing the product.

In block 708 following block 706, input from the consumer is optionally received for payment of the product. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with a product dispenser, such as 102A, may prompt a consumer to purchase a product. For example, a processor or controller such as 106 may prompt the consumer to pay by any monetary or financial transaction device or method, such as a method of receiving a credit or debit card or account number. Payment for the selected product may be through a cashless or currency-based transaction. In one embodiment, the consumer may be provided with the option to purchase the product via a client type device or a wireless communication device, such as 214A-214C in FIG. 2. In this particular embodiment, the consumer may pay for the selected product by authorizing payment via a client type device or wireless communication device, e.g., 214A-214C, which may be received over an associated network, e.g., 104. In any event, the consumer is allowed to purchase the product.

In block 710, following block 708, the product is dispensed. In the illustrated embodiment, a processor or controller, such as 106 in fig. 1, associated with the product dispenser, such as 102A, may allow the consumer to dispense the product.

The method 700 ends after block 710.

In one embodiment, the machine readable item or icon may be placed on product packaging, printed advertising, or associated with other objects that may be carried or otherwise accessed by the consumer. In this regard, a suitable machine readable item or icon may be a bar code or other machine readable code. Additionally, suitable machine readable items or icons may be RFID tags or other devices capable of wireless data communication with the product dispenser. In operation, a consumer may scan machine readable items or icons on a product dispenser. The product dispenser may then dynamically configure itself to dispense a particular product that is associated or otherwise directed by the machine readable item or icon.

In one embodiment, a consumer may scan a product dispenser for a printed advertisement containing a machine readable item or icon from a magazine. The machine readable item or icon may instruct the product dispenser to dispense a certain product formulation to the consumer. Such machine readable items or icons may be used in promotions, such as attempting to spam advertising campaigns for new product parties that are available for free or at a reduced price. Additionally, machine readable items or icons may be used to speed up or otherwise facilitate consumer selection at the product dispenser. In this regard, the consumer need only scan the machine readable items or icons to facilitate the preparation and dispensing of a particular product at the product dispenser.

Referring to FIG. 8, an example method 800 for a consumer to interact with a dispenser is illustrated. The method 800 begins at block 802. At block 802, input from a consumer for at least one product is received. In this embodiment, the consumer may place an order for at least one product at an order station. The ordering station may be located at a check-in machine at a quick-service restaurant, at a convenience-store checkout lane, and/or other types and/or kinds of ordering stations as may be needed and/or desired in particular embodiments. For example, the ordering station may be configured with at least one client type device or wireless communication device, such as 214A-214C in FIG. 2, to receive an order for at least one product. A customer or person associated with the order station may enter data corresponding to an order for at least one product through a client type device or wireless communication device, e.g., 214A-214C.

At block 804, following block 802, a machine readable icon or item is provided to the consumer. At least one machine readable icon or item may be provided or otherwise obtained by the customer during or after the order is submitted. Machine readable icons or items may include, but are not limited to, receipts with bar codes or other machine readable codes, RFID tagged items, items associated with RFID tags, items with wireless communication devices, and/or other types of items with associated wireless communication devices. The machine readable icons or items may include any number of wireless technologies including, but not limited to, RFID, radio frequency, infrared, or other wireless communication methods as may be needed and/or desired in a particular embodiment.

Following block 804, in block 806, the consumer scans the machine readable icon or item on the product dispenser. In this embodiment, the consumer may scan a machine readable icon or item in proximity to the product dispenser, e.g., 102A. It may be configured to detect the presence of a machine-readable icon or item, or otherwise receive information associated with the presence of a machine-readable icon or item. For example, the product dispenser may be configured to include an RFID reading/writing device, such as the identification reader/scanner device 106A, capable of detecting the presence of, or otherwise receiving information associated with, the presence of machine-readable icons or items associated with RFID tags. In any case, the machine readable icon or item may include data that may be received by the product dispenser as the machine readable icon or item is scanned or read on the product dispenser.

In block 808, following block 806, the product dispenser obtains the customer's order. In this embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may communicate with a local and/or remote processor, controller, server, or data processing resource, such as 126, memory, or data storage device, such as 110, to obtain information related to the customer order based at least in part on data derived from scanning the machine-readable icon or item. The data obtained from scanning the machine-readable icon or item may include, but is not limited to, product type information, product identification information, and other information associated with the product and/or item. For example, when a product dispenser, such as 102A, receives data from scanning machine readable icons or items, an associated processor or controller, such as 106, may access an associated memory or data storage device, such as 106, to retrieve information associated with a customer order. In another example, a local and/or remote processor, controller, server, or data processing resource, such as 216, may access an associated memory or data storage device, such as 110, to retrieve information associated with a customer order.

In decision block 810, following block 808, a determination is made as to whether the consumer is entitled to the product. If the determination is positive, that is, the consumer is entitled to the product, the method 800 continues to block 812. If the determination is negative, that is, the consumer is not entitled to the product, then the method 800 ends. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, may determine whether the consumer is entitled to the product. For example, the controller, such as 106, may determine whether the consumer is entitled to the product by obtaining information associated with the consumer order and determining whether predetermined criteria are met, such as whether the consumer order is valid or whether a full payment is made. In one embodiment, a processor or controller, such as 106, may communicate with local and/or remote servers or data processing resources, such as 126, which may determine whether the consumer is entitled to the product. In any event, a determination is made as to whether the consumer is entitled to the product.

At block 812, the product dispenser is configured to allow a consumer to select and dispense a product. In this embodiment, a processor or controller associated with the product dispenser, such as controller 106 in fig. 1, may configure one or more dispenser parameters to allow a consumer to select and dispense a product. Dispenser parameters may include, but are not limited to, product type, category, product formulation, portion size, and price. For example, a consumer may be allowed to select a product formulation, and optionally, a portion size, via a user interface associated with the product dispenser, such as user interface e.g., 112. In some cases, the product dispenser may allow the consumer to set a price, or the price may depend on any dispenser parameter selected by the consumer, such as product type, category, product formulation, or portion size.

In block 814, following block 812, the product is dispensed. In the illustrated embodiment, a processor or controller, such as 106 in fig. 1, associated with the product dispenser, such as 102A, may allow the consumer to dispense the product.

In block 816, the product dispenser updates the customer's order indicating the status of the dispensed product. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may update the customer's order indicating the status of the dispensed product. For example, a customer order may be updated such that the status of the order may reflect changes or new data associated with the dispensed product, including, but not limited to, the type or category of the product, portion size, and price. In one embodiment, a local and/or remote server or data processing resource, such as 126, may update the customer's order indicating the status of the product being dispensed. In one embodiment, the product dispenser may update the customer's order indicating that a product has been dispensed. Additionally, any status, configuration, product formulation, portion size, price, and/or other types and/or kinds of information and other data may be communicated and updated as may be needed and/or desired in a particular implementation. In any event, product dispenser data may be transmitted to update the customer's order, indicating the status of the product being dispensed.

The method 800 ends after block 816.

In one embodiment, the consumer may place an order including a product at a counter or elsewhere. The consumer may be provided with a receipt or other item that indicates, either printed or electronically, that the consumer is entitled to the product. The consumer may then scan the receipt or other item on the product dispenser. Information about the customer's order may be obtained and the customer may select and dispense the product if the customer is entitled to it.

FIG. 9 illustrates an example method 900 for limiting product refills. The method 900 begins at block 902. At block 902, a machine readable icon or item is read and/or scanned on the product dispenser. In this embodiment, the consumer may scan the machine readable icon or item in proximity to the product dispenser, e.g., 102A, which may be configured to detect the presence of the machine readable icon or item or otherwise receive information associated with the presence of the machine readable icon or item. For example, a product dispenser, such as 102A, may be configured to include an RFID read/write device, such as an identification reader/scanner device 106A, capable of detecting the presence of, or otherwise receiving information associated with, the presence of a machine-readable icon or item associated with an RFID tag. In any case, the machine readable icon or item may include data that may be received by the product dispenser when the machine readable icon or item is scanned.

In one embodiment, the machine readable icons or items may be obtained from an ordering station. The ordering station may be located at a registry of a quick-service restaurant, at a checkout lane of a convenience store, and/or may be other types and/or kinds of ordering stations as may be needed and/or desired in particular embodiments. For example, the ordering station may be configured with at least one client type device or wireless communication device, such as 214A-214C in FIG. 2, to receive an order for at least one product. A customer or person associated with the order station may enter data corresponding to an order for at least one product via a client type device or a wireless communication device, e.g., 214A-214C. Machine readable icons or items may include, but are not limited to, receipts with bar codes or other machine readable codes, RFID tagged items, items associated with RFID tags, items with wireless communication devices, and/or other types of items associated with associated wireless communication devices. The machine readable icons or items may include any number of wireless technologies including, but not limited to, RFID, radio frequency, infrared, or other wireless communication methods as may be needed and/or desired in a particular embodiment.

In block 904, following block 902, the product dispenser obtains a customer order. In this embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may communicate with a local and/or remote processor, controller, server, or data processing resource, such as 126, memory, or data storage device, such as 110, to obtain information related to the customer order based at least in part on data obtained by scanning the machine-readable icon or item. The data acquired by scanning the machine-readable icon or item may include, but is not limited to, product type information, product identification information, and other information associated with the product and/or item. For example, when a product dispenser, such as 102A, receives data obtained by scanning a machine-readable icon or item, an associated processor or controller, such as 106, may access an associated memory or data storage device, such as 110, to retrieve information associated with a customer's order. In another example, a local and/or remote processor, controller, server, or data processing resource, such as 126, may access an associated memory or data storage device, such as 110, to retrieve information associated with a customer's order.

In decision block 906 following block 904, a determination is made as to whether the consumer is entitled to continue charging. If the determination is positive, that is, the consumer has the right to continue, the method 900 continues to block 908. If the determination is negative, that is, the consumer is not entitled to recharge, then the method 900 proceeds to block 912. In the illustrated embodiment, a processor or controller, such as 106, may determine whether the consumer enjoys product renewal rights. For example, the controller, e.g., 106, may determine whether the consumer is entitled to product replenishment by obtaining information associated with the consumer order and determining whether predetermined criteria are met, such as whether the consumer order includes product replenishment or whether the order has been paid full. In one embodiment, a processor or controller, such as 106, may communicate with local and/or remote servers or data processing resources, such as 126, which may determine whether the consumer is entitled to product replenishment. In any event, a determination is made as to whether the consumer enjoys product renewal.

In one embodiment, an order station, such as a quick service restaurant, may have a policy of product renewal or not. Thus, when a customer's order is checked after the product is initially filled, the determination may be that the customer does not have the right to continue filling.

In another embodiment, an order station, such as a quick service restaurant, may offer a half or other discounted price refill for the product. Thus, when a customer's order is checked after the product is initially filled, the determination may be to allow the customer to pay for the product refill.

In another embodiment, an order station, such as a quick service restaurant, may allow a predetermined number of product refills, such as one. Thus, when a customer's order is checked after an initial fill of product, the determination may be to allow the customer to dispense a predetermined number of product refills, such as one. The determination may be that the consumer does not have the right to enjoy additional product refill when the predetermined number of product refills is reached.

At block 908, product refills are 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 dispense a product, such as a product refill.

In block 910, following block 908, the product dispenser updates the customer's order indicating the status of the product being dispensed. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may update the customer's order indicating the refill status of the product being dispensed. For example, a customer order may be updated such that the status of the order may reflect changes or new data associated with the refill of the dispensed product, including, but not limited to, the type or kind of product, portion size, and price. In one embodiment, a local and/or remote server or data processing resource, such as 126 in FIG. 1, may update the customer's order indicating the refill status of the product being dispensed. In one embodiment, the product dispenser may update the customer's order indicating that a refill of product has been dispensed. Additionally, any status, configuration, product formulation, portion size, price, and/or other types and/or kinds of information and other data may be data that is transmitted and updated as may be needed and/or desired in a particular implementation. In any event, product dispenser data may be transmitted to update the customer's order indicating the refill status of the product being dispensed.

The method 900 ends after block 910.

Referring to block 912, the consumer knows that he or she is not entitled to recharge. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may notify the consumer that he or she does not enjoy the rights to replenish the product. For example, after the consumer requests product renewal or attempts to renew the product, the consumer is not entitled to renewal, and the controller, e.g., 106, can provide a communication that the consumer is not entitled to renewal, such as a message that the consumer is entitled to renewal, via a user interface, e.g., 112, associated with the product dispenser.

The method 900 ends after block 912.

In an example embodiment, a consumer may include an order for at least one product at a product station. The consumer may be given a machine readable icon or item. Such machine readable icons or items may be bar coded receipts, RFID tagged items, wireless devices, and/or other types and/or kinds of machine readable icons or items as may be needed and/or desired in a particular embodiment. The consumer may then scan the icon or item on the product dispenser to obtain the ordered product. The performance of the order may be tracked and, thus, when the consumer wishes to replenish the product, a determination may be made as to whether the consumer is entitled to replenish.

In one embodiment, the ability of a consumer to dispense too many product refills may be avoided or otherwise limited by updating the consumer's order. In this regard, once the consumer scans the machine readable icon, item, or code, dispenses the product, and the consumer's order is updated, further dispensing of the product by the consumer may be avoided or otherwise restricted from refilling. For example, if the consumer desires product refill, the product dispenser may prompt the consumer to pay for the refill at a price that may be reduced compared to the initial price at the order station or the price of the first purchase of the product.

Referring to fig. 10, an example method 1000 of combining promotional offers to a phone card and/or wireless phone with product transactions is illustrated. The method 1000 begins at block 1002. At block 1002, input from a consumer is received for selecting a product. In the embodiment shown in fig. 10, the consumer may enter data through a user interface such as 112 in fig. 1,e.g. selection of an indicator corresponding to a product, e.g. DIET CHERRY COKE^TM. In other embodiments, other products may be selected by the consumer, or other data associated with one or more product selections may be entered by the consumer. In one embodiment, product selection may be accomplished through a graphical user interface, such as user interface e.g. 112, associated with the product dispenser.

In block 1004 following block 1002, the product dispenser data is communicated locally and/or remotely to determine promotional phone card and/or wireless phone promotional offers. In this embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may communicate with a local and/or remote processor, controller, server, or data processing resource, such as 126, memory, or data storage device, such as 110, to obtain information related to promotional phone cards and/or wireless phone promotional offers. For example, when a product dispenser, such as 102A, receives data obtained by scanning a machine-readable icon or item, an associated processor or controller, such as 106, may access an associated memory or data storage device, such as 110, to obtain information associated with a promotional phone card and/or wireless telephone promotional offer. In another example, a local and/or remote processor, controller, server, or data processing resource, such as 126, may access an associated memory or data storage device, such as 110, to obtain information associated with promotional phone cards and/or wireless phone promotional offers.

In block 1006, following block 1004, the consumer is provided a promotional offer. 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 to the consumer a communication prompting the consumer for a promotional offer. For example, the processor or controller, e.g., 106, may provide the message and associated prompts to the consumer via an output device, e.g., a user interface, e.g., as 112. In another embodiment, a local and/or remote server or data processing resource, such as 126 in FIG. 1, may generate a communication or other output, such as a message, and send the message to a product dispenser, such as 102A, for communication with a consumer. A processor or controller, e.g., 106, associated with the dispenser, e.g., 102A, can receive the message to communicate with the consumer. In any event, the consumer is prompted with promotional offers, such as for a phone card and/or wireless phone.

In decision block 1008 following block 1006, a determination is made as to whether the consumer accepts the promotional offer. If the determination is positive, that is, the consumer receives a promotional offer, the method 1000 continues to block 1012. If the determination is negative, that is, the consumer does not accept the promotional offer, the method 1000 continues to block 1010. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may determine whether the consumer accepts the promotional offer. For example, a processor or controller, such as 106, may receive a consumer input or selection through a user interface, such as 112, and determine whether the input or selection corresponds to whether the consumer accepts a promotional offer.

At block 1010, appropriate input from the consumer is optionally received to pay for the product and, if necessary, for the promotional offer. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may prompt the consumer to pay for the product and, if necessary, the promotional offer. For example, a processor or controller such as 106 may prompt the consumer to pay by any monetary or financial transaction device or method, such as a method of receiving a credit or debit card or account number. Payment for the product and/or promotional offer may be through a cashless or currency-based transaction. In one embodiment, the consumer may be provided with an option to purchase products and/or promotional offers via a client type device or a wireless communication device, such as 214A-214C in FIG. 2. In this particular embodiment, the consumer may pay for the product and/or promotional offer by authorizing payment via a client type device or wireless communication device, e.g., 214A-214C, and payment may be received via an associated network, e.g., 104. In any event, the consumer is allowed to purchase the product and/or promotional offers.

The method 1000 ends after block 1010.

Referring to block 1012, an appropriate input from the consumer is received to execute the promotional offer. In the illustrated embodiment, the consumer enters data, including the entry of any data needed to execute a promotional offer, through a user interface associated with the product dispenser, such as user interface 112 in FIG. 1. For example, the data may be entered corresponding to a phone card or wireless phone. In one embodiment, the consumer may provide an email address, wireless telephone number, and/or other types and kinds of information as needed and/or desired in a particular embodiment to enforce any need for promotional offers.

In block 1014, following block 1012, a payment from the consumer is received to pay for the promotional offer and/or otherwise add the promotional offer to the transaction amount. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may prompt the consumer to pay for the promotional offer and/or otherwise add the promotional offer to the transaction amount. For example, a processor or controller such as 106 may prompt the consumer to pay by any monetary or financial transaction device or method, such as a method of receiving a credit or debit card or account number. Payment for the selected products and/or promotional offers may be through cashless or currency-based transactions. In one embodiment, the consumer may be provided with the option to pay for the product and/or promotional offer via a client-type device or wireless communication device, such as 214A-214C in FIG. 2. In this particular embodiment, the consumer may pay for the selected product and/or promotional offer by authorizing payment via a client type device or wireless communication device, e.g., 214A-214C, and payment may be received over an associated network, e.g., 104. In another embodiment, a particular promotional offer may require detailed consumer information, fees, and/or other information, and the consumer may be allowed to pay for some or all of these fees, or otherwise add an amount to the current transaction and pay after the order is executed. In any event, the consumer is allowed to pay for the selected product and/or add a promotional offer to the transaction amount.

In a block 1016, following block 1014, execution of the promotional offer is facilitated, if necessary. Depending on the type of promotional offer, some or all of any remaining requirements for executing the promotional offer may be facilitated. For example, if a promotional phone card or wireless phone is dispensed to a consumer, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, can facilitate the transfer of corresponding instructions to a local and/or remote server or data processing resource, such as 126 in FIG. 1, to facilitate dispensing, routing, or other means required to execute a promotional offer.

Block 1016 is followed by block 1010, which has been described in detail above.

In one embodiment, a consumer using the product dispenser may be prompted with promotional offers for phone card and/or wireless phone offers. For example, a consumer may receive a promotion of free or discounted time (disconnected minute) on a wireless telephone plan.

Referring to FIG. 11, an example method 1100 of combining a promotional offer associated with a product from a product dispenser is illustrated. The method 1100 begins at block 1102. At block 1102, a machine readable code or item associated with a product is scanned or read. In this embodiment, the consumer may scan the product proximate to a product dispenser, such as 102A in fig. 1, which may be configured to detect the presence of the product or otherwise receive information associated with the presence of the product. The product may include any number of wireless technologies including, but not limited to, RFID, radio frequency, infrared, or other wireless communication methods as needed and/or desired in a particular embodiment. The product may be, for example, a cup, a box, a tray, a container, or any product packaging as needed and/or desired in a particular embodiment.

In block 1104, following block 1102, the product dispenser determines whether the scanned product is part of a promotional offer. In one embodiment, a processor or controller, such as 106, may communicate with a local and/or remote server or data processing resource, such as 126, over a network, such as 104, which may determine whether the scanned product is part of a promotional offer.

In block 1106, following block 1104, a determination is made as to whether the scanned product is part of a promotional offer. If the determination is positive, that is, the scanned product is part of a promotional offer, then method 1100 continues to block 1108. If the determination is negative, that is, the scanned product is not part of a promotional offer, then method 1100 ends. In the illustrated embodiment, a processor or controller, such as 106, may determine whether the scanned product is part of a promotional offer. For example, the controller, e.g., 106, can determine whether the scanned product is part of a promotional offer by obtaining information associated with the scanned product and determining whether predetermined criteria are met, such as whether the promotional offer covers or otherwise contains the scanned product. In one embodiment, a processor or controller, e.g., 106, may communicate with a local and/or remote server or data processing resource, e.g., 126, which may determine whether the scanned product is part of a promotional offer. In any event, a determination is made as to whether the scanned product is part of a promotional offer.

At block 1108, the consumer knows that the product is part of a promotional offer. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with a product dispenser, such as 102A, may notify the consumer that the product is part of a promotional offer. For example, after a consumer scans products proximate to a product dispenser, such as 102A, a controller, such as 106, may provide a communication, such as a message, that the products are part of a promotional offer via a user interface, such as 112, associated with the product dispenser.

At block 1110, following block 1108, consumer promotional offer information is provided. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may provide the consumer with promotional offers or detailed information. For example, after a consumer learns that a product is part of a promotional offer, the controller, e.g., 106, may provide additional information, e.g., a message, via a user interface, e.g., 112, associated with the product dispenser.

In decision block 1112, following block 1110, a determination is made as to whether the consumer accepts the promotional offer. If the determination is positive, that is, the consumer receives a promotional offer, the method continues to decision block 1114. If the determination is negative, that is, the consumer does not accept the promotional offer, the method 1100 ends. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may determine whether the consumer receives a promotional offer. For example, a processor or controller, such as 106, may receive a consumer input or selection through a user interface, such as 112, and determine whether the input or selection corresponds to whether the consumer accepts a promotional offer.

At decision block 1114, a determination is made as to whether the promotional offer is for a free product. If the determination is positive, that is, the promotional offer is for a free or discounted product, the method 1100 continues to block 1116. If the determination is negative, that is, the promotional offer is not for a free or discounted product, the method 1100 continues to block 1118. In the illustrated embodiment, the processor or controller, e.g., 106, can determine whether the promotional offer is for a free or discounted product. For example, a controller such as 106 in FIG. 1 may determine whether the promotional offer includes an offer for a free or discounted product by obtaining information associated with the promotional offer. The controller, e.g., 106, can determine whether predetermined criteria are met, such as whether the promotional offer encompasses or otherwise contains a free or discounted product. In one embodiment, a processor or controller, such as 106, may communicate with a local and/or remote server or data processing resource, such as 126, which may determine whether the promotional offer includes an offer for a free or discounted product. In any case, a determination is made as to whether the promotional offer is for a free or discounted product.

At block 1116, the free or discounted product is distributed to the consumer. 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 dispense free or discounted products.

The method 1100 ends after block 1116.

Referring to block 1118, the consumer is prompted for appropriate information to facilitate execution of the promotional offer. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, may prompt the consumer to enter or otherwise provide appropriate detailed information to facilitate execution of the promotional offer. The consumer may utilize a user interface associated with the product dispenser, such as user interface e.g., 112, to provide detailed information, such as consumer preferences or information, to implement or facilitate promotional offer execution. The user may enter one or more selections through a user interface, such as 112, and a processor or controller, such as 106, may facilitate promotional offer execution based at least in part on consumer preferences or information provided by the consumer. For example, the consumer may be allowed to pay for the promotional offer and/or otherwise add the promotional offer to the transaction amount. Thus, the promotional offer may require or otherwise require detailed consumer information, fees, and/or other data to allow the consumer to pay, add an amount to the current transaction, or pay after the order is executed.

The method 1100 ends after block 1118.

In one embodiment, promotional offers between products and beverages may be implemented. In this regard, the product may be scanned on the product dispenser. Offer details may be obtained and the product dispenser may be configured as necessary.

In one embodiment, a promotional offer to purchase candy pieces and obtain products at a free or discounted price may be implemented. The consumer may first purchase the candy pieces. The candy package may be scanned on the product dispenser. The product dispenser may obtain information related to a particular offer and determine that a free or discounted product should be dispensed. The consumer may be allowed to dispense a product such as a beverage.

In another embodiment, one or more promotions may be implemented to provide free or discounted products, products of a particular type and/or category, and/or other benefits as may be needed and/or desired in a particular embodiment.

Referring to FIG. 12, an example method 1200 of allocating a free or discounted product to a consumer while the consumer is paying for Internet or network access is illustrated. The method 1200 begins at block 1202. At block 1202, input from a consumer is received to open a transaction through a product dispenser and pay for network or internet access. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may allow the consumer to initiate a transaction and pay for network or Internet access or services. For example, a processor or controller such as 106 may prompt the consumer to pay by any monetary or financial transaction device or method, such as a method of receiving a credit or debit card or account number. Payment for network or internet access or services may be through cashless or currency-based transactions. In one embodiment, the consumer may be provided with the option to pay for network or internet access or services through a client type device or wireless communication device, such as 214A-214C in FIG. 2. In this particular embodiment, the consumer may pay for network or internet access or services by authorizing payment via a client type device or wireless communication device, e.g., 214A-214C, and the payment may be received over an associated network, e.g., 104. In any event, the consumer is allowed to open the transaction by way of the product dispenser and pay for internet access.

In decision block 1204, following block 1202, a determination is made as to whether the consumer wants to dispense the product. If the determination is positive, that is, the consumer wants to dispense a product, payment 1200 continues to block 1206. If the determination is negative, that is, the consumer does not want to dispense the product, then payment continues to decision block 1208. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may allow the consumer to select the product to be dispensed. For example, after a consumer initiates a transaction and pays for network or internet access or services, the consumer may decide or otherwise select to select a product. The consumer may select a product through a user interface associated with the product dispenser, such as user interface 112.

At block 1206, the product is dispensed to 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 allow the consumer to dispense a selected product. For example, the consumer is allowed to dispense product from a product dispenser, such as 102A, whenever the consumer pays for network or Internet access or service.

In decision block 1208 following block 1206, a determination is made as to whether the consumer is still using the Internet. If the determination is positive, that is, the consumer is still using or accessing the network or the Internet, the method 1200 continues to block 1210. If the determination is negative, that is, the consumer is not using or accessing the network or the Internet, the method 1200 continues to block 1212. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, may determine whether the consumer is still using or accessing a network or the Internet. For example, the controller, e.g., 106, can determine whether the consumer is still using or accessing the network or internet by obtaining information associated with the consumer's use of the network or internet. The controller, e.g., 106, can determine whether a predetermined criteria is met, such as whether the consumer is logged onto a network or the internet. In one embodiment, a processor or controller, such as 106, may communicate with local and/or remote servers or data processing resources, such as 126, which may determine whether the consumer is still using or accessing the network or internet. In any case, a determination is made as to whether the consumer is still using the internet or network.

At block 1210, the consumer continues to be billed for network or internet access. In the illustrated embodiment, the processor or controller, e.g., 106, may continue to bill the consumer if the consumer is still using or accessing the network or internet.

Following block 1210 is decision block 1204, which has been described above.

Referring to block 1212, the transaction ends. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may end the transaction if the consumer does not use or access the network or Internet. For example, the billing process for the consumer with network or internet access is terminated and the consumer can no longer dispense free or discounted products from the product dispenser, such as 102A.

The method 1200 may end after block 1212.

In one embodiment, the consumer may subscribe to internet access at the internet cafe site. By charging, the consumer may be allowed to use the internet or other network of the location to check email, surf the web, and/or for other purposes. During this time period, the consumer may pay for internet or other network access, allowing the consumer to dispense free or discounted products from the product dispenser.

Referring to fig. 13, an example method 1300 of paying for a product, such as a beverage, using a product dispenser is illustrated. In the embodiment shown in FIG. 13, the business partner may choose to set up an account with the product or beverage provider so that employees, students, group members, or other members associated with the business partner may use the product dispenser and the cost of any dispensed products or beverages may be credited to the account associated with the business partner. For example, business partners such as United ParcelService (UPS)^TMTMA business partner account with the product provider may be selected to be set up or established so that UPS employees may use a particular product dispenser associated with the product provider and the cost of any dispensed product may be credited to the associated UPSTo the business partner account of (1). In this case, the UPS employee may obtain the dispensed product from the particular product dispenser associated with the product provider without having to pay for the product at the time of dispensing, either at the location of the product dispenser or otherwise at the site associated with the product dispenser.

In another example, a particular product dispenser may be positioned at one or more McDonald' s^TMIn a store. UPS employees may activate the product dispenser using identification techniques such as RFID, identification tags, and/or other similar services. In this case, the UPS employee may enter any McDonald' s^TMThe store, identifies himself or herself to the product dispenser and dispenses the product without having to pay for the product at the time of dispensing or otherwise on site at the dispensing location. Payment for the dispensed product may be credited to an account associated with the UPS, such as a business partner account.

Method 1300 begins at block 1302. At block 1302, an identification device associated with a consumer or a product cup of a consumer is scanned or otherwise detected at or near the product dispenser. In this embodiment, the identification information may be associated with a consumer, who may provide such information to the product dispenser. For example, a consumer may swipe a magnetic card or other device with identification information on a reader or other input/output device associated with a product dispenser, such as 102A in fig. 1. In another embodiment, a cup or other container, such as 136, may include identification information, such as an RFID or other machine readable tag, such as 138, and a reader, such as an RFID or other machine readable code reader, such as 140, associated with a product dispenser, such as 102A, may receive the identification information.

In decision block 1304, following block 1302, a determination is made as to whether a business partner account has been identified. If the determination is positive, that is, the business partner account is identified, then method 1300 moves to block 1308. If the determination is negative, that is, the business partner account is not identified, method 1300 moves to decision block 1306. In the embodiment shown in fig. 13, an identification scanner/reader device, such as 106A in fig. 1, may be associated with the product dispenser, wherein the identification reader device is operable to receive or otherwise obtain identification information associated with a consumer or a product cup of the consumer. The identification scanner/reader device 106A may communicate with a server or data processing resource, e.g., 126 or 206, over a network, e.g., 104 or 204, which may make a determination based at least in part on the identification information whether the consumer and/or the consumer's product cup is associated with a business partner account. A server or data processing resource, such as 126 or 206, may communicate with one or more data storage devices, such as 128A-128C, to identify at least one business partner account.

In one embodiment, a consumer having a product cup with an RFID or other identification device associated with the product cup may operate the product cup proximate an identification reader device, e.g., 118A-118Q, associated with the product dispenser. Alternatively, the consumer may scan for other identification devices, such as RFID tags, labels, cards, PINs, and/or other forms of IDs as may be needed and/or desired for a particular implementation. Through the product dispenser, the identification reader device may be in data communication with at least one server or data processing resource, such as 126 or 206, either locally or remotely, to determine whether there is a commercial account associated with the consumer. Based at least in part on the results of the determination, processing may move to decision block 1306 or decision block 1308.

At decision block 1306, a notification is transmitted that the business partner account was not identified or otherwise determined. In the embodiment shown in FIG. 7, if the server or data processing resource, e.g., 126 or 206, determines that a business partner account associated with the consumer is not established or is not present, then corresponding instructions are transmitted to the product dispenser to avoid or otherwise limit the consumer from dispensing the product unless payment for the product is received. For example, in one embodiment, a notification may be transmitted to a client-type device associated with the product dispenser, which may inform the consumer and/or service personnel that a business partner account is not established or is not present and that payment from the consumer is to be received. After block 1306, method 1300 ends.

At decision block 1308, a determination is made as to whether the account status is 'normal' (OK). If the determination is positive and the status of the account is 'normal', the method 1300 continues to block 1310. If the determination is negative, that is, the status of the account is not 'normal', then the method 1300 returns to block 1306. In the embodiment shown in fig. 13, if the server or data processing resource, e.g., 126 or 206, determines that the business partner associated with the consumer is not properly funded, or that the account is not otherwise suitable for product reimbursement, then corresponding instructions will be communicated to the product dispenser to avoid or otherwise limit the consumer from dispensing the product unless payment for the product has been received.

Referring to block 1310, if a determination is made that the account status is 'normal', then corresponding instructions will be transmitted to the product dispenser to allow the consumer to dispense the product.

In block 1312, following block 1310, the balance (balance) associated with the account is adjusted or otherwise accounted for the dispensed product. In the embodiment shown in FIG. 13, a server or data processing resource, such as 126 or 206, may monitor and adjust accounts, such as business partner accounts, for each product dispensed. In this manner, the account may be debited for each product dispensed.

The method 1300 ends after block 1312.

Referring to fig. 14, an example method of using portion control for a child size and sample size cup is illustrated. The method 1400 begins at block 1402. At block 1402, the consumer is allowed to place a cup in an area proximate to a nozzle of the product dispenser. In this embodiment, the consumer may operate or otherwise place the cup proximate to a nozzle associated with the product dispenser, such as nozzle 124 in FIG. 1.

In block 1404 following block 1402, the cup is scanned. In this embodiment, a product dispenser, such as 102A in fig. 1, may be configured to detect the presence of a product or beverage cup or otherwise accept information associated with the presence of a product or beverage cup. The product or beverage cup may include any number of wireless technologies including, but not limited to, machine code, bar code, RFID, radio frequency, infrared, or other wireless communication methods or devices as may be needed and/or desired in a particular embodiment.

In decision block 1406 following block 1404, a determination is made as to whether a child sized cup was scanned. If the determination is positive, that is, the child sized cup has been scanned, the method 1400 continues to block 1408. If a determination is made as to whether the result is positive, that is, the scanned cup is not a child-sized cup, the method 1400 continues to decision block 1410. In the illustrated embodiment, a processor or controller, such as 106 in fig. 1, may determine whether a child-sized cup is scanned. For example, the controller, e.g., 106, may determine whether a child-sized cup is scanned by obtaining information associated with the product cup and determining whether a predetermined criterion has been met, e.g., whether the product cup is a predetermined sized cup, e.g., a child-sized cup.

At block 1408, the product dispenser is set for child size portion control. Processor or controller associated with the product dispenser in this embodiment, controller 106 in fig. 1, may configure the dispenser for child-size portion control. In one embodiment, the controller, e.g., 106, may limit the volume of product dispensed to an amount suitable for filling a child-sized cup.

Block 1414 following block 1408 is described in more detail below.

Referring to decision block 1410, a determination is made as to whether a sample size cup was scanned. If the determination is positive, that is, the sample size cup is scanned, the method 1400 continues to block 1412. If the determination is negative, that is, the scanned cup is not a sample size cup, the method 1400 continues to block 1414. In the illustrated embodiment, a processor or controller, such as 106 in fig. 1, may determine whether a sample size cup is scanned. For example, the controller, e.g., 106, may determine whether a sample size cup is scanned by obtaining information associated with the product or beverage cup and determining whether a predetermined criterion has been met, e.g., whether the product or beverage cup is a predetermined size cup, e.g., a sample size cup.

At block 1412, the product dispenser is configured for sample size portion control. In this embodiment, a processor or controller associated with the product dispenser, such as controller 106 in fig. 1, may configure the dispenser for sample size portion control. In one embodiment, the controller, e.g., 106, may limit the volume of product dispensed to an amount suitable to fill a sample size cup.

In block 1414, following block 1412, the consumer is allowed to select a product. In the illustrated embodiment, the consumer may enter data through a user interface, such as 112 in FIG. 1, for example, with a product, such as DIET CHERRY COKE^TMSelection of the corresponding indicator. In other embodiments, other products may be selected by the consumer, or other data associated with one or more product selections may be entered by the consumer. In one embodiment, product selection may be accomplished by way of a graphical user interface, such as user interface 112, associated with the product dispenser.

In block 1416 following block 1414, the consumer is allowed to dispense the product with portion controls set for the child size and sample size cups. 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 user to dispense a desired product with a portion control set for a predetermined size, such as a child-sized and/or sample-sized cup. In one embodiment, all other sized cups, for example, cups of a size that does not set a portion control limit, may receive other product amounts.

The method 1400 ends after block 1416.

In one embodiment, to avoid product spillage when using child-sized and sample-sized cups, the product dispenser may use portion control. In this regard, the product dispenser may limit the serving volume of the dispensed product when a child-sized or sample-sized cup is detected. Thus, a smaller volume of product may be dispensed, minimizing the chance that a child-sized or sample-sized cup (of a smaller size) may spill over and be wasted beverage product. In one example, the child-sized cup may be a relatively small cup that is commonly used by children. The sample size cup may be a relatively small cup typically used by consumers to sample from a small serving of product, for example to see if the consumer likes such a serving before dispensing a relatively full cup of product.

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 (e.g., one or more computer program products) having, for instance, computer usable media. The media has embodied therein, for instance, computer readable program code for providing and facilitating the capabilities of embodiments of the present invention. The article of manufacture may be included as a part of a computer system or sold separately. One 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 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 implemented in a different order, or elements may be added, deleted or modified. All of these variations are considered a 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 (7)

1. A product dispenser (102) comprising:

a reader (106A) configured to read machine-readable items (116A-116Q) associated with a consumer; and

a controller (106) in communication with the reader (106A) and configured to execute a set of instructions that, in response to execution, cause the controller to:

receiving, by the reader, information from the machine-readable items (116A-116Q);

configuring dispenser parameters for a product to be dispensed from the product dispenser based at least in part on information from the machine readable item (116A-116Q), the dispenser parameters including a product formulation of the product and a product size of the product;

providing a promotional offer to the consumer based at least in part on the product and portion size of the product;

prior to dispensing the product, providing an option to a consumer through a user interface to select an adjusted product associated with a promotional offer, wherein the adjusted product comprises an adjustment to one or more of the dispenser parameters based on the promotional offer; and

the adjusted product is dispensed based on the selection of the adjusted product.

2. The dispenser (102) of claim 1, wherein the controller (106) is further configurable to execute a set of instructions that, in response to execution, cause the controller to:

determining whether the consumer is eligible to receive the product.

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

receiving information from a machine readable item (116A-116Q) associated with a consumer;

configuring dispenser parameters for a product to be dispensed from a product dispenser based at least in part on information from the machine readable item (116A-116Q), the dispenser parameters including a product formulation and a product size;

providing a promotional offer to the consumer based at least in part on the product and portion size of the product;

prior to dispensing any product, providing an option to a consumer through a user interface to select an adjusted product associated with a promotional offer, wherein the adjusted product comprises one or more dispenser parameters for the selected product adjusted based on the promotional offer; and

dispensing the adjusted product.

4. The method of claim 3, further comprising configuring at least one of a product size of the product to be dispensed or a product price of the product to be dispensed.

5. The method of claim 3 wherein the machine readable items (116A-116Q) include at least one of product packaging, printed advertisements, bar codes, icons, or RFID tags.

6. The method of claim 3, wherein the step of dispensing the adjusted product comprises determining whether the consumer is eligible to receive the product.

7. The method of claim 3, wherein the product comprises at least one of a beverage, a beverage can, a beverage bottle, a beverage container, or a beverage refill.