When should a new customer price list take effect?
Format: Article.
A new price list should start when the business has agreed it starts, not when someone uploads a file. Name the customers, items, units, and currency it covers. Set its start date and decide how to handle open quotes. Then test which list each sales tool uses. This guide tracks approved terms. It does not tell you what to charge.
Keep three facts separate: who approved the list, where the file is, and when staff may use it. A list can be approved today but start next month. A file in a shared folder can still be a draft. Staff need all three facts before they use its prices.
Create a version and effective-date worksheet
| Field | Question it must answer |
|---|---|
| List identity and revision | Which exact approved artifact is this? |
| Customer scope | Which accounts or groups qualify? |
| Item and unit scope | Which variants and selling units does it cover? |
| Currency and other conditions | Which commercial context makes the terms applicable? |
| Start and end | When does this version begin and cease to apply? |
| Time-zone rule | Which zone governs an operational cutoff, if one exists? |
| Selection event | Does the rule use quote issue, acceptance, order, or another approved date? |
| Open-quote treatment | Which existing offers remain governed by their original terms? |
| Override | Who approved an exception, for what scope, and until when? |
| Systems checked | Which quoting tools, files, and channels were tested? |
A business system may store only a date, with no time. That may not support a rule that starts at noon. Write the needed time and zone in the agreed work rules. Then test whether each tool can follow them. Adding a time to a sheet does not change how the business system works.
Microsoft's Business Central guide lists start and end dates, minimum quantities, and currency for price agreements. [S08] It describes the Sales Prices page. Check whether your setup uses that page or a newer pricing setup. The guide alone does not prove which price your current quote will choose.
Hypothetical example: a Monday list change
A fictional wholesaler approves list L-9 for new quotes sent from Monday in its agreed time zone. Older quotes that have not expired keep their own terms. This is the rule for this example company. It is not a rule for every business.
A salesperson drafts a quote on Friday but sends it on Monday. Under this rule, the send date means the new list applies. A second customer accepts a quote sent last week that has not expired. Staff check that quote's own terms and conditions. They do not replace them with L-9 just because Monday has arrived.
A third account has an approved short-term exception for one item. That does not give it a discount on everything. Write the item, unit, approver, and end date on the sheet. Another salesperson should be able to see exactly where the exception stops.
No amounts need to change to test this process. Use version labels and expected selections in a practice environment. The goal is to verify which approved terms apply, not to publish or execute a price change.
Test the boundary from both sides
Test a quote just before the start time and one at that time. Write which list should apply under the rule. Add a quote sent earlier but accepted later. Try a draft held past the start time and an expired quote that needs a new review. Check each result against the expected list.
Next, test the wrong customer group, currency, or selling unit. Try a count below the list's minimum. Then try a case where two lists seem to fit. Staff need a clear rule for which one wins, or a hold for review. The first file an assistant finds is not a rule.
Check the end date as well as the start. An old exception should not stay active in a saved quote form. Test a user in another time zone too. Their local clock should not change which list applies under the company's rule.
Preserve the reason for each selection
Save the chosen list version and the rule used with the quote. Keep the approved file so staff can check the exact terms later. If the master list changes, the old quote's proof should stay the same. A live link to a file that can change is not enough on its own.
Name who can approve price terms. Sales can flag conflicts and ask for exceptions. Warehouse staff should not guess the price just to get an order out. Hold unclear terms for review. Do not turn a guess into a customer promise.
Core Agentic builds custom AI software to fit current sales tools. A proposed view could show which lists fit and flag conflicts for the pricing owner. Test access, the price rules, and how each installed tool uses them. The design would not set prices or approve exceptions on its own.
To explore a price-version review that fits your quoting process, Book a Demo.
Sources
These sources describe the named provider or framework. They do not establish a Core Agentic integration, customer result or certification.