Release Notes

We introduced the key field on LineItem and LineItemDraft. This ensures a consistent experience when working with external identifiers across different entity types in Composable Commerce.

Changes:

• [GraphQL API] Changed the AddStagedOrderLineItem type:
  • Input field key was added to AddStagedOrderLineItem type
• [GraphQL API] Changed the MyLineItemDraft type:
  • Input field key was added to MyLineItemDraft type
• [GraphQL API] Changed the LineItemDraft type:
  • Input field key was added to LineItemDraft type
• [GraphQL API] Changed the AddCartLineItem type:
  • Input field key was added to AddCartLineItem type
• [GraphQL API] Changed the LineItem type:
  • Added the key field to the LineItem type.
• [GraphQL API] Changed the LineItemDraftOutput type:
  • Added the key field to the LineItemDraftOutput type.
• [GraphQL API] Changed the AddMyCartLineItem type:
  • Input field key was added to AddMyCartLineItem type

Business Units and Associate Roles can now be used as ReferenceTypes on Custom Fields. The new associate-role and business-unit values are supported on all customizable data types providing full flexibility in extending B2B features.

Changes:

• [API] Added business-unit and associate-role to CustomFieldReferenceValue.

We are announcing that Confluent Cloud is now supported as a Subscription destination.

With the introduction of Confluent Cloud support, customers can now natively use Apache Kafka across their preferred cloud platforms, whether it's Google Cloud, Azure, or AWS. This integration not only eliminates the necessity for intermediary gateways to consume messages from Kafka but also reduces the associated resources and costs.

Changes:

• [API] Added ConfluentCloudDestination to Subscriptions.
• [GraphQL API] Added the following types to the GraphQL schema: ConfluentCloudDestination, ConfluentCloudDestinationInput
• [GraphQL API] Changed the DestinationInput type:
  • Input field ConfluentCloud was added to DestinationInput type

We introduced GraphQL support for creating Associates using My Business Units. This allows Customers with the UpdateAssociates Permission to create a new Associate, assigning them roles specific to the given Business Unit.

Changes:

• [GraphQL API] Added the following types to the GraphQL schema: SignUpInMyBusinessUnitDraft.
• [GraphQL API] Changed the Mutation type:
  • Added the signUpInMyBusinessUnit field to the Mutation type.

We introduced the key field on Parcel and ParcelDraft. This ensures a consistent experience when working with external identifiers across different entity types in Composable Commerce.

Changes:

• [API] Added the key field to Parcel and ParcelDraft.
• [API] Added the parcelKey field and changed the parcelId field to be optional on the following Order and StagedOrderUpdateAction update actions:
  • Set Parcel Custom Type
  • Set Parcel Custom Field
  • Remove Parcel from Delivery
  • Set Parcel Measurements
  • Set Parcel Tracking Data
  • Set Parcel Items
• [API] Added the parcelKey field to the Add Parcel update action on Order and StagedOrderUpdateAction.
• [GraphQL API] Changed the Parcel type:
  • Added the key field to the Parcel type.
• [GraphQL API] Changed the ParcelDraft type:
  • Input field key was added to ParcelDraft type
• [GraphQL API] Changed the SetStagedOrderParcelCustomTypeOutput type:
  • Added the parcelKey field to the SetStagedOrderParcelCustomTypeOutput type.
  • SetStagedOrderParcelCustomTypeOutput.parcelId field type changed from String! to String
• [GraphQL API] Changed the SetOrderParcelMeasurements type:
  • SetOrderParcelMeasurements.parcelId input field type changed from String! to String
  • Input field parcelKey was added to SetOrderParcelMeasurements type
• [GraphQL API] Changed the SetStagedOrderParcelCustomType type:
  • SetStagedOrderParcelCustomType.parcelId input field type changed from String! to String
  • Input field parcelKey was added to SetStagedOrderParcelCustomType type
• [GraphQL API] Changed the SetStagedOrderParcelTrackingData type:
  • SetStagedOrderParcelTrackingData.parcelId input field type changed from String! to String
  • Input field parcelKey was added to SetStagedOrderParcelTrackingData type
• [GraphQL API] Changed the SetStagedOrderParcelCustomField type:
  • SetStagedOrderParcelCustomField.parcelId input field type changed from String! to String
  • Input field parcelKey was added to SetStagedOrderParcelCustomField type
• [GraphQL API] Changed the SetStagedOrderParcelMeasurements type:
  • Input field parcelKey was added to SetStagedOrderParcelMeasurements type
  • SetStagedOrderParcelMeasurements.parcelId input field type changed from String! to String
• [GraphQL API] Changed the AddOrderParcelToDelivery type:
  • Input field parcelKey was added to AddOrderParcelToDelivery type
• [GraphQL API] Changed the SetStagedOrderParcelTrackingDataOutput type:
  • SetStagedOrderParcelTrackingDataOutput.parcelId field type changed from String! to String
  • Added the parcelKey field to the SetStagedOrderParcelTrackingDataOutput type.
• [GraphQL API] Changed the SetStagedOrderParcelMeasurementsOutput type:
  • SetStagedOrderParcelMeasurementsOutput.parcelId field type changed from String! to String
  • Added the parcelKey field to the SetStagedOrderParcelMeasurementsOutput type.
• [GraphQL API] Changed the SetOrderParcelTrackingData type:
  • SetOrderParcelTrackingData.parcelId input field type changed from String! to String
  • Input field parcelKey was added to SetOrderParcelTrackingData type
• [GraphQL API] Changed the RemoveOrderParcelFromDelivery type:
  • RemoveOrderParcelFromDelivery.parcelId input field type changed from String! to String
  • Input field parcelKey was added to RemoveOrderParcelFromDelivery type
• [GraphQL API] Changed the ParcelData type:
  • Added the key field to the ParcelData type.
• [GraphQL API] Changed the AddStagedOrderParcelToDelivery type:
  • Input field parcelKey was added to AddStagedOrderParcelToDelivery type
• [GraphQL API] Changed the SetStagedOrderParcelItems type:
  • SetStagedOrderParcelItems.parcelId input field type changed from String! to String
  • Input field parcelKey was added to SetStagedOrderParcelItems type
• [GraphQL API] Changed the SetOrderParcelCustomType type:
  • SetOrderParcelCustomType.parcelId input field type changed from String! to String
  • Input field parcelKey was added to SetOrderParcelCustomType type
• [GraphQL API] Changed the ParcelDataDraftType type:
  • Input field key was added to ParcelDataDraftType type
• [GraphQL API] Changed the SetStagedOrderParcelItemsOutput type:
  • SetStagedOrderParcelItemsOutput.parcelId field type changed from String! to String
  • Added the parcelKey field to the SetStagedOrderParcelItemsOutput type.
• [GraphQL API] Changed the RemoveStagedOrderParcelFromDeliveryOutput type:
  • Added the parcelKey field to the RemoveStagedOrderParcelFromDeliveryOutput type.
  • RemoveStagedOrderParcelFromDeliveryOutput.parcelId field type changed from String! to String
• [GraphQL API] Changed the SetOrderParcelItems type:
  • Input field parcelKey was added to SetOrderParcelItems type
  • SetOrderParcelItems.parcelId input field type changed from String! to String
• [GraphQL API] Changed the SetOrderParcelCustomField type:
  • Input field parcelKey was added to SetOrderParcelCustomField type
  • SetOrderParcelCustomField.parcelId input field type changed from String! to String
• [GraphQL API] Changed the RemoveStagedOrderParcelFromDelivery type:
  • RemoveStagedOrderParcelFromDelivery.parcelId input field type changed from String! to String
  • Input field parcelKey was added to RemoveStagedOrderParcelFromDelivery type
• [GraphQL API] Changed the SetStagedOrderParcelCustomFieldOutput type:
  • SetStagedOrderParcelCustomFieldOutput.parcelId field type changed from String! to String
  • Added the parcelKey field to the SetStagedOrderParcelCustomFieldOutput type.
• [GraphQL API] Changed the AddStagedOrderParcelToDeliveryOutput type:
  • Added the parcelKey field to the AddStagedOrderParcelToDeliveryOutput type.

You can now change the InventoryMode of an existing LineItem by using the Set LineItem InventoryMode update action on the general endpoint. The InventoryMode could previously only be set when creating new Line Items.

Changes:

• [API] Added Set LineItem InventoryMode update action to the Carts API.
• [GraphQL API] Added the following types to the GraphQL schema: SetCartLineItemInventoryMode.
• [GraphQL API] Changed the CartUpdateAction type:
  • Input field setLineItemInventoryMode was added to CartUpdateAction type

A new state RenegotiationAddressed has been added to QuoteState. With this new state, Sellers can see Quotes where renegotiations requested by the respective buyer have been addressed.

Changes:

• [API] Added RenegotiationAddressed field to QuoteState.
• [GraphQL API] Changed the QuoteState type:
  • Enum value RenegotiationAddressed was added to enum QuoteState

After collecting feedback during the beta phase, we have moved countries on Stores out of beta. The status of the following features has been changed to general availability:

• Adding a country to a Store.
• Removing a country from a Store.
• Setting the countries on a Store.
• The StoreCountriesChanged Message.

Visit the API reference to learn more about how countries on Stores can enable filtering prices in Product Projections and Cart, Order, and Shopping List Line Items.

We've added the MoneyOverflow error code to help identify instances when a Money operation has failed due to an integer overflow.

Both centAmount (applicable to all money types), as well as preciseAmount (for high precision money types) are represented as 64-bit integers. If a Money operation results in either object exceeding the 64-bit limit, the API returns a 400 Bad Request with the MoneyOverflow error code.

Changes:

• [API] Added the MoneyOverflow error code.

After collecting feedback during the beta phase, we have moved Attribute Groups out of beta. The status of the following features has been changed to general availability:

• Querying and managing Attribute Groups.

Attribute Groups let you organize Attribute Definitions by providing a list of references to Product Attributes. Learn more by visiting our documentation page.

After collecting feedback during the beta phase, we have moved Direct Discounts out of beta. With Direct Discounts you can add a fixed or percentage discount to a single Cart.

The status of the following features has been changed to general availability:

• Set Direct Discounts on Order Edits

• Set Direct Discounts on Carts

We introduced functionality to enable the reassignment of B2B Quotes and Quote Requests. This enhancement ensures that the Customer on a Quote or Quote Request can be updated in the event that they leave their Business Unit. The new Change Customer update action is available on Quote and Quote Request.

The new ReassignMyQuotes and ReassignOthersQuotes Permissions determine the ability to reassign a Quote within the context of a Business Unit. To enhance visibility and tracking, we have introduced two new Messages: QuoteRequestCustomerChanged and QuoteCustomerChanged. These Messages are triggered whenever a Quote or Quote Request's Customer is modified.

These enhancements improve the management of B2B Quotes within Composable Commerce, ensuring that Quotes and Quote Requests remain connected to the appropriate Associates even during organizational changes.

Changes:

• [API] Added the Change Customer update action to Quote.
• [API] Added the Change Customer update action to Quote Requests.
• [API] Added ReassignMyQuotes and ReassignOthersQuotes Permissions.
• [API] Added QuoteRequestCustomerChanged and QuoteCustomerChanged Messages.
• [GraphQL API] Added the following types to the GraphQL schema: ChangeQuoteCustomer, ChangeQuoteRequestCustomer.
• [GraphQL API] Changed the Permission type:
  • Enum value ReassignOthersQuotes was added to enum Permission
  • Enum value ReassignMyQuotes was added to enum Permission
• [GraphQL API] Changed the QuoteRequestUpdateAction type:
  • Input field changeCustomer was added to QuoteRequestUpdateAction type
• [GraphQL API] Changed the QuoteUpdateAction type:
  • Input field changeCustomer was added to QuoteUpdateAction type

You can now replicate Carts in a given Business Unit using the Associate Carts endpoint.

• [API] Added Replicate Cart in Business Unit endpoint.
• [GraphQL API] Changed the Mutation type:
  • Argument asAssociate was added to Mutation.replicateCart field

We have added support for external tax rates and tax amounts on multiple Shipping Methods. You can now target individual Shipping Methods by including a shippingKey when using the Set ShippingMethod TaxAmount and Set ShippingMethod TaxRate update actions for Carts and Order Edits.

Changes:

• [API] Added the shippingKey field to the following update actions on Carts:

  • Set ShippingMethod TaxAmount
  • Set ShippingMethod TaxRate

• [API] Added the shippingKey field to the following update actions on Order Edits:

  • Set ShippingMethod TaxAmount
  • Set ShippingMethod TaxRate

• [GraphQL API] Changed the SetStagedOrderShippingMethodTaxRateOutput type:

  • Added the shippingKey field to the SetStagedOrderShippingMethodTaxRateOutput type.

• [GraphQL API] Changed the SetStagedOrderShippingMethodTaxAmount type:

  • Input field shippingKey was added to SetStagedOrderShippingMethodTaxAmount type

• [GraphQL API] Changed the SetCartShippingMethodTaxRate type:

  • Input field shippingKey was added to SetCartShippingMethodTaxRate type

• [GraphQL API] Changed the SetStagedOrderShippingMethodTaxRate type:

  • Input field shippingKey was added to SetStagedOrderShippingMethodTaxRate type

• [GraphQL API] Changed the SetCartShippingMethodTaxAmount type:

  • Input field shippingKey was added to SetCartShippingMethodTaxAmount type

• [GraphQL API] Changed the SetStagedOrderShippingMethodTaxAmountOutput type:

  • Added the shippingKey field to the SetStagedOrderShippingMethodTaxAmountOutput type.

We have added support for New Relic to Composable Commerce SDKs.

New Relic is an observability platform which monitors your application's performance. This integration helps you analyze your application to identify potential improvements for performance and user experience.

With this update, you can:

• Trace and profile application performance directly from the SDK.
• View and analyze your application's performance.
• Get real-time insights and alerts about your application's performance and issues.

New Relic is currently supported by the latest versions of the Java SDK, TypeScript SDK and PHP SDK. To learn more, visit the SDK Observability page.

commercetools Composable Commerce is now available in China on AWS Ningxia in addition to our existing Regions in North America, Europe, and Australia. The China Region is available as part of Composable Commerce for China. Please reach out to your commercetools contact person to learn more.

Find the URLs to the commercetools Composable Commerce API here. Log in here.

When configuring a Project in the China Region, note that external links (for example, URLs used for images, external OAuth, and API Extensions) may be blocked due to firewall restrictions.

The variantId, sku and price fields are now deprecated in the Remove Price update action on Products. Please use priceId instead. For the GraphQL API, please use RemoveProductPrice.priceId instead.

Changes:

• [GraphQL API] Changed the RemoveProductPrice type:
  • RemoveProductPrice.variantId is deprecated
  • RemoveProductPrice.sku is deprecated
  • RemoveProductPrice.price is deprecated

We introduced the key field on Delivery and DeliveryDraft. This ensures a consistent experience when working with external identifiers across different entity types in Composable Commerce.

Changes:

• [API] Added the key field to Delivery and DeliveryDraft.

• [API] Added the deliveryKey field to the following update actions on Orders:

  • Add Delivery
  • Add Parcel
  • Remove Delivery
  • Set Delivery Address
  • Set Delivery Address CustomField
  • Set Delivery Address Custom Type
  • Set Delivery CustomField
  • Set Delivery Custom Type
  • Set Delivery Items

• [API] Added the deliveryKey field to the following update actions on Order Edits:

  • Add Delivery
  • Add Parcel
  • Remove Delivery
  • Set Delivery Address
  • Set Delivery Address CustomField
  • Set Delivery Address Custom Type
  • Set Delivery CustomField
  • Set Delivery Custom Type
  • Set Delivery Items

