AU783243B2 - Labelling system and method - Google Patents

Description

0 5-DEC-2001 16:59 A J PARK 64 4 472 3358 P.03/32 Regulation 3.2

AUSTRALIA

PATENTS ACT, 1990 COMPLETE

SPECIFICATION

FOR A STANDARD

PATENT

ORIGINAL

Name of AVISUAL MARKETING (NZ) LIMITED Name of Applicant: Brent Andrew McGrath and Stephen James Cane Actual Inventors: Address for service A J PARK, Level 11, 60 Marcus Clarke Street, in Australia: ,.ra ACT 2601 Labelling System and Method Invention Title: The following staterMnt is a full description of this invention, including the best method of performing it known to mCe/U 21-Jkl+-2004 12:25 A J PARK 64 4 472 3358 P.03/0? 2 LALBELLING SYSTM ANID METHOD FIELD OF MNVNT1ION 5 The invention relates to a labelling system and method, particularly but not solely designed for labelling retail items. The invention is particularly suitable for pricing. and marketing in additdon to labelling.

BACKGROUND TO INVENTION It is common to display produce and other items for sale in a self-service environment for example a supemaurket or other retail premises. Produce is generally displayed in one or mnore bins or open-top containers. Positioned near the product container is generally a display board or label identifying the product for sale and the price of that product.

It would be particularly advantageous to provide a system for generating and displaying such* *product labels in a timely and cost effective manner. It would also be pariularly advantageous to display other irformation on the product label, for example a description of the product, suggestions for use of the product, and any health benefits of using the product.

SUMMARY OFTIVEION In broad terms in one form the invention comprises a labelling system comprising a product information database in which is stored product infoirmation representing one or more retail products available for sale from a retail premises; a product retrieval component configured to retrieve product data representing a product from, the product information database; a product imnages database in which is stored electronic images associated with one or more products in the product information database; an image retrieval component configured to retrieve image data representing the retrieved product from the product images database; and a product label generator configured to produce a physical label from the retrieved product information and the retrieved image, data. the physical label arranged for display near the retail product(s) in the retail premises, COMS ID No: SMBI-00580201 Received by IP Australia: Time 11:14 Date 2004-01-21 21-JAN--%,--_V04 12:25 A J PARK 64 4 4?2 3358 P.084/07 3 In another form in broad terms the invention comprises a method of producing a physical label arranged for display near retail product(s) in a retail premises comprising the steps of retrieving product information representing a retail product from a product information database; retrieving product image data from a product images database; and producing the physical label from the retrieved product information and the retrieved product image data- BRIEF DESCRIPTION OF THE FIGURES Preferred forms of the product labelling system and method will now* be described with reference to the accompanying figures in which: Figure 1 shows a block diagram of a system in which pne form of the invention may be implemented; 15 Figure 2 shows an example product information database; Figure 3 shows a sample pricing daiabase; Figur 4 shows a sample product image database; Figure 5 illustrates an example product barcodes database; Figure 6 shows the preferred system architecture of hardware on which the present invention may be implemented; Figure 7 shows a flowchart of one preferred method of the invention; Figure 8 shows an example product label generator used to generate a label; Figure 9 shows the label generator used to generate a price; Figure 10 illustrates a user defined label design; Figure 11 shows a user defined price label; and Figures 12, 13 and 14 show example labels generated in accordance with the invention.

COMS ID No: SMBI-00580201 Received by IP Australia: Time 11:14 Date 2004-01-21 05-DEC-2001 17:00 A J PARK 64 4 472 3358 P.06/32 4 DETAILED DESCRIPTION OF PREFERRED

FORMS

Figure I illustrates a block diagram of the preferred system 10 in which one form Of the present invention may be implemented. The system 10 could include a personal computer or s workstation 20 operating under the control of appropriate operating and application software having a data memory 22 interfaced to a server or data processor 24.

The workstation 20 is preferably connected to a suitable network or networks 30. It is envisaged that network 30 could includes a local area network Or LAIN, a wide area network io or WAN, an Internet, Intranet, wireless access network, telecomnjfications network or any combination of the foregoing.

The system 10 further includes one or more clients indicated generally at 40, for example 40B and 40C. Each client workstation 40 is preferably operated by a retail Organisation 0 1. in the business of selling products to consumers, for example a supermarket. The Organisation could operate in any area in which goods or services are provided to a customer.

A client workstation could also be operated by a wholesaling or distribution organisation in the business of supplying goods and/or services to a retail Organisation.

'0 0 2o The system 10 fur-ther includes a product database indicated at 50. The product database has :stored in it product data representing one or more products or items, preferably those items sold by an Organisation operating a client workstation 40 in the course of its business. The product database 50 is preferably implemented as a relational database having a series of 0. unique product identifiers as primary keys for the product database, Each record in the 0.00 25 database is preferably identified by a unique item identifier, and includes data such as product name and other product information which is further described below.

