AU2018101042A4 - Method, system, and device for recording loyalty data - Google Patents

Abstract

A method for recording loyalty data, comprising the steps of: * maintaining a database on an account server; * receiving a bag ID from a loyalty terminal in data communication with the account server, the bag ID obtained from reading an ID token of a bag and uniquely associated with the bag; * receiving bag loyalty data from the loyalty terminal, the bag loyalty data corresponding to a transaction associated with the reading of the ID token; and * storing, within the database, the bag loyalty data in association with the bag ID. 62 <60

Description

Field of the Invention

The invention generally relates to the provision of a loyalty system for customers.

Background to the Invention

Loyalty programs are known where a customer is enabled to actively sign up to the program and receive as a result a membership ID (for example, provided as a personalised card or smartphone app). The loyalty program is designed to encourage repeat custom by rewarding the customer. Often rewards are based on a total shopping value of a customer at the provider of the program.

Recently, there has been a move to replace single-use shopping bags (such as those provided by supermarkets) with multiple use bags—often at a price to the customer. These multiple use bags are designed to be brought back on future shopping trips to be used again to carry bought items.

It is common for particular retailers to brand the multiple use bags, such that, for example, the name of the retailer is present on the bag. However, a problem exists in that customers may bring multiple use bags branded with a competitor’s branding to a store, thereby diminishing the brand value of the retailer.

Summary of the Invention

According to an aspect of the present invention, there is provided a method for recording loyalty data, comprising the steps of: maintaining a database on an account server; receiving a bag ID from a loyalty terminal in data communication with the account server, the bag ID obtained from reading an ID token of a bag and uniquely associated with the bag; receiving bag loyalty data from the loyalty

10507018_1 (GHMatters) P109252.AU.1

2018101042 27 Jul 2018 terminal, the bag loyalty data corresponding to a transaction associated with the reading of the ID token; and storing, within the database, the bag loyalty data in association with the bag ID.

The method may further include the step of producing a plurality of bags, each bag comprising a readable ID token, wherein each ID token uniquely identifies its associated bag, wherein the received bag ID is obtained from one of the plurality of bags. The ID token may be a barcode or other printed code.

The method may further comprise the step of: reading, from the bag comprising the unique ID token, a bag ID recorded within the ID token using a 10 reader of the loyalty terminal. Optionally, the method further comprises the step of: the loyalty terminal obtaining transaction data relating to the transaction associated with the reading of the ID token. The loyalty terminal may obtain the transaction data via data communication with a POS terminal. Alternatively, the loyalty terminal may obtain the transaction data via receiving an input at a user 15 interface of the loyalty terminal. Optionally, the method further comprises the step of: determining the bag loyalty data from the transaction data.

According to another aspect of the present invention, there is provided a method for recording loyalty data, comprising the steps of: maintaining a database on an account server; receiving a plurality of bag IDs from a loyalty terminal in 20 data communication with the account server, the bag IDs obtained from reading ID tokens of an associated plurality of bags, each ID token uniquely associated with one of the plurality of bags; receiving bag loyalty data from the loyalty terminal, the bag loyalty data corresponding to a transaction associated with the reading of the ID token; selecting a bag ID of the plurality of bag IDs as a primary 25 bag ID; and storing, within the database, the bag loyalty data in association with the primary bag ID.

The primary bag ID may be selected as the first bag ID read by the loyalty terminal. The account server may be configured to determine whether one or more of the bag IDs is already stored within the database, and upon determining that 30 one bag ID is stored in the database, selecting that bag ID as the primary bag ID.

10507018_1 (GHMatters) P109252.AU.1

2018101042 27 Jul 2018

The account server may be configured to determine whether one or more of the bag IDs is already stored within the database, and upon determining that two or more bag IDs are stored in the database, selecting one of these bag IDs as the primary bag ID. The primary bag ID may be selected as the first bag ID of the bag 5 IDs stored in the database read by the loyalty terminal.

According to another aspect of the present invention, there is provided a method of associating a bag ID stored in a database of an account server with a customer ID stored in a customer database, comprising the steps of: maintaining the database on the account server; receiving a bag ID from a loyalty terminal in 1 o data communication with the account server, the bag ID obtained from reading an