• [API] Changed the deliveryId field to be optional on the following update actions on Orders:

  • Add Parcel
  • Remove Delivery
  • Set Delivery Address
  • Set Delivery Address CustomField
  • Set Delivery Address Custom Type
  • Set Delivery CustomField
  • Set Delivery Custom Type
  • Set Delivery Items

• [API] Changed the deliveryId field to be optional on the following update actions on Order Edits:

  • Add Parcel
  • Remove Delivery
  • Set Delivery Address
  • Set Delivery Address CustomField
  • Set Delivery Address Custom Type
  • Set Delivery CustomField
  • Set Delivery Custom Type
  • Set Delivery Items

• [GraphQL API] Changed the SetStagedOrderDeliveryCustomField type:

  • Input field deliveryKey was added to SetStagedOrderDeliveryCustomField type
  • SetStagedOrderDeliveryCustomField.deliveryId input field type changed from String! to String

• [GraphQL API] Changed the AddStagedOrderDeliveryOutput type:

  • Added the deliveryKey field to the AddStagedOrderDeliveryOutput type.

• [GraphQL API] Changed the SetStagedOrderDeliveryAddressOutput type:

  • SetStagedOrderDeliveryAddressOutput.deliveryId field type changed from String! to String
  • Added the deliveryKey field to the SetStagedOrderDeliveryAddressOutput type.

• [GraphQL API] Changed the Delivery type:

  • Added the key field to the Delivery type.

• [GraphQL API] Changed the SetStagedOrderDeliveryAddressCustomType type:

  • Input field deliveryKey was added to SetStagedOrderDeliveryAddressCustomType type
  • SetStagedOrderDeliveryAddressCustomType.deliveryId input field type changed from String! to String

• [GraphQL API] Changed the AddStagedOrderDelivery type:

  • Input field deliveryKey was added to AddStagedOrderDelivery type

• [GraphQL API] Changed the SetStagedOrderDeliveryItemsOutput type:

  • Added the deliveryKey field to the SetStagedOrderDeliveryItemsOutput type.
  • SetStagedOrderDeliveryItemsOutput.deliveryId field type changed from String! to String

• [GraphQL API] Changed the SetStagedOrderDeliveryAddress type:

  • Input field deliveryKey was added to SetStagedOrderDeliveryAddress type
  • SetStagedOrderDeliveryAddress.deliveryId input field type changed from String! to String

• [GraphQL API] Changed the SetStagedOrderDeliveryAddressCustomTypeOutput type:

  • Added the deliveryKey field to the SetStagedOrderDeliveryAddressCustomTypeOutput type.
  • SetStagedOrderDeliveryAddressCustomTypeOutput.deliveryId field type changed from String! to String

• [GraphQL API] Changed the SetOrderDeliveryAddressCustomField type:

  • SetOrderDeliveryAddressCustomField.deliveryId input field type changed from String! to String
  • Input field deliveryKey was added to SetOrderDeliveryAddressCustomField type

• [GraphQL API] Changed the SetStagedOrderDeliveryCustomType type:

  • SetStagedOrderDeliveryCustomType.deliveryId input field type changed from String! to String
  • Input field deliveryKey was added to SetStagedOrderDeliveryCustomType type

• [GraphQL API] Changed the DeliveryDraft type:

  • Input field key was added to DeliveryDraft type

• [GraphQL API] Changed the RemoveStagedOrderDeliveryOutput type:

  • Added the deliveryKey field to the RemoveStagedOrderDeliveryOutput type.
  • RemoveStagedOrderDeliveryOutput.deliveryId field type changed from String! to String

• [GraphQL API] Changed the RemoveStagedOrderDelivery type:

  • RemoveStagedOrderDelivery.deliveryId input field type changed from String! to String
  • Input field deliveryKey was added to RemoveStagedOrderDelivery type

• [GraphQL API] Changed the AddOrderDelivery type:

  • Input field deliveryKey was added to AddOrderDelivery type

• [GraphQL API] Changed the SetStagedOrderDeliveryCustomFieldOutput type:

  • Added the deliveryKey field to the SetStagedOrderDeliveryCustomFieldOutput type.
  • SetStagedOrderDeliveryCustomFieldOutput.deliveryId field type changed from String! to String

• [GraphQL API] Changed the SetStagedOrderDeliveryAddressCustomFieldOutput type:

  • SetStagedOrderDeliveryAddressCustomFieldOutput.deliveryId field type changed from String! to String
  • Added the deliveryKey field to the SetStagedOrderDeliveryAddressCustomFieldOutput type.

• [GraphQL API] Changed the AddStagedOrderParcelToDelivery type:

  • Input field deliveryKey was added to AddStagedOrderParcelToDelivery type
  • AddStagedOrderParcelToDelivery.deliveryId input field type changed from String! to String

• [GraphQL API] Changed the SetOrderDeliveryAddress type:

  • SetOrderDeliveryAddress.deliveryId input field type changed from String! to String
  • Input field deliveryKey was added to SetOrderDeliveryAddress type

• [GraphQL API] Changed the AddOrderParcelToDelivery type:

  • AddOrderParcelToDelivery.deliveryId input field type changed from String! to String
  • Input field deliveryKey was added to AddOrderParcelToDelivery type

• [GraphQL API] Changed the RemoveOrderDelivery type:

  • RemoveOrderDelivery.deliveryId input field type changed from String! to String
  • Input field deliveryKey was added to RemoveOrderDelivery type

• [GraphQL API] Changed the SetOrderDeliveryCustomType type:

  • Input field deliveryKey was added to SetOrderDeliveryCustomType type
  • SetOrderDeliveryCustomType.deliveryId input field type changed from String! to String

• [GraphQL API] Changed the SetOrderDeliveryCustomField type:

  • SetOrderDeliveryCustomField.deliveryId input field type changed from String! to String
  • Input field deliveryKey was added to SetOrderDeliveryCustomField type

• [GraphQL API] Changed the SetStagedOrderDeliveryItems type:

  • SetStagedOrderDeliveryItems.deliveryId input field type changed from String! to String
  • Input field deliveryKey was added to SetStagedOrderDeliveryItems type

• [GraphQL API] Changed the SetStagedOrderDeliveryCustomTypeOutput type:

  • Added the deliveryKey field to the SetStagedOrderDeliveryCustomTypeOutput type.
  • SetStagedOrderDeliveryCustomTypeOutput.deliveryId field type changed from String! to String

• [GraphQL API] Changed the SetOrderDeliveryAddressCustomType type:

  • Input field deliveryKey was added to SetOrderDeliveryAddressCustomType type
  • SetOrderDeliveryAddressCustomType.deliveryId input field type changed from String! to String

• [GraphQL API] Changed the SetStagedOrderDeliveryAddressCustomField type:

  • SetStagedOrderDeliveryAddressCustomField.deliveryId input field type changed from String! to String
  • Input field deliveryKey was added to SetStagedOrderDeliveryAddressCustomField type

• [GraphQL API] Changed the AddStagedOrderParcelToDeliveryOutput type:

  • Added the deliveryKey field to the AddStagedOrderParcelToDeliveryOutput type.
  • AddStagedOrderParcelToDeliveryOutput.deliveryId field type changed from String! to String

• [GraphQL API] Changed the SetOrderDeliveryItems type:

  • SetOrderDeliveryItems.deliveryId input field type changed from String! to String
  • Input field deliveryKey was added to SetOrderDeliveryItems type

We added support for locale-based Product Projection to the product and products queries on the GraphQL API. With this projection, your response contains the translation on Products (also in a Store) you have specified in your query only. All other locales are filtered out from the product information. Furthermore, the projection can also be applied to Products expanded on Reference Type Attributes.

Changes:

• [GraphQL API] Changed the Query type:
  • Argument localeProjection was added to Query.products field
  • Argument localeProjection was added to Query.product field
  • Argument projectExpandedProducts was added to Query.productProjectionSearch field
  • Argument projectExpandedProducts was added to Query.product field
  • Argument projectExpandedProducts was added to Query.products field
• [GraphQL API] Changed the InStore type:
  • Arguments localeProjection was added to InStore.product field
  • Argument projectExpandedProducts was added to InStore.product field

We have made the fields BusinessUnit.associateMode, Associate.associateRoleAssignments, and AssociateRoleAssignment.inheritance mandatory in responses. They were previously optional during the closed beta period.

Changes:

• [GraphQL API] Changed the BusinessUnit type:
  • BusinessUnit.associateMode field type changed from BusinessUnitAssociateMode to BusinessUnitAssociateMode!
• [GraphQL API] Changed the Associate type:
  • Associate.associateRoleAssignments field type changed from [AssociateRoleAssignment!] to [AssociateRoleAssignment!]!
• [GraphQL API] Changed the AssociateRoleAssignment type:
  • AssociateRoleAssignment.inheritance field type changed from AssociateInheritanceMode to AssociateInheritanceMode!

We introduced the error code AssociateMissingPermissionError for Associate Roles. This error code helps to identify when an Associate is missing a specific Permission on a B2B resource.

Changes:

• [API] Added AssociateMissingPermissionError.

The GraphQL API now supports querying inherited Stores of a Business Unit. Visit the API reference for more information on additional GraphQL fields available on Business Units.

Changes:

• [GraphQL API] Changed the BusinessUnit type:
  • Added the inheritedStores field to the BusinessUnit type.

The new Associate Roles API provides B2B customers with the flexibility to define and manage the permissions of their Associates. The feature allows the configuration of granular permissions that provide controlled access to Business Units, Carts, Orders, Quotes, and Quote Requests. Additionally, roles can be inherited from a parent Business Unit by its children.

This feature replaces the less flexible AssociateRole enum with Buyer and Admin values. This type alongside the roles field on Associate and AssociateDraft is now deprecated and will be completely removed on 02 August 2023.

In addition to the Associate Roles API, a new set of associate endpoints can be used to validate that an Associate has sufficient permissions on a given resource. These endpoints are available for Business Units, Carts, Orders, Quotes, and Quote Requests and perform permission evaluation checks based on an associateId.

These features are part of Composable Commerce for B2B and will be subject to additional terms and pricing.

Changes:

• [API] Added Associate Roles API.
• [API] Added Associate Carts, Associate Orders, Associate Quote Requests, Associate Quotes, and Associate BusinessUnit endpoints.
• [API] Added BusinessUnitAssociateMode, AssociateRoleInheritanceMode, AssociateRoleAssignment, and AssociateRoleAssignmentDraft, InheritedAssociate, and InheritedAssociateRoleAssignment types to BusinessUnit.
• [API] Added inheritedAssociates and associateMode fields to BusinessUnit.
• [API] Added associateMode fields to BusinessUnitDraft.
• [API] Added associateRoleAssignments field to Associate and AssociateDraft.
• [API] AddedassociateRoleAssignments to MyBusinessUnitAssociateDraft.
• [API] Deprecated AssociateRole enum with Admin and Buyer values.
• [API] Deprecated roles and inheritedAssociates field on Associate and AssociateDraft.
• [API] Added Associate Role Messages.
• [API] Added BusinessUnitAssociateModeChanged Message.
• [API] Added myBusinessUnitAssociateRoleOnCreation to BusinessUnitConfiguration in Project settings.
• [GraphQL API] Added the following types to the GraphQL schema: AddAssociateRolePermission, AsAssociate, AsAssociateArgument, AssociateInheritanceMode, AssociateRole, AssociateRoleAssignment, AssociateRoleAssignmentDraft, AssociateRoleBuyerAssignableChanged, AssociateRoleCreated, AssociateRoleDeleted, AssociateRoleDraft, AssociateRoleNameSet, AssociateRolePermissionAdded, AssociateRolePermissionRemoved, AssociateRolePermissionsSet, AssociateRoleQueryResult, AssociateRoleUpdateAction, BusinessUnitAssociateMode, BusinessUnitAssociateModeChanged, ChangeAssociateRoleBuyerAssignable, ChangeBusinessUnitAssociateMode, InheritedAssociate, InheritedAssociateRoleAssignment, Permission, RemoveAssociateRolePermission, SetAssociateRoleCustomField, SetAssociateRoleCustomType, SetAssociateRoleName, SetAssociateRolePermissions, SetProjectSettingsMyBusinessUnitAssociateRoleOnCreation.
• [GraphQL API] Changed the BusinessUnitDraft type:
  • Input field associateMode was added to BusinessUnitDraft type
• [GraphQL API] Changed the BusinessUnit type:
  • Added the inheritedAssociates field to the BusinessUnit type.
  • Added the associateMode field to the BusinessUnit type.
• [GraphQL API] Changed the Associate type:
  • Added the associateRoleAssignments field to the Associate type.
  • Field roles was deprecated in Associate type
• [GraphQL API] Changed the AssociateDraft type:
  • Input field associateRoleAssignments was added to AssociateDraft type
  • Input field roles was deprecated in AssociateDraft type
• [GraphQL API] Changed the BusinessUnitConfiguration type:
  • Added the myBusinessUnitAssociateRoleOnCreation field to the BusinessUnitConfiguration type.
  • Added the myBusinessUnitAssociateRoleOnCreationRef field to the BusinessUnitConfiguration type.
• [GraphQL API] SimpleAssociateRole type was deprecated
• [GraphQL API] Changed the Query type:
  • Added the asAssociate field to the Query type.
  • Added the associateRole field to the Query type.
  • Added the associateRoles field to the Query type.
• [GraphQL API] Changed the Mutation type:
  • Argument asAssociate was added to Mutation.updateBusinessUnit field
  • Added the updateAssociateRole field to the Mutation type.
  • Argument asAssociate was added to Mutation.createOrderFromCart field
  • Argument asAssociate was added to Mutation.deleteCart field
  • Argument asAssociate was added to Mutation.createBusinessUnit field
  • Argument asAssociate was added to Mutation.updateQuoteRequest field
  • Argument asAssociate was added to Mutation.createOrderFromQuote field
  • Argument asAssociate was added to Mutation.createCart field
  • Argument asAssociate was added to Mutation.updateOrder field
  • Added the deleteAssociateRole field to the Mutation type.
  • Argument asAssociate was added to Mutation.updateQuote field
  • Argument asAssociate was added to Mutation.createQuoteRequest field
  • Added the createAssociateRole field to the Mutation type.
  • Argument asAssociate was added to Mutation.updateCart field
• [GraphQL API] Changed the ProjectSettingsUpdateAction type:
  • Input field setMyBusinessUnitAssociateRoleOnCreation was added to ProjectSettingsUpdateAction type
• [GraphQL API] Changed the BusinessUnitUpdateAction type:
  • Input field changeAssociateMode was added to BusinessUnitUpdateAction type

After collecting feedback during the beta phase, we have moved Product Selections out of beta. The status of the following features has been changed to general availability:

• Querying and managing Product Selections.
• Adding and removing Products from Product Selections.

Product Selections can be used to manage individual assortments for different sales channels and Stores. Learn more by visiting our documentation page.

We introduced a new type ProductSelectionMode to replace ProductSelectionType. The functionality of Individual and IndividualExclusion Product Selections remains the same. We adjusted the naming of the type and the enums to ensure a consistent experience when working with the Composable Commerce APIs.

Instead of the previous individual and individualExclusion enums defined by the type field on ProductSelection, you can now use the mode field with the values Individual and IndividualExclusion. The type field, alongside ProductSelectionType is now deprecated and will be completely removed on 18 July 2023.

We also aligned the behavior of ProductSelectionCreated Message with other similar Messages generated by resource creation. The Message now includes the entire ProductSelection object in the payload, instead of a subset of the fields.

Changes:

