[CATALYST-1681] Add Supported Features #1236

jamesqquick · 2026-01-14T19:44:11Z

CATALYST-1681

What changed?

Add new Supported Features page and updated the choose a storefront doc with updated language.

Release notes draft

In an effort to be more clear around what features are and are not supported in Catalyst, we have added a dedicated Supported Features page. This page will be updated as we make progress in implementing new features and is the go-to resource for feature parity questions going forward.

ping {names}

…talyst

chanceaclark · 2026-01-14T21:32:26Z

docs/storefront/catalyst/features/supported-features.mdx

+| Feature | Supported | Notes |
+|---------|-----------|-------|
+| [Banners](https://support.bigcommerce.com/s/article/Creating-Editing-Banners) | 🔴 | Use [Makeswift](https://www.makeswift.com) (or an alternative) instead. |
+| Hosting for Catalyst by BigCommerce | 🔴 | Requires hosting your own storefront code. |


Should we provide a list of hosting solutions, like we do with the Returns / RMA feature?

Great suggestion. Added some details and referenced our hosting deployment doc

chanceaclark · 2026-01-14T21:33:48Z

docs/storefront/catalyst/features/supported-features.mdx

+| [Banners](https://support.bigcommerce.com/s/article/Creating-Editing-Banners) | 🔴 | Use [Makeswift](https://www.makeswift.com) (or an alternative) instead. |
+| Hosting for Catalyst by BigCommerce | 🔴 | Requires hosting your own storefront code. |
+| [Meta Pixel](https://support.bigcommerce.com/s/article/Meta-Pixel) | 🔴 |  |
+| [Draft Orders](https://support.bigcommerce.com/s/article/Creating-a-Draft-Order) | 🔴 | Specifically, the ability for Catalyst to take a customer-facing Draft Order URL and apply it to the Catalyst session is not supported. |


This reminds me that we probably need an item for Abandoned Cart Emails as well from the slack message this morning.

Added a line below. I'll tag you there to get feedback on the language.

"Specifically, the ability for Catalyst to take a customer-facing Abandoned Cart URL and apply it to the Catalyst cart is not supported."

Added a line item below "Specifically, the ability for Catalyst to take a customer-facing Abandoned Cart URL and apply it to the Catalyst cart is not supported."

Does that language fit?

Yeah that sounds good to me.

chanceaclark · 2026-01-14T21:34:35Z

docs/storefront/catalyst/features/supported-features.mdx

+| [App Support](https://support.bigcommerce.com/s/article/Apps-Video) | 🟡 | Back-office apps focused on backend and Control Panel functionality are supported in Catalyst. Additionally, any app that exposes APIs can be integrated with custom code.  However, storefront apps that modify frontend storefront behavior most likely will not work with Catalyst. To learn more about app compatibility with Catalyst, read our [Building Catalyst compatible apps guide](/docs/integrations/apps/guide/catalyst-compatible-apps). |
+| Express Wallet Buttons | 🟡 | Can be custom-built using the GraphQL Storefront API |
+| [Gift Wrapping](https://support.bigcommerce.com/s/article/Gift-Wrapping) | 🟡 | |
+| Masquerading / Login as Customer | 🟡 | |


This is 🟡 because it's supported by Catalyst Customer Login app https://github.com/bigcommerce/catalyst-customer-login. We should support this natively though

What language would you add here? "Supported by Catalyst Customer Login app but not natively supported"?

chanceaclark · 2026-01-14T21:36:22Z

docs/storefront/catalyst/features/supported-features.mdx

+| [B2B Open Source Buyer Portal](https://github.com/bigcommerce/b2b-buyer-portal) | 🔴 | Although you can layer in the Open Source Buyer Portal into Catalyst, it is not natively supported. |
+| [App Support](https://support.bigcommerce.com/s/article/Apps-Video) | 🟡 | Back-office apps focused on backend and Control Panel functionality are supported in Catalyst. Additionally, any app that exposes APIs can be integrated with custom code.  However, storefront apps that modify frontend storefront behavior most likely will not work with Catalyst. To learn more about app compatibility with Catalyst, read our [Building Catalyst compatible apps guide](/docs/integrations/apps/guide/catalyst-compatible-apps). |
+| Express Wallet Buttons | 🟡 | Can be custom-built using the GraphQL Storefront API |
+| [Gift Wrapping](https://support.bigcommerce.com/s/article/Gift-Wrapping) | 🟡 | |


I think this can be done through Shared Product Options, but @matthewvolk you might know more here.

chanceaclark · 2026-01-14T21:37:07Z

docs/storefront/catalyst/features/supported-features.mdx

+| Order Downloads | 🟡 | Use custom digital product fulfillment pipeline. Like agencies do for Stencil today. |
+| Order Tracking Links | 🟡 | |
+| Product Videos | 🟡 | |
+| [Saved Payment Methods](https://support.bigcommerce.com/s/article/Enabling-Stored-Payment-Methods) | 🟡 | |


This works on the checkout side, but not within the Catalyst account area. I think it's possible to use REST API's in order to fetch this 🤔

Got it. Do you think it's worth clarfying those two things here?

"This works in redirected checkout, but customers cannot save payment methods in the Catalyst account settings directly"?

Makes sense to me.

I think that is good verbiage. I don't know if it's actually possible to use the REST API but it's something to look into.

chanceaclark · 2026-01-14T21:38:52Z

docs/storefront/catalyst/features/supported-features.mdx

+| Order Tracking Links | 🟡 | |
+| Product Videos | 🟡 | |
+| [Saved Payment Methods](https://support.bigcommerce.com/s/article/Enabling-Stored-Payment-Methods) | 🟡 | |
+| Sitemap | 🟡 | Catalyst does generate a sitemap for you, but it does not factor in routes that are not managed by BigCommerce. For example, it does not include routes that are created in Makeswift |


Something that keeps coming up from merchants is the ability to change the domain within the sitemap index file to be the vanity domain. I don't think we should do it, but instead we need to inform merchants that it shouldn't affect crawlers abilities to index their site correctly.

Do you have a reference as to what that looks like?

https://catalyst-demo.site/sitemap.xml

This is what is currently looks like:

<sitemapindex xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/siteindex.xsd"> <sitemap> <loc>https://store-rwyfoupid7-1669478.mybigcommerce.com/xmlsitemap.php?type=products&page=1</loc> </sitemap> // ... </sitemapindex>

This is what they want, but what we have doesn't actually affect SEO:

<sitemapindex xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/siteindex.xsd"> <sitemap> <loc>https://catalyst-demo.site/xmlsitemap.php?type=products&page=1</loc> </sitemap> // ... </sitemapindex>

chanceaclark · 2026-01-14T21:39:48Z

docs/storefront/catalyst/features/supported-features.mdx

+| [Saved Payment Methods](https://support.bigcommerce.com/s/article/Enabling-Stored-Payment-Methods) | 🟡 | |
+| Sitemap | 🟡 | Catalyst does generate a sitemap for you, but it does not factor in routes that are not managed by BigCommerce. For example, it does not include routes that are created in Makeswift |
+| In-app search | 🟡 | Catalyst does support search for BigCommerce products, but it does not factor in content that is not managed by BigCommerce. For example, it does not include content that is created in Makeswift |
+| Session Syncing | 🟡 | Session can be synced from a headless storefront to a Stencil checkout. For example: you log in/out in headless then redirect to checkout. Session cannot be synced from a Stencil checkout to a headless storefront. For example: you log in/out in Stencil then redirect back. |


We should probably link to this documentation https://developer.bigcommerce.com/docs/storefront/catalyst/development/session-sync

Great suggestion. Added!

migueloller

Looking good! Got a couple of suggestions

docs/storefront/catalyst/features/supported-features.mdx

migueloller · 2026-01-15T16:04:23Z

docs/storefront/catalyst/features/supported-features.mdx

+- 🟡 **Yellow**: Partially supported but might be missing functionality
+- 🔴 **Red**: Not supported
+
+<Callout type="info">Since you have complete ownership of the code with Catalyst, you can custom build implementations of yellow and red features if you would like to.</Callout>


Might it be helpful to call out what's in the GraphQL API and what isn't? The difficulty of building something depends a lot on availability in the GraphQL API. Perhaps yellow means it's supported by the API but it's not in Catalyst and red that it's not in the GraphQL API?

Yeah I'd love to get that level of detail. Unfortunately, that means additional help from others which may or may not be a big deal. I was thinking of including those details as a future iteration and being able to ship this one and communicate "this is where you go for feature lists". Then, track update work for the future and also take feedback. If you happen to know the answers to a few of these right of hand, I'd love that!

Co-authored-by: Miguel Oller <[email protected]>

jamesqquick · 2026-01-15T18:25:12Z

docs/storefront/catalyst/features/supported-features.mdx

+- 🟡 **Yellow**: Partially supported but might be missing functionality
+- 🔴 **Red**: Not supported
+
+<Callout type="info">Since you have complete ownership of the code with Catalyst, you can custom build implementations of yellow and red features if you would like to.</Callout>


Yeah I'd love to get that level of detail. Unfortunately, that means additional help from others which may or may not be a big deal. I was thinking of including those details as a future iteration and being able to ship this one and communicate "this is where you go for feature lists". Then, track update work for the future and also take feedback. If you happen to know the answers to a few of these right of hand, I'd love that!

jamesqquick · 2026-01-15T18:31:46Z

docs/storefront/catalyst/features/supported-features.mdx

+| [Banners](https://support.bigcommerce.com/s/article/Creating-Editing-Banners) | 🔴 | Use [Makeswift](https://www.makeswift.com) (or an alternative) instead. |
+| Hosting for Catalyst by BigCommerce | 🔴 | Requires hosting your own storefront code. |
+| [Meta Pixel](https://support.bigcommerce.com/s/article/Meta-Pixel) | 🔴 |  |
+| [Draft Orders](https://support.bigcommerce.com/s/article/Creating-a-Draft-Order) | 🔴 | Specifically, the ability for Catalyst to take a customer-facing Draft Order URL and apply it to the Catalyst session is not supported. |


Added a line below. I'll tag you there to get feedback on the language.

"Specifically, the ability for Catalyst to take a customer-facing Abandoned Cart URL and apply it to the Catalyst cart is not supported."

jamesqquick · 2026-01-15T18:31:59Z

docs/storefront/catalyst/features/supported-features.mdx

+| [Order Messages](https://support.bigcommerce.com/s/article/Communicating-with-Customers#Messages) | 🔴 | Specfically, the ability for a customer to add additional messages on the order details page after checkout is not supported. |
+| Promotional Banners | 🔴 |  |
+| Returns / RMA | 🔴 | Recommended to use partner solutions (e.g., Happy Returns, Returnly, Loop Returns, AfterShip). |
+| [Abandoned Cart](https://support.bigcommerce.com/s/article/Using-the-Abandoned-Cart-Saver?language=en_US) | 🔴 | Specifically, the ability for Catalyst to take a customer-facing Abandoned Cart URL and apply it to the Catalyst cart is not supported. |


cc @chanceaclark on abandoned cart text

jamesqquick · 2026-01-15T18:33:43Z

docs/storefront/catalyst/features/supported-features.mdx

+| [Banners](https://support.bigcommerce.com/s/article/Creating-Editing-Banners) | 🔴 | Use [Makeswift](https://www.makeswift.com) (or an alternative) instead. |
+| Hosting for Catalyst by BigCommerce | 🔴 | Requires hosting your own storefront code. |
+| [Meta Pixel](https://support.bigcommerce.com/s/article/Meta-Pixel) | 🔴 |  |
+| [Draft Orders](https://support.bigcommerce.com/s/article/Creating-a-Draft-Order) | 🔴 | Specifically, the ability for Catalyst to take a customer-facing Draft Order URL and apply it to the Catalyst session is not supported. |


Added a line item below "Specifically, the ability for Catalyst to take a customer-facing Abandoned Cart URL and apply it to the Catalyst cart is not supported."

Does that language fit?

jamesqquick · 2026-01-15T18:33:51Z

docs/storefront/catalyst/features/supported-features.mdx

+| [Order Messages](https://support.bigcommerce.com/s/article/Communicating-with-Customers#Messages) | 🔴 | Specfically, the ability for a customer to add additional messages on the order details page after checkout is not supported. |
+| Promotional Banners | 🔴 |  |
+| Returns / RMA | 🔴 | Recommended to use partner solutions (e.g., Happy Returns, Returnly, Loop Returns, AfterShip). |
+| [Abandoned Cart](https://support.bigcommerce.com/s/article/Using-the-Abandoned-Cart-Saver?language=en_US) | 🔴 | Specifically, the ability for Catalyst to take a customer-facing Abandoned Cart URL and apply it to the Catalyst cart is not supported. |


cc @chanceaclark

jamesqquick · 2026-01-15T18:34:19Z

docs/storefront/catalyst/features/supported-features.mdx

+| [App Support](https://support.bigcommerce.com/s/article/Apps-Video) | 🟡 | Back-office apps focused on backend and Control Panel functionality are supported in Catalyst. Additionally, any app that exposes APIs can be integrated with custom code.  However, storefront apps that modify frontend storefront behavior most likely will not work with Catalyst. To learn more about app compatibility with Catalyst, read our [Building Catalyst compatible apps guide](/docs/integrations/apps/guide/catalyst-compatible-apps). |
+| Express Wallet Buttons | 🟡 | Can be custom-built using the GraphQL Storefront API |
+| [Gift Wrapping](https://support.bigcommerce.com/s/article/Gift-Wrapping) | 🟡 | |
+| Masquerading / Login as Customer | 🟡 | |


What language would you add here? "Supported by Catalyst Customer Login app but not natively supported"?

jamesqquick · 2026-01-15T18:35:44Z

docs/storefront/catalyst/features/supported-features.mdx

+| Order Downloads | 🟡 | Use custom digital product fulfillment pipeline. Like agencies do for Stencil today. |
+| Order Tracking Links | 🟡 | |
+| Product Videos | 🟡 | |
+| [Saved Payment Methods](https://support.bigcommerce.com/s/article/Enabling-Stored-Payment-Methods) | 🟡 | |


Got it. Do you think it's worth clarfying those two things here?

"This works in redirected checkout, but customers cannot save payment methods in the Catalyst account settings directly"?

jamesqquick · 2026-01-15T18:36:05Z

docs/storefront/catalyst/features/supported-features.mdx

+| Order Tracking Links | 🟡 | |
+| Product Videos | 🟡 | |
+| [Saved Payment Methods](https://support.bigcommerce.com/s/article/Enabling-Stored-Payment-Methods) | 🟡 | |
+| Sitemap | 🟡 | Catalyst does generate a sitemap for you, but it does not factor in routes that are not managed by BigCommerce. For example, it does not include routes that are created in Makeswift |


Do you have a reference as to what that looks like?

CNanninga · 2026-01-15T20:21:46Z

docs/storefront/catalyst/features/supported-features.mdx

@@ -0,0 +1,57 @@
+# Feature Support
+
+Here is a list of BigCommerce platform features and whether or not they are supported and to what extent in Catalyst. One important note when considering Catalyst feature support is that Catalyst is focused on working with the [GraphQL Storefront API](/docs/storefront/graphql) and not the [REST Management API](/docs/rest-management). This means that some features cannot be supported in Catalyst until the functionality is available in the GraphQL Storefront API.


A couple wording changes for this paragraph:

For just a better flow for the first sentence, something like: "Below is a list of major BigCommerce platform features, detailing what support exists in Catalyst."

I think the last sentence is a little misleading in that it implies you CAN'T make use of the REST Management API for these features in Catalyst. Should we say "will not be supported out of the box" or something like that? Might even be worth an additional note that you can build support for these features if you integrate authentication with the REST Management API.

CNanninga · 2026-01-15T20:33:32Z

docs/storefront/catalyst/features/supported-features.mdx

+
+<Callout type="info">Since you have complete ownership of the code with Catalyst, you can custom build implementations of yellow and red features if you would like to.</Callout>
+
+| Feature | Supported | Notes |


The table seems to be organized specifically with unsupported first. Just a note that that was counterintuitive to me.

Yeah that was intentional although I debated about it. I assume the most important thing someone wants to know is what is not supported vs what is. That's why I put it at the top. I'm curious to see what other feedback we get on that

CNanninga · 2026-01-15T20:34:23Z

docs/storefront/catalyst/features/supported-features.mdx

+| Feature | Supported | Notes |
+|---------|-----------|-------|
+| [Banners](https://support.bigcommerce.com/s/article/Creating-Editing-Banners) | 🔴 | Use [Makeswift](https://www.makeswift.com) (or an alternative) instead. |
+| Hosting for Catalyst by BigCommerce | 🔴 | Requires hosting your own storefront code (ex. Vercel, AWS, Cloudflare, etc.). See the [Deploying a Catalyst storefront guide](/docs/storefront/catalyst/getting-started/deploying/overview) for more information. |


I would say "hosting on your own provider" rather than "your own storefront code"

CNanninga · 2026-01-15T20:34:51Z

docs/storefront/catalyst/features/supported-features.mdx

+| Feature | Supported | Notes |
+|---------|-----------|-------|
+| [Banners](https://support.bigcommerce.com/s/article/Creating-Editing-Banners) | 🔴 | Use [Makeswift](https://www.makeswift.com) (or an alternative) instead. |
+| Hosting for Catalyst by BigCommerce | 🔴 | Requires hosting your own storefront code (ex. Vercel, AWS, Cloudflare, etc.). See the [Deploying a Catalyst storefront guide](/docs/storefront/catalyst/getting-started/deploying/overview) for more information. |


Also, "for Catalyst" is redundant. "Hosting by BigCommerce"

CNanninga · 2026-01-15T20:36:24Z

docs/storefront/catalyst/features/supported-features.mdx

+| Returns / RMA | 🔴 | Recommended to use partner solutions (e.g., Happy Returns, Returnly, Loop Returns, AfterShip). |
+| [Abandoned Cart](https://support.bigcommerce.com/s/article/Using-the-Abandoned-Cart-Saver?language=en_US) | 🔴 | Specifically, the ability for Catalyst to take a customer-facing Abandoned Cart URL and apply it to the Catalyst cart is not supported. |
+| File Upload Product Option Type | 🔴 | |
+| [B2B Open Source Buyer Portal](https://github.com/bigcommerce/b2b-buyer-portal) | 🔴 | Although you can layer in the Open Source Buyer Portal into Catalyst, it is not natively supported. |


We have an official integration that's considered experimental. Shouldn't we mention that and link to the docs page?

Great point! Updated accordingly!

CNanninga · 2026-01-15T20:58:39Z

docs/storefront/catalyst/features/supported-features.mdx

+| PCI Compliance | 🟢 | Today, no payments information touches the Next.js application due to the use of redirected checkout, so the Next.js layer is kept out of PCI scope for the most part. As we figure out the path to add Saved Payment Methods into the My Account area, we will approach this with an embedded/iframe based approach to provide similar guarantees. |
+| [Persistent Cart](https://support.bigcommerce.com/s/article/Persistent-Cart) | 🟢 | Login mutation will be extended to automatically restore and merge carts just like Stencil. |
+| [Promotions](https://support.bigcommerce.com/s/article/Promotions-Video) | 🟢 | Promotional logic works in cart; some promo banners are not yet supported (separate item). |
+| [Scripts API](https://support.bigcommerce.com/s/article/Using-Script-Manager) | 🟢 | Although we don't think frontend script injection is the right way for most solutions to integrate into Catalyst - we think most people would be better served by writing Server Components - we have added Scripts into GraphQL Storefront API so they can be rendered in Catalyst when it does make sense, such as for analytics pixels. |


I think we should note here that Handlebars expressions that work in scripts on a Stencil storefront won't function in Catalyst. I'm not sure if we would consider that as downgrading this to a yellow, but we should at least note it.

Would Script Manager be a better title for the line item, rather than Scripts API? We're supporting scripts you add in Script Manager in the control panel or via the Management API (which I think still end up being listed in Script Manager).

Updated on both!

CNanninga · 2026-01-15T21:02:18Z

docs/storefront/choosing-a-storefront.mdx

-Understanding the strengths and limitations of your options will help you make an informed decision when building your next BigCommerce storefront. 
-
-Let’s dive into the details\! 
+BigCommerce provides developers multiple ways to build and customize ecommerce storefronts catering to different developer needs and use cases. This makes it crucial to understand their differences and similarities when choosing the right approach for your project. This guide will walk you through choosing between our primary storefront options, [Stencil](/docs/storefront/stencil/start) and [Catalyst](/docs/storefront/catalyst), as well as a custom headless implementation.


Just a heads-up that I believe we're going to be shifting toward contrasting Stencil with Next.js and contrasting Cornerstone with Catalyst. (i.e., Catalyst is a theme on Next.js.

We haven't shifted that yet, but it's worth considering it when creating new docs.

Good callout. We'll have to update in multiple places I imagine so I'll save that for a bigger initiative

CNanninga · 2026-01-15T21:07:13Z

docs/storefront/choosing-a-storefront.mdx

+** Limitations of Catalyst:**

-## What does a custom headless build look like on BigCommerce?
+* **GraphQL Storefront API Limitations:** - The GraphQL Storefront API that Catalyst depends on does not support all BigCommerce platform features


Again, I wonder if it's worth making a distinction that this is specifically just what's out of the box.

CNanninga · 2026-01-15T21:07:38Z

docs/storefront/choosing-a-storefront.mdx

+* **GraphQL Storefront API Limitations:** - The GraphQL Storefront API that Catalyst depends on does not support all BigCommerce platform features
+* **Hosting:** - You are responsible for hosting your deployed storefront code
+* **App Marketplace** - Apps from the App Marketplace are not all supported
+* **Themes:** - Catalyst does not provide a list of themes to choose from. However, you can customise the existing theme in code or by using Makeswift


I would say "theme marketplace" instead of "list of themes to choose from".

CNanninga · 2026-01-15T21:08:00Z

docs/storefront/choosing-a-storefront.mdx

+* **Themes:** - Catalyst does not provide a list of themes to choose from. However, you can customise the existing theme in code or by using Makeswift

-Building a headless storefront with BigCommerce’s GraphQL APIs enables a fast, flexible, and scalable ecommerce experience. By decoupling the frontend, you can use your preferred frameworks to create a dynamic, SEO-friendly site while BigCommerce powers commerce operations. The GraphQL Storefront API optimizes data fetching, improving performance and enabling seamless integrations. This modern, API-first approach allows for personalized experiences, custom checkout flows, and easy third-party integrations.
+## Headless


"Custom Headless"

jamesqquick added 4 commits January 13, 2026 11:25

add catalyst features doc and update messaging between stencil and ca…

630fd26

…talyst

Add supported features docs and update choosing a storefront details

5a1386d

update wording on feature support

9e275c7

remove question mark from header

f226222

jamesqquick requested review from CNanninga, chanceaclark, chris-nowicki and matthewvolk January 14, 2026 19:44

chris-nowicki previously approved these changes Jan 14, 2026

View reviewed changes

add line item for sitemaps

4d8bb36

jamesqquick dismissed chris-nowicki’s stale review via 4d8bb36 January 14, 2026 20:59

add line item for in app search

f79291a

chanceaclark reviewed Jan 14, 2026

View reviewed changes

migueloller reviewed Jan 15, 2026

View reviewed changes

jamesqquick and others added 6 commits January 15, 2026 13:23

Merge branch 'main' into CATALYST-1681-add-feature-support-page

95f3f03

Update docs/storefront/catalyst/features/supported-features.mdx

e08fbe4

Co-authored-by: Miguel Oller <[email protected]>

Update docs/storefront/catalyst/features/supported-features.mdx

c4a9bb1

Co-authored-by: Miguel Oller <[email protected]>

add additional details for deplyoying catalyst

f8712ea

add line item for abandoned cart

0325176

added link to session sync documentation

5fc2888

jamesqquick commented Jan 15, 2026

View reviewed changes

CNanninga requested changes Jan 15, 2026

View reviewed changes

jamesqquick added 3 commits January 15, 2026 16:25

updated language and ordering of supported features

2fe96d7

update wording on pci compliance

6e7f3d4

update wording on graphql api limitations with catalyst

5ff4d65

		@@ -0,0 +1,57 @@
		# Feature Support

		Here is a list of BigCommerce platform features and whether or not they are supported and to what extent in Catalyst. One important note when considering Catalyst feature support is that Catalyst is focused on working with the [GraphQL Storefront API](/docs/storefront/graphql) and not the [REST Management API](/docs/rest-management). This means that some features cannot be supported in Catalyst until the functionality is available in the GraphQL Storefront API.


		<Callout type="info">Since you have complete ownership of the code with Catalyst, you can custom build implementations of yellow and red features if you would like to.</Callout>

		\| Feature \| Supported \| Notes \|

[CATALYST-1681] Add Supported Features #1236

Are you sure you want to change the base?

[CATALYST-1681] Add Supported Features #1236

Uh oh!

Conversation

jamesqquick commented Jan 14, 2026 • edited by atlassian bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What changed?

Release notes draft

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

migueloller left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

jamesqquick commented Jan 14, 2026 •

edited by atlassian bot

Loading