Adobe has posted the November 2026 release #1 notes for Adobe Commerce as a Cloud Service. The changes are in Sandbox environments now and, according to Adobe, reach Production on 10 November 2026. Most items are small API and webhook additions, but one of them can break existing order integrations, and a few bug fixes touch things shoppers notice, such as stock alert emails. Here is what Magento 2 teams should take from it.
Who this applies to
These notes cover Adobe Commerce as a Cloud Service, Adobe's SaaS edition. Adobe says that stores on Adobe Commerce on-premises or on cloud infrastructure (PaaS) should follow the regular Adobe Commerce release notes instead, and Magento Open Source does not get these changes automatically. Still, the SaaS release notes are a useful preview: they show where Adobe is taking the APIs that agencies and integrators build against.
1. REST orders now need a shipping address
This is the change to check first. New non-virtual orders created through POST /V1/orders and PUT /V1/orders/create now require a shipping address. Requests without one return an HTTP 400 error. Adobe says the goal is to stop orders without shipping information from causing order email failures.
If an ERP, marketplace connector or POS integration creates orders through these endpoints, test it in Sandbox before 10 November. Adobe lists two ways to create an order without a shipping address:
- Set is_virtual to 1 when the order only contains digital products.
- Place the order from a cart with the PUT /V1/carts/:cartId/order endpoint.
2. Custom attributes on cart items
The addProductsToCart GraphQL mutation now accepts custom attributes on cart items, as an array of key/value pairs in CartItemInput.custom_attributes. That is useful for things like engraving text, gift notes or a reference that a B2B buyer needs to see on the order, without a custom module to carry the value through the cart.
3. New webhooks for returns and shipments
- observer.rma_save_before lets you read a return and its items before it is saved and change attribute values. It runs as part of the save, so if a required webhook fails, the return is not saved.
- plugin.magento.out_of_process_shipping_methods.api.shipment_item_filter.filter lets you exclude order items from new shipments, for example items that a third party fulfils.
Both follow Adobe's direction of moving customisation out of PHP modules and into App Builder apps and webhooks.
4. Smaller API additions
- Category GraphQL types (CategoryInterface and CategoryTree) gain an asset_role_image field for category images assigned from AEM Assets.
- A new GET /V1/customers/:customerId/balance REST endpoint returns a customer's store credit balance. It needs the Manage Store Credit Balances permission.
- InvoiceItemInterface in GraphQL now includes row_total, the stored row subtotal for an invoice item.
5. Bug fixes shoppers will notice
A few of the listed fixes affect the storefront and customer emails directly:
- Price and back-in-stock alert emails were not being sent. That is fixed, so expect alerts to start going out again.
- Abandoned cart reminder emails could be sent more than once.
- Configurable product options such as colour or size could be missing from selected_options in GraphQL order responses when the item also had custom options.
- AEM Assets product images were returned without image roles in GraphQL product queries. Adobe says products exported before the fix need a product data feed resync to get their image roles back.
If you paused alert campaigns because emails were not arriving, check them again after the release. If your product images come from AEM Assets, plan the feed resync.
What to do this week
- Search your integrations for calls to POST /V1/orders and PUT /V1/orders/create, and test them in Sandbox with and without a shipping address.
- If you rely on price or stock alerts, watch the alert email volume after 10 November.
- If you use AEM Assets for product images, schedule the product data feed resync.
- If you are on PaaS or Magento Open Source, treat this as a preview of the API direction, not something to deploy.
Why clean catalog data keeps paying off
Several items in this release are about structured product data: cart item attributes, configurable options in order responses, image roles and category images. The same structure matters for on-site AI search. Claspwell is a catalog-aware AI sales assistant for Magento 2 and Hyvä that works from your synced categories, products and shopper-facing attributes rather than from crawled pages, so well-maintained attributes lead directly to better answers. If you want to see how it would fit your store, you can request an integration. A typical install takes 3 days to 1 week once scope and access are ready.
Source: Adobe Commerce as a Cloud Service release notes, November 2026 release #1 (Adobe Experience League).