• [API] Added the mode field to ProductSelection and ProductSelectionDraft.
• [API] Deprecated ProductSelectionTypeEnum, IndividualProductSelectionType, IndividualExclusionProductSelectionType from ProductSelection.
• [API] Deprecated the type field from ProductSelection and ProductSelectionDraft.
• [API] Changed the type of productSelection field on ProductSelectionCreated Message from ProductSelectionType to ProductSelection.
• [GraphQL API] Removed the following types from the GraphQL schema: ProductSelectionType, IndividualExclusionProductSelectionCreatedPayload, IndividualProductSelectionCreatedPayload, ProductSelectionCreatedPayload.
• [GraphQL API] Changed the ProductSelection type:
  • Removed the type field from the ProductSelection type.
  • Added the mode field to the ProductSelection type.
• [GraphQL API] Changed the CreateProductSelectionDraft type:
  • Input field type was removed from CreateProductSelectionDraft type
  • Input field mode was added to CreateProductSelectionDraft type
• [GraphQL API] Changed the ProductSelectionCreated type:
  • ProductSelectionCreated.productSelection field type changed from ProductSelectionCreatedPayload! to ProductSelection!

Audit Log is now available in AWS Regions in beta.

You can now retrieve the shippingCustomFields and shippingKey fields on Carts and Orders with Single ShippingMode.

Changes:

• [API] Added the shippingCustomFields field to Cart and Order.
• [API] Added the shippingKey field to Cart and Order.
• [GraphQL API] Changed the Cart type:
  • Added the shippingKey field to the Cart type.
  • Added the shippingCustomFields field to the Cart type.
• [GraphQL API] Changed the Order type:
  • Added the shippingKey field to the Order type.
  • Added the shippingCustomFields field to the Order type.

We introduced the key field on TaxRate and TaxRateDraft. This ensures a consistent experience when working with external identifiers across different entity types in Composable Commerce.

Changes:

• [API] Added the key field to TaxRate and TaxRateDraft.
• [API] Added the taxRateKey field to Remove TaxRate and Replace TaxRate update actions.
• [API] Changed the taxRateId field to be optional on Remove TaxRate and Replace TaxRate update actions.
• [GraphQL API] Changed the TaxRate type:
  • Added the key field to the TaxRate type.
• [GraphQL API] Changed the TaxRateInput type:
  • Input field key was added to TaxRateInput type
• [GraphQL API] Changed the TaxRateDraft type:
  • Input field key was added to TaxRateDraft type
• [GraphQL API] Changed the TaxCategoryRemoveTaxRate type:
  • Input field taxRateKey was added to TaxCategoryRemoveTaxRate type
  • TaxCategoryRemoveTaxRate.taxRateId input field type changed from String! to String
• [GraphQL API] Changed the TaxCategoryReplaceTaxRate type:
  • TaxCategoryReplaceTaxRate.taxRateId input field type changed from String! to String
  • Input field taxRateKey was added to TaxCategoryReplaceTaxRate type

We fixed the Reference Expansion input types on Business Unit Messages to provide a consistent experience when working with the GraphQL API. Additionally, we updated the type BusinessUnitConfiguration to align it with the HTTP API. We have also made the roles field optional on AssociateDraft in the HTTP and GraphQL API to allow creating Associates without having to assign roles.

Changes:

• [API] Changed roles field to be optional on AssociateDraft.
• [GraphQL API] Changed the AssociateDraft type:
  • AssociateDraft.roles input field type changed from [SimpleAssociateRole!]! to [SimpleAssociateRole!]
• [GraphQL API] Added the following types to the GraphQL schema: BusinessUnitConfigurationStatus.
• [GraphQL API] Changed the BusinessUnitConfiguration type:
  • BusinessUnitConfiguration.myBusinessUnitStatusOnCreation field type changed from BusinessUnitStatus! to BusinessUnitConfigurationStatus!
• [GraphQL API] Changed the BusinessUnitStoreAdded type:
  • BusinessUnitStoreAdded.store field type changed from KeyReference! to Store!
  • Added the storeRef field to the BusinessUnitStoreAdded type.
• [GraphQL API] Changed the BusinessUnitStoresSet type:
  • BusinessUnitStoresSet.stores field type changed from [KeyReference!]! to [Store!]!
  • Added the storesRef field to the BusinessUnitStoresSet type.
• [GraphQL API] Changed the BusinessUnitStoreModeChanged type:
  • Added the oldStoresRef field to the BusinessUnitStoreModeChanged type.
  • Added the storesRef field to the BusinessUnitStoreModeChanged type.
  • BusinessUnitStoreModeChanged.stores field type changed from [KeyReference!] to [Store!]
  • BusinessUnitStoreModeChanged.oldStores field type changed from [KeyReference!] to [Store!]
• [GraphQL API] Changed the BusinessUnitParentChanged type:
  • Added the oldParentUnitRef field to the BusinessUnitParentChanged type.
  • Added the newParentUnitRef field to the BusinessUnitParentChanged type.
  • BusinessUnitParentChanged.newParentUnit field type changed from KeyReference to BusinessUnit
  • BusinessUnitParentChanged.oldParentUnit field type changed from KeyReference to BusinessUnit
• [GraphQL API] Changed the ChangeProjectSettingsMyBusinessUnitStatusOnCreation type:
  • ChangeProjectSettingsMyBusinessUnitStatusOnCreation.status input field type changed from BusinessUnitStatus! to BusinessUnitConfigurationStatus!
• [GraphQL API] Changed the BusinessUnitStoreRemoved type:
  • BusinessUnitStoreRemoved.store field type changed from KeyReference! to Store!
  • Added the storeRef field to the BusinessUnitStoreRemoved type.

We introduced the Individual Exclusion Product Selection type that lets you model the availability of your Products in different Stores by excluding individual Products explicitly. Before, we supported the Individual type only in which you include individual Products explicitly. We also added Messages triggered when Product Selections of that new type are created, deleted, or updated.

Changes:

• [API] Added individualExclusion value to ProductSelectionTypeEnum.

• [API] Added IndividualExclusionProductSelectionType.

• [API] Added Exclude Product update action for Product Selections.

• [API] Added Set Variant Exclusion update action for Product Selections.

• [API] Added ProductSelectionProductExcluded and ProductSelectionVariantExclusionChanged Message.

• [GraphQL API] Added the following types to the GraphQL schema: ExcludeProductSelectionProduct, IndividualExclusionProductSelectionCreatedPayload, ProductSelectionProductExcluded, ProductSelectionType, ProductSelectionVariantExclusionChanged, ProductVariantExclusion, ProductVariantExclusionDraft, SetProductSelectionVariantExclusion.

• [GraphQL API] Added the type field to the ProductSelection type.

• [GraphQL API] Added the type input field to the CreateProductSelectionDraft type.

• [GraphQL API] Added the excludeProduct input field to ProductSelectionUpdateAction type.

• [GraphQL API] Added the setVariantExclusion input field to ProductSelectionUpdateAction type.

• [GraphQL API] Added the staged field to the ProductVariantDeleted type.

We changed the type for the state field in PaymentStatusDraft from Reference to ResourceIdentifier allowing you to reference a State by key when creating a new Payment. The HTTP API now behaves as documented, and we aligned the GraphQL API with this behavior also.

Changes:

• [GraphQL API] Changed the PaymentStatusInput.state input field type from ReferenceInput to ResourceIdentifierInput.

We renamed the types of Product Variant Selection from Inclusion to IncludeOnly and from Exclusion to IncludeAllExcept. Based on our feedback, the new names describe the semantics of these types better and make their purpose clearer.

The previous types have now been deprecated and will be migrated to the new types automatically on 30 June 2023 without any disruption of services.

Changes:

• [API] Added includeOnly and includeAllExcept values to the type field of Product Variant Selection.
• [API] Deprecated inclusion and exclusion values on the type field of Product Variant Selection.
• [GraphQL API] Changed the ProductVariantSelectionDraft type:
  • Added input field includeOnly and includeAllExcept to ProductVariantSelectionDraft type.
  • Deprecated input field inclusion and exclusion on ProductVariantSelectionDraft type.
• [GraphQL API] Added the following types to the GraphQL schema: ProductVariantSelectionIncludeOnly, ProductVariantSelectionIncludeAllExcept.
• [GraphQL API] Deprecated the following types on the GraphQL schema: ProductVariantSelectionExclusion, ProductVariantSelectionInclusion.

We are announcing that external OAuth is out of beta. During the beta phase, we collected feedback to ensure a reliable, stable, and performant feature.

The status of the following functionality has changed to general availability:

• Requesting an access token using an External OAuth server.
• Configuring external OAuth through Project settings using the Set ExternelOAuth update action.

We have enhanced API Extensions to support Cloud Functions natively.

Using the GoogleCloudFunctionDestination you can directly invoke Cloud Functions without providing authorization headers or having to use intermediate gateways.

The new destination uses the permissions granted through Identity and Access Management (IAM) of Google Cloud Platform projects. Visit the API Extensions reference to learn more about using IAM-authorized Cloud Functions as destinations for your API Extensions.

Changes:

• [API] Added GoogleCloudFunctionDestination to API Extensions.
• [GraphQL API] Added the following types to the GraphQL schema: GoogleCloudFunctionDestination, GoogleCloudFunctionDestinationInput.
• [GraphQL API] Changed the ExtensionDestinationInput type:
  • Input field GoogleCloudFunction was added to ExtensionDestinationInput type.

Quote Requests, Staged Quotes, and Quotes now support Reference Expansion on Business Unit in the GraphQL API.

Changes:

• [GraphQL API] Changed the StagedQuote type:
  • Added the businessUnitRef field to the StagedQuote type.
  • StagedQuote.businessUnit field type changed from KeyReference to BusinessUnit
• [GraphQL API] Changed the Quote type:
  • Added the businessUnitRef field to the Quote type.
  • Quote.businessUnit field type changed from KeyReference to BusinessUnit
• [GraphQL API] Changed the QuoteRequest type:
  • Added the businessUnitRef field to the QuoteRequest type.
  • QuoteRequest.businessUnit field type changed from KeyReference to BusinessUnit

To align with the PriceDraft object in the HTTP API we added the discounted field to the ProductPriceDataInput type in the GraphQL schema. Furthermore, we fixed the field type for the DiscountedProductPriceValueInput type in the GraphQL API.

Changes:

• [GraphQL API] Added discounted field to the ProductPriceDataInput type.
• [GraphQL API] Changed the DiscountedProductPriceValueInput.discount field type from ReferenceInput! to ResourceIdentifierInput!.

We added the oldValue field to the Standalone Price Value Changed Message that contains the StandalonePrice value as it was before the change. You can now see how much the value of your updated Standalone Price has changed by comparing the Message fields value and oldValue.

Changes:

• [API] Added field oldValue to Standalone Price Value Changed Message.
• [GraphQL API] Changed the StandalonePriceValueChanged type:
  • Added the oldValue field to the StandalonePriceValueChanged type.

We are announcing that CloudEventsFormat for Subscription destinations is out of beta.

In the process of bringing the feature to general availability status, we ensured that the payload format is in accordance with the 1.0.2 specification. This will ensure consistency when using CloudEvents across different services.

Visit the API reference to learn more about enabling CloudEvents for your Subscription destinations.

To align with the HTTP API, multiple Shipping Methods are now supported on Carts and Orders in the GraphQL API.

Changes:

• [GraphQL API] Added the following types to the GraphQL schema: AddCartCustomShippingMethod, AddCartShippingMethod, CustomShippingDraft, MethodTaxRate, RemoveCartShippingMethod, Shipping, ShippingDraft, ShippingMode.
• [GraphQL API] Changed the MyCartDraft type:
  • Input field shippingMode was added to MyCartDraft type
  • Input field customShipping was added to MyCartDraft type
  • Input field shipping was added to MyCartDraft type
• [GraphQL API] Changed the CartDraft type:
  • Input field customShipping was added to CartDraft type
  • Input field shipping was added to CartDraft type
  • Input field shippingMode was added to CartDraft type
• [GraphQL API] Changed the CartUpdateAction type:
  • Input field addCustomShippingMethod was added to CartUpdateAction type
  • Input field removeShippingMethod was added to CartUpdateAction type
  • Input field addShippingMethod was added to CartUpdateAction type
• [GraphQL API] Changed the Cart type:
  • Added the taxedShippingPrice field to the Cart type.
  • Added the shipping field to the Cart type.
  • Added the shippingMode field to the Cart type.
• [GraphQL API] Changed the Order type:
  • Added the taxedShippingPrice field to the Order type.
  • Added the shipping field to the Order type.
  • Added the shippingMode field to the Order type.
• [GraphQL API] Changed the LineItem type:
  • Added the perMethodTaxRate field to the LineItem type.
  • Added the taxedPricePortions field to the LineItem type.
• [GraphQL API] Changed the ShippingTargetDraft type:
  • Added the shippingMethodKey field to the ShippingTargetDraft type.

With the new purchaseOrderNumber field, Buyers are now able to track their purchase throughout the order creation process with their Purchase Order Number. To support B2B scenarios, this new field is also supported on all types related to Quotes.

Changes:

• [API] Added optional field purchaseOrderNumber to OrderFromCartDraft, OrderImportDraft, QuoteRequestDraft, QuoteRequest, StagedQuote, Quote, Order.
• [API] Added setPurchaseOrderNumber update action to Orders and Order Edits APIs.
• [API] Added PurchaseOrderNumberSet message.
• [GraphQL API] Changed the QuoteRequestDraft type:
  • Input field purchaseOrderNumber was added to QuoteRequestDraft type
• [GraphQL API] Changed the OrderCartCommand type:
  • Input field purchaseOrderNumber was added to OrderCartCommand type
• [GraphQL API] Changed the ImportOrderDraft type:
  • Input field purchaseOrderNumber was added to ImportOrderDraft type
• [GraphQL API] Changed the StagedOrderUpdateAction type:
  • Input field setPurchaseOrderNumber was added to StagedOrderUpdateAction type
• [GraphQL API] Changed the StagedQuote type:
  • Added the purchaseOrderNumber field to the StagedQuote type.
• [GraphQL API] Changed the OrderUpdateAction type:
  • Input field setPurchaseOrderNumber was added to OrderUpdateAction type
• [GraphQL API] Changed the Quote type:
  • Added the purchaseOrderNumber field to the Quote type.
• [GraphQL API] Changed the Order type:
  • Added the purchaseOrderNumber field to the Order type.
• [GraphQL API] Changed the QuoteRequest type:
  • Added the purchaseOrderNumber field to the QuoteRequest type.

We introduced a background service that reflects any change for SKUs performed on Products in all corresponding SKUs on ProductVariantSelections. This service keeps SKUs in ProductSelectionAssignments up to date with eventual consistency.

We deprecated IronMQ as a Subscription destination in 2018 due to low adoption. The feature is now completely removed and newer versions of our SDKs no longer support it.

You can now retrieve Shipping Methods that match a given Cart and Location. The new endpoint is especially useful in cases where a Cart must match Shipping Method predicates, but does not have its shippingAddress defined. For example, this allows you to retrieve applicable Shipping Methods for a Cart with multiple Shipping Methods.

Changes:

• [API] added Get ShippingMethods for a Cart and Location endpoint.

AWSLambdaDestination now accepts Lambda function aliases. This allows you to optimize your development and deployment workflows by pointing to a specific version of a Lambda in your API Extension.

Changes:

• [API] The arn field of AWSLambdaDestination now accepts AWS Lambda function aliases.

We have added the option to freeze Carts during the purchasing journey of your Customers. With this, usual price and discount updates are primarily not applied on frozen Carts. This new feature is useful if you want to prevent Carts from being modified by changes affecting prices until the order is placed. Inventory is not reserved by freezing a Cart.

Changes:

• [API] Added FreezeCart and UnfreezeCart update actions to Carts API.
• [API] Added Frozen field to CartState.
• [GraphQL API] Added the following types to the GraphQL schema: FreezeCart, UnfreezeCart.
• [GraphQL API] Added input fields freezeCart and unfreezeCart to the CartUpdateAction type.
• [GraphQL API] Added Frozen value to the CartState enum type.

