Skip to content
Connection Guide

Connect commercetools Composable Commerce Without Breaking the Audit Trail

Use this guide to connect commercetools Composable Commerce or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeDirect connection
CategoryPayments / PCI
Checklist4 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect commercetools Composable Commerce and make sure the first collection lands cleanly.

  1. 1
    Create a dedicated Commercetools API client with the documented read scopes for the target project.
  2. 2
    Store client ID and client secret securely and configure auth_url, api_url, history_url, and project_key.
  3. 3
    Confirm whether the project is B2B-enabled and whether Audit Log Premium is licensed before production rollout.
  4. 4
    Validate project, customer, business-unit, and bounded history reads before enabling scheduled sync.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

client_idclient_secret

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.