← Back to all sparks
commercetools logo

commercetools

E-COMM
Velocity5.0

Headless commerce platform

commercetools is grinding out API ergonomics — extension dependencies, audit log coverage, import API breadth.

api extensibilityaudit logheadless commercecomplete checkoutimport apiinstore commerce
Current state
commercetools' recent cadence is dense and small-grained: API Extension execution-order dependencies, previous-state payloads on extensions, Audit Log coverage for payment transaction interface changes, Standalone Price import flags, Product Tailoring import endpoint, External Shipping Methods entering Complete Checkout public beta, and InStore configuration knobs. Nothing dramatic, but the consistent pattern is removing friction from how developers compose extensions and how data moves in via the Import API.
Where it's heading
commercetools is reinforcing its core position as the API-first composable commerce platform by deepening extension composability and observability — exactly what enterprise integrators ask for after they've adopted the platform and started building real workflows. The InStore stream parallel to the headless API work signals continued investment in unified online/in-store commerce, where the InStore payment GA earlier this month is the most visible move.
Prediction
Expect Complete Checkout's external shipping methods to graduate from beta and be followed by external payment methods, completing the headless-checkout extensibility story. The Audit Log will likely keep expanding event coverage on a steady drip until it reaches parity with what enterprise compliance audits actually request.

Recent moves

  1. 1mo ago

    Improved Stores and Channels management in Merchant Center

    View source ↗
  2. 1mo ago

    API Extensions can declare dependencies for execution order and data flow

    API Extensions on the same resource can now declare dependencies, giving developers explicit control over execution order and inter-extension data flow. Removes a real source of race-condition surprise when integrators stack multiple extensions on a single resource — directly aligned with the composability-deepening trajectory.

  3. 2mo ago

    Added SetTransactionInterfaceIdChange to Audit Log

    Audit Log now records changes to the interface ID on Payment Transactions — incremental coverage expansion, useful for payments-team forensics. Fits the steady audit-log breadth push that's been visible across recent releases.

    View source ↗
  4. 2mo ago

    Override job application schedule in Deployment configuration

    Connect deployments can now override a job application's default schedule with a cron expression set in the Deployment configuration. Operational ergonomics for teams running scheduled Connect apps — useful in multi-environment setups where the developer-supplied default doesn't fit.

    View source ↗
  5. 2mo ago

    Added previous resource state in API Extension payloads

    API Extensions can now receive the previous resource state alongside the current one. This unlocks diff-based extension logic without callers having to maintain their own state cache — same composability-deepening theme as the new dependency declarations.

    View source ↗
  6. 2mo ago

    External Shipping Methods are now supported in Complete Checkout mode in public beta

    External Shipping Methods become usable in Complete Checkout mode (public beta), extending the headless-checkout extensibility story. Reads as the precursor step before external payment methods get the same treatment.

    View source ↗