AU2017101327A4 - Frameworks and methodologies configured to enable generation of real-time response offers for delivery to client devices in response to query data via hybrid technology including rules-based process and bespoke generation process - Google Patents

Abstract

Abstract The present invention relates to frameworks and methodologies configured to enable generation of real-time response offers for delivery to client devices in response to query data via hybrid technology including rules-based process and bespoke generation process. Some embodiments provide technological infrastructure to provide purchase intent merchant stimulus; technology by which a user request enables a merchant to automatically or manually define a response offer to generate an in-store lead. this may include a geolocation dependent trigger based upon a desired product and gis intelligence. Customer Mobile Devices Example Customer Mobile Device L----------------------------- -------------- Lead Management System Data Management Subsystem ------------------- ------ -------- Customer Rerds 170 - Preconfigured Offer Data Set 161 Notification Module Generation Modile i 100 162 Offer Data Seta 11Ret P .oesn Module 162 Customer DeviceoLocation 171 Product Taxomy 162 WiFi Network Data Bespoke Offer Management Analytics Module 107 -Module Offer Templates t I Vendor Manager Devices I I Vendor Sales Devices I 120 I | Example Vendor Sales 130 Example Vendor Manager | i Device Device (e.g. smartphmne with paired smartwatch) | |

Description

FRAMEWORKS AND METHODOLOGIES CONFIGURED TO ENABLE GENERATION OF REAL-TIME RESPONSE OFFERS FOR DELIVERY TO CLIENT DEVICES IN RESPONSE TO QUERY DATA VIA HYBRID TECHNOLOGY INCLUDING RULES-BASED PROCESS AND BESPOKE GENERATION PROCESS

FIELD OF THE INVENTION

[0001] The present invention relates to frameworks and methodologies configured to enable generation of real-time response offers. Some embodiments provide technological infrastructure to provide purchase intent merchant stimulus; technology by which a user request enables a merchant to automatically or manually define a response offer to generate an in-store lead. This may include a geolocation dependent trigger based upon a desired product and GIS intelligence. While some embodiments will be described herein with particular reference to that application, it will be appreciated that the invention is not limited to such a field of use, and is applicable in broader contexts.

BACKGROUND

[0002] Any discussion of the background art throughout the specification should in no way be considered as an admission that such art is widely known or forms part of common general knowledge in the field.

[0003] A great deal of technology has been developed to enable the gathering and utilisation of sales intelligence data in the online shopping space. For example, user activity is monitored thereby to populate web pages with products predicted to be of interest to a user. There are various technical challenges associated with extending these sorts of technologies to the “offline” shopping space (i.e. physical stores).

SUMMARY OF THE INVENTION

[0004] It is an object of the present invention to overcome or ameliorate at least one of the disadvantages of the prior art, or to provide a useful alternative.

[0005] One embodiment provides a computer system configured to manage a hierarchical framework of client devices, thereby to enable delivery of real-time location-specific sales intelligence data, the system including: [0006] a data management subsystem configured to maintain data representative of a plurality of user profiles, including: [0007] (i) a plurality of highest level user profiles, wherein each highest level user profile represents a highest level user in a group hierarchy, wherein there is a plurality of group hierarchies; and [0008] (ii) a plurality of lowest level user profiles, wherein each lowest level user profile represents a lowest level user in a respective one of the plurality of group hierarchies; [0009] a data management input module that is accessible via a user interface executing at a first client terminal, wherein the user interface enables a user of the first client terminal to: [0010] (i) log-in based on a given one of the highest level user profiles, thereby to gain access permissions associated with that one of the highest level user profiles; and [0011] (ii) create one or more lowest level user profiles associated with the same group hierarchy as the given one of the highest level user profiles; [0012] wherein creating a given lowest level user profile includes: [0013] (i) associating vendor location data with the given lowest level user profile; and [0014] (ii) generating a unique identification code for the given lowest level user profile, and associating that unique identification code with the given lowest level user profile; [0015] an intelligence subsystem including: [0016] a mobile device registration module, wherein the mobile device registration module is configured to: [0017] (i) receive, from a unique mobile device having a user interface, a unique identification code associated with a given one of the lowest level user profiles; and [0018] (ii) cause updating of the maintained data representative of a plurality of user profiles such that the given one of the lowest level user profiles is associated with addressing data for the unique user device; [0019] a notification management module that is configured to: [0020] (i) receive data representative of a sales intelligence notification associated with a customer record and vendor location data; [0021] (ii) identify one of the lowest level user profiles associated with the same vendor location data; [0022] (iii) in response to a location-based trigger caused by location monitoring of a mobile device associated with the customer record, deliver the sales intelligence notification to the mobile device associated with the identified one of the lowest level user profiles.

[0023] One embodiment provides a computer system wherein the data management subsystem is configured to maintain data representative of a plurality of user profiles, including: [0024] (i) a plurality of highest level user profiles, wherein each highest level user profile represents a highest level user in a group hierarchy, wherein there is a plurality of group hierarchies; [0025] (ii) a plurality of lowest level user profiles, wherein each lowest level user profile represents a lowest level user in a respective one of the plurality of group hierarchies hierarchy; and [0026] (i) one or more tiers of mid-level user profiles, wherein each mid-level user profile is defined in a given group hierarchy nested beneath at least one highest level user profile, and has nested beneath it at least one lowest level user profile; [0027] One embodiment provides a computer system wherein the notification management module is configurable via a user interface thereby to define notifications rules.

[0028] One embodiment provides a computer system wherein a notifications rule includes providing a notification to addressing data associated with one or more user profiles belonging to a predefined group hierarchy, being of a defined level, and having defined location data, wherein the notification is provided in response to identifying of request data satisfying predefined location and taxonomy requirements.

[0029] One embodiment provides a computer system wherein the notification provides access, from a device at which the notification is received, to a user interface that enables defining of a bespoke response to the request data.

[0030] One embodiment provides a computer system wherein a notifications rule includes providing a notification to addressing data associated with one or more user profiles belonging to a predefined group hierarchy, being of a defined level, and being associated with defined vendor location data, wherein the notification is provided in response to identifying of predicted demand at a defined location.

[0031] One embodiment provides a computer system wherein the notification provides data representative of the predicted demand and determined supply.

[0032] One embodiment provides a computer system wherein the predicted demand is based on monitoring of mobile device locations for one or more mobile devices associated with customer records.

[0033] One embodiment provides a computer system wherein the predicted demand is based on monitoring of offer acceptances associated with customer records.

[0034] One embodiment provides a computer system wherein the determined supply is based on identification of a number of active mobile devices associated with lowest level user profiles and vendor location data corresponding to the defined location.

[0035] One embodiment provides a computer system configured to enable generation and configuration of offer data, the system including: [0036] a data management subsystem configured to maintain data representative of: [0037] (i) a product taxonomy, wherein the product taxonomy provides a hierarchical framework of classes for objective categorisation of goods and/or services; [0038] (ii) a plurality of vendor records, wherein each vendor record includes data representative of addressing information for one or more vendor devices configured to enable presentation of lead data, and further includes location data for a vendor physical location; [0039] an offer generation module, wherein the offer generation module is configured to be accessible to a user of a networked device that renders an offer generation user interface, wherein the offer generation module is configured to: [0040] (i) receive a request to commence generation of a new offer associated with a specified one of the vendor records; [0041] (ii) receive primary input representative of a product; [0042] (iii) based on the primary input, perform an automated process thereby to identify a class in the product taxonomy with which the new offer is to be associated, and selectively associating the new offer with that class in the taxonomy; [0043] (iv) receive secondary input representative of product details for the product; [0044] (v) based on the secondary input, perform a process thereby to associate the new offer with product details; [0045] (vi) cause presentation via the offer generation user interface of a template-driven offer structure generation interface, wherein the template-driven offer structure generation interface is configured to enable a user to select an offer structure template, and define offer structure data for that offer structure template; [0046] (vii) receive, via the template-driven offer structure generation interface, user generated offer structure data associated with a specific offer template, and associating that offer structure data associated with the specific offer template with the new offer; [0047] (vii) cause presentation of an offer publication rules interface via the offer generation user interface, wherein the offer publication rules interface is configured to enable a user to define rules for automated publication of the new offer to one or more customer client devices; and [0048] (viii) configure the new offer to be activated into a published state based on the user defined rules.

[0049] One embodiment provides a computer system wherein the primary input representative of a product includes a photo of the product, and wherein performing an automated process thereby to identify a class in the product taxonomy with which the new offer is to be associated includes an Internet-based search based on that image.

[0050] One embodiment provides a computer system wherein receiving secondary input representative of product details for the product includes receiving an image of a physical tag associated with the product.

[0051] One embodiment provides a computer system wherein performing a process thereby to associate the new offer with product details includes performing an Optical Character Recognition process on the image of the physical tag and extracting textual data representative of product details.

[0052] One embodiment provides a computer system wherein performing a process thereby to associate the new offer with product details includes reading a unique code from the image of the tag, and querying a product database based on that unique code thereby to extract data representative of product details.

[0053] One embodiment provides a computer system wherein the template-driven offer structure generation interface is configured to display a subset of offer templates selected from a full set of offer templates, wherein the selection is based on identified class in the product taxonomy with which the new offer is associated.

[0054] One embodiment provides a computer system wherein the user defined rules for automated publication of the new offer to one or more customer client devices include: a rule to make the new offer available via a customer user interface at a customer client device in response to a request from that customer client device representative of: the identified class in the product taxonomy with which the new offer is associated.

[0055] One embodiment provides a computer system wherein the user defined rules for automated publication of the new offer to one or more customer client devices include: a rule to make the new offer available via a customer user interface at a customer client device in response to a request from that customer client device representative of: a higher level class in the taxonomy under which the identified class in the product taxonomy with which the new offer is associated is nested.

[0056] One embodiment provides a computer system wherein the user defined rules for automated publication of the new offer to one or more customer client devices include: a rule to make the new offer available via one or more of: a defined web location; and a defined social media feed.

[0057] One embodiment provides a computer system including a request processing module that is configured to: [0058] (i) receive a request generated by a customer client device, wherein the request is associated with location data and with a specified class defined in the taxonomy; [0059] (ii) identify one or more offers in a published state defined by the offer generation module that match the received request based on a combination of: [0060] · location-based matching, based on proximity rules, of the request’s associated location data with a given a given offer’s vendor record’s location data; and [0061] · taxonomy-based matching based on the specified class defined in the taxonomy for the request with the identified class in the product taxonomy with which the given offer is associated; and [0062] (iii) cause presentation at the customer client device of data representative of the one or more identified offers.

