Skip to main content
Migrate to Polaris

Version 2025-07 is the last API version to support React-based UI components. Later versions use web components, native UI elements with built-in accessibility, better performance, and consistent styling with Shopify's design system. Check out the migration guide to upgrade your extension.

Collections

Collection pages display information about product groupings, including the products within each collection, collection rules, and display settings. Extensions on these pages help merchants organize inventory and streamline collection management workflows.

  • Bulk product tagging: Automatically apply tags or metafields to all products within a collection based on custom rules or external data sources.
  • Collection sync: Synchronize collection data with external platforms like marketplaces, PIM systems, or marketing tools.
  • SEO optimization: Generate and apply SEO metadata, descriptions, or structured data for collections to improve search visibility.
  • Inventory alerts: Check stock levels across collection products and notify merchants of low inventory or out-of-stock items.
  • Collection analytics: Display performance metrics or generate reports for products within a collection from external analytics platforms.

Anchor to Collection details targetsCollection details targets

Use action and block targets to extend the collection details page. Add workflows and contextual information that help merchants manage collection relationships and access integrated collection data. Action targets open as modal overlays from the More actions menu, while block targets display as inline cards.

The examples demonstrate fetching data from Shopify's direct API or your app's backend.

Anchor to Collection details action targetCollection details action target

admin.collection-details.action.render

Renders an admin action extension on the collection details page. Merchants can access this extension from the More actions menu. Use this target to provide workflows that operate on collection data, such as syncing with external systems, exporting collection information, or managing credit terms.

Extensions at this target can access collection data through the data property in the Action Extension API. The action renders in a modal overlay, providing space for multi-step workflows, forms, and confirmations.

Anchor to Collection details action (should render) targetCollection details action (should render) target

admin.collection-details.action.should-render

Controls the render state of an admin action extension on the collection details page. Use this target to conditionally show or hide your action extension based on the collection's properties, such as status, configuration, or specific business requirements.

This target returns a boolean value that determines whether the corresponding action extension appears in the More actions menu. The extension evaluates each time the page loads.

Support
Components (0)
APIs (1)

Supported components

-

Available APIs

Anchor to Collection details block targetCollection details block target

admin.collection-details.block.render

Renders an admin block extension inline on the collection details page. Use this target to display contextual information, analytics, or status updates related to the collection without requiring merchant interaction to open a modal.

Extensions at this target can access collection data through the data property in the Block Extension API. Blocks appear as cards on the page and can show real-time data, insights, or quick actions, providing persistent visibility for information merchants need to see at a glance.


Anchor to Collection index targetsCollection index targets

Use action targets to extend the collection index page with bulk operations and workflows that help merchants manage multiple collections efficiently.

Anchor to Collection index action targetCollection index action target

admin.collection-index.action.render

Renders an admin action extension on the collection index page. Merchants can access this extension from the More actions menu. Use this target to provide workflows that operate on collection data, such as syncing with external systems, exporting collection information, or managing credit terms.

Extensions at this target can access collection data through the data property in the Action Extension API. The action renders in a modal overlay, providing space for multi-step workflows, forms, and confirmations.

Anchor to Collection index action (should render) targetCollection index action (should render) target

admin.collection-index.action.should-render

Controls the render state of an admin action extension on the collection index page. Use this target to conditionally show or hide your action extension based on the collection's properties, such as status, configuration, or specific business requirements.

This target returns a boolean value that determines whether the corresponding action extension appears in the More actions menu. The extension evaluates each time the page loads.

Support
Components (0)
APIs (1)

Supported components

-

Available APIs


  • Account for automated collections: Collections can be manual (fixed product list) or automated (rule-based). When displaying collection analytics or inventory status, remember that automated collection membership changes when products are added/removed or when their properties change. Check ruleSet to determine collection type.
  • Handle large product sets with pagination: Collections can contain thousands of products. When fetching collection products, use cursor-based pagination (for example, 50 products per page) and implement progressive loading for collections with more than 100 products to avoid timeouts and high query costs.
  • Show product rankings within collections: If your extension displays collection analytics, consider showing product performance rankings within the collection. This helps merchants optimize product ordering and identify which items drive collection sales.
  • Manage products in multiple collections: Products often belong to multiple collections. When building extensions that modify product metafields or tags based on collection membership, allow merchants to specify whether changes should be collection-specific or apply globally.
  • Consider collection availability: Collections can be published to specific sales channels (online store, POS, and others). When syncing collections to external systems, include publication context so the external system knows where the collection is available.

  • Single target per module: Each [[extensions.targeting]] entry in your TOML configuration maps one target to one module file.
  • Product pagination: The GraphQL API limits product queries to a maximum of 250 items per request.
  • Smart collection restrictions: Smart collections reject manual product additions. GraphQL returns an error: "Can't manually add products to a smart collection."
  • Block target visibility: Block extensions must be manually added and pinned by merchants before they appear.
  • Block collapse behavior: Returning null from a block extension collapses the block rather than removing it from the page. Blocks can't be fully hidden at runtime.

Was this page helpful?