To fully comply with the GraphQL response format, we have moved the code field under the extensions map as shown in this example.

From 15 January 2023, code will no longer be returned as a top-level field of the errors array, but under the extensions map.

As a part of the same initiative oriented towards complying with the GraphQL specification, we also removed support for non-standard variables. This change was announced on 4 October 2022 and took effect on 1 December 2022.

In addition to identifying Embedded Prices by their id, you can now use key as a user-defined unique identifier. By assigning a human-readable key to Embedded Prices, you have greater flexibility for referencing Embedded Prices.

The key field was already available for StandalonePrices and this allowed us to assess and confirm its usefulness. Implementing the key field in Embedded Prices ensures consistency in offerings for both Standalone Prices and Embedded Prices.

Update actions for setting the key value has also been added for both Embedded Prices and Standalone Prices, allowing you to efficiently update Price keys without needing to bulk import Prices with the updated price keys.

Changes:

• [API] Added keyfield to Price and PriceDraft.
• [API] Added Set Price Key update action.
• [API] Added Set Standalone Price Key update action.
• [API] Added the error code DuplicatePriceKey.
• [API] Added ProductPriceKeySet Message.
• [API] Added StandalonePriceKeySet Message.
• [GraphQL API] Changed the ProductPrice type:
  • Added the key field to the ProductPrice type.
• [GraphQL API] Changed the ProductPriceSearch type:
  • Added the key field to the ProductPriceSearch type.
• [GraphQL API] Changed the ProductPriceDataInput type:
  • Input field key was added to ProductPriceDataInput type
• [GraphQL API] Added the following types to the GraphQL schema: SetProductPriceKey, SetStandalonePriceKey, StandalonePriceKeySet, ProductPriceKeySet.
• [GraphQL API] Changed the ProductUpdateAction type:
  • Input field setPriceKey was added to ProductUpdateAction type
• [GraphQL API] Changed the StandalonePriceUpdateAction type:
  • Input field setKey was added to StandalonePriceUpdateAction type

Following the deprecation of the Missing Data API due to low adoption and usage, we have now removed all its endpoints and data types.

The API was an experimental project and removing it will help us focus our efforts toward developing more advanced machine learning features while prioritizing data quality.

We have made several improvements and changes to the Business Units functionality in GraphQL:

• Carts and Orders now support Reference Expansion on Business Unit.
• Added support for creating Carts that reference a Business Unit.
• Changed the naming of the type AssociateRole to free up the namespace for new functionality.

Changes:

• [GraphQL API] Changed the Cart type:
  • Added the businessUnitRef field to the Cart type.
  • Cart.businessUnit field type changed from KeyReference to BusinessUnit
• [GraphQL API] Changed the Order type:
  • Order.businessUnit field type changed from KeyReference to BusinessUnit
  • Added the businessUnitRef field to the Order type.
• [GraphQL API] Changed the CartDraft type:
  • Input field businessUnit was added to CartDraft type
• [GraphQL API] Changed the MyCartDraft type:
  • Input field businessUnit was added to MyCartDraft type
• [GraphQL API] Added the following types to the GraphQL schema: SimpleAssociateRole
• [GraphQL API] Removed the following types from the GraphQL schema: AssociateRole.
• [GraphQL API] Changed the Associate type:
  • Associate.roles field type changed from [AssociateRole!]! to [SimpleAssociateRole!]!
• [GraphQL API] Changed the AssociateDraft type:
  • AssociateDraft.roles input field type changed from [AssociateRole!]! to [SimpleAssociateRole!]!

You can now subscribe to Messages about adding, changing, setting, and removing Embedded Prices on Products, as well as setting the PriceMode on Products.

Changes:

• [API] added ProductPriceAdded Message.
• [API] added ProductPriceChanged Message.
• [API] added ProductPricesSet Message.
• [API] added ProductPriceRemoved Message.
• [API] added ProductPriceModeSet Message.
• [GraphQL API] Added the following types to the GraphQL schema: ProductPriceAdded, ProductPriceChanged, ProductPriceModeSet, ProductPriceRemoved, ProductPricesSet.

We have extended the abilities of Audit Log to include tracking of changes made on a Store's Product Selections. With this enhancement, all Product Selection-related Changes performed on Stores are tracked from now on and these Changes are now retrievable via API.

We understood there is a demand to retrieve the full information about the Channel and the Customer Group on Standalone Prices instead of just the reference to those via the GraphQL API. Before, additional API calls were needed to retrieve the respective information, from now on just one query is sufficient for this use case.

Changes:

• [GraphQL API] Changed the StandalonePrice type:
  • Added the channel field to the StandalonePrice type.
  • Added the customerGroup field to the StandalonePrice type.

We have released countries in Stores in public beta. You can now define countries on Stores and filter prices by country in Product Projections and Cart/Order/Shopping List Line Items.

Changes:

• [API] Added type StoreCountry to Stores.
• [API] Added countries field to Store and StoreDraft.
• [API] Added Add Country, Remove Country, and Set Countries update actions to Stores.
• [API] Added optional countries field to StoreCreated Message.
• [API] Added StoreCountriesChanged Message.
• [API] Added the error code CountryNotConfiguredInStore.
• [GraphQL API] Added the following types to the GraphQL schema: AddStoreCountry, RemoveStoreCountry, SetStoreCountries, StoreCountriesChanged, StoreCountry, StoreCountryInput.
• [GraphQL API] Changed the StoreUpdateAction type:
  • Input field addCountry was added to StoreUpdateAction type
  • Input field setCountries was added to StoreUpdateAction type
  • Input field removeCountry was added to StoreUpdateAction type
• [GraphQL API] Changed the CreateStore type:
  • Input field countries was added to CreateStore type
• [GraphQL API] Changed the StoreCreated type:
  • Added the countries field to the StoreCreated type.
• [GraphQL API] Changed the Store type:
  • Added the countries field to the Store type.

We made a correction to the ChangeQuoteState type in the GraphQL API. The type of the input field quoteState was incorrectly marked as MyQuoteState instead of QuoteState. This caused certain QuoteStates, for example, the Withdrawn state, to be unavailable through the GraphQL API. With this correction in place, the ChangeQuoteState type now supports all QuoteStates in GraphQL.

Changes:

• [GraphQL API] Changed the ChangeQuoteState type:
  • ChangeQuoteState.quoteState input field type changed from MyQuoteState! to QuoteState!

You can now organize related Attributes together into Attributes Groups and ease your product data enhancement workflows.

Changes:

• [API] Added Attribute Groups API.
• [API] Added the view_attribute_groups and manage_attribute_groups OAuth scopes.
• [GraphQL API] Added the following types to the GraphQL schema: AddAttributeGroupAttribute, AttributeGroup, AttributeGroupDraft, AttributeGroupQueryResult, AttributeGroupUpdateAction, ChangeAttributeGroupName, RemoveAttributeGroupAttribute, SetAttributeGroupAttributes, SetAttributeGroupDescription, SetAttributeGroupKey, AttributeReference.

You can now enable automatic state transitions between various pre-defined states for Quote Requests, Staged Quotes, and Quotes. In particular:

• When creating a Staged Quote you can transition the referenced Quote Request to the Accepted state using the quoteRequestStateToAccepted field on StagedQuoteDraft.
• When creating a Quote you can transition the referenced Staged Quote to the Sent state using the stagedQuoteStateToSent field on QuoteDraft.
• When creating an Order you can transition the referenced Quote to the Accepted state using the quoteStateToAccepted field on OrderFromQuoteDraft. The same functionality is available on the My Order endpoint using MyOrderFromQuoteDraft.

This simplifies the management of Quote states by eliminating the need for an additional API call to transition the state.

We have added support for IAM-based authentication for SNS and SQS Destinations. The new field authenticationMode is available on SQSDestination and SNSDestination and defines the mode of authentication. IAM-based authentication allows the Subscriptions API to send messages to a queue or publish to a topic, without explicitly providing credentials in the form of an accessKey and accessSecret. This simplifies key management for customers who maintain hundreds of queues and rotate credentials regularly. By providing permissions to an IAM user instead, the access needs to be set up once per topic and requires no additional key management. For backwards compatibility, the authenticationMode field is set to Credentials by default.

Changes:

• [API] Added fields authenticationMode to SQSDestination and SNSDestination.
• [API] Added AwsAuthenticationMode.
• [GraphQL API] Added the following types to the GraphQL schema: AwsAuthenticationMode.
• [GraphQL API] Changed the SQSDestinationInput type:
  • SQSDestinationInput.accessSecret input field type changed from String! to String
  • SQSDestinationInput.accessKey input field type changed from String! to String
  • Input field authenticationMode was added to SQSDestinationInput type
• [GraphQL API] Changed the SNSDestinationInput type:
  • SNSDestinationInput.accessSecret input field type changed from String! to String
  • SNSDestinationInput.accessKey input field type changed from String! to String
  • Input field authenticationMode was added to SNSDestinationInput type
• [GraphQL API] Changed the SQSDestination type:
  • SQSDestination.accessSecret field type changed from String! to String
  • Added the authenticationMode field to the SQSDestination type.
  • SQSDestination.accessKey field type changed from String! to String
• [GraphQL API] Changed the SNSDestination type:
  • SNSDestination.accessSecret field type changed from String! to String
  • SNSDestination.accessKey field type changed from String! to String
  • Added the authenticationMode field to the SNSDestination type.

The My Quotes API provides access to Quotes scoped to a specific user. Using the My Quotes endpoints, Buyers can view and update Quotes that they have access to. By updating the state of the Quote, Buyers can indicate whether they accept or decline a given Quote.

Changes:

• [API] Added My Quotes API.
• [API] Added MyOrderFromQuoteDraft to My Orders.
• [API] Added Create Order from Quote endpoint to My Orders.
• [GraphQL API] Added the following types to the GraphQL schema: ChangeMyQuoteMyQuoteState, MyQuoteState, MyQuoteUpdateAction, OrderMyQuoteCommand
• [GraphQL API] Changed the Me type:
  • Added the quote field to the Me type.
  • Added the quotes field to the Me type.
• [GraphQL API] Changed the Mutation type:
  • Added the updateMyQuote field to the Mutation type.

We have released Business Units in public beta. This new feature allows you to model companies and their divisions in Composable Commerce. You can assign Customers to Business Units to manage Carts, Orders, and Quotes on behalf of companies. With the help of Stores, Business Units can support company-specific products and pricing. When linked to a Business Unit, Carts, Orders, and Quotes will validate a Customer's role within the Business Unit. This feature is part of Composable Commerce for B2B and will be subject to additional terms and pricing.

To be fully compliant with the GraphQL specification for serving over HTTP, we will be accepting GraphQL variables only as a JSON objects from 1 December 2022.

From then on, we will no longer accept variables to be passed as String containing a JSON object.

Please find an example on how to use GraphQL variables on our GraphQL API page.

To align with the HTTP API we released following Carts- and Quotes-related features in the GraphQL API.

Changes:

• [GraphQL API] Added the inventoryMode field to the LineItem type.
• [GraphQL API] Added Enum value Quote to CartOrigin type .
• [GraphQL API] Added the sellerComment field to the StagedQuote type.

You can now view Product Selections limits for Stores in the GraphQL API.

Changes:

• [GraphQL API] Changed the StoreLimitsProjection type:
  • Added the productSelections field to the StoreLimitsProjection type.

We understood from our customers that there is a need to store more than 100 Line Items in a Shopping List and after analyzing the performance impact of higher numbers of Line Items we can now raise this limit to 250. This limit can be increased per Project after we reviewed the performance impact. Find more details in the documentation.

You can now subscribe to Messages about additions, removals, or overwrites of inventory supply Channels on Stores.

Changes:

• [API] Added StoreSupplyChannelsChanged Message.
• [GraphQL API] Added the following type to the GraphQL schema: StoreSupplyChannelsChanged.

With the new ShipmentState, Delivered, you can now track the orders that are received by the customer.

Previously, this was only possible by using a custom state on the Order, or on the Line Item if they have more shipments per Order.

With the new 'active' field on Standalone Prices you can activate or deactivate individual Standalone Prices. This allows you to make changes or edits to your prices without them being visible to your customers. When a Standalone Price is not active, it is not considered during price selection. All existing Standalone Prices received an active status.

Due to low adoption, we have deprecated all endpoints and data types of the Missing Data API. This API was an early, experimental project that did not find wide adoption and steady usage. Data quality remains a key priority for us and deprecating the Missing Data API will help focus our development efforts toward new, more advanced machine learning features.

We continue to maintain the Missing Data API until 09 December 2022, at which point the API will be completely removed. From now on, requests to deprecated endpoints will yield a response with the X-DEPRECATION-NOTICE HTTP header.

You can now subscribe to Messages about name changes on Stores.

Changes:

• [API] Added StoreNameSet Message.
• [GraphQL API] Added the following type to the GraphQL schema: StoreNameSet.

After successful experiences with Projects having up to 50,000 Stores, we have now raised this limit to 300,000. With this, we provide better support for B2B scenarios now in which separate product catalogs with pricing for business units of companies are required.

This limit can be increased per Project after we reviewed the performance impact. See also documentation.

Direct Discounts on Carts are now supported in the GraphQL API. The feature has been released in beta in the HTTP API on 30 June 2022.

Changes:

• [GraphQL API] Added the following types to the GraphQL schema: DirectDiscount, DirectDiscountDraft, DirectDiscountDraftOutput, SetCartDirectDiscounts, SetStagedOrderDirectDiscounts, SetStagedOrderDirectDiscountsOutput.
• [GraphQL API] Changed the MyCartUpdateAction type:
  • Input field setDirectDiscounts was added to MyCartUpdateAction type
• [GraphQL API] Changed the Quote type:
  • Added the directDiscounts field to the Quote type.
• [GraphQL API] Changed the QuoteRequest type:
  • Added the directDiscounts field to the QuoteRequest type.
• [GraphQL API] Changed the CartUpdateAction type:
  • Input field setDirectDiscounts was added to CartUpdateAction type
• [GraphQL API] Changed the Cart type:
  • Added the directDiscounts field to the Cart type.
• [GraphQL API] Changed the StagedOrderUpdateAction type:
  • Input field setDirectDiscounts was added to StagedOrderUpdateAction type
• [GraphQL API] Changed the Order type:
  • Added the directDiscounts field to the Order type.

As announced previously in our long-term support plan for Composable Commerce SDKs, Version 1 (v1) of our PHP and DotNET Core SDKs are now deprecated effective today.

These SDKs will not receive any future updates to fix bugs or security vulnerabilities. If you are using one of these SDKs, you should migrate to PHP v2 or DotNET Core v2. You can find migration guides for both SDKs on their respective pages.

We fixed the GraphQL type for changing the Cart Discounts on Discount Codes to achieve alignment with the respective update action on the Discount Codes API. With this, you can now reference the CartDiscounts by user-defined key in addition to id also in the GraphQL API. Furthermore, we made the Channel-related fields optional in the Store Distribution Channels Changed Message.

You can now add multiple Shipping Methods to a Cart and Order. This is useful for cases where you want to have individual Shipping Methods for each Line Item ordered from a Cart.

A newly introduced shippingMode on Cart and Order controls whether Carts and Orders can have single or multiple Shipping Methods. The default ShippingMode is Single for backwards compatibility. For Carts and Orders with multiple Shipping Methods, all shipping-related information (such as address, rate, deliveries) are wrapped in a newly introduced Shipping object per Shipping Method. The Shipping object can also be extended with Custom Fields.

Additionally, you can add deliveries to Carts during Cart creation, which was previously only possible on Orders.

You can now subscribe to Messages about language changes on Stores.

Changes:

• [API] Added StoreLanguagesChanged Message.
• [GraphQL API] Added the following type to the GraphQL schema: StoreLanguagesChanged.

