WO2001093059A1

WO2001093059A1 - Interactive communication network system

Info

Publication number: WO2001093059A1
Application number: PCT/US2000/015456
Authority: WO
Inventors: Jason S. Flegel; Melissa L. Harmon; S. Leslie Flegel; Dwight L. Degolia
Original assignee: The Source Company
Priority date: 2000-05-30
Filing date: 2000-05-30
Publication date: 2001-12-06
Also published as: AU2000253234A1

Abstract

A computer network-enabled database which provides an interactive communication network system (2) for communications among multiple remote users. Generally the system comprises a database managed with a plurality of data managers (20, 22, 24) to provide several services to the remote users. In one embodiment, the data managers include a data manager (22) for consolidated reporting of sales data on a plurality of products. In one embodiment, the system is directed toward use by different types of remote users involved in the same or related businesses, such as publisher, retailers, wholesalers, and distributors involved in the sale and distribution of periodicals, or those who manufacture, distribute or sell other merchandise such as confections and general merchandise.

Description

INTERACTIVE COMMUNICATION NETWORK SYSTEM

CROSS-REFERENCE TO RELATED APPLICATIONS

A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

BACKGROUND OF THE INVENTION This invention relates generally to computer network-based electronic communications systems and more particularly, to a network-enabled database for the interactive exchange and maintenance of commercial data for business users.

Communications among business people is a fundamental aspect of commercial activity. The extent and type of information being exchanged between individuals depends in large measure on the business relationship between them. For example, a product manufacturer might wish to know how sales of the manufacturer's own products are doing in all the stores of a particular retailer, or in one particular store. A retailer might need to know how sales of a particular product are doing in a specific store. Retailers also need to update the electronic databases which store the Umversal Price Codes (UPC) or bar codes for items sold by the retailer. Despite the availability of computer network-based communications systems, the efficient and rapid exchange of such specific information remains a problem. Typically, business people must request specific information from those with whom they deal, or else generate the information themselves using, for example, analysis by personal computing software. Useful information is often simply lost or never obtained because of the burden in generating or otherwise obtaining the information. This results in gaps in communications, or inefficiencies of communications where the same mformation is being regenerated and communicated over and over again among different individuals . It would therefore be desirable to provide a system for consolidating the exchange and maintenance of commercial data among business people. It would also be desirable to provide such a system which is directed toward a particular type of business. It would be further desirable to provide such a system using a network-based system so that the data can be consolidated at one easily accessible site. It would be still further desirable to provide such a system which accesses and utilizes the data to pro.vide commercial services to trading partners. It would be yet still further desirable to provide such a system which provides information which dynamically responds to the specific needs of an individual remote user of the system.

BRIEF SUMMARY OF THE INVENTION

These and other objects may be attained by an interactive communication network system which in one embodiment is implemented through a network- enabled computerized database. The network is, for example, the World Wide Web, referred to herein as the Web. The network hardware includes, for example, a central server computer at a central site, and at least one remote terminal comiected to the central server. A database is installed on the central server, which provides an interactive, dynamic Web site which utilizes database functions to maintain and organize the Web site. The system thus provides an interactive and dynamically responsive information hub for providing commercial services to multiple remote users with different but related information needs.

In one embodiment, the interactive communication network system central server includes at least one database having data representing specific product information and individual remote user profiles . A portion of the data is collected from various external sources, including the remote users themselves, and a portion of the data is internally generated from the data collected from the external sources. The data includes, for example, UPC information for specific products, sales information on specific products or categories of products, and specific sales data from individual remote users.

The system also includes multiple data managers for organizing and managing the database. In one embodiment, the system includes three data managers and is generally directed towards users involved with the publishing, distribution or sales of periodicals and related products. A first data manager is configured to automatically retrieve and store downloaded information from an external information clearing house. A second data manager is configured to provide a remote user with access to updated product UPC codes and other updated product information through an interactive communications network (ICN). A third data manager is configured to provide consolidated reporting of sales data on periodicals through a periodical information network (PIN). In alternate embodiments, the system includes additional data managers directed toward other functions.

The above-described interactive communication network system provides an interactive, dynamic Web site consolidating the exchange and maintenance of commercial data among business people. The system provides a range of commercial services at one conveniently accessible and user-friendly site. Utilizing the database, remote users accessing the Web site may exchange and update a range of commercially relevant and up-to-date data. Further, the dynamic aspects of the database allow individual remote users to obtain updated information tailored to their own business needs.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 is a schematic diagram illustrating a general relationship among elements of an interactive communication network system. Figure 2 is a schematic diagram showing the data files included in a first data manager in the system (IPDA).

Figure 3 is a schematic diagram showing the data files included in a second data manager in the system (ICN). Figure 4 a schematic diagram showing the data files included in a third data manager in the system (PIN).

Figure 5 is a first login page in the system.

Figure 6 is a second view of the login page.

Figure 7 is an introductory page in the system. Figure 8 is a world item file page in the system.

Figure 9 is a titles page in the system.

Figure 10 is a bipad page in the system.

Figure 11 is a UPC information page in the system.

Figure 12 is an add authorized list page in the system. Figure 13 is an authorized list page in the system.

Figure 14 is an authorized list title detail page in the system.

Figure 15 is an update authorized list page in the system.

Figure 16 is an authorized list UPC information page

Figure 17 is a new title/special promotion page in the system. Figure 18 is a new products page in the system.

Figure 19 is a magazine cover information page in the system.

Figure 20 is a UPC updates page in the system.

Figure 21 is a communication page in the system.

Figure 22 is a publisher home page in the system. Figure 23 is a publisher world title list search page in the system.

Figure 24 is an authorized chain list page in the system.

Figure 25 is a chain selection page in the system.

Figure 26 is a retailer authorized list page in the system.

Figure 27 is a publisher new title/promotions page in the system. Figure 28 is a second view of the publisher new title/promotions page.

Figure 29 is a third view of the publisher new title/promotions page.

Figure 30 is a fourth view of the publisher new title/promotions page.

Figure 31 is a publisher communications page in the system. Figure 32 is a year/quarter selection in a periodical information network

(PIN).

Figure 33 is a main menu page in the PIN.

Figure 34 is a global/class of trade report menu page in the PIN.

Figure 35 is a global title report page in the PIN. Figure 36 is a class of trade title report page in the PIN.

Figure 37 is a chain specific report menu page in the PIN.

Figure 38 is second view of the chain specific report menu page.

Figure 39 is a category analysis page in the PIN.

Figure 40 is a chain specific title report page in the PIN. Figure 41 is a chain specific top 200 titles report page in the PIN.

Figure 42 is a chain specific schematic page in the PIN.

Figure 43 is a chain specific pockets per bipad report page in the PIN.

Figure 44 is a chain specific store list report page in the PIN.

Figure 45 is a chain name report page in the PIN. Figure 46 is a first client profile page in a fourth data manager in the system.

Figure 47 is a second client profile page in the fourth data manager.

Figure 48 is a first category manager page in the fourth data manager.

Figure 49 is a second category manager page in the fourth data manager. Figure 50 is a first plan manager page in the fourth data manager.

Figure 51 is a second plan manager page in the fourth data manager.

Figure 52 is a second view of the second plan manager page.

Figure 53 is a third view of the second plan manager page.

Figure 54 is a profit picture page in the fourth data manager. DET AILED DESCRIPTION OF THE INVENTION

The interactive communication network system includes at least one network- or Web-enabled database for providing dynamic network communications. In one embodiment, the system is directed toward use by individuals who publish, market, distribute and sell periodicals such as magazines . The users include, for example, chain and independent retailers, publishers, national distributors, local distributors, wholesalers, local suppliers, and consumers. However, as will be apparent to those skilled in the art of building Web-enabled databases, the services are readily adaptable for use by individuals involved in almost any type of business, including manufacturers and retailers of substantially any type of product including, for example, confections and general merchandise.

Generally, the system is directed toward dynamic interactive communication of data among multiple remote users by combining database technology with distributed computer network communication. The system is implemented with known computer network hardware including a central server on which a central relational database is installed. The system further includes an application server which allows the database to be manipulated in response to HTML commands from remote users accessing the database over the network. The system allows multiple users to access and update the centralized database, which is thus dynamically updated through various inputs, including remote user input. The term dynamic refers to the capability of the the system to immediately update the database in response to the external inputs. Thus, the system provides a centralized and highly current source of information for multiple remote users having different but related information needs.

