WO2011088475A2

WO2011088475A2 - A system and method for facilitating an invitation to a private retail sale event

Info

Publication number: WO2011088475A2
Application number: PCT/US2011/021590
Authority: WO
Inventors: Adam C. Leining
Original assignee: VERCAI Inc
Current assignee: VERCAI Inc
Priority date: 2010-01-15
Filing date: 2011-01-18
Publication date: 2011-07-21
Anticipated expiration: 2012-07-15
Also published as: WO2011088475A3

Abstract

A system and method for facilitating a private retail sale event includes establishing a set of associated merchants and providing a providing a communications portal that publishes information about these retail merchants. Via the communications portal, a user request an invitation to a private sale event hosted by a specific merchant. This request is communicated to the specific merchant. The merchant may then communicate an invitation for a private sale event to the user, via the communications portal. In response, the user may communicate an RSVP message to the merchant, via the communications portal.

Description

A SYSTEM AND METHOD FOR FACILITATING AN INVITATION TO A PRIVATE RETAIL SALE EVENT

Retail merchants such as department stores, boutiques, and kiosks sell goods and merchandise directly to customers. Retail merchants generally buy goods or products in large quantities from manufacturers or importers, either directly or through a wholesaler. These goods are then sold to customers in smaller qualities. Historically, retail merchants sell primarily from stores and shops. Recently, retail merchants have begun to offer their goods and products on the internet.

Because retail merchants may purchase goods or products in large quantities, challenges arise when products and product lines do not sell well. If products do not sell, the retail merchant incurs an economic loss. To recover or minimize loss, retail merchants can offer unsold products for sale at a discounted value after a certain period. If the product is not sold after being discounted, they can be sold at a steeper discount or liquidated to outlet stores. However, some retail merchants of high-end brands may hesitate to have advertised sales and discounts because these can damage the brand image of the products. Even when a retail merchant decides to discount the cost of its product, the timing of such sales presents difficulties. If the product is discounted early, a retail merchant may miss future profits. If a product is discounted too late, the entire product line may be outdated or out of season.

Traditionally, retail products are advertised via television commercials, newspaper ads, billboard signs, mail flyers, and in-store sign, generally directed to the public at large. Such advertisements can be delivered at inconvenience times, and require the retail merchant to predict the needs and wishes of the consumer.

Frequently advertisements can be irrelevant or bothersome for consumers, and time- intensive and expensive for retail merchants.

Consumers generally want popular products at discount prices. However, popular products are might be sold out, and thus never discounted or liquidated. Thus, the selection of size, type, colors, etc of discounted products can be limited and frustrating to consumers.

SUMMARY

In response to the problems in the art, the present system and method provide a cost-effective way for customers and retailers to participate in sale events in response to active marketing practices. This system and method allow retailers to protect their brands and their profit margins by empowering customers to initiate when, where, and what products a retailer offers for sale. A user-initiated personal sale enables the customer to choose brands and categories of products that he or she is in the market for, and request a promotional discount at a time of convenience. This dramatically increases consumer attention, receptivity, and response to promotional marketing. This system provides retailers with information about a customer so that they can promptly respond to customer requests with promotional messaging and offers that are targeted to the customer's profile and consistent with the retailer's current pricing strategies and objectives.

In one aspect, a method for facilitating a private retail sale event includes establishing a plurality of associated merchants and providing a communications portal displaying information relating to at least some of the plurality of associated merchants. Via the communications portal a user is allowed to request an invitation to a private sale event hosted by a specific merchant of the plurality of associated merchants. The user's request is communicated to the specific merchant.

Implementations of the method may include one or more of the following steps. Via the communications portal, a merchant may communicate an invitation for a private sale event hosted by a specific merchant to the user. Via the communications portal, a user may communicate an RSVP message from the user to the merchant via the communications portal. Via the communications portal, an access mechanism, such as a password, ticket, or other like article that give the user access to a private sale event is communicated to the user. Via the communications portal, a merchant may communicate that the user's request for an invitation has been placed on a waiting list. The communications portal may include an internet website.

The method may include authenticating the user as a subscribing user. Allowing a user to request an invitation may include verifying that the user is authorized to make the request and allowing the request if the user is authorized. Storage information may be associated with the user, and communicating the user's request to the specific merchant may include transferring stored information associated with the user to the specific merchant. Information associated with the user may include at least one of a username, gender, and age. The private retail sales event may be an in-store sales event or an online sales event.

In another aspect, a system for facilitating private sale events includes a storage device, a communications portal, and a compilation mechanism. The storage device stores information associated with a plurality of associated merchants and information associated with a plurality of network users. The communications portal is a portal through which information relating to the merchants of the plurality of associated merchants is displayed and through which a network user can request an invitation to a private sale event hosted by at least one of the plurality of associated merchants. The compilation mechanism is coupled to the communications portal and the storage device for compiling and presenting to each merchant a list of network users who requested an invitation to a private sale event hosted by that particular merchant.