Buyers can now request to renegotiate a Quote provided by the Seller. Previously, Buyers only had the option to accept or reject a Quote. Renegotiation offers more flexibility and allows Buyers to ask for amendments to the Quote. Buyers can express additional details regarding their request in the form of a comment.

You can now set the price mode for a Custom Line Item when adding the Custom Line Item to a Cart.

Previously, new Custom Line Items had the Standard price mode set by default for backwards compatibilty. You could only change the price mode on an existing Custom Line Item with the Change CustomLineItem Price Mode update action.

Reference Expansion for Attributes of ProductProjectionsSearch is now supported in the GraphQL API.

We appreciate your feedback on this new in public beta feature. An example query can be found in our GraphQL API documentation.

Changes:

• [GraphQL API] Changed the RawProductSearchAttribute type:
  • Added the referencedResourceSet field to the RawProductSearchAttribute type.
  • Added the referencedResource field to the RawProductSearchAttribute type.

With Staged Standalone Prices, you can make changes or edits to Standalone Prices without them being visible to your customers. This allows you to prepare and test your changes before applying them with confidence when they are ready. Staged Standalone Prices support DiscountedPrice which means that you can assess how a given Product Discount would affect your Prices before making them live. Staged Standalone Prices is currently available in public beta.

Changes:

• [API] Added StagedStandalonePrice to Standalone Prices API.
• [API] Added field staged to StandalonePrice.
• [API] Added applyStagedChanges update action to StandalonePrice.
• [API] Added StandalonePriceStagedChangesApplied Message.
• [API] Added field staged to StandalonePriceValueChanged Message
• [GraphQL API] Added the following types to the GraphQL schema: ApplyStagedChanges, StagedStandalonePrice, StandalonePriceStagedChangesApplied.
• [GraphQL API] Changed the StandalonePriceUpdateAction type:
  • Input field applyStagedChanges was added to StandalonePriceUpdateAction type
• [GraphQL API] Changed the ChangeStandalonePriceValue type:
  • Input field staged was added to ChangeStandalonePriceValue type
• [GraphQL API] Changed the StandalonePrice type:
  • Added the staged field to the StandalonePrice type.
• [GraphQL API] Changed the StandalonePriceValueChanged type:
  • Added the staged field to the StandalonePriceValueChanged type.

You can now set States reflecting custom business logic on QuoteRequests, StagedQuotes, and Quotes.

In our June 14, 2022 release we incorrectly labeled some closed beta features as available in public beta and introduced them in our GraphQL schema file.

We made a correction to the schema file and the original release note to remove the closed beta features listed below. This does not change the availability of the features. They remain discoverable through introspection and are intended for selected customers taking part in closed beta programs.

If you are interested in evaluating a closed beta feature, please reach out to your contact at commercetools.

You can now extend the Quotes APIs with your custom business logic using API Extensions. You can trigger Extensions on create and update requests to Quote Requests, Staged Quotes, and Quotes. This allows you to integrate with other services seamlessly and cover custom B2B use cases by modifying the default behavior of the APIs.

Changes:

• [API] Added quote-request, staged-quote, and quote to ExtensionResourceTypeId.

The inventory mode can now be configured for individual LineItems. The Cart/Order-level inventory mode remains, but can be overridden on a per-line-item basis. For example, in a Cart with two Line Items, you can now give Line Item 1 an inventory mode that is different from the inventory mode for Line Item 2. Before this release, it was only possible to specify one inventory mode valid for all Line Items in the Cart or Order.

Changes:

• [API] Added optional inventoryMode field to LineItem, LineItemDraft, and LineItemImportDraft.
• [GraphQL API] Changed the LineItemDraftOutput type:
  • Added the inventoryMode field to the LineItemDraftOutput type.
• [GraphQL API] Changed the AddStagedOrderLineItem type:
  • Input field inventoryMode was added to AddStagedOrderLineItem type
• [GraphQL API] Changed the AddCartLineItem type:
  • Input field inventoryMode was added to AddCartLineItem type
• [GraphQL API] Changed the LineItemDraft type:
  • Input field inventoryMode was added to LineItemDraft type

You can now set a price mode on a CustomLineItem that controls whether Cart Discounts should be applied to them by Composable Commerce or not. Use this if you want to control application of Cart Discounts for each Custom Line Item in the Cart individually. For backwards compatibility, Standard is the default price mode for newly created Custom Line Items, that allows application of Cart Discounts. For cases where Cart Discounts should not be considered on a Custom Line Item, you can change its price mode to External via new update action. You can still overwrite the price for a Custom Line Item via Change CustomLineItem Money update action.

Changes:

• [API] Added field priceMode to CustomLineItem.
• [API] Added Change CustomLineItem Price Mode update action to Carts.
• [GraphQL API] Added the following types to the GraphQL schema: ChangeCartCustomLineItemPriceMode, CustomLineItemPriceMode.
• [GraphQL API] Changed the CartUpdateAction type:
  • Input field changeCustomLineItemPriceMode was added to CartUpdateAction type
• [GraphQL API] Changed the CustomLineItem type:
  • Added the priceMode field to the CustomLineItem type.
• [GraphQL API] Changed the TypeDefinition type:
  • TypeDefinition type description is changed

We have extended the capabilities of Audit Log to include the tracking of changes made on Quotes, Quote Requests, and Staged Quotes. With this enhancement, all Changes performed on Quotes, Quotes Requests and Staged Quotes are tracked from now on and these Changes are now retrievable via API.

Changes:

• [API] Added scopes view_quotes:{projectKey}, view_quotes:{projectKey}, and view_quotes:{projectKey}.
• [API] Added quote, quote-request, and staged-quote to ChangeHistoryResourceType.
• [API] Added ChangeQuoteRequestStateChange, ChangeQuoteStateChange, ChangeStagedQuoteStateChange, SetSellerCommentChange, and SetValidToChange.
• [API] Added StagedQuoteLabel, QuoteRequestLabel, QuoteLabel, and StagedQuoteLabel.
• [GraphQL API] Added the following types to the graphQL schema: QuoteRequestChangeInput, QuoteChangeInput and StagedQuoteChangeInput.
• [GraphQL API] Added QuoteRequestLabel, QuoteLabel, and StagedQuoteLabel type.
• [GraphQL API] Added queries quoteRequest and quoteRequests.
• [GraphQL API] Added queries quote and quotes.
• [GraphQL API] Added queries stagedQuote and stagedQuotes.
• [GraphQL API] Added QuoteRequest, Quote, and StagedQuote to the ResourceType enum.

You can now subscribe to Messages about additions, removals, or overwrites of product distribution Channels on Stores.

Changes:

• [API] Added StoreDistributionChannelsChanged Message.
• [GraphQL API] Added the following type to the GraphQL schema: StoreDistributionChannelsChanged.

You can now create an Order by import using the GraphQL API.

Changes:

• [GraphQL API] Added the following types to the GraphQL schema: CustomLineItemImportDraft, DeliveryDraft, DiscountedLineItemPriceDraft, ImportOrderDraft, LineItemImportDraft, ParcelDraft, ProductVariantImportDraft, ShippingInfoImportDraft, TaxRateInput, TaxedPriceDraft.
• [GraphQL API] Changed the Mutation type:
  • Added the importOrder field to the Mutation type.

You can now check if a Product Type exists using its id, key or a query predicate. These methods are useful if you are only interested in the existence of a certain Product Type without the need of fetching its information.

• [API] Added HEAD methods for Product Types by ID, by Key, and by Query Predicate.

We have extended the capabilities of Audit Log to include the tracking of changes made on Product Selections. With this enhancement, all Changes performed on Product Selections are tracked from now on and these Changes are now retrievable via API.

Changes:

• [API] Added the view_product_selections:{projectKey} scope.
• [API] Added product-selection to ChangeHistoryResourceType.
• [API] Added AddProductChange.
• [API] Added RemoveProductChange.
• [API] Added SetProductCountChange.
• [GraphQL API] Added the following types to the graphQL schema: ProductSelectionChangeInput.
• [GraphQL API] Added queries productSelection and productSelections.
• [GraphQL API] Added ProductSelection to the ResourceType enum.

We have released Quotes in public beta. This new feature allows you to negotiate quote requests for your products with your customers. The negotiation process involves utilizing several APIs that we introduced with this feature, allowing you to control each step of the intended workflow of the negotiation. All the introduced resources, such as Quote Request, Staged Quote, and Quote can be extended with Custom Fields. The discounts applied on a specific Quote, can be utilized by the newly added DirectDiscount. After successful negotiation, the Order can be created right from the Quote.

Changes:

• [API] Added Quote Requests and My Quote Requests APIs.
• [API] Added Staged Quotes API.
• [API] Added Quotes API.
• [API] Added QuoteRequestCreated, QuoteRequestStateChanged, and QuoteRequestDeleted Messages.
• [API] Added StagedQuoteCreated, StagedQuoteStateChanged, StagedQuoteValidToSet, StagedQuoteSellerCommentSet, and StagedQuoteDeleted Messages.
• [API] Added QuoteCreated, QuoteStateChanged, and QuoteDeleted Messages.
• [API] Added Quote to CartOrigin.
• [API] Added DirectDiscount and DirectDiscountDraft to Carts API.
• [API] Added directDiscounts field to Cart and Order.
• [API] Added setDirectDiscounts update action to Carts and Orders via OrderEdit.
• [API] Added OrderFromQuoteDraft and Create Order from Quote endpoint to Orders API.
• [API] Added quote field to Order.
• [API] Added OAuth scopes manage_quote_requests, view_quote_requests, manage_my_quote_requests, manage_staged_quotes, view_staged_quotes, manage_quotes, and view_quotes.
• [GraphQL API] Added the following types to the GraphQL schema: CancelQuoteRequest, ChangeMyQuoteMyQuoteState, ChangeQuoteRequestState, ChangeQuoteState, ChangeStagedQuoteState, MyQuoteRequestDraft, MyQuoteRequestUpdateAction, MyQuoteState, MyQuoteUpdateAction, OrderMyQuoteCommand, OrderQuoteCommand, Quote, QuoteDraft, QuoteQueryResult, QuoteRequest, QuoteRequestDraft, QuoteRequestQueryResult, QuoteRequestState, QuoteRequestUpdateAction, QuoteState, QuoteUpdateAction, SetMyQuoteRequestCustomField, SetMyQuoteRequestCustomType, SetQuoteCustomField, SetQuoteCustomType, SetQuoteRequestCustomField, SetQuoteRequestCustomType, SetStagedQuoteCustomField, SetStagedQuoteCustomType, SetStagedQuoteSellerComment, SetStagedQuoteValidTo, StagedQuote, StagedQuoteDraft, StagedQuoteQueryResult, StagedQuoteState, StagedQuoteUpdateAction.

You can now include or exclude particular Product Variants in/from a Product Selection. Formerly it was only possible to add Products as a whole to a Product Selection meaning that all existing Product Variants of the Product are included.

Changes:

• [API] You can now specify a Product Variant Selection when you Add a Product to the Product Selection.
• [API] You can now specify a Product Variant Selection for an existing Product in the Product Selection by the new Set Variant Selection update action.
• [API] When you query a Product Selection for Products assigned to a Product Selection the response now also contains Product Variant Selections.
• [API] When you query for Products available in a Store through active Product Selections the response now also contains Product Variant Selections.
• [API] When you Get Product Projection in Store by ID or by Key you can now project by Product Selection assignments for Product Variants.
• [API] Added variantSelection field to ProductSelectionProductAdded Message.
• [API] Added ProductSelectionVariantSelectionChanged Message.
• [API] Added ProductAssignmentMissing and ProductPresentWithDifferentVariantSelection errors.
• [GraphQL API] Added the following types to the GraphQL schema: ProductSelectionVariantSelectionChanged, ProductVariantSelection, ProductVariantSelectionDraft, ProductVariantSelectionExclusion, ProductVariantSelectionInclusion, SetProductSelectionVariantSelection.
• [GraphQL API] Changed the ProductOfSelection type:
  • Added the variantSelection field to the ProductOfSelection type.
• [GraphQL API] Changed the SelectionOfProduct type:
  • Added the variantSelection field to the SelectionOfProduct type.
• [GraphQL API] Changed the ProductSelectionUpdateAction type:
  • Input field setVariantSelection was added to ProductSelectionUpdateAction type
• [GraphQL API] Changed the AddProductSelectionProduct type:
  • Input field variantSelection was added to AddProductSelectionProduct type
• [GraphQL API] Changed the ProductSelectionProductAdded type:
  • Added the variantSelection field to the ProductSelectionProductAdded type.

After collecting feedback during the beta phase, we have moved Standalone Prices out of beta. The status of the following features has been changed to general availability:

• Querying and managing Standalone Prices through the Standalone Prices API
• Adding Custom Fields on Standalone Prices
• Setting the priceMode on the Product

Read more on Standalone Prices and how to use them in the API reference.

The long-term support plan for the Java v1 SDK has been extended until the end of 2023. This provides additional time for users to migrate to Java v2 SDK.

Changes:

• [GraphQL API] Changed the AuthenticationMode type:
  • AuthenticationMode type description is changed
• [GraphQL API] Changed the StandalonePriceCustomField type:
  • StandalonePriceCustomField type description is changed
• [GraphQL API] Changed the ProductPrice type:
  • Added the key field to the ProductPrice type.
• [GraphQL API] Changed the RoundingMode type:
  • RoundingMode.HalfDown description changed
• [GraphQL API] Changed the ProductPriceSearch type:
  • Added the key field to the ProductPriceSearch type.
• [GraphQL API] Changed the Payment type:
  • Payment type description is changed
• [GraphQL API] Changed the SelectionOfProduct type:
  • Added the createdAt field to the SelectionOfProduct type.
• [GraphQL API] Changed the MyPayment type:
  • MyPayment type description is changed
• [GraphQL API] Changed the Query type:
  • Query.standalonePrices description is changed
  • Query.standalonePrice description is changed
• [GraphQL API] Changed the ProductPriceDataInput type:
  • Input field key was added to ProductPriceDataInput type
• [GraphQL API] Changed the Cart type:
  • Argument id was added to Cart.lineItems field
• [GraphQL API] Changed the PriceMode type:
  • PriceMode type description is changed
• [GraphQL API] Changed the StandalonePriceQueryResult type:
  • StandalonePriceQueryResult.exists description is changed
• [GraphQL API] Changed the TriggerInput type:
  • Input field condition was added to TriggerInput type
• [GraphQL API] Changed the Mutation type:
  • Mutation.replicateMyCart description is changed
• [GraphQL API] Changed the Order type:
  • Order type description is changed
  • Argument id was added to Order.lineItems field
• [GraphQL API] Changed the Trigger type:
  • Added the condition field to the Trigger type.
• [GraphQL API] Changed the StandalonePrice type:
  • StandalonePrice type description is changed

You can now set the discounted value of a Standalone Price via update action also. Before, it was only possible to set that value during creation of the Standalone Price.

Changes:

• [API] Added SetStandalonePriceDiscountedPrice update action to Standalone Prices.
• [API] Added StandalonePriceExternalDiscountSet Message.
• [GraphQL API] Added the following types to the GraphQL schema: SetStandalonePriceDiscountedPrice, StandalonePriceExternalDiscountSet.
• [GraphQL API] Changed the StandalonePriceUpdateAction type:
  • Input field setDiscountedPrice was added to StandalonePriceUpdateAction type

Conditional triggers on API Extensions allow you to specify the criteria under which a given Extension is triggered. By default, API Extensions are called on every create or update to the resource they are configured for. However, the new feature allows you to specify fine-grained predicates based on the resource's properties. Using conditional statements you can configure the API Extension to trigger only when your particular use case requires it. Conditional triggers are especially useful in cases where multiple brands or countries reside in a single project.

Changes:

