WO2001035186A2

WO2001035186A2 - Interactive in-store and online shopping system

Info

Publication number: WO2001035186A2
Application number: PCT/US2000/030291
Authority: WO
Inventors: Robert D. Covington; Melanie A. Al-Shabkhoun; Andrew D. Carlson; Sandeep Chugani; Drew Conrad; Paul M. D'alessandro; John E. Khalil; Jason Kunesh; Charles Brent Lohrmann; James C. Spira; John Sviokla; Darren S. Yaphe
Original assignee: Simon Property Group, L.P.
Priority date: 1999-11-05
Filing date: 2000-11-02
Publication date: 2001-05-17
Also published as: AU1458301A; WO2001035186A3; WO2001035186B1

Abstract

An interactive system and method are provided in which the shopping process is separated from the buying process. In one embodiment, the system includes an instore/in-mall computer system (12) and a plurality of handheld data entry units (20) that are configured to download their internal memories to the computer system (16). The system further includes an interactive web site (30) that is in communication with the computer system and a plurality of Electronic Retailers (24) via the INTERNET (26).

Description

Interactive In-Store/In-Mall and Online Shopping System and Method FIELD OF THE INVENTION

The present invention relates to the field of electronic shopping. More

specifically, the invention relates to a system and method that separates the shopping

process from the buying process through an electronic shopping system that is coupled through the Internet (or some other wide area network) to an online shopping and

buying web site portal.

BACKGROUND OF THE INVENTION Traditionally, most shopping and subsequent buying was done on the premises

of a physical store. Over time, shopping centers and malls were developed to bring together various types of stores, including specialty shops, in close geographical

proximity to each other. The convenience offered by malls and shopping centers has

long been appreciated by consumers for they had previously spent a great deal of time traveling from store to store.

In addition to shopping in physical locations, various companies have offered their products or services by mail order. Mail order typically works by the delivery of a product catalog to a potential customer. If the potential customer was interested in

making a purchase, they simply picked up the telephone and ordered the items seen in the catalog, or placed an order by mail. Those ordered items were then delivered to the purchaser's specified address by mail.

The availability of cable television has provided yet another method for

shopping. In addition to just the casual advertisement on the local channels, dedicated

cable networks, such as the Home Shopping Network and QVC, are available which advertise products or services. Typically, a consumer watches the television and picks up the phone to place an order for an item just "seen" on television.

Most recently, electronic commerce ("e-commerce") has had a major impact

on the "shopping experience." Specifically, an individual is now able to shop on the

Internet. Internet shopping is usually accomplished by the individual seeking out particular web sites having the types of items of interest, such as Amazon.com for books, CDnow.com for music CDs, etc., browsing that web site for particular items,

and then placing orders. However, many people do not actually place orders over the Internet, but rather return to a physical store or place a mail order for the particular products they've selected. The reluctance of consumers to place an order over the

Internet has been, in part, due to the general population's concern with the security of using credit card numbers over the Internet, the inability of the consumer to talk with a

sales representative about the product, and/or the inability of the consumer to evaluate

the item in something other than virtual reality.

There are still significant advantages to actually seeing merchandise in a physical location rather than simply viewing the item in a two-dimensional perspective as on the Internet, on television, or in a catalog. The two-dimensional view of an item does not provide information as to the item's texture, and may also be very deceptive as to the actual appearance or color, as color is very much determined by the particular settings on a computer monitor, the settings and reception of a

television, and the quality of print in a catalog.

Further, in Internet, television and mail order shopping it is difficult to bring

together many types of items in close proximity to each other. Television and catalog shoppers are limited to the specific items presented on television or in the catalog. In

the Internet world, it is not uncommon for a web site to be dedicated to a particular

manufacturer's products. While cyber-malls (virtual malls on the Internet) exist, they

are usually limited to the particular manufacturers that have signed up with the cyber- mall owner. Thus, while Internet technology presents the possibility of improved

"space" navigation through various choices that are available to the shopper, it

provides a disjointed shopping experience.

These prior art systems do not provide any linkage between the "space" and "place" aspects of shopping. In this regard, "space" refers to the navigability (or degree of availability) of information presented (e.g., over the Internet), and "place" refers to the physical location of the merchandise. Such an integration of space and

place would provide a more cohesive shopping experience.

In the past, gift registries for wedding showers and/or weddings have provided

a limited ability to separate the general shopping process from the buying process. However, these registries are usually limited to the physical place. For example, an

engaged couple may go to a particular store and select various items that they are interested in receiving as wedding gifts. Sometimes, the couple may be able to enter their information electronically, such as on a gift registry web site or through a computer-operated kiosk; however, their selections are typically limited to the particular virtual store in which they are shopping (if through a web site), or are

limited to a particular mall in which one or more merchants may be participating in the gift registry (if through an in-mall kiosk). Thus, there remains a general need in this field for a system and method of

electronic shopping that separates the shopping process from the buying process while

at the same time providing for the integration of "space" and "place," without

necessarily being bound to the merchandise available in any physical place.

SUMMARY OF THE INVENTION

An interactive system and method are provided for in-store/in-mall and online shopping in which the shopping process is separated from the buying process. The system preferably includes an in-store or in-mall computer interface and database

system(s) coupled to a plurality of handheld data entry units, and an interactive shopping web site portal in communication with the in-store or in-mall systems and a plurality of Electronic Retailers via the Internet.

Using this interactive shopping system, a user (or shopper) uses the PDA

scanner at the physical mall to shop for and select particular products that the user desires to have purchased for him/her. These selected products are then stored as a

"wish list" in a database coupled to the web site portal. Having selected products from the physical store or mall, the user thereafter logs into the web site portal using, for example, a personal computer and generates one or more "event lists," which include one or more products from the wish list. An event list includes a list of

occasions or special dates (such as birthdays, anniversaries, trips, etc.) associated with a particular user. The user may then add products to the event list (or the wish list)

from a variety of Electronic Retailers.

The user then selects an access mechanism for allowing buyers access to

selected wish lists and/or event lists. Such mechanisms include providing password protection, providing an access control list (ACL), making one or more of the wish

lists and/or event lists public, or making one or more of the wish lists and/or event

lists private. The user then transmits an e-mail with access information to one or more

buyers in order to inform them of the existence of the wish lists and/or a particular

event list(s). The buyers can then access the system web site home page where the appropriate list(s) may be displayed. From this web page, the buyer may: (1) print out the list(s) and go to the physical store where the products are located to make a purchase, (2) purchase one or more of the products on-line and have them delivered,

(3) purchase one or more of the products on-line and pick-up the products at a physical store, or (4) notify an in-store/in-mall concierge service to go to a physical store, buy the products on behalf of the buyer, and ship the products to the buyer or to the user.

The present invention provides a shopping system in which the shopping

process, i.e., the act of browsing a store (either physical or e-commerce) and selecting a particular product or set of products, is separated from the buying process, i.e.,

purchasing a particular product that has been previously selected through the shopping process. Moreover, the present invention provides a shopping system in which the shopping process is not necessarily constrained by any physical place, or, indeed, any particular vendor of products. According to another aspect of the invention, a system and method are

provided for integrating the space and place in an interactive shopping system, as

previously described. To accomplish this objective, this aspect of the present invention includes a central computer system for retaining product and related data from a myriad of retailers, such as all the retailers situated in a particular physical mall

or shopping center. Ancillary to the computer are handheld data entry units, such as

barcode scanners, PDA's (e.g., Palm Pilots™), or any other portable data entry unit,

that can communicate with the computer system by means known in the art (such as

direct link, network, infrared, RF, or other communication means). These handheld devices are used by a shopper for entry of desired items as is described herein. The

central computer may be connected to the Internet and/or to an interactive kiosk located in a store or mall.

As to the method of this aspect of the present invention, a shopper can survey the "place," i.e., the physical store which has contributed information to the central

computer, and then make selections of desired items. Those items would be stored,

for example, in the handheld device and then sent, for example, directly from the handheld device to the central computer, from the handheld device to an interactive

kiosk to the central computer, from the handheld device to the central computer via

the Internet, or from the handheld device to the central computer via any such similar communication means. After the user completes selecting all the desired items, the user is given the ability to identify which individuals should receive information about certain items selected by the user via, e.g., an "event list". By so doing, the user will have created a list of desired items from participating retailers and granted access to specific individuals (buyers) for certain selected items of interest to the user. This

method results in a unique cross-channel cross-retail interactive shopping experience.

Also, the list of desired items that the user creates by this method is no longer limited to the particular type of event (such as a wedding) as is true in the prior art. Thus, the system has the effect of creating a cross-event shopping experience in addition to one

that is cross-channel and cross-retail.

Those who have been given access to the product purchase information by the

user can retrieve the product information via, for example, the Internet. These buyers

can then purchase any of these products based on this retrieved information. Such

purchases could be transacted over the Internet, by mail order, by shopping directly at the store where the user selected the item, or by a store similar to where the user

selected the item (such as a chain store in a different geographical location). The buyer may wish to shop at a physical store to ascertain features or characteristics of a selected item, such as, for example, the color, size, or texture, which are not

discernable via electronic or printed media.

As will be appreciated, the invention is capable of other and different

embodiments than those discussed above and described in more detail below, and its

several details are capable of modifications in various respects, all without departing from the spirit of the invention. Accordingly, the drawings and description of the embodiments set forth below are to be regarded as illustrative in nature and not

restrictive.

BRIEF DESCRIPTION OF THE DRAWINGS The present invention satisfies the general need noted above and provides m∑tj y advantages, as will become apparent from the following description when read

in conjunction with the accompanying drawings, wherein:

FIG. 1 is a diagram of an in-store/in-mall and online interactive shopping

system according to a preferred embodiment of the present invention. FIG. 2 is a flow chart showing how a user (or shopper) interacts with the

system shown in FIG. 1.

FIG. 3 is a flow chart showing one embodiment of how a buyer interacts with

the system shown in FIG. 1.

FIG. 4 illustrates the components of one embodiment of the present invention.

FIG. 5 illustrates how a wish list creator (user) and/or a wish list buyer interact

with components of the system of FIG. 1.

FIG. 6 illustrates how an aggregated shopper interacts with components of the

system of FIG. 1. FIGs. 7a-b are detailed flow charts illustrating how a user registers and

accesses the system of FIG. 1.

FIG. 8 is a detailed flow chart illustrating how the system allows a user to

access system functions that require registration.

FIG. 9 is a detailed flow chart illustrating how the user searches for products

and creates and/or modifies a wish list.