Each record in the product database 50 could further includes a text description of the product or item. This text description could include for example suggestions on use of the item.

Where the item is a food item, the suggestions could include preferred methods of using the item in cooking. It is envisaged that the text description could further include health benefits of using the items, hazards and warnings for using the item, and the nutritional value of the item.

05-DEC-2001 1?:01 A J PARK 64 4 4?2 3358 P.O?/32 Figure 2 shows one example of product information database. The database could include a line entry for each retail item, Each line entry could include a product identifier 52 and an item name 54. Each line entry could also include fuirther product information indicated at 56 which could further include one or more product information fields. These fields could include a consumer information field 56A, tips for selecting a product at 56B, tips for storing a retail item 56C, arid tips for preparing a retail item at 56D.

The product information database could also include user defined fields shown at 58. Such user defined fields could include price lookup data (PLU data) 58A and pricing data 58B for l0 example a value identifying scale number, or price by weight of the item.

Each record of the product database 50 in one form could include both an image of the item and a text description of the item. It is also envisaged that images of the item could be stored in a separate database to a text description of each item. It is also envisaged that the product database could be installed on a memory connected to the network 30, could be installed on the workstation 20, or could be installed on one or more of the clients It is envisaged that the text description of each item for example fields 54 and 56 includes character strings and may further includes formatting codes and commands for presenting the 20 character strings. It is also envisaged that the text description could be in English where the :intended purchasers of the items are mostly English speaking. Where some or all of the customers do not speak English, the text description could be stored in a language other than English more appropriate for that organisation.

.0 25 Alternatively, the formatting code and comnmands could be stored in a master file which is loaded by the system. This master file could specify, for example, the style and size and character sets of the text used in the system.

The system 10 further includes a pricing database 60. The pricing database is preferably implemented as a relational database having a series of records. Each record is preferably identified by a unique product identifier, preferably the same unique product identifier as the product identifier used in the product database 50. Each record of the pricing database preferably includes the sale price of an individual item. It is envisaged that each record could also include different pricing structures, for example prices which exclude GST, prices which b5-DEC-2001 1?:01 A J PARK 64 4 4?2 3358 P.08/32 6 include GST, and prices which include a product discount. It is envisaged that the Pricing data in the pricing database could be stored in any appropriate currency.

Figure 3 illustrates a sample pricing database 60. The database could include a line entry for each retail item. Each line entry could have, for example, a product identifier 62 and a regular price 64 for the product. The database could also include further price entries indicated at 66 which could include special or "sale" prices. The database could also include a unit entry indicated at 68 Storing information on whether the retail item is sold individually, in a packet or by weight.

Referring to Figure 1, the system 10 could further include a product image database Figure 4 illustrates one example of a product image database. The product image database could include, for example a line entry for each product or item having a product identifier 72 and a product image 74. The product image 74 could includes a graphical representation of the item, for example an electronic image in JPEG file interchange format, BITMAP

(BMP)

format, graphics interchange format (OlE) or TIFF.

As shown in Figure 1, the system 10 may also include a product barcodes database Referring to Figure 5 the product barcodes database could include a series of line entries.

0 Each line entry could include, for example a product item identifier 82 and a barcode identifier 84. At point of sale, a barcode reader could read the barcode of an item which is then cross-checked in the product barcodes database 80 to an item identifier. The item identifier could then be used to retrieve further data on the product, for example the price from the pricing database Referring to Figure 1, the system 10 may also include a label designs database 90 which is used to store a series of pre-defined product, price and combination product/price labels, together with user defined labels. These label designs are further described below.

It is envisaged that the product information database 50, pricing database 60, product images database 70, product barcodes database 80 and label designs database 90 could be combined into a single database storing both product data and pricing data. In one form of the invention, each of the databases 50, 60, 70, 80 and 90 could be remotely updateable. A user on a client 40 could initiate transfer of data from the workstation 20 over the network(s) 30 to 05-DEC-2001 1?:01 A J PARK 64 4 472 3358 P.09/32 7 update one or more of the databases. This remote updating could be provided, for example, on a website, enabling a user to download such information easily. in another form, data could be transmitted as it is altered on the workstation 20 over the networks 30 to the product databases. Each of the update files could include a time anid date of update. In one version, the client 40 on running the application would automatically interrogate the data stored on workstation 20 to ensure that the latest data has been transferred to the databases 50, 60, and/or In a further form of the invention, the user could define, edit and manage the database or databases 50, 60, 70, 80 and/or 90 and send updated information to the workstation One advantage of separating at least product information, pricing data and images is that data which is updated more frequently, for example pricing data, can be updated independently of the product information and the product images. Furthermore, separating the product is information database from the other components of the system enables information specific to a particular country or region to be displayed as a label. One example could be countries which require labelling for genetically modified items.