[0063] One embodiment provides a computer system to enable delivery of in-store lead data, the system including: [0064] a data management subsystem configured to maintain data representative of: [0065] (i) a plurality of customer records, wherein each customer record includes data representative of addressing information for a customer client device at which a customer engagement module executes; [0066] (ii) a plurality of vendor records, wherein each vendor record includes data representative of addressing information for one or more vendor devices configured to enable presentation of lead data, and further includes location data for a vendor physical location; and [0067] (iii) a plurality of pre-configured offer data sets, wherein each defined preconfigured offer data set is associated with a vendor record and class defined in a product taxonomy, wherein the product taxonomy provides a hierarchical framework of classes for objective categorisation of goods and/or services; [0068] a customer request module, wherein the customer request module is configured to receive data representative of a customer request defined by way of interaction with the customer engagement module executing at a client device associated with a particular one of the customer records; [0069] a request processing module, wherein the request processing module is configured to process the request thereby to identify at least one class defined in the product taxonomy; [0070] a location-aware matching module that is configured to perform a matching process for the customer request thereby to identify one or more preconfigured offer data sets, the matching process including: [0071] (i) identifying location data associated with the customer client device via which the customer request is defined; [0072] (ii) proximity-based matching, based on proximity rules, of the customer client device’s associated location data with a given a given offer data set’s vendor record’s location data; and [0073] (iii) taxonomy-based matching based on the specified class defined in the taxonomy for the customer request with the identified class in the product taxonomy with which the given offer data set is associated; and [0074] a result delivery module configured to cause presentation at the customer client device of data representative of the one or more identified preconfigured offer data sets.

[0075] One embodiment provides a computer system wherein the location aware matching module is configured to perform the matching process periodically such that further preconfigured offer data sets are periodically identified responsive to changes in location data associated with the customer client device.

[0076] One embodiment provides a computer system including a bespoke offer data set management module configured to execute a bespoke offer request/response process including: [0077] (i) identifying location data associated with the client device via which the customer request is defined; [0078] (ii) identifying one or more vendor records that are matched to the customer request based on a combination of: [0079] · location-based matching, based on proximity rules, of the customer client device’s associated location data with one or more vendor record’s location data; and [0080] · taxonomy-based matching based on the specified class defined in the taxonomy for the customer request with the identified class in the product taxonomy with bespoke advertising setting associated with one or more vendor records; [0081] (iii) for each matched vendor record, causing delivery of a bespoke request notification based on addressing data associated with the vendor record, wherein the bespoke request notification enables defining via a user interface of a bespoke offer data set based on the bespoke request; and [0082] (iv) causing the result delivery module to cause presentation at the customer client device of data representative of one or more defined bespoke offer data sets.

[0083] One embodiment provides a computer system wherein the bespoke offer data set management module is configured to perform the execute a bespoke offer request/response process periodically such that further bespoke preconfigured offer data sets are periodically defined for presentation responsive to changes in location data associated with the customer client device.

[0084] One embodiment provides a computer system wherein the result delivery module is configured to cause presentation of data representative of one or more preconfigured offer data sets and one or more bespoke offer data sets for a given customer request on a common map-based interface.

[0085] One embodiment provides a mobile device including: [0086] a GPS module that is configured to enable tracking of mobile device location; [0087] a request generation module, wherein the request generation module is configured to enable a user of the mobile device to generate a request data set representative of a specified class defined in a product taxonomy, wherein the product taxonomy provides a hierarchical framework of classes for objective categorisation of goods and/or services; [0088] a request submission module that is configured to transmit to a server device: [0089] (i) customer record data associated with the mobile device; [0090] (ii) location data associated with the mobile device; [0091] (iii) the request data set; [0092] wherein the server device is configured to execute an offer identification process including: [0093] (i) a first matching process configured to identify one or more preconfigured offer sets that match the request data set based on location-based matching and taxonomy-based matching; and [0094] (ii) a second matching process that, via a bespoke offer request/response process, identifies one or more vendor records based on location-based matching and taxonomy-based matching, and enables devices associated with the one or more identified vendor records to define bespoke offer data sets; [0095] a result receipt module that is configured to receive data representative of one or more preconfigured offer data sets and one or more bespoke offer data sets responsive to execution of the offer identification process; [0096] a result presentation module that is configured to present, via a user interface of the mobile device, a user interface object that allows accessing of a rendering representative of a selected one or more of the one or more preconfigured offer data sets and one or more bespoke offer data sets.

[0097] One embodiment provides a mobile device wherein the offer identification process is periodically repeated based on updated mobile device location data, thereby to periodically identify one or more new more preconfigured offer sets and one or more new bespoke offer data sets.

[0098] One embodiment provides a mobile device wherein the mobile device includes an offer acceptance module, wherein the offer acceptance module is configured to enable a user of the mobile device to accept a given one of the one or more preconfigured offer data sets and/or one or more bespoke offer data sets, wherein the offer acceptance module is configured to, in response to the accepting, transmit data representative of the accepting to the server, wherein the server is configured to configure location monitoring rules based on the accepting.

[0099] One embodiment provides a mobile device wherein the mobile device includes an automated network identification and connection module, wherein the automated network identification and connection module is configured to identify, based on a radio of the mobile device, availability of a wireless network belonging to a predefined set, identifying a passcode for the wireless network belonging to the predefined set in data accessible to the automated network identification and connection, and automatically connect to the wireless network belonging to the predefined set via the identified passcode.

[00100] One embodiment provides a mobile device wherein the server device is configured to: [00101] (i) identify that the mobile device has connected to the wireless network belonging to the predefined set; [00102] (ii) identify that the wireless network belonging to the predefined set is associated with location data for a vendor record for a vendor in respect of which an offer data set has been accepted via the mobile device; and [00103] (iii) cause transmission of a customer arrival notification to addressing data associated with the vendor record.

[00104] One embodiment provides a computer system configured to enable delivery of in-store lead data, the system including: [00105] a data management subsystem configured to maintain data representative of: [00106] (i) a plurality of customer records, wherein each customer record includes data representative of addressing information for a customer client device at which a customer engagement module executes; [00107] (ii) a plurality of vendor records, wherein each vendor record includes data representative of addressing information for one or more vendor devices configured to enable presentation of lead data, and further includes location data for a vendor physical location; and [00108] (iii) a plurality of offer data sets, wherein each offer data set is associated with a vendor record; [00109] a customer request module, wherein the customer request module is configured to receive data representative of a customer request defined by way of interaction with the customer engagement module executing at the customer client device associated with a particular one of the customer records; [00110] a result delivery module configured to cause presentation at the customer client device of data representative of the one or more offer data sets matched to the customer request; [00111] an offer acceptance module configured to receive data representative of an acceptance notification triggered via user-interface based accepting of an offer set presented at a customer client device; [00112] a vendor notification module configured to deliver, via addressing data associated with a vendor record: [00113] (i) data representative of an acceptance notification for an offer data set associated with the vendor record; [00114] (ii) data associated with the customer record associated with the customer client device at which the accepting occurred; [00115] (iii) an arrival notification in response to identification that, based on location monitoring of the customer client device, the customer client device has a defined proximity relationship relative to the vendor physical location.

[00116] One embodiment provides a computer system wherein the data associated with the customer record associated with the customer client device at which the accepting occurred includes a photo associated with the customer record.

[00117] One embodiment provides a computer system wherein the data associated with the customer record associated with the customer client device at which the acceptance occurred includes data representative of one of more products predicted to be of interest to the customer.

[00118] One embodiment provides a computer system wherein the one or more products predicted to be of interest to the customer include a product identified based on monitoring of interaction of the customer with the customer engagement module.

[00119] One embodiment provides a computer system wherein the one or more products predicted to be of interest to the customer include a product identified based on monitoring of interaction of the customer with one or more online platforms.

[00120] One embodiment provides a computer system wherein the one or more products predicted to be of interest to the customer include a product identified based output of a sales intelligence data module that analyses data associated with the customer record.

[00121] One embodiment provides a computer system wherein the data delivered via the vendor notification module is displayed via a user interface executing on a wearable device.

[00122] One embodiment provides a computer system wherein the wearable device includes a smartwatch.

[00123] One embodiment provides a computer system wherein the wearable device includes displays either integrated into glasses, contact lenses or other visual display technologies.

[00124] One embodiment provides a computer system wherein the location monitoring of the customer client device includes location monitoring based on connection to a location-known wireless network.

[00125] One embodiment provides a computer system wherein the vendor notification module is additionally configured to deliver data representative of the customer device moving away from the vendor physical location, wherein such data causes presentation of a vendor sales outcome feedback input interface.

[00126] One embodiment provides a computer program product for performing a method as described herein.

[00127] One embodiment provides a non-transitory carrier medium for carrying computer executable code that, when executed on a processor, causes the processor to perform a method as described herein.

[00128] One embodiment provides a system configured for performing a method as described herein.

[00129] Reference throughout this specification to “one embodiment”, “some embodiments” or “an embodiment” means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrases “in one embodiment”, “in some embodiments" or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment, but may. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner, as would be apparent to one of ordinary skill in the art from this disclosure, in one or more embodiments.

[00130] As used herein, unless otherwise specified the use of the ordinal adjectives "first", "second", "third", etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.

[00131 ] In the claims below and the description herein, any one of the terms comprising, comprised of or which comprises is an open term that means including at least the elements/features that follow, but not excluding others. Thus, the term comprising, when used in the claims, should not be interpreted as being limitative to the means or elements or steps listed thereafter. For example, the scope of the expression a device comprising A and B should not be limited to devices consisting only of elements A and B. Any one of the terms including or which includes or that includes as used herein is also an open term that also means including at least the elements/features that follow the term, but not excluding others. Thus, including is synonymous with and means comprising.

[00132] As used herein, the term “exemplary” is used in the sense of providing examples, as opposed to indicating quality. That is, an “exemplary embodiment” is an embodiment provided as an example, as opposed to necessarily being an embodiment of exemplary quality.

BRIEF DESCRIPTION OF THE DRAWINGS