FIG. 10 is a detailed flow chart illustrating how the user modifies a general wish list contains all the items selected while shopping online.

FIG. 11 is a detailed flow chart illustrating how the user adds items to a

shopping cart database. FIG. 12 is a detailed flow chart illustrating how the user modifies a wish list.

FIG. 13 is a detailed flow chart illustrating how the user creates a specific wish

list. FIGs. 14a-b are detailed flow charts illustrating how the system allows the user

to transfer items from a wish list to a shopping cart for purchase.

FIG. 15 is a detailed flow chart illustrating how the system allows the user to

transfer items from a general wish list to a specific wish list.

FIG. 16 is a detailed flow chart illustrating how the system allows the user to delete items from a wish list.

FIG. 17 is a detailed flow chart illustrating how the user selects a certain

number of items from his/her wish list to be added to the user's shopping cart.

FIGs. 18a-b are detailed flow charts illustrating how the user selects items to purchase online and how the user reviews his/her shopping cart online.

FIGs. 19a-b are detailed flow charts illustrating how the user adds an item to a wish list from an e-tailer web site.

FIGs. 20a-b are detailed flow charts illustrating how a buyer buys an item from an e-tailer web site.

FIG. 21a is a detailed flow chart illustrating the system shopping cart checkout module.

FIG. 21b-c are detailed flow charts illustrating how the system fulfills an order.

FIGs. 22a-b are detailed flow charts illustrating how the user creates an access

mechanism that allows specified buyers to be notified about, and have access to, one or more of the user's wish lists.

FIGs. 23a-b are detailed flow charts illustrating how the user adds a buyer to his/her access mechanism. FIGs. 24a-b are detailed flow charts illustrating how the buyer views a wish

list at a store/mall or online.

FIG. 25 is a detailed flow chart illustrating how the user, aggregated shopper

and/or buyer interact with components of the system of FIG. 1.

FIGs. 26a-b are detailed flow charts illustrating how the buyer at an in¬

store/in-mall kiosk interacts with the system of FIG. 1.

FIG. 27a is a detailed flow chart illustrating how the buyer purchases items on

a wish list at a store or mall.

FIG. 27b is a detailed flow chart illustrating how the kiosk agent synchronizes the data in the PDA with retailer data from an external database.

FIG. 28 is detailed flow chart illustrating how the kiosk agent identifies an in¬

store/in-mall user to the system.

FIGs. 29a-b are detailed flow charts illustrating how the user adds items to a

wish list at a physical store or mall. FIGs. 30a-b are detailed flow charts illustrating how the system handles errors

when an item is scanned.

FIGs. 31a-b are detailed flow charts illustrating how the kiosk agent synchronizes the new PDA data with existing data on an external database.

FIGs. 32a-b are detailed flow charts illustrating how the user can add, delete

and/or buy items on a wish list at a physical store or mall.

FIG. 32c is a detailed flow chart illustrating how the user can purchase items

in his/her electronic shopping cart while at a physical store or mall. DETAILED DESCRIPTION OF THE INVENTION

Turning now to the drawings, FIG. 1 is a diagram of an in-store/in-mall and

online interactive shopping system 10 according to one embodiment of the present

invention. This system 10 includes Electronic Shopping Systems 14 located within a

plurality of physical stores or malls 12. Located within each mall are a plurality of physical stores 22 (Store A - Store Z). These stores (all or some of them) may be

active participants in the interactive shopping system 10, although not necessarily to the same degree. The system also includes an Interactive Internet Shopping Web Site Portal 30, a plurality of Electronic Retailer Web Sites 24, and a plurality of user and

buyer personal computers (PCs) 28, 32. All of these various systems 14, 30, 24, 28 and 32 are coupled together via a wide-area communications network 26, such as the Internet. Note, however, that network 26 could also be a cable TV network, a satellite

network, a wireless data network, or any other type of communications network.

In the Internet embodiment, the communication network 26 is defined by the

TCP/IP protocol. The various connections between the in-store/in-mall systems 14, the Interactive Internet Portal 30, the Electronic Retailer Web Sites 24, and the user and buyer PCs via the Internet may be any type of connection, such as a circuit- switched telephone line connection (using a data modem), a T-l or T-3 dedicated telephone connection, a fiber-optic line, an xDSL connection, a CATV modem connection, a wireless connection, a satellite link connection, or any other type of

connection that is capable of transporting data.

The in-store/in-mall systems 14 preferably include a computer interface system 18, which could be a PC, a workstation, or any other type of computer system, a local database 16 coupled to the computer interface system 18, which could be integral to

the computer interface system 18, or could be separate and apart from it, or could be

coupled to the computer interface system 18 via a network. The computer interface

system 18 is coupled to a plurality of PDA scanners 20 which, for example, are in communication with the computer interface system 18 through an interface cradle that