ID token of a bag and uniquely associated with the bag; receiving bag loyalty data from the loyalty terminal, the bag loyalty data corresponding to a transaction associated with the reading of the ID token; storing, within the database, the bag loyalty data in association with the bag ID; maintaining the customer database 15 comprising customer IDs and associated customer loyalty data; receiving a command from a user device instructing the account server to associate the received bag ID with a particular customer ID, and recording an association between the received bag ID and the particular customer ID.

The method may further comprise the steps of: receiving a command from a 20 user device instructing the account server to associate a second bag ID with a particular customer ID, the second bag ID being stored in the database, and recording an association between the second bag ID and the particular customer ID.

The bag loyalty data associated with the bag ID may be recorded at 25 customer loyalty data associated with the customer ID.

According to another aspect of the present invention, there is provided a loyalty rewards system comprising: a plurality of bags, each bag having a unique ID token comprising a readable bag ID; a plurality of loyalty terminals, each comprising an ID reader configured for reading the ID tokens of the bags and 30 obtaining the associated bag ID; an account server in data communication with the

10507018_1 (GHMatters) P109252.AU.1

2018101042 27 Jul 2018 loyalty terminals, the account server configured to: maintain a database on an account server; receive a bag ID from a loyalty terminal in data communication with the account server, the bag ID obtained from reading an ID token of a bag and uniquely associated with the bag; receive bag loyalty data from the loyalty 5 terminal, the bag loyalty data corresponding to a transaction associated with the reading of the ID token; and store, within the database, the bag loyalty data in association with the bag ID.

According to another aspect of the present invention, there is provided an account server comprising a processor interfaced with a memory and a network 10 interface, the account server configured to maintain a database within the memory, and further configured to: receive a bag ID from a loyalty terminal in data communication with the account server, the bag ID obtained from reading an ID token of a bag and uniquely associated with the bag; receive bag loyalty data from the loyalty terminal, the bag loyalty data corresponding to a transaction 15 associated with the reading of the ID token; and store, within the database, the bag loyalty data in association with the bag ID.

Also disclosed herein is a bag comprising a ID token configured to be utilised in the methods according to the aspects described above. Also disclosed are a plurality of such bags, each having a unique ID token.

As used herein, the word “comprise” or variations such as “comprises” or “comprising” is used in an inclusive sense, i.e. to specify the presence of the stated features but not to preclude the presence or addition of further features in various embodiments of the invention.

10507018_1 (GHMatters) P109252.AU.1

2018101042 27 Jul 2018

Brief Description of the Drawings

In order that the invention may be more clearly understood, embodiments will now be described, by way of example, with reference to the accompanying drawing, in which:

Figures la and lb show exemplary incentivisation systems according to different embodiments;

Figure 2 shows a bag according to an embodiment;

Figure 3 show a loyalty terminal according to an embodiment;

Figure 4 shows an account server according to an embodiment;

Figure 5 shows a method for storing bag loyalty points with the account server;

Figure 6 shows a system including a user terminal;

Figure 7 shows a method comprising recording loyalty data against a customer ID; and

Figure 8 shows a method of determining a bag ID and/or customer ID against which to record loyalty data.

Description of Embodiments

Figures la and lb show exemplary incentivisation systems 10, according to different embodiments. Both systems 10 include a first loyalty terminal 13a 20 separate to and interfaced with a point-of-sale (POS) terminal 15a, a second loyalty terminal 13b integrated into a POS terminal 15b (i.e. loyalty terminal 13b is the same device as POS terminal 15b and is typically implemented within the same hardware), and a third loyalty terminal 13c that is not interfaced with a POS terminal 15. The different loyalty terminals 13 are to illustrate examples of 25 different possible configurations of the system 10 (although, a particular implementation of the system 10 can comprises two or more different configurations of loyalty terminal 13).

10507018_1 (GHMatters) P109252.AU.1

2018101042 27 Jul 2018

According to the embodiment of Figure la, each loyalty terminal 13 is in data communication with a loyalty module 16 via the network 14. The loyalty module 16 is then itself in communication with an account server 12. The loyalty module 16 can be implemented within the hardware of the account server 12 or 5 can be provided within physically distinct hardware.