• [API] Added condition field to ExtensionTrigger.
• [GraphQL API] Changed the TriggerInput type:
  • Input field condition was added to TriggerInput type
• [GraphQL API] Changed the Trigger type:
  • Added the condition field to the Trigger type.

You can now subscribe to Messages specific to Standalone Prices to get informed about their creation, deletion, or updates on them.

Changes:

• [API] added StandalonePriceCreated Message, StandalonePriceDeleted Message, StandalonePriceValueChanged Message, and StandalonePriceDiscountSet Message.
• [GraphQL API] Added the following types to the GraphQL schema: StandalonePriceCreated, StandalonePriceDeleted, StandalonePriceDiscountSet, StandalonePriceValueChanged.

The lastMessageSequenceNumber field is deprecated from Order, as it is an internal field that should not be used in customer logic. For processing Messages in the correct order, a message processor can continue to use the id field of the resource alongside the sequenceNumber of the Message.

Changes:

• [API] Removed lastMessageSequenceNumber from Order.
• [GraphQL API] Changed the Order type:
  • Field lastMessageSequenceNumber was deprecated in Order type.

The Standalone Prices feature provides an alternative way to store your product prices as standalone resources. In comparison to prices embedded inside the Product, this new approach allows increasing the limit of prices per ProductVariant from 100 to 50.000. It also brings a more flexible way to query and manage your prices, separately from your Products, which contributes to better query performance.

The feature allows you to manage and query Standalone Prices through the Standalone Prices API, and to associate them to a ProductVariant via SKU. Additionally, a new priceMode has been introduced on the Product that controls whether the Prices of the ProductVariants are embedded into the Product resource or stored separately as Standalone Prices.

Please note that currently it is not possible to use filters, facets, and sorting on Standalone Prices via the Product Projection Search endpoint.

Read more on Standalone Prices and how to use them in the API reference.

Changes:

• [API] Added Standalone Prices API.
• [API] Added view_standalone_prices and manage_standalone_prices OAuth scopes.
• [API] Added optional field priceMode to Product and ProductDraft.
• [API] Added Set PriceMode update action to Product.
• [API] Added DuplicateStandalonePriceScope and OverlappingStandalonePriceValidity 400 Bad Request errors specific to Standalone Prices.
• [GraphQL API] Added the following types to the GraphQL schema: ChangeStandalonePriceValue, CreateStandalonePrice, PriceMode, SetProductPriceMode, SetStandalonePriceCustomFields, StandalonePrice, StandalonePriceCustomField, StandalonePriceQueryResult, StandalonePriceUpdateAction.
• [GraphQL API] Changed the Query type:
  • Added the standalonePrice field to the Query type.
  • Added the standalonePrices field to the Query type.
• [GraphQL API] Changed the Mutation type:
  • Added the createStandalonePrice field to the Mutation type.
  • Added the deleteStandalonePrice field to the Mutation type.
  • Added the updateStandalonePrice field to the Mutation type.
• [GraphQL API] Changed the Product type:
  • Added the priceMode field to the Product type.
• [GraphQL API] Changed the ProductDraft type:
  • Input field priceMode was added to ProductDraft type
• [GraphQL API] Changed the ProductUpdateAction type:
  • Input field setPriceMode was added to ProductUpdateAction type

When creating an Order from a Cart, the Custom Fields in the OrderFromCartDraft now merge with the Custom Fields in the referenced Cart.

With this, you can enrich the Custom Fields that already exist on the Cart and store them in the Order with a single API call.

Changes:

• [API] The custom field on OrderFromCartDraft is now used for adding extra Custom Fields on Create Order from Cart.

Creating a new Cart by replicating an existing Cart or Order can be useful in case a Customer wants to cancel a recent order to make some changes, or if a previous order should be ordered again. This has been supported for Carts already, and now we added a replicatiion endpoint for My Carts also.

Changes:

• [API] Added Replicate My Cart endpoint.
• [API] Added ReplicaMyCartDraft.
• [GraphQL API] Changed the Mutation type:
  • Added the replicateMyCart field to the Mutation type.

You can now view and configure the deletion date of API Clients in the GraphQL API.

Changes:

• [GraphQL API] Changed the APIClientWithoutSecret type:
  • Added the deleteAt field to the APIClientWithoutSecret type.
• [GraphQL API] Changed the APIClientWithSecret type:
  • Added the deleteAt field to the APIClientWithSecret type.
• [GraphQL API] Changed the CreateApiClient type:
  • Input field deleteDaysAfterCreation was added to CreateApiClient type

The total tax amount on Cart, Order, LineItem, CustomLineItem, and ShippingInfo. Before, your application had to calculate that amount if you wanted to display it to your customers.

Changes:

• [API] Added optional totalTax field to TaxedPrice and TaxedItemPrice.
• [GraphQL API] Changed the TaxedPrice type:
  • Added the totalTax field to the TaxedPrice type.
  • Added the totalTax field to the TaxedItemPrice type.

Reference Expansion for Attributes of Products is now supported in the GraphQL API.

We appreciate your feedback on this new in public beta feature. An example query can be found in our GraphQL API documentation.

Changes:

• [GraphQL API] Changed the RawProductAttribute type:
  • Added the referencedResourceSet field to the RawProductAttribute type.
  • Added the referencedResource field to the RawProductAttribute type.

You can now add Custom Fields when you Create an Order from a Cart. With this, you can now store additional information, like payment reference, to your Order during checkout if required for your business logic.

Changes:

• [API] Added optional custom field to OrderFromCartDraft.
• [GraphQL API] Changed the OrderCartCommand type:
  • Added the custom field to OrderCartCommand type.

We have extended the abilities of Audit Log to include tracking of changes on Stores as well as on Store-related information on Customers, Orders, and Shopping Lists.

For supported resources, this enhancement will now scope Audit Log response data to the user's or API Client's Store permissions. All other resources will remain unaffected.

Changes:

• [API] Adds stores attribute to Record response.
• [API] Adds filter for store keys to all available endpoints.
• [GraphQL API] Adds stores attribute to ChangeHistory type.
• [GraphQL API] Adds filter for store keys to all queries for supported resources.

You can now set the PaymentInfo as well as a State to an Order via Order Import.

Changes:

• [API] Added optional field paymentInfo to OrderImportDraft.
• [API] Added optional field state to OrderImportDraft.

Reference Expansion for Custom Fields of CustomFieldReferenceType (as well as for the CustomFieldSetType of it) is now supported in the GraphQL API.
We appreciate your feedback on this new in public beta feature; for an example query, please refer to the respective section in the GraphQL API documentation.

Changes:

• [GraphQL API] Changed the RawCustomField type:
  • Added the referencedResourceSet field to the RawCustomField type.
  • Added the referencedResource field to the RawCustomField type.
• [GraphQL API] Changed the Cart type:
  • Cart object type now implements ReferenceExpandable interface
• [GraphQL API] Changed the CartDiscount type:
  • CartDiscount object type now implements ReferenceExpandable interface
• [GraphQL API] Changed the Category type:
  • Category object type now implements ReferenceExpandable interface
• [GraphQL API] Changed the Channel type:
  • Channel object type now implements ReferenceExpandable interface
• [GraphQL API] Changed the Customer type:
  • Customer object type now implements ReferenceExpandable interface
• [GraphQL API] Changed the CustomerGroup type:
  • CustomerGroup object type now implements ReferenceExpandable interface
• [GraphQL API] Changed the CustomObject type:
  • CustomObject object type now implements ReferenceExpandable interface
• [GraphQL API] Changed the DiscountCode type:
  • DiscountCode object type now implements ReferenceExpandable interface
• [GraphQL API] Changed the Extension type:
  • Extension object type now implements ReferenceExpandable interface
• [GraphQL API] Changed the InventoryEntry type:
  • InventoryEntry object type now implements ReferenceExpandable interface
• [GraphQL API] Changed the Message type:
  • Message object type now implements ReferenceExpandable interface
• [GraphQL API] Changed the Order type:
  • Order object type now implements ReferenceExpandable interface
• [GraphQL API] Changed the Product type:
  • Product object type now implements ReferenceExpandable interface
• [GraphQL API] Changed the ProductDiscount type:
  • ProductDiscount object type now implements ReferenceExpandable interface
• [GraphQL API] Changed the ProductTypeDefinition type:
  • ProductTypeDefinition object type now implements ReferenceExpandable interface
• [GraphQL API] Changed the Review type:
  • Review object type now implements ReferenceExpandable interface
• [GraphQL API] Changed the ShippingMethod type:
  • ShippingMethod object type now implements ReferenceExpandable interface
• [GraphQL API] Changed the ShoppingList type:
  • ShoppingList object type now implements ReferenceExpandable interface
• [GraphQL API] Changed the State type:
  • State object type now implements ReferenceExpandable interface
• [GraphQL API] Changed the Store type:
  • Store object type now implements ReferenceExpandable interface
• [GraphQL API] Changed the TaxCategory type:
  • TaxCategory object type now implements ReferenceExpandable interface
• [GraphQL API] Changed the TypeDefinition type:
  • TypeDefinition object type now implements ReferenceExpandable interface
• [GraphQL API] Changed the Zone type:
  • Zone object type now implements ReferenceExpandable interface

We introduced the AuthenticationMode that controls whether the password field is required for a Customer in public beta. The Password authentication mode is the default mode for backwards compatibility that requires to set a password for the Customer. For use cases where Customers are authenticated externally, you can now set the authenticationMode to ExternalAuth to create Customers without a password.

Changes:

• [API] Added authenticationMode field to Customer and CustomerDraft.
• [API] Changed password field to be optional on CustomerDraft when authenticationMode is set to ExternalAuth.
• [API] Removed password field from Customer when authenticationMode is set to ExternalAuth.
• [API] Added Set AuthenticationMode update action.
• [GraphQL API] Added the following types to the GraphQL schema: AuthenticationMode, SetCustomerAuthenticationMode.
• [GraphQL API] Changed the Customer type:
  • Customer.password field type changed from String! to String
  • Added the authenticationMode field to the Customer type.
• [GraphQL API] Changed the CustomerSignUpDraft type:
  • CustomerSignUpDraft.password input field type changed from String! to String
  • Input field authenticationMode was added to CustomerSignUpDraft type
• [GraphQL API] Changed the CustomerUpdateAction type:
  • Input field setAuthenticationMode was added to CustomerUpdateAction type
• [GraphQL API] Changed the CustomerSignMeUpDraft type:
  • CustomerSignMeUpDraft.password input field type changed from String! to String

InventoryEntry now supports the key field. You can now retrieve, update, and delete InventoryEntry by user-defined key.

Changes:

• [API] Added key field to InventoryEntry and InventoryEntryDraft.
• [API] Added Get, Update, and Delete by Key methods to InventoryEntry.
• [API] Added Set Key update action to InventoryEntry.
• [GraphQL API] Changed the Query type:
  • Query.inventoryEntry(id) type changed from String! to String
  • Query.inventoryEntry(id) description is changed
  • Argument key was added to Query.inventoryEntry field
• [GraphQL API] Changed the Mutation type:
  • Mutation.updateInventoryEntry(id) type changed from String! to String
  • Mutation.updateInventoryEntry(id) description is changed
  • Argument key was added to Mutation.updateInventoryEntry field
  • Mutation.deleteInventoryEntry(id) type changed from String! to String
  • Mutation.deleteInventoryEntry(id) description is changed
  • Argument key was added to Mutation.deleteInventoryEntry field

The messagePayloads field has been added to the PreviewSuccess OrderEdit result in our GraphQL API.

Changes:

• [GraphQL API] Added the following types to the GraphQL schema: OrderMessagePayload.
• [GraphQL API] Changed the OrderCustomLineItemQuantityChanged type:
  • OrderCustomLineItemQuantityChanged object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderShippingRateInputSet type:
  • OrderShippingRateInputSet object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderCustomLineItemRemoved type:
  • OrderCustomLineItemRemoved object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderBillingAddressSet type:
  • OrderBillingAddressSet object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the ParcelItemsUpdated type:
  • ParcelItemsUpdated object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderEditApplied type:
  • OrderEditApplied object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the DeliveryAdded type:
  • DeliveryAdded object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the PreviewSuccess type:
  • Added the messagePayloads field to the PreviewSuccess type.
• [GraphQL API] Changed the OrderPaymentStateChanged type:
  • OrderPaymentStateChanged object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the ReturnInfoSet type:
  • ReturnInfoSet object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderCustomerSet type:
  • OrderCustomerSet object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderDiscountCodeStateSet type:
  • OrderDiscountCodeStateSet object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderCustomerGroupSet type:
  • OrderCustomerGroupSet object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderLineItemDiscountSet type:
  • OrderLineItemDiscountSet object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderStateChanged type:
  • OrderStateChanged object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderLineItemAdded type:
  • OrderLineItemAdded object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderImported type:
  • OrderImported object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderCustomerEmailSet type:
  • OrderCustomerEmailSet object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderCustomLineItemDiscountSet type:
  • OrderCustomLineItemDiscountSet object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderDiscountCodeAdded type:
  • OrderDiscountCodeAdded object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the CustomLineItemStateTransition type:
  • CustomLineItemStateTransition object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderPaymentRemoved type:
  • OrderPaymentRemoved object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the ParcelTrackingDataUpdated type:
  • ParcelTrackingDataUpdated object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderDiscountCodeRemoved type:
  • OrderDiscountCodeRemoved object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the DeliveryRemoved type:
  • DeliveryRemoved object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderCreated type:
  • OrderCreated object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderLineItemRemoved type:
  • OrderLineItemRemoved object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the ParcelRemovedFromDelivery type:
  • ParcelRemovedFromDelivery object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderDeleted type:
  • OrderDeleted object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderStoreSet type:
  • OrderStoreSet object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the DeliveryItemsUpdated type:
  • DeliveryItemsUpdated object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the ReturnInfoAdded type:
  • ReturnInfoAdded object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderReturnShipmentStateChanged type:
  • OrderReturnShipmentStateChanged object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the ParcelMeasurementsUpdated type:
  • ParcelMeasurementsUpdated object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderStateTransition type:
  • OrderStateTransition object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the LineItemStateTransition type:
  • LineItemStateTransition object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderLineItemDistributionChannelSet type:
  • OrderLineItemDistributionChannelSet object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the ParcelAddedToDelivery type:
  • ParcelAddedToDelivery object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the DeliveryAddressSet type:
  • DeliveryAddressSet object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderCustomLineItemAdded type:
  • OrderCustomLineItemAdded object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderShipmentStateChanged type:
  • OrderShipmentStateChanged object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderShippingInfoSet type:
  • OrderShippingInfoSet object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderShippingAddressSet type:
  • OrderShippingAddressSet object type now implements OrderMessagePayload interface
• [GraphQL API] Changed the OrderPaymentAdded type:
  • OrderPaymentAdded object type now implements OrderMessagePayload interface

Please find officially released features for our GraphQL API in the schema file publicly available on Github.

Only the features listed in that schema file are fully covered by our SLAs. Any additional features you might discover through introspection are intended for selected customers taking part in closed beta programs. Since such closed beta features can change, we strongly advise against using those in productive environments.

If you are interested in evaluating a closed beta feature and you would like to provide us with feedback about it, please reach out to your contact person at commercetools.

You can now sort the query results, for example by ShippingRate price, when retrieving the Shipping Methods for a Location. Before, you had to implement this logic in the store front application.

• [API] Added sort query parameter to Get ShippingMethods for a Location endpoint.

You can now extend the ProductSelection resource with Custom Fields. With this, you can add meta-information to your Product Selection in case it is required for your business logic.

Changes:

• [API] Added optional custom field to ProductSelection and ProductSelectionDraft.
• [API] Added Set Custom Type and Set CustomField update actions to Product Selections.
• [GraphQL API] Added the following types to the GraphQL schema: SetProductSelectionCustomField, SetProductSelectionCustomType.
• [GraphQL API] Changed the ProductSelection type:
  • Added the custom field to the ProductSelection type.