holds the PDA 20, and provides an electrical data connection between the PDA 20 and the computer interface system 18 so that data from the PDA 20 can be uploaded to or downloaded from the computer interface system 18 (as used herein, PDA's that

connect to the interface system 18 via an interface cradle are considered "batch processing" PDA's). Alternatively, the PDA scanners 20 may be coupled to the computer interface system 18 via a wireless data connection that allows data to be

uploaded or download periodically or continuously without having to be physically

connected to an interface device.

The Interactive Internet Shopping Web Site Portal 30 includes, in one embodiment, a web server 34 (which hosts one or more web sites comprising a

plurality of web pages coded using standard languages and protocols, such as HTML, XML, Java, JavaScript, ActiveX, SHTML, etc.), an underlying electronic commerce shopping operating system (SOS) 36, a credit card authorization module 40, an order fulfillment module 42, and a central database 38. As used herein, the term "database" refers to any collection of data organized especially for rapid search and retrieval, whether that data reside on one or more physical storage devices (e.g., a distributed

database system), or whether the data is accessed via an index, a directory, a table, etc.

Therefore, although different names are given to some of the databases herein, this is for ease of understanding and should not limit the appended claims. The web server

34 preferably hosts the web site 30 which allows a user to store and generate "wish

lists" of products selected either through the in-store/in-mall systems 14 and/or from

the Electronic Retailers 24, and create various "events" that include one or more products from the wish lists. The web site 30 also provides a buyer interface for

enabling purchase of products associated with a particular event. In one embodiment, the web site 30 is referred to and accessed using the domain name "fastfrog.com." In

addition to the electronic shopping and purchasing features noted herein, the web site 30 may also include many other functional attributes that are particular to the target audience, e.g., adults, teenagers.

As described in more detail below, users (or shoppers) of the system 10 enter

login information 44A to register with the system 10. After the user has selected one

or more products though the in-store/in-mall systems 14 and/or through the Electronic

Retailers 24, a wish list 44B of products is created and stored in the central database 38. The wish list 44B contains all of the products (either located in the physical stores

22 or at the Electronic Retailers 24) that the user has shopped for and selected so that

someone else (e.g., a buyer) can purchase one or more of those selected products as a gift (or for any other reason) for the user. Having generated a wish list 44B, the user

can then use the web site 30 to create one or more "events" including one or more "event lists." An event is an occasion, special date, or other categorization associated with the particular user that includes one or more of the items on that user's wish list.

For example, a user may have 30-40 products listed on his/her wish list, and

may have several "events" up-coming, such as a ski trip, Christmas and a birthday. Using the event feature of the present invention, the user can create a "Ski Trip

Event", a "Birthday Event", and a "Christmas Event", and then select certain of the

items from the wish list 44B for one or more "event lists" 44C that are linked to one

of the created events. So, for example, the user may select a new jacket and pair of

skis to add to the Ski Trip Event, and may select a digital camera and a tripod to add

to the Birthday Event. In this manner, users can create a series of "events" in their life and then associate certain wish list items with those events.

For each event, users also select an access mechanism such as, for example, an access control list ("ACL") that only allows members of the ACL to access selected event list(s), password protection which only grants buyers having the required

password access to specified event list(s), public access which allows any interested

buyer to access selected event list(s), or private access which only allows the creator- user to access selected event list(s). Although the access control list (ACL)

embodiment is illustrated herein, any access mechanism that allows one or more

buyers access to a scan list, wish list, and/or event list is within the scope of the claimed invention. In FIG. 1, ACL 44D includes a list of authorized buyers that may gain access to the product information associated with a particular event.

FIG. 2 is a flow chart showing one embodiment of the invention depicting how the user (or shopper) interacts with the system 10 shown in FIG. 1. The system first proceeds from block 50 to block 52 where the user registers with the system 10 either

at one of the in-store/in-mall systems 14, or through the Interactive Internet Shopping

Web Site Portal 30. The registration process requests identifying information about the user, including, for example, his/her home address, telephone number and e-mail address, and asks the user to select a username and password that will uniquely

identify the user to the system 10. Other registration information may also be

collected from the user. If the user registers at a particular in-store/in-mall system 14,

then this registration information will be stored in the local database 16 associated

with that particular in-store/in-mall system 14, and will thereafter be replicated to the

central database 38 associated with the web site portal 30.

In block 54, the user goes to a physical store or mall 12 and checks-out a PDA scanner 20. Using the scanner 20 (block 56), the user may then browse through one or

more of the participating physical stores 22, and select certain products to add to his/her wish list by, for example, scanning a UPC barcode located on the particular product. Alternatively, the user (or a store clerk) may enter information about a

desired product manually into the PDA scanner 20. Other means of data input may

also be employed to get identification information on a particular product into the

scanner 20. The user may then continue to visit stores 22 and scan (or enter data regarding) products into the scanner 20. In this manner, users can "shop" for certain products that they want a buyer to purchase for them, but the users do not actually purchase any of the products, although, of course, there is nothing in the system design of the present invention that would prevent the users from purchasing any of the products on their wish list.

Having selected (or shopped) for particular products at the various stores 22, the user, in block 58, returns the scanner 20 to the in-store/in-mall system 14. In one

embodiment, the scanner 20 is placed into a cradle that physically holds the scanner

and puts the scanner 20 to communicate with the computer interface system 18. Alternatively, the scanner 20 may be in continuous (or periodic) communication with the computer interface system 18 through a wireless data connection. Regardless of

the method of communication, when the scanner 20 is coupled to the computer

interface system 18, the system 18 sends a command to the scanner 20 to download

product information to the local database 16. Here, the product information is saved as a "wish list" of items that this particular user wants a buyer(s) to purchase for

him/her. Periodically, in block 60, the wish list information in the local database 16 is replicated to the central database 38 associated with the web site portal 30.

After block 60, the user can leave the store or mall 12 and later return to this store or mall (or some other store or mall) and continue to select products and add

them to his/her wish list by returning to block 54, or the user can proceed to block 62 to begin the event generation process.

The user, in block 62, has left the physical store or mall 12, and is now most

likely at his/her home (or somewhere with access to the Internet) where he/she has a PC 28, which is coupled to the Internet by, for example, a dial-up modem connection

through an Internet Service Provider, a cable-modem connection over a local cable TV system, etc. The user, operating standard web-browser software such as

Microsoft's Internet Explorer or Netscape's Communicator, then connects to the Internet by establishing a TCP/IP connection and navigates the web browser to the Interactive Internet Shopping Web Site Portal 30 by entering the Uniform Resource

Locator ("URL") of the web site associated with the web site portal 30. As previously indicated, in one embodiment the URL for a web site associated with teenage users is

"www.fastfrog.com," although, of course, any other URL could be used. This particular URL is only listed herein because some of the Figures refer to the "fastfrog"

web site.

At the web site portal 30, the user is prompted to enter his/her login

information (username/password), and if there is a match to the entered login

information stored in the central database 38, then the user can gain access to any wish

list 44B, event list 44C and ACL 44D information associated with this particular user. Having entered the proper login information (block 62), the user may: (1) create an event list (block 64); (2) view/edit a wish list (block 74); (3) view/edit events (block

80); and (4) create a buyer account (block 88). Note that these are only four of the basic functions provided by the system, and many other functions and features of the web site portal 30, not specifically described with reference to FIG. 2, are evident

from the other Figures which describe in more detail the full capabilities of the system

10, as described below.

In block 64, the user can create an event and a corresponding event list. In

block 66, the user selects a name for an even, such as "Birthday", "Ski Trip",

"Christmas" or any other event name that the user desires. Then, in block 68, the user selects one or more products that he/she previously added to his/her wish list through, for example, the PDA scanner 20 and the in-store/in-mall system 14, and/or from the plurality of Electronic Retailers 24, and adds the selected product(s) to the event list. In block 70, the user can add additional items from the Electronic Retailers 24.

Finally, in block 72, the user selects an access mechanism for the particular event,

which identifies which buyers, if any, are permitted access to the particular event list. In one embodiment, the access mechanism is an ACL that includes buyers who are

authorized to access the particular event.

In block 74, the user can view and/or edit his/her stored wish list. The user

can delete an item from the wish list (block 76), or add an item to the wish list from

an Electronic Retailer 24 (block 78).

In block 80, the user can view and/or edit the events the user created. The user can delete a certain event from the system (block 82), the user can select a particular event and edit items, in block 84, on the event list (by, for example, deleting items, providing or changing a description of an item or certain particulars regarding an item), or the user may edit the ACL (by, for example, deleting certain buyers from the

ACL, or adding a new buyer) for a particular event (block 86).

In block 88, the user can create buyer accounts. Buyer accounts are needed so

that certain buyers (which are given access to various events via an access mechanism) can gain access to the Interactive Internet Shopping Web Site Portal 30

so that they can then access a particular event list. In block 90, the user enters identifying information regarding the new buyer, such as the buyer's name, e-mail address, and password. This information is then used to generate an e-mail message that is electronically transmitted to the buyer (block 92) to inform him her that he/she has been designated as a potential buyer for a specified user. The message also describes how the buyer can gain access to the particular event list for which the user

has designated the buyer. In one embodiment, the e-mail may contain an embedded

HTTP hot-link (hyperlink) that, when selected by the buyer, will navigate the buyer's web browser directly to the web page where the particular event list is displayed. The web page will then request the buyer's password information in order to allow the

buyer access to the particular event list. From this point, the system proceeds to FIG.

3.

FIG. 3 is a flow chart showing one embodiment of how a buyer interacts with the system 10 shown in FIG. 1. In block 100, the buyer receives an e-mail with an

embedded hyperlink, as described with reference to block 92. The buyer activates the

hyperlink (block 102) which links the buyer's web browser to the shopping portal web site 30. Specifically, the hyperlink will direct the buyer's web browser to the web page where the particular event list is located. In one embodiment, the user's ACL grants the buyer access to the event list. In another embodiment, the user's event list is password protected and the e-mail to the buyer includes this password so that the

buyer can access the event list. For example, the user may have created a "Birthday"

event, and granted his/her brother access to the user's Birthday event list. The brother

is then sent an e-mail informing him that his sibling has created a wish list for an upcoming birthday, and directing the brother to the appropriate web page in order to view the wish list.

In block 104, the buyer may browse the event list of products, and select a particular product for purchase. In block 106, the buyer, depending on the product, may be able to immediately purchase the product online, in which case, in block 108,

the wish list will be automatically updated to reflect that a particular product has been purchased. Online purchasing (block 106) can be done using many well-known

methods of carrying out e-commerce transactions through secure web pages and

protocols. Alternatively, in block 110, the buyer can select to buy the product through an

in-store/in-mall concierge service (e.g., yoursherpa.com). This service may be

available for certain products that can only be purchased at the physical stores 22, and

not online, and is useful where the buyer does not want to actually visit a physical

store or mall 12. In block 112, the buyer updates the wish list.

Alternatively, in block 114, the buyer may simply view a list of the items on the event list (e.g., by displaying the list on a PDA or printing out a copy of the list), and then go to a physical store or mall where the buyer would shop in a conventional

manner. In the event that the buyer elects to go to a physical store to buy a product on the event list, then, in block 116, a means is provided for the buyer to return to the event list web page and indicate that a particular product on the event list has been

purchased. Thus, the buyer can update the current status of the event list. At the end

of each of these alternatives, the buyer can loop back to block 102 where the buyer is linked to the shopping web site portal 30 so that the buyer can view another event list

or quit.

The following Figures represent various flow charts that are carried out using the system of the present invention. These flow charts illustrate: (1) how the instore/in-mall and online shopper (user) interacts with the system (FIGs. 5-24); and (2) how the user uses the PDA scanner 20 in a physical store or mall 12 (FIGs. 25-32). In one embodiment, the interactive shopping system 10 includes two

components (1) an online wish list component, and (2) an in-store/in-mall PDA

shopping component, as illustrated in FIG. 4. These components will be described in

detail below. With respect to the online wish list component, FIGs. 5-24 show detailed flow

charts illustrating one embodiment of how the in-store/in-mall and online shopper

(user) interacts with the shopping system 10 shown in FIG. 1. FIG. 5 shows one

embodiment illustrating how a wish list creator 120 (a user who creates a wish list)

and/or a wish list buyer 140 interact with the web site portal 30 (identified in this

embodiment as fastfrog.com) in order to, for example, add a wish list item to an electronic shopping cart (block 122); create a wish list (block 124); modify a wish list (block 126); remove purchased items from a wish list (block 128); move the list of

scanned items to a wish list (block 130); and obtain online help (block 132). Similarly, the wish list creator (user) 120 and/or the wish list buyer 140 interact with a prosumer 152 (a platform where common functionalities of various applications, such

as the user's wish list and personal profile, reside) in order to, for example, access the

prosumer 152. The prosumer 152 may comprise a remote server that allows the user and/or buyer to: register with the web site provider to gain access to the system (block

134); add an item to a list of scanned items (block 136); maintain an electronic shopping cart (block 138); chat in an online forum such as a teen forum (block 142); create and maintain an ACL (block 144); checkout by purchasing items in the shopping cart or exiting the web site (block 146); maintain the list of scanned items (block 148); and move the list of scanned items to a shopping cart (block 150). In addition, a customer service representative (CSR) 154 is available to educate the wish

list user/creator or wish list buyer about the shopping system and its functionality

(block 156). FIG. 6 shows an aggregated shopper 160 that interacts with the prosumer 152 in order to assist a user or buyer to, for example, register with the web site provider

(e.g., fastfrog.com) to gain access to the system web site (block 134); add an item to a

list of scanned items (block 136); maintain an electronic shopping cart (block 138);

check-out by purchasing items in the shopping cart or exiting the web site (block

146); maintain a list of scanned items (block 148); and move one or more of the scanned items to the shopping cart (block 150). In one embodiment, the aggregated

shopper 160 represents a store or mall kiosk agent that, in addition to helping the user or buyer perform the above tasks, supervises the kiosk, authorizes user's to check out PDA's, and synchronizes the data in the PDA's with the data residing in the local database 16. In another embodiment, the aggregated shopper 160 is also known as

YourSherpa which is a concierge service that buys selected items for a user from

physical stores. The CSR 154 is available to educate the aggregated shopper 160

about the shopping system and its functionality (block 156). A user (not shown) can interact with a web site 158 (identified in this

embodiment as yoursherpa.com) in order to, for example, create a buy list; modify a buy list; remove purchased items from a buy list; add a buy list item to an electronic shopping cart; and purchase items through an in-store/in-mall concierge service (block

151) (e.g., YourSherpa). FIGs. 7a-b illustrate a flow chart showing in more detail block 134 of FIG. 5, the acquisition (registration and access) procedure. In the illustrated embodiment, a

user (e.g., a teen) wishes to sign up and participate in the wish list web site 30, as

shown in block 162. The user enters the wish list web site 30 by entering an appropriate URL on the user's web browser, as shown in block 164. The URL may be, for example, wishlist.com, fastfrog.com, yoursherpa.com, or alphatribe.com.

Then, the user browses the web site without completing the registration process (block

166). If the user accesses functionality requiring registration (block 168), then the

user is required to register by entering the requested information in the registration

fields provided (block 170). The user enters the information requested, which depends on the registration level required by the user to proceed. For example, a Level 1 Registration, as shown in block 172, requires the user to enter: a login name,

e-mail address, password, first and last name, city, state, and a password hint (in case the user forgets his/her password). In this embodiment, Level 1 Registration is required to build a wish list and/or to participate in a chat room.

In this embodiment, as shown in block 174, Level 2 Registration requires the

user to provide, in addition to the Level 1 information, a mailing address, including

zip code and street address, and a phone number. In the illustrated embodiment, Level 2 Registration is required to notify others of a wish list created by the user. If a user wants to check-out a scanner 20 at a store or mall to build a wish list, the user must provide Level 2 Registration information in addition to credit card information including, for example, a credit card number, expiration date, and credit card billing

address. In this embodiment, Level 3 Registration requires the user to provide, in

addition to the Level 1 and 2 information, the name of a credit card owner (if different

than the user's name), a credit card number, expiration date, and credit card billing address (block 178). In one embodiment, Level 3 Registration is required to buy items on a wish list. In this embodiment, Level 4 Registration requires the user to

provide, in addition to the Level 1-3 information, the name of a parent, the parent's

name as it appears on a credit card, a credit card number, and credit card billing

address (if different than mailing address entered at Level 2) (block 180). In one

embodiment, Level 4 Registration is required to provide collateral to check out a PDA

scanner 20. In addition, as shown in block 182, the user's credit card, drivers license or photo identification is taken by a kiosk agent in the store or mall before allowing the PDA scanner 20 to be checked-out. This collateral is, for example, photocopied and immediately returned to the user or returned when the user returns the scanner 20.

In block 188 of FIG. 7b, the system issues the user a wish list account and password. The user is then granted access to specified modules or functionality

corresponding to the user's registration level (block 190). The user can, for example, search for products and create and/or modify a wish list and/or an access control list

(ACL) (or any other access mechanism listing authorized buyers), as shown in block 192; view existing wish lists, block 194. From blocks 192 or 194, the user proceeds

to block 196, described below with reference to FIG. 9.

In FIG. 8, the system allows the user to access functions that require registration, such as accessing a wish list and/or using a concierge service (e.g. , YourSherpa), as shown in block 202. If the user has not registered with the system and desires to access or perform functions that require registration, the user is linked to the prosumer registration screen (block 204). In one embodiment, the system then

displays a list of registration benefits and provides links to various disclaimers (block

208). In block 210, the system displays a registration screen that allows the user to input registration information. The system then determines whether the customer

entered valid information in all the required fields, as shown in block 212. If not, the

system lists the field(s) that need to be completed (block 214). Otherwise, the system

proceeds to block 216 where the user may obtain a higher registration level by

entering more information.

In block 218, the system determines whether the user wants to register at a higher level. If not, the system proceeds to block 222. Otherwise, the system proceeds to block 220 where the system determines whether the user entered valid information in all the additional input fields. If all the fields do not contain valid information, the system proceeds to block 226 where the system lists the fields that

were incorrectly completed. Otherwise, the system proceeds to block 224 where the

user is provided a higher registration level depending on how much additional information the user provided. In block 222, the system determines whether the user

has a credit card with a credit limit greater than the cost of a PDA. If the user has

such a card, the user is thereafter authorized to check out a PDA at a participating store or mall (block 240). Otherwise, in block 228, the user is informed of the benefits of registering online for a PDA.

Next, the system determines whether the user wishes to register for a PDA (block 230). If not, the user is provided with a user name and password and is sent back to the main web page (block 234). Otherwise, in block 232, the user is prompted to provide a credit card for collateral. The system then determines whether the credit

card is in the name of the user (block 236). If so, the user is thereafter authorized to

check out a PDA (block 240). Otherwise, the user enters a valid credit card number, the name of the card holder (e.g., the parent's name), and an e-mail address (block

242). In block 244, the system verifies that the credit card belongs to the card holder

by, for example, verifying that the registration address entered by the user matches the

mailing address for the credit card. If it does, the user is thereafter authorized to check

out a PDA (block 240).

In FIG. 9, the system proceeds from block 196 to block 246 where the system determines whether the user wants to search for products (browse), or create and/or modify his/her wish list (create/modify). To create and/or modify a wish list, the system proceeds to block 282 (described below with reference to FIG. 12).

Otherwise, the user can browse products from a list of retailers or perform a Boolean key word search (block 248). To do the former, the user browses through categories of products provided by registered retailers and/or e-tailers (such as Abercrombie &

Fitch, Camelot Music, etoys, etc.) (block 250). Then, the system advises the user that

he/she may select items from either retailers or e-tailers (block 252). The system then

determines whether the user wants to shop at e-tailers or retailers (block 254). To shop e-tailers, the system proceeds to block 256 (described below with reference to FIGs. 19a-b). Otherwise, the system proceeds to block 258.

If the user chose (in block 248) to perform a Boolean key word search to find a

particular item, the system proceeds to block 274 where the customer is prompted to enter search criteria (in Boolean search form) such as the name of a particular product,

manufacturer, product category, retailer, etc. The system then searches database 410 which contains product data. The search results are then returned to the user. The

results include a list of products that match the search criteria specified by the user (block 278). The user can then select the desired item(s) from the search results

(block 280).

In block 258, the system allows the user to view the selected item(s) by

displaying the attributes of the selected item(s) such as the store where the item(s) can

be purchased, the name of the product, a description of the product, the size, if necessary, the price, a picture or illustration of the product, the available colors, if

appropriate, etc. Next, the system determines whether the user selects one or more of the items being viewed (block 260) by, for example, clicking on the item(s). If no items are selected, the system proceeds to block 264. Otherwise, the system adds the selected item(s) to the user's wish list (block 262). Then, the system determines in

block 266 (via, for example, a display prompt) whether the user desires to move the selected item from the user's general wish list (scan list) to a specific wish list (event

list), such as the user's birthday or Christmas wish list (event list). If the user does not

move the selected item to a specific wish list, the system proceeds to block 264. Otherwise, in block 268, the item is removed from the general wish list (scan list).

Then, the user selects a pre-existing wish list (event list) and adds the selected item to that specific wish list (block 270). The system then determines whether the user

selects the next item being viewed (block 260). In block 264, the system determines whether the user wants to add more items to his/her general wish list. If not, the

system proceeds to block 272 (described below with reference to FIG. 10).

Otherwise, the system returns to block 246.

In FIG. 10, the system proceeds from block 272 to block 284 where the user

reviews his/her general wish list (scan list) which contains all the items selected while browsing the retailers and e-tailers online. All these items are displayed (block 286)

whether the items are only on the general wish list (scan list) or whether one or more

items were copied to a specific wish list (event list). The system retrieves these items

from database 410 and displays product information for each item such as, for

example, the product name, store name, product ID code, size, color, price, etc. In block 290, the system allows the user to make the following choices regarding the

items on the scan list: add an item to a specific wish list (event list) (block 292), delete an item (block 298), or add an item to a shopping cart for purchase (block 304). If the user decides to add an item to a specific wish list, the system will prompt the user, in block 294, to select the wish list(s) to which the item should be added. In block 296, the system adds the item to the specific wish list(s) indicated by the user,

which are resident on the wish list database 302. If the user decides to delete an item,

the system deletes the item from the scan list (general wish list), in block 300, which

is resident on the wish list database 302. If the user decides to add one or more items (or all the items on the scan list) to the shopping cart, the system determines whether the item(s) were selected from an e-tailer (block 306). If not, the system proceeds to block 308. Otherwise, the system launches a window displaying the web page of the

e-tailer where the user can purchase the item(s) (block 310).

Referring to FIG. 11, the system proceeds from block 308 to block 312 where the system copies the selected items to database 410 which contains shopping cart data. The system then determines whether the user wishes to remove one or more of

these items from the scan list (block 316). If so, the system transfers the data

corresponding to those items to the user's personal archive (block 318). Otherwise, the system does not change the scan list (block 322). The system then proceeds to

block 320, where the system includes the selected items in the user's shopping cart. In

block 324, the user is prompted to enter the quantity of each item to be purchased.

The system then proceeds to block 272 (described above with reference to FIG. 10).

In FIG. 12, the system proceeds from block 282 to block 326 where the system

prompts the user to determine whether the user wants to modify or create a specific wish list (event list). To create a wish list, the system proceeds to block 354 (described below with reference to FIG. 13). Otherwise, the system proceeds to block 328 where the system displays a list of all existing wish lists, named by event, e.g.,

birthday, Christmas, summer vacation. In block 330, the system determines whether the user wants to delete an item(s) from a wish list. If so, the user selects an item(s)

from one of the wish lists and deletes it (block 332). Otherwise, the system determines whether the user wants to rename a wish list (block 334). If so, the user

re-enters a name for a selected wish list (block 336). Otherwise, the system determines whether the user wants to change the date of a wish list (i.e. , change the

date of an event) (block 338). For example, the user could change the date of his/her summer vacation wish list if the date of the vacation changed.

If the date needs to be changed, the system allows the user to re-enter the date of the wish list (block 340). Otherwise, in block 342, the system determines whether the user wants to change the layout of the wish list by, for example, placing more desired items on the top of a wish list. If such a change is desired, the system allows

the user to select the new layout for the items in a particular wish list (block 344).

Otherwise, the system determines, in block 346, whether the user wants to change the list of authorized buyers for a particular wish list. If so, the system proceeds to block

348 (described below with reference to FIG. 22a). Otherwise, the system determines,

in block 350, whether the user wants to select another wish list to modify. If so, the

system returns to bock 326. Otherwise, the system proceeds to block 352 where the system sends the user to the wish list home page (described below with reference to

FIGs. 14a-b).

Referring to FIG. 13, if the user chose to create a specific wish list, the system

proceeds from block 354 to block 356 where the system allows the user to name an event by, for example, using a pull-down menu or entering a name into a field. In block 358, the user inputs the date associated with the particular wish list. However, if pull-down menus are used, the date field will be completed (block 360) and the

system proceeds to block 362. There, the user is prompted to add members to the list

of authorized buyers for this wish list (block 362). If the user desires to add members to the list of authorized buyers, the system proceeds to block 364 (described below

with reference to FIG. 22a). Otherwise, the user can proceed to add items to this wish list by browsing retailers and/or e-tailers (block 366).

In FIGs. 14a-b, the system allows the user to transfer items from a wish list to an electronic shopping cart for purchase (block 368). In one embodiment, the user selects a wish list tab which reveals the wish list home page (block 370). In block 372, the user selects one of his/her existing wish lists which may, for example, be

presented in alphabetical order according to the names of the wish lists. In block 374,

the system presents the user with a list of items in the selected wish list. Next, the user can select one or more items listed in the wish list (block 376).

The system then determines whether the customer wants to move an item(s) to a

shopping cart (block 378) residing on database 410. If so, the user is prompted, in

block 380, to enter the quantity of the desired item to add to the shopping cart. In one

embodiment, the default quantity is set to one. As indicated in block 382, the system will not remove the item(s) from the wish list or decrease the number of items indicated on the wish list until a certain event has happened such as, for example, the system confirming that the item(s) have been packed. The system then adds the desired number of item(s) to the user's electronic shopping cart (block 383). The system then returns to block 374.

If the customer (in block 378) does not desire to move an item to a shopping

cart, the system determines whether the user wants to move an item(s) to one or more different wish lists (block 384). If not, the system returns to block 374; otherwise, the

system proceeds to block 386 where the user is presented with a list of existing wish list(s), excluding the current wish list. The system then allows the user to select one of these wish list(s) (block 388). Next, the user is prompted to enter the number of

items to be added to each selected wish list (block 390). The item(s) are then copied, in block 392, to the other wish list(s). The system then returns to block 374.

In FIG. 15, the system allows the user to transfer items from a scan list (i.e., a general wish list) to a specific wish list (event list) (block 394). In one embodiment, the user goes online and selects the scan list option which brings the user to the scan

list web page (block 396). The user is then presented with a list of the items on the

user's scan list (block 398). Next, the user selects one or more of the items from the scan list (block 400). The system, in block 402, determines whether the user wants to

move the selected item(s) to a shopping cart. If so, the user is prompted, in block 404,

to enter the quantity of each item to be added to the shopping cart. As indicated in

block 408, the system then removes those item(s) from the scan list. Next, the system

adds the desired number of item(s) to the user's shopping cart (i.e., to database 410)

(block 405). The system then returns to block 396. If the user indicated, in block 402, that he/she did not want to move the selected item(s) to a shopping cart, the system determines whether the user wants to move one or more items to one or more different

wish lists (block 406). If not, the system returns to block 396. Otherwise, the system presents the user with a list of existing wish lists (block 412). Then, the user selects one or more

of the existing wish lists (block 414). The user is then prompted to enter the number

of products to be added to the selected wish list(s) (block 416). The item(s) are then copied, in block 418, from the user's scan list to the selected wish list(s). The system

then returns to block 396.

In FIG. 16, the system allows the wish list creator (user) to delete items from a wish list (block 420). In one embodiment, the user goes online and selects the wish

list option (e.g., a tab) which brings the user to the wish list web page (block 422). The user then selects an existing wish list (block 424). The wish lists may, for example, be presented in alphabetical order according to the names of the wish lists.

The user is then presented with a list of one or more items from the selected wish list

(block 426). In block 428, the user selects one or more of the items from the selected

with list. The system, in block 430, determines whether the user wants to delete the

selected item(s) from the wish list. If not, the system returns to block 424. If so, the

user is prompted, in block 432, to reduce the quantity associated with an item. In

block 434, the system determines whether the user reduced the quantity to zero. If so,

the item is removed from the wish list and transferred to the customer transactional archive (block 436). Otherwise, the quantity for the selected item is reduced to the

amount indicated by the user (block 438). After either block, the system returns to block 424.

FIG. 17 describes what happens when a user selects a certain number of items from his/her wish list to be added to the user's shopping cart (block 440). In one embodiment, the user, in block 442, checks-out online (i.e., proceeds to purchase the

items in the user's electronic shopping cart) by, for example, clicking an icon

representing a shopping cart. The system then receives the order (block 444). In

block 446, the system decrements the number of items from the selected wish list by the quantity purchased by the user and updates database 410. In one embodiment, the number of items outstanding on a wish list is visible only to the person buying the item (block 450). Therefore, in this embodiment, the number of outstanding items is only visible to the user). If the user printed out a particular wish list and dropped it off at a participating store or mall, a kiosk agent will input the number of items to be purchased from that wish list (block 452). The system then returns to block 446.

FIGs. 18a-b describe what happens when the user has selected items to purchase online and desires to review his/her shopping cart (block 454). In block 456,

the system displays the prosumer purchase module. The system then displays for the user a description of the items in the user's electronic shopping cart along with the

status of the items (e.g., available, sold out, backordered) (block 458). The status of

the items is retrieved from database 410 which includes the inventory levels for each

of the retail items available to the user. In one embodiment, the database 410 is linked to each retailer's database (represented by database 470) so that current inventory

levels can be determined. The inventory levels can be updated in real-time, hourly,

daily, etc. The system next determines whether the user wants to remove one or more items from the list of items in the shopping cart (block 460). If so, the system proceeds to block 462 where the customer selects the item(s) to be removed from the shopping cart. Then, the item(s) are removed from the shopping cart (block 464) and database 410 is updated. The system then returns to block 458.

If in block 460 the user chose not to remove any items from the shopping cart,

the system proceeds to block 472 where the system determines whether the user wants to change the quantity of any of the items in the shopping cart. If not, the customer

selects the items to be purchased (block 474). In one embodiment, the system assumes the user wants to purchase all of the items in the shopping cart, unless the quantity of an item is zero (block 480). The system then proceeds to block 482 (described below with reference to FIG. 21a).

If the system determines, in block 472, that the user wants to change the quantity of any of the items in the shopping cart, the system proceeds to block 476

where the user is permitted to enter a new quantity for one or more of the selected

items (in this embodiment, the system default is the quantity transferred to the shopping cart). The user is allowed to change the quantity to, for example, any value less than 100 (block 478), i.e., the quantity field allows only two digits to be entered.

Changing the quantity updates database 410 and returns the system to bock 458.

FIGs. 19a-b describe what happens when the user adds an item to a wish list

from an e-tailer web site (block 256). The user, in block 486, selects an e-tailer icon by, for example, clicking on an appropriate icon. In one embodiment, this launches a

second instance of the user's web browser and points the browser to the URL of the

selected e-tailer. The user then browses through an online catalog at the e-tailer's web site (block 488). The user identifies the items to be added to a wish list (block 490) by, for example, selecting one or more of the items by clicking thereon or typing the name of one of the items in a text box provided by the first instance of the user's web browser. In the latter embodiment, the user switches from the second browser

window showing the e-tailer's web site to the first browser window showing the

system's web site (e.g., fastfrog.com) (block 492). The system then proceeds to block

494 where the user inputs the name of the desired item into the text box and selects the e-tailer where the item can be purchased by, for example, using a pull down menu

of e-tailers.

To allow the system to easily return to the e-tailer web page where the selected item(s) are located, the system, in one embodiment, creates an addition to the user's selected wish list in HTML (block 496) by appending the name of the desired item to the URL of the e-tailer. For example, if the user added a beanie baby to his/her wish

list from etoys.com, the HTML code would be modified to read:

<A HREF=HTTP://WWW.etoys.com>beanie_baby</A> In block 498, the system determines whether the selected item(s) are the first item(s)

from this e-tailer that are associated with the selected wish list. If these items are not

the first item(s) from this e-tailer, the system proceeds to block 500 where the relationship between the e-tailer and the selected wish list is already established. This

means that (1) user identification and the type of wish list event are already appended

to the URL of the system's web site (e.g., http://www.fastfrog.com/wishlist.ixw?user_id=l&wishlist=birthday) and (2) the street address of the user is already known to the system. From block 500, the system proceeds to block 506 where the relationship information (in the form of a URL) is saved as the unique name for this transaction for later use by the system (for example,

the information can be used to easily return to this web page, for reconciliation

purposes at periodic intervals, etc.).

