Non-serialized electronic product registration system and method of operating same
||Non-serialized electronic product registration system and method of operating same
||Cheney, et al.
||April 29, 2014
|Attorney Or Agent:
||Nixon & Vanderhye P.C.
||705/26.8; 705/14.24; 705/22; 705/26.1; 705/340
|Field Of Search:
||;705/26; ;705/26.1; ;705/340; ;705/14
|U.S Patent Documents:
|Foreign Patent Documents:
||3 315 724; 0 068 642; 0 191 636; 0 286 130; 0 349 284; 0 845 749; 0 862 154; 2 559 599; 2 143 662; 2 203 879; 2 209 157; 2 209 158; 02-139698; 405178422; 405342482; 10188141; 11066176; 87/00948; 88/02524; 88/06771; 89/09460; 92/01273; 99/33016
||Information Disclosure Statement filed in U.S. Appl. No. 09/509,021, on Oct. 26, 2001. cited by applicant.
Information Disclosure Statement filed in U.S. Appl. No. 09/065,552, on Jul. 19, 1999. cited by applicant.
Information Disclosure Statement filed in U.S. Appl. No. 08/725,259, on Oct. 5, 1998. cited by applicant.
1994 Nintendo Product Returns Policies and Procedures. cited by applicant.
1995 Nintendo Product Returns Policies and Procedures. cited by applicant.
1996 Nintendo Product Returns Policies and Procedures. cited by applicant.
1992 Nintendo Product Returns Policy. cited by applicant.
John Longwell, "Robec Links Its 18 Sales Facilities Via Newly Adopted NetWare System", Computer Reseller News, Sep. 6, 1993. cited by applicant.
Software Maker Promises Many Happy Returns, Drug Topics, Mar. 4, 1996, vol. 140, No. 5, pp. 124-128. cited by applicant.
Direct Return 2000, Software Overview, http://www.directreturn.com/software.sub.--overview.htm, Oct. 2, 2000. cited by applicant.
Amazon.com Returns Policy, Our Return Policy is Simple, Jun. 20, 2000, Amazon.com, www.amazon.com/exec/obidos/subst/help/returns-policy.html, pp. 1-2. cited by applicant.
Leyden, "Burgled mum finds stolen iPod on eBay," The Register, May 17, 2005, 1 page. cited by applicant.
"Man accused in Lego selling scam," http://www.kptv.com/Global/story.asp?S=4137050&nav=munil56.sub.--2, Nov. 18, 2005, 1 page. cited by applicant.
Grace, "Reseller Profile--Reynolds and Reynolds; Reynolds goes extra mile--Evolving solutions continue to fuel clients' capabilities", Computer Reseller News, CMP Publications, Inc., Feb. 21, 1994, 2 pages. cited by applicant.
PR Newswire, "CompuServe Introduces Electronic Product Registration Software", PR Newswire Association, Inc., Mar. 10, 1994, 2 pages. cited by applicant.
Longwell, "Western Digital Wins--Price/performance gives driver maker victory margin", Computer Reseller News, CMP Publications, Inc., Jun. 28, 1993, 3 pages. cited by applicant.
Grace, "ABCD Looks to Adopt EDI Transaction Sets", Computer Reseller News, CMP Publications, Inc., Jun. 28, 1993, 2 pages. cited by applicant.
Discount Store News, "New Policy System can Par Suspect Returns, Cut Losses", Discount Store News, Lebhar-Friedman Inc., Jan. 1, 1996, 2 pages. cited by applicant.
Synchronics.RTM. User Manual: Point of Sale, Version 6.5, Apr. 1993 (ON 004464-ON 005116). cited by applicant.
Synchronics.RTM. User Manual: Inventory Plus, Version 6.5, Apr. 1993 (ON 005117-ON 005892). cited by applicant.
Dranov, Paula, Automated Library Circulation Systems, 1977-1978, pp. 24-47 (ON 001905-ON 001929). cited by applicant.
Hoadley, Irene Braden and A. Robert Thorson, An Automated On-Line Circulation System: Evaluation, Development, Use, 1973, 19 pp. (ON 001930-ON 001948). cited by applicant.
Meyer, James, "NOTIS: The System and Its Features", Library Hi Tech, Issue 10, vol. 3, No. 2, 1985, pp. 81-89 (ON 001949-ON 001959). cited by applicant.
Dowlin, Kenneth E., "Maggie III: The Prototypical Library System", Library Hi Tech, Issue 16, vol. 4, No. 4, Winter 1986, pp. 7-15 (ON 001960-ON 001970). cited by applicant.
Matthews, Joseph R., "Graphical User Interfaces GUI in Library Products", Library Technology Reports, vol. 32, No. 1, Jan. 1996, p. 53 (ON 001972-ON 001976). cited by applicant.
Saffady, William, "Integrated Library Systems for Microcomputers and Mainframes: A Vendor Study", Library Techology Reports, vol. 30, No. 1, Jan. 1994, p. 5 (ON 001977-ON 002087). cited by applicant.
Saffady, William, "Vendors of Integrated Library Systems for Minicomputers and Mainframes: An Industry Report, part 1", Library Technology Reports, vol. 33, No. 2, Mar. 1997, p. 161 (ON 002088-ON 002096). cited by applicant.
Saffady, William, "Vendors of Integrated Library Systems for Microcomputers and Mainframes: An Industry Report, part 2", Library Techology Reports, vol. 33, No. 3, May 1997, p. 277 (ON 002097-ON 002138). cited by applicant.
Direct Return 2000, Software Overview, http://www.directreturn.com/software.sub.--overview.htm, Copyright .COPYRGT. 2000 Pharmacy Software Solutions, Inc. cited by applicant.
"Retailing in Cyberspace", Narda News, Apr. 1995, pp. 21-22. cited by applicant.
PR Newswire, "Escada Offers a Garden Variety for Spring", PR Newswire Association, Inc., Mar. 10, 1994, 2 pages. cited by applicant.
Automotive News, "Reynolds, ADP differ on superhighway progress", Crain Communications, Inc., Apr. 11, 1994, 3 pages. cited by applicant.
Computer Reseller News, "Case Study; Tapping the Channel's `Best in Class`", CMP Publications, Inc., Jan. 30, 1995, 2 pages. cited by applicant.
Rigney, "User Migrates to Windows NT", InternetWeek, CMP Publications, Inc., Jan. 10, 1994, 2 pages. cited by applicant.
Business Wire, "Multimillion-dollar Health-care Products", Business Wire, Inc., Dec. 15, 1993, 2 pages. cited by applicant.
Margulis, "Reclaim: an efficient way to handle damaged products", U.S. Distribution Journal, BMT Publications Inc., Mar. 15, 1992, 7 pages. cited by applicant.
Jiji Press Ticker Service, "MITI Working Out Business Practice Guidelines", JiJi Press Ltd., Apr. 20, 1990, 1 page. cited by applicant.
Jiji Press Ticker Service, "JCCI Issues Booklet to Explain Distribution", JiJi Press Ltd., Jul. 20, 1989, 1 page. cited by applicant.
Business Wire, "Aztech Labs Inc. is Chosen as Business Depot's `Vendor of the Year`; Canadian Company Honors Multimedia Hardware Manufacturer as Number One in Computer Category", Business Wire, Inc., May 6, 1996, 2 pages. cited by applicant.
LaPlante, "Rugby Darby; From proprietary host to a distributed LAN-based architecture in 2 years", InfoWorld, InfoWorld Media Group, Nov. 15, 1993, 4 pages. cited by applicant.
Witt et al., "Distribution: a differentiator in 2000", Material Handling Engineering, Penton Publishing Inc., Oct. 1995, 15 pages. cited by applicant.
Grotta, "Return to vendor: the right way to make mail-order returns", PC Sources, Information Access Company, a Thomson Corporation Company, ASAP Coastal Associates Publishing L.P., Feb. 1992, 10 pages. cited by applicant.
Business Wire, "DataTrend receives award from AT&T Global Information Solutions", Business Wire, Inc., Nov. 7, 1995, 2 pages. cited by applicant.
Quinn, "Why Wang took the third-party route", Information Access Company, a Thomson Corporation Company, ASAP Reed Publishing USA, vol. 30, No. 2, p. 30, Feb. 1991. cited by applicant.
Rogers et al., "Going Backwards: Reverse Logistics Trends and Practices", Reverse Logistics Executive Council, 1998 (entire book). cited by applicant.
IBM Systems Journal, vol. 14, No. 1, 1975, pp. 1-101. cited by applicant.
CollegeTermPapers web page printout, "History of Fed Ex", www.collegetermpaper...rmPapers/Aviation/history.sub.--of.sub.--fed.sub.-- -ex.html (Aug. 24, 2001), 7 pages. cited by applicant.
Rosenbloom, "Midnight Express", Inc., Jul. 2001, 4 pages. cited by applicant.
Sleeper, "FedEx Pushes The Right Buttons to Remain No. 1 in Fast Shipping", Investor's Business Daily, May 25, 2001, 2 pages. cited by applicant.
Brewin et al., "Follow That Packager!", Computer World, vol. 35, No. 12, Mar. 19, 2001, 4 pages. cited by applicant.
Joachim, "FedEx Delivers on CEO's IT Vision", InternetWeek, Oct. 25, 1999, 4 pages. cited by applicant.
Sigafoos et al., "Absolutely Positively Overnight!: The Unofficial Corporate History of Federal Express", St. Luke Press, 1988, pp. 1-22. cited by applicant.
Witt, "How to Master the Art of Returns: Automation Is the Key", Material Handling Engineering, Jun. 1994, pp. 58-60. cited by applicant.
Dilger, "The Other Direction", Manufacturing Systems, vol. 15, No. 10, pp. 12-13 (Oct. 1997). cited by applicant.
"Computer City Moves to Consolidate Returns", Computer Retail Systems, vol. 6, No. 125, Jan. 22, 1998, 2 pages. cited by applicant.
Dreamcom web page printout, www.dreamcomdirect.com/RMA.htm (May 25, 1997). cited by applicant.
Consumer Electronics, Consumer Electronics Personals, vol. 35, No. 6, p. 18., Copyright 1995 Warren Publishing, Inc. cited by applicant.
Cooper, Michael D., Design of Library Automation Systems, pp. 83-109, (ON 001859-ON 001873), (at least as early as Oct. 2001). cited by applicant.
Corbin, John, Developing Computer-Based Library Systems, pp. 144-149, (ON 001874-ON 001877); Copyright 1981. cited by applicant.
DataPhase, Inc. Automated Circulation System, 43 pp., (ON 001878-ON 001904), (at least as early as May 2008). cited by applicant.
Grosch, Audrey N., Distributed Computing and the Electronic Library: Micros to Superminis, pp. 78-79, (ON 002144-ON 002146); Copyright 1985. cited by applicant.
Nintendo Point of Purchase Mail-In Card, (at least as early as Dec. 1992). cited by applicant.
Reynolds, Dennis, Library Automation: Issues and Applications, pp. 42-49 and pp. 146-149, (ON 002147-ON 002153); Copyright 1985. cited by applicant.
Salmon, Stephen R., Library Automation Systems, p. 239, (ON 002154-ON 002155); Copyright 1975. cited by applicant.
Salton, Gerard, Dynamic Information and Library Processing, pp. 62-69, (ON 002139-ON 002143); Copyright 1975. cited by applicant.
Synchronics Software Product Information guide, 95 pages; Copyright 1992. cited by applicant.
Collins, David Jarrett and Nancy Nasuti Whipple, Using Bar Code: Why It's Taking Over, Second Edition (ON 003696-ON 004031); Copyright 1990. cited by applicant.
Birnbaum, Henry, General Information Manual: IBM Circulation Control at Brooklyn College Library, 29 pp., (ON 001822-ON 001848); Copyright 1960. cited by applicant.
White, Howard S., Library Technology Reports, Mar. 1982, vol. 18, No. 2, pp. 178-184 (ON 001851-ON 001858). cited by applicant.
||A non-serialized electronic product registration (ER) system and method which enables return qualification information to be provided upon request for non-serialized products. Retailer specific return policies are enforced by providing the ER system with retailer return policies for UPCs, SKUs, model numbers and/or other non-unique product identifiers. The retailer periodically provides information to the ER system that indicates the last date on which products having a particular non-unique identifier have been sold. The ER system then determine the last date on which such products can be returned and provides non-serialized return qualification information to the retailer upon request.
||What is claimed is:
1. An electronic product registration method for use with non-serialized products, comprising: receiving product information at a computerized electronic registration (ER)system including a database for registration, the product information identifying at least one non-serialized product type that has been sold; associating a registration date with the at least one non-serialized product type via the ER system; determining, via a computer system of the ER system and based on the product information and applicable return criteria, a last date on which a non-serialized product belonging to the at least one non-serialized product type can be accepted for returnunder the applicable return criteria, said last date being determined in relation to the registration date associated with the non-serialized product type; and providing, via the computer system and in response to an inquiry to the electronicregistration system, an indication as to whether a non-serialized product belonging to at least one of the non-serialized product types might qualify for return under the applicable return criteria when the inquiry is made.
2. The method of claim 1, wherein the product information is received at the electronic product registration system on a daily basis, the product information including a product identifier for each type of product sold that day.
3. The method of claim 1, wherein products of the same type share a common non-unique identifier.
4. The method of claim 3, wherein the common non-unique identifier is a UPC.
5. The method of claim 1, wherein said receiving includes receiving a UPC for the at least one non-serialized product.
6. The method of claim 1, wherein the indication specifies the last date on which the non-serialized product can be accepted for return under the applicable return criteria.
7. The method of claim 1, further comprising enabling the electronic product registration system to respond to return/warranty inquiries that involve serialized products, as well as non-serialized products.
8. The method of claim 7, further comprising determining whether an inquiry relates to a serialized product or a non-serialized product.
9. The method of claim 8, wherein the determination as to whether an inquiry relates to a serialized product or a non-serialized product is based at least in part on the content of the relevant inquiry.
10. The method of claim 1, wherein the electronic registration system is located remotely from a location where the non-serialized product is presented for return.
11. The method of claim 1, wherein the product information is received from, and the indication is transmitted to, a retail sales location.
12. An electronic product registration method for use with non-serialized products, comprising: transmitting product information to a computerized electronic registration (ER) system including a database for registration, the productinformation identifying at least one non-serialized product type that has been sold; causing a registration date to be associated with the at least one non-serialized product type via the ER system; sending an inquiry to the electronic registrationsystem when a non-serialized product belonging to at least one of the non-serialized product types is presented in connection with a post-sale return and/or warranty request; causing a determination to be made, in connection with a computer system ofthe ER system and based on the product information and applicable return criteria, as to a last date on which the non-serialized can be accepted for return under the applicable return criteria receiving, from the computer system and in response to theinquiry, an indication as to whether the non-serialized product might qualify for return under applicable return criteria when the inquiry is made.
13. The method of claim 12, wherein said last date is determined in relation to the registration date associated with the product's non-serialized product type.
14. The method of claim 12, wherein the product information is transmitted to the electronic product registration system on a daily basis.
15. The method of claim 12, wherein products of the same type share a common non-unique identifier.
16. The method of claim 15, wherein the common non-unique identifier is a UPC.
17. The method of claim 12, wherein the indication specifies the last date on which the non-serialized product can be accepted for return under the applicable return criteria.
18. The method of claim 12, further comprising sending to the electronic product registration system inquiries that involve serialized products or non-serialized products.
19. The method of claim 12, wherein the electronic registration system is located remotely from a location where the non-serialized product is presented for return.
20. The method of claim 19, wherein the indication is transmitted to a retail sales location.
||BACKGROUND AND SUMMARY OF THE INVENTION
The present invention relates to electronic registration systems for purchased products. More particularly, the invention relates an improved electronic product registration system that enables non-serialized products to be effectively andefficiently incorporated into electronic registration systems.
Electronic registration (ER) systems enable eligibility information regarding return, warranty, replacement and/or repair of previously purchased products to be collected, stored and accessed for the primary purpose of enforcing policiesregarding same. Exemplary electronic product registration (ER) systems are disclosed in U.S. Pat. Nos. 5,978,774 and 6,018,719, the disclosures of which are incorporated by reference herein in their entirety.
Electronic registration (ER) systems have, in the past, relied on the use of a unique identifier, such as a serial number, for each product that is purchased. The serial number is obtained at the point of sale for inclusion in a registrationdatabase, together with other information, such as a date of transaction. This database can then be accessed in connection with an attempted product return/warranty transaction for the purpose of determining if the product qualifies for return/warrantyunder applicable return/warranty criteria (which are also stored in or made available to the ER system). Such electronic registration systems may also be used in connection with repair and/or exchange transactions, in addition to returns, by enabling anaccurate determination as to whether the product qualifies for any of these actions under the appropriate policies and criteria under which the product was originally sold.
The ER system uses pre-established return/repair policies and procedures that are programmed into the system so that the system can perform a check when a product is presented for return to determine if the product qualifies for return,replacement and/or warranty repair based on sales transaction information available in the ER system for the particular product at issue. Thus, known ER systems include a database of return qualification information (or warranty/replacement criteria)for various manufacturer's and/or retailers that enables the system to make an accurate determination with respect to whether or not a particular product or item (that is uniquely identified by the system using a serial number or other unique identifier)actually qualifies for return (or warranty/replacement) based on the appropriate qualification criteria. Such ER systems have greatly reduced improper and fraudulent returns and warranty claims.
ER systems have, in the past, used a unique identifier for each product that is registered, thereby enabling the system to provide return qualification information with respect to the particular product being returned. Voice recognition,dial-in or internet systems are used to access the ER database to obtain information on registered products. For example, the ER system may be accessed at the time a product is being presented for return in order to obtain return qualificationinformation for that specific product. An example of a voice recognition (VRU) system that uses serial numbers to access an ER system is disclosed in PCT application No. PCT/US01/25296 filed Aug. 14, 2001 , and entitled "Voice Recognition Method andApparatus Using Dynamic Link Library", the disclosure of which is incorporated by reference herein. Due to the fact that the ER systems have been based on serialized products (i.e., products each having a unique serial number), the access systems usedtherewith have also been based on the use of serial numbers.
Due to the serialized nature of previous ER systems, products that do not include a unique identifier associated therewith have not been able to be incorporated into such ER systems. As a result, such non-serialized products have not been ableto enjoy the many benefits provided by ER systems.
While ER systems have proven to be very useful in their current forms, additional improvements in such systems are still desired in order to provide additional functionality that will benefit customers, retailers and/or manufacturers. Thus,improvements in ER systems are needed in order to enable effective use thereof for non-serialized products, as well as serialized products. To this end, the instant invention provides an improved ER system that has increased functionality, by providingan enhancement to known ER systems that enables information on non-serialized products (i.e., products that do not have a unique identifier) to be incorporated into an ER system. The instant invention provides an improved ER system that enablesnon-serialized products to be easily and effectively incorporated into ER systems. The term "non-serialized" as used herein means items that are not uniquely identified relative (by some type of identifier, such as a serial number) to other similarproducts, thereby preventing the items from being distinguished from other items after manufacture, sale or the like.
In accordance with a main aspect of the instant invention, a method and system are provided for obtaining and using information on sales of non-serialized products for the primary purpose of reducing the number of unauthorized returns ofpurchased products. In accordance with a preferred embodiment of the invention, retailer specific information on sales of non-serialized products are collected by the ER system in an efficient manner and in a way that enables an educated decision to bemade when a non-serialized product is presented for return as to whether it is possible for the product to qualify for return under applicable return policies or criteria. Thus, the improved ER system of the invention enables non-serialized data oridentifiers to be used to access return/warranty qualification information that applies to a class or group of similar products. For example, in accordance with the invention, model numbers or other non-serialized data (such as UPC or SKU numbers) thatdo not uniquely identify a particular product can be entered into the ER system for the purpose of storing non-serialized product transaction information and later obtaining return and/or warranty qualification information for a product that is beingpresented for return. Thus, the invention enables electronic registration of non-serialized products, such as products that may not have been originally intended for electronic registration, due to, for example, their price, nature or othercharacteristics. The invention also enables products that have been sold without collecting serialized registration data to still be added to and benefit from ER systems.
In accordance with a main feature of the invention, retailers provide information on a periodic basis which identifies when and which non-serialized products have been sold by the retailer. The ER system stores this information together withinformation on applicable return policies relating to the sold non-serialized products. By knowing the last date on which a particular type of product (but not the exact product) was sold by a retailer, the ER system is able to determine whether it ispossible, at the time a product of this type is presented for return, that the product could qualify for return. For example, by knowing that a specific retailer last sold a product having a certain UPC 100 days ago, the ER system is able to inform theretailer upon inquiry that it is impossible that the product qualifies for return under the retailers 90 day return policy. Thus, a key aspect of the invention involves obtaining from participating retailers (or other entity) information indicating whencertain types of products (e.g., products having the same UPC or other non-unique identifier) were last sold by the retailers, respectively. In one embodiment, the retailer transmits to the ER system each day at least one UPC for each product that theretailer sells that day. In this way, the ER system knows the last date on which each type of product was sold by each participating retailer. The system also includes return policies for each retailer, such as "no returns allowed after 90 days frompurchase." Thus, when someone attempts to return a non-serialized product to a particular retailer, the ER system is able to assess transaction information for that retailer and for the specific type of product presented (e.g., UPC) and determine whetheror not it is possible that the product qualifies for return under the retailer's specific return policy(ies). For instance, if the last date of sale for products having that UPC number, for example, was more than 90 days from the attempted return date,then it is impossible for that product to qualify for return under a 90 day return policy. Similarly, if the last date of sale for that UPC was within the 90 day period, it is possible that the product does qualify for return and the retailer can thenmake an educated and informed decision as to whether to accept the return. In this way, the invention is able to reduce the number of unauthorized returns by providing the retailer (or other party) with return qualification information, upon request,with respect to each type of product that it has sold, without requiring the use of a unique identifier.
The ER system of the invention provides and uses a database that is loaded with information on last sale date for products having certain model numbers, UPCs, SKUs or other non-unique identifiers, as well as applicable return and/or warrantycriteria for products having these specific non-unique identifiers. The database may also contain serialized information so that the ER system can perform serial number (or other unique identifier) lookup operations as well as model number, UPC, SKU orother non-unique identifier lookup operations. Thus, the instant invention enables non-serialized products to benefit from electronic registration in substantially the same manner that serialized products have and are currently benefiting fromelectronic registration. Of course, the non-serialized ER system described herein does not provide the same level of accuracy as a serialized ER system, in that actual sales date or sales location information on a specific product is not available forthe non-serialized products. However, the information provided by the non-serialized ER system is still very useful in making logical decisions about whether or not products qualify for return or warranty repair/replacement based on the last sale dateinformation in the system for each class or group (e.g., UPCs) of products.
BRIEF DESCRIPTION OF THE DRAWINGS
The invention will be further understood by review of the following detailed description of the invention when read in conjunction with the appended drawings, in which:
FIG. 1 is an schematic view of an exemplary electronic registration system that can be used in connection with the instant invention; and
FIG. 2 is an exemplary overall block diagram illustrating the main steps that are performed in accordance with a preferred embodiment of the instant invention;
FIG. 3 is an exemplary block diagram of the main steps involved in initializing the ER system to handle non-serialized transactions; and
FIG. 4 is an exemplary block diagram of the main steps involved in using the ER system in connection with returns of non-serialized products.
DETAILED DESCRIPTION OF THE DRAWINGS
The preferred embodiment of the instant invention will now be described with reference to the drawings. It is noted that this description of the invention is only exemplary and is not meant to limit the invention beyond the express scope of theappended claims.
FIG. 1 shows an exemplary electronic registration (ER) system of the type described in the ER patents identified above. In such ER systems, products are registered at the point of sale using a unique identifier, such as a serial number, thatuniquely identifies the product involved in a sales transaction. By storing the unique identifier along with a date associated with the transaction, as well as return policy information, ER enables prompt, efficient and accurate return transactions tobe performed in connection with product returns using the ER system.
As shown in FIG. 1, a typical ER system includes a point of sale (POS) transaction register 2, preferably having a scanner or wand 4 associated therewith. The scanner or wand enables efficient and accurate reading of information, such as a UPCand/or serial number, off a product, product packaging, electronic tag (such as an RFID tag) or other such device or indicia. The register 2 is connected to a local computer system 6 having local database 8 for storing the transaction informationobtained by POS register 2. The local computer system typically has a user terminal 12 and printer 10 connected thereto for accessing and controlling the local computer system 6. The local computer system is, for example, a retailer store computersystem and may be connected to other computer systems via channels 13. The local computer system 6 is also preferable connected to a central ER computer system 14 having an associated database 16 which acts as a master ER database. The central computersystem 14 also includes a terminal 20 and a printer used in connection with its ER functions. The central computer system 14 is also preferably connected to other local computer systems over channels 12, so that it contains registration information frommany retail locations covering many different manufacturer's products.
The instant non-serialized ER system is preferably implemented using substantially the same conventional ER system described above. In accordance with the invention, the conventional ER system is modified to accept non-serialized registrationsand associated return criteria, as explained in detail below.
In accordance with the invention, non-unique product identifiers, such as product model numbers, UPCs, SKUs or the like, are loaded into a database system, such as an electronic product registration system. The loaded UPCs, for example, defineproducts for which the system will be able to provide return qualification information to a requesting party. Thus, if a retailer or other party desires to utilize the system for the purpose of reducing the number of unauthorized returns, that partyprovides the UPCs of interest (or other non-unique product identifiers) so that they can be loaded into the ER system. The party then also defines a return/warranty policy for each different UPC that has been loaded into the ER system. Alternatively,the party may simply provide a global return policy covering all of its non-serialized products. The policies are preferably based on some information that relates to the last sale date (or other key date, such as last ship date) having the particularUPCs. For example, a policy may state that products having a certain model number or UPC cannot be returned X days (e.g., 90 days) after the last date on which a product having that UPC was sold by the retailer. The term "sale date" is used looselyherein, and covers any date that at least closely approximates the sale date, such as the date that the non-serialized sales information is transmitted to the ER system.
In this way, the ER system knows that a product having a certain model number, UPC or SKU was last sold on a certain date (or approximate date). This information, combined with the return policy connected to this non-serialized product, enablesthe ER system to determine whether or not it is possible for a product corresponding to that UPC to qualify for return on a specific date. Of course, this system may allow some improper returns, due to the fact that there is no way to know exactly whena particular product having the UPC was purchased. However, the system at least can provide a logical cut-off date for returns based on the last sale (or other key) date for all products having that UPC, thereby still operating to reduce the number ofunauthorized returns. In other words, the ER system basically assumes that all products having that UPC were purchased on the date the last product having that UPC was purchased (even though this is likely not the case). This enables decisions to bemade as to return qualification based on these last dates. The system of the instant invention is particularly useful in reducing improper returns that, for example, are presented for return long after the retailer has stopped selling a particularproduct. Any suitable policy can be used in accordance with the system for a group (or groups) of products having the same non-unique product identifier depending on the particular desires of each retailer (or possibly manufacturer) that participates inthe non-serialized ER program.
Once the non-serialized products have been registered, as described above, access to the ER system can be provided through, for example, a VRU system or a fully computerized look-up system. In the computerized system, the user would access theER system through a web site or other computer communication and then be prompted for the model number, UPC or other non-unique identifier. The ER system would then look up the associated return/warranty policy for the product and provide non-serializedreturn qualification information back to the user through the computer system (or through a VRU system).
As explained above, rather than sending a product serial number query to a database, a non-unique identifier, such as a product model number, is accepted by the ER system and is sent to the database. As will be understood by those skilled inthe art, a product serial number is unique for each product, whereas more than one product (typically the same type of products) may have a non-unique identifier such as a product model number or UPC. While the description herein may refer to "UPC",those skilled in the art will understand that any non-unique identifier or other indicia could be used in connection with the non-serialized system of the instant invention.
In one embodiment of the instant invention, the ER system handles serial number lookups and UPC (or non-serialized) lookups. The ER system will then access the appropriate database based on the selection. If a serial number lookup query isrequested, serial number registration information is retrieved from the system, as described, for example, in the above-referenced U.S. Patents. On the other hand, if return qualification information for a product model number, UPC of othernon-uniquely identified product is requested, then qualification information relating to all products having that model number, UPC etc. is provided by the ER system. Thus, the instant invention enables users (such as sales clerks or purchasers) toobtain information regarding return, warranty, replacement and/or repair of previously purchased products using product model number (or other non-serialized) information and without the need for specific information (e.g., serial number, purchasedate/time and/or individual transaction information) being obtained at the time the specific product is actually purchased.
By using a model number lookup rather than a serial number lookup, a retailer can effectively control the return, warranty, replacement and/or repair of purchased products even if the retailer did not collect any serialized information at thetime the products were purchased. In accordance with the invention, no information regarding the individual purchase transactions, particular purchase dates/times and/or serial numbers is needed to provide the non-serialized ER system in accordance withthe instant invention. Instead, policy or criteria information is needed that relates to the entire class or group of products that are covered by the model number or other non-unique identifier (such as UPC). For example, a policy may be defined for aparticular product model number such that any purchased product having that model number cannot be returned to a particular retailer X number of days after the last date on which that retailer sold a product having that model number. Once this policy isestablished in the ER system, the only other information needed by the ER system to function as described herein is the last date (or approximate last date) on which that retailer sold a product having that model number. This exemplary return policy canbe instituted by the retailer and/or manufacturer without collecting any serialized information at the time of sale and can thus be instituted after some or all of the sales of the products having that particular model number are completed. As long asthe return policy for that particular model number has been defined, the only additional information needed is the model number itself from the requester and the last sale date information. Serial number, purchase date/time and/or other specifictransactional data at the time of sale (or any time thereafter) is not required.
A non-serialized ER system, as described herein, can generally be implemented and operated at a lower cost as compared to a serialized registration system, due to the fact that specific transaction data does not need to be provided to thenon-serialized ER system for every product being registered. In addition, the products do not have to be assigned unique identifiers. Thus, a system which registers serial number, purchase date/time and/or other transactional information is notnecessarily needed in order for the ER system of the instant invention to operate effectively to reduce the number of improper or fraudulent returns and/or warranty repair/replacement. Moreover, less storage space for non-serialized data and policyinformation is typically needed as compared to a serialized ER system. For the above reasons, the instant invention is particularly useful for relatively less expensive products or products not originally intended for ER registration. However, theimproved ER system of the instant invention can be used for any suitable product.
Referring now to FIG. 2, there is shown a flow chart of the main steps performed in accordance with a preferred embodiment of the instant invention. As shown in FIG. 2, the first step (step 200) involves signing up one or more retailers toparticipate in the non-serialized ER system. The participating retailers provide return (and/or warranty/replacement) criteria or policies to the operator of the ER system (or possibly directly to the ER system) for each group or class of products thatthe retailer desires to have registered in the ER system (step 202). Each policy is connected with a group (or groups) of products having the same non-unique identifier thereon (i.e., non-serialized products). As indicated above, this non-uniqueidentifier could be a model number, UPC, SKU or any other suitable identifier that is used on the products. Each retailer is free to define its own policies.
The retailer then sells, in a conventional manner, non-serialized products having, for example, UPC numbers corresponding to those that have previously been identified to the ER system by the retailer as having a particular return policy. Whenthe retailer sells a non-serialized products (step 204) the UPC (or SKU) is scanned or otherwise obtained at the point of sale and recorded within the retailers computer system. Throughout the sales day, many UPCs are collected which represent soldproducts for that day. At the end of the day, the retailer preferably transmits to the ER system a single UPC corresponding to each of the UPCs that were collected that day (step 206). By transmitting the UPCs for sold products, the ER system is ableto determine that a sale has occurred that day for each of the transmitted UPCs. As a result, the ER system knows that a legitimate return of that product could occur for the next 90 days (assuming a 90 day return policy). Similarly, for any UPC in theER system for which a UPC was not transmitted that day, the ER system knows that a legitimate return could only occur over the next 89 days in this example. In other words, based on the last date that a retailer has transmitted a UPC, the ER systemdetermines the last possible day that a legitimate return can occur for that UPC (step 208). By transmitting the UPCs on a daily basis from each participating retailer, the ER system is able to make daily last return date determinations for all of theUPCs in the system and for each participating retailer, respectively. Preferably, the last return dates are retailer specific, meaning that each retailer may (and probably will) have a different last date for return for common UPCs, which is determinedbased on the last date they sold a product having that UPC and the retailer's specific return policy for that UPC.
While in the preferred embodiment the retailers transmit UPCs for purchased products each day, such frequent transmissions are not required. In fact, the retailer may choose to only provide the UPC list and associated sales dates on a periodicbasis. However, the time between transmissions must be at least as frequent as the return policy itself for the system to work effectively. In this example, the ER system basically assumes after 90 days without a transmission for a specific UPC thatthe UPC is no longer being sold and that no further returns are permitted. However, should another UPC get transmitted (indicating a sale of a product having that UPC) after the 90 day period, the ER system resets the return period for another 90 days,thereby allowing return for that UPC for at least another 90 days and possibly longer if another corresponding UPC transmission occurs within the 90 days. In this way, the ER system constantly updates its database to reflect the calculated last returndates for each of the non-serialized products in its database based on the information it receives from the retailers (or other party).
In order to improve the operation of the non-serialized ER system with respect to reducing improper returns, retailers (and/or manufacturers) should change the UPC, SKU or other non-unique identifier used on its products periodically so that oldproducts cannot be returned simply because a newer product having the same UPC has been sold within the legitimate return period. This situation can be avoided or at least minimized by changing the UPC fairly often, such as each time a new feature,color or other characteristic or the product changes or evolves, thereby effectively constituting a new and different product.
Once the ER system has the last return date stored for each UPC, the ER system can then be used for inquiries in a similar manner to the known serialized ER system. For example, a sales clerk being presented with a return accesses the ER systemeither by VRU, computer terminal or the like, and enters the non-unique identifier (e.g., UPC) on the product. The ER system then checks its database for the UPC and returns return qualification information (step 210) to the sales clerk (such as lastdate for return) that enables the sales clerk to make a determination as to whether or not it is possible for that product to still qualify for return under the applicable return criteria. The sales clerk is then able to proceed accordingly with respectto the attempted return (i.e., accept or reject the return).
As can be seen from the description herein, the instant invention enables non-serialized products to be registered in an ER system for the purpose of reducing the cost of product returns. While the non-serialized system is not as accurate asthe serialized system with respect to return qualification determinations, the non-serialized system described herein still provides significant benefits to the retailer and manufacturer with respect to reducing unauthorized returns. The non-serializedsystem is also easier to implement and less information intensive due to, for example to the fact that information on every product sale does not need to be transmitted to the ER system. Instead, transmission of a list containing a single reference toeach different UPC for products sold each day (or within another suitable time period) will enable the system to operate as explained herein.
It is noted that the actual date of sale does not necessarily have to be transmitted to the ER system. Instead, the ER system could, for example, assume that the date the UPC is transmitted is the date of sale, or the retailer could transmit adate that is associated with the sale or other desired event other than the actual sale date.
FIG. 3 is an exemplary block diagram showing the main steps involved in setting-up or initializing a non-serialized ER system in accordance with the preferred embodiment of the instant invention. As shown in FIG. 3, and as described above, theprocess begins when a retailer begins its participation in a non-serialized ER program (step 300). The retailer periodically transmits information to the ER system which indicates which non-serialized products were sold since the last transmission andwhen. The transmission may be daily, but it need not be daily (step 302). For example, the retailer could simply send the information at intervals that correspond to the return period(s) for the products. For example, if the return period is 90 days,the retailer could simply send the information at the end of each 90 day period, thereby providing the ER system information as to which products should have their return periods reset by the ER system. Any other suitable period between transmissionthat satisfies a business rule may be used. The retailer also provides the ER system with information that defines return policies for the non-serialized products. Based on the transmitted information, the ER system determines, for each non-serializedproduct referenced in the transmission, the last day on which returns should be accepted under the applicable return policies of the retailer to which a return is presented (step 304).
FIG. 4 is an exemplary block diagram of the main steps involved in using the ER system in connection with returns of non-serialized products. As shown in FIG. 4, and as discussed above, the return process begins when a party presents anon-serialized product for return to a retailer (or other agent of a manufacturer) (step 400). The ER system is the contacted and provided with a non-unique identifier (such as UPC or SKU) for the product being presented for return (step 402). The ERsystem then checks its database for information on the non-serialized product. If no information is found, then the ER system reports this to the retailer so that the retailer can handle the return request in a conventional fashion without the benefitof ER. On the other hand, if information for the non-serialized product is found in the database, the ER system returns information to the retailer indicating the whether or not it is possible for the presented product to qualify for return under theapplicable return policy using the previously transmitted information on non-serialized sales (step 404). The retailer then makes the decision on whether or not to accept the return based on the information provided by the ER system (step 406). In thisway, the retailer can assure that returns are only accepted if it is at least possible for the product to qualify for return based on the last date that such a product was sold by that retailer. Thus, the non-serialized ER system of the instantinvention is operable to reduce the number of improper returns as well as reducing the costs associated therewith. The system also helps with customer relations by providing information that can be used to explain to a customer why a return cannot beaccepted.
While the preferred forms and embodiment of the instant invention have been illustrated and described, it will be apparent to those of ordinary skill in the art that various modification and/or changes may be made to the exemplary embodimentdescribed above. Thus, the exemplary embodiment described above is not meant to limit the scope of the invention beyond the express scope of the appended claims.
* * * * *