A brief title that describes what is included in the event. The title is included in emails to suppliers and helps them to get a general idea about the event. This will be prominently displayed to buyers and suppliers.
Data type: Text
Example: Cleaning Services for Wisconsin Area
| | | Buyer | buyer\_email |Buyer's email. Fairmarkit does not validate the email. This value is used to assign the event in Fairmarkit and must be an existing account in Fairmarkit.
Data type: Email
Example:
Request for proposal ID from your purchasing application
Data type: Text
Example: ID123
| | | Event description | event\_description |A detailed description to explain why you are running an event for this project. This description acts as a cover letter, introducing suppliers to your event. Can contain up to 50,000 characters.
Data type: Long Text
Example: MyCompany is requesting proposals for fish tank cleaning services at our offices across the United States.
| | | Closes at | closes\_at |Date and time when all responses are due for the event. This value can be set via logic (create+7 days). This value must be after the Scheduled Publish Date and before the Close Date.
Data type: Date + Time
Example: 2/23/2023 0:00:00
| | | Scheduled publish at | scheduled\_publish\_at |Date and time to open the event. Events can be manually opened or scheduled to be opened. This value must be after the current date and before the Close Date and Questions Date.
Data type: Date + Time
Example: 1/23/2023 0:00:00
| | | Questions due at | questions\_due\_at |Date and time when responses to questions are due. This value must be after the Scheduled Publish Date and before the Close Date.
Data type: Date + Time
Example: 1/30/2023 0:00:00
| | | Department | department |The name of the department or business unit that requested the event.
Data type: Text
Example: Facilities
| | | Business unit | business\_unit |The business unit that requested or is related to the event. This is an optional field that may not be configured for your organization.
Data type: Text
Example: MyCompany-US
| | | Project name | project\_name |The name of the project associated with the event.
Data type: Text
Example: Project Aquarium
| | | Shipping Type | shipping\_type |Your preferred shipping method.
Data type: Drop-Down
Accepted values: Fairmarkit defined values; see Shipping type and Carrier.
| | | Carrier | carrier |Your preferred shipping carrier. The available carriers depend on the selected Shipping Type.
Data type: Drop-Down
Accepted values: Fairmarkit defined values; see Shipping type and Carrier.
| | | Justification | justification |A note describing the justification for the event. This field is not visible to suppliers.
Data type: Text
Example: Contract expiring
| | | Is RFI | is\_rfi |Set if this is a request for information event.
Default: No
Data type: True / False
Example: No
Accepted values: Yes or No
| | | Estimated Value | value |The projected value of the event.
Data type: Number
Example: 10000000
| | | Projected Savings | savings |The projected savings for the event.
Data type: Number
Example: 500000
| | | Currency | currency |Event currency when awarding. This should be the three letter currency code.
Default: USD
Data type: Three letter currency code
Example: EUR
| | | Notes to suppliers | notes |Add additional information and communication about the event with all invited suppliers. This correlates to the Notes to Suppliers in the Fairmarkit user interface.
Data type: Text
Example: Proposals must be received on or before 2:00 p.m. on Monday, January 30, 2023 MyCompany reserves the right to accept or reject any or all proposals and to waive any irregularities. We do not accept late or misdirected proposals. Persons submitting a response to this RFP must comply with all applicable laws, ordinances and regulations including the provisions of the State of Texas Government Code Chapter 176. Failure to follow the procedures of this RFP will result in immediate disqualification from consideration. All inquiries for information regarding this solicitation should be directed in writing to:
Client company. This is an optional field that may not be configured for your organization. When enabled, you'll have a custom list of options.
Data type: Text
Example: Cameron's Consulting Agency
| | | Erp system | erp\_system |Your purchasing application. When entered, it will override the system level settings.
Data type: Text
Example: Compass
| | | Section Title | question\_title |Section title. You can add up to 3000 questions (lines) to an event and 100 questions per section.
Data type: Text
Example: Company Information
| | | Section Description | question\_description |Section description.
Data type: Text
Example: Company Information
| | | Benchmark Price Per Unit | benchmark\_price\_per\_unit |Benchmark price per unit. This is internal to your company. Presumably in your currency and UOM for the item.
Data type: Text
Example: 10.00
| | | Benchmark Supplier ID | benchmark\_supplier\_id |Benchmark supplier ID.
Data type: Text
Example: S1002
| | | Benchmark Supplier Title | benchmark\_supplier\_title |Benchmark supplier name. This can be a name, title, entity, or description.
Data type: Text
Example: Charlie's Convenience Store
| | | Manufacturer | manufacturer |Manufacturer of the line item.
Data type: Text
Example: Local Co
| | | Manufacturer Part Number | manufacturer\_part\_number |Manufacturer part number of the line item.
Data type: Text
Example: 900
| | | Internal Part Number | internal\_part\_number |Your organization's part number for the item. This value is entered at your discretion.
Data type: Text
Example: IPN100
| | | Quantity | quantity |Item quantity. This is assumed to be an integer.
Data type: Text
Example: 1
| | | UNSPSC | unspsc |Standard 8 digit UNSPSC code for the item or requested service.
Data type: Text
Example: 50201706
| | | Line number | line\_number |Line number or order of the line item.
Data type: Text
Example: 1
| | | Item Kind | item\_kind |Line item type. For more information, see Create a request for proposal.
Default: Item
Data type: Text
Example: Item
Accepted values : item/service/group
| | | Item Description | item\_description |Item name.
Data type: Text
Example: coffee beans
| | | UOM | uom |Unit of measure of the item.
Default: Each
Data type: Text
Example: Each
Accepted values: Fairmarkit defined values; For more information, see Available UOMs.
Note: Custom mapping is available. For more information, contact your technical architect.
| | | Is required | is\_required |Set if suppliers are required to respond to the line item.
Default: No
Data type: True / False
Example: No
Accepted values: Yes or No
| --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.fairmarkit.com/buyers/integrations/flat-file-integration/import-data/import-requests-for-proposal-rfp-or-information-rfi.md?ask=