If the selected item(s) are the first item(s) selected from this e-tailer, the

system proceeds from block 498 to block 502 where the system interfaces with the e- tailer and creates a relationship between the user, the wish list and the e-tailer. The system creates an e-tailer relationship for this wish list, in block 504, by appending user identification and the type of wish list event to the URL of the system (e.g., http://www.fastfrog.com wishlist.ixw?user_id^:=l&wishlist=birthday) and saving the

street address of the user. The system then proceeds to block 506. FIGs. 20a-b describe what happens when a buyer wishes to buy an item from an e-tailer web site (block 510). The buyer, in block 512, views a wish list created by

one of the users. The buyer then selects one or more of the item(s) on the wish list. In one embodiment, the buyer then selects a "purchase product" icon by, for example, clicking thereon (block 514). This is different than selecting the "shopping cart" icon

discussed above with reference to FIG. 17. In block 516, the system determines

whether the buyer wants to view and or purchase the selected product(s). If not, a

second instance of the buyer's browser is not launched (block 518) and the system

returns to block 514. Otherwise, the buyer is warned that he/she will be using a third-

party's web site to purchase the selected item(s) and will return to the system's web site (e.g., fastfrog.com) upon completion of the purchase (block 520). In block 522, the system launches a second instance of the buyer's web browser thus producing a second window displaying the web site associated with the URL of the e-tailer where

the selected product(s) may be purchased. In one embodiment, the buyer is responsible for finding, selecting and purchasing the selected product(s) (block 524).

In another embodiment, the system automatically links the buyer to a web page containing the selected product. After the buyer purchases the selected product(s), the

buyer is responsible for closing the second instance of the web browser and returning

to the system's web site (e.g., fastfrog.com) (block 526).

In block 528, the system determines whether the buyer found the selected product(s). If so, the buyer continues to browse and shop at the system's web site (block 530). In one embodiment, the e-tailer will periodically send affiliate revenue and activity reports to the originating web site (e.g., fastfrog.com) so that, for example, the success of the affiliate program can be assessed (block 532).

If the buyer did not find one or more of the selected item(s), the buyer can use

a concierge service to complete the e-tailer order (block 536) by, for example, clicking

on an appropriate icon displayed on the system's web site. The system then displays the user's shopping cart list which is sent to the concierge service so that the user's

order can be fulfilled (block 538).

Referring to FIG. 21a, the system proceeds from block 482 (the buyer has

selected items to purchase by including certain items in his/her shopping cart) to 540

where the system displays the shopping cart check-out module. The system

determines whether the buyer wishes to gift wrap one or more of the items in the shopping cart (block 544). If not, the system proceeds to block 550. Otherwise, in

block 546, the buyer selects which item(s) should be wrapped. Next, the buyer selects a card design and inputs the text to be included therein (block 548). In block 550, the system determines whether the buyer intends to be the recipient of the purchase. If so, the buyer must confirm his/her address or enter his/her address (block 552). If not, the

buyer is prompted to enter the address of the recipient (block 553). The address

information is stored to database 410. In block 554, the system determines whether

there are any additional items in the shopping cart that do not have a shipping address associated with them. If there are items without a shipping address, the system returns to block 550. Otherwise, the system proceeds to block 556.

Referring to FIGs. 21b-c, the system proceeds from block 556 to 560 where the system will identify the location of the system's fulfillment center where the order will be processed based on the e-tailer web site that generated the order. In block 562, the buyer will be prompted to select the shipping method to be used for each group of

one or more items to be shipped. The system then provides the buyer with the total cost, including shipping and taxes (block 564). The tax information for the order is

generated from a separate tax software program (block 566). In block 568, the system determines whether the buyer wants to proceed with the purchase. If not, in block

570, the buyer is sent back to the home page of the system's web site (the items in the

buyer's shopping cart remain there in perpetuity or until deleted by the system).

Otherwise, the system determines, in block 572 (FIG. 21c), whether the buyer's

credit card is already on file by checking database 410 which contains directory data.

If not, the system proceeds to block 576. If the credit card is on file, the system determines whether the credit card is valid (block 574) by, for example, obtaining a credit authorization from a credit authorization firm (block 575). If the card on file is valid, the system proceeds to block 578 where the buyer is prompted to enter the last

four digits of the credit card.

If the card on file is not valid, the buyer is requested to re-enter his/her credit

card information (block 594). In block 576, the buyer inputs his/her credit card number and expiration date. The system next determines whether the entered credit

card number is valid (block 592) by, for example, obtaining a credit authorization

from a credit authorization firm (block 575). If the number is not valid, the system returns to block 594; otherwise, the system proceeds to block 580. In block 580, the system provides the buyer with an order number for the purchase. The system generates an e-mail confirming the order in block 582. The system, in block 584, transfers data to the in-store/in-mall process module by downloading order data to database 410. The system then proceeds to block 588 and the system is finished.

FIGs. 22a-b describe what happens when a user wishes to create an access

mechanism, such as an ACL, that allows specified buyers to be notify about, and have access to, one or more of the user's wish lists (block 598). The user, in block 600, views a previously created wish list. The system proceeds from block 600 (or block 364) to block 602, where the system determines^* whether the user wishes to remove or

add a wish list buyer to, for example, the user's access control list (ACL). If the user

wishes to remove a buyer, the system removes the selected buyer from the ACL

corresponding to the wish list selected by the user so that the removed buyer cannot

access the selected wish list (block 604). The system then updates the user's personal list of ACL members, which resides on the user's ACL database 606. If the user wishes to add a buyer, the system proceeds from block 602 (or block 348) to block 608 where the system determines whether the buyer entered by the user is a member

residing within the user's ACL. If not, the system searches the shopping operating system (SOS) member directory, residing on the SOS ACL database 612, for the

entered buyer (block 610).

In block 630, the system determines whether there was a match to an existing SOS member. If not, the system must add the buyer to the SOS ACL (block 632). In

one embodiment, the user enters the buyer's full name, city and state, and either (1) the buyer's e-mail address, (2) street address, or (3) telephone number (block 634). The entered buyer is then registered as an SOS ACL member (block 636).

If there was a match to an existing member in block 630 or once the new buyer is registered in block 636, the system, in block 614, adds the registered member to the

user's ACL for the selected wish list, which resides on database 606. The system next determines whether the buyer has an e-mail address registered with the system (block

618). If not, the system, for example, generates a preprinted post card to mail to the buyer (block 620). The generated post card notifies the recipient that he/she has been granted access to the user's online wish list and has been signed up as a registered member of the SOS program (block 622). The post card further includes the buyer's