[00133] Embodiments of the invention will now be described, by way of example only, with reference to the accompanying drawings in which: [00134] FIG. 1A to 1C illustrate computer systems and devices according to embodiments.

[00135] FIG. 2 illustrates a user/device framework according to one embodiment.

[00136] FIG. 3A to FIG. 3D illustrate methods according to embodiments.

DETAILED DESCRIPTION

[00137] The present disclosure relates primarily to technology by which a central system enables functional interactions between mobile devices associated with customers and devices (primarily mobile and/or wearable devices) associated with vendors having physical stores. For example, some embodiments provide a combination of mobile device location monitoring with a dual form request/offer process, such that users are able to access physical store’s preconfigured and bespoke offer data sets, and such that vendors are provided real time customer sales intelligence data (including data provided via wearable device user interfaces), including data providing notifications of customer “arrivals” (i.e. events when a customer reaches a defined level of proximity to a vendor) and cross-selling opportunities.

[00138] The term “vendor” as used herein should be read broadly to include any person or business that uses the technology to assist in marketing of goods and/or services. The term “store” should also be read broadly to include any location at which a vendor conducts sale activities, including conventional physical shops, and other residential/public/other locations at which a vendor provides goods and services. In some cases a “store" (or “vendor location” as described below) varies based on observable data, for example where a vendor’s “store” and vendor location is tied to a current location of a GPS-enabled mobile device. It follows that the term “arrival” relates to an identifiable proximity relationship between a customer location and a vendor location, and is not limited to arrival at a conventional retail venue.

Overview [00139] At a very high level, technology described below is configured to support a lead generation framework, geared towards assisting vendors with physical locations (as opposed to vendors having a strictly online only presence). Mobile device apps are distributed to customers and to vendors. The customer mobile apps allow customers to search for goods/services (referred to herein by the term “products”) based on their current location. The results are derived from offer data sets, defined in some embodiments by way of the vendor mobile application (and optionally via a desktop platform). The offer data sets include both preconfigured offer data sets, which are automatically returned based on customer request attributes, and bespoke offer data sets, which a vendor generates upon receiving a real-time notification of a customer request in their vicinity (and which meets certain conditions, for example the nature of product/s requested). Upon acceptance of an offer data set by way of the customer app, notifications are provided to one or more mobile devices associated with the relevant vendor. In a preferred embodiment, these notifications allow rendering on a wearable device (such as a smartwatch) of a lead data set that includes a photo of the customer, details of the offer accepted, and information to assist with cross-selling (based on gathered sales intelligence). The notifications also inform a user of the wearable device when the customer arrives at the store (for example via customer mobile device GPS monitoring, Bluetooth-based location monitoring, or in some embodiments via connection of the customer mobile device to a prescribed local wireless network).

[00140] Technology is described below by reference to example systems and devices. It should be appreciated that these systems and devices embody numerous inventive aspects of the present technology. Further embodiments provide some of these aspects, but not others. Aspects of the technology include (but are not limited to): • Technology that provides location aware notifications directly to vendor salesperson representatives (for example via wearable device user interface), for example thereby to provide customer arrival notifications, customer identification assistance, and customer-specific cross-sell intelligence. • Technology that enables request/offer matching based on a combination of location-based matching and taxonomy based matching via a framework that provides for either or both of preconfigured offer data sets and bespoke offer data sets. • Technology that enables a streamlined intelligent user interface for the generation and publishing of offer data sets (for example digital advertisements). • Technology that enables management of a hierarchical structure of client devices, thereby to deliver real time vendor sales intelligence and analytics in a highly customisable manner. • Technology that provides real-time analytics based on monitoring of customer device location and behaviour, optionally in combination with monitoring of vendor device characteristics. ‘ • Technology that enables customer device location monitoring/detection via automated secure network connection. • Technology that enables restricted access to software functionalities at a mobile device responsive to observed device hardware operational characteristics.

[00141] Computer systems are described by reference to functionally separable modules. As used herein, the term "module" refers to a software component that is logically separable (a computer program), or a hardware component. The module of the embodiment refers to not only a module in the computer program but also a module in a hardware configuration. The discussion of the embodiment also serves as the discussion of computer programs for causing the modules to function (including a program that causes a computer to execute each step, a program that causes the computer to function as means, and a program that causes the computer to implement each function), and as the discussion of a system and a method. For convenience of explanation, the phrases "stores information," "causes information to be stored," and other phrases equivalent thereto are used. If the embodiment is a computer program, these phrases are intended to express "causes a memory device to store information" or "controls a memory device to cause the memory device to store information." The modules may correspond to the functions in a one-to-one correspondence. In a software implementation, one module may form one program or multiple modules may form one program. One module may form multiple programs. Multiple modules may be executed by a single computer. A single module may be executed by multiple computers in a distributed environment or a parallel environment. One module may include another module. In the discussion that follows, the term "connection" refers to not only a physical connection but also a logical connection (such as an exchange of data, instructions, and data reference relationship). The term "predetermined" means that something is decided in advance of a process of interest. The term "predetermined" is thus intended to refer to something that is decided in advance of a process of interest in the embodiment. Even after a process in the embodiment has started, the term "predetermined" refers to something that is decided in advance of a process of interest depending on a condition or a status of the embodiment at the present point of time or depending on a condition or status heretofore continuing down to the present point of time. If "predetermined values" are plural, the predetermined values may be different from each other, or two or more of the predetermined values (including all the values) may be equal to each other. A statement that "if A, B is to be performed" is intended to mean "that it is determined whether something is A, and that if something is determined as A, an action B is to be carried out". The statement becomes meaningless if the determination as to whether something is A is not performed.

[00142] The term "system" and the term "device" refer to an arrangement where multiple computers, hardware configurations, and devices are interconnected via a communication network (including a one-to-one communication connection). The term "system" and the term "device" also refer to an arrangement that includes a single computer, a hardware configuration, and a device. The term "system" and the term "device" have the same definition and are interchangeable with each other. The system does not include a social system that is a social "arrangement" formulated by humans.

[00143] At each process performed by a module, or at one of the processes performed by a module, information as a process target is read from a memory device, the information is then processed, and the process results are written onto the memory device. A description related to the reading of the information from the memory device prior to the process and the writing of the processed information onto the memory device subsequent to the process may be omitted as appropriate. The memory devices may include a hard disk, a random-access memory (RAM), an external storage medium, a memory device connected via a communication network, and a register within a CPU (Central Processing Unit).

[00144] FIG. 1A illustrates an example system, showing a selection of example devices. A lead management system 100 provides a central hub that interfaces the remaining devices, including: • Customer devices, including an example customer device 110. Customer devices 110 are, in this described example, mobile devices, for example smartphones. In some embodiments functionalities of customer devices are provided via alternate forms of computing device, for example desktop and/or laptop computers. Each customer device includes a customer engagement module 111, which executes at customer device thereby to enable rendering on a display of the customer device of a customer engagement user interface. Primary functions of the customer engagement module include: defining requests; reviewing offers identified in response to requests; and accepting offers. A customer device becomes associated with a customer record responsive to a login event representative of a defined customer record being performed via the customer engagement module. • Vendor manager devices, including an example vendor management device 120. Vendor management devices may include mobile devices such as smartphones, or other computing devices. Each vendor management device includes a vendor management module 121 which executes at vendor manager device thereby to enable rendering on a display of the vendor manager device of a vendor management user interface. Primary functions of the vendor management module include: configuring a vendor record; defining preconfigured offer data sets, configuring bespoke offer monitoring; defining bespoke offer data sets; publishing offer data sets via further platforms; and reviewing analytics data. • Vendor sales devices, including an example vendor sales device 130. Vendor sales devices may include wearable devices (for example smartwatches and/or display-enabled glasses; it will be appreciated that the term “wearable” should be afforded broad interpretation that is able to adapt as this fast-moving area of technology evolves). Such wearable devices in some cases operate in conjunction with mobile devices, such as smartphones (and the wearable device serves as a lightweight user interface device). Each vendor sales device includes a vendor sales module 131, which executes at vendor manager device thereby to enable rendering on a display of the vendor manager device of a vendor sales user interface. Primary functions of the vendor sales user interface include: providing a notification that a customer has accepted an offer associated with the vendor; displaying customer information for such a customer including name and photo; displaying cross-sell opportunity data; and displaying a customer arrival notification responsive to customer device location monitoring. In some embodiments vendor sales devices also provide corresponding functionalities to vendor manger devices, including defining preconfigured offer data sets, configuring bespoke offer monitoring; defining bespoke offer data sets; publishing offer data sets via further platforms; and reviewing analytics data.

[00145] Processes performed by these devices are described in more detail further below.

High Level Data Structure [00146] Embodiments described below include (or make use of) a data management subsystem (item 150 in FIG. 1A). The data management system provides access (for example read and write access) to a database that contains data relating to customers, vendors, offers, and other artefacts. The following forms of data used across various embodiments. • Customer records. Each customer record is representative of at least one customer, and includes data representative of addressing information for a customer client device at which a customer engagement module executes. The customer records additionally include, in various embodiments: customer demographic information (for example name, age, sex, photos, and the like); customer social media information (for example a Facebook profile); customer data for third party monitoring services (for example to enable access to third party data); data representative of one or more current persistent customer requests (optionally defined as a “watch list”); and data representative of one or more offer data sets that have been accepted by the customer, and data representative of customer historical activity (for example previous requests, purchases, locations, demographic buying patterns, and other data relevant for analytics purposes). In some embodiments customer records are configured to automatically update over time based on rules (for example clothing size data being updated over time automatically for customer records or other profile data relating to children). • Vendor records: Each vendor record includes data representative of addressing information for one or more vendor devices configured to enable presentation of lead data, and further includes location data for at least one vendor physical location (which may be a physical location defined by the location of a mobile device, such that the vendor physical location is point-in-time variable). As described further below, a given vendor record is in some embodiments associated with multiple vendor devices and multiple sets of location data (where a vendor has multiple physical locations). Each vendor record is additionally associated with one or more offer data sets, and rules for bespoke offer monitoring (as discussed further below). • Offer data sets. As described in more detail below, offer data sets in some embodiments include both of: preconfigured offer data sets; and bespoke offer data sets. Each offer data set is associated with a vendor record (based on a vendor responsible for generation of the offer data set), and is enabled to be associated with one or more customer records responsive to an offer acceptance process. • A product taxonomy. The product taxonomy provides a hierarchical framework of classes for objective categorisation of goods and/or services. Each vendor is associated with one or more classes in the product taxonomy. This is optionally based on a vendor configuration step, where a vendor selects classes in the product taxonomy. A vendor optionally associates its vendor record with a class (and all of its nested subclasses), or to only selected subclasses. For example, classes may include “clothing”, with nested classes for “male clothing” and “female clothing”, and further nested classes under “male clothing” for “sportswear”, “shoes”, and so on.