Generally, the interactive communication network system is practiced over a distributed computer network. The term Web as used herein refers to the distributed computer network also known as the World Wide Web. The term page as used herein refers to a document composed in Hyper Text Mark-up Language (HTML) which communicates information over the Web or other network from a computer server at the central site to a remote computer terminal used by the customer. Although the exemplary system described herein is implemented on the Web, it should be understood that the present invention may be implemented on many other distributed computer networks.

In one embodiment of the interactive communication network system, the location of a page on the Web is specified by a uniform resource locator (URL), which is an alphanumeric string representing the server address on the Web. At the remote computer terminal, a remote user initially accesses a page by typing a specified URL into a Web-browser such as Netscape™ by Netscape Communications Corporation, or Internet Explorer™ by Microsoft Corporation. Multiple pages at a Web site are linked together via hyperlinks which are represented on a computer screen by a graphical icon such as a button or a highlighted line of text. Hyperlinks are configured to implicitly invoke another URL when a computer user clicks on a computer mouse button while a mouse- controlled screen cursor is positioned over a hyperlink icon. As explained in more detail below, HTML pages in the system are further linked to the database in the system through an application server. The application server links HTML commands from the remote user to the database, and database functions are used to access and manipulate the data to provide services to the remote user.

Figure 1 is a schematic illustration of interactive communication network system 2 which, in one embodiment, is implemented with readily available computer network hardware including a central server 4, at least one remote terminal 6, and a central terminal 8. Central server 4 is, for example, a desktop computer having stored in memory (not shown) at least one database for storing data. Generally, the stored data relates to sales of specific products, categories of products, or to a group of product types, and data relating to individual remote users, and is gathered or generated as described below. In one embodiment, the data in the database is stored and organized among multiple data managers as described in more detail below, and each data manager includes multiple database files for further structuring the data. Terminals 6 and 8 are, for example, personal computers such as those available from International Business Machines, linked together in a computer system through which several users communicate using multiple terminals, or another type of intelligent interface device. In one embodiment, terminals 6 and 8 each have a conventional video monitor (not shown) as an output device, and a keyboard (not shown) and a computer mouse (not shown) as input devices. A Web-browser is installed on terminal 6. Terminal 6 communicates with server 4 via a telecommunications device such as a conventional phone line 10 linked to terminal 6 through a modem (not shown). Alternatively, the telecommunications device is a dedicated network cable, a cable-free cellular digital packet transfer device, or other known remote data transfer system such as, for example, a satellite link.

In one embodiment, the database is of the desktop relational type and is adapted for use by multiple simultaneous users. One suitable desktop database is, for example, Microsoft's Foxpro which runs under Windows, Mac or DOS. However, dozens of other desktop databases are readily commercially available and suitable for implementing the interactive communication network system. In an alternative embodiment, the databases are computationally more powerful and adapted for use by thousands to hundreds of thousands of simultaneous users. One example of such an enterprise database is Oracle, available from Oracle Corp., which runs under UNIX, Windows or WindowsNT.

The system further includes an application server (not shown) for accessing and manipulating data in the database in response to HTML commands entered by the remote user on a Web page. The application server is, for example, a tool such as Web Connects from WestWind Corp. of Paia, Hawaii, or Cold Fusion from Allaire Corp. of Cambridge , Massachusetts. However, other products may be used. Through the application server, the database responds to HTML commands by using corresponding database functions to query the data so that the appropriate information is transmitted and displayed on the remote user's output device.

The data is supplied by various sources. For example, some information such as product UPC information is provided by an information clearing house which regularly collects and updates the information which is downloaded regularly, for example daily or weekly, into a download terminal 12 as described below. Other information is collected from the remote users themselves and entered into an adjunct server 14 by system administrators as described below. For example, and as will be described in more detail below, sales data for specific periodicals is regularly collected from retailers and wholesalers by system administrators. Also, publishers occasionally volunteer information on newly available periodicals, and retailers submit information regarding which new titles they want to sell. In addition, the data generally includes user profile information for each remote user and each business customer using the system. Some of the data, such as product UPC information, are subject to regular daily updating by system administrators as explained above. Other data, such as new periodical titles available from a publisher, are updated only upon request by a remote user.

In one embodiment and as shown in Figure 1 , system 2 includes three data managers, 20, 22, and 24, for managing the data stored in the database. In an exemplary embodiment, data manager 20 resides in download terminal 12 and is structured to retrieve and store downloaded data from an external source for use by data manager 22. The remaining data managers 22 and 24 reside in central server 4 and are each structured to provide a different type of function or service for the remote user. In one embodiment, these services include interactive communications through a network (ICN) 22, and communication of regularly updated information on periodicals through a periodical information network (PIN) 24. Generally, data managers 22 and 24 respond to HTML commands from the remote user, through the application server, to access and analyze different classes of data stored in the databases. In alternative embodiments, additional data managers are included to provide additional functions or services. For example, in an alternative embodiment system 2 further includes a fourth data manager (not shown in Figure 1) which uses sales data provided to the database by the retailers and wholesalers, to analyze product displays for the most profitable placement of products on a display fixture. In addition, those skilled in the art of database structuring and management will recognize that there are many alternative ways to structure any of the data managers as described below. The system as described herein is therefore not intended to be limited to specific data files or structures. Figure 2 is a schematic illustration of the data file layout of one embodiment of data manager 20. In this exemplary embodiment, data manager 20 is identified with the acronym of a professional association known as the International Periodicals Distributors Association (IPDA), which functions as the central information clearing house to collect and provide updated UPC information on periodicals. Generally, data manager 20 runs around the clock and dials in to a computer system (not shown) at the central clearing house every 24 hours to download into data manager 20 all updated UPC information. The updated information is regularly (usually daily or weekly) provided to the clearing house system by users of that system, such as publishers and national periodicals distributors.

Figure 2 shows one embodiment of data manager 20 which includes twenty-six data files . A portion of the files store downloaded clearing house data or data generated from downloaded data. Other data files are copies of data files from data manager 22. More specifically, and in one embodiment, data manager 20 includes an authorized list file 26, a title file 28, a chain file 30, a bipad trans file 32, a retailer file 34, an LPDA in file 36, an IPDA configuration file 38, an IPDA log file 40, an IPDA full file 42, an IPDA history file 44, a chain authorized history file 46, a chain update authorized list file 48, a chain UPC update history file 50, a chain update UPC file 52, a distributor authorized history file 54, a distributor update authorized list file 56, a distributor UPC update history file 60, a distributor update UPC file 62, a publisher UPC update history file 64, a publisher update UPC file 66, a UPC update file 68, a UPC not in IPDA file 70, a UPC error file 72, a UPC active file 74, an authorized list update file 76, and an authorized list complete file 78.

As explained above, some of the data are downloaded, or generated from downloaded data, and other data are copies of data, in the form of data files, from data manager 22. For example, authorized list file 26, title file 28, chain file 30, and retailer file 34 are each tables of data pulled from data manager 22 and are described in detail below. In one embodiment, data manager 20 includes bipad trans file 32, which stores in one file all of several bipads identifying a single title. For example, bipad trans file 32 is included when a title such as TV Guide™, which is identified by several bipads, is included in system 2. IPDA in file 36 is received as downloaded data from the central clearing house. IPDA in file 36 includes separate records for each periodical , each record having fields for storing information such as the bipad code, title, category, cover price, issues per year, UPC code, and the like. IPDA configuration file 38 stores a dialing script for dialing into the IPDA central clearing house. For example, the script contains fields for storing the phone number, modem baud rate, etc. IPDA log file 40 is the log file for the IPDA dial-in and download. IPDA full file 42 stores substantially the same information as IPDA in file 36, but for the previous date of download. Similarly, IPDA history file 44 stores substantially the same information as IPDA full file 42, but also includes fields for storing whether there has been any change in any of the fields when the two latest data batches are compared as described below. Chain authorized history file 46 stores all authorized list update records, i.e. historical data on the authorized list. Chain update authorized list file 48 is a compiled authorized list table of all the most currently authorized titles in the authorized list. File 48 is used to compare with an updated authorized list which is dynamically generated when the remote user adds or deletes titles from the authorized list as described below. Chain UPC update file 52 stores chain remote users' current UPC updates, while chain UPC update history file 50 stores past UPC update files by chain so that the two can be compared to reveal what, if any UPC changes have recently been made. Distributor authorized history file 54 stores substantially the same data as chain, authorized list history file 46 but for national distributors instead of retail chains. Likewise, files 56, 60, and 62 store substantially the same information as, respectively, files 48, 50, 52, but for national distributors instead of chain retailers. Similarly, files 64 and 66 store substantially the same information as files 50 and 52, but for publishers instead of chain retailers. UPC update file 68 is a table storing separate records for each periodical updated over a specified period, each record having fields for storing the UPC code, title, cover price, bipad, and the like. UPC not in IPDA file 70 is a table with separate records for each periodical which is on the authorized list but does not have any record stored in IPDA full file 42, each record storing the bipad code and title of the periodical. UPC error file 72 stores the bipad code, UPC code, title, cover price, and the like for each periodical subject to a UPC update with errors. UPC active file 74 stores UPC information for each title, each record storing the UPC code, title, cover price, bipad, and the like. Authorized list update file 76 generally stores update records including entries for storing the retailer ' s chain identification number, the title, bipad code, the date the title was added to the authorized list, status codes, user access codes, and the like. Similarly, authorized list complete file 78 stores a complete, updated authorized list, similar to authorized list file 26.

