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.
Unit price imports just got simpler. You can now use individual columns for each unit price field instead of dealing with JSON formatting.
🚀 What’s New # Separate columns – use dedicated columns for Unit Price Total Measure, Unit Price Total Measure Unit, Unit Price Base Measure, and Unit Price Base Measure Unit. Export field group – select the new Unit Price Columns group when creating product exports to get the separate column format. Clear unit prices – set either measure value to 0 to remove unit pricing from a variant. 🔧 Improvements # Backwards compatible – the original JSON format in Variant Unit Price column still works exactly as before. Pre-import validation – file analysis now validates separate column values before import starts. Better error messages – new error code PRD031 helps identify issues in the separate columns, while PRD019 covers JSON format errors. 📝 How It Works # Instead of JSON:
Activity exports just got more useful. You can now include order details when exporting order-related events, and filter your exports by the type of action that occurred.
🚀 What’s New # Order fields in activity exports – include order ID, name, email, phone, tags, total price, payment status, fulfillment status, and processed date when exporting order-related events. Verb filter – filter activity exports by action type such as create, update, destroy, refund_created, and more. 🔧 Improvements # Phone formatting – order phone numbers in activity exports now use the same formatting options as order exports. Status formatting – payment and fulfillment status fields display in lowercase format consistent with order exports. ⚠️ Heads-up # Verb filter is client-side – when using the verb filter, export counts will not be available since filtering happens after data is retrieved.
You can now export your Shopify data directly to Google Sheets or Google Drive-no more downloading files and uploading them manually.
🚀 What’s New # Google Sheets exports – send data directly to a Google Sheet that updates automatically with each scheduled run Google Drive exports – upload export files to a specific folder in your Google Drive for easy sharing and backup Google Drive imports – import spreadsheets directly from Google Drive without publishing them to the web 🔧 Improvements # Remote Connections – manage all your Google, FTP, and SFTP connections in one place under Settings > Remote Connections Granular permissions – Altera only accesses the specific Google Drive folders or sheets you authorize, not your entire Drive
We’ve added new filtering options for product exports that let you target products based on whether they have a Shopify product category assigned.
🚀 What’s New # Category filter – filter product exports by category ID with four options: is equal to, is not equal to, is set, and is not set. Is set / Is not set – quickly find products that are missing a category or already have one assigned.
You can now control the URL handle for metaobject definitions when importing and exporting.
🚀 What’s New # Capability: Online Store URL Handle – new field for metaobject definitions that sets the URL path for published entries. On import, the handle defaults to the definition’s type but can be overridden with a custom value. On export, the configured URL handle is now included in the export data.
Metaobject definitions that reference other metaobjects can now be exported from one store and imported into another.
🚀 What’s New # Cross-store metaobject definitions – field validations that reference other metaobject definitions now use portable type handles instead of store-specific GIDs. Flexible import format – imports accept both comma-separated type handles (author, brand) and legacy GID format for backwards compatibility. 🔧 Improvements # Cleaner exports – multiple definition references now export as author, brand, store_location instead of JSON arrays. 🐛 Fixes # Reference validation – importing a definition that references a non-existent metaobject definition now shows a clear error message (MOBD006) instead of failing silently.