user name and password. The buyer can then proceed to a participating store or mall

to view the wish list at an in-store/in-mall kiosk or logon to the SOS web site and

view the wish list online.

If, in block 618, the system determines that the buyer has an e-mail address registered with the system, the system generates an e-mail notification to alert the buyer that he/she has been granted access to the user's online wish list and has been

signed up as a registered member of the SOS program (block 624). The e-mail further includes, for example, the buyer's user name and password, wish list password (if appropriate), and a hyperlink to the SOS web page where the buyer can view the wish

list online (block 626). In block 628, the system alters the user if the buyer's entered

e-mail address is invalid.

FIGs. 23a-b describe what happens when a user wishes to add a buyer to

his/her access mechanism (e.g., an ACL) (block 638). The user, in block 640, enters, for example, the buyer's full name, city and state, and either (1) the buyer's e-mail address, (2) street address, or (3) telephone number. The system then determines whether the user entered the proper information into the supplied fields (block 642). If not, the system determines whether a valid e-mail address has been entered (block 644). Otherwise, the system proceeds to point D (block 646, described below with

reference to FIG. 23b).

If a valid e-mail address was not entered, the system will assign the buyer a unique identification number which can be used as the buyer's user name for login purposes (block 664). The system then proceeds to block 666. If a valid e-mail

