Dynamic Attributes is the correct feature. It allows business users in the Backoffice to define and manage custom product attributes directly through the UI, without requiring code changes or a system restart. This provides the agility and self-service capability the client needs.

The Unit concept (specifically, B2BUnit) is designed for this. It allows you to model an organization’s hierarchy (e.g., parent company, divisions, branches). You can assign users, budgets, and shipping addresses to different units, enabling centralized ordering with decentralized fulfillment, which is a classic B2B requirement.

The most likely cause is that the search index does not include up-to-date stock or product status information. The correct first step is to investigate the indexing configuration (e.g., in the impex files or Solr configuration) to ensure the relevant fields (like stock level and product approval status) are being indexed and that the index is being updated properly upon catalog changes.

In SAP Commerce Cloud, creating a Promotion (with conditions and actions) is only one part. For it to be executed, it must be part of a Promotion Rule, which is then added to a Rule-Based Promotion Engine (RBPE) campaign. The most common oversight is creating the promotion components but failing to assemble them into a rule and campaign, which is the operational container.

Text labels in SAP Commerce Cloud are typically externalized into property files (e.g., .properties files). This is a best practice for internationalization (i18n) and maintainability. Changing the value for the key (like “basket.add.to.cart”) in the appropriate extension’s property file will update the text everywhere it is referenced, without touching code.

The core commerce logic, including the checkout process, cart management, order calculation (taxes, promotions, shipping), and persistence, is handled by the SAP Commerce Core (the Platform) running on the JVM. Solr is for search, Cockpit is a management UI, and the frontend primarily handles presentation and user interaction, delegating business logic to the core.

Impex (Import/Export) is the standard, powerful tool for bulk data manipulation in SAP Commerce. It can be automated by placing the Impex script and data file in a hot folder and using a cron job (or a scheduler like Quartz) to trigger the import. The `impex.legacy.script.mode` or staging mechanisms can provide the desired preview capability before live update.

A Content Slot is a fundamental CMS concept. It represents a designated area or placeholder on a page (e.g., ‘Top Banner’, ‘Left Sidebar’, ‘Footer’). Content editors can then add, remove, and arrange CMS Components (like banners, link lists, product carousels) into these slots via the CMS Cockpit, providing flexible page composition without coding.

SAP Commerce Cloud follows a strict extension pattern to allow for customization without modifying core code. The correct approach is to create a custom extension for your project and define the new attribute for the Product type (using `atomic` or `deployment` type) in your extension’s `items.xml` file. This uses the platform’s type system to safely extend the model.

Dynamic Attributes is the correct feature. It allows business users in the Backoffice to define and manage custom product attributes directly through the UI, without requiring code changes or a system restart. This provides the agility and self-service capability the client needs.0