WO2018118981A1

WO2018118981A1 - Systems and methods for managing inventory across a distributed network

Info

Publication number: WO2018118981A1
Application number: PCT/US2017/067406
Authority: WO
Inventors: Enoch Cary HOOPER; Chamrong CHHUT
Original assignee: Magna Trada Inc.
Priority date: 2016-12-19
Filing date: 2017-12-19
Publication date: 2018-06-28

Abstract

Presently discloses are systems and methods for managing inventory across multiple transactions and bringing those items to market in a brokered sale with multiple parts. The system may include a first mobile device having a sensor and configured to receive user input associated with an item, the first mobile device configured to package the user input as item information. They system may also include a transaction server configured to receive the item information from the first mobile device. A first database may be in electrical communication with the transaction server and configured to store the item information, and a second database may be in electrical communication with the transaction server or the first database, and configured to store the redacted item information therein.

Description

SYSTEMS AND METHODS FOR MANAGING

INVENTORY ACROSS A DISTRIBUTED NETWORK

BACKGROUND

[0001] During an auction, items for bid are stored at an auction house prior to an auction. At the time of the auction or sale, the items are brought out for display before a group of individuals or bidders. The bidders offer prices at which they are willing to purchase the item (bids). To facilitate inspection of the item or items on which the bidders intend to bid, auction houses permit the public, or at least prospective bidders, to physically inspect items prior to the auction. Depending on the items to be auctioned, significant venue space may be required (for example, during an automobile auction) to house and store the inventory prior to and during the auction.

[0002] In response to the growing demand of the public to engage in auctions, companies such as EBay^® and Craigslist provide online auction spaces for single transactions. These service providers allow for items to go to auction individually, and at varying prices. For example, a seller may upload an image and a description of an item to be sold, and prospective buyers are given the option to bid on the auction item. Additionally, bidders are sometimes given the opportunity to immediately purchase the item at a particular price. While these service providers host websites which enable auction transactions, they generally do not provide opportunities for physical auctions, often relying on sellers to directly ship purchased goods to buyers. Additionally, while a seller may be able to set a traditional "reserve" on an item, the seller cannot withhold sale once reserve price is met.

[0003] Accordingly, the disclosure of systems and methods which improve upon both electronic (online) and/or physical (offline) brokered transactions is desirable. SUMMARY

[0004] This disclosure relates generally to systems and methods for managing inventory across a distributed network. More particularly, certain aspects of the present disclosure relate to managing the transfer of data associated with inventory across a distributed market or network and facilitating the brokerage of the inventory among multiple potential transactions.

[0005] In accordance with an aspect of the present disclosure, a system for managing inventory across multiple transactions is disclosed. The system includes a first mobile device, a transaction server, a first database, and a second database. The first mobile device includes a first sensor disposed thereon. The first mobile device is configured to receive user input associated with an item at a first location. Based on user input, the first mobile device is configured to package the user input as item information. The transaction server is in electrical communication with the first mobile device and is located at a second location different from the first location. The first database is in electrical communication with the transaction server and is configured to store the item information on a memory of the first database. The second database is in electrical communication with the transaction server or the first database. The second database is also configured to receive item information redacted by the transaction server, and store the redacted item information in a memory of the second database. The redacted item information stored in the second database is associated with the item information stored in the first database.

[0006] In aspects, the first mobile device is configured to capture an image of the item at the first location and, in response to capturing the image, include the captured image in the item information. The transaction server may be configured to determine whether the second mobile device is permitted to receive the item information or the redacted item information and, in a case where the transaction server is permitted to transmit the item information or the redacted item information, transmit the item information or the redacted item information to the second mobile device. The transaction server may be configured to modify the item information or the redacted item information based on input received from the first mobile device or the second mobile device. The transaction server may be configured to associate the item information with auction data stored in the database and, based on the auction data, calculate a suggested sale price of the item associated with the item information. The transaction server may be configured to associate the item information with one or more auctions based on the calculated suggested sale price of the item associated with the item information. The transaction server may be configured to disassociate the item information with the auction in a case where the suggested sale price is recalculated and, based on the recalculation, the item information is no longer appropriate for the auction associated with the item information.

[0007] In accordance with aspects of the present disclosure, a method of managing inventory across multiple transactions is disclosed. The method includes receiving item information associated with an item at a transaction server from a first mobile device having a first sensor disposed thereon at a first location, storing the item information in a first database in electrical communication with the transaction server, generating redacted item information by redacting the item information at the transaction server and subsequently storing the redacted item information, and storing the redacted item information in a second database in electrical communication with the transaction server or the first database, the redacted item information associated with the item information.

[0008] In aspects, receiving item information at the transaction server includes receiving item information from the mobile device of a type selected from the group consisting of image data, text data, and audio data. [0009] According to aspects, the method of managing inventory further includes receiving a request from a second mobile device at the transaction server to receive either the item information or redacted item information.