address was entered in block 644 or after block 664, the system proceeds to block 666

where the system determines whether the remaining fields contain valid information.

If not, the system notifies the user which fields were improperly entered (block 668)

and the system proceeds to block 272 (described above with reference to FIG. 10).

Otherwise, the system proceeds to point D (block 646).

From block 646, the system proceeds to block 648 where the system determines whether the entered buyer information matches a buyer already present in the SOS ACL database 612. If not, the new buyer information is added, in block 650, to database 606 which contains the user's ACL. Otherwise, the system prompts the user to select from a list of existing buyers on the SOS ACL or cancel and return to

the home page of the SOS (block 654).

In block 656, the system determines whether the user selected a buyer from the

SOS ACL. If not, the system proceeds to block 650; otherwise, if an existing buyer is

selected (block 658), that buyer is added to the user's individual ACL (block 660). In one embodiment, the user's individual ACL is linked via an index or table to the SOS

ACL.

FIG. 24 describes what happens when a buyer wishes to view a wish list at a store/mall or online (block 670). The system, in block 672, determines whether the buyer is an existing or new buyer. If the buyer is new, the system prompts the buyer

to register with the system as a Level 2 user (block 674). Then, the system determines

whether the buyer completed the registration information (block 676). If so, the system proceeds to block 678. Otherwise, the system returns to block 672. In block 678, the buyer logs into the system by entering a user name and password (block 678). The buyer may have previously registered with the SOS or a user may have added the

name of this buyer to the user's list of buyers who are authorized to access a particular wish list. The system then determines whether the buyer successfully logged into the

system (block 680) by comparing the entered user name to the SOS ACL which

resides in database 612. If the login was unsuccessful, the system notifies the buyer

that he/she entered an invalid user name and/or password (block 682). Otherwise, the system determines whether the buyer has already registered with the SOS (block 684).

If not, the buyer is considered a Level 1 registered user (block 686). Otherwise, the buyer is presented with a list of all wish lists that he/she is authorized to view (block

688). The list of authorized buyers and the corresponding wish lists reside in the SOS

ACL database 612 and the wish list database 302, respectively. The buyer then selects

a specific wish list to view (block 692).

At this point the buyer has various options. As a first alternative, the buyer

may select a specific item in the selected wish list (block 694). Then, the buyer can print a description of the item (block 696) and/or buy the selected item (block 698). As a second alternative, the buyer can choose to buy all the items on the selected wish list (block 1200). If the buyer decides to do this, the entire wish list is added to the buyer's shopping cart (block 1202). Otherwise, the system proceeds to block 694. As a third alternative, the buyer can print the wish list via the print option on the user's

web browser (block 1204). In block 1206, the system prints a report including all the items on the wish list. With respect to the in-store/in-mall PDA shopping component of the system

10, FIGs. 25-32 show detailed flow charts illustrating one embodiment of how a

shopper uses a PDA scanner in a physical store or mall 12. FIG. 25 shows one

embodiment illustrating how a wish list creator (user) 120, an aggregated shopper 160

and/or a wish list buyer 140 interact with the illustrated in-store/in-mall experience

896 in order to, for example, shop with a PDA scanner (block 898); buy items through an aggregated shopper (block 900); and buy items from a wish list (block 902). Similarly, the user 120, aggregated shopper 160 and/or buyer 140 interact with the

illustrated kiosk 888 to pick-up a PDA scanner (block 894); and return the PDA scanner (block 892).

Likewise, the user 120, aggregated shopper 160 and/or buyer 140 interact with

the illustrated PDA workstation 882 to upload data from the PDA scanner (block

884); and download data to the PDA scanner (block 886). In addition, the user 120, aggregated shopper 160 and/or buyer 140 interact with the illustrated prosumer 152 (a

platform where common functionalities, such as the wish list, and buyer and user profiles, reside) to enter user information to generate a scan list (block 878); and enter buyer information to obtain a wish list (block 880). The PDA agent 890 interacts with the prosumer, PDA workstation and kiosk to help users and buyers register with the system, create and obtain wish lists, and shop using PDA scanners. In FIGs. 26a-b, a buyer is at a kiosk at a participating store or mall where the buyer can interact with a computer. The system, which is connected to the computer,

first determines whether the buyer provided a user name and password (block 904). If so, the system allows the buyer to print out one or more buy lists (or, if the buyer is the creator-user, his/her wish list(s) can be edited) (block 906). If the buyer is the

creator-user, the system proceeds to block 922 where the user can edit items in an

existing wish list(s) and/or an existing scan list(s). Otherwise, the third-party buyer

proceeds to block 908 where the system displays for the buyer a list of buy lists (wish

lists) that the buyer is authorized to access. The buyer then selects one or more of the displayed wish lists (block 910). In block 912, the system provides the buyer with a

print-out of the items on the wish list(s). The system, in block 914, prints out the selected wish list(s) in a "shopping list" format that includes, for example, the name of the store where each item can be purchased, the name of the products on the wish list(s), a description of each item, the number of items remaining that the user desires,

the wish list creator's (user's) name, a barcode number for each product, if applicable,

and the name of the wish list(s). The system then displays, for example, a list of participating stores and policies relating to buying items on the wish list(s) (block

916). In block 918, the buyer proceeds to the designated stores. The system then

proceeds to block 920 (described below with reference to FIG. 27a).

If the buyer did not enter a user name and password in block 904 or if the

buyer is registering at an in-store/in-mall kiosk (block 923), the system initiates the SOS web site which allows the buyer to register with the system (block 924). The system prompts the buyer to enter Level 1 registration information (block 926). This information includes, for example, the buyer's full name, e-mail address, login name,

password, and telephone number. In block 928, the buyer completes the online registration process. The system then determines whether the buyer entered valid

information in all the required fields (block 930). If so, the system proceeds to block 936. Otherwise, the system will provide feedback to the buyer indicating, for

example, incomplete fields, and will request that the buyer enter valid information

into the indicated fields (block 932). In block 934, the system again determines

whether the buyer entered valid information in all the required fields. If not, the

system returns to block 932. Otherwise, the system proceeds to block 936 where the

system confirms the login and provides the buyer with his/her user name and password. The system then proceeds to block 906.

Referring to FIG. 27a, the system proceeds from block 920 to block 938 where the buyer visually identifies, from a printed wish list "shopping list," the stores

participating in the wish list program. In block 940, the buyer purchases one or more items on the wish list from a physical store. The buyer then has the option of

returning to the kiosk where he/she began (block 942). If the buyer does not return to the kiosk, the wish list will not be updated to indicate which items the buyer

purchased (block 944), unless the buyer thereafter updates this information online by

