This topic describes feature-specific configuration options available for Optimizely Customized Commerce. Depending on your specific solution and how you set up and work with Customized Commerce, you can configure for example tracking execution and synchronization of versioning.
## Configuration options
The configuration settings are available in <appSettings> in the _web.config_ file. The following example is from the Episerver Commerce "Quicksilver" sample site.
Indicates if a promotion is excluded from being applied per order or per unit.
Order (default): Promotions are excluded from being applied to an order when excluded by other promotions.
Unit: Promotions can partly be prevented from being applied to one or more individual items when excluded by other promotions. Order level and shipping level promotions are still excluded in full. See also [Promotion exclusions](🔗).
If set to **true**, when the site starts, the migration steps are run automatically. Otherwise, site admins must log in to the migration view and run the steps manually.
Indicates if an update to catalog content done outside of the content APIs removes version data (for example, drafts, old published versions) for affected content. Setting this to **true** can improve the speed of batch operations done through the lower-level APIs (like ICatalogSystem), for example the catalog import.
Indicates if the Tracking system executes tracking. See also [Commerce Cloud API overview](🔗).
The URL of the Episerver Product Recommendations environment to be used. Should contain only the protocol and host name.
The site name used to identify requests to the tracking server.
The token used to authenticate tracking requests to the REST API. See also [Product Recommendations](🔗).
The token used to authenticate admin requests to the REST API.
**\[Optional\]** Timeout for REST calls. The default value is 30 seconds.
**\[Optional\]** The number of products processed in one batch when the product feed is generated. A higher value can be faster but puts more pressure on the memory. Default value is 50. See also [Customizing exported product information](🔗).
**\[Optional\]** Selects the catalog used to generate the product feed if you have multiple catalogs. If this value is not set, the first catalog is used. See also [Customizing exported product information](🔗).
This property will be removed when Product feed support for multiple catalogs is added.
For the Remove Expired Carts job, sets the number of days after the last modification before a cart is considered abandoned and removed by the job. Default value is 30 days.
For the Remove Expired Carts job, sets the cart name that is excluded from being removed by the job, even if it has not been changed for a longer time than the configured value. Default value is "WishList".
For the Maintenance Database Indices job, set the value (in seconds) before database requests are considered timeouts.
For the Maintenance Database Indices job, sets the fragmentation value (in percent) of indices. If an index's fragmentation level is below this value, it is not maintained. Default value is 10.
For the Maintenance Database Indices job, sets the value (in percent).
Indices with a fragmentation level higher than this value will be _rebuilt_.
Indices with a fragmentation level lower than this value, but higher than the value configured by episerver::LowFragmentationThreshold will be _reorganized_.
Default value is 30.
Indicates whether validation of entry uri segments should be strict or not.
Strict validation means uri segments must be globally unique (for the language) to make sure all hierarchical routes to entries will work despite any crosslinking that happens after the uri segment has been saved.
Less strict validation means that the uri segment is still validated for uniqueness against sibling items, but since this happens at the time of saving, crosslinking items can create conflicts in hierarchical routes.
Default value is **false** (that is, use strict validation). See also [URL segment and SEO URL](🔗) and [Increased Flexibility in Commerce Catalog URLs](🔗).
Recipients that will get an email if any URI conflicts are found by the Find Catalog Uri Conflicts scheduled job. To specify multiple recipients, separate email addresses by a semicolon (;). See also [URL segment and SEO URL](🔗) and [Increased Flexibility in Commerce Catalog URLs](🔗).
## Feature switch
The Features configuration options are set in the _Configs/ecf.app.config_ file.
The Features configuration options control the following features.