According to the embodiment of Figure lb, each loyalty terminal 13 includes a loyalty module 16a-16c implemented as a module of the loyalty terminal 13. The loyalty modules 16 are each in communication with an account server 12. In a general sense, a loyalty module 16 is configured to facilitate 10 communication between the account server 12 and one or more of the loyalty terminals 13.

Referring to Figure 2, a bag 20 is shown (for example, a shopping bag). The bag 20 is typically provided as suitable for multiple subsequent uses—for example, being made of a sufficiently robust material. The bag 20 may be made of 15 a plastic, paper, or any other suitable material. It is also envisaged that the bag 20 may be substituted for another container, such as a cardboard box. The bag 20 includes branding 21, which is typically displayed on outside surface 22 (on either or both sides of the bag 20). The branding 21 may be confined to a region (as shown), although this is not required. The branding 21 will typically include 20 visual features associated with the retailer providing the bag 20. Thus, a customer can readily identify the retailer associated with the bag 20.

The bag 20 further comprises an ID token 23. In the embodiment shown, the ID token 23 comprises a printed code 24 (for example, a barcode or QR-code) that contains an identifying value associated with the bag 20. The printed code can be 25 located on the outside surface 22, offering ease of access, or inside surface 23, offering protection against inadvertent reading, depending on the implementation. The printed code should be suitable for uniquely identifying the bag 20.

In another embodiment, the ID token 23 utilises an RFID technology. For example, the ID token 23 corresponds to an RFID tag configured to communicate 30 the associated identifying value to a suitably configured RFID reader. Several

10507018_1 (GHMatters) P109252.AU.1

2018101042 27 Jul 2018 other embodiments are envisaged, including those utilising Bluetooth Low Energy technology.

Referring back to Figures la and lb, each loyalty terminal 13 includes an ID reader 11 for obtaining a bag ID of a bag 20 by reading the ID token 23 present on 5 the bag 20. For example, the ID reader 11 comprises a barcode scanner when the ID token 23 is a barcode or a RFID reader when the ID token 23 is a RFID tag. Generally, the ID reader 11 comprises known data reading technology.

Figure 3 shows a schematic representation of the first loyalty terminal 13a, according to an embodiment. The first loyalty terminal 13a is implemented within 10 a device having computer functionality; that is, the first loyalty terminal 13a comprises a processor 50 interfaced with a memory 51 and an input/output (I/O) port 52. The memory 51 comprises programming instructions for causing the processor to implement the functionality described herein, as well as a working memory space—typically the memory 51 comprises both volatile and non-volatile 15 memories. The first loyalty terminal 13a can also comprise a user interface 53.

The user interface 53 can comprise input means 54 and output means 55. Input means 54 may include any of a touchscreen, button(s), or other known inputs. Output means 55 may include any of a display, LED indicators, audible outputs, or other known outputs. The I/O port 52 is in data communication with the POS 20 terminal 15a and is configured to receive at least a portion of the transaction data (see description below) generate by the POS terminal 15a via the data communication. The I/O port 52 is also interfaced with the ID reader 11, which is typically found as a component of the first loyalty terminal 13a. In a variation, the ID reader 11 can be found as a component of the first POS terminal 15a and the 25 bag ID is communicated to the first loyalty terminal 13a via the I/O port 52.

Typically, the processor 50 is also interfaced with a network interface 57.

The second loyalty terminal 13b is implemented within the second POS terminal 15b (not shown). The second POS terminal 15b comprises computer functionality similar to that of the first loyalty terminal 13 a. In effect, the second 30 POS terminal 15b includes programming enabling it to implement the

10507018_1 (GHMatters) P109252.AU.1 functionality of the second loyalty terminal 13b. The POS terminal 15b therefore comprises the ID reader 11.

The third loyalty terminal 13c comprises similar features and functionality to the first loyalty terminal 13a, however, is not interfaced with a POS terminal 15. Instead, transaction data is received via a user input via the user interface 53 (e.g. by the user entering a total transaction value).

In a general sense, the loyalty terminal 13 according to the embodiments herein described is configured to receive transaction data related to a transaction, and to communicate with the account server 12 via the loyalty module 16.

