Each product holds the amount its monthly price rises by in each year after it is quoted, per unit, in pounds and pence. You can set them one product at a time or for many products with the price book.
This needs the Contracted Price Increases add-on and the settings described in Contracted Price Increases: overview and setup.
One product at a time
Go to Settings and open the product.
Select the Price Increases tab.
Enter the amount for Year 1. Click Add a year for each further year, up to ten.
Click Save price increases.
The tab shows the date increases apply and whether the last amount repeats, so you can see how the amounts will be used.
Each amount must be more than zero, with no more than two decimal places. To make a product fixed price again, click Remove the last year until no years are left, then save.
Example
A product has Year 1 £3.25 and Year 2 £5.00, increases apply on 6 April, and the last increase repeats. A line quoted at £56.50 a month in October 2026 on a 36 month term shows:
Increases to £59.75 on 6 April 2027
Increases to £64.75 on 6 April 2028
Increases to £69.75 on 6 April 2029
For a quantity of 2, the prices shown are for the whole line, so each is doubled.
With the price book
Go to Settings, Inventory and export the category as usual. The file now ends with the columns Price Increase 1 to Price Increase 10, filled in for products that have increases.
Edit the amounts, following the rules below.
Import the file as usual. The increases are read once the import has finished.
What the cells mean
An amount in Price Increase 1, 2 and so on sets that year's increase. Fill the years in order with no gaps.
Every Price Increase cell empty leaves the product's increases as they are.
A 0 in Price Increase 1, with the other cells empty, removes the product's increases so it becomes fixed price.
How products are found
Keep the column headings exactly as exported. Each row is matched to a product by its Existing Product Guid. A row for a new product, which has no guid yet, is matched to the product the same import created by its Internal SKU or, failing that, its Product Name.
Rows that cannot be read
A row is skipped when, for example, Price Increase 3 has a value but Price Increase 2 is empty, an amount is not a number, is negative or has more than two decimal places, a 0 appears after Price Increase 1, or the product cannot be found. The rest of the import carries on.
The audit trail records how many products were set, how many were made fixed price and how many rows were skipped, with the row number and reason for the first five skipped rows. If the file itself cannot be read, that is recorded in the audit trail too. Correct the rows and import the file again, or set those products on their Price Increases tab. Layer Support can see the reason for every skipped row.
Good to know
Amounts are per unit, a month.
Changing a product's increases does not change quotations that have already been generated. Regenerate a draft quotation to pick up the change.
Each change made on a product's Price Increases tab is recorded in the audit trail.