logging into the system's web site. Otherwise, the buyer provides the kiosk agent

(sherpa) with the shopping list and an indication of which items were purchased (block 946). The agent then decrements the requested number of items on the wish list to reflect the number of items purchased by the buyer (block 948), which updates the wish list database 302. The agent can do this anytime after the buyer returns the shopping list, but will likely do this after hours.

In FIG. 27b, the kiosk agent places each PDA into its respective interface

cradle for recharging and data synchronization (block 954), where retailer data is downloaded into each PDA (block 956) from database 410. This downloading procedure is only required for PDA's that are not wireless (i.e., PDA's that connect to

the system via an interface cradle - batch processing PDA's). Wireless PDA's can

download information periodically or continuously without having to be physically

connected to an interface device.

FIGs. 28a-b describes how the kiosk agent (sherpa) identifies the user to the system (block 962). The system first prompts the user for his/her full name (block 964). In one embodiment, the system then downloads all of the user's existing wish

lists, scan lists and shopping cart lists from an external database to the internal memory of the PDA (block 966) by via a wireless data connection, an interface cradle, etc. In another embodiment, the system downloads information to display all of the

user's existing wish lists, scan lists and shopping cart lists from an external database to the PDA via an interface cradle, a wire connection, an Infra-Red connection, etc. The

display information includes, for example, all the products sold by each participating

retailer in that specific mall and the UPC, product description, size, color, price, and retailer name (block 970). In block 968, product data, such as product name data, retailer SKU data, etc., is downloaded into the PDA memory for subsequent shopping and scanning. In block 972, the system determines whether any of the products on the user's wish list(s), scan list(s) or shopping cart list(s) are not available in that store or mall. If any of the products are not available, then data on those products must also be downloaded into the user's PDA (block 974). Otherwise, the PDA is ready for use by

the user (block 976).

Referring to FIGs. 29a-b, the user can either proceed from block 978 to block 980 to add items to his/her scan list by scanning items at a store or mall, or to block 1034 (FIG. 32a) to modify a scan list and/or buy one or more items at a store or mall.

If the user chooses the first option, the system proceeds from block 978 to block 980

(FIG. 29a) where the user visually identifies stores participating in the wish list

program. In block 982, the user has the option of scanning a barcode outside a

participating store to identify the store to the PDA. If the user does not scan a

barcode, when the user scans a product in that store, the PDA will prompt the user to identify the store using the PDA interface (block 984). If the user does scan a barcode or after he/she enters the identity of the store, the PDA will recognize the store (block 986). From blocks 986 or 990, the user scans the barcode of any item in the store using the PDA (block 988). The system then either proceeds to block 1024 (which is

described below in relation to FIG. 32b) or block 992.

Referring to FIG. 29b, in block 992, the PDA determines whether it recognizes

the scanned barcode. If not, the system proceeds to block 996 (which is described

below in relation to FIG. 30a). Otherwise, the system proceeds to block 994 where

the PDA confirms the user's selection by, for example, beeping, displaying a confirmation message, or displaying the store name, item number, product name, color, size, etc. The system proceeds from block 994 or block 998 to block 1000 where the user then has the option of deleting the scanned item or continuing to shop

(which, for example, could be the default setting). If the user does not indicate that he/she wants to delete the scanned item (block 1002), the scanned item is added to the

scan list (block 1004). Otherwise, the system returns to block 988.

From block 1004, the system proceeds to block 1016 where the user has the

option of moving a scanned item from the scan list to a specific wish list. In one embodiment, if the user wants to move an item, the item is first removed from the

scan list (block 1020). Alternatively, the item may be copied to the wish list while

remaining on the scan list. In block 1022, the user selects from one or more

preexisting wish lists and adds the scanned item to the selected wish list(s). Next, the system determines whether the user selected another item in the store by scanning a

barcode (block 1018). If so, the system proceeds to block 988. Otherwise, if the user has proceeded to another retailer in the mall (block 1006), the system proceeds to

block 982. If not, the user can use additional functionality provided by the PDA (block 1008) such as, for example, deleting, moving and copying items between all

existing wish lists, scan lists and shopping cart lists (block 1010). Then, the user proceeds to the kiosk where the PDA cradle or lily pad resides (block 1012). From

there, the system proceeds to block 1014 and the system is finished.

Referring to FIGs. 30a-b, the system proceeds from block 996 to block 1026 where the system produces an error code after an item is scanned. In block 1028, the

system determines whether the scanner captured the complete barcode. If not, the

PDA prompts the user to rescan the item (block 1030). Then, the system determines whether the user successfully rescanned the item (block 1052). If so, the system proceeds to block 998 (described above with reference to FIG. 29b). Otherwise, the system determines whether the user unsuccessfully scanned the item three consecutive times (block 1054). If not, the scanner successfully captures the complete barcode

(block 1056) and proceeds to block 990 (which is described below in relation to FIG. 32a). Otherwise, the user is alerted that there is a problem scanning the item and that the user should select another item to scan (block 1058) or enter the barcode number

manually. The system then proceeds to block 990.

If the scanner, in block 1028, did capture a complete barcode, the system

determines whether the store carries an item corresponding to the scanned barcode

(block 1032). If not, the barcode does not reside in the memory of the PDA (block

1034). In block 1046, the system will log the unknown barcode for future analysis. The PDA then alerts the user that the product does not reside in its memory and that

the item cannot be scanned (block 1048). Thereafter, the user is not allowed to enter that product into the PDA (block 1050). The system then proceeds to block 990 (described below with reference to FIG. 32a).

If the current store does not carry an item corresponding to the scanned

barcode, the user most likely entered a new store without identifying that store to the

PDA (block 1036). The PDA will then list stores that carry the scanned product (block 1038). Then, the system determines whether the user makes a valid store

selection (block 1040). If not, the system returns to block 1038. Otherwise, the PDA will, for example, display the scanned item to indicate that the scan was successful (block 1042). In one embodiment, the PDA then updates itself to operate in the new store (block 1044). The system then proceeds to block 998 (which is described above in relation to FIG. 29b). FIGs. 31a-b describe how the kiosk agent synchronizes batch processing

PDA's by placing them into cradles connected to the system (block 1060). In one

embodiment, the system gathers behavioral data about the users (block 1062) such as

which items were scanned, which items were added to a wish list, which items were deleted from a wish list, etc. The system then determines whether there are any

changes to the wish lists, scan lists or shopping cart lists stored in the memory of the

PDA (block 1064). If not, PDA data (such as behavioral data) is uploaded and the

synchronization is complete (block 1066). Otherwise, the system determines whether

there was a change to any of the wish lists (block 1068). If not, no changes are made to the pre-existing wish list data for this user which resides on an external database

(block 1069). Otherwise, in block 1070, the data residing in the PDA will replace the preexisting wish list data for this user which resides on the external database. After block 1069 or 1070, the system determines whether there are any changes to the scan list (block 1072). If not, no changes are made to the pre-existing scan list data for this

user which resides on an external database (block 1074). Otherwise, in block 1076, the data residing in the PDA will replace the preexisting scan list data for this user

which resides on the external database.

After block 1074 or 1076, the system determines whether there are any changes to the shopping cart list data (block 1078). If not, no changes are made to the pre-existing shopping cart list data for this user which resides on an external database (block 1080) and the system proceeds to block 1088. Otherwise, in block 1082, the

data residing in the PDA will replace the preexisting shopping cart list data for this user which resides on the external database. In block 1084, the system determines whether the user wants to purchase one or more items in the user's shopping cart. If so, the system proceeds with order fulfillment by displaying a list of items in the user's

shopping cart (block 1088). The user then selects one or more of these items to

purchase (block 1090). Otherwise, if the user does not want to make a purchase, all the items will continue to reside in the user's shopping cart (block 1086). The user can thereafter add one or more of these items to a wish list and/or purchase one or

more of these items at a later time.

Referring to FIGs. 32a-b, if the user chose the option of modifying a scan list

and/or buying one or more items at a store or mall, the system proceeds from block

978 to block 1094 where the user visually identifies stores participating in the wish list program. In block 1096, the user has the option of scanning a barcode outside a

participating store to identify the store to the PDA. If the user does not scan a barcode, when the user scans a product in that store, the PDA will prompt the user to identify the store using the PDA interface (block 1098). If the user does scan a barcode or after he/she enters the identity of the store, the PDA will recognize the

store (block 1100). After block 1100 or block 990, the user scans the barcode of any

item in the store using the PDA (block 1102). The system then proceeds to either block 1104 or block 1024 (which is described below in relation to FIG. 32b). In block

1104, the PDA determines whether it recognizes the scanned barcode. If not, the system proceeds to block 996 (which is described above in relation to FIG. 30a). Otherwise, the system proceeds to block 1106 where the PDA confirms the user's selection by, for example, beeping, displaying a confirmation message, or displaying the store name, item number, product name, color, size, etc. The system proceeds from block 1106 or block 998 to block 1108 where the

user is presented with three options: delete item, add item to shopping list, or buy

item now. If the user chooses to delete the selected item, the system determines if the user selects another item in that store (block 1112). If so, the system returns to block 1102. Otherwise, if the user has proceeded to another store (block 1114), the system

returns to block 1096. If not, the system proceeds to block 1116 (which is described

below in relation to FIG. 32c).

If, in block 1108, the user chooses the second option, the system adds the

selected item to the user's shopping list (block 1110). The system then proceeds to

block 1112. If the user chooses the buy now option, the PDA instructs the user, for example, to place the scanned item into the YourSherpa bin at that store (block 1118). Then, the user carries the item to the YourSherpa bin located in that store (block 1120). The system proceeds to block 1122 where the PDA requests the user to confirm that the item was placed in the YourSherpa bin. The system then returns to block 1112.

If an error occurred while scanning an item, the system proceeds from block

1024 to block 1124 where the user can manually enter the UPC/SKU number into the

PDA so the system will recognize the item the user attempted to scan. Referring to FIG. 32c, the system proceeds from block 1116 to block 1126

where the user proceeds to the kiosk where the PDA cradle or lily pad resides. In block 1128, additional functionality is provided by the PDA for the user such as, for

example, displaying store promotions for the store just scanned by the user. The system, in block 1134, determines whether the user has placed any items in the "buy now" shopping cart. If so, the system determines whether the user has completed registration Level 3 (block 1136). If the user has not completed that registration level,

the system proceeds to block 1140 where the user must complete a Level 3

registration at the store/mall kiosk before the user makes a purchase. Then, the user confirms the items to be purchased and the price to be paid (block 1142). The kiosk

