Several technical and organizational factors can affect how your Sales Layer account performs, especially when you are working with imports, exports, connectors, and other ongoing processes. Good performance is not only about speed. It also depends on how your catalog is structured, how complex your setup is, and how your team plans everyday work in the platform.

What affects performance

The main factors that can affect performance in Sales Layer are the number of references, the number of fields, the number of languages and multi-language fields, the number of Attribute Sets created, the number of categories linked to each product, the formulas used in imports and exports, the number of active processes, how often those processes run, and the generation of backup copies.

Performance is not only about catalog size

A larger catalog does not always mean lower performance. For example, an account with 500,000 simple references and a light structure can perform better than an account with 50,000 references that includes many fields, many languages, multiple Attribute Sets, and products linked to many categories. What matters is the overall complexity of the account, not only the number of items it contains.

Structure complexity

As your project grows, complexity can increase very quickly. Creating more Attribute Sets than you really need, adding multi-language fields before they are required, or linking products to too many categories can all make the account harder to manage and can affect performance.

The same applies to formulas in connectors. A single formula may have little impact, but repeating many formulas across thousands of references can create a heavier process overall.

Scheduling

Scheduling also matters. Heavy tasks such as import connector runs or backup generation are better planned for quieter moments, when fewer users are actively working in the account. This helps reduce overlap between processes and can make the platform easier to use during the day.

Running a connector import and a manual import at the same time can slow the platform down.

Project planning

Performance is not only technical. It also depends on how the account is managed. A well-organized project usually performs better over time because decisions about structure, ownership, and processes are clearer from the start.

Assigning Ownership

It is useful to define a PIM manager or project owner who can coordinate with the Sales Layer team or with the partner managing the account. This person can help make decisions about user permissions, account setup, and ongoing maintenance. Clear ownership helps avoid unnecessary complexity and makes it easier to keep the platform organized as the project grows.

Specialists

If your team is working on a complex ecommerce setup or advanced integrations, involving an experienced partner can help reduce mistakes, rework, and avoidable configuration issues. This is especially useful when project requirements are complex or when different systems need to work together smoothly.

Backups

Backups are important, but they are also part of the performance picture. Depending on how complex the account is, a backup can take longer and may affect users working in the platform at the same time. For that reason, backups are best planned for low-activity periods.

It is also important to understand how restoring a backup may affect work completed after that restore point.

Supporting efficiency with Quality Report

The Quality Report can also help improve the overall efficiency of your project. It allows teams to identify missing information, focus on incomplete fields, and correct them more easily from Excel mode. Keeping product data cleaner and more complete makes it easier to manage exports, validations, and publishing workflows.

Common Use Cases

This article is most useful when you are planning a new Sales Layer setup, reviewing why an account feels slower than expected, preparing a large import or export process, reorganizing your Attribute Sets and categories, or deciding how to schedule connector activity and backups more efficiently.

This combined approach is also helpful when you want to align technical configuration with day-to-day project management.

Best practices

Keep your structure as lean as possible, avoid creating fields or Attribute Sets before they are truly needed, review connector formulas regularly, and plan imports and backups for quieter times. It also helps to assign clear ownership inside the project and use the Quality Report as part of regular catalog maintenance.

If you are unsure how a certain setup may affect performance, check the Support Center or review it with your Sales Layer contact or implementation partner.