Finding a specific job in your history just got easier. Import and export jobs now receive more descriptive titles based on the object types, fields, and filters in each job.
🔧 Improvements # Descriptive job titles – Jobs now get titles like “Export Active Products” or “Update Prices and Inventory” instead of generic names, making it easier to tell them apart at a glance. Your titles are kept – If you name a job yourself, your title is never overwritten. ⚠️ Heads-up # Odd titles? – Titles are generated automatically and may occasionally miss the mark. If you spot something strange, let us know.
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.
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.
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.
Scheduled jobs just got easier to manage. You can now view and edit schedule settings right from the job detail page.
🚀 What’s New # Scheduling card – job schedules now appear in a dedicated card on the job detail page, making it easier to find scheduling info. Inline schedule editing – click the edit button to change the frequency and start time without recreating the job. 🔧 Improvements # Clearer schedule display – the scheduling card shows the repeat frequency and next run time in plain language (e.g., “Runs every day. Next run is tomorrow at 3:00 PM”). Active/paused toggle – quickly enable or disable a schedule with the toggle button directly in the scheduling card.
Discount exports now support a full set of filters to help you export exactly the discounts you need, plus you can see the count before starting the export.
🚀 What’s New # Discount count preview – see how many discounts match your filters before starting the export. Status filter – filter by active, expired, or scheduled discounts. Method filter – export only automatic discounts or code-based discounts. Discount class filter – filter by order, product, or shipping discounts. Type filter – filter by percentage, fixed amount, free shipping, buy X get Y, or app discounts. Combines with filter – find discounts that can combine with order, product, or shipping discounts. Times used filter – filter discounts by how many times they’ve been used. Date filters – filter by starts at, ends at, created at, and updated at dates. Title and code filters – search discounts by title or discount code.
When jobs fail, it’s important to understand why. We’ve improved how errors are displayed so you can quickly identify the cause and take action.
🔧 Improvements # Specific error badges – Failed jobs now show the reason for failure, such as “API rate limit”, “Shop closed”, or “App uninstalled” instead of a generic “Error” label. Help article links – Clicking the help icon on a failed job now takes you directly to the relevant help article when available. Better error tracking – Jobs now track specific error codes, making it easier to diagnose issues and get support.
Metafield definitions that reference metaobjects can now be transferred between stores.
🚀 What’s New # Cross-store metafield definitions – validation values for metaobject_reference, list.metaobject_reference, mixed_reference, and list.mixed_reference types now use portable type handles instead of store-specific GIDs. Flexible import format – imports accept both type handles (features) and GID format for backwards compatibility. 🔧 Improvements # Cleaner exports – mixed_reference validations with multiple allowed types now export as comma-separated handles (camera_specs, speaker_specs) instead of JSON arrays.