[0010] In aspects, the method of managing inventory may further includes determining, based on the request from the second mobile device, whether the second device is permitted to receive either the item information or the redacted item information and, in a case where the transaction server is permitted to transmit the item information or the redacted item information, transmitting the item information or the redacted item information to the second mobile device.

[0011] According to aspects, the method of managing inventory further includes receiving item information from the second mobile device and modifying the item information or the redacted item information based on input received from the second mobile device. The method may further include associating the item information with auction data stored in the database. The method may also include disassociating the item information with the auction data in a case where the item information is no longer appropriate based on items associated with the auction data different from the item information and the item information.

BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Various embodiment of this disclosure are described with reference to the accompanying drawings wherein:

[0013] FIG. 1 is a schematic diagram of an auction inventory management system in accordance with embodiments of the present disclosure;

[0014] FIG. 2 is a schematic block diagram of an illustrative embodiment of a computing device that may be employed in various embodiments of this system, for instance, as part of the system or components of FIG. 1 ; [0015] FIG. 3 is a flowchart showing an illustrative method for indexing auction inventory;

[0016] FIG. 4 is a flowchart showing an illustrative method for managing auction inventory;

[0017] FIG. 5 is an illustration of an item and associated data associated with the item;

[0018] FIG. 6 is an illustration of data items associated with a user and an auction;

[0019] FIG. 7 is a flowchart showing an illustrative method for checking and generating an instant auction based on an item listing; and

[0020] FIG. 8 is a flowchart showing an illustrative method for determining item placement across multiple transactions.

DETAILED DESCRIPTION

[0021] The present disclosure is directed to systems and methods for managing auction inventory. More particularly, the present disclosure relates to the indexing and management of inventory between appraisers, dealers, auctioneers, and estate professionals in anticipation of a brokered sale such as an auction, a listing, and the like.

[0022] As described herein, the term "appraiser" will be used to refer to individuals who specialize in determining an appropriate value at which an item will sell in any given market; the term "dealer" will be used to refer to individuals who specialize in the transaction of goods on the behalf of a second individual (such as a buyer or a seller of goods); the term "auctioneer" will refer to individuals or service providers which facilitates a bidding transaction across multiple buyers; and the term "seller" will refer to any individual selling or authorized to sell goods either on their own behalf, or on behalf of another. As described herein, the term "broker" or any variant thereof, will be used to refer to transactions which are mediated or settled between two or more parties, such transactions including, but not limited to, auctions and listings. It will be understood that, though throughout the present disclosure discussion is primarily conducted in the singular, multiple individuals, entities, or goods may be transacted in or with.

[0023] The following example, provided for illustrative purposes and not intended to limit the present disclosure, describes a transaction in accordance with certain embodiments of the present disclosure. Initially, an estate for an individual, and more particularly an estate administrator, may be tasked with selling, among other items, a painting. The estate administrator may execute an application on computing device (e.g., a mobile device) to capture identifying information relating to the painting. The identifying information may include one or more images of the painting, text input relating to the age, size, and weight of the painting, and location information about where the painting is currently stored. Once the information is input into the mobile device, the information may be aggregated or packaged for transmission to a transaction server.

[0024] Upon receipt, the transaction server stores the packaged information in one or more databases. In certain embodiments, when desired by the administrator, the transaction server may store the packaged information in an un-redacted information database as well as a redacted information database. The information stored in the redacted information database may obscure or exclude certain input identifying information which the estate administrator prefers not to be seen by the all participants in the market place. The packaged information may include one or more data elements or flags which correspond to certain attributes (e.g., a non-public flag may be included to indicate that the item is not to be displayed to the public at large, a private flag may be included to indicate that only the estate administrator should be able to see the item, etc.).

[0025] Once the packaged information is stored in the un-redacted information database and/or the redacted information database (referred to generally as the database) the packaged information may be made available for future review or recall. For example, if the estate administrator would prefer that the painting be made available for immediate auction, individuals, dealers, or auctioneers may be permitted to view the painting to either bid on the painting, or reserve the painting for an auction. The estate administrator may also forward the packaged information relating to the painting to one or more auctioneers for inclusion in any particular brokered transaction. For purposes of clarity, reference will be made to auctions, though other similar brokered transaction are contemplated as being manageable by the systems and methods of the present disclosure.

[0026] Once the painting is assigned to one or more auctions, the painting may either be set as inactive inventory (e.g., individuals cannot bid on it) or as active inventory available for sale. The estate administrator may optionally request that one or more appraisers review the painting at any time to determine a suggested market value. Once the appraiser determines the appropriate market value, the item information may be updated to include the suggested market value.

[0027] Depending on the availability of the item information to individuals other than the seller, dealers and auctioneers may suggest or include the item in auctions or other sale venues in which the items are associated with. For example, a dealer who specializes in paintings may identify the painting and request to include it in a gallery associated with the dealer. The seller may subsequently negotiate with the dealer to have the painting displayed in the gallery, while simultaneously maintaining the availability of the painting in multiple co-pending auctions.

