BACKGROUND OF THE INVENTION

1. Field of the Invention:

[0001] The present invention is generally directed to systems and methods for selling products and/or services. More specifically, the present invention assists vendors/providers and customers better identify products and/or services that may be of interest to those customers.

2. Description of the Related Art

[0002] This invention is an upselling system that may provide an opportunity for selling related products (inclusive of services, and advertising) after the product has left the retail store or has been shipped to a customer or used, as well as initiating the purchase of the product. This invention extends to having the smart packaging in the product itself so long term upsells and information can be embedded in or with the product or in a smart card or other media delivered separately. As used herein, the term "vendor" is inclusive of vendors, manufacturers, and other products and services providers, such as advertising/marketing agencies , while "product" is inclusive of products, services, and upsell advertising .

[0003] The invention extends to having the retail store or provider of e-commerce that may sell the manufactured product (or service related to the product), to be involved in the sales and ordering function of follow-on products. The invention extends to allowing the customer to store and manage a wish list, scheduled purchases, alerts and fulfilment options, perform other services and also ask questions of the up- seller even if they are not the original provider.

[0004] Utilizing smart packaging or card technology (US8125667 and US8970864) to provide a completely customized and targeted sales and ordering function on a shipped package to upsell related products of the product that gets shipped that has either integration of (1) goes around the original e-commerce supplier of the product or (2) goes through the original e-commerce supplier of which both integrations capable of executing the purchase of the related merchandise without returning to the website or store.

[0005] Methods and systems for selling products and services to customers today are performed via a variety of means that include direct person to person sales, by phone, or by computer via the internet. These systems and methods are limited as they do not timely or conveniently provide customers with information regarding different products and services sold by various different vendors when customers make decisions relating to purchases, as well as receive or obtain a product that may be related to another product or service.

[0006] What are needed are systems and methods that allow products and services sold by various different vendors to be provided to users in a timely and convenient way upon delivery and/or receiving of a related product or service.

[0007] The problem is how to sell follow-on products (and related services) after the customer has left the retail store, website or opened or used a product? How to create a system that can upsell related products after the product has left the retail store or has been shipped or used?

SUMMARY OF THE PRESENTLY CLAIMED INVENTION

[0008] The presently claimed invention relates to apparatus, methods, and non- transitory computer readable storage mediums that collects information from a plurality of different vendors that may be used to sell products to customers or users via computing devices that may be owned or used by those customers. A method consistent with the presently claimed invention may receive information relating to products offered by different vendors from a product tag, display information regarding products that are related to the tagged product in a graphical user interface (GUI), and receive user selections via the GUI, where the related product is available for purchase based on one or more user selections. The information received from those vendors may be stored. This method may also include sending a software application to an electronic device of a user. This software application may associate a first product to another product offered for sale by a vendor, where the other product offered to the user may be related to the first product, the other product is ordered by the user, and where the vendor fulfills the order of the other product.

[0009] In instances where the presently claimed invention is implemented as a non- transitory computer readable storage medium, a processor executing instructions out of the memory may also receive information relating to products offered by different vendors, where the information received from those vendors may be stored. This method may also include sending a software application to an electronic device of a user. This software application may associate a first product to another product offered for sale by a vendor, where the other product offered to the user may be related to the first product, the other product is ordered by the user, and where the vendor fulfills the order of the other product.

[0010] Some embodiments provide for a non-transitory computer readable storage medium consistent with the present disclosure that may also receive information from a product tag, display information regarding products that are related to the tagged product in a graphical user interface (GUI), and receive user selections via the GUI, where the related product is purchased based on one or more user selections received over the GUI.

[0011] When the presently claimed invention is implemented in apparatus that includes a memory, a processor, a network interface, and a database, the network interface may receive information relating to products offered by different vendors, where the information received from those vendors may be stored in the database. The processor executing instructions out of the memory may also implement methods consisting with the present disclosure, where a software application may be sent to an electronic device of a user. This software application may associate a first product to another product offered for sale by a vendor, where the other product offered to the user may be related to the first product, the other product is ordered by the user, and where the vendor fulfills the order of the other product.

[0012] Apparatuses consistent with the present disclosure may include a memory, a processor that executes instructions out of the memory, an interface that receives tag information from a tag that is associated with a product, and a display that displays information relating to one or more products that are related to the tagged product in a graphical user interface (GUI). Apparatus consistent with the present disclosure may also receive one or more user selections over the GUI, where at least one of the one or more user selections received initiate a purchase of a product that is related to the tagged product based on the user selections received over the GUI.

[0013] Methods and apparatus consistent with the present disclosure may provide a targeted and custom recommendation for each purchase/customer and a

simple/seamless method of purchase. By improving the relevance of product suggestion and reducing the friction of payment, overall sales improve. This use of upsell information (1) on the package or (2) on the product or (3) on any related information in the product package or (4) in a smart card or other advertising media delivered after the original sale, which will extend the upsell opportunities for the original manufacturer, retailer, and original e-commerce provider. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] FIG. 1 illustrates an exemplary environment where an upsell system may provide information and services to a user operating a user device.

[0015] FIG. 2 is a block diagram of an exemplary system for implementing a computing device.

[0016] FIG. 3 illustrates an exemplary set of steps that may be performed when upsell opportunities are organized for transmission to a user device.

[0017] FIG. 4 illustrates various different types of flows of monies (or revenues) of different types that may be processed by systems and methods consistent with the present disclosure.

[0018] FIG. 5 illustrates user devices that may receive information regarding products, catalogs, or packaging options that may be associated with a product.

[0019] FIG. 6 illustrates a series of exemplary steps consistent with the present disclosure that may be performed by an upsell system that receives information relating to the sale of products and services to customers.

[0020] FIG. 7 illustrates a series of exemplary steps that may be performed by an upsell system that services upsell requests or that validates provider upsell information.

[0021] FIG. 8 illustrates exemplary content that may be displayed on user devices when a user of a use device makes a purchase.

[0022] FIG. 9 illustrates a series of steps that may be performed by upsell software consistent with the present disclosure.

[0023] FIG. 10 illustrates exemplary steps of a flow chart where questions from a customer may be shared with a vendor.

[0024] FIG. 11 illustrates an exemplary flow chart where various items ordered by a customer may be fulfilled by a single vendor or may be fulfilled by several different vendors.

[0025] FIG. 12 illustrates exemplary steps that may be performed by a method that schedules the fulfillment of customer orders. [0026] FIG. 13 illustrates exemplary alert software that may be used to setup and activate alerts that relate of orders made at a user device.

[0027] FIG. 14 illustrates exemplary steps that may refer a product offering to a friend

[0028] FIG. 15 illustrates exemplary steps that may be performed by loyalty program software consistent with the present disclosure.

[0029] FIG. 16 illustrates a flow chart of a method that may be used to provide feedback regarding the performance of a vendor after a customer has purchased a product from that vendor.

[0030] FIG. 17 illustrates a user devices that downloads upsell software and receives information regarding products, catalogs, or packaging options that may be associated with a product.

[0031] FIG. 18 illustrates a method of encoding product upsell information and retrieving information from a database.

[0032] FIG. 19 illustrates an exemplary shopping cart graphical user interface (GUI) that may allow a user to select one of a number of selection boxes when that user wishes to manage options relating to making purchases.

[0033] FIG. 20 illustrates exemplary GUIs that may be used by a user to display and enter information relating to electronic tags may be associated with a product.

[0034] FIG. 21 illustrates exemplary GUIs that may be used by a user to display and enter information relating items that a user has in a hold list.

[0035] FIG. 22 illustrates exemplary GUIs that may be used by a user to display information relating to a customer's purchased history may be associated with a product [0036] FIG. 23 illustrates an exemplary GUI where a user may make selections when they make a purchase.

[0037] FIG. 24 illustrates an exemplary GUI where a user may select a sub-GUI that relates to a service that benefit a customer.

[0038] FIG. 25 illustrates exemplary GUIs that a user may use when scheduling the delivery of products they wish to order. [0039] FIG. 26 illustrates exemplary GUIs that may be used to set or change user alert settings or to setup different types of alerts.

[0040] FIG. 27 illustrates two exemplary GUIs that may be used by a user to access a loyalty program or to send feedback to a vendor.

[0041] FIG. 28 illustrates an exemplary GUI that allows a user to set various purchase security controls.

[0042] FIG. 29 illustrates two exemplary GUI that allow users to create and manage a Wish List

[0043] FIG. 30 illustrates an exemplary GUI that allows users to refer an upsell product to a friend.

DETAILED DESCRIPTION

