Invalid metafield values used to block entire rows from being imported. Now they’re handled gracefully - the row still gets created or updated, and any metafields that couldn’t be saved are reported as warnings.
🚀 What’s New # Warning status – import results now show a “Warning” badge when an item was saved but some data was skipped. 🔧 Improvements # Metafield errors no longer block imports – invalid metafields are skipped individually instead of failing the entire row. One-by-one retry – when a batch of metafields fails, each is retried individually so valid ones still get saved. Consistent error handling – products, collections, articles, and companies all handle invalid metafields the same way.
A new export option makes it easier to move data between stores by letting you choose how file and image references are written: as the file name (default, good for re-import) or as the CDN URL (e.g. https://cdn.shopify.com/...).
🔧 Improvements # File name format – In Advanced options when creating an export, File name format lets you pick File name (default) or CDN URL for file references. Use file names when you need portable values for the destination store; use CDN URL when you need direct links. Applies to metaobject file/image fields and to file reference metafields on products, orders, and other object types.
Product imports now validate that your metafield columns are targeting the correct resource type, helping you catch mistakes before they happen.
🚀 What’s New # Owner type validation – when you upload a product file, Altera checks if each metafield column matches an existing metafield definition for the correct owner type (product or variant). Helpful suggestions – if you use a product metafield column but the definition only exists for variants (or vice versa), you’ll see a warning with the correct column header to use. Pre-import detection – issues are caught during file analysis, before your import starts.
Handle filters for product exports now support comma-separated values, making it easier to export multiple products at once.
🔧 Improvements # Equals any of – Provide a comma-separated list of exact handles to match (e.g., blue-shirt,red-pants,green-hat). Contains any of – Provide a comma-separated list of partial matches (e.g., shirt,pants matches blue-shirt, cargo-pants, etc.). Filter documentation – Updated the Understanding Filters guide with handle filter examples.
Altera CLI 0.3.0 gives you more granular control over your exports with individual field selection.
🚀 What’s New # Individual field selection – prefix any field name with + to export only the columns you need (e.g., products:+id,+handle,+title). Mixed selection – combine field groups with individual fields in the same export (e.g., products:general,+metafield_custom_sizing). --list-fields option – discover all available fields for any resource, organized by field group. 🔧 Improvements # Flexible syntax – existing field group commands continue to work unchanged; the new + prefix is additive. Clear validation – invalid field names now show a helpful error message with a suggestion to use --list-fields.
Scheduled jobs now show times in their configured timezone, removing confusion when working across different geographies.
Previously, scheduled job times were converted to your browser’s local timezone. This made it harder to coordinate when team members in different locations looked at the same job. Now all times display in the timezone the job was configured with, so everyone sees the same time.
🔧 Improvements # Timezone display – the job detail page now shows which timezone the schedule uses. Consistent time display – all schedule times appear in the job’s configured timezone rather than converting to your local timezone. Team coordination – distributed teams can now see exactly when a job will run without mental timezone math.
Remote spreadsheet downloads now have more time to complete, preventing timeout errors on larger file transfers.
🔧 Improvements # HTTP timeout – increased to two minutes for downloading remote spreadsheets, ensuring larger files have enough time to transfer successfully.
Importing discounts across multiple stores just got easier. You can now use the same discount file on stores with and without subscription apps installed.
🔧 Improvements # Subscription fields – Purchase Type and Recurring Subscription Limit columns are now ignored when importing to stores without a subscription app, instead of failing with an error. Cross-store compatibility – Use the same discount export file across all your stores without needing to remove columns first. Previously, importing discounts with subscription-related columns onto a store without a subscription app would fail with error DISC022. Now these fields are simply skipped-the discount is created with all other settings applied normally.
Translations now support imports alongside the existing export functionality. Export your translations, edit them in Excel or Google Sheets, and import them back to update translated content across your store.
🚀 What’s New # Translation imports – create, update, or delete translations for products, collections, pages, metafields, and 20+ other resource types. Command column – control how each row is processed with MERGE, NEW, DELETE, or IGNORE commands. Existing translation check – the NEW command skips translations that already exist, preventing accidental overwrites. 🔧 Improvements # Parent tracking – import results now show the parent handle for nested resources like metafields, making it easier to identify what was updated. Better error messages – clearer feedback when translations fail to import, with specific error codes for troubleshooting. See the Translations reference for full details on import requirements and available commands.
You can now manage blog metafields directly through blog post (article) imports and exports, similar to how variant metafields work for products.
🚀 What’s New # Blog metafield exports – when exporting articles, select the “Blog Metafields” category to include metafields defined on each article’s blog. Blog metafield imports – use columns with the Blog Metafield: namespace.key [type] header format to set metafields on blogs during article imports. 🔧 Improvements # Smart deletion handling – when importing multiple articles from the same blog, blank blog metafield values won’t delete metafields that were set by earlier rows in the same import.
