Limitations and Best Practices of the Effective Date Pricing SuiteApp

The following limitations and best practices apply to Effective Date Pricing:

On a single run, Effective Date Pricing can process up to:
- 10,000 customers per customer group. Additional customers are not validated and processed. After this limit is exceeded, the status may still show as In Progress, even though there are unprocessed customers.
- 1,000 items per item category. After this limit is exceeded, the status may still show as In Progress, even though there are unprocessed items.
- 4,998 Item Category Update Type price updates or Customer Group Update Type price updates whose start date is today. Additional price updates are not processed.
- 4,988 Item Category Update Type price updates or Customer Group Update Type price updates whose end date is today. Additional price updates are not processed.
For optimal performance, process no more than 10,000 items and 10,000 customers per day.
Default discounts are not taken into account. If a scheduled update changes an item's base price and that item has default discounts on other price levels, those price levels also change. Changes due to default discounts are not recorded in the Price Update logs.
Effective Date Pricing does not support:
- accounts with multiqueue
- negative prices
- reactivation of an inactive price update or price detail update
Effective Date Pricing does not work unless the following features are enabled:
- Multiple Currencies
- Pricing Level
- Multiple Prices
Item and customer price updates are applied regardless of subsidiary, class, department, and location to which you have access.
Specifying a parent item matrix updates only that parent matrix item and not its children.
The scheduled script processes only the records that start or end on the day the script runs. Any unprocessed records from previous days are not picked up and updated by the script.
There are no restrictions on:
- adding customers to customer groups
- removing customers from customer groups
- adding items to item categories
- removing items from item categories
Items removed from an item category or customers removed from a customer group after running the script are not reverted back to their original prices.
Items added to an item category or customers added to a customer group when the script is run are not validated against existing price updates. There is a possibility of an overlap, which means an item or customer can be updated multiple times in a day. Overlaps between price updates may sometimes occur even if there is a price update overlap validation. You should not add items to an item category or customers to a customer group when there are ongoing price updates.
You are not restricted from manually changing an item or customer’s price while a price update is in progress.
Customers of one customer group are not validated against customers of another customer group.
Only static customer groups are supported.
Effective Date Pricing supports two decimal places. If the original price of an item has more than two decimal places, on the reversal date, the reverted price rounds to two decimal places. For example, the item price 1.29876 is rounded to 1.30 on the reversal date.
For processing price updates, you can use only the supplied map/reduce script deployments. Do not create new map/reduce script deployments.
You should use the Price Detail Update Search saved search in map/reduce script deployments. This is the saved search provided by the Effective Date Pricing SuiteApp to make sure that the correct price update records are processed.

The Effective Date Pricing SuiteApp supports the following languages:

Chinese (Traditional)
Chinese (Simplified)
Czech
Danish
Dutch
English
Finnish
French
German
Indonesian

Italian
Japanese
Korean
Norwegian
Portuguese
Russian
Spanish
Swedish
Thai
Turkish

Related Topics