More specifically, and for example, IPDA in file 36 is created when data manager 20 dials in to the clearing house system. The first record in file 36 represents the entire record received from the central clearing house system, stored as characters. In one embodiment, an additional twenty-one character fields in file 36 separately store the information which includes, for example, the date the download was done from the central clearing house, UPC code, cover price, bipad code, issue and year, title, periodical category, country, and the like. The data from file 36 is then compared to the previous batch of records, as determined from the date of download, which is stored in a data file 42, the IPDA full file. Data manager 20 runs several comparisons between the two batches of data to determine if changes have been made, and if so, whether the changes are valid. More specifically, data manager 20 looks for new information, changed information and deleted information. Once data manager 20 has validated the new information, a new record is added to file 42 and also, along with the batch date, to IPDA history file 44. Retailer file 34 is a copy of a file from data manager 22 and includes information provided by a remote user who is a retailer, such as the retailer's choice of which day or days of the week the UPC update files should be updated. Chain UPC update file 52, UPC not in IPDA file 70, UPC error file 72, and UPC active file 74 are updated with the correct information according to the retailer choices indicated in retailer file 34. Data from files 52, 70, 72 and 74 are then used to generate files in data manager 22 for downloading by the remote user through the Web site.

Figure 3 is a schematic illustration of the structure of data manager 22, the interactive communications network (ICN). More specifically, and in one embodiment, data manager 22 includes eighteen databases, some of which store data provided by the remote user, and some of which are copies of files from data managers 20 and 24. In an exemplary embodiment, data manager 22 includes the following files generated from remote user input through an HTML page: an authorized list file 80, a distribution file 82, a magazine cover file 84, a name file 86, a password file 88, the retailer file 34 (as explained above), a wholesaler file 90, a category file 92, a product history file 94, a product file 96, a title file 98, a wholesaler name file 100, a chain file 102, a PIN global file 104, a PIN class of trade file 106, and a PIN chain title file 108, IPDA full file 42 and IPDA history file 44. The PIN filesl04, 106 and 108 are copies of files originally generated in PIN data manager 24 as described below. IPDA full file 42 and IPDA history file 44 are copies of the same files from data manager 20.

Authorized list file 80 is a table including separate records for each title which a retailer remote user has identified as a title he sells or wants to sell. Each record includes, for example, fields for storing a chain (i.e. retailer) identification number, a bipad code unique to the periodical title, authorization date, and the like. Magazine cover file 84 stores records of the latest magazine cover for a specific magazine identified by a bipad. Name file 86 is a table storing separate records for each publisher using the system. Each record includes fields for storing each publisher's contact information such as name of the publisher, contact name of an individual at the publisher, at least one contact address, at least one phone number, fax numbers if any, email addresses, a trade code, and the like. Name file 86 is referenced, for example, to display the publisher name on the login screen when the publisher logs in, as well as for pulling e-mail addresses, fax numbers and addresses for automatic communications such as e-mails and faxes. Password file 88 is a table storing separate records for each remote user, each record including fields for storing the user name, the user's password, a letter code for the visitor type (i.e. retailer, publisher, wholesaler, etc.), and a user identification code for granting the remote user access to specific databases.

Retailer file 34 is a table storing separate records for each retailer using the system, each record including profile information on the retailer, such as the chain (or retailer) name, chain identification number, address and phone number information, as well as the retailer's choices for schedule of UPC updates, names and contact information for the retailer's UPC manager and category managers, an the like. Wholesaler file 90 is a table storing separate records for each retailer using the system, each record including, for example, wholesaler identification codes for the wholesalers used by the retailer. Category file 92 is a table storing separate records for each periodical category, each record including fields for storing a category code, a category description, and a category flag. Product history file 94 is a table storing separate records for each retailer, the table storing information related to the retailer's reaction to a new product. Each record includes fields for storing a chain identification number, product type, bipad, product status and status date. Product file 96 is a table storing a separate record for each product, each record including fields for storing identifying information for each product such as, for example, product type, UPC code, on-sale date, and the like. Title file 98 is a table storing separate records for each periodical title, each record including fields for storing the periodical bipad code, a publisher code, and the category code. Wholesaler name file 100 is a table storing separate records for each wholesaler, each record including fields for storing an individual wholesaler's name, address and other contact information such as phone number and email address. Wholesaler name file 100 is referenced in a manner analogous to name file 86, for example, for data manager 22 to display the wholesaler name on the login screen when the wholesaler logs in, as well as for pulling the wholesaler's e-mail addresses, fax numbers and addresses for automatic communications such as e-mails and faxes. Chain file 102 is a table storing separate records for each chain or retailer, each record including fields for storing, for example, the current year and quarter, the chain identification number, chain name, address information, and the like. PIN global file 104, PIN class of trade file 106, and a PIN chain title file 108 are copies of files from PIN data manager 24 as explained in more detail below.

Figure 4 is a schematic diagram of the structure of PIN data manager 24. In one embodiment, data manager 24 includes fourteen data files, including PIN global file 104, PIN class of trade file 106, and PIN chain title file 108, and an alphal file 120, a bipad file 122, a distributor file 124, a pocket file 126, a chain store count file 128, an alpha2 file 130, a roll-up file 132, a chain table2 file 134, a category file 136, a chain table file 138, and a publisher bipad file 140. In one embodiment, data for use by PIN data manager 24 is generated as follows. First, quarterly sales data, as described in more detail below, is collected on adjunct server 14 for all magazine sales from all chains or retailers registered with the system. Most of the sales data is collected electronically directly from the wholesalers, chains, or retailers, but some of the data is also collected from computer-generated print-outs from wholesalers, chains, or retailers and then manually keyed into the system by keypunch operators. In an alternative embodiment, the data is collected with written submissions from the wholesalers, chains or retailers and then manually keyed into the system. Generally, the sales data is continually collected so that the registered wholesalers , chains and retailers can provide frequent updates according to the most recent sales data available to them.

In one embodiment, the collected sales data on adjunct server 14 are stored in eight data files which are then downloaded in ASCII text format from adjunct server 14 to a PIN processor 150 through central server 4. PIN processor 150 is, for example, a separate personal computer coupled to central server 4 as shown in Figurel. All PIN processing takes place on PIN processor 150, where data reports are generated on PIN processor 150 in .pdf file format produced with Adobe Acrobat software which is available from Adobe Systems Incorporated, of San Jose, California. Once the accumulated data is converted to .pdf file format on PIN processor 150, the .pdf files are transmitted to central server 4 for display of PIN reports to the remote user on remote terminal 6. For example, PIN chain title file 108 is used by PIN processor 150 to generate and report figures for draw, sale, retail dollars and number of stores receiving the data, as described more fully below.

In one embodiment, the eight data files downloaded to PIN processor 150 include alphal file 120, bipad file 122, distributor file 124, pocket file 126, chain store count file 128, roll-up file 132, chain table2 file 134, and category file 136. Alphal file 120 is a table having separate records for each title by chain or retailer, including separate fields for storing information unique to each title such as bipad, issues per year, suggested cover price, and the like, in addition to the retailer's sales figures for the select title such as draw, and sale as described in more detail below. Alpha2 file 130 is generated from alphal file 120 and is a stripped version of alphal file 120 so that alρha2 is easier to work with. Publisher bipad file 140 is a file storing a list of titles, by bipad, which a user who is a publisher has selected to be monitored for sales with each retailer or chain. Typically, publisher bipad file 140 will store all the titles published by the publisher, but in some cases the publisher may only wish to monitor a subset of all its titles. Distributor file 124 stores the full name and associated distributor code of the national distributor associated with a particular bipad from bipad file 122 coming from adjunct server 14. Category file 136 stores a magazine category code associated with a particular bipad from bipad file 122. Rollup file 132 stores a list of group bipads, each of which designates a group of special interest publications instead of individual titles, so that all sales data for the group of special interest publications is rolled up into one line of data, instead of having separate lines of data for a large number of individual titles. Chain store count file 128 is a table storing separate records for each chain, each record including fields for storing total number of stores in the chain. Pocket file 126 stores the total number of front-end display pockets, or check-out pockets, which each retailer or chain devotes to each title.