• [GraphQL API] Changed the ProductSelectionCreatedPayload type:
  • Added the custom field to the ProductSelectionCreatedPayload type.
• [GraphQL API] Changed the IndividualProductSelectionCreatedPayload type:
  • Added the custom field to the IndividualProductSelectionCreatedPayload type.
• [GraphQL API] Changed the ProductSelectionUpdateAction type:
  • Input field setCustomField was added to ProductSelectionUpdateAction type
  • Input field setCustomType was added to ProductSelectionUpdateAction type
• [GraphQL API] Changed the CreateProductSelectionDraft type:
  • Input field custom was added to CreateProductSelectionDraft type

The expiration time for access and refresh tokens can now be configured per API Client by using the new accessTokenValiditySeconds and refreshTokenValiditySeconds fields. If specified, each access and refresh token created by the API Client will expire within the specified number of seconds. If not specified, the tokens will expire as per the default configuration.

Changes:

• [API] Added accessTokenValiditySeconds field to API Client and APIClientDraft.
• [API] Added refreshTokenValiditySeconds field to API Client and APIClientDraft.
• [GraphQL API] Changed the APIClientWithoutSecret type:
  • Added the refreshTokenValiditySeconds field to the APIClientWithoutSecret type.
  • Added the accessTokenValiditySeconds field to the APIClientWithoutSecret type.
• [GraphQL API] Changed the APIClientWithSecret type:
  • Added the accessTokenValiditySeconds field to the APIClientWithSecret type.
  • Added the refreshTokenValiditySeconds field to the APIClientWithSecret type.
• [GraphQL API] Changed the CreateApiClient type:
  • Input field refreshTokenValiditySeconds was added to CreateApiClient type
  • Input field accessTokenValiditySeconds was added to CreateApiClient type

We added the totalLineItemQuantity field to Cart that represents the sum of all Line Item quantities. Its value does not take the Cart's Custom Line Items into consideration. With this, there is no need for you any more to calculate this value on the client side.

Changes:

• [API] Added totalLineItemQuantity field to Cart.
• [GraphQL API] Changed the Cart type:
  • Added the totalLineItemQuantity field to the Cart type.

Add OrderPayment update action performed on Orders or OrderEdits now triggers Messages . To subscribe to Messages, see Subscriptions for Messages and Notifications.

Change:

• [API] Added OrderPaymentAdded Message.

The default limit of Customers you can have in a Project has been increased from 1 million to 10 million. This limit can be increased per Project after we reviewed the performance impact. Find more details in the documentation.

Product Selections let you model the availability of your products in different sales channels. Depending on your use case and by leveraging the existing Stores functionality you can create individual catalogs or assortments for your brand sites, regional shops or brick-and-mortar stores.

Currently, the feature allows you to create Product Selections, populate them with Products, add them to any of your Stores and activate them independently for each Store. We also introduced a new endpoint that returns a Product Projection available in a given Store's active Product Selections.

Please note that the focus of this first release lies in scenarios where assortment management happens in a commercetools-external Product Information Management system and a commercetools-external search provider is used for product discovery in the shop frontend. As a consequence, you currently can’t filter your search results by Product Selections or Stores in both, Product Projections and the Merchant Center Product list. We plan to close these gaps progressively and add more functionality to Product Selections during the public beta phase.

Read more on Product Selections and how to use them in the API reference.

Read more on how to integrate with an external search service providing product discovery for your Store-specific shop frontends in this guide.

Furthermore, you can now subscribe to Messages triggered when Product Selections are created, deleted, or updated or when the Store's Product Selections have changed.

Changes:

• [API] Added the view_product_selections and manage_product_selections OAuth scopes.
• [API] Added ProductSelections.
• [API] Added query on Product Selections for a Product.
• [API] Added Get ProductProjection in Store by ID or by Key.
• [API] Added ProductSelectionCreated and ProductSelectionDeleted Message.
• [API] Added ProductSelectionProductAdded and ProductSelectionProductRemoved Message.
• [API] Added StoreProductSelectionsChanged Message.
• [GraphQL API] Added the following types to the GraphQL schema: AddProductSelectionProduct, AddStoreProductSelection, ChangeProductSelectionName, ChangeStoreProductSelectionActive, CreateProductSelectionDraft, IndividualProductSelectionCreatedPayload, ProductAssignment, ProductAssignmentQueryResult, ProductOfSelection, ProductOfSelectionQueryResult, ProductSelection, ProductSelectionCreated, ProductSelectionCreatedPayload, ProductSelectionDeleted, ProductSelectionProductAdded, ProductSelectionProductRemoved, ProductSelectionQueryInterface, ProductSelectionQueryResult, ProductSelectionSetting, ProductSelectionSettingDraft, ProductSelectionSettingInActionInput, ProductSelectionUpdateAction, RemoveProductSelectionProduct, RemoveStoreProductSelection, SelectionOfProduct, SelectionOfProductQueryResult, SetProductSelectionKey, SetStoreProductSelections, StoreProductSelectionsChanged.
• [GraphQL API] Changed the CreateStore type:
  • Input field productSelections was added to CreateStore type
• [GraphQL API] Changed the Query type:
  • Added the productSelections field to the Query type.
  • Query.inStores description is changed
  • Query object type now implements ProductSelectionQueryInterface interface
  • Added the productSelectionAssignments field to the Query type.
  • Added the productSelection field to the Query type.
  • Query.inStore description is changed
• [GraphQL API] Changed the Mutation type:
  • Added the updateProductSelection field to the Mutation type.
  • Added the deleteProductSelection field to the Mutation type.
  • Added the createProductSelection field to the Mutation type.
• [GraphQL API] Changed the Product type:
  • Added the productSelectionRefs field to the Product type.
• [GraphQL API] Changed the StoreCreated type:
  • Added the productSelections field to the StoreCreated type.
  • Added the productSelectionsRef field to the StoreCreated type.
• [GraphQL API] Changed the Store type:
  • Added the productSelections field to the Store type.
• [GraphQL API] Changed the StoreUpdateAction type:
  • Input field changeProductSelectionActive was added to StoreUpdateAction type
  • Input field setProductSelections was added to StoreUpdateAction type
  • Input field addProductSelection was added to StoreUpdateAction type
  • Input field removeProductSelection was added to StoreUpdateAction type
• [GraphQL API] Changed the InStore type:
  • Added the product field to the InStore type.
  • Added the productSelectionAssignments field to the InStore type.

You can now extend the LineItemReturnItem as well as the CustomLineItemReturnItem object on the Order resource with Custom Fields. With these you can, for example, add the courier name or their shipment IDs to the return items of the Orders.

Changes:

• [API] Added custom field to LineItemReturnItem and CustomLineItemReturnItem.
• [API] Added custom field to LineItemReturnItemDraft and CustomLineItemReturnItemDraft.
• [API] Added Set ReturnItem Custom Type and Set ReturnItem CustomField update actions to Orders and Order Edits.
• [GraphQL API] Added the following types to the GraphQL schema: SetOrderReturnItemCustomField, SetOrderReturnItemCustomType SetStagedOrderReturnItemCustomField, SetStagedOrderReturnItemCustomFieldOutput, SetStagedOrderReturnItemCustomType, SetStagedOrderReturnItemCustomTypeOutput.
• [GraphQL API] Changed the CustomLineItemReturnItem type:
  • Added the custom field to the CustomLineItemReturnItem type.
• [GraphQL API] Changed the ReturnItem type:
  • Added the custom field to the ReturnItem type.
• [GraphQL API] Changed the StagedOrderUpdateAction type:
  • Input field setReturnItemCustomField was added to StagedOrderUpdateAction type
  • Input field setReturnItemCustomType was added to StagedOrderUpdateAction type
• [GraphQL API] Changed the ReturnItemDraftType type:
  • Input field custom was added to ReturnItemDraftType type
• [GraphQL API] Changed the ReturnItemDraftTypeOutput type:
  • Added the custom field to the ReturnItemDraftTypeOutput type.
• [GraphQL API] Changed the OrderUpdateAction type:
  • Input field setReturnItemCustomField was added to OrderUpdateAction type
  • Input field setReturnItemCustomType was added to OrderUpdateAction type
• [GraphQL API] Changed the LineItemReturnItem type:
  • Added the custom field to the LineItemReturnItem type.

You can now extend the Parcel object on the Order resource with Custom Fields. With these you can, for example, add meta data associated with your ERP system to the deliveries of the Orders.

Changes:

• [API] Added custom field to Parcel and ParcelDraft.
• [API] Added Set Parcel CustomType and Set Parcel CustomField update actions to Orders and Order Edits.
• [GraphQL API] Added the following types to the GraphQL schema: SetOrderParcelCustomField, SetOrderParcelCustomType, SetStagedOrderParcelCustomField, SetStagedOrderParcelCustomFieldOutput, SetStagedOrderParcelCustomType, SetStagedOrderParcelCustomTypeOutput.
• [GraphQL API] Changed the Parcel type:
  • Added the custom field to the Parcel type.
• [GraphQL API] Changed the ParcelDataDraftType type:
  • Input field custom was added to ParcelDataDraftType type
• [GraphQL API] Changed the StagedOrderUpdateAction type:
  • Input field setParcelCustomField was added to StagedOrderUpdateAction type
  • Input field setParcelCustomType was added to StagedOrderUpdateAction type
• [GraphQL API] Changed the AddOrderParcelToDelivery type:
  • Input field custom was added to AddOrderParcelToDelivery type
• [GraphQL API] Changed the AddStagedOrderParcelToDeliveryOutput type:
  • Added the custom field to the AddStagedOrderParcelToDeliveryOutput type.
• [GraphQL API] Changed the ParcelData type:
  • Added the custom field to the ParcelData type.
• [GraphQL API] Changed the AddStagedOrderParcelToDelivery type:
  • Input field custom was added to AddStagedOrderParcelToDelivery type
• [GraphQL API] Changed the OrderUpdateAction type:
  • Input field setParcelCustomField was added to OrderUpdateAction type
  • Input field setParcelCustomType was added to OrderUpdateAction type

Added key field to the ProductProjection GraphQL type.

Change:

• [GraphQL API] Changed the ProductProjection type:
  • Added the key field to the ProductProjection type.

You can now revoke your API access and refresh tokens compliant to Auth 2.0 Token Revocation.

Revoking tokens prevents the abuse of abandoned tokens and contributes to the security of your applications. You might want to revoke the tokens associated with the Customer, for example, when the Customer logs out, changes identity or uninstalls your application.

For more information, see Revoking tokens.

With the new Order Search, merchants are able to perform faster search for their orders with enhanced performance, increased query capabilities, and in a scalable way as it supports Projects with a large number of Orders. The feature needs to be activated for the Project before it can be used.

The Order Search API is utilized by our Merchant Center, but you are also welcome to build your own applications with this API. This feature is meant to support back office use cases. It is not intended for searching through the customer's order history in a storefront application.

Changes:

• [API] Introduced Order Search API in public beta.
• [API] Added orders field to Search Indexing Configuration on Projects.
• [API] Added Change Order Search Status update action on Projects.

The Product Projection Search feature on the GraphQL API now supports Price selection.

Changes:

• [GraphQL API] Added the following types to the GraphQL schema: ScopedPrice.
• [GraphQL API] Changed the ProductSearchVariant type:
  • Added the scopedPrice field to the ProductSearchVariant type.
  • Added the scopedPriceDiscounted field to the ProductSearchVariant type.
• [GraphQL API] Changed the PriceSelectorInput type:
  • PriceSelectorInput.date input field type changed from DateTime! to DateTime

You can now extend the Delivery object on the Order resource with Custom Fields. With these you can, for example, add meta data associated with your ERP system to the deliveries of the Orders.

Changes:

• [API] Added custom field to Delivery.
• [API] Added update actions Set Delivery CustomType and Set Delivery CustomField to the Order.
• [GraphQL API] Added the following types to the GraphQL schema: SetOrderDeliveryCustomField, SetOrderDeliveryCustomType, SetStagedOrderDeliveryCustomField, SetStagedOrderDeliveryCustomFieldOutput, SetStagedOrderDeliveryCustomType, SetStagedOrderDeliveryCustomTypeOutput.
• [GraphQL API] Changed the AddOrderDelivery type:
  • Input field custom was added to AddOrderDelivery type
• [GraphQL API] Changed the Delivery type:
  • Added the custom field to the Delivery type.
• [GraphQL API] Changed the AddStagedOrderDelivery type:
  • Input field custom was added to AddStagedOrderDelivery type
• [GraphQL API] Changed the StagedOrderUpdateAction type:
  • Input field setDeliveryCustomField was added to StagedOrderUpdateAction type
  • Input field setDeliveryCustomType was added to StagedOrderUpdateAction type
• [GraphQL API] Changed the AddStagedOrderDeliveryOutput type:
  • Added the custom field to the AddStagedOrderDeliveryOutput type.
• [GraphQL API] Changed the OrderUpdateAction type:
  • Input field setDeliveryCustomType was added to OrderUpdateAction type
  • Input field setDeliveryCustomField was added to OrderUpdateAction type

Previously, the Line Items in Carts and Orders contained the Product ID only, to refer to the related Product. From now on, the Line Items have the user-defined Product key also, in case it exists for the related Product. The new field is present on Carts that were created or updated after 2 December 2021 and on Orders created after this date.

Changes:

• [API] Added productKey field to LineItem.
• [GraphQL API] Changed the LineItem type:
  • Added the productKey field to the LineItem type.

You can now extend the Transaction object on the Payment resource with Custom Fields. With this, you can now store additional information, like refund details and taxed amounts, on the specific payment transaction.

Changes:

• [API] Added custom field to Transaction, TransactionDraft, and MyTransactionDraft .
• [API] Added update actions Set Transaction CustomType and Set Transaction CustomField to Payments.
• [API] Added Set Transaction CustomField update action to My Payments.
• [GraphQL API] Added the following types to the GraphQL schema: SetPaymentTransactionCustomField, SetPaymentTransactionCustomType.
• [GraphQL API] Changed the Transaction type:
  • Added the custom field to the Transaction type.
• [GraphQL API] Changed the MyTransactionDraft type:
  • Input field custom was added to MyTransactionDraft type
• [GraphQL API] Changed the TransactionDraft type:
  • Input field custom was added to TransactionDraft type
• [GraphQL API] Changed the PaymentUpdateAction type:
  • Input field setTransactionCustomType was added to PaymentUpdateAction type
  • Input field setTransactionCustomField was added to PaymentUpdateAction type

You can now update the inventory supply channel for Line Items that are already in a Cart. Before, you could only achieve this via replacing the existing Line Item with a new one.

Changes:

• [API] Added Set LineItem SupplyChannel to Carts and My Carts.
• [GraphQL API] Added the following types to the GraphQL schema: SetCartLineItemSupplyChannel.
• [GraphQL API] Changed the CartUpdateAction type:
  • Input field setLineItemSupplyChannel was added to CartUpdateAction type
• [GraphQL API] Changed the MyCartUpdateAction type:
  • Input field setLineItemSupplyChannel was added to MyCartUpdateAction type

We have increased the maximum timeout for API Extensions of resource type payment from 2 to 10 seconds what makes your integrations with Payment Service Providers more reliable. You can set this timeout on the ExtensionDraft upon creation of the Extension or via Set TimeoutInMs update action (setTimeoutInMs mutation in the GraphQL API).

AWS EventBridge is now supported as a Subscription destination. Configuring EventBridge as a destination allows your serverless event bus to receive message from commercetools Composable Commerce and forward them to a variety of targets based on forwarding rules. Please find more information in our tutorial.