As will be described below, the invention provides a method and system of producing a product label for an organisation based on data stored in the product information database the pricing database 60, the product images database 70 and/or the product barcodes database 80, and/or the label designs database Figure 6 illustrates one preferred system architecture of the workstation 20 and/or client 25 The computer system 100 typically includes a central processor 102, a main memory 104 for ~.example RAM and an input/output controller 106. The computer system 100 also includes peripherals such as a keyboard 108, a pointing device 1 10 for example a mouse, trackball or touch pad, a display or screen device 112, a mass storage memory 114, for example a hard disk, floppy disk or optical disc, and an output device 116 for example a printer. The computer system 100 could fur-ther include wireless data transmission apparatus (not shown), a network interface card or controller 118 and/or a modemn 120. The individual components of the system 100 could commuinicate through a system bus 122. Alternatively, the various components of the computer system 100 could be distributed from each other and interfaced through the network 05-DEC-2001 17:02 Al J PAlRK 64 4 472 3358 P.10/32 8 Figure 7 illustrates a preferred form method 200 of the invention- As indicated at 202, product information associated with an item is retrieved from the product database 50. As described above, this product database could be stored on workstation 20 and accessed over the network 30, could be stored on a fturther memory interfaced to the network 30 or could be installed on a client workstation The product image is then retrieved from the product images database 70 as shown at 204.

Preferably, the product identifier from the product information database is used to index the ID product image.

As shown at 206, once the item information and item image are retrieved from the item information database and the item images database respectively, a sample ticket is created from this information. The preferred form ticket includes an electronic label design into which the information retrieved from the above databases is inserted. Where necessary, the text to be inserted in a particular field in the label design could be adjusted in terms of height ~:and width for example, so that product display names such as "Yams" and "Californian seedless grapes" appear proportional and visually appropriate in the label. Similarly the size S of an image could be adjusted to fit a particular image field in the label design.

As indicated at 208, the product information is printed on a suitable device, for example a printer 116. The printer could includes a suitable colour inkjet or laser printer.

It is envisaged that further product data could be retrieved as described below.

As shown at 210, pricing data relating to the product retrieved at step 202 is retrieved from the pricing database. Once again, the retrieval could be performed over the network 30 from the server 20 or a separate memory in which the pricing database 60 is stored. Alternatively, where the pricing data is installed on the client 40, the pricing data is simply retrieved from the hard drive of the client workstation 40. As shown at 212, the pricing data is printed on a printer, for example printer 116.

05-DEC-2001 17:02 A J PRRK 64 4 472 3358 P.11/32 9 As shown at 214, the ticket or label is assembled by mounting the printed product and image information on a mounting board and then overlaying the physical printed pricing data onto the product information.

s In another preferred form, the product information and the pricing data could be arranged in an electronic form, for example by using a pointing device 1 10 and viewing a screen display 112 and the combination of product information and pricing data printed on printer 116 and mounted on a display board.

The invention also provides a convenient user interface to enable a user to create a product label and retrieve product images, product information and product prices from the appropriate databases. The user interface provides access to one or more label designs stored in the label designs database 90. Examples of these label designs are described with reference to Figures 8 to 11. Referring to Figure 8, a user interface in the form of a label generator 300 includes a data entry and retrieval panel 3 10 and a label preview panel 320. The data entry/retrieval panel 3 10 includes a plurality of fields which are further described below.

One of these fields is a label design field 330 enabling a user to select a dropdown list of predefined label designs accessible fromn the label database 90. The label design field 330 preferably includes a label retrieval component configured to retrieve the available label designs from the label design database and to list these label designs in a dropdown list in the field 3 A product field 340 enables a User to select a particular product from among a list of alternatives. The product field 340 could include product retrieval component configured to retrieve product names from the product database and to make these product names available to a user in a dropdown list in the product field 340.

The label generator 300 could also include product information field 360 which uses the product retrieval component to retrieve product information from the product database 50 and to populate field 360 with this information. Field 360 preferably shows the product information available to a user and field 370 shows the information selected by the user from field 360 to be displayed on the label.

05-DEC-2001 17:03 A J PARK 64 4 472 3358 P.12/32 As the user is retrieving or entering data in the panel 3 10, panel 3 20 is preferably populated with this data in pre-selected regions. These regions could include, for example, a product name region 380, a product image region 390 and a product information region 400.

The product label generator 300 could then produce a physical label by printing the contents of preview panel 320.