In one embodiment, once the original data files on adjunct server 14 are downloaded to PIN processor 150, several processes are run on PIN processor 150 to generate PIN global file 104, PIN class of trade file 106, and PIN chain title file 108. In particular, PIN global file 104 is generated from data stored in alpha2 file 130, and also in bipad file 122, distributor file 124, roll-up file 132, and category file 136. PIN global file 104 generally stores, for example, sales data for each bipad accumulated for all retailers or chains listed in alpha2 file. PIN global file 104 is indexed with a national ranking according to a figure for retail dollars which is included in the sales data from alpha2 file, and a national ranking is added into PIN global file 104. PIN class of trade file 106 is similarly generated from data stored in files 130, 122, 124, 132, and 136, but stores sales data accumulated from all retailers or chains in a particular class of trade. For example, class of trade file 106 stores a data set of sales data accumulated for all supermarkets, the data indexed according to retail dollars as described above, and a class of trade ranking is added into PIN class of trade file 106. The bipad of the particular title links PIN class of trade file 106 to PIN global file 104 so that the global ranking can be pulled into PIN class of trade file 106. PIN chain title file 108 is also generated from data stored in files 130, 122, 124, 132, and 136, and is a chain specific file storing sales data such as, for example, the current year and quarter, chain identification, and bipad, which are used by the PIN processing terminal as described below. Once the PIN global file 104, PIN class of trade file 106 and PIN chain title file 108 are created, system 2 is ready to generate PIN reports for display by PIN data manager 24 to the remote user.

In one embodiment, a remote user accesses system 2, and thus data managers 22 and 24, through multiple HTML pages hyperlinked together and viewed through the Web-browser. It should be understood by those skilled in the art of constructing Web sites that the exact layout of HTML pages, for example the arrangement of hyperlinks on a page, the sequence of pages, the number of pages used to achieve a specific function, etc., can easily be varied. The system is directed primarily to providing the described interactive and dynamically updated data communications among the remote users, and may be accomplished in a variety of ways. Figure 5 shows a first login HTML page 200 for one embodiment of system 2. In use, login page 200 is displayed when a remote user enters a specific uniform resource locator (URL) specifying the location of server 4 on the Web. An ICN login hyperlink 202 is displayed on page 200 and when selected links the remote user to a second view of login page 200 as shown in Figure 6. Data managers 22 and 24 are then generally accessible by a remote user through the second view of login page 200 which invokes a login procedure requiring the remote user to enter his or her unique user name or identifier, and the password which the user has previously registered. A search is made of password file 88 and if the correct password has been entered, system 2 grants the user access to certain database files in data managers 22 and 24. The visitor type code stored in password file 88 is used by the system to provide the remote user with access to specific services, or to particular database functions within one of the services. For example, a publisher may be allowed to upload information related to a new product, while a retailer may be limited to only reading, or downloading, the information related to the new product.

Figure 7 shows an introductory page 204 which, in one embodiment, provides the remote user with a plurality of hyperlinks, each hyperlink linking the user to other pages available on system 2. In one embodiment, page 204 is common for all types of remote users and each hyperlink is functional or not depending on the type of user as identified by system 2 with the visitor type code in password file 88. In one embodiment, page 204 includes a home hyperlink 220, a world item file hyperlink 222, an authorized list hyperlink 224, a new products hyperlink 226, an updates hyperlink 228, a communication hyperlink 230, and a PIN hyperlink 232. The buttons, or areas, provide the remote user with a graphical locator for each hyperlink on a page. Of course, the number and spatial arrangement of hyperlinks on page 204 or any page may vary.

Figure 8 shows a world item file page 240 which is displayed when the remote user clicks on world item file hyperlink 222. World item file page 240 provides access to every magazine in the ICN database. In one embodiment, the products, for example magazines, are sorted alphabetically and indexed by a starting letter of the magazine. Using page 240, a remote user may locate a specific title by clicking on one of the index letters 242 representing the first letter of the title, by clicking on a bipad search button, or by clicking on a title search button. Clicking on, for example, the letter A displays a titles page 244, as shown in Figure 9.

In addition, a search routine is included in world item file page 240, so that the remote user may find a specific bipad or title in the database. For example, the remote user may enter, or search for, a specific bipad, i.e. , 01111, so that information relative to the selected bipad is displayed on bipad page 246, as shown in Figure 10. Bipad page 246 includes, in one embodiment, the bipad reference number or name, a title, the category, the publisher, a national distributor code, national sales ranking for the title, national sales for the title, class of trade ranking and sales, chain ranking, and chain sales. Of course, the specific information reported on bipad page 246 may vary. In alternative embodiments additional information related to the selected bipad is also included. For example, in one embodiment, bipad page 246 includes a hyperlink to another page which displays a graphical representation of a magazine cover. In an alternative embodiment, bipad page 246 itself includes the magazine cover graphic . Searching for a specific title operates similarly to the search for a specific bipad with information for the title being displayed on a title page (not shown).

From pages 244 and 246, the retailer may click on the selected bipad to display a UPC information page 248, as shown in Figure 11. UPC information page 248 includes, in one embodiment, a status of the selected magazine's UPC code, i.e., whether the selected magazine's UPC code is active or inactive, a full UPC code, a compressed UPC code, the magazine's title, national distributor, and a cover price. The remote user may also, from pages 244 and 246, click on the magazine title to display an add authorized list page 250, as shown in Figure 12. Add authorized list page 250 includes, in one embodiment, a date to add the selected magazine to the retailer's deliveries, an authorization type, and an accept child determination.

Initially, in one embodiment, each retailer has an authorized list, or file, based on a unique remote user identification number, which is empty or contains no authorized products, i.e., magazines. For each magazine that is added, the retailer determines whether the added title is designated a core title, an optional title, or a tolerable title. In one embodiment, the tolerable titles do not appear on the authorized list, however, the UPC updates are received by the retailer for these titles. If the retailer determines that child bipads are accepted, by clicking inside an accepted child bipads area 252, the retailer will receive, for example, special editions of an authorized bipad. If the retailer fails to check accepted child bipad area 252, the retailer will not receive the special editions unless each is authorized separately. After entering responses to the requested information, the remote user clicks on an Add area 254, or button, to add the selected title to the remote user's authorized list.

The retailer may return to world item file page 240, using hyperlink 222, at any time to add additional titles to the authorized list as well as make changes to the selected titles. For example, a retailer may connect to the correct URL and world item file page 240, using hyperlink 222, on a daily, weekly, monthly, or any other desired period of time to alter the retailer's authorized list. This alteration may include adding new titles, and adding existing titles. (To remove titles from the authorized list, the remote user uses authorized list hyperlink to link to an authorized list page as described below.) More specifically, as the retailer makes the appropriate selections, the selection data is transferred to system 2 and stored using ICN data manager 22.

After the retailer has created the authorized list via world item file page 240, the retailer may review the authorized list by clicking on authorized list hyperlink 224. By clicking on hyperlink 224, the retailer is advanced to an authorized list page 258, as shown in Figure 13 and the authorized list data is transferred from system 2 to remote user via terminal 6. Authorized list page 258, in one embodiment, allows the remote user to search bipads for UPC information, remove titles from the remote user's authorized list as well as print or download the authorized list to terminal 6, i.e., the retailer's local computer. A title detail page 260, as shown in Figure 14, is displayed after clicking on the download area, or entering a bipad or title. Page 260 includes, in one embodiment, bipad number, title, authorization level, national distributor, publisher, national rank and sales, class of trade rank and sales, chain rank and sales, parent bipad, magazine cover graphics, and category information for each product in the remote user's authorized list.

From page 260, the retailer may delete one or more selected bipads or titles from the authorized list or view UPC information for the selected product. In one embodiment, a title is removed from the authorized list by clicking on the title on page 260. After being selected to be removed, an update authorized list page 262 as shown in Figure 15 is displayed. The remote user then enters a date to remove the selected title, and clicks on the delete hyperlink to delete the selected title. To view UPC information for a selected product, the remote user clicks on the bipad of a selected title on page 260, so that an authorized list UPC information page 264, as shown in Figure 16, is displayed. From page 264 the retailer may review a UPC status, a transaction date, the UPC code, the uncompressed UPC code, national distributor and cover price. Generally, the retailer thus uses authorized list pages 260, 262 and 264 to review the retailer's authorized list, to update the authorized list by deleting titles, as well as to obtain information related to the UPC code.