Figure 4 shows a schematic representation of the account server 12. The account server 12 is typically located off-site to the loyalty terminals 13 (although this is not required) and can be implemented in a number of forms depending on the embodiment. Generally, the account server 12 comprises one or more processors 60 interfaced with a memory 61 (typically comprising both volatile and non-volatile memories). The memory 61 comprises instructions to cause the processor to implement the functionality herein described. The account server 12 comprises a network interface 62, which is configured to receive data from the loyalty terminals 13. The account server 12 can be implemented as a standalone computer or an interconnected plurality of computers (e.g. a server farm), which can be implemented as a cloud server.

The account server 12 is configured to maintain a database 30 (for example, with the memory 61) comprising bag IDs (or a data value derived from the bag IDs) in association with bag loyalty data. The bag loyalty data associated with each bag ID is unique to that bag ID—therefore, an individual bag 20 is associated with both its own bag ID and its own bag loyalty data. The account server 12 can, on receiving a bag ID, undertake standard data manipulations of the associated bag loyalty data (e.g. add information, remove information, and modify information). For simplicity of the following disclosure, reference is made to “bag loyalty points” as being synonymous with bag loyalty data—although the bag loyalty data can take any required form.

10507018_1 (GHMatters) P109252.AU.1

2018101042 27 Jul 2018

It should be clear that the loyalty terminals 13 and the account server 12 can be implemented in any suitable hardware. In particular, such hardware may include additional components not herein described.

Figure 5 shows a method of storing bag loyalty points within the account server 12 in association with a bag ID, according to an embodiment. A bag 20 includes, as previously described, an ID token 23 which can be read from the bag 20 by the ID reader 11 associated with a loyalty terminal 13, thereby obtaining the bag ID associated with the bag 20. The bag 20 is provided for sale (or even provided free of charge) to the customer. For example, the customer may ask for 10 the bag 20 or may pick up the bag 20 themselves (for example, in a self-service checkout implementation). The bag 20 is used associated with a particular transaction, where the transaction includes one or more products being purchased by the customer from the merchant. The transaction can include or exclude the purchase of the bag 10, depending on the implementation. Generally, the 15 transaction will produce transaction data (e.g. total value of the transaction and/or value of each item of the transaction).

The bag 20 is placed in a position such that the ID reader 11 can read the bag ID from the ID token 23. The ID reader 11 then reads the bag ID, at ID read step 100, and provides the bag ID to its associated loyalty terminal 13. The bag ID 20 is communicated to the account server 12 from the loyalty terminal 13, at bag ID communication step 101. It is understood that the bag ID may be modified before communicating to the account server 12 such that a derived value is communicated to the account server 12.

The loyalty terminal 13 also obtains transaction data relating to the 25 transaction, at transaction step 102. The transaction data comprises information in relation to the purchase(s) made by the customer from the merchant during the transaction. The transaction data can comprise data in one or more categories, depending on the implementation. For example, the transaction data can comprise a total transaction value indicating the total payment made to the merchant by the 30 customer. In another example, the transaction data can comprise item values

10507018_1 (GHMatters) P109252.AU.1

2018101042 27 Jul 2018 indicating the value of each individual item in a transaction. Typically, in this case, the transaction data will also comprise item names indicating the particular item for each item value. In an embodiment, the loyalty terminal 13 receives directly bag loyalty points as transaction data. However, for the purposes of this 5 disclosure, it is assumed that that bag loyalty points are not directly received by the loyalty terminal 13.

In an embodiment, for example which may be applicable to the arrangement of the first and/or second loyalty terminal 13a, 13b, the loyalty terminal 13a, 13b receives the transaction data directly from the POS terminal 15 via a data o communication. In another embodiment, for example which may be applicable to the arrangement of the third loyalty terminal 13c, the transaction data is input into the loyalty terminal 13c via a user interface 53. For example, the merchant may input the total purchase amount.

The loyalty terminal 13 then provide the transaction data to its connected 15 loyalty module 16, which is configured to determine the bag loyalty points for the transaction based on the received transaction data. The bag loyalty points may simply correspond to the total cost of the transaction, although, usually a conversion is applied. For example, bag loyalty points can be expressed in arbitrary units separate from the monetary value of the transaction. In an o embodiment, the bag loyalty points are proportional to the total transaction value and/or individual item transaction values. Generally, the bag loyalty points can be produced according to known loyalty schemes. Individual transactions and/or individual purchases may accrue bag loyalty points at different rates—for example, to satisfy marketing promotions.

