Short answer: Yes, since October 13, 2026. The Matrixify Products sheet now has Published: <Channel> and Published At: <Channel> columns for every sales channel on the store (Online Store, Point of Sale, Shop, Buy Button, Hydrogen, marketplace channels, and so on), and Variant Published: <Channel> columns on the variant rows. Collections have had Published: <Channel> columns since September 2026. Before October 2026, Matrixify product publishing covered only the Online Store and Point of Sale.
Altera uses the same columns. It has had product Published: <Channel> columns since July 2025, and since October 2026 it also has Published At: <Channel>. Because Altera reads and writes the same files as Matrixify, a products file with these columns imports into either app without changes.
Matrixify and Altera sales channel columns#
| Feature | Matrixify | Altera |
|---|---|---|
Product Published: <Channel> columns | Since October 2026 | Since July 2025 |
Product Published At: <Channel> columns | Since October 2026 | Since October 2026 |
Variant Variant Published: <Channel> columns | Since October 2026 | Since May 2026 |
Collection Published: <Channel> columns | Since September 2026 | Since January 2026 |
| Channels in the export | The channels you pick | Every channel installed on the store |
Old Published, Published At, Published Scope columns | Removed from the export, still imported | Not in new exports, kept in saved exports, still imported |
In Matrixify, the channel columns are in the “Sales Channels” export group. This group is off by default and is marked as slow. Matrixify also added the export filters “Published” (by channel) and “Published At: Online Store”.
For per-variant columns, see Matrixify variant sales channel publishing.
How the columns work#
Shopify keeps a separate publication record for each product on each sales channel. A product can be on the Online Store and not on Shop, or on Hydrogen and not on Buy Button. The spreadsheet has one column per channel:
Published: <Channel>:TRUEpublishes the product on that channel,FALSEunpublishes it. In Altera, a blank cell is skipped, so it never unpublishes a product.Published At: <Channel>: the publish date on that channel. A future date schedules the publication on channels that support scheduling, such as the Online Store. On channels that do not support scheduling, such as Shop and Point of Sale, both apps show a warning for that value.- Old columns:
Published,Published At, andPublished Scopestill import in both apps. When the file also has aPublished: <Channel>column, both apps ignore the old columns.
The same pattern applies to collections on the Collections sheet, and to variants with Variant Published: <Channel> and Variant Published At: <Channel> on the variant rows.
The same file works in both apps#
Altera reads and writes the same spreadsheet format as Matrixify. A Matrixify products file with Published: <Channel> columns imports into Altera unchanged, and an Altera export imports into Matrixify. What carries over:
- The column names:
Published: <Channel>,Published At: <Channel>,Variant Published: <Channel>, andVariant Published At: <Channel>. - The same identifiers:
HandleandIDto match products, aCommandcolumn withMERGE,NEW,UPDATE, andDELETE, and one row per variant. - The same export and import flow: filter, download a spreadsheet, edit it, upload it back.
When per-channel columns are useful#
- Headless storefronts. During a move to Hydrogen, you can put some products on Hydrogen and keep them off the Online Store, or the other way round.
- Marketplace launches. Publish a selected set of products to Facebook & Instagram, Google & YouTube, or TikTok in one import.
- B2B and wholesale. Keep wholesale-only products on a private channel and off the public storefront.
- Buy Button embeds. Put a few products on Buy Button and keep the rest off.
- Staged rollouts. Launch on the Online Store first and on marketplace channels later, with a scheduled date in
Published At: <Channel>where the channel supports it.
How to publish products to sales channels with Altera#
- In Altera, click Export and select Products. In the Sales Channels field category, tick “Published on Sales Channel” (and “Variant Published on Sales Channel” if you also want the variant columns). Use the export filters to narrow the export by handle, vendor, or tag.
- Open the exported spreadsheet. There is one
Published: <Channel>column for each channel installed on your store, and each product row shows its current state. - Set a cell to
TRUEto publish the product on that channel,FALSEto unpublish it, or leave it blank to keep the current state. - Delete the rows for products you do not want to change. Keep the
Handlecolumn (orID) as it is so each row matches the right product. - Upload the file to Altera, check the product count in the analysis preview, and start the import.
You can also start from a Matrixify products export that has the channel columns. Altera imports it unchanged.
Example: five channels on two products.
| Handle | Published: Online Store | Published: Shop | Published: Hydrogen | Published: Buy Button | Published: GraphQL App |
|---|---|---|---|---|---|
| bench-00098 | TRUE | TRUE | TRUE | FALSE | TRUE |
| crate-00045 | TRUE | FALSE | FALSE | FALSE | TRUE |
The same column pattern works for any channel installed on your store, for example Published: Facebook & Instagram or Published: Google & YouTube.
Collection level#
Collections use the same Published: <Channel> columns on the Collections sheet. See the collection sales channel publishing changelog for the release notes.
Variant level#
Variant Published: <Channel> columns on the variant rows publish or hide one variant on one channel without changing the product. Since Shopify’s 2026-10 API, this includes Point of Sale. See the variant sales channel publishing page for the column reference, and the bulk variant publishing guide for examples across many products.
See the product field reference for every publishing column.
Rules Altera follows for sales channel publishing#
TRUEpublishes,FALSEunpublishes, and blank is skipped. A blank cell never unpublishes a product.- Altera reads the channels installed on your store and exports a
Published: <Channel>column for each one, so a channel you install later gets a column on the next export. - A future date in
Published At: <Channel>schedules the publication on channels that support scheduling. On other channels, Altera shows a warning. - The old
Published,Published At, andPublished Scopecolumns still import. When the file also hasPublished: <Channel>columns, Altera ignores the old columns. - A variant can only be published on a channel where its parent product is published.
Variant Published:columns narrow a product’s visibility and never widen it.
Frequently asked questions#
Does Matrixify support sales channel publishing?
Yes, since October 13, 2026. The Matrixify Products sheet has Published:Does Altera support the same columns?
Yes. Altera has had product Published:What happens to the old Published, Published At, and Published Scope columns?
Matrixify removed them from its export, and new Altera exports do not include them (saved Altera exports keep them). Both apps still import them, and both ignore them when the file has a Published:Can I schedule a product to be published on a channel?
Yes, on channels that support scheduling, such as the Online Store. Put a future date in the Published At:Which channels does Altera export?
Altera exports a Published:Can I keep using Matrixify and use Altera for some jobs?
Yes. Both apps read the same files, so you can run them side by side and move a file from one to the other without changes.See the full Altera vs. Matrixify comparison for the differences between the two tools, or the FAQ for more common questions.