The retailer may obtain information related to new products, specials and special promotions by clicking on new products hyperlink 226 so that a new product page 270 is displayed on the retailer's computer. New product page 270, in one embodiment as shown in Figure 17, includes a new titles hyperlink 272, a specials hyperlink 274, and a promotions hyperlink 276. Clicking on new titles hyperlink 272 displays a new title page 278, as shown in Figure 18. Clicking on one of the new titles on page 278 displays an information page 280 which includes, in one embodiment shown in Figure 19, information related to the new title. The information may include, for example, a picture or graphical representation of the cover of a past or current edition, a brief summary of the magazine, target buyers, UPC code, bipad number, available date, suggested retail cost, i.e. , cover price, and an area to click on to add, hold, or refuse the selection from the retailer's authorized list. Hyperlinks 274 and 276, enable the remote user to review specials and promotions that other remote users, for example, distributors and publishers, may be offering on certain magazines or products. For example, in one embodiment new title page 278 includes a list of new titles, specials, and promotions.

Once the remote user has finished selecting products, for example magazines, the revised authorized list for the remote user is delivered to the appropriate remote users for future deliveries. For example, a retail magazine store's authorization list may be delivered to distributors and publishers for future deliveries. The authorized list may be automatically delivered using the system via e-mail or FAX directly to the other remote users, as selected, or where these methods are unavailable or undesired, printed for manual delivery in person or via regular mail. In one embodiment, the entire authorized list is initially transferred to an appropriate user and thereafter only changes, or modifications, to the authorized list are transferred. For example, after a retailer initially develops, or selects, its authorized list, the entire authorized list is transferred to the appropriate supplier or suppliers. Thereafter, only the changes to the authorized list for that retailer are transferred to the suppliers. In one embodiment, the entire authorized list is transferred to the suppliers at a regular predetermined period of time, for example monthly, so that the suppliers and retailer do not have to work from a series of changed authorized lists. Using this predetermined period for scheduling the processing of fully updated authorized lists reduces time associated with maintaining the proper authorized list, while also assuring matching lists between the suppliers and retailers.

To obtain an update of the UPC information or authorized list for products in the remote user's authorized list, the remote user clicks on updates hyperlink 228 which displays an updates page 282, as shown in Figure 20, on the user's computer 6. From updates page 282 the remote user may request to receive an update for at least one update file for a specified date. More specifically, the remote user, in one embodiment, may select to receive a UPC update file, all UPC codes withheld due to errors file, all authorized titles for which there are no codes available file, and an entire authorized list file. Typically, the remote user will download only the UPC update file, while the other files are typically used for informational purposes only. More specifically, in one embodiment, page 282 enables a remote user who is a retailer to download only the changes to the UPC information from a specified date. In addition, page 282 enables a remote user without an authorized list to obtain UPC information. For example, page 282 enables the retailer to receive, or download, UPC information, including price and UPC code, for all bipads and titles.

The UPC update file, in one embodiment, is configured as a standard database or spreadsheet file so that the file can be reviewed, or modified, using known database and spreadsheet programs, for example, Excel™ by Microsoft Corporation. In addition, the retailer may determine the frequency of automatic updates to be received from server 4 as defined in a remote user update profile stored in server 4. Using the time determined by the remote user update profile, server 4, will automatically transfer an update to the appropriate remote user. For example, the retailer may determine that the UPC update file should automatically be transmitted from central server 4 every Tuesday. As a result, the UPC update file will be automatically transmitted from server 4 to the remote terminal 6, i.e. , the retailer's computer every Tuesday. Another retailer may select to receive the UPC update file every day, or once a month. Additionally, the retailer may alter the frequency of receiving the UPC update file at any time.

In one embodiment, the remote user's, i.e., retailer's, updated authorized list is automatically transferred to the proper other remote user or users, for example the appropriate supplier, each and every time the retailer makes a change to its authorized list. By automatically providing this update to the supplier, the retailer will be assured of receiving only the appropriate bipads and titles. The automatic transfer also reduces the management cost to the retailer in that the information is automatically sent and the retailer does not have to remember to send the information.

The retailer may exchange information with other remote users, for example, magazine distributors and publishers, by clicking on communication hyperlink 230 which displays a communication page 284 on the retailer's computer, as shown in Figure 21. Using communication page 284, the remote user may send messages and information directly to a selected remote user, or the system operator. More specifically, a remote user may enter the message and send to all remote users by clicking on a send all button 286. The information is then transferred to all remote users . In one embodiment, communication page 284 also includes a send select button 288. By clicking on button 288, a remote user select page (not shown) is displayed. The remote user then may select a remote user or group of remote users to receive the entered message. By clicking on selectable areas of communication page 284, e-mail messages may be transmitted to other selected, or desired, remote users. For example, if a retailer has a question for a publisher, the retailer may send an electronic message directly to the publisher via communication page 284.

Generally, many of the pages configured for retailer access to system 2 are modified to create a whole set of related pages for use by publishers. For example, a new title/promotions page for publishers, is similar to new titles/promotion page 270 as shown in Figure 17, but is modified so that publishers can upload JPEG of GIF files representing magazine covers for select titles. The cover files are posted on the system 2 and can be viewed by retailers using page 270. Similarly, publishers have a communications page similar to page 284 but modified to select retailers and wholesalers. Figure 22 shows a publisher's home page 290 which is displayed in the alternative to introductory page 204 if the ID and password entered on login page 200 are associated with, or identified as a different, or a second type of remote user, for example a publisher. In one embodiment, page 290 includes a home hyperlink 292, a world item file hyperlink 294, an authorized list hyperlink 296, a new products hyperlink 298, an updates hyperlink 300, a communications hyperlink 302, and a PIN hyperlink 304. Hyperlinks 292 - 304 operate similarly to hyperlinks 220 - 232 on introductory page 204 except as follows.

Clicking on hyperlink 294 displays a publisher world title list search page 310 as shown in Figure 23. Page 310 enables a second type of remote user, for example a publisher, to search for a bipad or title, and then to select a bipad for display of UPC information for that bipad. More specifically, publisher world title list search page 310 is generally a search page from which a publisher can search its world title list for a particular bipad or title. In addition, a download hyperlink 312 enables the publisher to download its entire world title list. For example, and in one embodiment of system 2, after searching for and clicking on a title from page 310, the remote user is linked to an authorized chain list page 314 as shown in Figure 24, which displays a list of all remote users, i.e. retailers, which have included the selected title on their authorized list page.

Figure 25 shows a chain selection page 316, which is displayed when hyperlink 296 is selected. Page 316 displays a list of chains or retailers registered with the system from which the remote user may select to view UPC information for the remote user's authorized list. After selecting a chain from page 316, a page (not shown) which looks like page 258 (Figure 13) but used only for publisher remote users, is displayed. Figure 26 shows an authorized list page 318, which is displayed when the display authorized list button is selected from the publisher's version of page 258. In one embodiment, page 318 displays the remote user's authorized list for a particular chain or retailer, in which the authorized list includes the bipad, title, authorization level, national distributor, publisher and category information, parent bipad and cover information for each title on the remote user's authorized list and sold at the selected chain.

Clicking on hyperlink 298 displays a new title/promotions page 320, as shown in two views in Figures 27 and 28. Using page 320, the remote user may click on an upload image button, or area, 322 to upload, or transmit, information from remote terminal 6 to server 4. In one embodiment, the system displays standard JPEG and GIF files, however, other standard file types may be displayed. Once the appropriate file is uploaded to the system, or central server, the operator will review the file for appropriate formatting and content and post, or connect, the file to the appropriate title or bipad. In addition, new title/promotions page 320 includes a new titles area, or button, 324.

