Limits
Ecommerce Search sets some limits that should help ensure good overall performance. However, if the system is used in such a way that too many of the limits are reached at the same time, it is recommended that the system be re-evaluated and performance load tested to ensure good performance.
Note that Rate Limiting may be triggered if the load is significantly above your agreement.
Search
| Name | Limit / Recommendation |
|---|---|
No of products |
Max 1000. A request size of around 40 will give good performance if the number of fields to be returned is low. Good performance can be achieved with a larger number of products, but requires more intensive load testing. |
SKUs per product |
Max 1000. This is due to the underlying top performing SKUs will be fetched per product. |
No of products * SKUs per product |
Max 1000. This makes it possible to balance the amount of SKUs and products to be returned while still beign able to achieve good performance. |
Product offset |
Max 10.000 - (No. of products*SKUs per product). Due to this limitation, the Search endpoint cannot be used to export all products. Use the Export endpoint to ensure good performance. |
Export
The number of products/SKUs that can be exported per request depends on the amount of data to be returned. However, no more than 1.000 SKUs are allowed per export request.
Ingestion
| Name | Limit / Recommendation |
|---|---|
StringAttributes |
String attribute values cannot exceed 32.766 bytes. It is highly recommended to use much fewer bytes to ensure good performance. Keys cannot exceed a length of 64 characters. |
NumberAttributes |
Keys cannot exceed a length of 64 characters. |
IntervalAttribute |
Keys cannot exceed a length of 64 characters. |
Metadata |
Metadata cannot exceed 32.766 bytes. It is highly recommended to use much fewer bytes to ensure good performance. Keys cannot exceed a length of 64 characters. |
PriceGroups |
Price groups are limited to 2.500 price groups per segment. |
Parameters |
Max 65.535 parameters globally. However 5-25 parameters should be more than enough for the majority. |
Partitions |
Max 1.000 partitions per parameter. |
CommercialParameters |
The total global amount of commercial parameters should be taken into account, as each value requires processing. Keys cannot exceed a length of 64 characters. |
Affinities
| Name | Limit / Recommendation |
|---|---|
| Affinity Sources | Up to 16 in total. |
| Product Affinities | Should be less than 100 per product, more than this could indicate a misuse. Keys cannot exceed a length of 64 characters. |
| User Affinities | Should be less than 100 per user, more than this could indicate a misuse. Keys cannot exceed a length of 64 characters. |
| User Affinity Profiles | Up to 1.000.000 profiles per segment provides good performance. |
Other API Limits
More fine-grained limits are defined in the OpenAPI specification, and using Swagger or the API Swagger reference allows you to see these limits. The limits can be found in the schema section by expanding a model and a field.
