You can now use WebDAV as a remote connection type for both imports and exports, joining FTP, SFTP, and HTTP as supported protocols.
What’s New # WebDAV connection type - connect to WebDAV servers using username and password authentication for both imports and exports. Automatic protocol detection - Altera tries HTTPS first, then falls back to HTTP, and remembers the result for future connections. Wildcard file downloads - use patterns like /orders/export_*.csv to automatically fetch the most recent matching file, just like FTP and SFTP. Automatic directory creation - directories are created on the server as needed when uploading export files.
Two new filters make it easy to export just the translations you need - like checkout strings for a specific theme, or only product titles across all locales.
What’s New # Theme ID filter - narrow translation exports to a specific theme using its ID. Field filter - filter translations by field key using equals, starts with, or not equals. Nested coverage - both filters apply to all nested resources including JSON templates, section groups, and locale content. Improvements # Translation filter warnings - the export UI now warns when a theme filter is combined with a non-theme data type.
You can now re-run any existing job straight from the command line with npx altera job run <jobId>. Set it up in a cron job, wire it into a CI/CD pipeline, or just trigger an export without opening the browser.
🚀 What’s New # job run <jobId> – triggers a new run on an existing import or export job. The job runs in the background on Altera’s servers. --wait flag – optionally wait for the job to complete before exiting, with live status updates. npx altera job run abc123 See the CLI documentation for full usage details. Update to the latest CLI with npx altera@latest.
When exporting data, metafield columns previously appeared in the order returned by the Shopify API, with no regard for which definitions were pinned in your store’s custom data settings. This made it harder to find the most important metafields in large exports.
🚀 What’s New # Smarter metafield column ordering – within each metafield group (e.g. product metafields, variant metafields), columns now appear in this order: SEO metafields (title_tag, description_tag) first, then pinned definitions ordered by their pinned position in your Shopify admin custom data settings, then remaining unpinned metafields, then Shopify standard metafields (namespaces starting with shopify) alphabetically. Applies to all object types – products, variants, orders, customers, collections, articles, blogs, companies, locations, and draft orders all respect the new ordering.
Exports now support two types of filters. Row-level filters control which records are exported - for example, only products created in the last 7 days. Metafield filters control which metafield columns appear in the file, so you can skip the ones you don’t need and get a smaller, more focused export.
🚀 What’s New # Metafield column filters – click the filter icon next to any metafield group to choose which metafields to include. Filter by namespace, key, or both – target exactly the metafields you care about. Per-group control – set different filters for product metafields, variant metafields, blog metafields, and more.
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.
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.