Clicking on new title button 324 displays a second view of title page 320, as shown in Figure 28 which includes, in one embodiment, a listing of new titles and related information. By clicking on one of the new titles, a third view of page 320, as shown in Figure 29, is displayed. In one embodiment, the third view of page 320 includes, for example, a picture or graphical representation of the cover of a past or current edition, a brief summary of the magazine, target buyers, UPC code, bipad number, available date, suggested retail cost, i.e., cover price, and a view status button or hyperlink. Clicking on a view status button 323 displays a fourth view of page 320 as shown in Figure 30 which includes, in one embodiment, information representing responses of remote users to the selected new title. For example, the fourth view of page 320 displays a listing of remote users, for example chains and retailers, and their identification numbers, names, and a remote user status, i.e. , whether each remote user decided to add, hold, or refuse the new title. Using this information, a remote user, for example a publisher, is able to determine the response to a new title or special promotion. Clicking on hyperlink 300 displays a publisher updates page (not shown). In one embodiment, the remote user uses the publisher updates page to transfer, or to review, UPC information from the system, specifically, the remote users product database. More specifically and in one embodiment, the remote user uses the information on the publisher updates page to add, remove, and modify the UPC information for the remote user's products in the central clearinghouse, or database, system, for example a lockbox system on the IPDA system as described above. This information may, in one embodiment, include the UPC code, the price, and distributor names. This information is then downloaded from the IPDA lockbox system to server 4. The downloaded information is then compared to the existing UPC information to generate an error file. The error file, in one embodiment, includes redundant, or duplicate, codes. The error file is then stored in server 4. Each remote user may review the UPC information, including the error file, to verify that the changes were incorporated into the UPC information stored in server 4.

Clicking on hyperlink 302 displays a publisher communication page 324, as shown in Figure 31. Using publisher communication page 324, the remote user may send messages and information directly to a selected remote user, or the system operator. More specifically, a remote user may enter the message and send to all remote users by clicking on a send all button 326. The information is then transferred to all remote users . In one embodiment, communication page 324 also includes a send select button 328. By clicking on button 328, a remote user select page (not shown) is displayed. The remote user then may select a remote user or group of remote users to receive the entered message. In alternative embodiments, ICN data manager 22 is configured to exchange product information for many products among all types of remote users. For example, the above described ICN data manager22 may include a plurality of databases which each contain information for a different type or class, of product, i.e., books, health and beauty products, canned goods, produce, as well as other types of goods. Using the system, different types of remote users may exchange information about these products. For example, using ICN 22, a retail buyer for a supermarket may review information provided by producers about new products to determine whether the supermarket will stock the specific product on its shelves. ICN 22 may then be used by the supermarket to determine a local distributor to arrange delivery of the selected products. Once the products are on the shelves, ICN 22 may be used to maintain the appropriate UPC information, including price, for use by the cashier scanners.

More particularly, the system operator, utilizing information provided by information uploaded from the remote users, creates the databases. A separate database may be generated for each product which, in one embodiment, includes, the bipad number, the title, the UPC code, full and compressed, the price, the name of the national distributor, the name of the publisher or producer, the category name, the UPC code status and effective date. In one embodiment, a separate new product and special promotion database is then generated which includes the information related to the new products and special promotions as described above. As the remote users login and generate a unique, or separate database for their individual authorized lists as described above, these lists are stored in memory of central server 4. In addition, as described above, information from other types of remote users is uploaded to system 2. This uploaded information is reviewed and stored, with the appropriate links, in central server 4 for use by the remote users.

In one embodiment, system 2 includes PIN data manager for providing consolidated reporting on the sales performance of periodicals to retailers and publishers. Referring to Figures 32 - 45, PIN 24 is implemented through, for example, a year/quarter selection page 330, a reports menu page 332, a global/class of trade report menu page 334, a global title report page 336, and a class of trade title report page 338. Further, PIN includes the following pages for displaying retail chain specific reports: a chain specific report menu page 340, a category analysis page 342, a chain specific title report page 344, a top 200 title report page 346, a schematic page 348, a pockets per bipad page 350, a store list page 352, and a chain name report page 354. PIN pages are displayed on remote terminal 6 through a shareware program such as, for example, Adobe Acrobat Reader.

Figure 32 shows year/quarter selection page 330 which, in one embodiment, displays a scroll box 360 for selecting a year and quarter.

Figure 33 shows reports menu page 332 which, in one embodiment, displays three hyperlinks corresponding to three different choices for the remote user: global reports 362, chain specific reports 364 and chain names reports 366.

Figure 34 shows global/class of trade menu page 334, which is displayed after clicking on global hyperlink 362 on menu page 332. Global/class of trade menu page 334 displays ten hyperlinks corresponding to ten different choices for the remote user: eight class of trade hyperlinks 368, including one each for the eight different classes of trade identified as convenience stores , drug , government, grocery wholesaler, mass merchandiser, newsstand, specialty, and supermarket; consolidated title 370, and return 372.

Figure 35 shows global title report page 336 which is displayed upon selecting consolidated title hyperlink 370. Page 336 shows a title report 376 organized by dollar sales of each periodical for all classes of trade combined. In one embodiment, title report 376 lists the national ranking, bipad, title, issues per year, draw, sale, percent of sale, dollars sales, percent of dollars sales, bipad category, and bipad distributor information for each periodical title. National ranking is the ranking of a title by dollars sales for all retail outlets (i.e. not restricted to a selected class of trade). Bipad is the unique identifying number assigned to each title. Title is simply the published title of the periodical. Issues per year is the number of times per year that the title is published. Draw is the number of units of a magazine that is placed in an outlet, for example, a retail outlet. Sale is the number of units that are sold in the outlet. Percent of sale is calculated by system 2 by dividing sale by draw, to obtain a number representing sales efficiency in a retail outlet. Dollars sales represents the total dollars received from the sale of a title, and percent of dollars sales is calculated by dividing dollars sales by the total of all dollars sales for the specific report. Bipad category is a description of the type or class of periodical. Bipad distributor is the name of the national distributor of the periodical, the organization that distributes copies of the periodical to local wholesale distributors who distribute the periodicals locally to retailers.

Figure 36 shows class of trade title report page 338 showing a title report 378 organized by dollar sales of each periodical for the selected class of trade. A class of trade is selected by the remote user by clicking on the corresponding hyperlink 368 on page 334, which displays a split screen view of class of trade title report page 338. A full screen view of class of trade title report page 338 is available to the remote user by clicking on a screen enlargement icon on the screen taskbar. Class of trade global report menu page 338 also displays a return to main menu hyperlink 372, which returns the remote user to main menu page 332. For example, Figure 36 shows a title report for convenience stores. In one embodiment, each title report 378 lists substantially the same information as global title report 376, but also includes a figure for class of trade ranking which is the ranking of a title by dollars sales within the selected class of trade, for example, in convenience stores.

Figure 37 shows chain specific report menu page 340, which is displayed when chain specific reports hyperlink 364 is selected by the remote user from main menu page 332. Chain specific reports menu page 340 displays a list 380 of letters of the alphabet, each letter corresponding to a hyperlink to an alphabetic directory list 382 of all PIN retail chains beginning with that letter. For example, Figure 38 shows a second view of chain specific reports menu page 340 with a view of directory list 382 showing multiple entries 384 representing all PIN retail chains beginning with the letter "F". Each entry 384 is a hyperlink to category analysis page 342.

Figure 39 shows category analysis page 342 for a retail chain selected from directory list 382. Category analysis page 342 displays a report by periodical category of sales data for the selected retailer. In one embodiment, category analysis page 342 displays the following information, as determined by system 2, under matching headings: bipad category, number of titles, draw, percent of total draw , sale , percent of total sale , percent of sale , dollars sales , and percent of total dollars sales. Number of titles is the number of titles represented in the corresponding bipad category on the list. Draw is the number of periodical units that are placed in a selected retail outlet. Percent of total draw is the category- specific draw divided by the total draw for the entire report. Sale is the number of periodical units that are sold from the selected retail outlet. Percent of total sale is the category specific sale divided by the total sale for the entire report. Percent of sale is the category-specific sale divided by the category-specific draw to obtain a measure of sales efficiency. Dollars sales is the total dollars received from the sale of a periodical within the category, and percent of total dollars sales is the category-specific dollars sales divided by total dollars sales for the entire report. Category analysis page 342 also displays a return to select chain hyperlink 390, a category analysis hyperlink 392, a titles hyperlink 394, a top 200 list hyperlink 396, a schematics hyperlink 398, a pockets per bipad hyperlink 400, and a store list hyperlink 402.

Figure 40 shows chain specific title report page 344 which is displayed when titles hyperlink 394 is selected from category analysis page 342. Title report page 344 displays information on a given publisher's titles, only for those users logged on and identified as the publisher. In one embodiment, title report page 344 displays according to title the following: national ranking, class of trade ranking, chain ranking, bipad, title, issues per year, draw, sale, percent of sale, dollars sales, percent of dollars sales, bipad category, and number of stores receiving the title. Chain ranking is the ranking of the title within the specific retail chain based on dollars sales. Number of stores receiving is the average number of stores in a retail chain which sell that periodical title. In one embodiment, the average, as determined by system 2, is based on the total number of issues sold within the most recent quarter.