Implementations of the method may include one or more of the following aspects. The storage device may be a database. The communications portal may an internet website. The communications portal may transfer invitations for private sale events from merchants to users. The communications portal may transfer RSVP information from users to merchants.

In another aspect, a computer-readable medium contains instructions for controlling a computer system coupled to a network to perform a method, the computer system having a display device, and input device, and a processor for executing the instructions. The method includes presenting, via the display device, a communications portal through which a merchant publishes information relating to the retail merchant and a user accesses the published information. The method also includes receiving at least one command from the user to submit a request to the merchant for an invitation to a private sale event. The method includes

communicating the submitted request to the merchant.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The features of the present invention will become more fully apparent from the following description and appended claims, taken in conjunction with the accompanying drawings. Understanding that these drawings depict only some example embodiments of the invention and are, therefore, not to be considered limiting of its scope, the invention will be described and explained with additional specificity and detail through the use of the accompanying drawings.

Figure 1 shows a block diagram of a system in which the invention may be practiced according to some embodiments.

Figure 2 shows a block diagram of a networked system configuration that may be used in association with some embodiments.

Figure 3 shows a graphical depiction of one embodiment of a communications portal according to some embodiments.

Figure 4 shows a flowchart depicting steps of a method according to some embodiment.

Figure 5 shows a block diagram depicting some aspects of a method according to some embodiments.

Figure 6 illustrates a screen shot of one embodiment of a user communications portal according to some embodiments.

Figure 7 illustrates a portion of the screen shot of Figure 6.

Figure 8 illustrates a screen shot of one embodiment of a merchant user communications portal according to some embodiments.

Figure 9 illustrates a screen shot of one embodiment of another merchant user communications portal according to some embodiments.

DETAILED DESCRIPTION

A description of embodiments will now be given with reference to the Figures. It is expected that the present invention may take many other forms and shapes, hence the following disclosure is intended to be illustrative and not limiting, and the scope of the invention should be determined by reference to the appended claims.

Figure 1 and the corresponding discussion are intended to provide a general description of a suitable operating environment in which embodiments can be implemented. One skilled in the art will appreciate that embodiments can be practiced by one or more computing devices and in a variety of system configurations, including in a networked configuration. However, while the methods and processes have proven to be particularly useful in association with a system comprising a general purpose computer, embodiments include utilization of the methods and processes in a variety of environments, including embedded systems with general purpose processing units, digital/media signal processors (DSP/MSP), application specific integrated circuits (ASIC), stand alone electronic devices, and other such electronic environments.

Certain embodiments embrace one or more computer readable media, wherein each medium can be configured to include or includes thereon data or computer executable instructions for manipulating data. The computer executable instructions include data structures, objects, programs, routines, or other program modules that can be accessed by a processing system, such as one associated with a general- purpose computer capable of performing various different functions or one associated with a special-purpose computer capable of performing a limited number of functions. Computer executable instructions cause the processing system to perform a particular function or group of functions and are examples of program code means for implementing steps for methods disclosed herein. Furthermore, a particular sequence of the executable instructions provides an example of corresponding acts that can be used to implement such steps. Examples of computer readable media include random- access memory ("RAM"), read-only memory ("ROM"), programmable read-only memory ("PROM"), erasable programmable read-only memory ("EPROM"), electrically erasable programmable read-only memory ("EEPROM"), compact disk read-only memory ("CD-ROM"), or any other device or component that is capable of providing data or executable instructions that can be accessed by a processing system.

With reference to Figure 1, a representative system for implementing embodiments includes computer device 10, which can be a general-purpose or special-purpose computer or any of a variety of consumer electronic devices. For example, computer device 10 can be a personal computer, a notebook computer, a netbook, a personal digital assistant ("PDA"), a tablet computer, a mobile phone or other hand-held device, a workstation, a minicomputer, a mainframe, a

supercomputer, a multi-processor system, a network computer, a processor-based consumer electronic device, or the like.

Computer device 10, in some embodiments, includes a system bus 12, which can be configured to connect various components thereof and enables data to be exchanged between two or more components. System bus 12 can include one of a variety of bus structures including a memory bus or memory controller, a peripheral bus, or a local bus that uses any of a variety of bus architectures. Typical components connected by system bus 12 include processing system 14 and memory 16. Other components can include one or more mass storage device interfaces 18, input interfaces 20, output interfaces 22, and/or network interfaces 24, each of which will be discussed below.