[00147] It will be appreciated that specifics of data structuring and storage vary between embodiments.

Example Customer Engagement Module Operation [00148] The customer engagement module is provided either via locally stored software instructions executing via a standalone app, or via code that is provided by a web server and accessed via a user interface rendered in a locally executing web browser. A user of a mobile device logs in to the customer engagement module via one of the customer records.

[00149] The customer engagement module includes a request generation module 112. The request generation module enables a user to input data representative of a request, for example via text input and/or voice input. The request processed thereby to identify one or more classes in the taxonomy (for example a request “I am shopping for jeans” is matched to a taxonomy class for “jeans”. In some embodiments the request generation module includes secondary inputs that enable request refinement (for example price parameters) and/or result sorting/filtering (for example price, discount, rating, and/or proximity).

[00150] In some embodiments customer engagement module 111 provides a favourites module 113, which is configured to enable re-submission of one or more saved previously generated requests, and/or a watch list module 114 which is configured to automatically resubmit one or more saved previously generated requests periodically (such that those requests are periodically resubmitted with updated customer device location data, such that requests managed by the watch list module in effect “follow” the user around as they geographically move.

[00151] In some embodiments request generation module 112 is configured to enable submission of a request based on the logged-in customer record, or based on alternate customer data (for example by identifying another customer record, or via defining of a secondary customer profile data set). The provision of functionality to select alternate customer data facilitates, in practice, shopping for another person. In some embodiments the user sets a secondary profile for a child, and by entering the child’s age, each year, profile data (such as clothing sizes) automatically increase to match the child’s age, and streamlining the user experience.

[00152] A request submission module 115 is configured to transmit to a server device, in respect of a request defined via module 111 (ora request stored and triggered via module 113 or module 114): (i) customer record data associated with the mobile device; (ii) current location data associated with the mobile device (for example using GPS data, or based on connection to a known local wireless network, Bluetooth, RFID, or other technologies); (iii) the request data set (which is at least representative of a class in the taxonomy).

[00153] A result receipt module 116 is configured to receive data representative of one or more offer data sets that are delivered by a lead management system 100 in response to each customer request. A result presentation module 117 that is configured to present, via a user interface of the mobile device, a user interface object that allows accessing of a rendering representative of a selected one or more of the one or more preconfigured offer data sets and one or more bespoke offer data sets. For example, in one embodiment the user interface object is a map, which shows locations associated with offer data sets.

[00154] In embodiments described herein, there are two categories of offer data sets: • Preconfigured offer data sets. These are preconfigured to be delivered in response to requests having defined attributes. • Bespoke offer data sets. These are defined by operation of vendor manager modules, with such operation occurring in response to notifications triggered in response to request having defined attributes.

[00155] Where a user interface in the form of a map is used by result presentation module 117, graphical icons representative of locations for preconfigured offer data sets are shown in an accessible form initially. Graphical icons representative of locations for bespoke offer data sets are shown in an accessible form progressively as those bespoke offer data sets are defined and transmitted (in some cases these are shown in as icons in an inactive state initially, and progressed to an active state upon receipt of a bespoke offer data set).

[00156] Result presentation module 117 is additionally configured to enable rendering of a user interface display that provides additional information provided via a given offer data set, for example offer structure (e.g. discount, etc), vendor details, product details, pricing, reviews (for example product reviews made by other users), and so on.

[00157] An offer acceptance module 118 enables a user to accept an offer displayed via the result presentation module. This triggers a process by which a one or more vendor devices associated with a vendor record with which an accepted offer is associated are provided with notifications, including notifications of offer acceptance, customer details, cross-sell opportunities, and customer arrival. In some embodiments the acceptance process triggers a payments module, which enables a user of the customer device to submit a payment associated with the offer via the customer engagement app.

[00158] In some embodiments a feedback module 119 is provided thereby to prompt for feedback regarding a customer-vendor interaction. For example, following acceptance of a given offer, a monitoring process is triggered which monitors for a customer arrival at the relevant vendor physical location and a subsequent customer departure from that vendor physical location (identified by either or both of GPS monitoring and local wireless network connection for a customer mobile device associated with the relevant customer record). In response to identification of the subsequent customer departure, the feedback module 119 provides a user interface display configured to seek feedback on the customer-vendor interaction, for example including either or both of a star rating and a purchase outcome input (for instance whether a sale associated with the accepted offer was made).

[00159] It should be appreciated that, given the broad definitions of “store”, “vendor location” and “arrival”, a customer arrival/departure event is in some cases triggered by a stationary customer device and a moving vendor device. For example, where a vendor is travelling and comes to a customer, a proximity relationship that represents customer “arrival” at a physical vendor location is in practice caused by the vendor location (which is bound to a vendor device) moving into proximity with a customer device.

[00160] Feedback module 119 is optionally used as a “loop closure” mechanism for a lead process; a lead is generated by system 100 by way of transmission of offer data sets to a customer, and system 100 is able to identify whether a customer accepts an offer associated with a vendor record and travels to a location associated with that vendor record. However, system 100 is in the embodiment presently described not directly involved in a transaction between the vendor and customer. Accordingly, additional input (such as input via module 119) is required to close the loop and determine whether a lead was successful. A further example of loop closure is discussed below in terms of a vendor device feedback module, which operates in a similar manner to module 119 but at a vendor device. There are alternate loop closing mechanisms used in further embodiments (for example POS integration with system 100).

[00161] In some embodiments offer acceptance module 118 is associated with a payment module, which enables a user to submit a payment associated with offer acceptance (for example via integration with a third party payment gateway, or embedded eCommerce functionality). However, for the purposes of examples discussed below, focus is given to examples where transactions occur directly between a customer and a vendor outside of system 100 (i.e. system 100 is a lead generation system, as opposed to an online sales system).

[00162] Mobile device 110 additionally includes a GPS module 180 configured to enable tracking of mobile device location, and a WiFi module 181 that is configured to connect to wireless networks.

[00163] An automated network identification and connection module 182 is configured to cause automated connection to secured wireless networks. This provides a secondary location monitoring capability based on knowledge of wireless network locations (and/or WiFi based triangulation), thereby to provide an alternative to GPS that is more effective in indoor environments (for example shopping malls). Module 182 maintains access to a predefined set of location-known wireless networks, and passcodes for those networks (preferably those passcodes are hidden from a user). Module 182 then monitors for availability of a wireless network belonging to the predefined set, identifies the passcode for the wireless network belonging to the predefined set, and automatically connects that wireless network (in some embodiments WiFi network details including SSID and/or passwords are downloaded automatically over time based on customer device location, optionally based on customer device location tracking). As discussed in more detail further below, automated network connection is used as a trigger for customer arrival notifications (optionally with or without connection to an offer acceptance), which provides a practical technical advantage in the context of the technology described herein. From a user perspective, a customer is provided with free wireless internet in certain areas with automated connection by way of customer engagement module 111 (and granting network connectivity access rights to that module), which incentivises installation of module 111.

[00164] In some embodiments, the request generation process is expended to provide a “gift registry” functionality, whereby one or more requests are defined based on activity carried out via a first customer record, with response data sets being provide to one or more further customer records. This allows a user associated with the first customer records to in essence create a gift registry, with one or more further users being provide response data sets when proximal a vendor location that provides a product corresponding to the first user’s request or requests. For example, the first user generates a plurality of requests, and saves those to a “gift list” (which causes data representative of the requests to be stored in a data repository of system 100). One or more further users subscribe to the first user’s “gift list”, which enables manual generation of requests and/or causes automated generation of requests based on the first user’s “gift list” requests, thereby to cause delivery of offer data sets based upon the gift list requests (hence assisting the further users in shopping for gifts for the first user).

Example Vendor Manager Module Operation - Configuration [00165] The vendor manager module is provided either via locally stored software instructions executing via a standalone app, or via code that is provided by a web server and accessed via a user interface rendered in a locally executing web browser. A user of a mobile device logs in to the vendor manager module via one of the vendor records.

[00166] A vendor details input module 122 is configured to enable inputting of vendor details, including physical location data (optionally including multiple instances of physical location data, where a vendor has multiple physical locations), vendor user data (for example different level of vendor users for a given vendor record), vendor social media (and other external publication platforms), and goods/services data.

[00167] The inputting of goods/services data via module 122 is preferably supported by a graphical user interface executing on device 120 that provides functionality to allow user review and designation of one or more classes and/or levels of classes in the product taxonomy (the term “designation” is used to describe a process whereby a user provides an instruction for a particular class or classes to become associated with the vendor record). For example, the user interface enables a user to select one of a plurality of nth level classes in the product taxonomy, and then designate either all or a subset of (n+1),h level classes nested below that n,h level class (either by positive selection or negative deselection means, i.e. exclusion or inclusion selections) and so on down the taxonomic tree.

[00168] Inputting of data representative of vendor social media, and other external publication platforms, includes configuring permissions for system 100 to publish content to social media and other platforms (via a publication module 123). As discussed below, this may include digital advertisements based on preconfigured and/or bespoke offer data sets that are defined. In some embodiments system 100 provides functionality, via input module 122, for a user to configure generation of system 100 of an automated webpage that displays vendor details and other information (based on information provided via module 122), this website providing a vehicle for publication of advertising content based on preconfigured and/or bespoke offer data sets that are defined. This provides a convenient streamlined means for a user to create (and configured automated updating of) a simple vendor website (for example where such a website does not already exist for a given vendor). In further embodiments a customer user embeds code into an existing website which enables rendering of an object to which advertising content based on preconfigured and/or bespoke offer data sets is pushed by system 100.

[00169] A vendor framework configuration module 124 enables a user of device 120 and module 121 to manage a hierarchical framework of vendor devices, thereby to enable delivery of real-time location-specific sales intelligence data (and other functions) via those devices. In this regard, each vendor record is configured to include data representative of a plurality of vendor user profiles, these having respective roles and/or permissions. In broad terms, this allows configuration of vendor user profiles for manager users (devices 120 and modules 121), salesperson users (devices 130 and modules 131), and other classes of user. A given user may have access to functionalities for multiple classes. The profiles include (i) One or more highest level vendor user profile. Each highest level user profile represents a highest level vendor user in a group hierarchy, wherein there is a plurality of group hierarchies. For the present purposes, the highest level user is referred to as a “vendor-administrator”, and has access permissions to perform all tasks available via system 100 in relation to the relevant vendor record (including management of other calluses of vendor user profiles). (ii) A plurality of lowest level user profiles, wherein each lowest level user profile represents a lowest level user in a respective one of the plurality of group hierarchies. For the present purposes, the lowest level user is referred to as a “salesperson”.

[00170] There are optionally one or more further levels between the highest and lowest levels. For the present purposes, there is one intermediate level referred to as a “manager”. An example is shown in FIG. 2, which shows a top level administrator device, three vendor manger devices, and four sales devices nested beneath each vendor manager device.

[00171] In some embodiments access rights for each level are preconfigured, and in some examples such preconfigured access rights are able to be modified (for example such that the vendor-administrator can give the same rights the vendor-administrator has to a salesperson).

[00172] Module 124 is operable as a data management input module that is accessible via a user interface executing at a first client terminal, wherein the user interface enables a user of the first client terminal to: (i) log-in based on a given one of the highest level user profiles, thereby to gain access permissions associated with that one of the highest level user profiles; and (ii) create one or more lower level user profiles associated with the same group hierarchy as the given one of the highest level user profiles.

[00173] Creating a given lowest level user profile includes: (i) Associating vendor location data with the given lower level user profile. This optionally includes either or both of physical location data, and department data. In some examples a vendor has multiple departments associated with common physical location data. In other examples a vendor has multiple departments with respective unique location data (for example where indoor device location infrastructure allows, such as where Bluetooth Low Energy (BLE) and/or WiFi triangulation is present). (ii) At least for lowest level users, generating a unique identification code for the given lowest level user profile, and associating that unique identification code with the given lowest level user profile. For example, the identification code may be an alphanumeric PIN. The identification code is configured to be inputted via a vendor sales module 131 executing at a vendor sales device 130 thereby to facilitate configuration of that vendor sales module to be identifies as belonging to a particular vendor record and vendor user profile.

[00174] In some embodiments module 124 enables setting of permissions against vendor user profiles, for example permissions relating to accessing of analytics, creation/approval of offer data sets, and other functionalities. In some embodiments module 124 enables setting of notification rules against vendor user profiles, for example to receive notifications representative of bespoke offer opportunities, supply/demand attributes (discussed below), and various other forms of alert notifications.

[00175] In relation to notifications, a notification management module 125 is in some embodiments configured to: (i) Receive data representative of a sales intelligence notification associated with a customer record and vendor location data (and other forms of data, for example data representative of what a customer is looking to buy). For example, this may include a lead data set generated in response to acceptance of a given offer data set by a consumer logged in via a given consumer record. (ii) Identify one or more of the salesperson user profiles associated with the same vendor location data. For example, the offer data set is associated with a particular vendor department, and one or more salesperson user profiles that are active (i.e. a user is logged in) and associated with that department at the relevant location are identified. (iii) In response to a location-based trigger caused by location monitoring of a mobile device associated with the customer record, deliver the sales intelligence notification to the mobile device associated with the identified one of the lowest level user profiles (and or other user profiles, depending on configuration). The location-based trigger may be caused by either of GPS tracking and/or connection to a location-known wireless network, either or which indicate proximity of the mobile device with the vendor physical location.

[00176] Notifications rules are also generated for bespoke offer opportunities. For example, a given notifications rule includes a rule for providing a notification to addressing data associated with one or more user profiles belonging to a predefined group hierarchy, being of a defined level, and having defined location data, wherein the notification is provided in response to identifying of request data satisfying predefined location and taxonomy requirements. For example, this may be used, at a practical level, to configure one or more user profiles to receive customer request data and in response define bespoke offer data sets, as discussed further below. This configuration allows setting of those notifications against manager and/or salesperson user classes. In such cases, the notification provides access, from a device at which the notification is received, to a user interface that enables defining of a bespoke response data set for given received request data.

[00177] Another class of notifications rule includes providing a notification to addressing data associated with one or more user profiles belonging to a predefined group hierarchy, being of a defined level, and being associated with defined vendor location data, wherein the notification is provided in response to identifying of predicted demand at a defined location. For example, such a notification provides data representative of the predicted demand and determined supply, optionally based on monitoring of mobile device locations for one or more mobile devices associated with customer records. By way of example, one embodiment implements supply/demand monitoring as follows: • System 100 monitors, for each vendor user, those salesperson user profiles with an active user. An active user is identified based on identification of a vendor sales device that is executing the vendor sales module and logged in using an identification code representative of a salesperson class vendor user profile. As discussed further below, technical means are implemented thereby to restrict such a log in to vendor devices connected to a prescribed wireless network or present at a prescribed geographic location, such that the active status is only possible where a vendor sales device is present at an associated vendor physical location (in some embodiments this is further broken down into departments defined at physical locations, for example “menswear” and “cosmetics” departments at a given vendor location). • Based on that monitoring, an analytics module 109 is configured to make available data representative of a number of active salesperson users at a given location, for example a location defined as a department at a physical location. This represents supply. So, for example, the analytics module is able to identify that there are N active salesperson users at Department X of Vendor Y. • System 100 monitors acceptance of offers and arrival of customer devices at vendor locations subsequent to (and related to) acceptance of offers. This allows analytics module 109 to identify anticipated demand in terms of: (i) a number of customers anticipated to be soon arriving at a vendor location (based on offer acceptances); and (ii) a number of customers present at a vendor location (based on customer device location tracking). This represents demand. So, for example, the analytics module is able to identify that there: (i) are M customers who have accepted offers from Vendor Z (relating to department Y) but not yet arrived at Vendor Z; (ii) M customers who have accepted offers from Vendor Z (relating to department Y) who have physically arrived at Vendor Z; and/or M customers for whom customer records are defined are present at Vendor Z. • System 100, based on the above, monitors a relationship between supply and demand. This is monitored at either or both of a vendor physical location basis and vendor department basis. So, for example, system 100 identifies that there are N active salesperson users Department X of Vendor Y, and M customers who have accepted offers from Vendor Z (relating to department Y) have physically arrived at Vendor Z. • Where there is a predefined imbalance between supply and demand (based on offer acceptance data, customer arrival data, and/or a combination of offer acceptance data and customer arrival data), a notification is generated (and delivered based on notification rules). This allows, for example, a manager class user to instruct salesperson users to move between locations/departments, and otherwise make preparations for anticipated customer levels. For example, in the example above, where N is 1 and M is 10, a notification may be generated.

[00178] It will be appreciated that the above example is provided for illustrative purposes only, and similar functionality is optionally provided via other means via the technology described herein. As a practical example, one way in which this delivered includes (i) identifying a supply deficit in a first department; (ii) notifications being sent to other staff members in other departments, the notifications providing a prompt to accept or decline a request for assistance for the first department (the notifications are optionally sent in series, with subsequent notifications being sent only when a given one is declined); and (iii) a manager being notified of acceptances, declines, and staff movements thereby to monitor staff balances.

[00179] In a similar manner to the preceding example, notification rules are preferably configured to check that the number of active salesperson user profiles to which a lead data set (resulting from acceptance of an offer) is to be delivered is non-zero. As noted above, the analytics module is able to identify that there are N active salesperson users at Vendor Y (and/or at a particular department/location of Vendor Y). In the case that an offer is accepted for an offer data set associated with Vendor Y (and/or at a particular department/location of Vendor Y), a check is performed to verify that there is at least one active salesperson user at Vendor Y (and/or at a particular department/location of Vendor Y). If that check fails, the notifications rules cause delivery of notifications to one or more other user profiles associated with the vendor record (for example this is configured to include the vendor-administrator and/or one or more manager users), or to deliver notifications to other addressing data (for example email, SMS, or the like). It will be appreciated that, from a practical perspective, for the technology to operate in the intended optional manner at least one salesperson user needs to be active to receive the resulting lead data set and practically service the customer upon arrival (i.e. know the customer has arrived and have information to assist in sales); these forms of notifications provide a technical means to identify where there is no such active user, and provide an opportunity to rectify the situation. Even where there is no active salesperson user, customer users are able to view and accept offers.

Example Vendor Manager Module Operation - Preconfigured Offer Set Generation [00180] As noted above, offer data sets that are presented via customer engagement modules 111 of customer devices 110 include preconfigured offer sets. This section described example processes performed via the vendor manager module 121 of a vendor device 120 thereby to generate preconfigured offer data sets.

[00181 ] Vendor manager module 121 includes a preconfigured offer data set generation module 126. Module 126 provides a user interface that allows for user generation of preconfigured offer data sets. In one embodiment, this includes the following primary methods: • Accessing of a saved previously created offer data set, and modification of that data set to define a new data set. • Creation of an offer data set directed to an entire product line, based on selection of a class in the product taxonomy having multiple classes nested beneath (for example an offer data set directed to “male clothing” generally). • Creation of a customised preconfigured data set.

[00182] Not all of these are present in all embodiments.

[00183] In relation to creation of a customised preconfigured data set, module 126 of device 120, in conjunction with a corresponding preconfigured offer data set generation module 170 of system 100, provides a computer system configured to enable generation and configuration of offer data in a particularly streamlined manner.

[00184] As noted previously, the data management subsystem of system 100 is configured to maintain data representative of: (i) a product taxonomy, wherein the product taxonomy provides a hierarchical framework of classes for objective categorisation of goods and/or services; and (ii) a plurality of vendor records, wherein each vendor record includes data representative of addressing information for one or more vendor devices configured to enable presentation of lead data, and further includes location data for a vendor physical location; [00185] Preconfigured offer data set generation module 170 is configured to be accessible to a user of a networked device that renders an offer generation user interface, in this example being device 120 executing module 121 and module 126. Offer generation module 170 is configured to: (i) Receive a request (from the vendor manager user) to commence generation of a new offer associated with a specified one of the vendor records. (ii) Receive primary input representative of a product. (iii) Based on the primary input, perform an automated process thereby to identify a class in the product taxonomy with which the new offer is to be associated, and selectively associating the new offer with that class in the taxonomy (“selectively” in the sense that in some embodiments a user is provided an opportunity to confirm or reject an automated association). (iv) Receive secondary input representative of product details for the product. (v) Based on the secondary input, perform a process thereby to associate the new offer with product details; (vi) Cause presentation via the offer generation user interface of a template-driven offer structure generation interface, wherein the template-driven offer structure generation interface is configured to enable a user to select an offer structure template, and define offer structure data for that offer structure template. The offer structure templates include templates to, for example, apply a “percentage off offer, a “two-for-one” offer, and so on. (vii) Receive, via the template-driven offer structure generation interface, user generated offer structure data associated with a specific offer template, and associating that offer structure data associated with the specific offer template with the new offer. (vii) Cause presentation of an offer publication rules interface via the offer generation user interface, wherein the offer publication rules interface is configured to enable a user to define rules for automated publication of the new offer to one or more customer client devices. (viii) Configure the new offer to be activated into a published state based on the user defined rules.

[00186] Process (ii) may include text-based input (for example a textual product description), and the automated process at (iii) to identify a class in the product taxonomy includes searching based on that text (for example the work “jeans” may be matched to a taxonomy class of “jeans”, or deeper searching associates a brand/form of jeans present in the text data to the taxonomy class of “jeans”). In a preferred embodiment, the primary input at (i) is defined by a photo of the product (captured by device 120), and the automated process at (iii) to identify a class in the product taxonomy includes an Internet-based search based on that image (for example a photo of a pair of jeans is identified as showing “jeans” and hence associated with a taxonomy class for “jeans”).

[00187] Receiving secondary input at process (iv) may include textual input. However, in a preferred embodiment this process includes receiving an image (captured by device 120) of a physical tag (e.g. swing tag) associated with the product. This image data is then process via OCR (and/or other techniques) to extracting textual data representative of product details. Alternately, in some embodiments integration with a vendor database system enables extraction of product details via a barcode or the like. That is, performing a process thereby to associate the new offer with product details includes reading a unique code from the image of the tag, and querying a product database based on that unique code thereby to extract data representative of product details.

[00188] In some embodiments a vendor manager user provides to system 100 data (e.g. an XML file) with data representative of to an email address with barcodes, images and item descriptions, thereby to configure system 100 to recognise data on product tags and streamline offer data set generation.

[00189] Alternatively, in some embodiments a vendor manger user can request a template for a given sector/department. A CSV file is provided with possible sale discounts that they can select. This can then be filled out off line coupled with the above information (previous paragraph) and this can be sent to system 100, uploading all marked for advertising along with their sale prices.

[00190] In some embodiments, the template-driven offer structure generation interface is configured to display a subset of offer templates selected from a full set of offer templates, wherein the selection is based on identified class in the product taxonomy with which the new offer is associated. As noted, the offer structure templates include templates to, for example, apply a “percentage off” offer, a “two-for-one” offer, and so on. In practice, certain forms of offer are relevant to certain types of goods and/or services, but not others. The present approach tailors offer structure templates based on taxonomy classes, such that only designated relevant templates are presented.

[00191] Template examples include: buy X get X free, buy X get X% off, buy X get X% of Xth item, X% off, sale price of X, X% interest rate, $X per hour, $X for X hours, and so on (the user selects a template and inputs values for X). It will be appreciated these that templates are also able to be used in the customer engagement module thereby to facilitate filtering of results.

[00192] The user defined rules of processes (vii) and (viii) preferably include a rule to make the new offer available via a customer user interface at a customer client device in response to a request from that customer client device representative of: the identified class in the product taxonomy with which the new offer is associated; and/or a higher level class un the taxonomy under which the identified class in the product taxonomy with which the new offer is associated is nested.

[00193] The user defined rules for automated publication of the new offer to one or more customer client devices may also include: a rule to make the new offer available via one or more of: a defined web location; and a defined social media feed, rules relating to the time at which an offer is to be active (for example certain times of day only, a start/finish date, and so on), and other forms of rules.

[00194] As discussed in more detail further below, a request processing module 171 of system 100 is configured to: (i) receive a request generated by a customer client device, wherein the request is associated with location data and with a specified class defined in the taxonomy; (ii) identify one or more offers in a published state defined by the offer generation module that match the received request based on a combination of: • location-based matching, based on proximity rules, of the request’s associated location data with a given a given offer’s vendor record’s location data (noting that vendor location data may be point-in-time variable); and • taxonomy-based matching based on the specified class defined in the taxonomy for the request with the identified class in the product taxonomy with which the given offer is associated; and (iii) cause presentation at the customer client device of data representative of the one or more identified offers.

[00195] In this manner, preconfigured offers are published and hence able to be delivered to customer devices 110 based on request defined via modules 111 of those customer devices.

[00196] The location-based matching is preferably configured responsive to product attributes (for example proximity rules are defined for each class in the taxonomy). For example, in one embodiment each class in the taxonomy is associated with a proximity radius value (with a proximity radius value of X kilometres meaning that location-based matching for a request data set is performed based on vendors having vendor location data within X kilometres of the requesting user device’s current location). In some embodiments the proximity radius value is defined based on a set of proximity radius rules, which allow variation of a radius based on other factors (optionally including number of result offer data sets identified). In some embodiments the proximity radius and/or proximity radius rules is defined based on an attribute of the request data other than (or in addition to) the taxonomy class. In some embodiments the proximity radius and/or proximity radius rules are defined to allow radius size determination based on market saturation (larger radius where there are less results for a request), The term “radius” should be afforded a particularly broad definition, to include both a radius defined “as the crow flies” and a radius based on other factors (such as travel times by foot, public transportation, car, and/or other vehicle).

[00197] Defining of request-variable proximity radius data allows the concept of proximity to be subjectively managed based on different products, and subjective analysis of the propensity of customers to travel for such products. For instance, some products (such as, for example, coffee) are set with a proximity threshold of less than 500 m, whereas others (such as automobiles) are set with a significantly larger proximity threshold (say 30 km).

Example Vendor Manager Module Operation - Bespoke Offer Generation [00198] As noted above, system 100 allows for bespoke offer data sets, which are defined by way of vendor manager modules 121 of vendor manager devices 120 in response to customer request having defined attributes (those attributes resulting in delivery of a notification to particular vendor manager modules 121 of vendor manager devices 120).

[00199] System 100 includes a bespoke offer management module 107 that is configured to execute a bespoke offer request/response process including: (i) Identifying location data associated with the client device via which the customer request is defined. For example, this information is defined by way of a customer device GPS module and transmitted as part of a request data set. (ii) Identifying one or more vendor records that are matched to the customer request based on a combination of: • location-based matching, based on proximity rules, of the customer client device’s associated location data with one or more vendor record’s location data; and • taxonomy-based matching based on the specified class defined in the taxonomy for the customer request with the identified class in the product taxonomy with bespoke advertising setting associated with one or more vendor records (additional matching, such as matching based on factors such as age, size and gender may also be applied). (iii) For each matched vendor record, causing delivery of a bespoke request notification based on addressing data associated with the vendor record, wherein the bespoke request notification enables defining via a user interface of a bespoke offer data set based on the bespoke request. This notification is received by one or more vendor manager devices 130 having bespoke offer set generation modules 128 provided by their respective modules 121. (iv) Causing a result delivery module to cause presentation at the customer client device of data representative of one or more defined bespoke offer data sets (for example via an interface in the form of a map provided via result presentation module 117 of module 111 of a device 110).

[00200] The defining via a user interface of a bespoke offer data set based on the bespoke request is optionally implemented via a process similar to the preconfigured data set generation process described above, however with certain data pre-populated based on the request. The process preferably makes use of the same offer structure template approach.

[00201] In some embodiments, a vendor manager user is presented with data representative of a state of a customer engagement module during the bespoke offer generation process.” For example, this state may include filter settings being applied by the customer user. This allows the vendor manager user to customise the bespoke offer data set to optimise its prevalence in a result set displayed to the customer. For example, a vendor manager user is shown that the customer user is filtering by “% discount”, and hence define a bespoke offer data knowing that a high “% discount” offer structure will be advantageous.

[00202] Bespoke offer generation, for instance as described in the above example, is of particular significance in solving technical problems associated with advertising. In particular, there is a technical challenge in configuring advertising that is personalised to particular times and places. Bespoke offer generation provides a framework whereby advertising is point-in-time generated via technical means in response to a particular customer request. Furthermore, by providing a combination of both preconfigured offer data sets and bespoke offer data sets, a further technical hurdle of result latency is overcome; a user is presented with results almost instantly, and as such has a first set of results to review during a period of time over which bespoke offers are generated and provided.

Example Vendor Sales Module Operation [00203] As noted above, each vendor sales device 130 executes a vendor sales module 131. In a preferred embodiment, module 131 includes a user interface that is presented via a wearable device (for example a smartwatch or display-enabled glasses). In some such embodiments the wearable device is paired to a mobile device (such as a smartphone), and presents a thin user interface. In other embodiments the wearable device connects directly to a network, and includes a local processor that executes module 131.

[00204] By way of vendor sales devices 130 and modules 131, the overall system is configured to enable delivery of in-store lead data. As noted above, the data management subsystem configured to maintain data representative of: (i) a plurality of customer records, wherein each customer record includes data representative of addressing information for a customer client device at which a customer engagement module executes; (ii) a plurality of vendor records, wherein each vendor record includes data representative of addressing information for one or more vendor devices configured to enable presentation of lead data, and further includes location data for a vendor physical location; and (iii) a plurality of offer data sets, wherein each offer data set is associated with a vendor record.

[00205] Furthermore, and again as noted above, system 100 is configured to receive data representative of a customer request defined by way of interaction with the customer engagement module executing at the customer client device associated with a particular one of the customer records, and a result delivery module is configured to cause presentation at the customer client device of data representative of one or more defined bespoke offer data sets (for example selectable icons displayed via an interface in the form of a map provided via result presentation module 117 of module 111 of a device 110).

[00206] System 100 includes an offer acceptance module 108 configured to receive data representative of an acceptance notification triggered via user-interface based accepting of an offer set presented at a customer client device (which in the current embodiments is transmitted via an acceptance module 118 at the customer client device).

Based on this, system 100 is configured to identify whenever an offer data set is accepted by a user associated with a known customer record. This allows a salesperson notification and intelligence presentation process as discussed below.

[00207] As shown in the figures, system 100 includes a vendor notification module 161 configured to deliver, via addressing data associated with a vendor record, data that defines in whole or in part a lead data set.

[00208] The lead data set includes data representative of an acceptance notification for an offer data set associated with the vendor record, along with data associated with the customer record associated with the customer client device at which the accepting occurred. The data associated with the customer record includes: • A photo associated with the customer record. This may be a photo uploaded by the customer as part of defining their customer record, or a photo extracted from a social media account (or other location) associated with the customer. • Data representative of one of more products predicted to be of interest to the customer, based on customer activity observed by way of monitoring interactions with module 111. For example, this may be based upon past request, for example past requests that are saved to a watch list. So, for example, in the case that the customer accepts an offer data set associated with a given vendor, and the customer record has stored in a watch list a product associated with a taxonomy class that is also associated with the vendor’s vendor record, then the data representative of one of more products predicted to be of interest to the customer includes data representative of that product. This assists in cross-selling, as a salesperson is pre-warned prior to arrival of a customer of other goods/services in respect of which the customer has a known interest (and again upon arrival). • Data representative of one of more products predicted to be of interest to the customer, based on customer activity observed by way of external sales intelligence processing (optionally via multiple sources of data). For example, this processing may include data from one or more technology platforms that monitor online browsing behaviours (for example social network posts, interests and interactions), and/or platforms that are configured to predict purchase likelihoods based on customer demographics, trends, and other sales intelligence factors. Again, this assists in cross-selling, as a salesperson is pre-warned prior to arrival of a customer of other goods/services in respect of which the customer has a potential interest. Technology for gathering such data representative of products predicted to be of interest is known in the field; technology described herein provides a novel and inventive means for utilising/distributing that data in an efficient manner.

[00209] Notification module 161 is also configured to transmit an arrival notification in response to identification that, based on location monitoring of the customer client device via a location monitoring module 162, the customer client device has a defined proximity relationship relative to the vendor physical location (for example by the customer device location moving into proximity with a fixed vendor location, or a variable vendor location moving into proximity with the customer device location) . This may include monitoring based on GPS (or other customer device derived positioning data) and/or monitoring based on customer device interaction with hardware at the vendor location (for example a WiFi router, BLE/Bluetooth beacon, and so on).

[00210] In a preferred embodiment, notification module 161 is, in response to data representative of acceptance of an offer, configured to monitor for presence of the accepting customer device’s presence of on a specific wireless network associated with the vendor record for the accepted offer data set. This preferably involves the vendor providing data representative of a local wireless network to system 100 during the vendor configuration process (via a manager device 120).

[00211] In a preferred embodiment, network connection based customer device location monitoring is facilitated by an automated network identification and connection module 184 that executes at each customer device 110. In the present embodiment this is a module provided by way of module 111, with module 111 functionally being represented by a single app that is installed on device 110. This app is configured to prompt a user to grant access to perform automated network connections.

[00212] The automated network identification and connection module is configured to identify, based on a radio of the mobile device, availability of a wireless network belonging to a predefined set. For example, the predefined set is defined in a data store maintained by system 100 (and/or replicated in local memory of device 110) based on vendors providing data representative of their respective local wireless networks to system 100 during the vendor configuration process (via a manager device 120). Upon identifying a network belonging to the set, module 184 identifies a passcode for the wireless network based on data locally stored or retrieved from system 100, and uses that passcode to connect to the network (the passcode is not made available to a user of device 110; for example it is encrypted and/or stored in a location that is not readily accessible by conventional user operations).

[00213] In this manner, upon a customer device 110 having a module 111 installed (and operating in a background execution capacity) moves into an area having a vendor’s wireless network, an automated connection to that network is made. Hence, where notification module 161 is, in response to data representative of acceptance of an offer, configured to monitor for presence of the accepting customer device’s presence on a specific wireless network associated with the vendor record for the accepted offer data set, automated connection causes such monitoring to be effective as a location-based customer device identification process. System 100 is in this regard configured to: (i) identify that the mobile device has connected to the wireless network belonging to the predefined set; (ii) identify that the wireless network belonging to the predefined set is associated with location data for a vendor record for a vendor in respect of which an offer data set has been accepted via the mobile device; and (iii) cause transmission of a customer arrival notification to addressing data associated with the vendor record.

[00214] As noted above, this data delivered via the vendor notification module is displayed via a user interface executing on a wearable device, such as a smartwatch. Hence, a salesperson user having such a smartwatch is informed both: (i) of a customer accepting an offer (being an offer associated by system 100 with that vendor record to which the salesperson user belongs), along information to facilitate preparing for the customer’s arrival (including a photo of the customer, and sales intelligence to assist in cross-selling); and (ii) a notification informing that the customer has arrived (or at least is within a threshold proximity that is deemed indicative of arrival).

[00215] In some embodiments, customer device location monitoring is additionally used to identify an event where a consumer device leaves a vendor location following and acceptance-related arrival event. This triggers a process by which system 100 causes device 130 to display a prompt to provide input representative of a customer interaction outcome (for example any one or more of: whether a sale was made connected to the accepted offer, whether a cross-sale was made, whether no sale was made, whether the customer was or was not identified by the salesperson user, and optionally other forms of input).

[00216] The vendor sales module is also configured for automated network connection, in a similar manner to the customer engagement module (that is it maintains access to data representative of prescribed wireless networks and passcodes for those networks). However, unlike the customer engagement module which connects to any of the prescribed networks), the vendor sales module connects only to networks that are associated with either or both of: the associated vendor record; and the salesperson user profile. Furthermore, the vendor sales module is configured to be operable in two states: a first state wherein the vendor sales device is not connected to a prescribed network and notifications from notification module 161 are not available (these are either not transmitted, or not displayed); and a second state in which the vendor sales device is connected to a prescribed network and notifications from notification module 161 are received and displayed. In this manner, access to lead data is provided to a device 130 only when that device is at a vendor location, hence restricting employee access to such data to times when the employee is on-site. In some embodiments additional and/or alternative technical means are employed to facilitate such restrictions.

[00217] More generally, an aspect of the present technology is embodied in a system that is configured to maintain data regarding customers, for example identifying information (such as names and photos) and sales intelligence information (for example based on interaction with a request/offer platform as herein described and/or other platforms that are configured to monitor interactions with web-based services), wherein the system is configured to monitor the location of those customers (for example via WiFi identification, geolocation, and/or other mobile device detection/monitoring technologies), and based on that monitoring deliver lead data to vendor computer systems (for example to known vendor mobile devices, wearables, and the like). In this manner, sales intelligence data is collected via any available customer analysis technology, and used to provide intelligence to vendors to assist sales to customers that visit their stores (either where there has been an offer acceptance as described above, or in other embodiments without such an offer acceptance). In some embodiments, this is configured in the context of a monetisation framework whereby a vendor is charged based on events whereby a known customer device moves into proximity with a vendor location, and sales lead data is communicated to the vendor in relation to the customer associated with that customer device.

[00218] In a further embodiment, a customer user is enabled via the customer engagement module to control settings data that affects sales lead data provided to vendor sales devices. For example, in one embodiment a customer user is enabled to set a “minimal engagement” setting, under which the data provided to the vendor sales device indicates that the customer user simply wishes to come to the vendor location and obtain a product associated with an accepted offer data set in an efficient manner with minimal extra interaction (e.g. cross-selling attempts). In one example, where a customer user has selected such a setting, cross-selling data is delivered to the customer device rather than to the vendor sales device, such that the customer is still informed of other potentially interesting purchase opportunities at the vendor location, but without necessarily interfering with an efficient purchase of accepted offer related products whilst at the vendor location.

Example Vendor Manager Module Operation - Analytics [00219] System 100 is configured to maintain and enables access to a range of analytics data based on monitoring of consumer interactions. This optionally includes data representative of trends in customer activity, data representative of sales conversions based on offers, and so on.

[00220] One particularly significant category of analytics is missed sales analytics. This is employed to solve a technical problem of inability to determine, for offline sales (that is, sales at physical vendor locations as opposed to online stores) the extent to which sales are being lost to competitors. Missed sales analytics is achieved via a process performed by system 100 including: (i) maintaining data representative of requests for each taxonomy class (and optionally whether those requests are successfully converted into sales); (ii) identifying data representative of a number of requests made within a predefined proximity to the vendor physical location for the vendor record that are associated with a taxonomy class which is also associated with the vendor record; (iii) for the requests identified at (ii), providing to a vendor manager device data representative of which of those requests were successful for the vendor, and those which were successful to another vendor (being “successful” in the sense of offer acceptance by a customer device and/or successfully converted into a sale).

[00221] In this manner, a vendor is able to identify opportunities that were lost to competitors, and based upon that, optimise a strategy for defining preconfigured offer data sets, defining bespoke offer data sets and/ monitoring for opportunities to define bespoke offer data sets.

[00222] The above approach is optionally extended to where consumers are asking for products that are not being serviced by any merchant; that is also a missed opportunity (this might be representative of issues with a given vendor’s taxonomy associations, and/or present an opportunity for a vendor to expand product offerings based on what is being sought by customers locally).

Example Methods [00223] FIG. 3A to FIG. 3D illustrate example methods according to embodiments, based on technology described above. These are examples only, and described briefly below.

[00224] Method 300 of FIG. 3A shows an offer an acceptance process performed by way of an app that embodies customer engagement module 111 executing on a customer device 110, in conjunction with system 100. The app is launched at 301, and request data is defined at 302 (for example via spoken or typed input). That request is then sent for processing by system 100 at 303, based on current mobile device location data (and other data associated with the relevant customer record, or another designated customer profile). Block 304 represents automated identification of preconfigured offer data sets that are matched to the request data. Block 305a represents generating notifications to invite vendors to generate bespoke offer data sets (which are generated at 320), and receipt of bespoke offer data sets. It will be appreciated that processes of blocks 304, 305a, 305b and 320 may occur repeatedly (for example as location data changes, and as more bespoke offer data sets are generated). Block 307 represents presentation of offer data sets in the user interface of module 111, for example via a graphical map style object. Block 308 represents user review of offer data sets and an acceptance event, and block 309 represents triggering of sales lead data and customer location monitoring in response to the acceptance.

[00225] Method 310 of FIG. 3B represents a sales lead process following offer acceptance. The method commences with block 309 of FIG. 3A, which as noted above 309 represents triggering of sales lead data and customer location monitoring in response to the acceptance of an offer. Block 311 represents defining of a sales intelligence data packet, including information about the customer (including a photo), information about the offer that was accepted, and sales intelligence data to facilitate cross-selling to that customer based on knowledge about the customer (for example as described above). That data is transmitted to one or more vendor sales devices at 312 (based on vendor profile settings). Location monitoring is configured at 313, thereby to monitor for arrival of the customer at the vendor’s location (either by the customer coming to the vendor location, or by the vendor location coming to the customer) at 314. A location-based trigger occurs at 315 upon detection of a proximity relationship between the customer device and the vendor physical location, and an arrival notification is then transmitted to the one or more vendor sales devices at 316.

[00226] Method 320 of FIG 3C shows a bespoke offer generation process performed by a sales manager device. Block 321 represents receipt of a bespoke offer opportunity notification (which includes data representative of the customer and the request). Blocks 322 and 323 represent a process by which the vendor defines an offer data set, including goods/services being offered (which may be derived directly from the request) and an offer structure from an offer structure template (for example a percentage off, 2-4-1, or the like). The bespoke offer data set is then transmitted back to system 100 at 324, and from there transmitted to the customer device.

[00227] Method 330 of FIG. 3D shows an example advertisement generation process (for example in relation to a preconfigured offer data set). The process commences at block 321. At block 322 a vendor user inputs primary product input, such as a photo of the product being offered, and completes taxonomy association (for example with assistance from a web-based photo object recognition algorithm). Block 324 represents a secondary product input, in this case being a photo of a product swing tag (which is used to extract product information such as price using OCR, barcodes, or other data extraction technologies). Offer structure templates are identified at 325 based on the relevant taxonomy class for the offer. A user selects and customises one of those templates at 326. Then, at 327, the user confirms auto-delivery rules (for example request characteristics that will trigger delivery of the offer data set). At 328, the user configures additional publication settings (for example sharing of the offer data set via social media and/or website objects).

Conclusions and Interpretation [00228] It will be appreciated that the technology described above provides significant technical advancements in the context of interfacing physical devices for the purposes of information sharing and location-aware functionality.

[00229] Unless specifically stated otherwise, as apparent from the following discussions, it is appreciated that throughout the specification discussions utilizing terms such as "processing," "computing," "calculating," “determining”, analyzing” or the like, refer to the action and/or processes of a computer or computing system, or similar electronic computing device, that manipulate and/or transform data represented as physical, such as electronic, quantities into other data similarly represented as physical quantities.

[00230] In a similar manner, the term "processor" may refer to any device or portion of a device that processes electronic data, e.g., from registers and/or memory to transform that electronic data into other electronic data that, e.g., may be stored in registers and/or memory. A “computer” or a “computing machine” or a "computing platform" may include one or more processors.

[00231] The methodologies described herein are, in one embodiment, performable by one or more processors that accept computer-readable (also called machine-readable) code containing a set of instructions that when executed by one or more of the processors carry out at least one of the methods described herein. Any processor capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken are included. Thus, one example is a typical processing system that includes one or more processors. Each processor may include one or more of a CPU, a graphics processing unit, and a programmable DSP unit. The processing system further may include a memory subsystem including main RAM and/or a static RAM, and/or ROM. A bus subsystem may be included for communicating between the components. The processing system further may be a distributed processing system with processors coupled by a network. If the processing system requires a display, such a display may be included, e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT) display. If manual data entry is required, the processing system also includes an input device such as one or more of an alphanumeric input unit such as a keyboard, a pointing control device such as a mouse, and so forth. The term memory unit as used herein, if clear from the context and unless explicitly stated otherwise, also encompasses a storage system such as a disk drive unit. The processing system in some configurations may include a sound output device, and a network interface device. The memory subsystem thus includes a computer-readable carrier medium that carries computer-readable code (e.g., software) including a set of instructions to cause performing, when executed by one or more processors, one of more of the methods described herein. Note that when the method includes several elements, e.g., several steps, no ordering of such elements is implied, unless specifically stated. The software may reside in the hard disk, or may also reside, completely or at least partially, within the RAM and/or within the processor during execution thereof by the computer system. Thus, the memory and the processor also constitute computer-readable carrier medium carrying computer-readable code.