Figure 41 shows a top title list page 346 which is displayed when top 200 list hyperlink 396 is selected from category analysis page 342. Top title list page 346 displays for both retailers and publishers information for a pre-determined number of periodical titles within the retail chain, according to dollars sales. For example, a top 200 list. In one embodiment, top title list page 346 lists according to retail dollars, the following: national ranking, class of trade ranking, chain ranking, bipad, title, issues per year, draw, sale, percent of sale, dollars sales, percent of dollars sales, bipad category, and number of stores receiving the title.

Figure 42 shows schematics page 348 which is displayed when schematics hyperlink 398 is selected from category analysis page 342. Schematics page 348 displays a schematic representation 404 of the front-end fixture displays in the selected retail chain. Schematics page 348 shows the arrangement of specific periodical titles in the display. The schematics are graphical representations drawn, for example, using Harvard Graphics and then converted to .pdf files for use in Adobe Acrobat.

Figure 43 shows pockets per bipad page 350 which is displayed when pockets per bipad hyperlink 400 is selected from category analysis page 342. Pockets per bipad page 350 lists, by title, the specific periodical titles placed in front-end fixture displays in the selected retail chain, and the total number of fixture pockets devoted to the given title across all stores in the retail chain.

Figure 44 shows store list page 352 which is displayed when store list hyperlink 402 is selected from category analysis page 342. In one embodiment, store list page 352 displays a list of codes 406 corresponding to different display fixture types. Store list page 352 further lists for each individual store in the selected retail chain, the following information: division number, store number, street address, city, state, zip code, servicing wholesaler, and the number of each type of display fixture in the store. In an exemplary embodiment, store list page 352 displays ten (10) columns for listing the fixture counts across ten (10) different fixture types.

Figure 45 shows chain name report page 354 which is displayed when chain names report hyperlink 366 is selected from main menu page 332. In one embodiment, chain names report page 354 displays a list by chain name, ordered by a chain identification number, class of trade code, class of trade name, total number of stores, and number of stores selling periodicals. Chain names report page 354 is subject to alternative viewing as an alphabetic list by chain name, by selecting a chain list by names hyperlink 410 displayed on chain name report page 354.

As will be understood by those skilled in the art of network-enabled database technology, data in the central database can be manipulated and accessed in a variety of different ways to provide additional information services for remote users. For example, in an alternative embodiment, system 2 includes a fourth data manager (not shown in Figure 1) which uses sales data provided by a remote user such as a retailer, and stored and updated on the central database, to analyze the effect of specific configurations of products on a display fixture (such as a front- end rack or end-cap) on sales of the products. More specifically, the fourth data manager performs a profit analysis as a function of the placement of products, to determine the most profitable placement of the products. Referring to Figures 46 - 54 the fourth data manager is implemented through, for example, a first client profile page 500, a second client profile page 502, a first category manager page 504, a second category manager page 506, a first plan manager page 508, a second plan manager page 510 and a profit picture page 512.

Figure 46 shows first client profile page 500 , which prompts a remote user with access to system 2, typically a retailer or a publisher, to provide client information. In one embodiment, the client profile information is transferred to system 2 via remote terminal 6 and includes, for example, client name, telephone number, address, a unique client identifier such as a client number, and the remote user's class of trade. The information further includes sales variables such as, for example, profit percentage, anticipated percent growth, percent attributable to warehousing costs, and percent attributable to shrinkage. In one embodiment, as shown in Figure 46 the sales variables are broken down for different categories of merchandise, such as, for example, publications, confections, and general merchandise and are transferred from remote terminal 6 to system 2. More specifically, and in one embodiment, the client profile information is collected by having each remote user provide the information through an electronic or written questionnaire. First client profile page 500 further includes a prompt for the remote user to provide the anniversary date of a particular product display fixture; a prompt for user input regarding a decision on a "pay-to-stay "option, an option to keep the display fixture for another specified time period; and a prompt for providing the name of the fixture manufacturer.

Figure 47 shows second client profile page 502. Second client profile page 502 includes, for example, user prompts for providing additional information on vendor contacts for the different categories of displayed merchandise: publications, confections and general merchandise. For example, the vendor contact information includes vendors' addresses, telephone numbers and the like. The information is stored so that the remote user can readily track vendor contacts while using the fourth data manager , enhancing the ability of the remote user to negotiate deals, and follow up on payments, with vendors. Second client profile page is hyperlinked, for example by a view next hyperlink 512, to first category manager page 504.

Figure 48 shows first category manager page 504. First category manager page 504 provides the remote user with up to about fifteen locations 516 across the page, each location 516 representing a different fixture configuration option. The fixture configuration options vary in terms of the relative amount and location of space devoted on each fixture to each category of merchandise, for example, publications, confections, and general merchandise. More specifically, the height and width of space devoted to each category of product varies among the different configuration options. Each option location 516 further is a hyperlink to second category manager page 506.

Figure 49 shows second category manager page 506 which displays at least one view of a graphical representation of the configuration option selected by the remote user from first category manager page 504. In one embodiment as shown in Figure 49, two views 520 and 524 of an end-cap configuration are displayed on . second category manager page 506. Second category manager page 506 further includes at least one interactive input space 526, such as a blank box, for the remote user to enter the total number of units, or display fixtures, the remote user, typically a retailer, desires to use. Second category manager page 506 further includes a plurality of interactive output spaces 528. At least one interactive output space 528 displays a figure for profit center monies, a dollar figure representing the placement money earned by the remote user from product vendors in exchange for selected positioning of the vendor's product on the display fixture. For example, one year profit center monies are determined by the following calculation from one year data provided by the remote user, (where # magazine shares = # of pockets in the display fixture; # general merchandise shares = # of display pegs):