Processing system 14 includes one or more processors, such as a central processor and optionally one or more other processors designed to perform a particular function or task. In some configurations, processing system 14 executes the instructions provided on a computer readable media, such as on memory 16, a magnetic hard disk, a removable magnetic disk, a magnetic cassette, an optical disk, a solid state drive or device, or from a communication connection, which can also be viewed as a computer readable medium.

Memory 16 includes one or more computer readable media that can be configured to include or includes thereon data or instructions for manipulating data, and can be accessed by processing system 14 through system bus 12. Memory 16 can include, for example, ROM 28, used to permanently store information, and/or RAM 30, used to temporarily store information. ROM 28 can include a basic input/output system ("BIOS") having one or more routines that are used to establish

communication, such as during start-up of computer device 10. RAM 30 can include one or more program modules, such as one or more operating systems, application programs, and/or program data.

One or more mass storage device interfaces 18 can be used to connect one or more mass storage devices 26 to system bus 12. The mass storage devices 26 can be incorporated into or can be peripheral to computer device 10 and allow computer device 10 to retain large amounts of data. Optionally, one or more of the mass storage devices 26 can be removable from computer device 10. Examples of mass storage devices include hard disk drives, magnetic disk drives, tape drives, and optical disk drives. A mass storage device 26 can read from and/or write to a magnetic hard disk, a removable magnetic disk, a magnetic cassette, an optical disk, or another computer readable medium. Mass storage devices 26 and their corresponding computer readable media provide nonvolatile storage of data and/or executable instructions that can include one or more program modules such as an operating system, one or more application programs, other program modules, or program data. Such executable instructions are examples of program code means for implementing steps for methods disclosed herein.

One or more input interfaces 20 can be employed to enable a user to enter data and/or instructions to computer device 10 through one or more corresponding input devices 32. Examples of such input devices include a keyboard and alternate input devices, such as a mouse, trackball, light pen, stylus, or other pointing device, a microphone, a joystick, a game pad, a satellite dish, a scanner, a camcorder, a digital camera, and the like. Similarly, examples of input interfaces 20 that can be used to connect the input devices 32 to the system bus 12 include a serial port, a parallel port, a game port, a universal serial bus ("USB"), an integrated circuit, a firewire (IEEE 1394), or another interface. For example, in some embodiments input interface 20 includes an application specific integrated circuit (ASIC) that is designed for a particular application. In a further embodiment, the ASIC is embedded and connects existing circuit building blocks.

One or more output interfaces 22 can be employed to connect one or more corresponding output devices 34 to system bus 12. Examples of output devices include a monitor or display screen, a speaker, a printer, a multi-functional peripheral, and the like. A particular output device 34 can be integrated with or peripheral to computer device 10. Examples of output interfaces include a video adapter, an audio adapter, a parallel port, and the like.

One or more network interfaces 24 enable computer device 10 to exchange information with one or more other local or remote computer devices, illustrated as computer devices 36, via a network 38 that can include hardwired and/or wireless links. Examples of network interfaces include a network adapter for connection to a local area network ("LAN") or a modem, wireless link, or other adapter for connection to a wide area network ("WAN"), such as the Internet. The network interface 24 can be incorporated with or peripheral to computer device 10. In a networked system, accessible program modules or portions thereof can be stored in a remote memory storage device. Furthermore, in a networked system computer device 10 can participate in a distributed computing environment, where functions or tasks are performed by a plurality of networked computer devices.

Thus, it will be appreciate that embodiments can be practiced in a variety of different environments with many types of system configurations. Figure 2 provides a representative networked system configuration that can be used in association with some embodiments. The representative system of Figure 2 includes a computer device, illustrated as client 40, which is connected to one or more other computer devices (illustrated as client 42 and client 44) and one or more peripheral devices (illustrated as multifunctional peripheral (MFP) MFP 46) across network 38. While Figure 2 illustrates an embodiment that includes a client 40, two additional clients, client 42 and client 44, one peripheral device, MFP 46, and optionally a server 48, which can be a print server, connected to network 38, alternative embodiments include more or fewer clients, more than one peripheral device, no peripheral devices, no server 48, and/or more than one server 48 connected to network 38. Other embodiments include local, networked, or peer-to-peer environments where one or more computer devices can be connected to one or more local or remote peripheral devices. Moreover, embodiments also embrace a single electronic consumer device, wireless networked environments, and/or wide area networked environments, such as the Internet. Thus, it will be appreciate that certain embodiments can include a variety of different network system configurations.

Generally, the present systems and methods relate to private sale events.

Private, or invitation-only, sale events (or "private sales") allow a retail merchant (hereinafter "merchant") an avenue to provide select inventory at discount prices to only a discrete audience. These private sales enable merchants to periodically sell select products at a discounted price without having to discount their entire inventory. Thus, private sales can facilitate the sale of overstocked or undersold products at time when such products or product lines are current and in-season.

