Consumer marketplace sourcing system
Patent Information
- Application Number
- EP2023866560
- Authority / Receiving Office
- EP · EP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2022-09-15
- Filing Date
- 2023-09-15
- Publication Date
- 2025-07-23
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Existing eMarketplace platforms require extensive inputs and processing, making them difficult to navigate and utilize, especially for individuals, and often require significant computational resources and memory, leading to inefficiencies in sourcing and bidding processes.
A computerized method using a marketplace sourcing platform that receives inputs via a user interface, including UNSPSC identifiers, to define and validate RFPs, RFQs, or RFIs, and generates bids, reducing processor load, memory requirements, and improving user interaction through a system that processes inputs for sourcing goods and services efficiently.
The solution enables faster, less costly, and more accurate bid generation and execution, improving user experience by reducing the complexity and computational demands of the sourcing process, while enhancing usability and efficiency in connecting consumers and sellers.
Smart Images

Figure 1.1
Abstract
Description
TE Docket No.: 018468-000014 CONSUMER MARKETPLACE SOURCING SYSTEM CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This non-provisional application claims the benefit of and priority to U.S. Provisional Application No.63 / 407,043, entitled “Consumer Marketplace Sourcing System” filed September 15, 2022, the disclosure of which is hereby incorporated by reference herein in its entirety. BACKGROUND
[0002] Electronic bidding and / or sourcing systems, such as sourcing software or online sourcing systems, are designed to connect consumers of products and services with sellers. For example, online marketplaces, auctions, bidding sites, etc., are used by companies and individuals to sell and buy goods and services. However, these online systems can be difficult to navigate and utilize, such as for individuals, and are often designed for specific applications. SUMMARY
[0003] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key factors or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
[0004] One or more techniques and systems described herein can be utilized for connecting consumers and seller using an eMarketplace sourcing platform. For example, systems and methods of generating bids for different projects, jobs, etc. described herein, can utilize an online sourcing platform for buying and selling products and services.
[0005] In one implementation, a computerized method for sourcing goods and / or services comprises receiving inputs via a user interface via a marketplace sourcing platform, wherein the inputs are received from one or more consumers and one or more vendors, and the inputs comprise at least one UNSPSC identifier. The computerized method further includes defining elements of at least one of an RFP, an RFQ, or an RFI using the received inputs using the marketplace sourcingplatform, wherein the elements are based at least in part on the received inputs, and validating the one or more elements of the RFP, the RFQ, or the RFI. The computerized method also includes generating one or more bids using the validated one or more elements and receiving via the marketplace sourcing platform, one or more responses relating to the one or more bids. The computerized method additionally includes outputting a final bid based in part on the received one or more responses and processing payment for at least a portion of the final bid based on performance tracking using the marketplace sourcing platform.
[0006] To the accomplishment of the foregoing and related ends, the following description and annexed drawings set forth certain illustrative aspects and implementations. These are indicative of but a few of the various ways in which one or more aspects may be employed. Other aspects, advantages and novel features of the disclosure will become apparent from the following detailed description when considered in conjunction with the annexed drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0007] FIGURE 1 is a block diagram illustrating one implementation of a sourcing system according to an implementation.
[0008] FIGURE 2 is a block diagram of a marketplace sourcing system according to an implementation.
[0009] FIGURES 3-5 show a flowchart of a process flow illustrating operations involved in a registration process for a marketplace sourcing system according to various implementations.
[0010] FIGURES 6-9 show a flowchart of a process flow illustrating operations involved in a bidding process for a marketplace sourcing system according to various implementations.
[0011] FIGURES 10 and 11 show a flowchart of a process flow illustrating operations involved in a contracting process for a marketplace sourcing system according to various implementations.
[0012] FIGURES 12 and 13 show a flowchart of a process flow illustrating operations involved in a payment process for a marketplace sourcing system according to various implementations.
[0013] FIGURES 14 and 15 illustrate a vendor registration user interface according to various implementations.
[0014] FIGURE 16 illustrates a signing account details user interface according to various implementations.
[0015] FIGURE 17 illustrates a payout account details user interface according to various implementations.
[0016] FIGURE 18 illustrates a contract selection user interface according to various implementations.
[0017] FIGURE 19 illustrates a bid request user interface according to various implementations.
[0018] FIGURE 20 illustrates bid summary user interface according to various implementations.
[0019] FIGURE 21 illustrates another bid summary user interface according to various implementations.
[0020] FIGURE 22 illustrates a bid detail user interface according to various implementations.
[0021] FIGURE 23 illustrates a transactions user interface according to various implementations.
[0022] FIGURE 24 is a block diagram of an example computing environment suitable for implementing various examples of a sourcing platform. DETAILED DESCRIPTION
[0023] The claimed subject matter is now described with reference to the drawings, wherein like reference numerals are generally used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the claimed subject matter. It may be evident, however, that the claimed subject matter may be practiced without these specific details. In other instances, structures and devices are shown in block diagram form in order to facilitate describing the claimed subject matter.
[0024] generally to a computer system which is used to electronically perform trades on an exchange, and more particularly, to a system which electronically tracks a focus of the user of the computer system and prioritizes the updating of the information displayed on one or more display units of the computer system based on the tracked focus.
[0025] The methods and systems disclosed herein, for example, may be suitable for use by consumers and sellers in an online marketplace environment. Various examples provide a computer system that implements a diverse marketplace with a broad range of access to consumers, business owners, non-business owners, etc. The computer system in some example is operable to provide one or more sourcing platforms that are configured to connect consumers of products and services with many different types of sellers (e.g., from babysitters to Fortune 500 corporations to government entities). Various examples allow consumers and sellers to discover new opportunities within an eMarketplace. Sourcing is easily accessible, for example, from a mobile phone or laptop / PC, for performing all types of purchasing. It should be noted that the examples given herein are merely for illustration. That is, one or more herein described examples can be used in different applications, such as a consumer application (e.g., a business-to-consumer (B2C) application), as well as a business-to-business (B2B) application and / or a business-to-government (B2G) application. Some examples provide peer-to-peer procurement. It should be appreciated that the one or more examples can be used or implemented by any type of vendor (e.g., small business or government) and any type of consumer. That is, different types of entities can use and / or operate one or more examples.
[0026] In one or more examples, a “BidLock” system is configured as a consumer eMarketplace sourcing platform that is an open eMarketplace platform promoting competition for all sellers. Using one or more examples, consumers are able to leverage the same purchasing power used by, for example, major corporations and to provide an eMarketplace for all sellers to excel. For consumers, various examples improve or maximize the value and reduce or minimize risks of purchases made on the eMarketplace platform. For sellers, various examples provide an opportunity that offers an expansive and scalable consumer marketplace, as well as allowing, for example, contract bidding (e.g., government contract bidding), wherein the entire procurement process is handled within one or more systems or platforms described herein.
[0027] Thus, improvements to a sourcing and / or marketplace system are provided that can result in the generation and execution of bids / proposals in a faster, less costly, more competitive, and / or more accurate manner. That is, bids / proposals can be generated and executed with reduced costs, risks and time associated with the buying and selling of products and services, as well as contracting or procuring products and services. In this manner, when a processor is programmed to perform the operations described herein, the processor is used in an unconventional way that allows for more efficient and reliable sourcing and bid generation and execution and / or procurement, which results in an improved user (e.g., consumer) experience.
[0028] Various examples provide a computer implemented systems for dynamic sourcing, which includes personal and professional applications having contract management capabilities. One or more consulting services and / or applications (e.g., configured as application programming interfaces (APIs)) focus on aiding consumers and business / government professionals to provide a portal or platform for different types of consumers and different types of vendors. One or more examples facilitate consumers or other entities in meeting purchasing (or selling) objectives prior to submitting a bid and assist vendors with understanding how to get the “most” out of proposals. The services can include, for example, consumer consulting, business consulting, government consulting, outsourcing operations, and not-for-profit consulting, among others as described herein.
[0029] One or more examples provide various options for consumers and sellers, such as different plans and levels of service. That is, different membership plans to the eMarketplace platform are provided in various examples. It should be noted that the membership plans can include no-cost (free) and pay plans. For example, a tiered structure based on the plan can be provided that allows for consulting services with respect to providing a defined number of actions (e.g., a defined number of request for information (RFI) responses per month, a defined number of request for quotation (RFQ) responses per month, a defined number of request for proposal (RFP) bids (or unlimited), and a defined number of proposal submittals per month), which in some tier levels have a maximum amount and in other tier levels are unlimited. In some examples, a “Bidlink” system allows for members to collaborate, network and exchange ideas to get the most out of business engagements through the “BidLock” system. For example, communication between members is provided in a managed manner throughout the entire procurement process.
[0030] It should be appreciated that the herein described examples can be used in different settings or environments, such as for different types of sourcing and bidding operations. That is, many different types of good and services at any price point can be sourced using one or more processes of an eMarketplace platform as described in more detail herein. In some examples, the techniques described herein can be configured (e.g., software reused) to solve different sourcing problems by providing different dynamically configurable bidding and sourcing interfaces. As such, different provisioners of the systems can differentiate offerings by providing different bids generated for particular users or use cases. In some examples, users can be offered different bids or proposals based on an individual’s or entity’s particular goals, characteristics, and selection process.
[0031] As should be appreciated, the herein-described examples may be implemented using computer programming or engineering techniques including computer software, firmware, hardware or any combination or subset thereof, wherein the technical effect may be achieved by performing one or more operations described herein. At least one technical problem with prior eMarketplace platforms is that the systems can require extensive inputs and searching, which can require a large amount or computations or processing, to provide a desired or required output. The systems and methods described herein address this technical problem by improving input and searching / processing operations within one or more platforms, by using at least easier to process criteria and / or processes in some examples. One or more technical effects provided by (i) receiving inputs via a user interface of a marketplace sourcing platform, wherein the inputs are received from one or more consumers and one or more vendors, and the inputs comprise at least one United Nations Standard Products and Services Code®(hereinafter UNSPSC or UNSPSC) identifier, and (ii) defining elements of one of an RFP or RFQ using a marketplace sourcing platform, wherein the elements are based at least in part on the received inputs, to identify one or more entities to provide the RFP or RFQ and generate a corresponding bid, include one or more of a reduced processor load, less memory space required, reduced hardware requirements, enhanced reliability, and improvements in user interaction (such as improved usability, improved user efficiency, and increased user interaction performance).
[0032] In one or more examples, a computer system is configured to provide one or more of:
[0033] Source-to-Pay portal dedicated only to Small Businesses;
[0034] Partnership Development (Joint Ventures & Consortiums);
[0035] Public and Private Sector Contract Management and Compliance;
[0036] Government Bid and Contract Interpretation and Support;
[0037] B2B and B2G Consultation for Small Disadvantaged Businesses;
[0038] Supplier Diversity Partnering Support and Consultancy;
[0039] Not-For-Profit Procurement and Long-Term Cost Savings Solutions; and
[0040] Create Custom Product and Service Delivery Strategies.
[0041] It should be noted that one or more examples can be implemented in different applications. That is, one or more herein described examples can be configured or implemented in different practical applications across many different industries and sectors, such as, for example, e-commerce transactions (e.g., e-commerce auctions or bidding, real estate auctions, charity auctions, etc.), government procurement, contract bidding, product or service procurement, and bookings, among others.
[0042] In one or more examples, a marketplace sourcing platform 100 is provided as illustrated in FIGURE 1. The marketplace sourcing platform 100 in various examples is configured as a sourcing system to receive one or more inputs 104, such as different inputs 104 from consumers and / or vendors via consumer and / or vendor portals, respectively. In the illustrated example, the inputs 104 include elements, requirements, options, etc. for sourcing and / or procuring the sale of goods and / or services. However, it should be appreciated that the illustrated inputs 104 are merely for example, and other inputs can be used by the marketplace sourcing platform 100. That is, the marketplace sourcing platform 100 can be configured to generate different types of bids and / or proposals, such as for the sale of different goods or the performance of different services.
[0043] With respect to the inputs 104, one or more variables, fixed requirements, etc. can be defined. As such, easily customizable bids and / or proposals can thereby be generated. In various examples, an end-to-end approach to sourcing of goods and services allows for dynamic creation of bids and / or proposals with one or more user definitions. For example, one or more requirements can be generated and validated, with corresponding actions tracked, and payment made accordingly (e.g., payments from an escrow account at an escrow system 106). In some examples, the inputs include one or more classification codes or other identifiers relating to the project, work,etc. to be performed. That is, the inputs 104 include codes that classify or relate to the goods or services of interest. In one particular example, the one or more classification codes are a UNSPSC identifiers. In this example, one or more UNSPSC identifiers corresponding to a hierarchical classification code set are used to identify the type of goods or services desired or required by the consumer (or other entity) and / or available or offered by the vendor. That is, in some examples, the UNSPSC identifier is used to identify matching consumers and vendors relating to marketplace sourcing for one or more goods and services. For example, the UNSPSC identifier allows for matching consumers and vendors to participate in a particular bidding or sourcing process. Thus, in one or more examples, the UNSPSC identifiers are used to define the particular desired bidding or sourcing project and not for general purchase / acquisition in the supply chain.
[0044] In operation, the marketplace sourcing platform 100 receives the inputs, processes the inputs 104 (e.g., requirements, cost, UNSPSC identifiers, etc.), and generates as an output, one or more bids / proposals 108 (or other types of quotes) for consideration and / or execution. The marketplace sourcing platform 100 allows for dynamically generating many different types of bids / proposals 108, wherein one or more instances of the marketplace sourcing platform 100 (including one or more user interfaces as described in more detail herein) can then be run on a user device, which allows interaction thereof by the user (e.g., seller or consumer).
[0045] In some examples, the marketplace sourcing platform 100 can be implemented in software, hardware, or a combination thereof. For example, a series of software packages implementing one or more aspects of the marketplace sourcing platform 100 can be provided. In this example, the marketplace sourcing platform 100 is configured to generate one or more bids / proposals 108 that are used to execute jobs, activities, tasks, sale of goods, etc. corresponding to one or more UNSPSC identifiers, which can be further defined in some examples (e.g., user modifications). In one example, a tracking feature can generate specific requirement that can be followed. Feedback is received in some examples, such as indicating that an activity, task etc. is not completed and / or is completed. It should be appreciated that by using the marketplace sourcing platform 100, the performance of the sale or service is thereby made dynamic. That is, the various steps from bidding, to validation, to performance, to payment, are not static.
[0046] It should also be appreciated that the marketplace sourcing platform 100 is not limited to generating specific types of bids / proposals, but can be used to generate bid / proposals for manydifferent applications. Additionally, the goods and / or services are not necessarily limited to specific UNSPSC identifiers and can include good / services that are differently or additionally defined.
[0047] In some examples, the marketplace sourcing platform 100 is configured to generate preprogrammed, predefined, or prepopulated templates to facilitate the bidding process. In one example, empirical, experimental or simulation data is used to train or configure the marketplace sourcing platform generator 100, and then the inputs 104 are processed to generate one or more bids / proposals 108. In some examples, machine learning is used to train or configure the marketplace sourcing platform 100 based on a training data from simulations or feedback received from previously generated bids or proposals 108. In some examples, artificial intelligence (AI) is used as part of the training of and / or processing by the marketplace sourcing platform 100 to generate improved bid / proposal generation, execution, and payment.
[0048] One particular implementation includes a marketplace sourcing system 200 as illustrated in FIGURE 2. In some examples, the marketplace sourcing system 200 is implemented as part of or includes the marketplace sourcing platform 100. The marketplace sourcing system 200 in one example is a processing machine that can be used in combination with one or more other systems (e.g., escrow systems, monitoring systems, etc.) to generate one or more bids / proposals 108. More particularly, the marketplace sourcing system 200 includes a marketplace sourcing processor 202 (also referred to as the sourcing processor 202) that is configured as a processing engine that performs operations to identify, generate, track, and / or execute payment for the sale and / or procurement of one or more goods and / or services based on one or more input data 204, illustrated as a request for bids (which in some examples relate to goods or services defined by the one or more UNSPSC identifiers). It should be noted that the input data 204 can include different types of data configured in different ways corresponding to different types of bids, goods and services to be performed, etc. (e.g., different or in addition to the UNSPSC identifiers). It should also be noted that the examples described in the present disclosure can be applied to different types of data, including non-bidding data. In some examples, the input data 204 is obtained via a user interface (e.g., one or more of the user interfaces illustrated in FIGURES 14-23) having selectable elements or fields (e.g., selectable UNSPSC identifiers displaying corresponding description of the codes). In various examples, manual entry of input data (e.g., consultant reviewed or validated data) is additionally or optionally performed.
[0049] In operation, the sourcing processor 202 has access to the input data 204, such as the different types of inputs 104 and performs one or more operations as illustrated in FIGURES 3-13 and described in more detail herein. It should be appreciated that the sourcing processor 202 is configured to perform sourcing operations in a wide variety of application domains. For example, the implementations of the present disclosure provide for bid / proposal generation and execution in a consumer domain, but various implementations can be used in other domains, such as within a business domain or a government domain.
[0050] In the illustrated example, the input data 204 includes requirements, variables, etc. relating to one or more of a sale of goods and / or services, wherein the marketplace sourcing processor 202 processes the input data 204 using a bid processor 206 as described in more detail herein. In some examples, the bid processor 206 processes the input data 204 using one or more algorithms or data structure processing engines that use different types of information corresponding to the input data 204 to create, for example, one or more RFQs, RFPs, or RFIs based on the input data 204 and source information 212 (e.g., information relating to the abilities of different sources for the sale of goods and services that are defined by UNSPSC identifiers some examples) that are validated in some examples. That is, the bid processor 206 generates options based on the request for bids and the source information 212 that are evaluated and / or selected at 208. For example, one or more options or components relating to RFQs, RFPs, or RFIs can be modified and / or accepted. It should be noted that the evaluation and / or selection performed at 208 is an iterative process in various examples as described in more detail herein. As such, the input data 204 is used to determine or define elements for a desired or required RFQ, RFP, or RFI based on the received input data 204 and generate the corresponding options.
[0051] In the implementation illustrated in FIGURE 2, the sourcing processor 202 performs processing using source information 212 to generate an output. For example, using one or more answers (in response to input requirements or queries), the sourcing processor 202 applies a rules engine to construct a finalized agreement and performs different phases of payment processing at 214 that is output as a final agreed to proposal, which in various examples includes identified actions, tasks, etc. for the proposal. In some examples, the proposal includes a checklist 218 that is populated and can be used for tracking as described in more detail herein.
[0052] In some examples, a control interface 216 is configured to allow interaction with the marketplace sourcing system 200. For example, the control interface 216 includes one or more user interfaces (see FIGURES 14-23) configured to receive the input data, as well as other information, such as feedback 222 as described in more detail herein. That is, the control interface 216 allows for user inputs or other inputs to be received and utilized by the marketplace sourcing processor 202 in bid / proposal assessment, validation, and generation as described in more detail herein. In some examples, the control interface 216 is a UNSPSC centric interface that initiates marketplace sourcing based on the UNSPSC identifiers, such as allowing searching based on UNSPSC identifiers (e.g., search for roofing services, legal services, contract services, etc. and then a drop down of the descriptions of the UNSPSC identifiers is displayed).
[0053] Reponses to one or more items in the checklist 218 (e.g., activities to be performed, tasks to be performed, etc.) in some examples are received manually by a user input or automatically from one or more monitoring devices. That is, responses are provided as feedback 222 to the marketplace sourcing processor 202. For example, with the input data 204 processed as described above, the marketplace sourcing processor 202 generates a finalized proposal, which is used to produce the output. The feedback 222 is then used in various examples to confirm performance, which in some examples, includes confirming that one or more items on the checklist 218 and / or that further actions / tasks are to be performed.
[0054] Various inputs and / or operations can be performed using one or more end user devices, for example, a smart phone 224, a laptop computer 226, or other end user computing device, which allow for user input. In some examples, one or more monitoring devices, such as a camera 228 (or other imaging or non-imaging sensor) are configured to acquire information and automatically provide information, which can include the feedback 222. It should be noted that in some examples, the marketplace sourcing platform 100 or components thereof are configured as a downloadable application that can be stored and loaded to one or more of the end user devices. The end user device is able to use the marketplace sourcing platform 100 to generate one or more RFPs, RFQs, and / or RFIs, and corresponding bids and / or proposals.
[0055] In some implementations, the marketplace sourcing platform 100 and / or the marketplace sourcing system 200 is operable and configured to perform one or more operations, including a registration process (see FIGURES 3-5), a bidding process (sees FIGURES 6-9), acontracting and / or selection process (see FIGURES 10 and 11), and a delivery and / or transaction completion / payment process (see FIGURES 12 and 13). In particular, flowcharts 300-500 are process flows illustrating operations involved in one or more sourcing operations. With the processes illustrated by the flowcharts, in various examples, the entire sourcing process is centralized from end-to-end.
[0056] Regarding the registration process at 300 (shown in FIGURES 3-5), both vendors and consumers initially interact with the marketplace sourcing platform 100 and / or the marketplace sourcing system 200 such as via a website at 302, 304 to perform an initial registration (e.g., set up user account, provide initial user details, etc.), which initial registration data is then stored at 306. For example, the user enters information regarding the person or entity registering (e.g., contact information, etc.). The user then reviews the terms for accessing and using the marketplace sourcing platform 100 and / or the marketplace sourcing system 200 at 308, 310 and can accept the terms at 312, 314 or reject the terms at 316, 318. If the terms are rejected, the process ends and the user cannot access the marketplace sourcing platform 100 and / or the marketplace sourcing system 200 (e.g., cannot participate in sourcing using one or more herein described platforms). If the terms are accepted, then at this point, in one or more examples, the user (e.g., consumer, business entity, government entity, etc.) becomes a member of the marketplace sourcing platform. That is, membership within the marketplace sourcing platform is required in various examples before access to the features and operations of the marketplace sourcing platform is made available. Thus, the initial registration process includes various steps of accepting the terms for membership to use the marketplace sourcing platform, and entering initial user information. It should be appreciated that some of the steps are the same for different types of users, such as consumers and vendors.
[0057] Once the terms are accepted at 312, 314, instructions on using the marketplace sourcing platform 100 and / or the marketplace sourcing system 200 via the website or other application can be reviewed at 317, 319. Additionally, the user can contact the host of the marketplace sourcing platform 100 and / or the marketplace sourcing system 200 with questions at 320, 322, as well as evaluate one or more plan options at 324, 326. A determination is then made whether the user does not want to proceed at 328, 327 (e.g., receive a user input declining the terms of user) or does want to proceed at 325, 330. If the user proceeds, contact data 602 (e.g., name, address, phone number, etc.) is received at 332, 334, such as on a registration page (e.g., a vendor registration userinterface 600 displayed as a vendor screen via the website as illustrated in FIGURES 14 and 15), and the information is then verified at 336, 338, including verifying the user’s email address at 340, 342. It should be appreciated that any suitable verification process can be used, and after which, a login page is presented to the user at 344, 346 (e.g., display login page user interface).
[0058] Thereafter, a user is able to log in to the marketplace sourcing platform 100 and / or the marketplace sourcing system 200 such as via a website and the system is configured to receive more detailed information regarding the user at 348, 350, such as by inputting data using the vendor registration user interface 600. For example, individual or business information is received (see FIGURES 14 and 15), such as contact data 604, diversity information 606, business identification numbers 608 (e.g., DUNS number, NAICS number, PCS number), payment terms 610, certifications 612 (e.g., diversity certifications), UNSPSC products / services 614 (e.g., select or identify UNSPSC identifiers to be associated with the vendor in the vendor profile) for the user, etc. The detailed information is verified at 352 and stored at 354. Again, any suitable verification process can be used, such as to confirm the validity or accuracy of the information that was input. It should be noted that the information input using the vendor registration user interface 600 (or other interfaces described herein) is performed using one or more fields or drop-down menus 616 on a vendor screen (user interface) or consumer screen (user interface) in some examples.
[0059] With the user information verified, contract management and payment accounts are set up at 356 when accessing the vendor portal, namely for vendor registration. For example, a contract management account (e.g., DocuSign account) is setup at 358 as illustrated by the vendor dashboard (provided as part of the vendor screen and showing a DocuSign account details page 620) shown in FIGURE 16 and then an account is selected, illustrated as a Bidlock account at 360 or a vendor account at 362. With the vendor account, log in is performed at 364 with a corresponding API account ID / key code then obtained at 366, which is then added to the vendor account at 368. A payment account is selected at 370, such as an credit card account at 372 and an escrow account at 374. For the escrow account, an escrow email is received at 376 and log in to the account provided at 378, with a corresponding API account ID / key code then obtained at 380 (using an escrow API process), which is then added to the vendor account at 382. For the credit card account, log in is performed at 384 with a corresponding API account ID / key code then obtained at 386, which is then added to the vendor account at 388. In one or more examples, the registration process is now completed and ends. It should be noted that the vendor dashboardcan provide different information during one or more operations of the marketplace sourcing platform 100 and / or the marketplace sourcing system 200, such as a payout accounts detail page 630
[0060] It should be noted that the registration process in some examples includes subscribing to a membership types (e.g., level or tier of service). It should also be noted that in various examples a vendor is any person or entity offering a good and / or service for sale, lease, rent, etc. And, in various examples a consumer is any person or entity that desires to consume (e.g., purchase) a good and / or service for sale, lease, rent, etc. It should further be noted that the registration process is performed in various examples to allow access to any of the operations or functions of the marketplace sourcing platform.
[0061] The registered person or entity can then access the bidding functionality of the marketplace sourcing platform to initiate one or more bids, such as for the sale of goods and / or services using the process 400 (shown in FIGURES 6-9). In some examples, the consumer accesses the bidding process and functionality of the marketplace sourcing platform 100 and / or the marketplace sourcing system 200 using a consumer portal and one or more consumer user interfaces and the vendor accesses the bidding process and functionality of the marketplace sourcing platform 100 and / or the marketplace sourcing system 200 using a vendor portal and one or more vendor user interfaces. As can be seen in FIGURE 6, the bidding process is initiated at 402 by the consumer (or other purchaser), which in some examples, then includes performing a search for goods / services at 404. In some examples, the search includes receiving one or more UNSPSC identifiers relating to one or more goods / services. Thereafter, bid request information is received at 406 (e.g., user input of bid request via a bid request page 650 of a consumer dashboard as illustrated in FIGURE 19) and the user can view a summary of the request at 408, which can be modified at 410 or submitted to the marketplace sourcing platform 100 and / or the marketplace sourcing system 200 at 412 for processing. The bid request page 650 in some examples allows for input of contract details, as well as searching for a product or service in one or more category listings 652. One or more criteria selections 654 can also be made and details of the scope of requirements 656 (e.g., bidder requirements) input.
[0062] In some examples, review of the bid request is performed at 414, which may be a manual review (e.g., by a Bidlock representative) or an electronic review, such as using one ormore automated review processes. If the request is found to have issues, not be compliant, etc., the request is rejected at 416 and a modification can be made at 410. It should be noted that the consumer dashboard in some examples forms part of a consumer portal and the vendor dashboard forms part of a vendor portal implemented by the marketplace sourcing platform 100 and / or the marketplace sourcing system 200.
[0063] If the request is accepted, then vendor matching is performed at 418. For example, vendors that are registered with the marketplace sourcing platform 100 and / or the marketplace sourcing system 200 and that are associated with the UNSPSC product / service (e.g., vendor profile includes the UNSPSC product / service) receive a bid notification at 418, which can be reviewed online at 420. If the bid is declined by a vendor, a notification is generated and sent to the consumer and received at 422 (e.g., notification that the vendor has declined to participate in the bid). If the bid is accepted at 424, questions or comments regarding the bid are received from the vendor at 426 and consumer responses received at 428.
[0064] After questions and comments are addressed, the bid (e.g., proposal) is submitted at 430, which results in notification to the consumer at 432 and notification to a Bidlock representative at 434. It should be noted that multiple proposals from multiple vendors are received in some examples and sorted at 436 with bids in process and proposals received viewed on a bid summary page 660 of the consumer dashboard as illustrated in FIGURE 20 and a bid summary page 670 of the vendor dashboard as illustrated in FIGURE 21. That is, as described herein, in addition to the consumer receiving notifications of the bids in process, the vendor also receives notification if categories are matched. In some examples, a bid detail page 680 as illustrated in FIGURE 22 is displayed via the consumer dashboard and / or the vendor dashboard, and that allows for review of the bid proposal (e.g., pricing, attachments, etc.).
[0065] Additional question or comments can be received at 438, which results in initiation of a live chat at 440 in some examples. Thereafter, a vendor selection from the consumer is received at 442 and notification provided to the vendor at 444 (e.g., email or other electronic communication to the vendor). Additionally, notification to a Bidlock representative is provided at 446. It should be noted that in one or more examples, the Bidlock representative can be an individual operating or coordinating with the marketplace sourcing platform 100 and / or the marketplace sourcingsystem 200 or a system or component of the marketplace sourcing platform 100 and / or the marketplace sourcing system 200.
[0066] Confirmation by the consumer of the notification is received at 448 and a transaction process is initiated at 450, which includes payment (e.g., credit card payment) at 452. In some examples, the payment is payment of the full amount for the bid, but can be less than the full amount as well. The contracting process then begins at 454, 456, which includes transfer of a fee to Bidlock at 458 that is received at 460. For example, the fee is paid from funds in escrow that were received as part of the credit card payment. As such, in various examples, in order for the process to continue, payment of the fee to Bidlock is required. It should be noted that as used herein, in various examples, Bidlock refers to the entity, system, and / or other component that is associated with, operates, and / or controls the marketplace sourcing platform 100 and / or the marketplace sourcing system 200.
[0067] Notification is then provided at 462 that the process can proceed. If a determination is made at 464 that no contract is needed (e.g., no payment stages), a credit card payment process is initiated at 466. If a determination is made at 468 that a contact is needed, notification is sent to the vendor at 470 with an appropriate contracted selected and provided at 472. For example, a template or base contract is selected from a vendor account at 474, or if not available, a contract is selected from a Bidlock account at 476. That is, different databases of selectable contracts are provided in some examples and can be accessed via the vendor dashboard using an add contract screen 640 as shown in FIGURE 18. That is, selection of one or more products contracts, service contracts, and / or supporting documentation uploaded by the vendor or a template document (Bidlock contract) can be searched and accessed. It should be noted that in various examples, when use herein, a “screen” refers to a user interface configured to be displayed for interaction with and to receive inputs from a user.
[0068] The selected contract is them customized or modified based on the proposal at 478 and the contract associated with the bid (e.g., attached to a bid file) at 480. Notification of the contract is provided to the consumer at 482, which can be accessed for review and finalization at 484. If the contract is rejected at 486, then modification can be made at 478 (e.g., receive vendor or consumer changes to terms), and if the contract is accepted at 488, then the contract is signed at 490 (e.g., electronically signed) and saved at 492, such as within a password or encrypted file.Notification of the contract finalization is then provided to the Bidlock entity at 494. In some examples, details of transactions corresponding to the accepted contract, including allowing payments, etc. is displayed on a transactions page 690 of the consumer dashboard as illustrated in FIGURE 23. In some examples, multiple payments, such as milestone payments, can be made.
[0069] Thus, in various examples, a sourcing option (e.g., RFI, RFP, or RFQ) is selected and a search performed of different categories for desired or requested goods (products) or services, which can include receiving user inputs of specific scope requirements that can include supporting information. The accuracy of the project information is confirmed at and a bid thereafter submitted in the marketplace sourcing platform as one or more requests (which includes matching UNSPSC identifiers in some examples). The requests are reviewed and can be accepted or rejected at, with further review performed. A proposal is then generated. As should be appreciated, the process in various examples results in a number of bids or bid responses being received that begins a selection process as described herein. In some examples, interactions between the consumer and vendor occur, such as live chats, with the consumer then selecting a bid, which results in notification being provided to the vendor having the bid selected and an administration fee initiated (e.g., a fee for locking in the bid – BidLock fee, which may be a platform fee or a processing fee). The agreement between the selected vendor and the consumer is finalized with the finalized agreement resulting in the administration fee being released (e.g., payment for the successful bid and acceptance).
[0070] A payment process 500 is then performed as shown in FIGURES 12 and 13. The payment process 500 in some examples includes a delivery / transaction process that includes sending payment(s) per the agreement terms (e.g., payment of the goods and / or services, refunds, etc.) to escrow. That is, in various examples, all transactions are managed by an escrow service that receives one or more invoices. Once delivery of the goods and / or services have been completed and satisfied (e.g., terms of the agreement are satisfied), vendor payment is released and the transaction closed. More particularly, notification of the finalized contract is sent to the consumer and vendor at 502, 504, which triggers logging into the escrow account by the consumer at 506 to create an escrow transaction. A notification is then sent to the vendor at 508 regarding accepting the escrow terms, including confirming escrow payments at 510, which results in payments being loaded or transferred into the escrow account at 512. Notification is then provided to the vendor at 514 that the escrow funding has been added with all payment transactions thereafter being monitored and managed at 516 by an escrow service. A disbursement methodinput is received from the vendor at 518 with the product or service then delivered (e.g., product delivered or service performed) at 520. Notification of delivery of the product or service is provided at 522, receipt of which is acknowledged by the consumer at 524. It should be noted that the various notifications, acknowledgments, etc. are automatically generated by the marketplace sourcing platform 100 and / or the marketplace sourcing system 200 and communicated using one or more systems or platforms as described in more detail herein in some examples. In this particular, example, data relating to the delivery is captured and stored at 526 as a record or receipt. Once payments have been released by the marketplace sourcing platform 100 and / or the marketplace sourcing system 200, such as automatically in response to the confirmed receipt, notification is provided to the vendor at 528 and payment is released at 530 (e.g., escrow funds transferred to vendor account as set up in the vendor profile). Thereafter, consumer rating of the vendor performance is received at 532 (e.g., user input into a vendor performance survey or evaluation). The process then ends at 534. It should be noted that one or more operations performed on the consumer system (or portal), the vendor (e.g., small business) system (or portal), the contract management system (or portal), the escrow system (or portal), and / or the Bidlock system (or portal) can be the same or similar (or different), can occur simultaneously, concurrently, or sequentially, and can be interrelated.
[0071] Thus, one or more examples provide a computer implemented (e.g., online) marketplace for different types of entities and individuals, such as business owners, non-business owners, everyday individuals, government entities, etc. The herein described examples provide an improved process for sourcing good and services online that uses UNSPSC identifiers to define the goods / services involved and operations performed in the marketplace process.
[0072] It should be appreciated that the user interfaces described are merely examples of user interface configured to allow interaction with the marketplace sourcing platform 100. Additional or fewer interfaces, as well as interfaces configured to receive different inputs, display different information, etc. are also contemplated. In various examples, one or more of the interfaces are configured to provide interaction with the marketplace sourcing platform 100 and / or the marketplace sourcing system 200using one or more UNSPSC identifiers to define, select, initiate, etc. the search process, the bidding process, etc. or other process described herein. Additionally, while various examples are described with respect to an RFP, an RFQ, or an RFI, other types of requests are contemplated and can be implemented as described herein.
[0073] With reference now to FIGURE 24, a block diagram of the computing device 700 suitable for implementing various aspects of the disclosure is described (e.g., the marketplace sourcing system 200). FIGURE 24 and the following discussion provide a brief, general description of a computing environment in / on which one or more or the implementations of one or more of the methods and / or system set forth herein may be implemented. The operating environment of FIGURE 24 is merely an example of a suitable operating environment and is not intended to suggest any limitation as to the scope of use or functionality of the operating environment. Example computing devices include, but are not limited to, personal computers, server computers, hand-held or laptop devices, mobile devices (such as mobile phones, mobile consoles, tablets, media players, and the like), multiprocessor systems, consumer electronics, mini computers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
[0074] Although not required, implementations are described in the general context of “computer readable instructions” executed by one or more computing devices. Computer readable instructions may be distributed via computer readable media (discussed below). Computer readable instructions may be implemented as program modules, such as functions, objects, Application Programming Interfaces (APIs), data structures, and the like, that perform particular tasks or implement particular abstract data types. Typically, the functionality of the computer readable instructions may be combined or distributed as desired in various environments.
[0075] In some examples, the computing device 700 includes a memory 702, one or more processors 704, and one or more presentation components 706. The disclosed examples associated with the computing device 700 are practiced by a variety of computing devices, including personal computers, laptops, smart phones, mobile tablets, hand-held devices, consumer electronics, specialty computing devices, etc. Distinction is not made between such categories as “workstation,” “server,” “laptop,” “hand-held device,” etc., as all are contemplated within the scope of FIGURE 24 and the references herein to a “computing device.” The disclosed examples are also practiced in distributed computing environments, where tasks are performed by remote- processing devices that are linked through a communications network. Further, while the computing device 700 is depicted as a single device, in one example, multiple computing devices work together and share the depicted device resources. For instance, in one example, the memory702 is distributed across multiple devices, the processor(s) 704 provided are housed on different devices, and so on.
[0076] In one example, the memory 702 includes any of the computer-readable media discussed herein. In one example, the memory 702 is used to store and access instructions 702a configured to carry out the various operations disclosed herein. In some examples, the memory 702 includes computer storage media in the form of volatile and / or nonvolatile memory, removable or non-removable memory, data disks in virtual environments, or a combination thereof. In one example, the processor(s) 704 includes any quantity of processing units that read data from various entities, such as the memory 702 or input / output (I / O) components 710. Specifically, the processor(s) 704 are programmed to execute computer-executable instructions for implementing aspects of the disclosure. In one example, the instructions 702a are performed by the processor 704, by multiple processors within the computing device 700, or by a processor external to the computing device 700. In some examples, the processor(s) 704 are programmed to execute instructions such as those illustrated in the flow charts discussed herein and depicted in the accompanying drawings.
[0077] In other implementations, the computing device 700 may include additional features and / or functionality. For example, the computing device 700 may also include additional storage (e.g., removable and / or non-removable) including, but not limited to, magnetic storage, optical storage, and the like. Such additional storage is illustrated in FIGURE 24 by the memory 702. In one implementation, computer readable instructions to implement one or more implementations provided herein may be in the memory 702 as described herein. The memory 702 may also store other computer readable instructions to implement an operating system, an application program and the like. Computer readable instructions may be loaded in the memory 702 for execution by the processor(s) 704, for example.
[0078] The presentation component(s) 706 present data indications to an operator or to another device. In one example, the presentation components 706 include a display device, speaker, printing component, vibrating component, etc. One skilled in the art will understand and appreciate that computer data is presented in a number of ways, such as visually in a graphical user interface (GUI), audibly through speakers, wirelessly between the computing device 700, across a wired connection, or in other ways. In one example, the presentation component(s) 706 are notused when processes and operations are sufficiently automated that a need for human interaction is lessened or not needed. I / O ports 708 allow the computing device 700 to be logically coupled to other devices including the I / O components 710, some of which is built in. Implementations of the I / O components 710 include, for example but without limitation, a microphone, keyboard, mouse, joystick, pen, game pad, satellite dish, scanner, printer, wireless device, camera, etc.
[0079] The computing device 700 includes a bus 716 that directly or indirectly couples the following devices: the memory 702, the one or more processors 704, the one or more presentation components 706, the input / output (I / O) ports 708, the I / O components 710, a power supply 2512, and a network component 714. The computing device 700 should not be interpreted as having any dependency or requirement related to any single component or combination of components illustrated therein. The bus 716 represents one or more busses (such as an address bus, data bus, or a combination thereof). Although the various blocks of FIGURE 24 are shown with lines for the sake of clarity, some implementations blur functionality over various different components described herein.
[0080] The components of the computing device 700 may be connected by various interconnects. Such interconnects may include a Peripheral Component Interconnect (PCI), such as PCI Express, a Universal Serial Bus (USB), firewire (IEEE 1394), an optical bus structure, and the like. In another implementation, components of the computing device 700 may be interconnected by a network. For example, the memory 702 may be comprised of multiple physical memory units located in different physical locations interconnected by a network.
[0081] In some examples, the computing device 700 is communicatively coupled to a network 718 using the network component 714. In some examples, the network component 714 includes a network interface card and / or computer-executable instructions (e.g., a driver) for operating the network interface card. In one example, communication between the computing device 700 and other devices occurs using any protocol or mechanism over a wired or wireless connection 720. In some examples, the network component 714 is operable to communicate data over public, private, or hybrid (public and private) connections using a transfer protocol, between devices wirelessly using short range communication technologies (e.g., near-field communication (NFC), Bluetooth® branded communications, or the like), or a combination thereof.
[0082] The connection 720 may include, but is not limited to, a modem, a Network Interface Card (NIC), an integrated network interface, a radio frequency transmitter / receiver, an infrared port, a USB connection or other interfaces for connecting the computing device 2500 to other computing devices. The connection 720 may transmit and / or receive communication media.
[0083] Although described in connection with the computing device 700, examples of the disclosure are capable of implementation with numerous other general-purpose or special-purpose computing system environments, configurations, or devices. Implementations of well-known computing systems, environments, and / or configurations that are suitable for use with aspects of the disclosure include, but are not limited to, smart phones, mobile tablets, mobile computing devices, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, gaming consoles, microprocessor-based systems, set top boxes, programmable consumer electronics, mobile telephones, mobile computing and / or communication devices in wearable or accessory form factors (e.g., watches, glasses, headsets, or earphones), network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, VR devices, holographic device, and the like. Such systems or devices accept input from the user in any way, including from input devices such as a keyboard or pointing device, via gesture input, proximity input (such as by hovering), and / or via voice input.
[0084] Implementations of the disclosure are described in the general context of computer- executable instructions, such as program modules, executed by one or more computers or other devices in software, firmware, hardware, or a combination thereof. In one example, the computer- executable instructions are organized into one or more computer-executable components or modules. Generally, program modules include, but are not limited to, routines, programs, objects, components, and data structures that perform particular tasks or implement particular abstract data types. In one example, aspects of the disclosure are implemented with any number and organization of such components or modules. For example, aspects of the disclosure are not limited to the specific computer-executable instructions or the specific components or modules illustrated in the figures and described herein. Other examples of the disclosure include different computer-executable instructions or components having more or less functionality than illustrated and described herein. In implementations involving a general-purpose computer, aspects of the disclosure transform the general-purpose computer into a special-purpose computing device when configured to execute the instructions described herein.
[0085] By way of example and not limitation, computer readable media comprises computer storage media and communication media. Computer storage media include volatile and nonvolatile, removable, and non-removable memory implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or the like. Computer storage media are tangible and mutually exclusive to communication media. Computer storage media are implemented in hardware and exclude carrier waves and propagated signals. Computer storage media for purposes of this disclosure are not signals per se. In one example, computer storage media include hard disks, flash drives, solid- state memory, phase change random-access memory (PRAM), static random-access memory (SRAM), dynamic random-access memory (DRAM), other types of random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD- ROM), digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium used to store information for access by a computing device. In contrast, communication media typically embody computer readable instructions, data structures, program modules, or the like in a modulated data signal such as a carrier wave or other transport mechanism and include any information delivery media.
[0086] While various spatial and directional terms, including but not limited to top, bottom, lower, mid, lateral, horizontal, vertical, front and the like are used to describe the present disclosure, it is understood that such terms are merely used with respect to the orientations shown in the drawings. The orientations can be inverted, rotated, or otherwise changed, such that an upper portion is a lower portion, and vice versa, horizontal becomes vertical, and the like.
[0087] The word “exemplary” is used herein to mean serving as an example, instance or illustration. Any aspect or design described herein as “exemplary” is not necessarily to be construed as advantageous over other aspects or designs. Rather, use of the word exemplary is intended to present concepts in a concrete fashion. As used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. Further, at least one of Aand B and / or the like generally means A or B or both A and B. In addition, the articles “a” and “an” as used in this application and the appended claims may generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form.
[0088] Although the subject matter has been described in language specific to structural features and / or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims. Of course, those skilled in the art will recognize many modifications may be made to this configuration without departing from the scope or spirit of the claimed subject matter.
[0089] As used herein, a structure, limitation, or element that is “configured to” perform a task or operation is particularly structurally formed, constructed, or adapted in a manner corresponding to the task or operation. For purposes of clarity and the avoidance of doubt, an object that is merely capable of being modified to perform the task or operation is not “configured to” perform the task or operation as used herein.
[0090] Various operations of implementations are provided herein. In one implementation, one or more of the operations described may constitute computer readable instructions stored on one or more computer readable media, which if executed by a computing device, will cause the computing device to perform the operations described. The order in which some or all of the operations are described should not be construed as to imply that these operations are necessarily order dependent. Alternative ordering will be appreciated by one skilled in the art having the benefit of this description. Further, it will be understood that not all operations are necessarily present in each implementation provided herein.
[0091] Any range or value given herein can be extended or altered without losing the effect sought, as will be apparent to the skilled person.
[0092] Also, although the disclosure has been shown and described with respect to one or more implementations, equivalent alterations and modifications will occur to others skilled in the art based upon a reading and understanding of this specification and the annexed drawings. The disclosure includes all such modifications and alterations and is limited only by the scope of the following claims. In particular regard to the various functions performed by the above described components (e.g., elements, resources, etc.), the terms used to describe such components areintended to correspond, unless otherwise indicated, to any component which performs the specified function of the described component (e.g., that is functionally equivalent), even though not structurally equivalent to the disclosed structure which performs the function in the herein illustrated exemplary implementations of the disclosure.
[0093] As used in this application, the terms “component,” “module,” “system,” “interface,” and the like are generally intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program and / or a computer. By way of illustration, both an application running on a controller and the controller can be a component. One or more components may reside within a process and / or thread of execution and a component may be localized on one computer and / or distributed between two or more computers.
[0094] Furthermore, the claimed subject matter may be implemented as a method, apparatus or article of manufacture using standard programming and / or engineering techniques to produce software, firmware, hardware or any combination thereof to control a computer to implement the disclosed subject matter. The term “article of manufacture” as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier or media. Of course, those skilled in the art will recognize many modifications may be made to this configuration without departing from the scope or spirit of the claimed subject matter.
[0095] In addition, while a particular feature of the disclosure may have been disclosed with respect to only one of several implementations, such feature may be combined with one or more other features of the other implementations as may be desired and advantageous for any given or particular application. Furthermore, to the extent that the terms “includes,” “having,” “has,” “with,” or variants thereof are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising.”
[0096] The implementations have been described, hereinabove. It will be apparent to those skilled in the art that the above methods and apparatuses may incorporate changes and modifications without departing from the general scope of this invention. It is intended to include all such modifications and alterations in so far as they come within the scope of the appended claims or the equivalents thereof.
Claims
What is claimed is:
1. A sourcing system, comprising: a processor; and a computer-readable medium storing non-transitory instructions that are operative upon execution by the processor to: receive inputs via a user interface of a marketplace sourcing platform, the inputs received from one or more consumers and one or more vendors, the inputs comprising at least one UNSPSC identifier; define elements of at least one of an RFP, an RFQ, or an RFI using the marketplace sourcing platform, the elements based at least in part on the received inputs; validate the one or more elements of the RFP, the RFQ, or the RFI; generate one or more bids using the validated one or more elements; receive via the marketplace sourcing platform, one or more responses relating to the one or more bids; output a final bid based in part on the received one or more responses; and process payment for at least a portion of the final bid based using the marketplace sourcing platform.
2. The sourcing system of claim 1, wherein the non-transitory instructions are further operative upon execution by the processor to access payment information from an escrow system, and perform one of a payment operation or a refund operation.
3. The sourcing system of claim 1, wherein the non-transitory instructions are further operative upon execution by the processor to receive registration information to generate a membership to the marketplace sourcing platform.
4. The sourcing system of claim 3, wherein inputs are only received from one or more consumers and one or more vendors that have the membership.
5. The sourcing system of claim 1, wherein the non-transitory instructions are further operative upon execution by the processor to perform a bidding process within the marketplace sourcing platform.
6. The sourcing system of claim 1, wherein the non-transitory instructions are further operative upon execution by the processor to perform a contracting process within the marketplace sourcing platform.
7. The sourcing system of claim 1, wherein the non-transitory instructions are further operative upon execution by the processor to perform a payment process within the marketplace sourcing platform.
8. The sourcing system of claim 1, wherein the non-transitory instructions are further operative upon execution by the processor to transfer a payment of a bid lock fee prior to outputting the final bid.
9. The sourcing system of claim 1, wherein the non-transitory instructions are further operative upon execution by the processor to generate and display user interfaces comprising a consumer dashboard and a vendor dashboard, and perform a search for a requested product or service for the RFP, the RFQ, or the RFI using the UNSPSC identifier and one or more inputs received via the consumer dashboard and the vendor dashboard.
10. A computer-implemented method for sourcing goods and / or services, the computerized method comprising: receiving inputs via a user interface of a marketplace sourcing platform, the inputs received from one or more consumers and one or more vendors, the inputs comprising at least one UNSPSC identifier; defining elements of at least one of an RFP, an RFQ, or an RFI using the marketplace sourcing platform, the elements based at least in part on the received inputs; validating the one or more elements of the RFP, the RFQ, or the RFI; generating one or more bids using the validated one or more elements;receiving via the marketplace sourcing platform, one or more responses relating to the one or more bids; outputting a final bid based in part on the received one or more responses; and processing payment for at least a portion of the final bid based using the marketplace sourcing platform.
11. The computer implemented method of claim 10, further comprising accessing payment information from an escrow system, and performing one of a payment operation or a refund operation.
12. The computer implemented method of claim 10, further comprising receiving registration information to generate a membership to the marketplace sourcing platform.
13. The computer implemented method of claim 12, wherein inputs are only received from one or more consumers and one or more vendors that have the membership.
14. The computer implemented method of claim 10, further comprising performing a bidding process within the marketplace sourcing platform.
15. The computer implemented method of claim 10, further comprising performing a contracting process within the marketplace sourcing platform.
16. The computer implemented method of claim 10, further comprising performing a payment process within the marketplace sourcing platform.
17. The computer implemented method of claim 10, further comprising transferring payment of a bid lock fee prior to outputting the final bid.
18. The computer implemented method of claim 10, further comprising generating and displaying user interfaces comprising a consumer dashboard and a vendor dashboard, and performing a search for a requested product or service for the RFP, the RFQ, or the RFI using the UNSPSC identifier and one or more inputs received via the consumer dashboard and the vendor dashboard.
19. A computer readable storage media having computer-executable instructions for sourcing goods and / or services that, upon execution by a processor, cause the processor to at least: receive inputs via a user interface of a marketplace sourcing platform, the inputs received from one or more consumers and one or more vendors, the inputs comprising at least one UNSPSC identifier; define elements of at least one of an RFP, an RFQ, or an RFI using the marketplace sourcing platform, the elements based at least in part on the received inputs; validate the one or more elements of the RFP, the RFQ, or the RFI; generate one or more bids using the validated one or more elements; receive via the marketplace sourcing platform, one or more responses relating to the one or more bids; output a final bid based in part on the received one or more responses; and process payment for at least a portion of the final bid based using the marketplace sourcing platform.
20. The computer readable storage medium of claim 19, wherein the computer- executable instructions, upon execution by the processor, further cause the processor to at least generate and display user interfaces comprising a consumer dashboard and a vendor dashboard, and perform a search for a requested product or service for the RFP, the RFQ, or the RFI using the UNSPSC identifier and one or more inputs received via the consumer dashboard and the vendor dashboard.