Imports Using Multiple Price Levels and Quantities Example

If both Multiple Prices and Quantity Pricing are enabled, the sublist area of the item record form includes a row for each price level, and a column for each quantity. You can view this form at Lists > Accounting > Items > New > Inventory Item (or any item type that uses pricing), and looking at the Sales / Pricing subtab.

Whenever you try to save a record of this type, the system enforces the following rule: A price level row that contains any values must include values for all defined quantity columns (all columns that have a number in the Qty field). Similarly, if a quantity column contains any values, it must include values for all price level rows that contain any other values.

For example, the following data could not be saved because two prices are missing in one row.

Similarly, the following data could not be saved because two prices are missing in one column.

By contrast, the following record has fully populated pricing data and could be saved. Note that it is acceptable for the Alternate Price 3 row to be empty. A row can be empty, but if it contains any data, it must be fully populated.

This rule also applies to your CSV import. If the Import Assistant cannot create fully populated pricing rows and columns as shown in the third of the preceding screenshots, an error like the following occurs: “Please enter missing price(s).” If you see this error and you believe that all required prices exist in your CSV file, the problem is likely that the file or the mapping were not set up correctly.

The “enter missing price(s)” error can occur in the following situations:

• During an import with update data handling that does either of the following:

  • Adds a new quantity threshold for an item

  • Adds a price to a previously unused pricing level

• During an import that creates a new item that uses multiple quantities and price levels

To avoid problems, make sure that your CSV data is formatted and mapped correctly. Two approaches are supported — multiple-file and single-file. For the purposes of the following examples, assume you are trying to create the pricing data pictured in the preceding figure.

Multiple Files Import

If you are using multiple CSV files, you should include one file for the body data and a second file for the pricing data.

The primary file should include required body fields such as the item's name and the tax schedule, plus any account data you want to include, as shown here:

The secondary file containing pricing data must repeat one row for each required quantity/price-level/price combination. Further, each of these rows must include a unique identifier for the item record, such as the repeating ExternalId values shown here:

When you do your mapping, you match the price columns to a single instance of the Item Pricing sublist fields.

Single File Import

If you are using a single CSV file for item body data and pricing data, all pricing fields for each item must be included in a single row. Each of the pricing groups should be represented by quantity, price level, price, and currency columns (unless you prefer to create a default value for some of these, such as currency, on the mapping page). The following example illustrates the first several columns for an item that includes nine pricing groups. Note that the columns for Item Pricing 4 through Item Pricing 9 are not pictured here.

On the Import Assistant Field Mapping page, each of these groups maps to a separate instance of the Item Pricing sublist. The following illustration shows how the first part of this mapping would look. (Not pictured are the Item Pricing instances 5 through 9.)

Considerations when Data Handling is Set to Update

When you are setting Data Handling to Update, be aware of the following:

• If you want to update a single price on an item record, you must identify both the price level and the quantity associated with that price.

• Remember that if you are doing an update that adds a new quantity to the record, you must identify a price for that quantity at every price level. Otherwise, the system generates an error about missing prices.

• If you are doing an update that adds a price for a new or previously unused price level, you must identify prices for that price level for every quantity that's already used by the item record. Otherwise, the system generates an error about missing prices.

General Notices