Each Headless storefront supports unique resource publishing and order attribution

Published

This summary was written by ShopDigest AI from Shopify Changelog’s report. Read the full story ↗

We’re releasing a feature that allows you to publish different products and collections to each of your Headless storefronts. This means if you hav…

Overview

Shopify now lets merchants publish different products and collections to each Headless storefront, treating each storefront as a unique channel. This replaces the previous single 'Headless' channel with individual storefront names in the admin and orders pages. API calls must now use the publicationId for each specific Headless storefront instead of the Headless sales channel app.

Key Details

  • Each Headless storefront can have its own set of published products and collections.
  • Admin now shows the storefront name as the publishing destination instead of 'Headless'.
  • Orders page and other admin areas reflect the same per-storefront channel distinction.
  • API calls using publishablePublish must pass the publicationId for each target Headless storefront.

Frequently asked questions

How do I publish different products to different Headless storefronts?

In the Shopify admin, each Headless storefront now appears as its own named channel. You can select a specific storefront as the publishing destination for products and collections, allowing different storefronts to have different catalogs.

What changed with publication IDs for Headless storefronts?

Previously, API calls used the publicationId for the Headless sales channel app. Now, you must pass the publicationId for each individual Headless storefront you want to publish to, since each storefront is treated as a unique channel.

How does the Orders page reflect Headless storefronts?

The Orders page and other admin areas now display the given name of each Headless storefront instead of a generic "Headless" label. This makes it easier to identify which storefront an order belongs to.

About this story

Published
17 Jan 2025
Originally published at