[00232] Furthermore, a computer-readable carrier medium may form, or be included in a computer program product.

[00233] In alternative embodiments, the one or more processors operate as a standalone device or may be connected, e.g., networked to other processor(s), in a networked deployment, the one or more processors may operate in the capacity of a server or a user machine in server-user network environment, or as a peer machine in a peer-to-peer or distributed network environment. The one or more processors may form a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.

[00234] Note that while diagrams only show a single processor and a single memory that carries the computer-readable code, those in the art will understand that many of the components described above are included, but not explicitly shown or described in order not to obscure the inventive aspect. For example, while only a single machine is illustrated, the term "machine" shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

[00235] Thus, one embodiment of each of the methods described herein is in the form of a computer-readable carrier medium carrying a set of instructions, e.g., a computer program that is for execution on one or more processors, e.g., one or more processors that are part of web server arrangement. Thus, as will be appreciated by those skilled in the art, embodiments of the present invention may be embodied as a method, an apparatus such as a special purpose apparatus, an apparatus such as a data processing system, or a computer-readable carrier medium, e.g., a computer program product. The computer-readable carrier medium carries computer readable code including a set of instructions that when executed on one or more processors cause the processor or processors to implement a method. Accordingly, aspects of the present invention may take the form of a method, an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of carrier medium (e.g., a computer program product on a computer-readable storage medium) carrying computer-readable program code embodied in the medium.