Figure 9 illustrates the generation of a pricing ticket, where a user wishes to generate a pricing ticket separate from a product label. The user first selects a label design in the label design field 330, for example a price design. The user then enters a price in the price field 410 or alternatively a plurality of available prices could be retrieved from the pricing database using a pricing retrieval component. Weightsuts field 420 preferably includes a data retrieval component configured to retrieve from the pricing database 60 a list of alternatives for weights/units, for example price per kilogram, price per 50 grams, or price per weight bag, for example.

The user may then enter further text in the auxiliary text field 430 and could also include data the scale number field 440, for example that there is a limit on the number of products available for sale to a particular consumer.

As panel 310 is populated with data, the corresponding data in the resulting price label preferably appears in panel 320. The price label could include a series of regions, for example, a price region 450, a weights/units region 460, an auxiliary text region 470, and a scale number 480.

**:The product label generator 300 could then produce a physical label representing the price of a product by printing the contents of preview panel 320.

The invention may also provide for a user a label designer which is described with reference to Figures 10 and I1I. The label designer enables a user to create a new design, or alter an existing one and store the new or altered design in the label designs database *05-DEC-2001 17:03 A~ J PAlRK 64 4 472 3358 P.13/32 Figure 10 illustrateS one example of the user defined label design 500 which could include a logo region 5 10, an image data region 520, a product name region 530, a data text region 540, product information text region 550, a further logo 560 and backgrounld colour 570.

Figure I I illustrates at 600 an example of a user defined price label. The price label could include a price dollars region 610, a price cents region 620, a price unit name 630, a static field showing currency 640, an auxiliary text field 650 and a scale number field 660. The price label could also include a background colour 670.

i0 The invention provides a convenient method for generating product labels and prices.

Examples of these product labels are shown in Figures 12, Figure 13 and Figure 14. It will be appreciated that the product labels are merely a few of the plethora of product labels able to be generated by a user.

The invention provides a product labelling system and method in which product labels can be *easily generated. Changes in product descriptions and product pricing can also be easily implemented by updating product database 50 and/or pricing database 60. The databases could be accessible over a network 30 for updates and/or access by one or more of the clients or by any other third party. Alternatively, the databases could be installed on a client workstation 40 with regular updates, for example on CD Rom, provided to the organisation associated with the client workstation The foregoing describes the invention including preferred forms thereof. Alterations and modifications as will be obvious to those skilled in the art are intended to be incorporated within the scope hereof as defined by the accompanying claims.

Claims (1)

1. 21-JR+-2004 12*26 A J PARK 64 4 472 3358 P.05/0? 12 CLAIMS: 1. A labelling system comprising: a product information database in which is stored product information representing s one or more retail products available for sale from a retail premises; a product retrieval component configured to retrieve product data representing a product from the product information database; a product images database in which is stored electronic images associated with one or more products in the product information dataibase; an image retrieval component configured to retrieve image data representing the retrieved product from the product images database; and a product label generator configured to produce a physical label from the retrieved product information and the retrieved image data, the physical label arranged for display near the retail product(s) in the retail premises. 2. A labelling system as claimed in claim, 1 further comprising: a pricing database in which is stored pricing data associated with one or more products inteproduct information database; and a pricing retrieval component configured to retrieve pricing data representing the retrieved product from the pricing memory; wherein the product label generator is configured to produce the physical label additionally representing the price of the product 3. A labelling system as claimed in any one of the preceding claims futher comprising: a label designs database in which is stored oneor more label designs; and a label retrieval component configured to retrieve a label design from the label designs database; wherein :the product label generator is configured to produce the physical* label from the retrieved label design. 4. A method of producing a physical label arranged for display near retail product(s) in a retail Premises comprising the steps of: retrieving Product informaltion representing a retail product from a product information database; COMS ID No: SMBI-00580201 Received by IP Australia: Time 11:14 Date 2004-01-21 21-JR4-2804 12:26 A J PARK 64 4 472 3358 P.086,0? 13 retrieving product image data from a product images database; and producing the physical label from the retrieved product information and the retrieved product image data. 5. A method of producing a label as claimed in claim 4 further comprising the steps of: retrieving pricing data representing the retail product from a pricing database; and producing the physical label additionally from the retrieved pricing data. 6. A method of producing a label as claimed in claim 4 or claim 5 further comprising the steps of: retrieving a label design from a label designs database; and producing the physical label from the retrieved label design. 7. A labelling system, substantially as herein described with reference to the 15 accompanying drawings. LO 8. A method of producing a physical label arranged for display near retail product(s) in a 9 retail premises, substantially as herein described with reference to the accompanying drawings. coo*o S..N. e a 0fro •3140• COMS ID No: SMBI-00580201 Received by IP Australia: Time 11:14 Date 2004-01-21