Exports now have two levels of filtering: the existing row-level filters that control which records are exported, and new metafield filters that control which metafield columns appear. You can also stop worrying about customer reference metafields showing up as cryptic GIDs.
🚀 What’s New # Metafield column filters – choose which metafields appear in your export by filtering on namespace, key, or namespace.key. Seven filter relations – equals, equals any of, not equals, starts with, ends with, contains, and does not contain. Per-group filtering – set different filters for product metafields, variant metafields, customer metafields, and so on. Customer reference metafields – these now resolve to email addresses on export and look up by email on import. 🔧 Improvements # Row filters vs column filters – row-level filters narrow which records you export, while metafield filters narrow which metafield columns appear, giving you smaller, cleaner files. Filtered badge – metafield groups with active filters show a badge so you can tell at a glance. Cross-store friendly – customer reference metafields export as emails, making store-to-store transfers easy. List support – list.customer_reference works too, with comma-separated emails on export. Saved configs – metafield filters are saved and restored when you clone a job or load a saved configuration.
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.
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.
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.
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.
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.
