(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2004/0103037 A1
`(43) Pub. Date:
`May 27, 2004
`Wetmore et al.
`
`US 2004O1 O3037A1
`
`(54) METHODS AND APPARATUS FOR
`ORGANIZING RETAL PRODUCT
`INFORMATION
`
`(75) Inventors: Andrew H. Wetmore, Geneva, IL
`(US); Dennis J. Honan, Cary, IL (US);
`James A. Tuchler, Northbrook, IL (US)
`Correspondence Address:
`Thomas A. Miller
`Michael Best & Friedrich LLP
`100 East Wisconsin Avenue
`Milwaukee, WI 53202-4108 (US)
`Assignee: Sears, Roebuck and Co., Hoffman
`Estates, IL
`Appl. No.:
`10/304.265
`
`(73)
`
`(21)
`(22)
`
`Filed:
`
`Nov. 26, 2002
`
`Publication Classification
`
`(51) Int. Cl." ..................................................... G06F 17/60
`(52) U.S. Cl. .............................................. 705/26: 709/230
`
`(57)
`
`ABSTRACT
`
`Methods and apparatus for organizing product information
`online based on retail Store purchases of the associated
`products are disclosed. The methods and apparatus
`described herein Store product information, Such as product
`identifiers, maintenance agreements, warranty information,
`and product manuals in a product information Server data
`base. Subsequently, actual product purchases are recorded
`by the product information Server based on data from one or
`more point-of-Sale terminals. Individual customerS may then
`acceSS product information associated with his purchases by
`going online, without the need to enter the product infor
`mation or manually identify which products were purchased.
`
`( Start D
`
`500 v-,
`Receive and store product information from
`manufacturer or Seller (e.g., IDs, MAs, warranties, - - 502
`manuals, tips, recalls, "room," etc.)
`
`y
`
`Receive and store customer registration information
`(e.g., user names, passwords, credit card numbers,
`etc.)
`
`y
`Receive and store purchase data from multiple
`points-of-sale (e.g., customer ID, product D, "room,"
`etc.)
`
`504
`
`- 506
`
`--. -
`
`y
`
`Receive login data from a customer (e.g., credit card - 508
`fi, PN, user name, password, etc.)
`
`Receive request for product information associated
`with purchased products or a "room" of purchased
`products
`
`510
`
`--- - -
`
`-.
`
`r
`Transmit requested product information
`
`---. 512
`
`--am--- Receive and store customer entered product - 514
`information
`
`Ymamma
`
`s
`
`Handle request to remove a product from a - 516
`Customer's acCount
`
`y
`Handle reception of a maintenance agreement
`purchase request
`
`y
`Handle reception of a request to synchronize
`maintenance agreements
`
`C Eat)
`
`- 518
`
`—— 520
`
`Lightspeed Ex. 1015.1
`
`

`

`Patent Application Publication May 27, 2004 Sheet 1 of 5
`
`US 2004/0103037 A1
`
`
`
`
`
`
`
`
`
`
`
`
`
`Lightspeed Ex. 1015.2
`
`

`

`CLS
`
`‘pieoqhey
`
`(s)eolAep
`
`
`
`
`
`indulJeyjoJ0o/pue\01‘asnow
`
`wallO
`
`Patent Application Publication May 27, 2004 Sheet 2 of 5
`
`US 2004/0103037 A1
`
`yomMjeu JoyNdwoo
`JOJO JO/PUe JOUIS}UI
`
`801
`
`GOC
`
`
`
`
`
`
`
`soylonu0590z90¢
`
`(s)aoepeyul=vz
`
`vbLe
`
`(s)eo1Aep
`
`
`
`‘Jojuud‘Aedsiq
`
`pusvaqeeds¢Old
`
`
`
`Lightspeed Ex. 1015.3
`
`Lightspeed Ex. 1015.3
`
`
`
`