(# of magazines shares x (billing rate - cost) x total number of units) (# general merchandise shares x (billing rate - cost) x total number of units)

+ (# inches shelf space for confections x (billing rate - cost) x total number of units) In one embodiment, a three year total is calculated similarly, but using three year total figures for general merchandise, and one year totals for periodicals and confections.

In one embodiment, second category manager page 506 further includes two interactive output spaces 528 for displaying two different figures for profit center monies, one each for monies earned over one year, and another for monies earned over three years. At least one interactive output space 528 displays a figure for annual profit monies, a dollar figure calculated using the total number of units provided by the remote user, and representing the total monies to be earned using the selected display fixture configuration in the remote user's retail outlet. For example, the annual profit monies figure includes quarterly pocket payments and magazine sales profits. In one embodiment, second category manager page 506 includes two interactive output spaces 528 for displaying two different figures for annual profit monies, one each for monies earned over one year, and another for monies earned over three years. Both profit center monies and annual profit monies are calculated using the sales variables provided by the remote user on first client profile page 500, so that the calculated profit figures take into account the remote user's sales history and expected growth.

Second category manager page 506 is hyperlinked to a first plan manager page 508, shown in Figure 50. First plan manager page 508 provides the remote user with up to about fifteen locations across the page, each location 530 representing a different product lay-out option in the fixture configuration selected by the remote user from first category manager page 504. The lay-out options vary in terms of the location for each individual product in individual fixture pockets, within the space devoted to the particular category of product. For example, the location and amount of space for a particular magazine title varies among lay-out options, within the space devoted to publications in the fixture configuration option selected by the remote user. Each lay-out option location 530 is also a hyperlink to a second plan manager page 510. Figure 51 shows second plan manager page 510. Second plan manager page 510 displays a graphical representation 532 of a section of the lay-out option selected from first plan manager page 508. The position of each product in the selected lay-out is determined in part by the relative profitability of the product based on past sales data provided by the remote user and stored in the database. In one embodiment, as shown in Figure 51, second plan manager page 510 displays a graphical representation of a section of a magazine lay-out within the space on the display fixture devoted to publications. For example, after second plan manager page 510 appears, the most profitable magazine titles sequentially appear as they are added to fixture pockets in order of profitability to the publications lay-out. The most profitable magazines are determined through a calculation performed on data stored in the database. More specifically, and for example, the database holds figures provided by the retailer remote user for total profit for a given title, taking into account placement fees, pocket payments, and sales profit index on total profit.

A complete publications lay-out displays, for example, a graphical representation of an array of magazine covers. A plurality of interactive output spaces 534 display sales variables for the selected lay-out. The displayed sales variables represent various breakdowns of the profit center figures, annual profit figures , and other figures provided by the retailer remote user . The sales variables include, for example, total number of display units or racks, profit center monies per unit, profit center monies for all units, gross profit on sales per unit, gross profit on sales for all units, gross rebate monies per unit, and gross rebate monies. In one embodiment, the default value for units is one (1) unit, and the total number of units is adjusted by the remote user.

As shown in Figure 52, each individual product in the selected lay-out displayed on second plan manager page 510 is subject to the remote user's selection by a single mouse click on the graphical representation of the individual product. Upon being selected, the graphical representation of an individual product is enlarged and displayed on second plan manager page 510, along with a dollar figure representing the sales profits generated by the individual product for the remote user, as determined from the sales data provided by the remote user. As shown in Figure 53, each product, for example each magazine cover, is further subject to selection by a double mouse click, which produces a scroll box 536. Scroll box 536 displays a scrolled listing of products which can be substituted for the selected product. For example, scroll box displays an alphabetic listing of multiple entries for alternative substitute magazine titles. In one embodiment, scroll box lists the top 200 selling products within the class of trade. Each entry in scroll box 536 is subject to selection by the remote user by a mouse click. Upon selection of an entry from the listing in scroll box 536, the substitute product represented by the selected entry is displayed in the fixture pocket where the previously selected product had been located. Second plan manager page 510 also displays a sales data window 538 showing sales data relating to the substitute. Still further, the graphical representation of each product is subject to click and drag movement with the mouse so that products can be rearranged among the fixture pockets. All profit figures are reanalyzed each time a product is moved, or removed and replaced. Second plan manager page 510 further includes a view next hyperlink 540 which links second plan manager page 510 to a new view of second plan manager page 510. The new view shows another section or segment of the selected layout. Again, the most profitable products for that section of the lay-out are displayed. Additional sections of the lay-out are viewed accordingly. In some cases, the new view will be of a section devoted to a different category of merchandise than the previously viewed section. The graphical representations of individual products in all categories of merchandise are subject to selection for enlargement and profit analysis, substitution, and click and drag movement. Second plan manager page 510 further includes a calculate hyperlink 542, which links second plan manager page 510 to profit picture page 512.

Figure 54 shows profit picture page 512. Profit picture page 512 displays a summarized profit analysis of the newly selected fixture and product mix. Profit picture page 512 includes a plurality of interactive output spaces 546 which display profit figures or numbers. The figures are calculated according to the client information provided by the remote user on first client profile page 500. For example, profit picture page 512 includes profit center monies and annual profit monies, broken down according to each product category, one-year totals, and three-year totals. More specifically, for example, billing, cost and net revenue figures are each displayed under a profit center heading, and are broken down according to the three product categories of publications, confections, and general merchandise, and for one year and three year totals. Under an annual profits heading, sales revenues, rebates and total sales figures are displayed for each of the three product categories, and for one year totals and three year totals. As will be clear to those skilled in the art, yet other data managers may be included in the system to provide additional services to remote users. The above- described interactive communication network system provides a network-based system for consolidating the exchange and maintenance of commercial data among trading partners in a business. The system provides regularly updated and thus very current information, which is particularly important for remote users involved in highly competitive businesses . The system provides a range of helpful commercial services at one conveniently accessible and user-friendly site. Remote users using the system exchange a range of commercially relevant information based on the regularly updated data. Further, individual remote users obtain the information tailored to their own needs.

From the preceding description of various embodiments of the present invention, it is evident that the objects of the invention are attained. Although the invention has been described and illustrated in detail, it is to be clearly understood that the same is intended by way of illustration and example only and is not to be taken by way of limitation. For example, although only certain types of remote users were described, any number of different types of remote users could be identified. In addition, depending on the flow of information, the different remote users may be a first type of user for a select type of database and be a second type of remote user for a different database. Accordingly, the spirit and scope of the invention are to be limited only by the terms of the appended claims.

Claims

WHAT IS CLAIMED IS:

1. A system for providing updated product data to a plurality of users, said system comprising:

at least one computer;

a server including at least one database, said database including product data relating to sales of a plurality of products, said server configured to automatically retrieve updated product data from an external source connected to said server, said server further configured to read input data relating to a user profile and input data relating to a user request for product data;

a network electronically connecting said server to said computer; and

a user interface on said server configured to allow a user to submit said input data relating to a user profile and input data relating to a request for product data, and to receive from said server output data relating to the plurality of products.

2. A system in accordance with Claim 1 wherem said at least one database is computer network-enabled.

3. A system in accordance with Claim 1 wherein said server is further configured to analyze said input data relating to a user profile and to provide said output data relating to the plurality of products according to said input data relating to a user profile for the user.

4. A system in accordance with Claim 3 wherein said input data relating to a user profile comprises uniquely identifying information relating to the user.

5. A system in accordance with Claim 4 wherein said uniquely identifying information includes at least one of a name, a user type, a unique identification number, an address and a telephone number.

6. A system in accordance with Claim 3 wherein said system is configured to provide the user with access to said server according to said user profile for the user.

7. A system in accordance with Claim 3 wherein said input data relating to a request for product data comprises an authorized list of products for the user.

8. A system in accordance with Claim 7 wherein said product data comprises updated UPC information and said output data comprises updated UPC information for products on said authorized list for the user.

9. A system in accordance with Claim 3 wherein said server is configured to allow the user to submit said input data relating to a user profile and said input data relating to a request for product data via the Internet.

10. A system in accordance with Claim 3 wherein said product data comprises product data for a plurality of products within a class of products.

11. A system in accordance with Claim 3 wherein said product data comprises at least one of product pricing information, product sales information and product display information for a plurality of products.

12. A system in accordance with Claim 11 wherein said product sales information comprises sales data for the plurality of products consolidated across a plurality of retailers of the products.

13. A system in accordance with Claim 11 wherein said product data comprises product display information, and wherein said server is configured to analyze said product display information and to provide said output data relating to the plurality of products, said output data comprising product sales in relation to said product display information.

14. A system in accordance with Claim 3 wherein said external source comprises a remote information clearing house.

15. A system in accordance with Claim 14 wherein said remote information clearing house stores updated UPC information for a plurality of products.

16. A system in accordance with Claim 15 wherein said product data comprises updated UPC information from said remote information clearing house, wherein said input data relating to a request for product data comprises an authorized list of products for the user and said output data comprises updated UPC information for products on said authorized list for the user

17. A system for managing product data for a plurality of users, said system comprising:

at least one computer;

a server including at least one dynamically updated database, said database including product data relating to sales of a plurality of products, said server configured to automatically retrieve updated product data from an external source connected to said server, said server further configured to read input data relating to a user profile and input data relating to a user request for product data;

a network electronically connecting said server to said computer; and

a user interface on said server configured to allow a user to submit said input to said server data relating to the user, said server configured to use said data relating to the user to generate an output of product data relating to the plurality of products, said interface configured to allow the user to receive said output.

18. A system in accordance with Claim 17 wherein said at least one dynamically updated database is computer network-enabled, said database updated through said computer network .

19. A system in accordance with Claim 17 wherein said server is further configured to analyze said input data relating to a user profile and to provide said output data relating to the plurality of products according to said input data relating to a user profile for the user.

20. A system in accordance with Claim 17 wherein said input data relating to a user profile comprises uniquely identifying information relating to the user.

21. A system in accordance with Claim 20 wherein said uniquely identifying information includes at least one of a name, a user type, a unique identification number, an address and a telephone number.

22. A system in accordance with Claim 19 wherein said system is configured to provide the user with access to said server according to said user profile for the user.

23. A system in accordance with Claim 19 wherein said input data relating to a request for product data comprises an authorized list of products for the user.

24. A system in accordance with Claim 19 wherein said product data comprises updated UPC information and said output data comprises updated UPC information for products on said authorized list for the user.

25. A system in accordance with Claim 19 wherein said server is configured to allow the user to submit said input data relating to a user profile and said input data relating to a request for product data via the Internet.

26. A system in accordance with Claim 19 wherein said product data comprises at least one of product pricing information, product sales information and product display information for a plurality of products.

27. A system in accordance with Claim 26 wherein said product sales information comprises sales data for the plurality of products consolidated across a plurality of retailers of the products.

28. A system in accordance with Claim 26 wherein said product data comprises product display information, and wherein said server is configured to analyze said product display information and to provide said output data relating to the plurality of products, said output data comprising product sales in relation to said product display information.

29. A system in accordance with Claim 19 wherein said external source comprises a remote information clearing house.

30. A system in accordance with Claim 29 wherein said remote information clearing house stores updated UPC information for a plurality of products.

31. A system in accordance with Claim 30 wherein said product data comprises updated UPC information from said remote information clearing house, wherein said input data relating to a request for product data comprises an authorized list of products for the user and said output data comprises updated UPC information for products on said authorized list for the user