[0044] The present disclosure relates to methods and apparatus where information relating to products and services offered by various vendors may be offered for sale to customers via computing devices owned or used by those customers. Products and services offered to a particular customer may be related to a product previously purchased by that customer or be related to a product that a customer has access to. In certain instances, a product that a customer has access to may include a tag, such as a circuit, a chip, or printed matter which may be affixed, printed or embedded that may provide information to an electronic device of a customer. In certain instances, a smart card including upsell information, a coupon card, a gift card, a credit card, or an advertising card may related to an upsell opportunity may be provided to a customer via a separate delivery.

[0045] After the customer's device receives the information provided by the product tag, information on other products, services, or services related to the tagged product may be received by the customer device. Methods consistent with the present disclosure may allow a user of a user device to interact with various different graphical user interfaces when making purchases. As such, a smart card or an advertisement associated with a product may facilitate the sale of other products or services. For example, a person that purchased a bicycle that includes a smart card or advertisement could link to offerings that sell bicycle accessories/clothing or that identify entities that perform bicycle maintenance. In certain instances, a smart card or advertisement/print advertisement may offer to sell or link to products or services that are not directly related to a particular product. For example, a smart card or advertisement associated with school supplies (such as pencils, pads, or notebooks) could be used to identify back to school clothing or tutoring services.

[0046] Products and services may include but are not limited to products, services and/or upgrades/incentives from: banks and financial institutions; sports and theatre venues; travel sites and travel agencies, hotels, restaurants, rental cars; real estate transactions of any kind; non-profits.

[0047] Products and services associated with an up-sell may be offered via a smart card or other media delivered to a person. For example, smart cards or other media may be handed to a person as they walk down the street or be received via the mail. Such upsell smart cards or media may link to an up-sell system consistent with the present disclosure where a prospective customer may browse up-sell offerings relating to any product or service that a person may be interested in. As such, up-sell offerings consistent with the present disclosure do not have to be linked to a particular product that a person has purchased before.

[0048] In certain instances, retailers or other providers may advertise products or services via a tag that may have been provided to a customer by a retailer or provider. These tags could be included in or be part of a flier circulated by a retailer/provider, they could be attached to a product sold by a retailer, and/or they also to an upsell system that offers to sell customers products and services.

[0049] Products and services offered for upsell may be provided via an upsell system consistent with the present disclosure. In certain instances, products, services, and upsell offerings of products or services may be provided by providers, retailers, e- commerce sites, or other third party entities. Upsell systems consistent with the present disclosure may be associated with a single entity that provides products or services or may be associated with various different entities that cross-sell products/services, or may be associated with a service provided to different entities that may cross-sell products and/or services.

[0050] FIG. 1 illustrates an exemplary environment where an upsell system may provide information and services to a user operating a user device. FIG. 1 includes upsell system 105 that may communicate with user devices, such as smart phone 130, and with service providers 160 via the Internet 155.

[0051] Upsell system 105 includes communication interface (COMM) 110, creating upsell information software 115, servicing upsell information software 120, and database storage 125. Note that database storage 125 may include a product database that stores product information, a catalog database that stores information relating to products or services that a customer may purchase, and a packaging database that stores information that identifies product packaging options.

[0052] A package is container that encloses an object and/or product. Packaging options are choices provided to a customer related to the type of packaging to be used when shipping the product that was ordered.

[0053] A smart card or other advertising may be a hard media delivered to customers after the delivery of the original purchase. The smart card or advertising could be a credit card or rewards card or other type of card imbedded with upsell information and/or other types of customer/provider relationship information. The advertising could identify an entity that provides mobile services or a brick and mortar establishment that could service a product.

[0054] A catalog is a document (digital, print or otherwise expressed) that contains an inventory of products and services that is available to potential customers to aid in the purchase of a product or service.

[0055] A database is a structured set of data stored in a computer or computer system that is accessible by other computers and computer systems to retrieve data.

[0056] The internet 155 is the set of interconnected computers that communicate via the internet protocol suite, including, yet not limited to TCP/IP or other current technology.