`

`Patent Application Publication May 27, 2004 Sheet 3 of 5
`
`US 2004/0103037 A1
`
`CO S XJONeujenduoo
`Jeulo JO/pue euleu
`
`CN
`O
`CY)
`
`- O
`d5
`C)
`CS
`t
`9
`
`Sn 9
`w
`S.
`
`wn
`
`r
`CY)
`
`w
`
`9.
`(s
`O
`s
`(s
`?h
`
`CY)
`CD
`-
`
`i
`
`v-
`
`(2 d
`Sco
`S
`O
`
`C
`O
`(5
`
`S O CD
`e is
`5 (?o
`
`S.
`l
`
`CO
`O
`
`g
`CY)
`
`s
`
`Lightspeed Ex. 1015.4
`
`

`

`Patent Application Publication May 27, 2004 Sheet 4 of 5
`
`US 2004/0103037 A1
`
``-gol
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Lightspeed Ex. 1015.5
`
`

`

`Patent Application Publication May 27, 2004 Sheet 5 of 5
`
`US 2004/0103037 A1
`
`500 y
`
`Start
`
`Receive and store product information from
`manufacturer or seller (e.g., Ds, MAS, warranties,
`manuals, tips, recalls, "room," etc.)
`
`- 502
`
`Receive and store customer registration information
`(e.g., user names, passwords, Credit card numbers,
`etc.)
`
`Receive and store purchase data from multiple
`points-of-sale (e.g., customer ID, product D, "room,"
`etc.)
`
`Receive login data from a customer (e.g., credit card
`#, PIN, user name, password, etc.)
`
`Receive request for product information associated
`with purchased products or a "room" of purchased
`products
`
`Transmit requested product information
`
`Receive and store customer entered product
`information
`
`Handle request to remove a product from a
`Customer's account
`
`Handle reception of a maintenance agreement
`purchase request
`
`Handle reception of a request to synchronize
`maintenance agreements
`
`F.G. 5
`
`504
`
`506
`
`508
`
`510
`
`5 1 2
`
`5 1 6
`
`5 1 8
`
`5 2 O
`
`Lightspeed Ex. 1015.6
`
`

`

`US 2004/0103037 A1
`
`May 27, 2004
`
`METHODS AND APPARATUS FOR ORGANIZING
`RETAL PRODUCT INFORMATION
`
`TECHNICAL FIELD
`0001. The present invention relates in general to orga
`nizing retail product information and, in particular, to meth
`ods and apparatus for organizing product information online
`based on retail Store purchases of the associated products.
`
`BACKGROUND
`0002 With the number of retail goods in consumer's
`homes greatly increasing, a need for manageable product
`warranties, maintenance agreements, owner's manuals, and
`other product information has emerged. Efficient use of
`many retail items, Such as dishwashers and lawn mowers,
`requires more than just the initial purchase, installation, and
`use of the product. In addition, a consumer may need to
`repair a product, change a feature, etc. Unfortunately, by the
`time a consumer needs certain product information, the
`paper version which typically accompanies the product may
`be lost. As a result, the consumer may not know if the
`product is under warranty or how to operate a particular
`feature.
`0003. In response, some websites offer online versions of
`user's manuals. However, these websites Suffer from certain
`drawbackS. First, the consumer must locate the product
`information that applies to his purchase, which may require
`extensive Searching acroSS Several websites. Second, once
`located, the website may not have any product information
`beyond the user's manual. Third, unless the consumer
`entered the date of purchase and what warranty and/or
`Service options were purchased, the website will be unable
`to determine the remaining time period and terms of his
`particular agreements.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`0004.
`Features and advantages of the disclosed system
`will be apparent to those of ordinary skill in the art in view
`of the detailed description of exemplary embodiments which
`is made with reference to the drawings, a brief description
`of which is provided below.
`0005 FIG. 1 is a high level block diagram of a commu
`nications System illustrating an exemplary environment of
`use for the present invention.
`0006 FIG. 2 is a more detailed block diagram of one of
`the client devices illustrated in FIG. 1.
`0007 FIG. 3 is a more detailed block diagram showing
`one embodiment of the product information server illus
`trated in FIG. 1.
`0008 FIG. 4 is a more detailed block diagram showing
`one embodiment of the point-of-Sale terminal illustrated in
`FIG. 1.
`0009 FIG. 5 is a flowchart of a process for organizing
`product information online based on retail Store purchases of
`the associated products.
`
`DETAILED DESCRIPTION OF EXEMPLARY
`EMBODIMENTS
`0010. In general, the system described herein stores prod
`uct information, Such as product identifiers, maintenance
`
`agreements, warranty information, and product manuals in a
`product information Server database. Subsequently, actual
`product purchases are recorded by the product information
`Server based on data from one or more point-of-Sale termi
`nals. Individual customerS may then access product infor
`mation associated with his purchases by going online, with
`out the need to enter the product information or manually
`identify which products were purchased.
`0011. A high level block diagram of an exemplary net
`work communications System 100 capable of employing the
`teachings of the present invention is illustrated in FIG. 1.
`Typically, the system 100 includes one or more client
`devices 102, one or more product information servers 104,
`and one or more point-of-sale terminals 106. Each of these
`devices may communicate with each other via a connection
`to one or more communications channels 108 Such as the
`Internet or Some other wide area network.
`0012 Typically, the product information server 104
`Stores a plurality of files, programs, and/or web pages for use
`by the client devices 102 and/or the point-of-sale terminals
`106. One product information server 104 may interact with
`a large number of clients 102 and point-of-Sale terminals
`106. Accordingly, each server 104 is typically a high end
`computer with a large Storage capacity, one or more fast
`microprocessors, and one or more high Speed network
`connections. Conversely, relative to a typical Server 104,
`each client device 102 and each point-of-sale terminal 106
`typically includes leSS Storage capacity, a single micropro
`ceSSor, and a Single network connection.
`0013 A more detailed block diagram of a client device
`102 is illustrated in FIG. 2. The client device may be a
`personal computer (PC), a personal digital assistant (PDA),
`an Internet appliance, a cellular telephone, or any other
`communication device. The client 102 includes a controller
`202 which preferably includes a central processing unit 204
`electrically coupled by an address/data bus 206 to a memory
`device 208 and an interface circuit 210. The CPU 204 may
`be any type of well known CPU, such as an Intel Pen
`tiumTM processor. The memory device 208 preferably
`includes volatile memory and non-volatile memory. Prefer
`ably, the memory device 208 stores a software program that
`interacts with the product information server 104 as
`described below. This program may be executed by the CPU
`204 in a well known manner. The memory device 208 may
`also Store digital data indicative of documents, files, pro
`grams, web pages, etc. retrieved from a server 104, 106
`and/or loaded via an input device 212.
`0014. The interface circuit 210 may be implemented
`using any type of well known interface Standard, Such as an
`Ethernet interface and/or a Universal Serial Bus (USB)
`interface. One or more input devices 212 may be connected
`to the interface circuit 210 for entering data and commands
`into the controller 202. For example, the input device 212
`may be a keyboard, mouse, touch Screen, track pad, track
`ball, isopoint, and/or a voice recognition System.
`0015. One or more displays, printers, speakers, and/or
`other output devices 214 may also be connected to the
`controller 202 via the interface circuit 210. The display 214
`may be cathode ray tube (CRTs), liquid crystal displays
`(LCDs), or any other type of display. The display 214
`generates Visual displays of data generated during operation
`of the client 102. The display 214 is typically used to display
`
`Lightspeed Ex. 1015.7
`
`

`

`US 2004/0103037 A1
`
`May 27, 2004
`
`web pages received from the product information Server
`104. The visual displays may include prompts for human
`operator input, run time Statistics, calculated values,
`detected data, etc.
`0016. The client 102 may also exchange data with other
`devices via a connection to the network 108. The network
`connection may be any type of network connection, Such as
`an Ethernet connection, digital Subscriber line (DSL), tele
`phone line, coaxial cable, etc. Users of the system 100 may
`be required to register with the product information Server
`104. In Such an instance, each user may choose a user
`identifier and a password which may be required for the
`activation of Services. The user identifier and password may
`be passed across the Internet 108 using encryption built into
`the user's browser. Alternatively, the user identifier and/or
`password may be assigned by the product information Server
`104.
`0.017. A more detailed block diagram of a product infor
`mation server 104 is illustrated in FIG. 3. Like the client
`device 102, the controller 302 in the server 104 preferably
`includes a central processing unit 304 electrically coupled
`by an address/data bus 306 to a memory device 308 and a
`network interface circuit 310. However, the sever controller
`302 is typically more powerful than the client controller 202.
`Again, the CPU 304 may be any type of well known CPU,
`such as an Intel PentiumTM processor, and the memory
`device 308 preferably includes volatile memory and non
`volatile memory. Preferably, the memory device 308 stores
`a Software program that implements all or part of the method
`described below. This program may be executed by the CPU
`304 in a well known manner. However, some of the steps
`described in the method below may be performed manually
`or without the use of the server 104. The memory device 308
`and/or a separate database 314 also Store files, programs,
`web pages, etc. for use by other Servers 104, point-of-Sale
`terminals 106, and/or the client devices 102. Preferably the
`database 314 Stores product information, customer informa
`tion, purchase data, login data, request logs, and other data.
`0.018. The server 104 may exchange data with other
`devices via a connection to the network 108. The network
`interface circuit 310 may be implemented using any data
`transceiver, Such as an Ethernet transceiver. The network
`108 may be any type of network, such as a local area
`network (LAN) and/or the Internet.
`0019. A more detailed block diagram of a point-of-sale
`terminal 106 is illustrated in FIG. 4. Preferably, the point
`of-Sale terminal 106 is a cash register and/or a personal
`computer executing point-of-Sale Software. The point-of
`sale terminal 106 includes a controller 402 which preferably
`includes a central processing unit 404 electrically coupled
`by an address/data bus 406 to a memory device 408 and an
`interface circuit 410. The CPU 404 may be any type of well
`known CPU, such as an Intel Pentium TM processor. The
`memory device 408 preferably includes volatile memory
`and non-volatile memory. Preferably, the memory device
`408 stores a software program that interacts with the product
`information server 104 as described below. This program
`may be executed by the CPU 404 in a well known manner.
`The memory device 408 may also store other data retrieved
`from a server 104 and/or loaded via an input device 412.
`0020. The interface circuit 410 may be implemented
`using any type of well known interface Standard, Such as an
`
`Ethernet interface and/or a Universal Serial Bus (USB)
`interface. One or more input devices 412 may be connected
`to the interface circuit 410 for entering data and commands
`into the controller 402. For example, the input device 412
`may be a keyboard, mouse, touch Screen, credit card reader,
`debit card reader, Smart card reader, track pad, track ball,
`isopoint, and/or a voice recognition System.
`0021 One or more displays, printers, speakers, and/or
`other output devices 414 may also be connected to the
`controller 402 via the interface circuit 410. The display 414
`may be cathode ray tube (CRTs), liquid crystal displays
`(LCDs), or any other type of display. The display 414
`generates Visual displays of data generated during operation
`of the point-of-sale terminal 106. The display 414 is typi
`cally used to display Sales data during checkout of a retail
`customer. For example, the Visual displayS may include
`prompts for clerk input, customer input, running totals,
`product descriptions, etc.
`0022. A flowchart of a process 500 for organizing product
`information online based on retail Store purchases of the
`associated products is illustrated in FIG. 5. Preferably, the
`process 500 is embodied in a software program which is
`stored in the product information server memory 308 and
`executed by the server CPU 304 in a well known manner.
`However, some or all of the steps of the process 500 may be
`performed manually and/or by another device. Although the
`process 500 is described with reference to the flowchart
`illustrated in FIG. 5, a person of ordinary skill in the art will
`readily appreciate that many other methods of performing
`the acts associated with process 500 may be used. For
`example, the order of many of the Steps may be changed
`without departing from the Scope or Spirit of the present
`invention. In addition, many of the StepS described are
`optional.
`0023 Generally, the process 500 causes the product
`information server 104 to receive and store product infor
`mation, Such as product identifiers, maintenance agree
`ments, warranty information, and product manuals in the
`product information server database 314. Subsequently,
`actual product purchases are recorded by the product infor
`mation server 104 based on data from one or more point
`of-Sale terminals 106. Each customer may then access
`product information associated with his purchases by going
`online, without the need to enter the product information or
`manually identify which products were purchased.
`0024. The process 500 begins when the product informa
`tion server 104 receives and stores product information from
`one or more product manufacturers and/or Sellers (step 502).
`Preferably, the product information is received by the inter
`face circuit 310 and stored in the database 314. Product
`information preferably includes product identifiers, mainte
`nance agreements, warranty information, product manuals,
`troubleshooting tips, recall data, “room' designators, and/or
`any other data associated with the product(s) (step 502).
`0025 Aproduct identifier is a digital string (i.e., numbers
`and/or letters) which distinguishes one product from another
`product. Some product identifiers uniquely identify the
`product (e.g., a serial number). Some product identifiers
`merely distinguish a type and/or family of products from
`another type and/or family of products (e.g., a model num
`ber). A maintenance agreement is a service contract which
`includes terms and/or conditions associated with the Servic
`
`Lightspeed Ex. 1015.8
`
`

`

`US 2004/0103037 A1
`
`May 27, 2004
`
`ing of a product. For example, a customer may purchase an
`annual tune up for a lawnmower at the time S/he purchases
`the lawn mower. Similarly, a customer may receive an
`option for a maintenance Service at a locked in price in
`eXchange for purchasing the product. For example, a cus
`tomer may receive “free” oil changes for five years with the
`purchase of an automobile.
`0.026 Warranty information preferably includes one or
`more warranty durations and terms of coverage. For
`example, the engine of a lawnmower may be guaranteed for
`two years. Preferably, product manuals are digital versions
`of paper manuals (e.g., PDF files) including a table of
`contents, an index, diagrams, descriptions, etc. Trouble
`shooting tips are text descriptions and/or diagrams of what
`a customer may do on his own to resolve certain common
`problems. For example, if the engine of the lawn mower is
`not starting, the customer may be asked to check the fuel
`level, depress the primer, etc. Troubleshooting tips may be
`included I the manual.
`0.027
`Preferably, recall data include products identifiers
`of recalled products, information regarding the reason for
`the recall, a telephone number to contact with questions,
`and/or where to return the product. A “room' designator is
`a String which categorizes the product. For example, a
`number indicative of kitchen, laundry, entertainment,
`garage, tool shed, and/or yard may be used to group Similar
`products together. The room designator facilitates online
`organization of purchased products as described in detail
`below.
`0028. In addition to product information, the product
`information server 104 preferably receives and stores cus
`tomer registration information (Step 504). Customer regis
`tration information preferably includes a unique customer
`identifier for each registered customer. For example, a user
`name, password, credit card number, and/or other identifi
`cation String may be used as a customer identifier. In one
`embodiment, the customer enters the registration informa
`tion via a client device 102. In another embodiment, the
`product information Server 104 automatically registers a
`user in response to a customer identifier from a point-of-Sale
`terminal 106. For example, the first time a customer pur
`chasers a product from a retailer associated with the System
`100, the point-of-sale terminal 106 may send a product
`identifier indicative of the purchased product (e.g., "Ken
`more refrigerator Model # 12345A) and a customer identi
`fier (e.g., the credit card number used to purchase the
`product) to the product information server 104 via the
`network 108. In response, the product information server
`104 may create an account for the customer which includes
`the customer identifier and the product identifier.
`0029. In addition, the point-of-sale terminal 106 may
`print out a personal identification number (PIN) and/or
`instructions on how to access the automatically generated
`account. Further, the clerk operating the point-of-Sale ter
`minal 106 may be given on-Screen instructions to explain
`usage of the new account to the customer. For example, the
`printed instructions and/or the displayed instructions may
`include a web address, an indication that the default user
`name is the credit card number used to make the purchase,
`and an indication that the default password is the PIN
`number. The PIN number may be generated by the server
`104 or the point-of-sale terminal 106. The customer may
`
`change the username and password via a client device 102
`after a Successful login. In addition, customers using more
`than one credit card may consolidate accounts via a web
`page provided to a client device 102.
`0030 Product identifiers associated with Subsequent pur
`chases from associated retailers using the same credit card
`(or other customer ID) are automatically added to the
`existing account when a point-of-Sale terminal 106 sends the
`additional product identifiers to the product information
`server 104 via the network 108 (step 506). In this manner,
`product information Such as maintenance agreements, war
`ranty information, product manuals etc. may be conve
`niently organized for a customer automatically based on
`actual customer purchases from retail Stores. The user does
`not have to enter the product information or the product
`identifiers.
`0031. After one or more purchases are made, the cus
`tomer may login to the product information server 104 in a
`well known manner (step 508). For example, the customer
`may enter his credit card number and PIN. Similarly, the
`customer may enter his usemame and password to login. In
`response to a Successful login, a request for product infor
`mation, and/or a request for a "room” of information (Step
`510), the product information server 104 preferably trans
`mits the requested product information to the customer's
`client device 102 (step 512).
`0032. Once a customer is logged in, the product infor
`mation Server 104 may handle additional customer requests.
`For instance, the product information server 104 may
`receive and Store customer entered product information (Step
`514). For example, the customer may enter a product
`identifier S/he would like added to his/her account that was
`not automatically entered (e.g., S/he paid cash or purchased
`the product from another retailer). Similarly, a customer may
`delete product information from his account (step 516). For
`example, a product which the customer no linger owns may
`be removed from the account.
`0033. In addition, the product information server 104
`may handle reception of maintenance agreement purchase
`requests (step 518) and/or handle reception of a request to
`Synchronize maintenance agreements (Step 520). For
`example, if a first maintenance agreement is Set to expire in
`two months and a Second maintenance agreement is Set to
`expire in Six months, the customer may which to extend the
`first maintenance agreement by fourteen months and the
`Second maintenance agreement by ten months. So that both
`maintenance agreements expire at the Same time.
`0034) Still further, the product information server 104
`may be programmed to transmit an e-mail message to a
`client device 102 prior to an expiration date associated with
`product information and/or in response to a product recall.
`Preferably, the e-mail message includes at least a portion of
`the product information and the relevant date. Optionally,
`individual customers may enable or disable this notification
`function.
`0035) In Summary, persons of ordinary skill in the art will
`readily appreciate that a method and apparatus for organiz
`ing product information online based on retail Store pur
`chases of the associated products has been provided. Users
`of Systems implementing the teachings described herein can
`enjoy easy access to online product information, Such as
`
`Lightspeed Ex. 1015.9
`
`

`