[00236] The software may further be transmitted or received over a network via a network interface device. While the carrier medium is shown in an exemplary embodiment to be a single medium, the term "carrier medium" should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term "carrier medium" shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by one or more of the processors and that cause the one or more processors to perform any one or more of the methodologies of the present invention. A carrier medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media includes, for example, optical, magnetic disks, and magneto-optical disks. Volatile media includes dynamic memory, such as main memory. Transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise a bus subsystem. Transmission media also may also take the form of acoustic or light waves, such as those generated during radio wave and infrared data communications. For example, the term "carrier medium" shall accordingly be taken to included, but not be limited to, solid-state memories, a computer product embodied in optical and magnetic media; a medium bearing a propagated signal detectable by at least one processor of one or more processors and representing a set of instructions that, when executed, implement a method; and a transmission medium in a network bearing a propagated signal detectable by at least one processor of the one or more processors and representing the set of instructions.

[00237] It will be understood that the steps of methods discussed are performed in one embodiment by an appropriate processor (or processors) of a processing (i.e., computer) system executing instructions (computer-readable code) stored in storage. It will also be understood that the invention is not limited to any particular implementation or programming technique and that the invention may be implemented using any appropriate techniques for implementing the functionality described herein. The invention is not limited to any particular programming language or operating system.

