Customer reference metafields now work just like other reference types - Altera resolves them to something human-readable instead of raw Shopify GIDs.
🚀 What’s New # Customer references export as emails – customer reference metafields now show the customer’s email address instead of a GID. Import by email – importing a customer reference? Just use the email address and Altera will find the right customer. List support – list.customer_reference works too, with comma-separated emails on export. 🔧 Improvements # Graceful fallback – if a customer has no email on file, the GID is kept in the export so no data is lost. Cross-store friendly – export from one store and import to another using email addresses instead of store-specific IDs.
You can now move translations between Shopify stores. Export your translations from one store, then import the same file into a different store - Altera uses resource handles to automatically find the matching products, collections, pages, and other resources on the target store.
🚀 What’s New # Cross-store translation transfers – export translations from a source store and import them directly into a destination store without manual ID remapping. Handle-based resource matching – during import, Altera verifies each resource ID against the target store and falls back to handle lookup when IDs don’t match. Collection filters – filter translation exports by collection handle or collection type (manual vs smart), helpful for exporting translations for a specific collection or group of collections. Metaobject type filter – filter translation exports by metaobject type, helpful when you only need translations for a specific type like “color” or “material”. Product option value translations – exports now include option value translations with structured handles like 1.Small for easy identification. 🔧 Improvements # Handles for all resource types – the Handle column now covers products, collections, pages, blogs, articles, menus, metaobjects, metafields, product options, and option values. Grouped metaobject types – the metaobject type filter groups custom and standard types into separate sections for easier browsing. Responsive filter layout – filter rows now wrap properly on smaller screens. See the Translations reference for full details on handle formats and cross-store import workflows.
Customer exports now have two separate date filters for orders, giving you more control over which customers you export.
🚀 What’s New # Order date filter – matches customers who placed any order during the specified period, useful for finding all customers active in a date range. Last order date filter – matches based on the customer’s most recent order only, useful for finding customers who haven’t ordered recently or whose last purchase was within a specific window.
Need to find empty collections or ones with hundreds of products? You can now filter collection exports by product count.
🚀 What’s New # Product count filter – Smart and manual collection exports now support a “Product count” filter with equals, not equals, greater than, and less than operators. Find empty collections – Use “Product count equals 0” to quickly export only collections with no products.
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 at support@getaltera.com.
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.