In another aspect, the present system allows merchants to offer selected inventory items for sale to a small group of consumers, rather than to the public at large. Furthermore, merchants using this system can direct general advertisements to a group of system users (herein "users" and including customer and merchant users) and receive consumer responses before these merchants are required to specify the details of a sale. In some configurations, this system allows merchants to customize a sale event for an indentified target group based on the responses the individuals of the group send along with demographic type data for individuals in the group.

The present systems and methods provides these features to merchants and consumers by providing a means whereby interested consumers can request that one or more merchants discount some or all of their inventory in a private sale event for them and possibly others of a small group. By allowing customers to request invitations (or make an 'invitation request") to private sale events, promotional expenses and materials can be significantly reduced on the part of the merchant. Such sales can be very beneficial to merchants, since such customers may generally have a higher level of interest than otherwise. This process can thus improve the efficiency and reduces the cost of advertising a private sale event.

To become involved with this system, a merchant need only become associated with the system, such as by registering as a member, paying a fee, and/or signing a membership agreement. Once the member is associated with the system, the member can invite system users (consumers) to request invitations to a private sale event. Thereafter, the merchant can periodically receive a notice of any users who have requested invitations. The merchant then need only plan a private sale event and send invitations the enlisted users. This process dramatically decreases the work and costs involved in advertising such events. Private sales can take place in-store or via the Internet.

A general example of the system in operation may illustrate the

aforementioned general features and benefits of the present system. Accordingly, a system user (user) can review a list of associated merchants to see if he/she is interested in the products of the merchants. If the user is interested in a certain merchant, the user can request an invitation to a private sale event hosted by that merchant. For instance, the request can indicate the desired location and date of the sale. The request can also specify the type of product the user is interest in purchasing and a number of friends or guests that the user would like to bring. This request can be sent to the merchant who can respond by extending an invitation for a private sales event to the customer and the customer's guests or friends or by declining or deferring the acceptance. Along with an invitation to a private sale event, the merchant retailer might also indicate specific products or price discounts for the private sale. On the planned date, the user and guests can attend the private sale event at the physical location of the event or at an online location

A more detailed description of the various embodiments of the present system is illustrated in the remaining figures. Referring now to Figure 3, according to some embodiments, the system includes a communications portal 50 (e.g. website 50, herein occasionally referred to merely as a "portal") through which consumers and merchants can access system services. As used herein, the term "portal" refers to a gateway, or communications portal, through which users can identify associated merchants and request an invitation from the associated merchants. In some embodiments, the communications portal could be implemented via one or more websites maintained by a system administrator. The portal can provide features including, but not limited to, data access and searching, categorization,

personalization options, data profiling, and application integration. In some configurations, the portal 50 is a network portal accessed via a computer network. In some particular configurations, the portal 50 is a website and the computer network is the Internet. As shown, the portal 50 can allow user to login, as discussed in detail below. In some instances, logging in requires a user to enter a predetermined username and password 52 in order to gain access some or all of the features and/or services of the portal 50.

In some embodiments, the portal 50 provides users with a service that allows them to review a set of associated merchants request an invitation to a private retail sale event from one or more merchants. For the purpose of explanation, the portal 50 includes information relating to only three retail merchants (Retail A, Retail B, and Retail C). In other instances, any number of merchants can be associated with the system and displayed on the portal, such as one, two, ten, fifty, one hundred, one thousand, or more. As illustrated, a user can access the portal 50 and review the listed associated merchants. In some configurations, the portal 50 provides the user with general or detailed information about the merchant, the merchant's inventory, and/or a link to the merchant's website or other network site. In some instances, the portal 50 has a separate network page for each merchant to which users can be directed to learn more about the merchant and the merchant's products.

As illustrated, the portal 50 allows users to request an invitation to a private retail sale event hosted by one or more associated merchants. In some embodiments, as shown, the portal provides an icon, link, or other device that a user can select to initiate an invitation request. As shown, such an icon can say "Request Invite" or something of that fashion. In some instances, an invitation request requires only a single-click. In these one-click configurations, the user can have a system account that stores user information and/or user preferences in order to facilitate a one-click invitation request.

Once, an invitation request is made, the request is communicated to the merchant. In some embodiments, these requests are communicated to the merchant via the portal 50, as illustrated in the embodiments of Figures 6-9. When the merchant receives communication relating to user requests, the merchant can respond by inviting the requesting users to a sale, denying the requests, sending invitations to future sales, or informing the requesting users that they are on a waiting list.

Merchants can respond in many other ways, as will be generally understood. This communication between merchants and requesting users can take place via the portal, via personal email, business email, telephone, fax, or physical mail.

In certain embodiments, the portal 50 facilitates all communication between merchants and requesting users. In some embodiments, users receive merchant's messages in a user account associate with the portal 50. In some embodiments, the portal 50 updates the status of the user's invitation request(s) on a user interface within the portal 50. Such status updates can indicate that an invitation request has been made, processed, received, accepted, etc. Further status updates on the portal can indicate that an invitation has been extended, declined, or placed on hold or on a waiting list.

Referring now to Figure 4, which illustrates a method 60 that can be practiced, at least in part by the portal 50 to facilitating private retail sale events. As shown, the method 60 involves establishing a set of associated merchants 62. A set of associated merchants refers to the collection of merchants who have agreed to be associated with the system and host, on occasion, a private retail sale event. While this step can be ongoing, an initial set of at least two merchants is preferred to provide an attractive system to consumers. In some instances, a merchant must register as a merchant, and or pay a fee prior to being associated with the system and displayed on the portal 50.

In some embodiments, merchants are divided into categories, so that portal 50 can present merchants to users in categories or allow users to search for merchants of particular categories. Categories can include the type of products sold by the merchant, the location of the merchant, etc. Categories can also separate merchants based on the frequency or number of private sales events the merchant hosts or intends to host. Additionally, some merchants can be distinguished by being included in a category for preferred merchants.

As a set of associated merchants is established 62, a communication portal (portal) facilitates private invitations hosted by the set of merchants 64 for system users 64. As illustrated in Figure 3 and mentioned above, the portal can provide one or more means whereby a user can make an invitation request. In some instances, as also mentioned, the portal publishes information about the merchants and allows users to browse and/or search this information. In some configurations, one or more databases stores merchant information, which can be searched via portal search features, such as a search engine. In some embodiments, the search engine accepts a search criteria, searches the database, and returns one or more merchant listings. The search criteria can utilize merchant information received and or categorized to enable users to search for, product types, merchants having upcoming private sales, dates of private upcoming sales, brands, price ranges, stores location, online private sales options, etc. Furthermore, using stored merchant information, the portal can allow users to browse products of a certain type from multiple merchants and compare these products.

In some embodiments, all or portions of the portal can only be accessed by authorized users. Thus, methods can be provided for performing user authentication and authorization. In one implementation, user authentication can be performed via logon passwords. For example, in some embodiments, a user can register using an assigned or self-declared password. In some embodiments, a user is required to pay a registration, subscription, or membership fee to become authorized with authorized login information. In some embodiments, this fee is a one-time fee. In other embodiments, the fee is a periodic fee, such a monthly or yearly fee.

Upon successful authentication, a user can be authorized to access information via the portal. According to some embodiments, the system provides varying levels of access restrictions. Thus, the system can provide user access to various features and portions of the portal based on the user's access authorization level. Thus, in some embodiment, a user can pay to have or can be assigned a certain authorization level. In some embodiments, a user can pay a fee to have a higher authorization level. For example, a user can pay to become a preferred customer. In some embodiment, users are assigned higher authorization levels based on a given set of requirements, such as purchase requirements.

Thus, according to some embodiments, authorization levels determine which users can access which portions of the portal. In some instances, authorized users are granted the first opportunity to request invitations to private sales, while unauthorized users are only granted access if availability remains. In other instances, only authorized users can make invitation requests. In some instances, invitations to specific sale events can only be request by users having a certain authorization level. In other instances, user authorization levels gives high level users priority over lower level users when private sales events are limited to a finite number of users. In some embodiments, a user's authorization can limit the number of requests a user can make in a given period. Some user authorization levels can allow a user to make an unlimited number of invitation requests.

In some embodiments, the portal could be configured as an internet website, accessible by the public. As such, certain portions of the portal can be restricted to authorized users, while other portions can be accessible to the public. In other embodiments, invitation requests can be purchased in a pay-per-invitation fashion, enabling all users to access portal content and make invitations request, contingent upon the payment for each request.

As illustrated in step 66 of Figure 4, some embodiments include receiving a user request for an invitation to a private retail sale hosted by a particular merchant. In some embodiments, prior to processing the request, the method 60 verifies whether the user is authorized to make the request. In some configurations, the user request is receiving by the system and stored in a memory device. In some embodiment, the system includes a compiling mechanism that compiles a list of all users who have made a request to receive an invitation to a private sale event from a particular store. This list is then transferred to the merchant, who can respond to it by extending invitations to some or all of the listed users. In some embodiments, the compiling mechanism includes a processor.

Consistent with principles of some embodiments, receiving a user request can further involve associating user information with the user request. Because the merchant will need to communicate an invitation to the user, the merchant can receive information about the user in order to contact the user. For instance, the merchant can receive the phone number, contact address, email address, or a username of those requesting an invitation. Accordingly, in some embodiments, this information is received or stored along with the user request.

In some configurations, the system enables a user to request an invitation from a specific merchant for specific products or product types. Additionally, the portal can allow a user to make an invitation request to all merchants carrying a particular type of inventory.

As illustrated in step 66 of Figure 4, some embodiments include transferring the user's request to the merchant. These requests can be mailed, e-mailed, faxed, or otherwise transferred. According to some embodiment, these requests are transferred to a merchant's account interface, as discussed below.

In some embodiments, the method 60 include additional steps. For instance, the method 60 can include the step of communicating an invitation for a private sale event hosted by a specific merchant from the merchant to the user via the

communications portal. Additionally, the method 60 can include communicating an RSVP message from the user to the merchant via the communications portal. Further, the method 60 can include communicating an access mechanism for a private sale event from the merchant to the user via the communications portal. An access mechanism for a private sale event is an item or information that grants the user access to a sale event. For example, an access mechanism can be a password, a code, a ticket, a certificate, a digital certificate, or device, material, or information that the user needs to access and enter an in-store or online private sale event.

Referring now to Figure 5, which illustrates a block diagram of the system for facilitating private sale events. As illustrated, a user 70 using a user terminal 72 can access the portal 74. Through the portal 72, the user 70 can see what merchants are associated with the portal 74 and access the portal features discussed above. In some embodiments, the user can see what products the merchant sale via the portal. Some merchants, for instance associated merchants A 76 and B 78 are not in electronic communication with the portal 74. Rather, these merchants have merely associated themselves with the portal 74 and have indicated that they will host a private sale to requesting users. In some embodiments, communication to these merchants is not via the portal, but via telephone, email, mail, and the like.

As further illustrated, merchants can also be in electronic communication to the portal. This communication link can include a merchant terminal 82 coupled to a communications network, such as the Internet. In some embodiments, via the network connection, the portal 74 can direct user network traffic to a merchant website, when users are interested in further information about the merchant. Such a website may be located on a merchant terminal 82. In other embodiment, the portal 74 can provide a gateway to a merchant private sale via the merchant website located on the merchant terminal 82. Via this electronic connection, a merchant can modify information associated with the merchant that is presented on the portal. For instance, the merchant can update product information, sales information, etc. In addition, as discussed above, the merchant can receive invitation requests via the portal, prepare and send invitations, receive RSVP messages (messages whereby the user replies to the invitation to indicate whether or not they will be attending the private sale event), and prepare and send tickets to private retail sales events.

Accordingly, via the system and method, a customer can request an invitation to a private retail sale event and thereby have insider access to discounted products while these products are current. Merchant also benefit from the method and system by receiving a list of interested purchasers who can purchase excess inventory while the inventory is current and can be sold at a higher price. Figures 6-9 illustrate portions of or complete screen shots of some embodiments of the portal discussed above. These embodiments illustrate the portal as a website. Figure 6 depicts a screen shot of user account interface according to some embodiments of the portal. Generally, a user account interface displays information relating a specific user, including user name, account preferences, account type, etc. In some instances, a user profile, account activity, and account history is displayed in the user account interface. In some embodiments, the user account interface displays messages from merchants, advertisements, and/or the status of invitation requests. In some embodiments, portal is configured to store the number and the date of invitation requests a user has submitted. In some embodiment, the user's account interface publishes the number of requests the user has made and/or has outstanding.

In some embodiments, a user account interface includes a wish list of list of favorite merchants. A wish list can allows the user to request a notification message if the merchant indicates that it will host a private sale event in the near future. This feature would allow a user to postpone requesting an invitation until the user knows when the details of the private sale event. In some embodiments, the action of adding a merchant to a user wish list places the user on a waiting list. In the instance that the selected merchant announces a private sale or begins allowing invitation requests, the user on the waiting list has priority for receiving an invitation over users not on the waiting list.

Referring again to Figure 6, as depicted the portal includes a plurality of tabs at the top of the interface that a user can select. As illustrated, the tab relating to a user account interface is selected, and is called "MYPAGE" 92. Other tabs can be selected to bring up additional interfaces, including "STORES&PLACES" 94 and

"PRJVATELIST" 96, Within the "MYPAGE" 92 tab additional tabs are depicted that can be selected, including "CHOOSESTORES," "MYSTORES" 100,

"FAVORITEITEMS," "MY ACCOUNT," and "INVITEFRIENDS." In some embodiments, the interface can display status information 98, which informs the user about expiring offers or upcoming sales for which the user plans to attend.

Additionally, the interface can display other status information, such as the number of requested invitations, the number of invitation requests remaining, and other such information.

In Figure 6, the "MYSTORES" tab 100 is depicted as selected. Because the MYSTORES tab 100 is selected, the interface depicts information about stores user is interested in on the bottom left portion 102 of the portal. As depicted, the user has indicated that she is interested in Bloomindales (TM) and Cole Haan (TM). In some embodiments, the MYSTORES tab 100 includes information about stores or merchants from which the user has requested an invitation. Thus, if a user submits an invitation requests from a merchant, that merchant can be added to the list of stores in the user's MYSTORES tab 100. Accordingly, in some embodiments, an RSVP icon 104, as depicted, is included in the information about each store MYSTORES tab. The RSVP icon 104 allows a user to send and RSVP notice to the merchant, indicating that the user plans to attend the store's private sale. In some embodiments, the portal displays information in the MYSTORES tab 100 about each of the selected stores. This information can include information about upcoming sales that the user has requested an invitation to. In some embodiments, the MYSTORES tab 100 only displays information about the user's selected stores if that store is hosting a private sale for which the user can RSVP.

As discussed, various tabs can be included in the user's account interface.

These tabs can allow the user to identify items or products the user wants. If a merchant is offering a sale of the indicated items, the interface can notify to the user of such and a suggesting that the user request an invitation to the merchant's sale. In some embodiments, a tab can include a wish list interface, as discussed above. The MYACCOU T tab can provide the user with an interface through with the user can change her contact information, her account preferences, pay a membership free, upgrade to a different membership status, and send and receive messages from users, merchants, or system manager. The I VITEFRIENDS tab can provide the user with an interface through which the user can send an invitation to a friend to join the system or request an invitation to a sale. This tab can also allow a user to invite a friend as a guest to a private retail sale event that the user is invited to.

Figure 6 depicts a personal sale interface 90 in the portal through which a user can "request a personal sale," or request an invitation to a private retail sale event. In some embodiments, the personal sale interface is provided to users via a user account interface, as depicted. Thus, in some embodiments, a user is required to login to the personal sale interface in order to have access to this personal sale interface 90 and request a personal sale. In other embodiments, the personal sale interface 90 is provided to users outside of a user account interface.

Figure 7 depicts an enlarged version of the personal sale interface 90. Via this interface, a user can request an invitation to a private retail sales event. Various interface embodiments can be utilized wherein a user can request such an invitation, Figure 7 depicts an interface as an example embodiment. As depicted, the user first chooses the place (or merchant) where the user would like a private sale or benefit. The user is presented with a drop down menu from which the user can select a merchant from the list of associated merchants. Next, in some embodiments, the user selects whether they prefer to shop online or in a store. Next, the user selects a date or a date range indicating when they would like to attend a private sale from that merchant. In some embodiments, the user can select a date or date range from a calendar interface, as illustrated. In some embodiments, a user can request an invitation for themselves and a number of guests. Accordingly, as depicted the personal sale interface 90 provides the user with a drop down menu from which the user selects the number of guests the user intends to bring. In other embodiments, the user can input a number representing the number of guests the user intends to bring. In some embodiments, the user is provided a comment box for typing comments to the merchant.

Figure 8 depicts a screen shot of user account interface for a merchant according to some embodiments of the portal. Via the merchant user account interface, the merchant users can receive invitation requests. Via this accounts interface the merchant user can create and edit a profile that is presented to via the portal to all users. In addition, via this accounts interface the merchant user can submit an announcement of an upcoming private retail sale event to which users can request an invitation.

In some embodiments, a merchant user account interface allows merchants to prepare and send tickets to private sales via the portal. These tickets can be printed by a user at home and brought to a sale location. In some embodiments, the private retail sale event is an online sales event. In these instances, the ticket can include a password, code, or hyperlink that the user uses to access special sale prices available online. In some embodiments, online sales events are administered via the merchant's online website. In some embodiments, online sales events are administered via the portal. In these instances, the portal includes a separate portal wherein a user can view sale items and purchase them at sale prices via the portal.

As depicted in Figure 8, in some embodiments, the merchant account page can be distinct from the user account page. In particular, the merchant account page can provide the merchant user with merchant specific tabs, such as

"MYFEATUREPAGE" 106, "MYINVITATIONS" 108, and "PERSONALSALES" 110, and "REVIEW&POST." In other embodiments, other tabs can be provided to merchant users. In other embodiments, icons or links are presented instead of tabs. In other embodiment, no tabs are present; rather a single interface allows the merchant to perform all the interface functions therein. In some embodiments, via this merchant account interface the merchant can receive user invitation requests, create and send requesting users an invitation, and provide information about upcoming sales that is published via the portal to customer user.

Figure 8 depicts a merchant account interface that displays information about requests for private (or personal) sales. As depicted, the interface displays the number of requests that have been made by users for specific days. In other embodiments, the interface can display the number of requests that have been made by users for specific months or specific weeks. As depicted, the interface provides a user with a link to "See Details" of the requests. Figure 9 depicts a merchant account interface that is displaying the details about the requests pertaining to a certain week. In some embodiments, the merchant is presented with information relating to each invitation request. This information can include the number of guests a user intends to bring, the date of the request, and any other information included on the request, including, for example, username, name, user comments, user locations, preferred sales location, preferred products, preferred sizes, preferred colors, etc. In other embodiments, the merchant is merely provided with the number of individuals requesting an invitation. In some embodiments, the merchant can be provided with information about the requesting users. This information can include username, age, gender, product preferences, spending preferences, spending habits, and contact information.

Once the merchant is presented with one or more user request the merchant can extend an invitation to a private retail sale event, wait to host a sale, send an invitation for a later date, or deny the request. In some embodiments, a merchant is provided with an interface that allows the merchant to reply to the request by indicating to the requesting user that the merchant plans to host a sale at a future date. In some embodiments, the merchant can put the user on a waiting list that provides the user with preferential status for the future sale. As depicted, in some

embodiments, a merchant user interface allows the merchant to merely accept or deny the invitation request by selecting a "accept" 1 14 or "deny" icon. In other embodiments, the merchant user interface allows the merchant to select the date of the private retail sale and send an invitation to the requesting users for a sale on that particular date. This allows the user to accept the date submitted by requesting users as suggestions.

Accordingly, the present method and system for facilitating an invitation to a private retail sale event provides a system and method that benefits both customer and merchant users. Customers receive the benefits of easy access to private retail sales. Merchants also benefit by reducing marketing and planning costs related to private sales. Furthermore, since private sales are offered to a limited set of customers, merchants can sell a limited quantity of current products without having to discount an entire product line.

The present invention can be embodied in other specific forms without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims, rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

What is claimed is:

Claims

1. A method for facilitating private sale events comprising:

establishing a plurality of associated merchants;

providing a communications portal displaying information relating to at least some of the plurality of associated merchants;

allowing, via the communications portal, a user to request an invitation to a private sale event hosted by a specific merchant of the plurality of associated retail merchants; and

communicating the user's request to the specific merchant.

2. The method of claim 1, further comprising communicating an invitation for a private sale event hosted by a specific merchant from the merchant to the user via the communications portal.

3. The method of claim 2, further comprising communicating an RSVP message from the user to the merchant via the communications portal.

4. The method of claim 3, further comprising communicating an access mechanism for a private sale event from the merchant to the user via the

communications portal.

5. The method of claim 1, further comprising communicating to the user via the communications portal that the user's request for an invitation has been placed on a waiting list.

6. The method of claim 1, wherein the communications portal includes an internet website.

7. The method of claim 1, wherein the method further comprises authenticating the user as a subscribing user.

8. The method of claim 7, wherein allowing a user to request an invitation includes verifying that the user is authorized to make the request and allowing the request if the user is authorized.

9. The method of claim 1, further comprising storage information associated with the user, and wherein communicating the user's request to the specific merchant further includes transferring stored information associated with the user to the specific merchant.

10. The method of claim 9, wherein the information associated with the user includes at least one of a username, gender, and age.

11. The method of claim 1, wherein in the private retail sales event is an in-store sales event or an online sales event.

12. A system for facilitating private sale events, the system comprising: a storage device for storing information associated with a plurality of associated merchants and information associated with a plurality of network users; a communications portal through which information relating to the merchants of the plurality of associated merchants is displayed and through which a network user can request an invitation to a private sale event hosted by at least one of the plurality of associated merchants;

a compiling mechanism coupled to the communications portal and the storage device for compiling and presenting to each merchant a list of network users who requested an invitation to a private sale event hosted by that particular merchant.

13. The system of claim 12, wherein the storage device is a database.

14. The system of claim 12, wherein the communications portal is an internet website.

15. The system of claim 12, wherein the communications portal transfers invitations for private sale events from merchants to users.

16. The system of claim 15, wherein the communications portal transfers RSVP information from users to merchants.

17. A computer-readable medium containing instructions for controlling a computer system coupled to a network to perform a method, the computer system having a display device, and input device, and a processor for executing the instructions, the method comprising the steps of:

presenting, via the display device, a communications portal through which a merchant publishes information relating to the retail merchant and a user accesses the published information;

receiving at least one command from the user to submit a request to the merchant for an invitation to a private sale event; and

communicating the submitted request to the merchant.

18. The computer-readable medium of claim 17, further comprising

communicating an invitation for the private sale event to the user via the

communications portal.

19. The computer-readable medium of claim 18, further comprising

communicating an RSVP message to the merchant via the communications portal.

20. The computer-readable medium of claim 17, further comprising storage user information and communicating stored user information to the merchant with the submitted request.

21. The computer-readable medium of claim 17 further comprises authenticating the user as a subscribing user prior to receiving at least one command from the user to submit a request to the merchant.