[00238] It should be appreciated that in the above description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, FIG., or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the Detailed Description are hereby expressly incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment of this invention.

[00239] Furthermore, while some embodiments described herein include some but not other features included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the invention, and form different embodiments, as would be understood by those skilled in the art. For example, in the following claims, any of the claimed embodiments can be used in any combination.

[00240] Furthermore, some of the embodiments are described herein as a method or combination of elements of a method that can be implemented by a processor of a computer system or by other means of carrying out the function. Thus, a processor with the necessary instructions for carrying out such a method or element of a method forms a means for carrying out the method or element of a method. Furthermore, an element described herein of an apparatus embodiment is an example of a means for carrying out the function performed by the element for the purpose of carrying out the invention.

[00241] In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In other instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.

[00242] Similarly, it is to be noticed that the term coupled, when used in the claims, should not be interpreted as being limited to direct connections only. The terms "coupled" and "connected," along with their derivatives, may be used. It should be understood that these terms are not intended as synonyms for each other. Thus, the scope of the expression a device A coupled to a device B should not be limited to devices or systems wherein an output of device A is directly connected to an input of device B. It means that there exists a path between an output of A and an input of B which may be a path including other devices or means. "Coupled" may mean that two or more elements are either in direct physical or electrical contact, or that two or more elements are not in direct contact with each other but yet still co-operate or interact with each other.

