Pricing Period
A pricing period: a code, its dates and its price category. Every pricing profile belongs to one.
What it is for
A Pricing Profile names a pricing period, and every line of the profile must fall inside the period's dates. The period's Price Category also narrows which price models the profile may use.
Date From and Date To are fixed once the period is created; Date From may not be later than Date To. Clone is allowed, so next year's period can start from this one.
Every field in plain words
| Field | What it means | What to put |
|---|---|---|
| Pricing Period | The short code. | For example PP2026. Cannot be changed once saved. Required |
| Name | The name shown in lookups and on documents. | A clear name |
| Price Category | The price category. The profile's Price Model list is narrowed to it. | Pick one |
| Date From | First day of the period. | A date, fixed after creation. Required |
| Date To | Last day of the period. | A date, fixed after creation |
| Controller | The employee who controls this period. | Pick an employee |
| Notes | Free notes on the record. | Any text |
How to configure it
There is nothing to configure beyond the fields above. Which fields are shown, required or hidden can be changed per company by the consultant in the screen configuration.
Scenarios
- A distributor revises prices every January. Make a period per year and write the year's pricing profiles against it.
What it is connected to
- Pricing Profile - written against a period
If something looks wrong
- "Pricing Period - Date From ... cannot be greater than Date To ..." Fix the dates.
- "Same Pricing Period ... already exists." Use another code.
- "Line ID: ... - Dates out of Pricing Period range" on a pricing profile. The line dates fall outside this period.