agent then submits the user's credit card information and the amount of the purchase

for credit authorization (block 1144). Next, the user receives a receipt to confirm

purchase of the items (block 1146).

From block 1146 or from block 1134 (if the user did not place an item in the

"buy now" shopping cart), the system proceeds to block 1138 where the system communicates the purchase request to an order fulfillment module that fulfills the order. This communication may occur, for example, immediately via wireless communication or when the PDA is placed in its interface cradle. Then, the system proceeds to block 1014 and the system is finished.

While particular embodiments of the invention have been shown and described in detail, it will be obvious to those skilled in the art that changes and modifications of

the present invention, in its various embodiments, may be made without departing

from the spirit and scope of the invention. Other elements, steps, methods and techniques that are insubstantially different from those described herein are also within the scope of the invention. Thus, the scope of the invention should not be limited by the particular embodiments described herein but should be defined by the

appended claims and equivalents thereof.

Claims

WHAT IS CLAIMED IS: 1. A method for shopping in a physical retailer and online, the method

comprising:

providing a database and a handheld data entry unit including an internal

memory;

storing item information corresponding to items scanned in the physical retailer in the internal memory of the data entry unit; downloading the item information from the internal memory of the data entry unit to the database; creating a wish list that includes the items; storing the wish list on the database;

providing a web site that allows a user to generate one or more buy lists, each buy list including one or more of the items from the wish list; and

transmitting a message to a buyer in order to inform the buyer of the existence of one or more of the buy lists.

2. The method of claim 1 , wherein the buyer is a concierge service, further including electronically authorizing the concierge service to purchase one or more of the items on the buy list through a retailer or e-tailer.

3. The method of claim 1, further including: allowing the user to create an access mechanism identifying a list of buyers that are allowed to access one or more of the buy lists.

4. The method of claim 3, wherein the access control mechanism is selected from

the group consisting of an access control list, password protection, public access and

private access.

5. The method of claim 1, further including: allowing the user to create an access control list (ACL) that identifies certain

buyers that are allowed to access one or more of the buy lists; and electronically requesting one or more of the buyers on the ACL to purchase

one or more of the items on the buy list.

6. The method of claim 1, further including allowing the user to add additional

items to the wish list by shopping at electronic retailers.

7. The method of claim 1, further including allowing the user to add additional

items to the buy list by shopping at electronic retailers.

8. The method of claim 1, further including:

linking the buyer to the web site; and

displaying a web page containing one of the buy lists.

9. The method of claim 1, further including: linking the buyer to the web site; and displaying a web page containing the buy list corresponding to the buyer.

10. The method of claim 1 , further including allowing the buyer to buy one of the

items on the buy list through an electronic retailer by linking the buyer to the electronic retailer.

11. The method of claim 1 , further including allowing the buyer to electronically

notify and authorize a concierge service to purchase one of the items on the buy list

through a retailer or e-tailer.

12. A computer system for shopping in a physical retailer and online, the computer

system comprising:

a processor; a database coupled to the processor; and at least one handheld data entry unit including an internal memory; the data entry unit being programmed to: scan physical items;

store item information corresponding to the scanned items in the internal memory; and

download the item information from the internal memory of the data entry unit to the database;

the processor being programmed to : create a wish list that includes items corresponding to the item

information downloaded to the database; provide a web site that is in communication with the database, the web site allowing a user to generate one or more event lists, each event list

including one or more of the items from the wish list;

allow the user to create an access mechanism that identifies a list of buyers that are allowed to access one or more of the event lists; and transmit a message to one of the listed buyers in order to inform the

listed buyer of the existence of one or more of the event lists.

13. The computer system of claim 12, wherein the data entry unit comprises a

personal digital assistant (PDA).

14. The computer system of claim 12, wherein the data entry unit comprises a

barcode scanner.

15. The computer system of claim 12, wherein the processor is further programmed to allow the user to add additional items to the wish list by shopping at

electronic retailers.

16. The computer system of claim 12, wherein the processor is further programmed to allow the user to add additional items to the event list by shopping at

electronic retailers.

17. The computer system of claim 12, wherein the processor is further

programmed to: link the listed buyer to the web site; and display a web page containing the event list corresponding to the listed buyer.

18. The computer system of claim 12, wherein the access control mechanism is selected from the group consisting of an access control list, password protection, public access and private access.

19. The computer system of claim 12, wherein the processor is further

programmed to link the listed buyer to an electronic retailer that sells one of the items

on the event list.

20. The computer system of claim 12, wherein the processor is further programmed to allow the listed buyer to electronically notify and authorize a concierge service to purchase one of the items on the event list through a retailer or e-

tailer.

21. A computer server for hosting a system for shopping in a physical retailer and

online, the server comprising:

a processor; and a database accessible to the processor;

the processor being programmed to : download data representing one or more items from a handheld data entry unit to the database; create a wish list from the data downloaded to the database, the wish

list including the one or more items;

provide a web site that is in communication with the database, the web site allowing a user to generate one or more buy lists, each buy list including

one or more of the one or more items from the wish list; and transmit a message to a buyer in order to inform the buyer of the existence of one or more of the buy lists.

22. The computer server of claim 21 , the processor being further programmed to : allow the user to create an access mechanism that identifies a list of buyers that are allowed to access one or more of the buy lists; and

transmit a message to at least one of the listed buyers in order to inform the listed buyer of the existence of one or more of the buy lists.

23. The computer server of claim 22, the processor being further programmed to

allow the user to electronically request at least one of the listed buyers to purchase one

or more of the items on the buy list.

24. The computer system of claim 22, wherein the access control mechanism is

selected from the group consisting of an access control list, password protection,

public access and private access.

25. The computer server of claim 21, wherein the buyer is a concierge service, the processor being further programmed to electronically authorize the concierge service to purchase one or more of the items on the buy list through a retailer or e-tailer.

26. The computer server of claim 21 , the processor being further programmed to

allow the user to add additional items to the wish list by shopping at electronic retailers.

27. The computer server of claim 21 , the processor being further programmed to:

link at least one of the buyers to the web site; and display a web page containing the buy list corresponding to the at least one buyer.

28. A method of receiving and communicating a list of one or more items over the Internet, the method comprising: downloading data representing the items from a handheld data entry unit to a database;

creating a wish list from the data downloaded to the database, the wish list including one or more of the items; providing a web site that is in communication with the database, the web site allowing a user to generate one or more event lists, each event list including one or

more of the items from the wish list; allowing the user to create an access mechanism that identifies a list of users

that are allowed to access one or more of the event lists; and transmitting a message to at least one of the listed users in order to inform the listed user of the existence of one or more of the event lists.

29. The method of claim 28, further including allowing the listed user to buy one of the items on the event list through an electronic retailer.

30. An Internet based method ofreceiving and communicating a list of one or more items over the Internet, the method comprising:

providing a web site having a user interface including one or more user

windows, the one or more windows providing an event list screen and a wish list screen;

retrieving a list of one or more items; arranging the one or more items into one or more wish lists on the wish list screen; entering one or more events into an event list on the event list screen; assigning one or more of the items from the wish list to one or more of the event lists;

creating an access mechanism that identifies a list of buyers that are allowed to

access one or more of the event lists; and transmitting a message to at least one of the listed buyers in order to inform the listed buyer of the existence of one or more of the event lists.

31. The Internet based method of claim 30, wherein the one or more windows provide a registration screen.

32. The Internet based method of claim 31 , further including allowing a user to

enter registration information on the registration screen to allow access to the event

list screen and the wish list screen.

33. A computer system for shopping in a physical retailer and online, the computer system being programmed to: download data representing one or more items from a handheld data entry unit to a database;

create a wish list from the data downloaded to the database, the wish list including the one or more items;

provide a web site that is in communication with the database, the web site

allowing a user to generate one or more event lists, each event list including one or

more of the one or more items from the wish list; and connect the user with an online retailer in order to add items to one or more of the event lists.

34. The computer system of claim 33, further instructing the computer to: allow the user to create an access mechanism that identifies a list of buyers that are allowed to access one or more of the event lists; and transmit a message to at least one of the listed buyers in order to inform the

listed buyer of the existence of one or more of the event lists.

35. The computer system of claim 34, further instructing the computer to connect

the listed buyer with an online retailer in order to purchase one or more of the items

on one or more of the event lists.

36. The computer system of claim 33, further instructing the computer to connect

the user with an online retailer in order to purchase one or more of the items on one or

more of the event lists.

37. The computer system of claim 33, further instructing the computer to electronically authorize a concierge service to purchase one or more of the items on the event list through a retailer or e-tailer.

38. A computer system for shopping in a physical retailer and online, the computer system being programmed to:

download data representing one or more items from a handheld data entry unit

to a database;

create a wish list from the data downloaded to the database, the wish list including the one or more items; provide a web site that is in communication with the database, the web site allowing a user to generate one or more buy lists, each buy list including one or more

of the one or more items from the wish list; and transmit a message to a concierge service to buy the items on one or more of the buy lists.

39. The computer system of claim 38, wherein the concierge service buys and

ships the items on one or more of the buy lists to the user.

40. The computer system of claim 38, wherein the concierge service buys and

delivers the items on one or more of the buy lists to the user.

41. The computer system claim 38, further instructing the computer to:

allow the user to create an access mechanism that identifies a list of persons

who are allowed to access one or more of the buy lists; and

transmit a message to one or more of the listed persons in order to inform the listed persons of the existence of one or more of the buy lists .

42. The computer system of claim 38, further instructing the computer to update the one or more buy lists to indicate what items have been purchased.

43. A computer system for shopping in a physical retailer and online, the system comprising:

a processor; and

a database accessible to the processor; the processor being programmed to: allow a user to create a wish list including one or more items by

shopping at one or more electronic retailers; store the wish list on the database; provide a web site that is in communication with the database, the web site allowing a user to generate one or more buy lists which include one or more of the items from the wish list; and

transmit a message to a buyer in order to inform the buyer of the

existence of one or more of the buy lists.

44. The system of claim 43, wherein the buyer is a concierge service, the processor being further programmed to electronically authorize the concierge service to

purchase one or more of the items on the buy list through a retailer or e-tailer.

45. The system of claim 43, wherein the processor is further programmed to:

allow the user to create an access mechanism that identifies a list of buyers that are allowed to access one or more of the buy lists; and

electronically request one or more of the listed buyers to purchase one or more of the items on the buy list.

46. The system of claim 43, wherein the processor is further programmed to allow the user to add additional items to the wish list by shopping at retailers or e-tailers.