Checking the status of integrations

Integrations brings together your store's external services into one overview view. You can see which integration is in use, whether its required settings are configured, and when the settings were last changed. The view does not change the values of the settings.

Open Integrations

Open Integrations at /configuration/integrations . The current registry includes 45 integrations in 15 categories: ERP, payments, delivery, email, search, PIM, advertising, artificial intelligence, support, analytics, authentication, content, maps, communications, and more.

Integrations are presented as cards by category. The card shows the service name, category, description, usage status, configuration status, and possibly the last modification time. Integrations in a group are organized by name.

Search and narrow down integrations

In the Search integrations field, enter the service name, code, description, or category. The search will filter cards instantly without a server request.

Limit the view to one category using the category filter. All shows all groups. An empty result indicates that no integrations were found with the current search criteria; it does not mean that the registry or services have been removed.

Search and category work together. For example, if you select the Payments category and type the name of a service, only cards that meet both criteria will be displayed. Clear the search text and return the category to All to return to the entire register.

Interpret the operating mode

The Integrations card's Enabled or Disabled status indicates the calculated usage status of the service. If the integration has a separate enable switch, the status is derived from that. If there is no switch, the integration is interpreted as enabled when all required settings are configured.

Specified means that no required configuration keys are missing. Missing N keys indicates the number of required keys that are missing. A disabled integration can still contain settings, and the specified state does not prove the functionality of the external service connection.

The card's Updated time is generated from the last modification time of the integration's known configuration keys. An empty timestamp means that no modification time to display is available.

Check the integration settings

Check the integration settings by selecting Edit on the card. Despite the name, the window that opens is read-only: fields are disabled and there is no save function.

Each field displays a name, description, mandatory status, and current display value. An empty value is displayed as No Value . A secret value is only provided to the user interface as a masked display value; the raw value is not returned as the field value.

If integration details are not received within eight seconds, the request is aborted and the window displays an error. Close the window and try again. A recurring error requires investigation of the service or management interface.

Use the view for troubleshooting

The Integrations view helps you find missing mandatory settings before attempting to implement a payment, delivery, search, or other service. Start by checking the usage status, configuration status, and number of missing keys.

The view does not test the connection to the external service. Defined only indicates that the required values exist. Verify the actual operation of the integration in its own workflow, such as with a test purchase, delivery method search, search query, or documented service-specific test.

If a required value is missing, update it in the actual settings management location for the integration. The Integrations view does not tell you the editing path for each service, so use the setting key name and the service's own instructions to find the correct maintenance location.

Impact on online shopping

The integrations summary itself does not change the online store. The real impact is created in the service-specific functionality: payments at checkout, delivery services in delivery methods, search in product search, and ERP in order or balance transfer.

Don't interpret every green card as a promise of the entire store being operational. Verify business-critical integrations with a real test and check any error logs of the external service separately.

Perform a functional check in a secure test environment whenever keys, endpoints, or usage mode are changed.

Good to know

Integrations is a snapshot, not a configuration form or monitoring service. It only shows the integrations defined in the current registry and their known configuration keys.

Secret values are obfuscated on the server before the response is generated. Do not copy the display value as a new secret, as the obfuscated string is not the original value.

The number of integrations, categories, and required keys may change as the implementation progresses. Use the current content of the cards as a primary checklist rather than a fixed number.