[00243] Thus, while there has been described what are believed to be the preferred embodiments of the invention, those skilled in the art will recognize that other and further modifications may be made thereto without departing from the spirit of the invention, and it is intended to claim all such changes and modifications as falling within the scope of the invention. For example, any formulas given above are merely representative of procedures that may be used. Functionality may be added or deleted from the block diagrams and operations may be interchanged among functional blocks. Steps may be added or deleted to methods described within the scope of the present invention.

Claims (2)

1. CLAIMS:

   1. A system configured to enable generation of data for delivery to client devices, the system including: a data management subsystem configured to maintain data representative of: (i) a plurality of customer records, wherein each customer record includes data representative of addressing information for a customer client device at which a customer engagement module executes; (ii) a plurality of vendor records, wherein each vendor record includes data representative of addressing information for one or more vendor devices configured to enable presentation of lead data, and further includes location data for a vendor physical location; and a customer request module, wherein the customer request module is configured to receive data representative of a customer request defined by way of interaction with the customer engagement module executing at a client device associated with a particular one of the customer records; a request processing module, wherein the request processing module is configured to process the request thereby to identify at least one class defined in the product taxonomy; a bespoke offer data set management module configured to execute a bespoke offer request/response process including: (i) identifying location data associated with the client device via which the customer request is defined; (ii) identifying one or more vendor records that are matched to the customer request based on a combination of: • location-based matching, based on proximity rules, of the customer client device’s associated location data with one or more vendor record’s location data; and • taxonomy-based matching based on the specified class defined in the taxonomy for the customer request with the identified class in the product taxonomy with bespoke advertising setting associated with one or more vendor records; (iii) for each matched vendor record, causing delivery of a bespoke request notification based on addressing data associated with the vendor record, wherein the bespoke request notification enables defining via a user interface of a bespoke offer data set based on the bespoke request; and (iv) causing the result delivery module to cause presentation at the customer client device of data representative of one or more defined bespoke offer data sets.
2. 2. A method according to claim 1 wherein the bespoke offer data set management module is configured to perform the execute a bespoke offer request/response process periodically such that further bespoke offer data sets are periodically defined for presentation responsive to changes in location data associated with the customer client device.