[0057] Providers 160 illustrated in FIG. 1 include manufacturers and vendors that supply and sell products, retailers that sell products, an e-commerce sales site that sell product online, and third (3 ^rd ) party sellers. Each of the providers 160 of FIG. 1 may organize various sets of provider information 165 that may be accessed when upsell system 105 organizes the delivery of upsell offerings to a user of smart phone 130. Provider information 165 may include offerings that may be accessible by user devices (user device may be a smartphone, tablet, a personal data assistant (PDA, personal computer, etc.) like user device 130 via upsell system 105. [0058] A manufacturer/vendor/provider may be a person or company that may produce or sell products, goods, material or a combination thereof by hand or machinery. A retailer is a seller of products and materials. E-commerce is the conduct of trade (buying and selling) via the internet. 3 ^rd party sellers are sellers of products who may or may not have a formal arrangement with the manufacturer of the product and/or service provider, retailer and/or the customer to sell similar or complimentary products and/or services.

[0059] Fulfillment is the receiving an order, processing and order and the delivery of the ordered product or service to the customer.

[0060] User device may be a wireless mobile device, mobile wireless telephone, PDA, tablet, personal computer and the like that transmits audio, video and data and incorporates a computer operating system that allows for the execution of software and communication with people and other computers.

[0061] FIG. 1 illustrates that user device 130 includes an upsell application 135 software program interface, an upsell software program module 140, a fulfillment option software module 145, and a questions software module 150.

[0062] In certain instances, providers 160 may provide provider information 165 to upsell system 105 via the internet 155 when upsell offerings are created and stored in database storage 125 at upsell system 105. Upsell offerings include offerings of products and services offered for sale by providers 160, where those offerings may be related to one or more products that a customer has previously purchased.

[0063] When providers 160 create upsell information, providers 160 may access the creating upsell information software 115 module via communication interface 110, where the creating upsell information software 115 may store those newly created offerings in database storage 125.

[0064] Once upsell offerings have been created and stored in database storage 125 at upsell system 105, those offerings may be provided to user device 130 via the servicing upsell information software 120 module at upsell system 105. The servicing upsell information software module may then provide offering information to user device 130 (e.g., smartphone) via communication interface 110 and internet 155. The upsell information received by user device 130 may be accessed by a customer using upsell application 135 and upsell software 140 at user device 130. In certain instances, upsell application 135 may be downloaded to user device 130 from upsell system 105. Upsell application 135 may include or be linked to various different upsell offerings currently offered by providers 160.

[0065] When a customer is interested in an upsell offering provided by one or more providers 160, that customer may communicate with one or more providers 160 when purchasing an offering. As such, a user device, such as user device 130 of the customer may not have to communicate with upsell system 105 when the customer makes an upsell purchase. Alternatively or additionally, however, upsell system 105 may be involved in communications between user device 130 and provider 160 offerings when a customer makes purchases. When user device 130 is used to make purchases, the customer making the purchase may compose and send questions and receive answers regarding provider offerings using questions software 150 at user device 130. After a customer makes a purchase using upsell software 140, that customer may select options regarding fulfilling that purchase using fulfillment option software 145. Fulfillment option software 145 may also be used to provide the customer with information relating to the status of the shipment of their offering. As such, fulfillment option software 145 may allow a customer to select how their purchase should be fulfilled and be used to track their purchase when it is being prepared and shipped.

[0066] The Upsell System diagram includes providers [(1) Manufacturer/Vendor Supplying/Selling Products, (2) Retailer Selling Products and (3) E-Commerce sales site] that interacts through the internet to the Upsell System that has communications (COMM) that allows connection to the creation of the upsell info, that software storing that data for a product, to catalog information, or to packaging databases. The providers ultimately get their respecting upsell info on either of the actual product, the catalog with the products(s) or on the packaging, where relevant information may be provided to the customer from their interactions with the providers, the customer may have a smartphone loaded with a upsell app and its Upsell Software. When the customer uses the Upsell App 135 they will connect to the Upsell System 105 to find their related upsell info in the databases 125 using the servicing upsell software 120 and then the transaction may be completed by the Processing Software 170 (US8125667 and US8970864). The 3 ^rd Party Sellers are vendors/providers that can sell products through the system when the providers refer them as well as upselling their own items.

[0067] An APP is a software application designed to be run on a mobile computing device that can accept user input, interact with external computers and electronic devices and the internet.

[0068] FIG. 2 is a block diagram of an exemplary system for implementing a computing device. The computing system 200 of FIG. 2 includes one or more processors 210 and main memory 220. Main memory 220 stores, in part, instructions and data for execution by processor 210. Main memory 220 can store the executable code when in operation. The system 200 of FIG. 2 further includes a mass storage device 230, portable storage medium drive(s) 240, output devices 250, user input devices 260, a graphics display 270, and peripheral devices 280.

[0069] The components shown in FIG. 2 are depicted as being connected via a single bus 290. However, the components may be connected through one or more data transport means. For example, processor unit 210 and main memory 220 may be connected via a local microprocessor bus, and the mass storage device 230, peripheral device(s) 280, portable storage device 240, and display system 270 may be connected via one or more input/output (I/O) buses.

[0070] Mass storage device 230, which may be implemented with a magnetic disk drive or an optical disk drive, is a non-volatile storage device for storing data and instructions for use by processor unit 210. Mass storage device 230 can store the system software for implementing embodiments of the present invention for purposes of loading that software into main memory 220.

[0071] Portable storage device 240 operates in conjunction with a portable nonvolatile storage medium, such as a floppy disk, FLASH memory, compact disk or Digital video disc, to input and output data and code to and from the computer system 200 of FIG. 2. The system software for implementing embodiments of the present invention may be stored on such a portable medium and input to the computer system 200 via the portable storage device 240.

[0072] Input devices 260 provide a portion of a user interface. Input devices 260 may include an alpha-numeric keypad, such as a keyboard, for inputting alpha-numeric and other information, or a pointing device, such as a mouse, a trackball, stylus, or cursor direction keys. Additionally, the system 200 as shown in FIG. 2 includes output devices 250. Examples of suitable output devices include speakers, printers, network interfaces, and monitors.

[0073] Display system 270 may include a liquid crystal display (LCD) or other suitable display device. Display system 270 receives textual and graphical information, and processes the information for output to the display device.

[0074] Peripherals 280 may include any type of computer support device to add additional functionality to the computer system. For example, peripheral device(s) 280 may include a modem or a router.

[0075] The components contained in the computer system 200 of FIG. 2 are those typically found in computer systems that may be suitable for use with embodiments of the present invention and are intended to represent a broad category of such computer components that are well known in the art. Thus, the computer system 200 of FIG. 2 can be a personal computer, hand held computing device, telephone, mobile computing device, workstation, server, minicomputer, mainframe computer, or any other computing device. The computer can also include different bus configurations, networked platforms, multi-processor platforms, etc. Various operating systems can be used including Unix, Linux, Windows, Macintosh OS, Palm OS, iOS, Android and other suitable operating systems.

[0076] Mobile computing devices can include smartphones, wearable computers, implanted devices or other portable hardware capable of storing and operating software instruction to execute user commands and communicate with other computer devices via network or other connections.

[0077] FIG. 3 illustrates an exemplary set of steps that may be performed when upsell opportunities are organized for transmission to a user device. In step 310 of FIG. 1 a customer operating a user device is provided with the ability to make a purchase. Next in step 320 of FIG. 1, information regarding a product and/or product upsell information may be provided to the user device. The information provided to the user device in step 320 may include a smart catalog, information regarding a smart manufacturer package, provider package, a smart card, a coupon card, a gift card, a credit card, an advertising card, or may include specific recommendations regarding upsell offerings that may be provided by one or more providers (i.e. manufactures/vendors, retailers, 3 ^rd party vendors/providers, and an e-commerce site). In certain instances, upsell offerings offered to a customer operating a user device may include information that is digitally encoded on the product. The advertising could identify an entity that provides mobile services or a brick and mortar establishment that could service a product.

[0078] Information encoded on a product may be encoded in various different means. In certain instances, a circuit or a wireless transceiver may be embedded in the product where a user device may wirelessly read information from the circuit or wireless transceiver. In such instances, the circuit or wireless transceiver embedded in the product may extract power from a wireless transmission from a user device that causes the circuit or wireless transceiver to transmit information to the user device wirelessly. Alternatively, or additionally, information encoded in a product may be visually encoded, where a user of a user device may take a picture of the visually encoded information that causes the user device to link to a WEB page that provides information to the user of the user device via a display at the user device.

[0079] After step 320, step 330 allows the customer to receive upsell

recommendations via their user device. Those upsell recommendations may include information relating to the delivery of a product and may be provided via a software monitoring application program installed on the customer's user device. In certain instances, the software monitoring application program may be an application program (i.e. an "app") that is provided by a manufacturer, a retailer, a 3 ^rd party vendor, or an e- commerce site.

[0080] Next in step 340, the customer may be allowed to purchase a recommended upsell product offering via an upsell software application installed on their user device. After a user has decided to purchase an upsell offering in step 340, determination step 350 identifies an upsell provider that could best service a purchase order related to the customer's upsell purchase decision. Depending on which provider has been identified as being the best provider to service the upsell offering purchase order, that purchase order may be passed to a retailer, to a manufacturer, or to an e commerce site. Note that step 360 of FIG. 3 may relate to actions associated with the purchase order that may be performed at a retailer. Note that step 370 of FIG. 3 is associated with actions associated with the purchase order that may be performed at a manufacturer. Similarly, step 380 of FIG. 3 is associated with actions associated with the purchase order that may be performed at an e-commerce site. Actions relating to servicing an upsell purchase order may include completing transactions, paying related parties, and providing shipment information.

[0081] The method involves (1) providing a Customer makes a retail purchase and (2) providing a product which is delivered with product upsell info e.g. by a (1) Smart Catalog, (2) Smart Package, (3) Smart Product, and/or (4) Smart Card or advertising that has customer specific recommendations digitally encoded with product upsell info or a link to external information for Upselling by e-commerce site, manufacturer or retailer other party and (3) Allowing a customer to receive Upsell recommendations 330 from product upsell info upon delivery of product via a related Upsell APP of a smartphone or other smart device, The monitor app may be supplied by the catalog, manufacturer or e-commerce site or retailer and (4) allowing a customer to purchase Upsell

recommended product via Monitor or Upsell APP 340 and (5) Determining an Upsell provider 350. When step 350 determines that the upsell provider should be a retailer 360, allowing the Retailer to complete transactions to generate new sales, and to optionally pay related parties. When step 350 determines that the upsell provider should be provider 370, provider 370 may be allowed to complete transactions, to realize new sales to increase revenue, and to optionally pay related parties. When step 350 determines that the provider should be e-commerce site 380, e-commerce site 380 may be allowed to complete transactions and optionally pay related parties.

[0082] FIG. 4 illustrates various different types of flows of monies (or revenues) of different types that may be processed by systems and methods consistent with the present disclosure. FIG.4 includes entities of customer 410, providers 420, retail sales 430, (430A/430B). Cross provider upsell sales may also be provided. Cross provider upsell sales are sales that may be provided by more than one entity, such entities may provide retail sales 430 or other providers 420 the ability to upsell products to a customer. As such upselling products in this way may allow additional monetary flows 450, 460, 470, and 480 to be generated. In certain instances, monetary flows 450, 460, 470, and 480 may flow between vendors, where funds relating to purchases may be forwarded from one vendor to another as appropriate. Note that sales provided by retailers 430 (retail sales) include both normal sales 430 A and upsell sales 430B.

[0083] Money flows illustrated in FIG. 4 include revenue flows related to normal retail money flows 450, retail upsell money flows 460, vendor upsell money flows 470, and cross-vendor upsell money flows 480. FIG. 4 thus, illustrates that revenues may flow between customer 410 and a retail sales establishment 430 when normal sales 430A and upsell sales when customer 420 buys products or services from retailer, i.e. when normal sales 430A or upsell sales 430B are made.

[0084] FIG. 4 also illustrates that revenue may flow between other providers 420 and with cross-vendor upsell 440 entities, where providers 420 and cross-vendor upsell 440 entities may transfer monies between the retailer 430 that performs upsell sales 430B and a retailer 430 that performs normal sales 430A. Because of this providers 420 and cross- vendor upsell entities 440 may allow other entities, such as retailer 430 to receive revenue when retailer 430 sells products or services related to a sale made by provider 420 or by cross-vendor upsell entity 440 or visa-versa. Similarly, cross vendor sales may be processed by vendor up-seller 435 interacting with vendor 421A according to monetary flow 470 or may be processed by a cross-vendor up-seller 440 interacting with cross vendor 421B according to monetary flow 480.

[0085] This method shows the flow of funds between the customers and the providers for a normal sale and an upsell sale when cross vendors are used in the upsell.

[0086] A GUI on an electronic device consists of an interface that allows users to interact with it through graphical icons and visual indicators; not just text, typed commands or other text navigation. The GUI interface allows direct manipulation of graphical elements that may be combined with text. GUI can be used on a computer, handheld devices such as portable media players, gaming devices, smartphones and household, office and applications.

[0087] FIG. 5 illustrates user devices that may receive information regarding products, catalogs, or packaging options that may be associated with a product. FIG. 5 includes user devices 510, 520, and 590. Catalog 530, insert 540, retail product 550, product in a package 560, package 570, removable card 580 of FIG. 5 each include one or more wireless transmitter tags and card 591 includes encoded visual data. In certain instances, user devices 510 and 520 may receive information wirelessly transmitted from catalog 530, insert 540, retail product 550, product in a package 560, package 570, removable card 580, service offer 585, and separately delivered card 581. The

information received by user device 510 may be displayed on a graphical user interface (GUI) via an application monitoring program at user device 510.

[0088] Additionally or alternatively the information received by user device 520 may be received by application programs that are installed on user device 520 where those programs may use that information when performing functions consistent with the present disclosure. Note that catalog 530, insert 540, retail product 550, product in a package 560, package 570, removable card 580, service offer 585, and separately delivered card 581 of FIG. 5 each include one or more wireless transmitters (e.g., transmitter tags) and card 591 includes encoded visual data. These transmitters may be connected to or be contained within catalog 530, insert 540, retail product 550, product in a package 560, package 570, removable card 580, service offer 585, and/or a smart/advertising card 581 delivered at a later date. Wireless transmission technologies associated with the present disclosure may include any type of wireless transmission capability known in the art, including, yet not limited to radio frequency identifiers (RFID), Bluetooth™, near field data communications (NFC), iBeacon, CCD, MEMS or other wireless transmission technique. Because of this, user devices 510 and 520 may receive information related to an upsell opportunity that may also be included in or associated with a print media entry or device associated with a catalog 530, an insert 540, a retail product 550, a product in a package 560, or a package 570, removable card 580. service offer 585, and/or a card 581.

[0089] NFC is near field communication technology, a communication protocol that allows two electronic devices to communicate wirelessly at close range. An NFC tag is and electronically enabled tag containing information or instructions related to and associated object. RFID is radio frequency identification technology that the energy from the radio waves emitted by a reader to access electronic information stored in electronic circuitry on a tag, key or other object. iBeacon is a proprietary electronic beacon system developed by Apple, based on Bluetooth Low Energy wireless computer networking technology. CCD is a charge coupled device that is used in cameras to capture light and generate images. MEMS are microelectromechanical systems that comprise of microscopic mechanical parts and can be used to create sensors, displays, switches, and other devices.

[0090] Catalog 530 is a bound container or physically printed document that includes a tag encoded with product information and Insert 540 is a flyer or other printed media with an encoded tag.

[0091] In an example, user devices 510 may receive information from a transmitter connected to product 550 that is a shoe. Upsell software operating on user device 510 may use the information received from product 550 (eg. shoe) to identify an upsell opportunity for shoe polish, where information relating to the shoe polish may be displayed in the GUI of user device 510. If the user decides to purchase the shoe polish, the user may make a selection in the GUI and user device 510 may then receive information relating to how the shoe polish will be paid for and how the user would like to receive the shoe polish. As such, the user could pay for the shoe polish with a credit card and could order that the shoe polish be sent to an address using next day delivery express mail.

[0092] FIG. 6 illustrates a series of exemplary steps consistent with the present disclosure that may be performed by an upsell system that receives information relating to the sale of products and services to customers. Step 610 of FIG. 6 may allow a vendor to create offerings that may be offered to customers. When upsell offerings are created, step 610 may ping vendor computers to identify whether particular vendors are interested in creating new offerings for storage in a database at the upsell system.

[0093] Next in step 620 of FIG. 6, information relating to the creation of different types of upsell offerings may be received from vendors. The information received in step 620 may be received in response to queries sent from an upsell system.

[0094] Next in step 630 of the flow chart of FIG. 6, the information received in step 620 may be stored in a database. Then that information may be sent to upsell processing software in step 640 of FIG. 6. Finally, in step 650, a processor executing the processing software may allow the received upsell information to be associated with a catalog offering. As such, step 650 may maintain a complete listing of a virtual catalog offerings continuously overtime. Step 650 may also allow upsell information to be associated with a product package, a catalog, a product, or with a card/smart card. After new upsell offerings have been created in a database at an upsell system, that information related to that new upsell may be verified by a verification process or may be shared with customers when those customers make purchase decisions.

[0095] The creating upsell software is continuously comprising (1) Pinging Comm for request from providers for creating upsell info 610, (2) Querying the providers for the types of upsell info 620, (3) Storing upsell info to the appropriate database 630, (4) Sending Upsell info to the Processing Software 640, (5) Connecting the Processing Software to the provider allowing completion of upsell info information insertion to the product package, or to the catalog product, or card/smart card 650, and (6) returning to Pinging Comm (step 610) when requesting upsell opportunities from providers for creating upsell information opportunities.

[0096] This software leverages the Processing Software that allows for a closed loop system to insert recordable information on a catalog, product or packaging and then executing a transaction between stakeholders (customer, providers, or others)

[0097] FIG. 7 illustrates a series of exemplary steps that may be performed by an upsell system that services upsell requests or that validates provider upsell information. Step 710 of FIG. 7 may send requests (ping) different providers to receive information regarding potential upsell requests that may be received from those providers. Next step 720 of FIG. 7 may query one or more providers for information relating to different types of upsell opportunities that may be provided by those providers, step 720 may also receive information from different providers based on the query.

[0098] Next step 730 may query upsell information stored at a database that may be related to the types of upsell opportunities that may be provided by one or more providers. After step 730, step 740 may verify whether the upsell information stored at the database are consistent with the types of upsell opportunities received from the providers in step 720. Finally, step 750 of FIG. 7 may allow processing software associated with an upsell system to complete upsell transactions based on available upsell opportunities and customer demand. Step 750 may also allow upsell information to be associated with a product package, a catalog, a product, a card, or with a smart card.

[0099] This method is used by the providers to service requests from the providers. The servicing upsell software is continuously comprising (1) Pinging Comm for request from providers for creating upsell info 710, (2) Querying the providers for the upsell info detected 720, (3) querying the upsell info from the appropriate database 730, (4) verifying Upsell info and inputting verification for the Processing Software 740, (5) Connecting Processing Software to the provider allowing completion of upsell info information insertion transaction to the product package, catalog or product 750, and (6) returning to Pinging Comm for request from providers for creating upsell information 710.

[0100] This software leverages the Processing Software that allows for a closed loop system to insert recordable information on a catalog, product or packaging and then executing a transaction between stakeholders (customer, providers, others)

[0101] FIG. 8 illustrates exemplary content that may be displayed on user devices when a user of a use device makes a purchase. FIG. 8 includes user interface 810 that displays information relating to a "don't forget" reminder and user interface 820 that displays information that may relate to purchasing and ordering products. User interface 830 includes information relating to questions that a customer may have regarding a purchase. Finally, user interface 840 includes information relating to an item selected for purchase. Note that the don't forget user interface 810 includes selection boxes that may be used to open the read info 810 user interface, the questions 830 user interface, or the purchase 840 user interface. Note also that each respective user interface includes various different selection boxes that may be selected to make a purchase, change items that are purchased, display content of a shopping cart, return to a previously user interface selection, or to save information included in a user interface.

[0102] The Upsell App GUI which is branded as "Don't Forget" 810. Upon entering the App (A) customer has the choice of reading information on the upsell info tag on the product, the catalog or the packaging, once read the customer has the ability to ask questions of the info provided or to actually purchase the upsell product. Once the customer initiates the "read Info" icon, the Read Info GUI B 820 is initiated. The customer has the ability to scan the catalog, package or product (Scan Info icon). Once connected and scanned the wireless connection signal may transmit the scanned info. This initiates the provider to initiate the servicing upsell info software in the Upsell System. (Note that previously the Upsell system was used to create the upsell information on the product, catalog or packaging). Once the customer sees what was purchased the upsell products are shown in the "Don't Forget Products." The customer can return or save the information. The customer may ask questions before purchase, by initiating the questions icon on a first question GUI panel A. The questions GUI C 830 is shown, the customer may then interact with the upsell product by sending and receiving information. The customer can return or save the information. If the customer decides to purchase the upsell product, he or she may initiate the purchase icon on a first purchase GUI A which may then open another Purchase GUI D. The consumer can see the prices, select the products to purchase and fill in payment info and purchase the items. When purchasing the products, the provider is connected to the customer, and the providers may then initiate the upsell system servicing. The customer can return or save the information. Saved Upsell product selections (from a single or multiple vendors) can be saved in My Central Shopping Cart where pending purchases, history, etc. can be managed. Additional transaction details can be controlled through Actions to create schedules, alerts and wish lists.

[0103] FIG. 9 illustrates a series of steps that may be performed by upsell software consistent with the present disclosure. Step 905 of FIG. 9 may receive user input information. After step 905, step 910 may open a graphical user interface (GUI) that may allow a user of a user device to select a type of sub-GUI. Next a series of determination steps (915A 920A, 925A, and 930A) may be used to identify what type of sub-GUI has been selected by a user of the user device. Note that step 915A relates to opening a shopping cart GUI, that step 920A relates to opening a services GUI, that step 925A relates to opening an information GUI, and that step 930A relates to opening a question GUI. When each of determination steps 915A 920A, 925A, and 930A identify that a GUI has not been selected, program flow moves to step 940 where a purchase GUI may be opened and where a purchase may be performed, executed, and fulfilled.

[0104] When step 915A identifies that the user wishes to open a shopping cart, program flow may move to step 915B where additional user input may be received. Next program flow may move to step 915C that calls the shopping cart GUI for information that performs different determination steps 985A, 990A, and 995A may identify whether a function associated with the shopping cart should be performed. When each of determination steps 985A, 990A, and 995A identify that a GUI has not been selected by a user, step 999 of FIG. 9 may call a check out GUI, where a user may complete a purchase.

[0105] When determination step 985A identifies that additional user input received in step 915B relates to a GUI associated with an electronic tag, program flow may move to step 985B where the electronic tag GUI is called. When determination step 990A identifies that additional user input received in step 915B relates to a GUI associated with a product "hold my items request," program flow may move to step 990B where a "hold my items GUI" is called. When determination step 995A identifies that additional user input received in step 915B relates to a GUI associated with a purchase history, program flow may move to step 995B where a purchase history GUI is called.

[0106] When step 920A identifies that a services GUI has been selected by a user, program flow may move to step 920B that calls the services GUI and that receives user input. After step 920A are a series of determination steps (950A, 955A, 960A, 965A, and 970A) that may identify whether the user has selected a schedule GUI, an alerts GUI, a wish list GUI, a friend GUI, or a loyalty program GUI in any of steps 950A, 955 A, 960A, 965 A, and 970A. When the user has not selected any GUI associated with steps 950A, 955 A, 960A, 965A, and 970A, program flow moves to step 980 where a callback GUI is called.

[0107] A loyalty program is a rewards program offered by product and service providers that provides special offers, discounts, access, etc. to frequent or high dollar volume customers.

[0108] When step 950A identifies that the user wishes to open a schedule GUI, program flow may move to step 950B where the schedule GUI may be called and software relating to scheduling a purchase may be executed. When step 955A identifies that the user wishes to open an alerts GUI, program flow may move to step 955B where the alerts GUI may be called and software relating to an alert may be executed.

[0109] When determination step 960A identifies that the user wishes to open a wish list GUI, program flow may move to step 960B where the wish GUI may be called and where software relating to products that the user would like to acquire may be executed. When step 965A identifies that the user wishes to open a "refer a friend GUI/' program flow may move to step 965B where the "refer a friend GUI" may be called and where software relating to a friend referral may be executed. When step 970A identifies that the user wishes to open a loyalty program GUI, program flow may move to step 970B where the loyalty program GUI may be called and where software relating to scheduling the loyalty program may be executed.

[0110] FIG. 9 illustrates that a processor executing instructions out of a memory at an upsell system may receive user input that allows a user to open different types of GUIs when entering information relating to purchases, upsell purchases, products, and/or services that a user may like to buy using a user device that may be

communicatively coupled to an upsell system consistent with the present disclosure.

[0111] The Upsell software receives data from the Upsell APP GUI as input by the customer. Based on this input the software presents the customer with the appropriate GUI and/or executes the appropriate software to satisfy the customer request.

[0112] FIG. 10 illustrates exemplary steps of a flow chart where questions from a customer may be shared with a vendor. Step 1010 of FIG. 10 is a step where a user may enter one or more questions over a GUI at a user device. After these questions are entered into the GUI, they may be sent to a vendor in step 1020 of FIG. 10. Next, in step 1030, the customer's user device may receive answers to those questions where the answers to those questions may be displayed in the GUI at the customer's user device in step 1040 of FIG. 10. Finally, after step 1040 of FIG. 10, program flow ends in step 1050.

[0113] The Questions Software receives input from the Questions GUI 1010 in the form of a question from the customer. This question is relayed 1020 to the

vendor/merchant 1030 of the Upsell product. The vendor/merchant response to the question is presented to the customer in the Questions GUI 1040.

[0114] FIG. 11 illustrates an exemplary flow chart where various items ordered by a customer may be fulfilled by a single vendor or may be fulfilled by several different vendors. In step 1110 of FIG. 11 an order data including a plurality of items are received from a checkout GUI. Determination step 1120 may then identify whether a user wishes all off the items listed in the checkout GUI be purchased from various different individual vendors or be bundled and be purchased from a single provider.

[0115] When determination step 1120 identifies that the items ordered by the customer should be purchased from several different vendors, step 1130 of FIG. 11 may send order 1130A to vendor A, order 1130B to vendor B, and send order 1130C to vendor C. After step 1130, vendors A, B, and C may each fulfill orders 1130A, 1130B, and 1130C.

[0116] When determination step 1120 identifies that the items ordered by the customer should be bundled, order 1140A may be sent to a single vendor for fulfillment in step 1140.

[0117] Steps performed by the fulfillment software of FIG. 11 may be performed at a user device based on information received from an upsell system, such as upsell system 105 of FIG. 1. Alternatively, the steps performed by the steps of FIG. 11 may be performed by a user device and by one or more different computers.

[0118] The Fulfilment Option Software allows customers to select the method of fulfilment for an Upsell to, if desired, potentially avoid multiple shipments. Items can be ordered and shipped individually from each vendor that is offering an Upsell item or Bundled by a retailer (or other aggregator) to generate a single transaction and single shipment. This choice is offered in the Check Out GUI and received as a component of the order data that is sent when the transaction is initiated on the Check Out GUI. Based on the fulfilment option selected, order data is sent to the Processing Software to generate a single transaction with at retailer or multiple transactions with individual vendors.

[0119] FIG. 12 illustrates exemplary steps that may be performed by a method that schedules the fulfillment of customer orders. Step 1210 of FIG. 12 may receive information that identifies items that a customer has ordered and may receive information that identifies a schedule relating to how the order will be fulfilled.

[0120] Next step 1220 of FIG. 12 may store the received order item and fulfillment data received in step 1210, after step 1210, a date and a time may be retrieved from a clock in step 1230. Next determination step 1240 may identify whether the current date corresponds to the scheduling data received in step 1210, when yes, program flow may move to step 1250 that sends order data that corresponds to today's date is sent to a fulfillments option software, such that the order may be fulfilled. After step 1250, the scheduling software program flow of FIG. 12 ends at step 1260.

[0121] When determination step 1240 identifies that the current data does not correspond to a scheduled date program, the scheduling software program flow of FIG. 12 also ends at step 1260.

[0122] Fulfillment is the receiving an order, processing and order and the delivery of the ordered product or service to the customer.

[0123] The Scheduling software receives purchase schedule data from the

Scheduling GUI and stores this data and queries the clock for the date and/or time of day. The scheduled purchase data is queried and compared to the queried clock data. For those Upsell items with scheduled dates/times matching the current date/time, Upsell item order data is send to the Fulfilment Options Software to begin the purchase process.

[0124] FIG. 13 illustrates exemplary alert software that may be used to setup and activate alerts that relate of orders made at a user device. Software consistent with the alert flow chart of FIG. 13 may be executed at an upsell system using information entered by a user in an alert GUI at a user device. Step 1310 of FIG. 13 may send requests (ping) providers when identifying what inventory is currently available at different providers.

[0125] Step 1320 of FIG. 13 may receive alert data entered over an alert GUI displayed on a display at a use device. After step 1320 the alert data entered in the alert GUI in step 1320 may be stored in a memory in step 1330. Next step 1340 of FIG. 13 may compare the upsell inventory data received in step 1310 with the alert data received from the alert GUI in step 1320.

[0126] Determination step 1350 may then identify whether the upsell inventory corresponds to the alert data received in step 1320 based on the comparison performed in step 1340. When determination step 1350 identifies that the upsell inventory does not match the received alert data, program flow ends in step 1380. When determination step 1350 identifies that the upsell inventory matches the received alert data, program flow moves to step 1360 where the received alert data is parsed/queried to identify an alert type that is associated with the alert data. After step 1360, step 1370 may activate or initiate an alert of the alert type identified in step 1360. After step 1370, program flown ends in step 1380.

[0127] The Alerts software receives inventory data from the Upsell System Comm and Customer Alerts data from the Alerts GUI and Alerts Type GUI. Alerts data is compared to the inventory data. An alert is activated for the customer for inventory items matching alerts criteria set by the customer. The activated alert is based on the alert type established by the customer in the Alerts Type GUI.

[0128] FIG. 14 illustrates exemplary steps that may refer a product offering to a friend. Step 1410 of FIG. 14 data may be received via a "refer a friend GUI" at a user device. The data received may include an email address or other contact information associated with a friend of a customer. Next in step 1420 of the information received in step 1410 may be stored. After step 1420, step 1430 may prepare information to send to the friend of the customer. Next step 1440 may send an email to the friend of the customer that includes product information that the customer's friend might be interested in purchasing.

[0129] The Refer A Friend software receives product and email data from the Refer A Friend GUI. This information is stored and sent to the user's email service software. The email software is then used to send the product information to the email specified in the referral. In other embodiments the users SMS software or social media APPs or other communication software is used to transmit the referral.

[0130] FIG. 15 illustrates exemplary steps that may be performed by loyalty program software consistent with the present disclosure. Step 1510 of FIG. 15 receives loyalty data entered via a loyalty program GUI at a user device, this received loyalty data may identify products that a customer has purchased. Next in step 1520, the loyalty program software may send product information to a vendor. The loyalty product information sent to the vendor may include the information that identifies products that were previously purchased by the customer that were purchased using the vendor.

[0131] Next information may be received from the vendor that verifies that the customer did purchase the products from the vendor in step 1530 of FIG. 15. After step 1530 identifies that the customer did purchase the products from the vendor, one more offerings of a loyalty program may be sent to a user device of the customer that the customer may select from as a loyalty reward in step 1540. After step 1540, program flow may end in step 1550 of FIG. 15.

[0132] The Loyalty software receives product and vendor/manufacturer data from the Loyalty Program GUI. This data is sent to the vendor/manufacturer. The vendor/manufacturer receives the data and determines the eligibility of the product for loyalty benefits, issues the benefit if appropriate and notifies the user of the status of the redemption request. This information is displayed in the Loyalty Program GUI.

Another embodiment allows the user to view Loyalty Program information directly on the vendor/manufacturer website with in this GUI.

[0133] FIG. 16 illustrates a flow chart of a method that may be used to provide feedback regarding the performance of a vendor after a customer has purchased a product from that vendor. Step 1610 of may receive information VIA a feedback GUI at a user device. The information received in step 1610 may include information relating to a product purchased by a customer and may include information that rates the customer's experience (feedback information) relating to how satisfied the customer is with products and/or services that were provided by the vendor. After step 1610,

determination step 1620 identify that the information received in step 1610 included feedback information relating to the performance of a vendor has been received from the feedback GUI. When step 1620 identifies that feedback data has been provided, program flow may move to step 1630 of FIG. 16 where the feedback information received in step 1610 may be sent to the vender. After step 1630, the flow chart of FIG. 16 ends in step 1640. [0134] When step 1620 identifies that the information received in step 1610 does not include feedback information, program flow may move from step 1620 to step 1650 where information relating to a product purchased by the customer and customer email contact information may be stored. After step 1650, step 1660 may access an email service after which an email that identifies the product that was purchased by the customer may be sent to the customer in step 1670 of the flow chart of FIG 16, then in step 1680, an email that contains feedback may be sent. After step 1680, program flow may move to step 1640 where program flow ends.

[0135] FIG 17. illustrates user devices that may receive information regarding products, catalogs, or packaging options that may be associated with a product. FIG. 17 includes a user device 1710, Product Card 1720, a QR or similar printed code 1730, and an image of a retail product 1740. The QR code 2030 is read to download/access the Upsell App and the Product Image 1740 is read to access product Upsell data.

[0136] FIG 18 illustrates a data structure encoded on tags that may be used to identify products for upsell and their manufacturer. Tag 1810 contains two digitally or graphically encoded number codes. Code A 1820 contain an alphanumeric code of unlimited length to define the upsell product or products. Code B 1830 contains an alphanumeric code of unlimited length to define the seller and/or manufacturer of the upsell product or products. These codes are read by the Upsell App 1850 and combined to generate a web-link to access a web database 1840 that provides an upsell product or products and their providers to the Upsell App 1850. Here again tags associated with a product may have been added or attached to that product by a retailer or provider of products and services when products and services are upsold to customers via an upsell system consistent with the present disclosure.

[0137] FIG. 19 illustrates an exemplary shopping cart graphical user interface (GUI) that may allow a user to select one of a number of selection boxes when that user wishes to manage options relating to making purchases. The shopping cart GUI 1910 of FIG. 19 includes "a my electronic tags" 1920 selection box, "a my hold items" 1930 selection box, "a my purchase history" selection box 1940, "a compare selection" box 1950, and "a checkout" 1960 selection box. When one of the selection boxes of FIG.19 are selected, a sub-GUI associated with that selection may be opened that allows the user of a user device to view and or set items relating to products that a user has access to or that relate to items that a user wishes to purchase.

[0138] The My Central Shopping Cart GUI provides a central location to manage Upsell items. The customer can review all of the electronic tags identified by the Upsell system by selecting My Electronic Tags (electronic tags can be NFC, RFID, IBEACON, CCD, MEMS or other electronic information interaction technology). This provides the customer with the opportunity to purchase or re-purchase any Upsell item that has ever been offered by all vendors, merchants, retailers, manufactures, etc. The customer reviews selected items that are pending purchase from various upsell offers in My Hold Item. Similarly, the history of purchased Upsell items is available in My Purchase history and made available for re-purchase. Items that are selected in My Hold Item can be purchased in a single transaction (even if items are from various vendors) via Proceed to Check Out.

[0139] Note that "my Central shopping cart" is in-essence a shopping cart of all shopping carts, that is, all shopping carts of all vendors are in one shopping cart. Given we have a shopping cart of sold items for an upsell from many vendors shopping cart, our shopping cart has, in essence information from other shopping carts

[0140] The compare button allows the user to compare the costs of the upsell item is the best possible price against the prices available from other vendors.

[0141] FIG. 20 illustrates exemplary GUIs that may be used by a user to display and enter information relating to electronic tags may be associated with a product. FIG. 20 includes my electronic tag GUI 2010 and my electronic tag GUI 2040 that display similar information in different formats. Note that electronic tag GUI 2010 includes various boxes 2020 that include a product name, a price, a retailer/manufacture, information, an "add to hold" selection box, an "add to wish list" selection box, and a proceed to checkout selection box. The boxes 2020 of FIG. 20 may be boxes that may be selected by a user when that user wishes to review certain information in more detail or that may be used to add a particular product to an action list. In an instance where the name, price, or retailer/manufacture box is selected, information that relates to a producf s name, a price relating to the product, or information relating to a retailer or manufacture associated with the product may be displayed after a user selects one of those selection boxes. Actions that may be executed when a selection box is selected may relate to adding a particular product to a hold list, adding a product to a wish list, or to moving to a checkout GUI depending on which box the user selects. Note also that tag GUI 2010 also includes checkbox 2030 that may be selected by a user. In certain instances, checkbox 2030 may have to be checked for one of the boxes 2020 to be populated with a name, a price, or a retailer/manufacturer, for example. In certain other instances, checkbox 2030 may have to be selected for action boxes of "add to hold items" or "add to wish list" selection boxes to be enabled to add a selected product to a hold list or to add that selected product to a wish list.

[0142] Note that tag GUI 2040 of FIG. 20 includes selection boxes 2050 and checkboxes 2060. Here again items that have been selected via checkboxes 2060 may be entered to a hold list when the "add to hold items" or may be added to a wish list when the "add to wish list" selection box is selected. Furthermore, when the "proceed to checkout" selection box is selected, a checkout GUI may be opened at a user device of a user. Note that tag GUI 2040 includes a table that includes rows information relating to various products. Various columns in the table of tag GUI 2040 include a product name, a price, a retailer/manufacture, and other information. Like the selection boxes 2010 of tag GUI 2010, entries in a particular column and row may be selected with a user wishes to see additional information relating to a product. For example, a user selecting the retailer/manufacture of the shoe illustrated in tag GUI 2040 may be presented with a GUI that displays extended information regarding a retailer or a manufacture. In such instances, for example, a manufacture's name and place of manufacture may be displayed in a GUI based on a user making one or more selections in a table.

[0143] Tagged products that appear in the tag GUIs 2010 and 2040 may have been identified via a wireless transmission from an electronic tag built into a product. Alternatively or additionally, product tags that include printed information may be photographed by a camera at a user device. Because of this, products that appear in tag GUIs 2010 and 2040 may be received via an electronic transmission or that may be identified electronically via software at the user device that identifies data included in a print media tag.

[0144] Note that other information that may be included in tag GUIs 2010 and 2040 may include a tag number, a tag type, a date that a sale or an upsell occurred, a hold status, or a shopping cart identifier.

[0145] My Electronic Tags allows the customer to review all of the Upsell items offered to them from all vendors. The interface allows the customer to review products, purchase them directly and/or add them to the Hold Items database. Single or multiple items can be selected, across vendors, for purchase. Embodiment 1 allows for the user to swipe through detailed product information one-at-a-time. Embodiment 2 allows for a table-view of product information to allow for sorting and multiple selection of Upsell items.

[0146] FIG. 21 illustrates exemplary GUIs that may be used by a user to display and enter information relating items that a user has in a hold list. FIG. 21includes my hold items GUI 2110 and hold items GUI 2140 that display similar information in different formats. Note that hold items GUI 2110 includes various boxes 2120 that include a product name, a price, a retailer/manufacture, information, and a proceed to checkout selection box. The boxes 2120 of FIG. 21 may be boxes that can be selected by a user when that user wishes to review certain information in more. In an instance where the name, price, or retailer/manufacture box is selected, information that relates to a producf s name, a price relating to the product, or information relating to a retailer or manufacture associated with the product may be displayed after a user selects one of those selection boxes. Actions that may be executed when a selection box is selected will depend on which box a user selects. For example, a checkout GUI may be displayed after a user selects "the proceed to checkout" selection box. Note also that hold items GUI 2110 also includes checkbox 2130 that may be selected by a user. In certain instances, checkbox 2130 may have to be checked for one of the boxes 2120 to be populated with information such as a name, a price, or a retailer/manufacturer, for example. In certain other instances, checkbox 2130 may have to be selected for that product to be added to a checkout list.

[0147] Note that tag GUI 2140 of FIG. 21includes selection boxes 2150 and checkboxes 2160. Here again items that have been selected via checkboxes 2160 may be entered to a wish list when the "add to wish list" selection box is selected. Note that tag GUI 2140 includes a table that includes rows information relating to various products. Various columns in the table of hold items GUI 2140 include a product name, a price, a retailer/manufacture, and other information. Like the selection boxes 2110 of hold items GUI 2110, entries in a particular column and row may be selected with a user wishes to see additional information relating to a product. For example a user selecting the retailer/manufacture of the shoe illustrated in hold items GUI 2140 may be presented with a GUI that displays extended information regarding a retailer or a manufacture. In such instances, for example, a manufacture's name and place of manufacture may be displayed in a GUI based on a user making one or more selections in a table.

[0148] Products that appear in the GUIs 2110 and 2140 may have been identified via a wireless transmission from an electronic tag built into a product. Alternatively or additionally, product tags that include printed information may be photographed by a camera at a user device. Because of this, products that appear in GUIs 2110 and 2140 may be received via an electronic transmission or may be identified electronically via software at the user device that identifies data included in a print media tag.

[0149] Note that other information that may be included in GUIs 2110 and 2140 may include a tag number, a tag type, a date that a sale or an upsell occurred, a hold status, or a shopping cart identifier.

[0150] My Hold Items allows the customer to review all of the Upsell items they intend to buy from all vendors. The interface allows the customer to review all products to be purchased in a single interface. Embodiment 1 allows for the user to swipe through detailed product information one-at-a-time. Embodiment 2 allows for a table-view of product information to allow for sorting and filtering of products based on criteria such as vendor, shopping cart ID or other convenient ways to review a pending purchase.

[0151] FIG. 22 illustrates exemplary GUIs that may be used by a user to display information relating to a customer's purchased history may be associated with a product. FIG. 22 includes purchase history GUI 2210 and purchase history GUI 2240 that display similar information in different formats. Note that purchase history GUI 2210 includes various boxes 2220 that include a product name, a price, a retailer/manufacture, information, an "add to hold" selection box, and a proceed to checkout selection box. The boxes 2220 of FIG. 22 may be boxes that may be selected by a user when that user wishes to review certain information in more detail or that may be used to add a particular product to an action list. In an instance where the name, price, or

retailer/manufacture box is selected, information that relates to a producf s name, a price relating to the product, or information relating to a retailer or manufacture associated with the product may be displayed after a user selects one of those selection boxes. Actions that may be executed when a selection box is selected may relate to adding a particular product to a hold list, adding a product to a wish list, or to moving to a checkout GUI depending on which box the user selects. Note also that tag GUI 2210 also includes checkbox 2230 that may be selected by a user. In certain instances, checkbox 2230 may have to be checked for one of the boxes 2220 to be populated. In certain other instances, checkbox 2230 may have to be selected for an action to occur.

[0152] Note that purchase history GUI 2240 of FIG. 22 includes selection boxes 2250 and checkboxes 2260. Here again items that have been selected via checkboxes 2260 may be entered to a hold list when the "add to hold items" selection box is selected, a checkout GUI may be opened at a user device of a user. Note that purchase history GUI 2240 includes a table that includes rows information relating to various products.

Various columns in the table of purchase history GUI 2240 include a product name, a price, a retailer/manufacture (vendor), and other information. Like the selection boxes 2210 of purchase history GUI 2210, entries in a particular column and row may be selected with a user wishes to see additional information relating to a product. Note that purchase history GUI 2204 includes an "add to hold items" selection box, a "add to wish list" selection box, and a "proceed to checkout" selection box.

[0153] Note that other information that may be included in purchase history GUIs 2210 and 2240 may include a tag number, a tag type, a date that a sale or an upsell occurred, a hold status, or a shopping cart identifier.

[0154] My Purchase History allows the customer to review all of the Upsell items they have purchased from all vendors. The interface allows the customer to review all products to be purchased in a single interface. Embodiment 1 allows for the user to swipe through detailed product information one-at-a-time. Embodiment 2 allows for a table-view of product information to allow for sorting and filtering of products based on criteria such as vendor, shopping cart ID or other convenient ways to review a pending purchase. Items that the customer wishes to purchase again can be purchased directly or tagged as and added to My Hold Items for later purchase.

[0155] FIG. 23 illustrates an exemplary GUI where a user may make selections when they make a purchase. FIG. 23 includes checkout GUIs 2310 and 2340 that display similar information in different formats. Checkout GUI 2310 includes selection boxes 2320 where a user may view or make selections regarding a product. By using selection boxes 2320 a user may view the name of a product, see the price of a product, identify a retailer or manufacturer associated with a product, check other information related to a product, or initiate a transaction. In certain instances selection boxes 2320 may be enabled only when checkbox 2330 is checked. As such, checkbox 2330 may be used to filter what information is displayed in a GUI. When individual selection boxes 2320 are selected, additional information relating to the selected section box may be viewed by a user.

[0156] Checkout GUI 2340 includes checkboxes 2360, checkboxes 2370, and initiate a transaction selection box 2350. Checkout GUI also includes selection boxes of products, product names, product prices, retailer/manufacturer, and other information discussed in respect to checkout GUI 2310. Here, however, the information displayed in the GUI is displayed in a table. Checkboxes may be used to select which products be selected for purchase when initiate transaction selection box 2350 is selected Checkboxes 2370 may be used to identify whether a particular order should be bundled in a single transaction with a single vendor or whether an order should be fulfilled via multiple different transactions from one or more vendors. When an order is bundled each of the products selected in checkboxes 2360 may be ordered from a single vendor. When the

"individual" selection box of FIG. 23 is selected, different products may be provided by several different vendors, such as vendor A, vendor B, and vendor Etc. of FIG. 23. Like the other GUIs illustrated in the present disclosure, other information that may be displayed in a checkout GUI includes a tag number related to a product identifier, tag type information, a date when an upsell occurred, a hold status, and a shopping cart identifier.

[0157] Checkout provides the customer with a summary of the Upsell items to be purchased and allows for customers to initiate the transaction to purchase the items and select the method of fulfilment. The Checkout GUI sends transaction data to the Fulfilment Option Software which sends order data to the Processing Software to executes the requested transaction in accordance with the fulfilment option selected.

[0158] FIG. 24 illustrates an exemplary GUI where a user may select a sub-GUI that relates to a service that benefits a customer. The services GUI 2410 of FIG. 24 includes selection boxes 2420 that include a scheduling selection box, an alert selection box, a wish list selection box, a refer a friend selection box, a loyalty program selection box, a feedback selection box, and security controls selection box.

[0159] When a user selects one of the selection boxes 2420 a sub-GUI relating to that selection may be opened in another GUI at a user device. As such, a user may use services GUI 2410 to view order status in a scheduling GUI, view or set alerts in an alert GUI, view entries that they have added to a wish list in a wish list GUI, view or setup information relating to a friend in a refer a friend GUI, collect rewards via a loyalty program GUI, provide feedback to vendors via a feedback GUI, or to set or modify security settings in a security control GUI. [0160] Services are the Scheduling, Alerts, Wish List, Refer a Friend, Loyalty Program, Feedback and Security Controls provided via GUI's.

[0161] FIG. 25 illustrates exemplary GUIs that a user may use when scheduling the delivery of products they wish to order. Scheduling GUI 2510 includes selection boxes 2520 that identify a name of a product, that provide order entry date, that add a selected product to a wish list, that adds a selected product to a hold items list, or that allows the user to move to a checkout GUI to purchase a product. When checkbox 2530 is checked, the particular product selected may be added to a wish list, added to a hold items list, or be purchased by selecting an appropriate selection box.

[0162] FIG. 25 also includes selection GUI 2540 that also displays product names and order dates. Selection GUI 2540 also includes various selection boxes 2550 and checkboxes 2560. Checkboxes 2560 of FIG. 25 allow a user to select products that may be added to a hold items list, added to a wish list, or that purchased by respectively selecting the add to hold items selection box, the add to wish list selection box, or the proceed to checkout selection box of FIG. 25. One other selection box of selection boxes 2550 of FIG. 25 is the "add to schedule" selection box that when selected may allow a user to add a product to a tabulated list of products in selection GUI 2540. In instances when the "add to schedule" selection box is selected, another GUI may be added that allows a user to select products to purchase.

[0163] Scheduling provides the customer the ability to input a scheduled purchase for Upsell items. They also have ability to review the Upsell items scheduled to be purchased, add them to the Hold Items and/or the Wish List and/or purchase the items directly from this GUI.

[0164] FIG. 26 illustrates exemplary GUIs that may be used to set or change user alert settings or to setup different types of alerts. Alerts GUI 2610 includes checkbox 2620 and selection boxes 2625. Checkbox 2625 may be used to select a product and select selection boxes 2625 relating to a purchase. The selection boxes 2625 of alerts GUI 2610 includes the product name, an enter alert type selection box, an add alert selection box, an add to wish list selection box, a hold items selection box, and a proceed to checkout selection box. Here again a product may be added to a wish list, added to a hold list, or purchased by selecting an appropriate selection box. When the enter an alert type selection box is selected the alerts type GUI 2645 may be opened, where the alerts type GUI 2645 may be used by a user to enter or change the types of alerts that may be generated based on user input. When the add alert selection box of alerts GUI 2610 is selected, a user may be allowed to select an alert from a list of alerts.

[0165] Alerts GUI 2630 includes selection checkboxes 2640 that may be used by a user to select different products that can be associated with an alert or an alert type. Selection boxes 2635 allow a user to add an alert, add a product to a wish list, to add a product to a hold items list, or to proceed to checkout to purchase a product.

[0166] The alerts type GUI 2645 of FIG. 26 allow a user to set different types of alert events 2650 related to informing a user when a product goes on sale, when a product is in-stock, when a product is out of stock, or to send an alert when a new related upsell offering is available. New related upsell offering alerts may identify other products that are related to a product that a user has ordered. For example, after a user has ordered skis and when they have set an alert relating to new added upsell offerings, the user may be provided with a message that identifies that a new ski wax is available for purchase.

[0167] Alerts type GUI 2645 also includes selections of alert types 2655 that may be delivered to a user at a preferred selection times 2660. Alert types 2655 of the alerts type GUI 2645 include email, text, and voice mail notifications. A user may receive an email, a text message, or a voice mail when a selected event is scheduled or after an event has occurred. Alerts may be sent a day before a scheduled event, immediately when an event occurs, or an hour after an event has transpired. After a user has set one or more alert type settings in alerts GUI 2645, the user may select the set alert type selection box 2665 to activate their alert settings.

[0168] Alerts provides the customer the ability to assign an alert for Upsell items. They also have ability to review the Upsell items assigned an alert, add them to the Hold Items and/or the Wish List and/or purchase the items directly from this GUI. The alert type is defined in the Alert Type GUI.

[0169] Alerts Type allows for the customer to define the parameters of the alert to be assigned to the Upsell item. In one embodiment alert parameters are based on the triggering event, the style of alarm and when the alarm will activate relative to the trigger.

[0170] Wish List provides the customer the ability to maintain a list of desired Upsell items. They also have ability to review the Upsell items on the list, add them to the Hold Items and/or purchase the items directly from this GUI.

[0171] Refer A Friend provides the customer the ability refer an Upsell product to a friend by entering their email address. Other embodiments of this GUI include interfaces with other methods of communications, for example text message, voicemail, social media, etc.

[0172] FIG. 27 illustrates two exemplary GUIs that may be used by a user to access a loyalty program or to send feedback to a vendor. Loyalty program GUI 2710 may allow a user to access loyalty points or view status associated with a loyalty program by interacting with selection boxes 2720. The loyalty program GUI 2710 includes selection boxes that identifies a product name, identifies a vendor/manufacturer, allows a user to submit the product to receive loyalty program rewards, or to display status information relating to the producf s eligibility for receiving reward points.

[0173] The feedback GUI 2730 of FIG. 27 may allow a customer to provide feedback to a vendor or manufacturer. Feedback GUI includes selection boxes 2740 that identify a product name, identify a vendor/manufacturer, to provide feedback, to request feedback from a friend, or to send a message. A user may enter information relating to their satisfaction by entering information relating to a product purchased using the provide feedback selection box of FIG. 27. Alternatively or additionally a user may request that a friend provide feedback regarding a vendor by selecting the request friend's feedback selection box. Finally, feedback may be sent to a vendor or a friend may be sent a feedback request when a user selected the sent selection box of FIG. 27. [0174] Loyalty Program provides the customer the ability to submit items to vendor/manufactures to redeem loyalty program credit. Information on the product is sent to the vendor/manufacturer to request loyalty program redemption. The vendor/manufacture responds by sending status information to indicate that the item is 1) eligible or not eligible and 2) if eligible, that the loyally benefits have been awarded.

[0175] Feedback provides the customer the ability to provide feedback to the vendor/manufacturer. It also provides the ability to request that a friend provide feedback. In another embodiment, response to feedback is displayed and/or feedback from friends is displayed and/or feedback from other customers is displayed and/or other combinations of feedback data is displayed.

[0176] FIG. 28 illustrates an exemplary GUI that allows a user to set various purchase security controls. Security controls GUI 2810 of FIG. 28 includes access settings 2820, functionality settings 2830, vendor settings 2840, and spending limit settings 2850. A user using the various settings of FIG. 28 may allow a user to password protect or to biometrically secure any of the GUIs of the present disclosure. These security settings may protect a user device from being used to make orders to those who cannot provide a correct password or an appropriate biometric. Functionality settings selection box 2830 may be used to enable notifications or alerts, vendor settings 2840 may allow a user to identify preferred vendors, and spending limits settings 2850 may cause a checkout GUI consistent with the present disclosure from processing orders that cost more than a threshold amount.

[0177] FIG.29 provides two exemplary Wish List GUIs 2910 and 2930 that provide the customer the ability to maintain a list of desired Upsell items. These GUI's also allow the customer to review the Upsell items on the list, add them to the Hold Items and/or purchase the items directly from this GUI by interacting with selection boxes 2920 or 2940.

[0178] FIG. 30 Refer A Friend GUI 3010 provides the customer the ability to refer an Upsell product to a friend by by interacting with input boxes 3020 to enter their email address. Other embodiments of this GUI include interfaces with other methods of communications, for example text message, voicemail, social media, etc.

[0179] Information relating to the various GUIs or products discussed in the present disclosure may be stored at a user device, be stored in a vendor database, may be stored at an upsell system operated by a third party, or may be stored in various different locations at a user device, at a vendor, or at a third party. Software at a user device may interact with vendors and with an upsell system when methods consistent with the present disclosure are performed.

[0180] The Security Controls GUI provides access to APP settings that manage the user experience. Access settings controls how the Upsell APP is accessed; this embodiment offers password or biometric authentication. Functionality Settings controls automatic functionality of the Upsell APP; this embodiment allows control of notifications. Vendor Settings allows the user to control which vendor/ manufacturers are allowed to offer upsells. Spending limits allows the user to control the maximum spending on upsells. Other embodiments can provide similar options and opportunities to control access to upsell transactions.

[0181] The Feedback software receives feedback data from the Feedback GUI. If the feedback data is solely for the vendor/manufacturer the feedback is sent directly to the vendor/manufacturer. If the user is requesting that a friend provide feedback on a product, feedback data including the friends email is stored. This data is then send to the users email service software to generate an email that requests a friend provide feedback.

[0182] The foregoing detailed description of the technology herein has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the technology to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. The described embodiments were chosen in order to best explain the principles of the technology and its practical application to thereby enable others skilled in the art to best utilize the technology in various embodiments and with various modifications as are suited to the particular use contemplated. It is intended that the scope of the technology be defined by the claims appended hereto.