The bag loyalty points are communicated from the loyalty module 16 to the account server 12 at transaction communication step 103. The bag loyalty points and bag ID are communicated to the account server 12 in a manner such that the bag ID is associated with the bag loyalty points; typically, the bag loyalty points and bag ID are communicated within the same communication. The account 30 server 12 is then configured to record a database entry in the database 30 such that

10507018_1 (GHMatters) P109252.AU.1

2018101042 27 Jul 2018 the bag loyalty points is recorded in association with the bag ID, at loyalty recording step 104.

In an embodiment, loyalty recording step 104 comprises the account server 12 determining whether a database entry exists associated with the received bag 5 ID. If the account server 12 determines that no database entry exists, one is created, and the loyalty data stored. If the account server 12 determines that a database entry does exist, then the loyalty data is stored against this existing entry. Advantageously, from the perspective of the customer, there is no step of actively joining the loyalty program associated with the merchant. Instead, a loyalty 10 account is effectively automatically created on the first use of the bag 20.

Referring to Figure 6, the system 10 of Figure 1 is shown with a user terminal 40 in data communication with the account server 12, according to an exemplary embodiment. Generally, the system 10 may comprise any number of user terminals 40. Generally, each terminal 40 is configured to interact with the 15 account server 12 to enable the relevant users to manage the database entries.

In an embodiment, user terminal 40 is a computing device (for example, a personal desktop or laptop computer, or a smartphone) configured for network communication with the Internet. The user terminal 40 is enabled to allow certain management actions of the database 30 to be made by the customer via this 2 o communication.

According to the embodiment of Figure 6, the account server 12 is further adapted to maintain a customer loyalty database 41. In a variation to the embodiment, not shown, the customer loyalty database 41 is maintained by a separate server which is interfaced with (for example, via a network connection) 25 the account server 12. The customer loyalty database 41 can be a component of the loyalty database 30 or can be logically distinct. Generally, the customer loyalty database 41 comprises customer loyalty associated with customers (herein, including “customer loyalty points”)—this is in contrast to bag loyalty data associated with individual bags 20. Thus, each entry in the customer loyalty 30 database 41 is associated a customer ID (which may be, for example, a customer

10507018_1 (GHMatters) P109252.AU.1

2018101042 27 Jul 2018 number). The customer ID can be associated with customer information, which can take many different forms (e.g. name, age, location, etc.). Each customer ID is also associated with customer loyalty points indicating a total number of accrued loyalty points by the customer. In an example, the customer ID is the same as, or 5 derived from, a bag ID (e.g. of the first bag 20 used by the customer).

In an embodiment, the customer is enabled to associate an obtained bag 20 with their customer ID. In this way, their customer loyalty points can be associated (in effect) with the bag loyalty points of the bag 20. The customer utilises a user terminal 40 to provide an instruction to the account server 12 to 10 associate their customer ID with the particular bag ID of the bag 10. For example, the customer may be prompted to enter the barcode number (where applicable) printed onto the bag 20, to enter their customer ID (or login information such as a username and password that is associated with their customer ID), and to accept an authorisation to combine the two. The account server 12 then updates a cross15 reference entry to indicate that the bag ID is associated with the customer ID.

Then, depending on the embodiment, bag loyalty points associated with the bag ID is transferred to the customer loyalty database 41 as customer loyalty points and recorded in an entry associated with the customer ID.

Figure 7 shows a modification to the method of Figure 5, according to an 20 embodiment. The account server 12 receives the bag ID and bag loyalty points as already described. The account server 12 is configured to check whether there is a customer ID associated with the received bag ID at customer check step 200. In the event that such an association exists, the bag loyalty points (or a derivation thereof) are automatically (that is, without further customer intervention) recorded 25 against the customer ID as customer loyalty points, at step 201. In this case, step 104 can be considered optional. In the event that such an association does not exist, the method proceeds to step 104 as already described.