• [API] Added EventBridge destination.
• [GraphQL API] Added the following types to the GraphQL schema: EventBridgeDestination, EventBridgeDestinationInput, SetCartLineItemSupplyChannel.
• [GraphQL API] Changed the SearchIndexingConfiguration type:
  • Added the categoriesDisabledForInternalTest field to the SearchIndexingConfiguration type.
• [GraphQL API] Changed the CartUpdateAction type:
  • Input field setLineItemSupplyChannel was added to CartUpdateAction type
• [GraphQL API] Changed the MyCartUpdateAction type:
  • Input field setLineItemSupplyChannel was added to MyCartUpdateAction type
• [GraphQL API] Changed the SetStagedOrderReturnInfo type:
  • SetStagedOrderReturnInfo.items default value changed from none to []
• [GraphQL API] Changed the DestinationInput type:
  • Input field EventBridge was added to DestinationInput type
• [GraphQL API] Changed the ProductProjection type:
  • Removed the key field from the ProductProjection type.
• [GraphQL API] Changed the SetOrderReturnInfo type:
  • SetOrderReturnInfo.items default value changed from none to []

You can now add the Product key to the results of Product Projection Search queries in the GraphQL API.

Changes:

• [GraphQL API] Added key field to the ProductProjection type.

We have extended the abilities of Audit Log to include the tracking of changes made against Custom Objects. This enhancement will start tracking new Custom Object Changes made and these Changes will be automatically added into your Audit Log responses.

Changes:

• [API] Added the view_key_value_documents:{projectKey} scope.
• [API] Added key-value-document to ChangeHistoryResourceType.
• [API] Added AddPropertyChange.
• [API] Added RemovePropertyChange.
• [API] Added SetPropertyChange.
• [API] Added SetValueChange.
• [API] Added CustomObjectLabel.
• [GraphQL API] Added the following types to the graphQL schema: CustomObjectLabel, CustomObjectChangeInput.
• [GraphQL API] Added queries customObject and customObjects.
• [GraphQL API] Added CustomObject to the ResourceType enum.

With the addition of three new Messages you can now use the MessageSubscription to subscribe to changes on the firstName, lastName, and title fields on Customers specifically. Before, you had to use the generic ChangeSubscription for that. These Messages are triggered by Set First Name, Set Last Name, and Set Title update actions.

Changes:

• [API] Added CustomerFirstNameSet Message.
• [API] Added CustomerLastNameSet Message.
• [API] Added CustomerTitleSet Message.
• [GraphQL API] Added the following types to the GraphQL schema: CustomerFirstNameSet, CustomerLastNameSet, CustomerTitleSet.

We added the field 'supplyChannel' to the InventoryEntryQuantitySet Message on the HTTP API and 'supplyChannel' and 'supplyChannelRef' fields to the GraphQL API. With these fields, you can check the Channel where changes took place.

Changes:

• [API] Added the supplyChannel field to InventoryEntryQuantitySet Message.
• [GraphQL API] Changed the InventoryEntryQuantitySet type:
  • Added the supplyChannelRef field to the InventoryEntryQuantitySet type.
  • Added the supplyChannel field to the InventoryEntryQuantitySet type.

With the Set ReturnInfo update action, you can now delete and overwrite multiple entries in the returnInfo array field of Order in a single request. Previously, to remove an entry from the returnInfo field, it was necessary to use the Add ReturnInfo update action with a negative quantity. The Set ReturnInfo update action triggers the ReturnInfoSet Message.

Changes:

• [API] Added Set ReturnInfo update action to Orders.
• [API] Added Set ReturnInfo update action to Order Edits.
• [API] Added ReturnInfoSet Message.
• [GraphQL API] Added the following types to the GraphQL schema: ReturnInfoDraftType, ReturnInfoDraftTypeOutput, ReturnInfoSet, SetOrderReturnInfo, SetStagedOrderReturnInfo, SetStagedOrderReturnInfoOutput.
• [GraphQL API] Changed the StagedOrderUpdateAction type:
  • Input field setReturnInfo was added to StagedOrderUpdateAction type
• [GraphQL API] Changed the OrderUpdateAction type:
  • Input field setReturnInfo was added to OrderUpdateAction type

We have added the ability to create a fixed price Cart Discount on a CustomLineItems target.

• [API] Added support for CustomLineItems Target when creating a fixed price Cart Discount.

After collecting feedback during the beta phase, we have moved Cart Discount type for fixed prices on Line Items out of beta. The status has been changed to general availability. With Fixed CartDiscountValue you can specify to which price you want to discount the Line Items.

To support the marked matching Variants feature in the GraphQL API we have added the field isMatchingVariant to the Product Variants in the result of productProjectionSearch queries. This field will only have a value when the argument markMatchingVariants (that we also added) is set to true.

Changes:

• [GraphQL API] Changed the ProductSearchVariant type:
  • Added the isMatchingVariant field to the ProductSearchVariant type.
• [GraphQL API] Changed the Query type:
  • Added argument markMatchingVariants to Query.productProjectionSearch field to align with the REST API.
  • Deprecated argument Query.productProjectionSearch(markMatchingVariant) in favor of markMatchingVariants.

To assist you better in error analysis we have added an error response format to the GraphQL API. This format contains detailed information about the errors that should help you in identifying the root cause of the problem.

• [Graphql API] Added the error response format to the GraphQL API.

We have added endpoints for checking whether a Product with certain ID, key or properties exists. These methods can be used if you are only interested in the existence of a certain Product without the need of fetching its product information.

• [API] Added existence check methods for Products by ID, by Key, and by Query Predicate.

It is now possible to sort on Custom Fields using custom.fields.${fieldName} sort parameter.

Shipping Method now supports localized names. This enables displaying shipping methods in different languages.

Changes:

• [API] Added localizedName to ShippingMethod.
• [API] Added localizedName to ShippingMethodDraft.
• [API] Added Set Localized Name Update Action.
• [GraphQL API] Changed the ShippingMethodUpdateAction type:
  • Input field setLocalizedName was added to ShippingMethodUpdateAction type.
• [GraphQL API] Changed the ShippingMethod type:
  • Added the localizedNameAllLocales field to the ShippingMethod type.
  • Added the localizedName field to the ShippingMethod type.
• [GraphQL API] Changed the ShippingMethodDraft type:
  • Input field localizedName was added to ShippingMethodDraft type.
• [GraphQL API] Added the following type to the GraphQL schema: SetShippingMethodLocalizedName.

After collecting feedback during the beta phase, we have moved Stores out of beta. The status of the following features has been changed to general availability:

• Creating and managing Stores
• Custom fields on Stores
• Stores on Carts, Orders, Customers, and Shopping Lists
• Store-based OAuth scopes for orders, customers, and Shopping Lists
• Store-based Product Projection dimensions for filtering of locales, prices, and inventory based on Store settings.

In addition, to support use cases requiring a high number of Stores we have increased the limit on the number of Stores in a Project from 500 to 50000.

We have added a specific Message that is published whenever a Customer is deleted. That means, you can now subscribe to this particular message and do not need to use the generic ChangeSubscription anymore to implement such use cases.

Changes:

• [API] Added CustomerDeleted Message.
• [GraphQL API] Added the following types to the GraphQL schema: CustomerDeleted.

It is now possible to exclude Changes initiated by background processes from Audit Log response data sets.

Change:

• [API] Added excludePlatformInitiatedChanges query parameter to all Query Record endpoints that will allow Changes originated by background processes to be excluded from the response data set.
• [GraphQL API] Added excludePlatformInitiatedChanges filtering parameter.

To align usage of data types on the GraphQL API we changed the type of the date field on PriceSelectorInput to DateTime.

Changes:

• [GraphQL API] Changed the PriceSelectorInput.date type from Instant! to DateTime!

To improve the developer experience for you we have added an exists operator to our GraphQL API. This improvement to the API design is now the recommended way of checking the existence of query results because

1. it optimizes the query resulting in shorter response times and
2. it avoids you finding workarounds with other query fields to achieve the same.

Changes:

• [GraphQL API] Added the Boolean exists field to all QueryResult types.

Calls to the introspection endpoint of an external OAuth server now include the correlation ID initially passed in the request. This enables users to have a complete trace of the HTTP calls exchanged with the API and thus helps troubleshoot implementation issues.

We have set up a long-term support plan to actively support and maintain Version 1 (v1) SDKs until their end of life. Additionally, we have provided information about migration to our Version 2 (v2) SDKs that are constantly updated with the newest API features as soon as they are released. This support plan indicates when you could schedule the migration to v2 SDKs.

To ensure best performance for your queries we have now limited the Channel settings for Stores. From now on each of your Stores can have

• up to 100 Inventory Supply Channels and
• up to 100 Product Distribution Channels

by default.

These default limits can be increased if needed after we have reviewed the performance impact on your project. To request a limit increase, contact us via the Support Portal, specifying your project region, project key and your use case.

The limit of Subscriptions per Project has been raised from 25 to 50.

ProductProjection Search can now be performed using the GraphQL API.

Changes:

• [GraphQL API] Added the following types to the GraphQL schema: CategoryOrderHintProductSearch, DimensionsProductSearch, DiscountedProductSearchPriceValue, ExistsFilterInput, FacetResult, FacetResultValue, ImageProductSearch, MissingFacetInput, MissingFilterInput, PriceSelectorInput, ProductPriceSearch, ProductProjection, ProductProjectionSearchResult, ProductSearchPriceTier, ProductSearchVariant, ProductSearchVariantAvailabilitiesResult, ProductSearchVariantAvailability, ProductSearchVariantAvailabilityWithChannel, ProductSearchVariantAvailabilityWithChannels, RangeCount, RangeCountDouble, RangeCountLong, RangeElementInput, RangeFacetInput, RangeFacetResult, RangeFilterInput, RawProductSearchAttribute, SearchFacetInput, SearchFacetModelInput, SearchFilterInput, SearchFilterModelInput, SearchKeywordProductSearch, SearchKeywordsProductSearch, SuggestTokenizerProductSearch,CustomSuggestTokenizerProductSearch,WhitespaceSuggestTokenizerProductSearch, TermCount, TermsFacetInput, TermsFacetResult, TreeFacetInput, TreeFilterInput, ValueCountFacetInput, ValueFacetInput, ValueFacetResult, ValueFilterInput.
• [GraphQL API] Changed the Query type:
  • Added the productProjectionSearch field to the Query type.

You can now subscribe to messages triggered when Stores are created and deleted.

Changes:

• [API] Added StoreCreated Message
• [API] Added StoreDeleted Message
• [GraphQL API] Added the following types to the GraphQL schema: StoreCreated, and StoreDeleted.

Introduced a limit on Product Types. For Projects created after 23 June 2021, the number of Product Types in a Project is limited to 1 000. To request a limit increase, please contact us via the Support Portal.

• [API] Introduced an API Limit on Product Types.

Extended support for Audit Log Change tracking. The following Changes are now properly identified and displayed in the Change History API instead of being identified as an UnknownChange. This applies to both the REST and the GraphQL APIs.

• [API] Added AddDiscountCodeChange.
• [API] Added RemoveDiscountCodeChange.
• [API] Added ChangeTaxCalculationModeChange.
• [API] Added ChangeTaxModeChange.
• [API] Added ChangeTaxRoundingModeChange.
• [API] Added SetCountryChange.
• [API] Added SetCustomLineItemTaxAmountChange.
• [API] Added SetCustomShippingMethodChange.
• [API] Added SetLineItemDistributionChannelChange.
• [API] Added SetLineItemTaxAmountChange.
• [API] Added SetOrderTotalTaxChange.
• [API] Added SetShippingMethodChange.
• [API] Added SetShippingMethodTaxAmountChange.
• [API] Added SetShippingMethodTaxRateChange.
• [API] Added SetShippingRateInputChange.
• [API] Added SetCustomLineItemTaxCategoryChange.
• [API] Added SetShippingInfoPriceChange.
• [API] Added SetShippingRateChange.
• [API] Added SetShippingInfoTaxedPriceChange.
• [API] Added SetOrderTaxedPriceChange.
• [API] Added SetCustomLineItemTaxRateChange.
• [API] Added SetLineItemTaxRateChange.
• [API] Added taxMode to SetOrderTaxedPriceChange.
• [API] Added taxMode to SetCustomLineItemTaxRateChange.
• [API] Added taxMode to SetLineItemTaxRateChange.
• [GraphQL API] Added the taxMode field to OrderChange.

The response to an OAuth 2.0 Token Introspection request now provides the client_id as optional field as defined in RFC 7662.

You can now set a Store on Shopping Lists, and view and manage Shopping Lists and My Shopping Lists in a Store. When expanding the Line Items on a Shopping List in a Store, the prices, locales, and inventory are filtered to only include data for the specified Store.

• [API] Added the store field to ShoppingList, ShoppingListDraft, and MyShoppingListDraft.
• [API] Added new Store-related scopes, view_shopping_lists, manage_shopping_lists, and manage_my_shopping_lists
• [API] Added Get ShoppingList in Store by ID method to Shopping Lists and My Shopping Lists.
• [API] Added Get ShoppingList in Store by Key method to Shopping Lists and My Shopping Lists.
• [API] Added Query ShoppingLists in Store method to Shopping Lists and My Shopping Lists.
• [API] Added Create ShoppingList in Store method to Shopping Lists and My Shopping Lists.
• [API] Added Update ShoppingList in Store by ID method to Shopping Lists and My Shopping Lists.
• [API] Added Update ShoppingList in Store by Key method to Shopping Lists and My Shopping Lists.
• [API] Added Set Store update action to Shopping Lists.
• [API] Added Delete ShoppingList in Store by ID method to Shopping Lists and My Shopping Lists.
• [API] Added Delete ShoppingList in Store by Key method to Shopping Lists and My Shopping Lists.
• [GraphQL API] The existing query fields inStore and inStores can be used to query, update and delete Shopping Lists in one or more Stores. The query fields can also be used for My Shopping Lists.
• [GraphQL API] Changed the ShoppingListQuery type:
  • Added the store field to the ShoppingListQuery type.

Indexing of Product information for non-production Projects will automatically be deactivated if there have been no calls against the following API endpoints within the last 30 days:

• Product Projection Search
• Product Suggestions
• Project update with the action Change Product Search Indexing Enabled

The deactivation of Product information indexing will always happen on the day after a 30 day observation period.

The first deactivations will happen on 12 April 2021 and will include Projects that had no calls against the aforementioned API endpoints between 13 March 2021 and 11 April 2021. Please see the example below:

• Start date 30 days observation period: 13 March 2021
• End date 30 days observation period: 11 April 2021
• Last API call or day of activation (search indexing activated): 12 March 2021
• Day of automatic deactivation: 12 April 2021

Deactivation of Product information indexing means that calls to either of the above Product Projection Search or Product Suggestions endpoint will return a status code of 400 unless Product information indexing is explicitly re-activated. Please refer to API documentation for more details.

At the moment, this change does not apply to Projects that are marked as production Projects or any Projects hosted on AWS Hosts.

By adding Client Logging information to the Search Indexing Configuration you can now find out who changed this project configuration and when it was changed.

• [API] Added lastModifiedBy and lastModifiedAt fields to SearchIndexingConfigurationValues
• [GraphQL API] Changed the SearchIndexingConfigurationValues type:
  • Added the lastModifiedBy field to the SearchIndexingConfigurationValues type.
  • Added the lastModifiedAt field to the SearchIndexingConfigurationValues type.

Introduced Audit Log, a new feature that tracks and stores changes made against resources in your Project. You can now view a historical log of these changes via the Change History API, including GraphQL, or the Merchant Center. The feature is currently available in our Google Cloud Regions.

As announced before, we have now removed deprecated fields and OAuth scopes from the GraphQL API. Using those fields in your GraphQL API requests will yield to HTTP 400 errors with header X-DEPRECATION-NOTICE from now on.