commercetools InStore compatibility and release lifecycle

Compatibility

commercetools InStore issues major releases as soon as features and updates are ready, and minor releases to allow us to promptly correct any issues. While efforts are made to minimize breaking changes, the nature of management APIs means they may be subject to change without prior notice.

Implications

If the Customer sends additional undocumented fields, these can conflict with future new field names in commercetools InStore, causing runtime errors. Avoiding this is the responsibility of the Customer.

Release life cycle

Early access

After being initially deployed, new features can go through an early access phase for evaluation by selected customers. This phase aims to collect feedback early in the development cycle to improve and refine the new feature. Participating in early access programs is a great way to experiment with new features and share your insights with the Product team. Please note that early access features should not be used in production, and they do not have publicly available documentation or release notes; instead, participants are notified of any changes directly.

commercetools may change or discontinue early access functionalities at any time. These features might be removed entirely on rare occasions. Regardless of whether these functionalities are free or paid, or used in test or production environments, commercetools does not offer support, service level commitments, or remedies for them.

Reach out to your contact person at commercetools to learn about or to get access to early access features.

General availability

Once a commercetools InStore feature is released, it becomes generally available. The change in status is announced in release notes.

Deprecation

As commercetools InStore evolves, some features are superseded by better implementations and should not be used anymore. Any such cases are announced in release notes.