In an embodiment, when two or more bags 20 are utilised in a single transaction, the loyalty data is added to the database entry for each bag 20. In 30 another embodiment, when two or more bags 20 are utilised in a single

10507018_1 (GHMatters) P109252.AU.1

2018101042 27 Jul 2018 transaction, the loyalty data is divided evenly between the bags 20. For example, where the loyalty data comprises a numerical value, that value is divided into equal portions and each portion is associated with one of the bag IDs (the system 10 may be configured to address any need for rounding).

In another embodiment, one bag 20 of the two or more bags 20 is elected as the primary bag 20—it is against the bag ID of this bag 20 that the bag loyalty points are applied. For example, the first bag 20 scanned by the ID reader 11 is selected as the primary bag 20. The remaining bag(s) 20 do not have the bag loyalty points associated with their bag IDs.

Figure 8 shows a modification to the method of Figure 7, according to an embodiment, where two or more bags 20 are utilised during a single transaction. Step 100 and 101 are modified such that each bag ID is scanned (at step 300) and communicated to the account server 12 (at step 301). The account server 12 is then configured to check (at step 302) whether any of the bag IDs are associated 15 with a customer ID.

If no bag ID is associated with a customer ID, the method proceeds to bag ID selection step 303. At this step, one of the bag IDs is elected for recording the bag loyalty points, and these are associated with the bag ID in the database 30.

If one bag ID is associated with a customer ID, or two or more bag IDs are all associated with one customer ID, the method proceeds to record the bag loyalty points against this bag ID, at step 304. The method then optionally proceeds to associate the, or each, remaining bag ID received by the account server 12 with the customer ID, at record additional bag ID step 305.

If two or more bag IDs are determined to be associated with different customer IDs, then a selection of one customer ID to record the bag loyalty data against is made at step 306. For example, the first bag 20 scanned. Alternatively, the loyalty terminal 13 may be enabled to alert the customer that an election must be made and to receive an input from the customer identifying which customer ID should have the bag loyalty points recorded against it.

10507018_1 (GHMatters) P109252.AU.1

2018101042 27 Jul 2018

Further modifications can be made without departing from the spirit and scope of the specification.

10507018_1 (GHMatters) P109252.AU.1

2018101042 27 Jul 2018

Claims (18)

1. The claims defining the invention are as follows:

   1. A method for recording loyalty data, comprising the steps of:

   maintaining a database on an account server;

   receiving a bag ID from a loyalty terminal in data communication with the account server, the bag ID obtained from reading an ID token of a bag and uniquely associated with the bag;

   receiving bag loyalty data from the loyalty terminal, the bag loyalty data corresponding to a transaction associated with the reading of the ID token; and storing, within the database, the bag loyalty data in association with the bag ID.
2. 2. A method as claimed in claim 1, further comprising the step of:

   producing a plurality of bags, each bag comprising a readable ID token, wherein each ID token uniquely identifies its associated bag, wherein the received bag ID is obtained from one of the plurality of bags.
3. 3. A method as claimed in claim 2, wherein the ID token is a barcode or other printed code.
4. 4. A method as claimed in any one of claims 1 to 3, further comprising the step of: reading, from the bag comprising the unique ID token, a bag ID recorded within the ID token using a reader of the loyalty terminal.
5. 5. A method as claimed in claim 4, further comprising the step of:

   the loyalty terminal obtaining transaction data relating to the transaction associated with the reading of the ID token.
6. 6. A method as claimed in claim 5, wherein the loyalty terminal obtains the transaction data via data communication with a POS terminal.

   10507018_1 (GHMatters) P109252.AU.1

   2018101042 27 Jul 2018
7. 7. A method as claimed in claim 5, wherein the loyalty terminal obtains the transaction data via receiving an input at a user interface of the loyalty terminal.
8. 8. A method as claimed in any one of claims 5 to 7, further comprising the step of: determining the bag loyalty data from the transaction data.
9. 9. A method for recording loyalty data, comprising the steps of:

   maintaining a database on an account server;

   receiving a plurality of bag IDs from a loyalty terminal in data communication with the account server, the bag IDs obtained from reading ID tokens of an associated plurality of bags, each ID token uniquely associated with one of the plurality of bags;

   receiving bag loyalty data from the loyalty terminal, the bag loyalty data corresponding to a transaction associated with the reading of the ID token;

   selecting a bag ID of the plurality of bag IDs as a primary bag ID; and storing, within the database, the bag loyalty data in association with the primary bag ID.
