You could already control permissions per API key. Now store owners can set data permissions that apply to everyone on the store, including the app UI and CLI.
What’s New # Store-wide data permissions - Control which data types (products, orders, customers, etc.) can be imported or exported on your store. Find it under Settings > Data permissions. Per-type controls - Set separate permissions for import and export. For example, allow exporting orders but block order imports. Full enforcement - Permissions are enforced on job creation, re-runs, file downloads, and CLI access so restricted data types cannot be accessed through any path. Owner-only access - Only the store owner can configure data permissions, keeping control with the right person.
You can now export multiple files at once by filtering on more than one filename.
What’s New # Filename filter - supports “equals any of” so you can enter a comma-separated list of filenames to export several files in one job. Multiple match - type banner.png, logo.svg, hero.jpg in the filename filter to match all three files at once.
Metaobject definition spreadsheets now include the Field: Name column, giving you visibility into the human-readable label for each field.
What’s New # Field: Name column - Metaobject definition exports now include the field name alongside the key, type, and description. Previously, only the field key was included. Import support - Set or update field names when importing metaobject definitions by populating the Field: Name column.
Translation imports now include support for variant metafields. Product variant metafields have the parent type set to ‘PRODUCT_VARIANT’ and the parent handle in the format product_handle.variant_title. Additionally, we’ve fixed an issue where multiple metafield translations without IDs were not importing correctly.
What’s New # Variant metafield translations - Metafields attached to product variants are now fully supported in both imports and exports. The Parent Handle uses the product_handle.variant_title format (e.g., cotton-tee.Small) to uniquely identify which variant the metafield belongs to. Cross-store variant metafields - Variant metafield translations can be transferred between stores using handle-based lookup. Fixes # Metafield translations - Multiple metafield translations now import correctly without IDs.
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.
