For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
  • Getting Started
    • Introduction
    • Getting Started
    • Tia — Operations Assistant
    • Architecture
    • Security Architecture
  • Onboarding & Plans
    • Onboarding Overview
    • Plans & Subscriptions
    • Tia Credits
  • Tenancy & Governance
    • Roles & Members
    • Audit Log
    • Notifications
    • Economic Operators
  • Authoring Studios
    • Content Studio
    • Theme Studio
    • Advanced Studio (Track B)
  • Product Module
    • Products
    • Custom Fields
    • Global Search
    • Identifiers
    • Product Import
    • Bulk Editing
    • Bulk Updates
    • Resolver & GS1 Digital Link
    • GS1 Digital Link Contract
  • Localisations
    • Overview
    • Market Packs
    • Multilingual Content
  • Domains & Custom Hostnames
    • Domain Architecture
    • Resolver Domain Flow
    • Custom Hostname Setup
    • DNS Setup Guide
    • Resolver & Passport Rendering
    • Custom Hostname Lifecycle
    • Troubleshooting
  • Passports
    • Overview
    • Passport Operations
    • Lifecycle States
    • Controlled Update & Break-Glass
    • Content & Templates
    • Themes & Presentation
    • Consumer Experience
    • Publication Lifecycle
    • Brand Setup & Readiness
    • Drafts
  • Passport Intelligence
    • Passport Intelligence
    • Intelligence Overview
    • Scan Visibility
    • Trust Signals
    • Engagement Insights
    • Investigation Timelines
    • Data & Privacy
    • Roadmap
  • Minting
    • Overview
    • Lifecycle
    • Architecture
    • Limits & Performance
    • Token Preview
    • Exports & Print Jobs
    • Carrier Output Profiles
    • Bring-Your-Own Serials
    • Security
    • FAQ
  • API Reference
    • API Credentials Guide
    • API: Credentials
    • API: Products
    • API: Identifiers
    • API: Import
    • API: Batches
    • API: Attachments
    • API: Bulk Updates
    • API: Minting
    • API: Resolver
    • API: Search
On this page
  • What It Does
  • Who It’s For
  • How It Works
  • Selecting Products
  • The Bulk Edit Grid
  • Eligible Fields
  • Saving
  • Validation Warnings
  • Limits & Notes
  • FAQ
Product Module

Bulk Editing

Was this page helpful?
Previous

Bulk Updates

Next
Built with

What It Does

Bulk editing lets you modify attribute values across multiple products simultaneously, without opening each product individually.

Who It’s For

Brand administrators who need to update shared attributes (e.g. compliance fields, descriptions) across a selection of products.

How It Works

Selecting Products

  1. In the Product Library, tick the checkbox on each product you want to edit (up to 100 at a time).
  2. Click Bulk edit to open the bulk editing page.

The Bulk Edit Grid

The grid displays one row per selected product. You can:

  • Pick visible columns using the column picker — choose which attribute fields to show.
  • Edit cells directly — all visible attribute cells are editable inline.
  • Bulk apply a value — set a single value across all selected rows for a given attribute column.

Eligible Fields

Only model-level attributes with compatible data types (text, number, integer, boolean, date/time, URL) appear in the column picker. Identifier fields (SKU, GTIN, EAN, UPC) are not available for bulk apply — they must be edited in Product Detail to preserve audit history.

Saving

When you save:

  • Each product is updated individually; per-row outcomes are displayed.
  • Success rows show a green tick.
  • Warning rows indicate a value-set validation warning (the save still proceeds; warnings are informational).
  • Error rows indicate a failure — you can review the error message and retry.

Validation Warnings

Warnings are surfaced when an attribute value does not match a predefined value set. Warnings never block a save; they are advisory only.

Limits & Notes

  • Maximum 100 products per bulk edit session.
  • Each save request processes up to 50 products per batch.
  • Identifier fields are excluded from bulk apply by design.
  • Attribute patches are merged server-side; unchanged fields are preserved.

FAQ

Why can't I bulk-edit SKU or GTIN?

Identifier changes create audit history entries (active/retired tracking). This requires the dedicated identifier editing flow in Product Detail.

What happens if some rows fail?

Successful rows are saved immediately. Failed rows display an error message — you can correct the value and retry without losing other changes.

Are warnings stored on the product?

No. Validation warnings are transient and displayed at save time only. They are not persisted on the product record.