PIM 1.10 Release: Bulk imports 1/12/26

Bulk imports  – Overview

This release significantly strengthens bulk import and batch upload flows for:

• Attributes

• Attribute groups

• Product templates

• Products & variants

Focusing on reliability, observability, and consistency across APIs, UI, and error handling.

New and enhanced capabilities

• Unified bulk-upload platform across entities

  • Introduced a consistent backend framework for bulk uploads for attributes, attribute groups, templates, products and variants.

  • Added pre‑processed and post‑processed status APIs (by feed ID) so you can see exactly where a feed is (import, ready, commit).

  • Exposed explicit “readying/committing” states and progress so long‑running operations are more transparent.

  • Enabled partial processing for large feeds so valid rows can complete even when some rows fail, with clear partial‑success reporting.

• Richer status & reporting for attribute, group and template feeds

  • Added detailed status for attributes, attribute groups and templates, including per‑sheet metadata and commit status per feed.

  • Extended erroneous report APIs so attributes, groups and templates return structured and consistent error details (IDs, sheet, row, error type).

• Improved download and re‑import compatibility

  • Aligned export headers with import headers for attribute groups and templates so exported spreadsheets can be used directly for re‑imports.

  • Included missing columns (like template version) in exports to keep bulk updates tied to the correct version.

Data quality, validation and error handling

• Attributes & attribute groups

  • Enforced mandatory fields (e.g. name/scope, display name) and blocked empty rows from being treated as successful imports.

  • Improved validation for large attribute files and attributes with complex structures (boolean defaults, custom types, child attributes, 2D/3D values), returning clear, row‑level errors instead of silent failures or 500s.

  • Fixed “multiple-of” and other validation rules so attributes created via bulk import behave the same as attributes created via the UI.

  • Validated site IDs and auto‑assigned UUIDs during attribute‑group imports to prevent bad data from entering the system.

• Templates

  • Stabilised template bulk imports where files contain mixed site IDs or large numbers of templates, so commits no longer fail or time out unexpectedly.

  • Corrected incorrect error counts and partial‑processing metrics in template status and feed reports.

  • Hardened template import feed‑report APIs to handle null/invalid data gracefully, improving resilience for downstream tooling.

• Products & variants

  • Enforced stricter validation for product/variant imports, ensuring all attribute‑value updates are checked and reported clearly.

  • Fixed issues where erroneous reports for products/variants had wrong or missing IDs, or incorrect error counts.

  • Improved behaviour when imports fail, so products and variants do not end up in inconsistent states and errors are surfaced where users expect them.

API and UX consistency

• Consistent status, filters and APIs

  • Standardised import status labels across attributes, attribute groups and templates so search filters and feed lists use the same terminology.

  • Normalised product & variant feed status APIs around a shared “items” response format to make integrations simpler and less brittle.

  • Cleaned up commit and erroneous‑report endpoints for products and variants, using consistent URL patterns and structures.

• Better visibility into feed health

  • Fixed issues where feed status and error counts only updated after a hard page reload; feeds now update correctly in the UI as processing progresses.

  • Improved status filters and listing views for bulk imports so users can reliably filter by import status and batch type.

• Improved user experience for bulk flows

  • Ensured buttons and actions (e.g. download, discard draft, bulk operations) appear consistently for the right states and entities.

  • Refined various mapping flows (recommended/provided mappings, sheet names, header consistency) so what you upload is what gets validated and mapped, without confusing duplicates or missing fields.

Net impact

• More predictable and transparent bulk imports for attributes, attribute groups, templates, products and variants.

• Stronger data validation and error reporting, so issues are caught early and are easier to debug.

• A more consistent API and UI surface across all bulk and batch workflows, simplifying integrations and support.

Support tickets Resolved

• Bulk Import > Attributes, Groups & Templates #1702 

• Bulk Import is cross mapping two fields 

• Make Field Required; Media  

• Custom Attribute > Add nested attribute info to property info label 

0 Votes