[0028] While the descriptions of the systems and methods included in the present application are described with reference to electronic auctioning, it will become apparent that physical auctions may also be managed in conjunction with electronic auctions. For example, to bolster the inventory of any given art auction, dealers and/or auctioneers may select from among multiple items (paintings) which are indexed in one or more databases. Accordingly, the present disclosure should not be limited to the embodiments described hereinabove.

[0029] Referring now to FIG. 1, a schematic diagram of an inventory management system is illustrated, the system referred to generally as management system 100. The management system 100 includes one or more items 102a-102d, one or more personal computing devices 104, a transaction server 106, and one or more databases 108. The items 102a-102d, collectively referred to as items 102, may be any item which may be available for purchase or otherwise held in inventory.

[0030] Personal computing devices 104, which are similar in many respects to the computing device of FIG. 2, may include specific devices such as an appraiser device 104a, a dealer device 104b, an auctioneer device 104c, and a seller device 104d. While the use or control of each device need not be limited to any particular individual or entity, each personal computing device 104 may be subject to particular subsets of data and/or actions which may be performed. For example, the appraiser device 104a may or may not be enabled to receive item information from one or more items 102. Alternatively, the appraiser device 104a may be able to input item information associated with the one or more items 102 to identify or verify the accuracy of the information associated with the item (e.g., a suggested bidding price).

[0031] A transaction server 106, similar in many respects to the computing device of FIG. 2, is in electrical communication with the personal computing devices 104a-104n, as well as one or more databases 108a, 108b (collectively referred to as database 108), discussed in detail below. More particularly, the transaction server 106 communicates with the personal computing devices 104a-104n and database 180 via communication links 110. Communication links may be any suitable wired or wireless connection capable of enabling data transfer between two computing devices. The transaction server is configured to receive item information (see FIG. 5), user information, and brokered transaction information (see FIG. 6). More particularly, upon receipt of communication from the devices 104a-104n, the transaction server 106 communicates with the database 108 to add or modify information about the items 102 stored in the database 108.

[0032] Database 108, which may include un-redacted information database 108a and/or redacted information database 108b, is configured to receive item information 112a-112c or redacted item information 112a'-112b' and store the information in memory stored therein. For purposes of clarity, item information 112a-112c will be referred to, though one skilled in the art will readily understand that, in certain embodiments, modifications described with respect to item information 112a-l 12c may be performed in a similar manner on redacted item information 112a'-112b'. Database 108 is a computing device similar in many respects to the computing device illustrated in FIG. 2, and discussed below. In operation, the database 108 is configured to receive the item information 112a-112c, store the item information 112a-112c in memory associated with the database 108, and upon recall, transmit the item information 112a-112c to the transaction server 106.

[0033] Referring now to FIG. 2, illustrated is a schematic block diagram of a computing device 200 that may be employed according to various embodiments of the present disclosure. Though not explicitly shown in the corresponding figures of the present application, the computing device 200, or one or more components thereof, may represent one or more components (e.g., appraiser device 104a, dealer device 104b, auctioneer device 104c, seller device 104d, transaction server 106, un-redacted information database 108a, and redacted information database 108b) of management system 100. The computing device 200 may include one or more processors 202, memories 204, display devices or displays 212, input modules 214, output modules 216, and/or network interfaces 218, or any suitable subset of components thereof. The memory 204 includes non-transitory computer readable storage media for storing data and/or software which include instructions that may be executed by the one or more processors 202 and which, when executed, control operation of the computing device 200. The memory 204 may include one or more solid-state storage devices such as flash memory chips. Additionally, or alternatively, the memory 204 may include one or more mass storage devices connected to the processor 202 through a mass storage controller and a communications bus (not shown) Although the description of computer readable media described in this disclosure refers to a solid-state storage device, it will be understood that computer-readable storage media may include any available media that can be accessed by the processor 202. More particularly, computer readable storage media may include non-transitory, volatile, non-volatile, removable, non-removable media, and the like, implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other suitable data access and management systems. Examples of computer-readable storage media include RAM, ROM, EPROM, EEPROM, flash memory, or other known solid state memory technology. Additionally, computer readable storage may include CD-ROMs or other such optical storage, magnetic cassettes, magnetic tape, magnetic disk storage, or other magnetic storage devices, or any other medium which may be used to store information and which can be accessed by computing device 200.