`US 2004/0103037 A1
`
`May 27, 2004
`
`maintenance agreements, warranty information, and product
`manuals, without the need to enter the product information
`or manually identify which products were purchased.
`0.036 The foregoing description has been presented for
`the purposes of illustration and description. It is not intended
`to be exhaustive or to limit the invention to the exemplary
`embodiments disclosed. Many modifications and variations
`are possible in light of the above teachings. It is intended that
`the scope of the invention be limited not by this detailed
`description, but rather by the claims appended hereto.
`What is claimed is:
`1. A method of organizing retail product information, the
`method comprising the Steps of
`receiving first product information associated with a first
`product, the first product information including a first
`product identifier and at least one of a first product
`maintenance agreement, a first product warranty, a first
`product owner's manual, first product troubleShooting
`tips, a first product parts list, and first product recall
`information;
`receiving Second product information associated with a
`Second product, the Second product information includ
`ing a Second product identifier and at least one of a
`Second product maintenance agreement, a Second prod
`uct warranty, a Second product owner's manual, Second
`product troubleShooting tips, a Second product parts
`list, and Second product recall information;
`receiving third product information associated with a third
`product, the third product information being different
`than the first product information, the third product
`information including a third product identifier and at
`least one of a third product maintenance agreement, a
`third product warranty, a third product owner's manual,
`third product troubleshooting tips, a third product parts
`list, and third product recall information;
`receiving first customer registration information from a
`first customer, the first customer registration informa
`tion including a first customer identifier;
`receiving Second customer registration information from
`a Second customer, the Second customer registration
`information including a Second customer identifier;
`receiving first purchase data from a first point-of-Sale
`device in response to a first retail purchase of the first
`product by the first customer, the first purchase data
`including the first product identifier and the first cus
`tomer identifier;
`receiving Second purchase data from a Second point-of
`Sale device in response to a Second retail purchase of
`the Second product by the Second customer, the Second
`purchase data including the Second product identifier
`and the Second customer identifier, the Second point
`of-sale device being different than the first point-of-sale
`device, the Second customer identifier being different
`than the first customer identifier;
`receiving third purchase data from a third point-of-Sale
`device in response to a third retail purchase of the third
`product by the first customer, the third purchase data
`including the third product identifier and the first cus
`tomer identifier, the third point-of-Sale device being
`
`different than the first point-of-sale device and the
`Second point-of-Sale device;
`receiving login data from a Internet client device, the
`login data including the first customer identifier; and
`transmitting at least a portion of the first product infor
`mation and at least a portion of the third product
`information to the Internet client device in response to
`receiving the login data from the Internet client device.
`2. A method as defined in claim 1, wherein the Step of
`receiving first customer registration information including a
`first customer identifier comprises receiving a credit card
`number.
`3. A method as defined in claim 1, further comprising the
`Step of transmitting an e-mail message to the Internet client
`device prior to an expiration date associated with the first
`product information, the e-mail message including at least a
`portion of the first product information and the expiration
`date.
`4. A method as defined in claim 1, further comprising the
`Step of transmitting an e-mail message to the Internet client
`device, the e-mail message including at least a portion of the
`first product information and a product recall notice.
`5. A method as defined in claim 1, further comprising the
`Step of receiving fourth product information from the Inter
`net client device, the fourth product information being
`manually entered into the Internet client device by the first
`CuStOmer.
`6. A method as defined in claim 5, wherein the step of
`receiving fourth product information includes the Step of
`receiving a date associated with a maintenance event.
`7. A method as defined in claim 1, further comprising the
`Step of receiving a maintenance agreement purchase request
`from the Internet client device.
`8. A method as defined in claim 7, further comprising the
`Step of receiving a request to Synchronize maintenance
`agreements associated with the first product and the third
`product.
`9. A method as defined in claim 8, further comprising the
`Step of transmitting an end date associated with request to
`Synchronize.
`10. A method as defined in claim 1, further comprising the
`Step of allowing the first customer to remove the first product
`identifier from an account associated with the first customer.
`11. A method as defined in claim 1, further comprising the
`Step of Storing the first product information in association
`with a room identifier.
`12. A method as defined in claim 11, wherein the step of
`Storing the first product information comprises the Step of
`Storing the first product information in association with a
`room identifier, the room identifier being inductive of at least
`one of kitchen, laundry, entertainment, garage, tool shed,
`and yard.
`13. A method as defined in claim 11, wherein the step of
`transmitting at least a portion of the first product information
`and at least a portion of the third product information to the
`Internet client device comprises the Step of transmitting data
`indicative of the room identifier.
`14. An apparatus Structured to organize retail product
`information, the apparatus comprising:
`an Internet receiver;
`an Internet transmitter
`
`Lightspeed Ex. 1015.10
`
`

`

`US 2004/0103037 A1
`
`May 27, 2004
`
`a processing unit operatively coupled to the Internet
`receiver and the Internet transmitter; and
`a memory device operatively coupled to the processing
`unit, the memory device Storing a Software program
`Structured to cause the processing unit to:
`receive first product information associated with a first
`product via the Internet receiver, the first product
`information including a first product identifier and at
`least one of a first product maintenance agreement, a
`first product warranty, a first product owner's manual,
`first product troubleShooting tips, a first product parts
`list, and first product recall information;
`receive Second product information associated with a
`Second product via the Internet receiver, the Second
`product information being different than the first prod
`uct information, the Second product information includ
`ing a Second product identifier and at least one of a
`Second product maintenance agreement, a Second prod
`uct warranty, a Second product owner's manual, Second
`product troubleShooting tips, a Second product parts
`list, and Second product recall information;
`receive customer registration information via the Internet
`receiver, the customer registration information includ
`ing a customer identifier;
`re