Skip to main content

RFP Submission Step 2: Add Inventory

The grid where you enter units for an RFP: required columns, how pricing and proration work, and what gets validated when you save.

Written by Zachary Cuva

The Add Inventory stage is the second step in the RFP submission workflow.

In this step, vendors enter the initial information for the units they plan to submit for an RFP.


Purpose

Use the Add Inventory grid to:

  • Input unit details for RFP consideration.

  • Add new or existing inventory.

  • Submit individual units or packages for review.


Standard Grid Columns


The following columns appear in the Add Inventory grid:

Column

Description

Face ID

Unique identifier for each unit. Used to recall saved unit data during the next step, Unit Details. Start typing to search your existing inventory.

Geopath ID

Optional. Appears on domestic requests only.

Start Date

Start date for the campaign flight.

End Date

End date for the campaign flight.

4 Week Price

Required field for pricing. On some requests this is replaced by Price for Duration — see Pricing below.

Latitude and Longitude

Only appear if your account has more than one unit sharing a Face ID. See Duplicate Face IDs below.


Pricing

4 Week Price is the standard price column. Enter your four-week rate. Proration is handled for you, and the prorated figure appears in the next step as a read-only Calculated Price Duration column.

On some requests this column is replaced by Price for Duration. That can happen when the request is international, or when it has been flagged as a short-flight campaign. If you see this column, enter the price for the actual flight length rather than your four-week rate — the four-week figure then becomes the read-only calculated column.

*Note: Most AdQuick RFPs are issued in four-week increments and will show 4 Week Price. If the column reads Price for Duration, you'll also see a banner above the grid confirming it.


What The Grid Checks When You Save

Validation runs when you click Save and Continue, not as you type. On every row:

  • Face ID, Start Date and End Date are required.

  • Price is required and must be greater than 100.

  • Start Date must be later than today. If the flight has already started, contact the Account Manager rather than back-dating the row.

  • End Date must be after Start Date.

An empty grid cannot be saved.


Duplicate Face IDs

If your account has more than one unit sharing the same Face ID, Latitude and Longitude columns appear so the units can be told apart, and coordinates become required on the affected rows.


Adding New Units

New units that have not been previously submitted can be created directly within the Add Inventory grid.


Handling Errors


When you save, anything that needs attention appears in a panel on the right-hand side of the page.

  • The panel counts what it found: "N Validation Errors Found" and, separately, "N Warnings Found".

  • Each entry is clickable. Selecting one moves the grid to the row and column that needs attention.

  • Errors prevent you from continuing. Correct them and save again — the panel clears as they are resolved.

  • Warnings do not prevent you from continuing. They flag values that look unusual so you can double-check them before submitting, such as impressions below 999 or an installation cost above 999,999. If the value is correct, carry on.


Submitting Packages Or Transit Units


To submit a package of units instead of individual ones, click Packages in the top bar. The button is available on both this step and Unit Details.

In the Packages panel you can:

  • Click Create Package to build a new one, or

  • Click Add From Template to start from a package you have saved before.

Once created, the package appears as a row in this grid with an auto-generated Package Face ID, and as a card in the Packages panel where you can view, edit or delete it.


Proceeding To The Next Step

When all required inventory data has been added:

  1. Click Save and Continue in the top-right corner of the page.

  2. Proceed to Step 3: Unit Details.

Did this answer your question?