[0034] In embodiments, the memory 204 stores data 206 and/or one or more applications 208. Such applications 208 may include instructions which are executed on the one or more processors 202 of the computing device 200. In aspects, the application 208 may include instructions which cause a user interface component 210 to control the display device 212 such that a user interface 210 is displayed (e.g., a graphical user interface (GUI) (not shown). The network interface 218 may be configured to couple the computing device 200 and/or individual components thereof to a network such as a wired network, a wireless network, a local area network (LAN), a wide area network (WAN), a wireless mobile network, a Bluetooth^® network, the Internet, and the like. The input module 214 may be any suitable input device or interface which may be engaged by a user for the entry of input data. For example, the input module 214 may include any combination of a mouse, a keyboard, a touch-capacitive display, a voice interface, or other such suitable devices known in the art. The output module 216 may include any connectivity port or bus such as, for example, a parallel port, a serial port, a universal serial bus (USB), or any other similar connectivity port known in the art.

[0035] Referring now to FIG. 3, illustrated is a flowchart depicting an illustrative method for indexing auction inventory, in accordance with certain embodiments of the present disclosure, the method designated generally process 300. As described the devices 104, transaction server 106, and database 108 may include various components of computing device 200, described above. The processes described in this application, including process 300, may be performed and/or executed on one or more of the components described in computing device 200. Further, one of ordinary skill will recognize that the processes described may be performed as a single or unitary process or, in the alternative, may be performed by performing a set of sub-processes. While the processes and sub-processes associated disclosed in the present application are described in a particular order for purposes of clarity, it is contemplated that performance of particular processes may occur in differing order without departing from the scope or spirit of the present disclosure. Further, specific examples of execution of any or all of the particular processes described below should not be seen as limiting, but merely as exemplary of embodiments consistent with this disclosure.

[0036] Process 300 starts at block 302 where the seller device 104d executes an application 208 (FIG. 2) on the seller device 104d. Once executed, the process 300 continues with the seller device 104d capturing item data 500 (FIG. 5) associated with an item 102d. More particularly, the seller device 104d may capture one or more images 501 of the item 102d, input from the seller such as an item type 502 (e.g., a painting, jewelry, etc.), an inventory type 504 (e.g., stock, for sale, for inclusion in a brokered transaction, not available for purchase, etc.), an item description 506, a condition 508, miscellaneous item data 510, and a reserve amount 514. The item information 500 captured by the seller device 104d is subsequently associated with the original item 102d at block 304. Association may occur by assigning a unique identification number or item ID (not explicitly shown) with the item description 506.

[0037] Once the seller device 104d captures the item data 500 (FIG. 5) of the item 102d, at blocks 306, the item is determined to be either inventory or available for brokered transactions. For example, in certain embodiments, the program executed on the seller device 104d causes an input screen as the user interface 210 on the display 212 of the seller device 104d to be displayed (not shown). The input screen may prompt a user to input, via the input module 214 of the seller device 104d, whether the item data 500 corresponds to an item which is for brokerage immediately or an item which is inventory. In response to the user input indicating that the item is inventory at block 306, the inventory type 504 of the item data 500 is set to indicate that the item is available for inclusion in one or more brokered transactions, for purchase, or for appraisal. Alternatively, if the user input indicates that the item is available for brokered transaction, the inventory type 504 is set to indicate that the item is to be put up for an instant auction at block 310, at which point the item may receive bids from other users for purchase in accordance with the item data 500.

[0038] If the seller device 104d subsequently receives input indicating that the item type has changed at block 312 (e.g., that the item is no longer available for immediate auction, the item is withdrawn and not to be shown as inventory, etc.) then process 300 returns to block 306 and the inventory type is determined again. At block 314, when the item information is received by the transaction server 106, the item information is stored in at least one database 108 as item information 112a-l 12c. Optionally, if the item 102a-102d is a redacted item, or an item which is to be only partially visible to other devices, the transaction may store corresponding redacted item information 112a'-112b' in a redacted information database 108b. More specifically, the redacted item information 112a'-112b' is associated with the corresponding item information 112a-l 12b found in the un-redacted item database 108a, but includes a subset of the information available with respect to the corresponding item information 112a-l 12b.

[0039] Once the item information 112a-112c, and corresponding redacted item information 112a'-l 12b' (referred to herein as item information 112a-l 12c for purposes of clarity), are stored in the database 108, the item information 112a-112c may be associated with one or more brokered transactions 700 (FIG. 6). For example, when the seller device 104d transmits the packaged item information 112a-112c at block 302 to the transaction server 106, the seller device 104d may include information indicating that the item 102 corresponding to the packaged information 112a-112c is available for immediate listing in one or more brokered transactions 700 (FIG. 6), is available for immediate listing as a single item 102 for a brokered transaction, if the item 102 or if the item 102 is to be stored in the database 108 and categorized as inventory. Further, if categorized as inventory, the item information 112a-112c may include a flag 518a- 518b which is marked indicating whether the inventory is to be made available for public inspection (e.g., if other devices can request to view the item information 112a-112c) or if the item information 112a-l 12c is to remain private.

[0040] It will be understood that, the item 102, and corresponding item information 112a- 112c, may be uploaded for immediate inclusion in one or more transactions. More particularly, the seller device 104d may send a request at any point after initially uploading the item information 112a-112c to modify permissions associated with the item information 112a-112c. For example, the seller controlling the seller device 104d may initially cause the seller device 104d to transmit the item information to the transaction server 106 and keep the item information 112a-112c private. Subsequently, the seller device 104d may transmit a request to the transaction server 106 to have the item information 112a-l 12c included in one or more brokered transactions 700 (see FIG. 6), listed to solicit offers from other devices 104, or listed as available inventory for inclusion in one or more transaction item lists 704 (see FIG. 6). As a result of the transaction server 106 being configured to receive input from the seller device 104d to change the inventory type 504 of the item information 112a-112c of a particular item 500 (see FIG. 5), the item 102 availability and inclusion in one or more brokered transactions 700 may be updated in real-time.

[0041] Additionally, the transaction server 106 may receive data input by devices 104 in response to requests made to view item information 112a-112c. In a scenario where the transaction server 106 receives a request for item information from a device 104 (e.g., appraiser device 104a, dealer device 104b, or auctioneer device 104c), the transaction server 106 may change the inventory type 504 of the item information 112a-112c. For example, if a dealer device 104b receives input from a user, after displaying the item information 112a-112c, to include the item 102 in one or more brokered transactions 700, an inventory associated with the dealer device 104b, and the like, the transaction server 106 may amend the item information 112a-112c associated with the item 102. Additionally, the transaction server 106 may associate the item information 112a-112c with one or more users 600 and/or one or more auctions 700 (FIG. 6).

[0042] In embodiments, the transaction server 106 may send notifications to devices 104 indicative of one or more transactions in which any particular item 102 is associated with. For example, if a dealer device 104b set a flag associated with the corresponding user information 600 (FIG. 6) indicating that the dealer device 104b would prefer to receive push notifications about a certain class of items, the transaction server 106 may transmit such notifications as they occur. One example may be when a particular type of automobile part becomes available, the transaction server 106 may search through all potential users 600 interested in that automobile part and transmit a notification to the corresponding device 104 that the part is available. These updates may occur periodically, continuously, or at an on-demand pace.

[0043] Referring now to FIG. 4, illustrated is a flowchart depicting an illustrative method for managing brokered transaction inventory, in accordance with certain embodiments of the present disclosure, the method designated generally process 400. Process 400 starts at block 402 where the transaction server 106 receives a request from a device 104 (e.g., dealer device 104b or seller device 104d) to conduct a brokered transaction. Receiving the request may further include receiving brokered transaction criteria at block 404. Brokered transaction criteria may be received by the input module 214 of the device used to request the brokered transaction at block 402. More specifically, the brokered transaction criteria may include an indication as to what items are to be included in the brokered transaction (e.g., what item types will satisfy the requirements for entry into the brokered transaction), what the duration of the brokered transaction will be, where is the brokered transaction to be held (either online or at a physical location), and the like.

[0044] Once the brokered transaction criteria is received (block 404), the transaction server 106 determines which items eligible for the brokered transaction are to be included in the brokered transaction at block 406 based on the brokered transaction criteria at block 406. For example, the transaction server 106 may identify all items 500 available which have a particular item type 502 (see FIG. 5), have a reserve type 514 within a predetermined threshold (e.g., an acceptable sale price which is above a certain value), and the like. For each item, a flag 518a, 518b may be set when the item data 500 is received by the transaction server 106 into indicate whether the item information 112a-112c may be displayed as either redacted item information 112a'-l 12b' or as item information 112a-l 12c when recalled by a device 104.

[0045] At block 408, the transaction server 106 selects, from among the relevant target brokered transaction items identified in block 406, whether any of the relevant target items are redacted items. If an item is determined not to be a redacted item, process 400 continues to block 412 in which the item information 112a-l 12c is added to a transaction item item list 704 (FIG. 6) associated with the brokered transaction data 700 of the particular brokered transaction. Alternatively, if it is determined that the target item is a redacted item, process 400 continues to block 410 in which the redacted item information 112a'-112b' is added to the transaction item list 704.

[0046] At block 414, in response to receiving a query for item information 112a-112c from the transaction server 106 during process 400, the transaction server 106 determines whether the requesting device 104 is a valid device (e.g., whether the device 104 is permitted to receive the item information 112). More particularly, depending on the settings input by the seller device 104d, a requesting device such as an appraiser device 104a, a dealer device 104b, or an auctioneer device 104c may be permitted to receive either the item information 112a-l 12c or the redacted item information 112a'-112b'. For example, if an appraiser device 104a requests the item information 112a-112c during the performance of an appraisal, the appraisal device 104a may be given the un-redacted item information 1 12a-l 12c for that particular item. Alternatively, if the seller device 104d receives input indicating that no appraisal is requested, or that an appraisal is to be denied if a particular appraiser device 104a is requesting to appraise the item 102, transaction server 106 denies the request by the appraiser device 104a for either item information 112a-l 12c or redacted item information 112a'-l 12b'.

[0047] If the device 104 requesting the item information 112a-112c is determined to be a valid device, e.g., the transaction server 106 approves the transmission of either the item information 112a-l 12c or the redacted item information 112a'-l 12b' to the device 104, at block 416 the transaction server 106 transmits the either the item information 112a-112c or redacted item information 112a'-112b' to the device 104. More particularly, if the requesting device 104 is permitted to view the full details about the item 102, the transaction server 106 transmits the details to the requesting device 104. Alternatively, if the device is determined to have access to only the redacted item information 102a-102b, the transaction server 106 transmits the redacted item information to the requesting device 104. In either case, the transaction retrieves the respective information from the database and subsequently transmits the information to the requesting device.

[0048] Referring now to FIGS. 5, illustrated is an example of an instance of item data 112a- 112c stored in database 108. More particularly, the illustrated instance of item data represents item information 112a-1 12c which is un-redacted. As discussed at block 302 of process 300, as the seller device 104d collects information associated with the item 102 to be formed in the un- redacted information database 108a, the information is packaged as item data 500. Specifically, the one or more images of the item 102 captured or otherwise input into the seller device 104d are stored as item images 501. The item images may additionally contain flags indicating whether they are available for display to requesting devices 104, or any subset of devices 104 thereof. The item type 502 corresponds to a particular class of item, and may include one or more classes. For example, an old automobile may be classified as both an automobile, as well as a show automobile. The inventory type, as described with respect to the distinction made at block 306 of process 300 (see FIG. 3), indicates, without limitation, whether the item is available for inclusion in an auction, is for sale, or is merely part of an inventory associated with a particular seller. The item description 506 may include text input into the seller device 104d which describes the item 102 being uploaded. For example, the item description 506 may include text associated with the age, amount of owners, etc., of the item 102. The item condition 508 may include a general rating (good, average, poor) relating to the quality of the item 102. Alternatively, the item condition 508 may include a description of the item condition either input by the seller to the seller device 104d, or by an appraiser into an appraiser device 104a during appraisal of the item 102. Miscellaneous item data 510 may be included with item data 500, the miscellaneous item data 510 associated including any information input into one of the devices 104 permitted to modify the description of the item data 500. For example, miscellaneous item data 510 may include the current location of the item, information regarding the owner of the item (if not the seller), etc. [0049] With continued reference to FIG. 5, the item data 500 may further include outstanding bid information or bid information 512, a reserve amount 514, and sale information 516. The bid information 512 may include a listing of bidders and bid prices, either for a particular brokered transaction or across multiple brokered transactions (where the reserve is not met, or the item is otherwise unsold). The reserve amount 514 may be included when the item is initially uploaded by the seller device 104d, or may be modified as is desired based on input received from the seller device 104d. Alternatively, the reserve amount 514 may be modified by input received by other authorized devices 104, such as the auctioneer device 104a (e.g., to conform the reserve price to the requirements of a particular auction. Additionally, flags 518a, 518b may be set so as to indicate whether item data 500, which corresponds to item 102, is available for brokered transaction, is available for public inspection, is sold, etc. It should be noted that, once an item 102 is sold or otherwise no longer subject to the ownership interest of the seller, the item information 112a-l 12c associated with the item 102 may be maintained in the database 108 so as to be relied upon for analysis of future items information 112a-l 12c managed by the transaction server 106.

[0050] Referring now to FIG. 6, illustrated are examples of instances of user data and brokered transaction data which may be stored in database 108 (FIG. 1, not shown). A user instance, referred to as user data 600, includes a user ID 602, a user address 604, user payment information 606, user bids 608, user inventory 610, a user description 612, and miscellaneous user information 614. The user ID 602 may be any identifying information (e.g., a serial no.) which is used to associate the particular user with the device 104 (FIG. 1) being used. The user address 604 may correspond to a personal or business address, and may be used by the transaction server 106 during when managing one or more brokered transaction, or when allowing or denying information to be transmitted to the device 104 used by the user. For example, if a device 104 is determined to be outside of a predetermined location or area, the device 104 may not be offered item information 112a-l 12c due to the distance of the device 104 relative to the item 102. This may be particularly useful when preventing appraisers from attempting to appraise items 102 which the appraiser would be unable to appraise the item in person, thereby working to prevent fraudulent appraisals.

[0051] The user payment information 606 may be any suitable information which can be used to complete a transaction (e.g., a purchase of an item 102 and/or for services such as appraisal of the item by an appraiser). The user inventory 610 relates to seller devices 104d, and corresponds to the items 102 owned or controlled by the seller. The user inventory 610 may include item information 112a-l 12c associated both with the inventory of the user 600 as well as inventory available for brokered transaction. {See FIG. 3, block 306.) The user description 612 may include a personal description (text, images, etc.) of the user 600. Additionally, the user description 612 may include information associated with verification of the user information (e.g., an independent verification of the credentials of the user), as well as a user rating. For example, in the case of an appraiser, the user rating may correspond to how accurate the appraiser is in setting a price at which an item 102 should be sold at. Additionally, a seller, dealer, or auctioneer may be rated based on similar criteria (e.g., how likely the particular user 600 is to deliver goods to a particular brokered transaction, whether the particular user 600 pays for services rendered or goods purchased, etc.). The miscellaneous user information 614 may include any suitable information associated with a particular user 600 which is not reserved for any of the field described earlier. [0052] With continued reference to FIG. 6, the instance of brokered transaction data 700 includes, without limitation, an auction ID 702, an brokered transaction item list 704, and a bid list 706. The transaction ID 702 corresponds to unique information (e.g., a serial no.) which is used to identify one or more particular brokered transaction. The transaction item list 704 includes item information 112a-112c, redacted item information 112a'-112b', or any combination thereof. Additionally, the transaction item list may include subsets of the information associated with a particular item 102. The bid list 706 includes all of the bids made during a particular brokered transaction. For example, when an item 102 goes up for bid during an auction, the bids are recorded in a bid list 706. This bid list may be temporary or persist over a period of time. Additionally, the bid list 706 may be used to base existing or subsequent reserves or appraisal prices. For example, if a vehicle having a specific make and model is sold at auction, when a similar vehicle appears in a later auction or is otherwise in database 108 (FIG. 1), the appraisal value of the item 102 may be amended to more accurately reflect the item value.

[0053] Referring now to FIG. 7, illustrated is a flowchart depicting an illustrative method for checking and generating a multi-stage instant auction based on an item listing, in accordance with certain embodiments of the present disclosure, the method designated generally process 800. Process 300 starts at block 802 where input data associated with an item 102 (FIG. 1) is captured by a device 104. (See FIG. 3, block 302.) Once the item information is received by the transaction server 106, and stored in the database 108, the transaction server 106 generates an item listing at block 804. The item listing permits other devices 104, such as a device associated with a buyer (not shown), to make offers on the item which are recorded by the transaction server 106 at block 806, the offers stored in a sealed fashion (e.g., the offers or bids not disclosed to other bidders placing offers on the same item). This effectively allows the market, to set the value of the item. As the listing persists, the transaction server 106 transmits updates about the listing to the seller device 104d (FIG. 1). Once the transaction server 106 determines that the list has expired at block 808, or periodically depending on the settings set by the seller, the transaction server 106 transmits a notification to the seller device 104d indicating the results at block 810.

[0054] The transaction server 106 subsequently determines whether the reserve is met at block 812. If the reserve is met (e.g., the minimum bid is reached during the listing), process 800 continues to block 814 in which the transaction server 106 determines whether an instant auction request is received from the seller device 104d. If no instant auction is requested, the transaction server 106 transmits a request to the seller device 104d to determine whether a settlement is requested. If the reserve is not met, process 800 continues to block 818 to determine whether a settlement is requested.

[0055] If no settlement is requested, process 800 continues to block 822 in which the participants who bid on the item 102 are notified of the results, namely, that no sale will occur. Alternatively, if a settlement is requested, process 800 continues to block 820, and the transaction server 106 initializes a settlement. During the settlement, communication between the seller device 104d and the corresponding highest bidder device 104 is mediated or passed between devices via the transaction server 106. If the seller and the buyer are able to come to an agreement, then the seller device 104d and the corresponding buyer device 104 receive notifications from the transaction server 106 at block 818 that the settlement was successful, and that the highest bidder has now purchased the item 102 at the agreed upon price. Alternatively, if no agreement is reached, then the seller device 104d and the corresponding buyer device 104 receive notifications from the transaction server 106 at block 818 that the settlement was unsuccessful.

[0056] Alternatively, if an instant auction is requested, process 800 continues to block 816 and an instant auction is generated. During the instant auction, devices 104 associated with users who participated (or bid) in the listing generated at block 804 are given a second opportunity to bid on the item 102 during an instant auction. More particularly, once an instant auction is requested, the initial bid price is set to the highest bid received during the item listing. The participants of the listing then bid over either during a predetermined bid period, or on a variable bid period. When bidding during a variable bid period, the bid period may be extended for a predetermined period of time after each bid is received. Once either the predetermined bid period or variable bid period expires, the participants of the instant auction receive a notification as to whether they won or lost the bid, and process 800 ends.

[0057] Referring now to FIG. 8, illustrated is a flowchart depicting an illustrative method for maintaining inventory across a distributed network, in accordance with certain embodiments of the present disclosure, the method designated generally process 900. Process 900 starts at block 902, where the transaction server 106 (FIG. 1) receives input data associated with a particular item 102. {See block 302; FIG. 1.) Based on the input data, which is packaged and stored in the database 108 as item information 112a-112c, the transaction server 106 identifies ongoing auctions or brokered transactions which would be appropriate (e.g., would have items commiserate to the instant item 102, such as items of a similar value, condition, age, etc.) for inclusion of the present item at block 906. If the item is determined to be appropriate for a particular brokered transaction at block 906, the item 102, and more particularly the item information 112a-112c, is associated with a potential brokered transaction list at block 910. Once the item is associated with the potential brokered transaction list, or is determined not to be appropriate, process 900 continues to block 908. If, at block 908, there are more brokered transaction which are appropriate for inclusion of the particular item 102, process 900 returns to block 904 and continues the analysis of the remaining identified brokered transaction. Alternatively, if no more potential brokered transaction are determined to exist, process 900 continues to block 912, and the users in control of the potential brokered transaction are identified. If the users in control of the particular brokered transaction determine that it is desirable to include the item 102 in the brokered transaction, the users input an input into their respective device 104, thereby indicating to the transaction server 106 that the auction 700 (FIG. 6) would like to include the item 102. In embodiments, where more than one brokered transaction 700 indicates interest in including the item 102, the transaction server 106 determines which brokered transactions 700 to include the item in based on the items currently listed in the competing brokered transaction 700, the disparity (or lack thereof) between the value of the items in the brokered transaction 700, the location of the auctions 700 relative to the item for sale, and the like. At block 914, once the brokered transaction or brokered transactions 700 are identified by the transaction server 106, the item information 112a-112c is forwarded to the particular brokered transaction, and included in the transaction item list 704 for those particular brokered transaction 700. As will be appreciated, while the foregoing example is presented from the standpoint of a seller looking for auctions in which to place items, the process could work in reverse with the auction house identifying the items from the seller's inventory and requesting access to include the item in their auction.

[0058] It will be understood that, while certain processes and methods are described as being in a particular blocked order, such an order may not be necessary in all embodiments contemplated by the present disclosure. As such, the processes described by the present disclosure may be modified or otherwise altered without departing from the scope and spirit of the present disclosure. Likewise, while illustrative embodiments of this disclosure have been described with reference to the accompanying drawings, it is to be understood that this disclosure is not intended to be limited to these precise embodiments. Further, it is to be understood that various changes may be effected by one skilled in the art to the embodiments of the present disclosure without departing from the scope and spirit of the present disclosure. It will be understood that, while the present disclosure describes inventory management with respect to auctions and brokering, the present disclosure relates generally to inventory management, and as such should not be limited to the particular applications described hereinabove.

Claims

CLAIMS What is claimed is:

1. A system for managing inventory across multiple transactions, the system comprising: a first mobile device having a first sensor disposed thereon and configured to receive user input associated with an item at a first location, the first mobile device configured to, package the user input as item information;

a transaction server in electrical communication with the first mobile device, the transaction server configured to receive the item information from the first mobile device and located at a second location different from the first location;

a first database in electrical communication with the transaction server and configured to store the item information on a memory of the first database; and

a second database in electrical communication with the transaction server or the first database, the second database configured to receive item information redacted by the transaction server, store the redacted item information in a memory of the second database, and associate the redacted item information with the item information stored in the first database.

2. The system of claim 1, wherein the first mobile device is further configured to capture an image of the item at the first location and, in response to capturing the image, include the captured image in the item information.

3. The system of claim 2, further comprising a second mobile device in electrical communication with the transaction server, the second mobile device configured to selectively request item information or redacted item information from the transaction server.

4. The system of claim 3, wherein the transaction server is further configured to determine whether the second mobile device is permitted to receive the item information or the redacted item information and, in a case where the transaction server is permitted to transmit the item information or the redacted item information, transmit the item information or the redacted item information to the second mobile device.

5. The system of claim 4, wherein the transaction server is further configured to modify the item information or the redacted item information based on input received from the first mobile device or the second mobile device.

6. The system of claim 1, wherein the transaction server is configured to associate the item information with auction data stored in the database and, based on the auction data, calculate a suggested sale price of the item associated with the item information.

7. The system of claim 6, wherein the transaction server is configured to associate the item information with one or more auctions based on the calculated suggested sale price of the item associated with the item information.

8. The system of claim 7, wherein the transaction server is configured to disassociate the item information with the auction in a case where the suggested sale price is recalculated and, based on the recalculation, the item information is no longer appropriate for the auction associated with the item information.

9. A method of managing inventory across multiple transactions, the method comprising: receiving item information associated with an item at a transaction server from a first mobile device having a first sensor disposed thereon at a first location;

storing the item information in a first database in electrical communication with the transaction server;

generating redacted item information by redacting the item information at the transaction server and subsequently storing the redacted item information; and

storing the redacted item information in a second database in electrical communication with the transaction server or the first database, the redacted item information associated with the item information.

10. The method of claim 9, wherein receiving item information at the transaction server includes receiving item information from the mobile device of a type selected from the group consisting of image data, text data, and audio data.

11. The method of claim 10, further comprising receiving a request from a second mobile device at the transaction server to receive either the item information or redacted item

information.

12. The method of claim 11, further comprising determining, based on the request from the second mobile device, whether the second device is permitted to receive either the item information or the redacted item information and, in a case where the transaction server is permitted to transmit the item information or the redacted item information, transmitting the item information or the redacted item information to the second mobile device.

13. The method of claim 12, further comprising:

receiving item information from the second mobile device; and

modifying the item information or the redacted item information based on input received from the second mobile device.

14. The method of claim 13, further comprising associating the item information with auction data stored in the database.

15. The method of claim 14, further comprising disassociating the item information with the auction data in a case where the item information is no longer appropriate based on items associated with the auction data different from the item information and the item information.