10. 10. A method as claimed in claim 9, wherein the primary bag ID is selected as the first bag ID read by the loyalty terminal.
11. 11. A method as claimed in claim 9, wherein the account server is configured to determine whether one or more of the bag IDs is already stored within the database, and upon determining that one bag ID is stored in the database, selecting that bag ID as the primary bag ID.
12. 12. A method as claimed in claim 9 or 11, wherein the account server is configured to determine whether one or more of the bag IDs is already stored within the database, and upon determining that two or more bag IDs are stored in the database, selecting one of these bag IDs as the primary bag ID.

    10507018_1 (GHMatters) P109252.AU.1

    2018101042 27 Jul 2018
13. 13. A method as claimed in claim 12, wherein the primary bag ID is selected as the first bag ID of the bag IDs stored in the database read by the loyalty terminal.
14. 14. A method of associating a bag ID stored in a database of an account server with a customer ID stored in a customer database, comprising the steps of:

    maintaining the database on the account server;

    receiving a bag ID from a loyalty terminal in data communication with the account server, the bag ID obtained from reading an ID token of a bag and uniquely associated with the bag;

    receiving bag loyalty data from the loyalty terminal, the bag loyalty data corresponding to a transaction associated with the reading of the ID token;

    storing, within the database, the bag loyalty data in association with the bag ID;

    maintaining the customer database comprising customer IDs and associated customer loyalty data;

    receiving a command from a user device instructing the account server to associate the received bag ID with a particular customer ID, and recording an association between the received bag ID and the particular customer ID.
15. 15. A method as claimed in claim 14, further comprising the steps of:

    receiving a command from a user device instructing the account server to associate a second bag ID with a particular customer ID, the second bag ID being stored in the database, and recording an association between the second bag ID and the particular customer ID.
16. 16. A method as claimed in either one of claims 14 and 15, wherein the bag loyalty data associated with the bag ID is recorded at customer loyalty data associated with the customer ID.
17. 17. A loyalty rewards system comprising:

    a plurality of bags, each bag having a unique ID token comprising a readable

    10507018_1 (GHMatters) P109252.AU.1

    2018101042 27 Jul 2018 bag ID;

    a plurality of loyalty terminals, each comprising an ID reader configured for reading the ID tokens of the bags and obtaining the associated bag ID;

    an account server in data communication with the loyalty terminals, the account server configured to:

    maintain a database on an account server;

    receive a bag ID from a loyalty terminal in data communication with the account server, the bag ID obtained from reading an ID token of a bag and uniquely associated with the bag;

    receive bag loyalty data from the loyalty terminal, the bag loyalty data corresponding to a transaction associated with the reading of the ID token; and store, within the database, the bag loyalty data in association with the bag ID.
18. 18. An account server comprising a processor interfaced with a memory and a network interface, the account server configured to maintain a database within the memory, and further configured to:

    receive a bag ID from a loyalty terminal in data communication with the account server, the bag ID obtained from reading an ID token of a bag and uniquely associated with the bag;

    receive bag loyalty data from the loyalty terminal, the bag loyalty data corresponding to a transaction associated with the reading of the ID token; and store, within the database, the bag loyalty data in association with the bag ID.

    10507018_1 (GHMatters) P109252.AU.1

    1/9

    2018101042 27 Jul 2018

    Figure la

    2/9

    2018101042 27 Jul 2018

    Figure lb

    3/9

    2018101042 27 Jul 2018

    Figure 2

    4/9

    2018101042 27 Jul 2018

    13a ⁵³ 54

    Figure 3

    5/9

    2018101042 27 Jul 2018

    Figure 4

    6/9

    2018101042 27 Jul 2018

    Figure 5

    7/9

    2018101042 27 Jul 2018

    Figure 6

    8/9

    2018101042 27 Jul 2018

    Figure 7

    9/9

    2018101042 27 Jul 2018

    Figure 8