Changelog

Shopify API 2026-10 Update: Multiple Barcodes, New Fulfillment Status, Accurate Counts

October 1, 2026

DataEase now uses Shopify Admin API version 2026-10. Most files and saved tasks keep working as before. This page lists what changed for you.

Products: multiple barcodes per variant

A variant can now have up to 20 barcodes, each with an optional type: UPC, EAN, ISBN, GTIN, ASIN, NS_PID.

  • The existing Barcode column (barcode) still means the first barcode of the variant.
  • New column All barcodes (barcodes) holds the full list: TYPE:value; TYPE:value. The type is optional (value alone). A value that contains a colon but has no type is written as :value.
  • Import with All barcodes: the cell sets the complete list. An empty cell removes all barcodes.
  • Import with Barcode only: the cell replaces the first barcode and keeps the others. An empty cell removes the first barcode.
  • Filling both columns in the same row is a row error.
  • Shopify’s barcode checks (checksum, length, duplicates, too many barcodes…) are shown in the import log.
  • Order line items (lineItemVariantBarcode) are matched by any of the variant’s barcodes.

Details: Products, Variants.

Orders

  • New fulfillment status “Fulfillment not required” (FULFILLMENT_NOT_REQUIRED). Orders with nothing left to fulfill (for example, all items were cancelled or refunded before fulfillment) show this status in exports. Previously they showed UNFULFILLED. Saved exports and schedules filtered by Unfulfilled may now return fewer orders. The new status is not yet offered as a filter option.
  • Several tracking numbers: when creating orders, all tracking numbers in the fulfillment tracking number column are imported. Separate them with commas or new lines (the format the export produces).
  • Shipping address on update: the address is sent to Shopify only if it actually changed. Changing the shipping address of an order that isn’t fully fulfilled can make Shopify recalculate the order’s taxes and totals. The import log shows a warning in that case.

Details: Orders.

Export filters by metafields

Shopify now rejects filters on metafields that aren’t enabled for filtering.

  • DataEase removes such conditions automatically (they had no effect before either) and shows a warning on the export page.
  • If a condition can’t be removed safely (it’s combined with OR or placed inside a group such as NOT), the export stops with an explanation so you can fix the filter.
  • Tip: turn on filtering for the metafield definition in Shopify admin (Settings → Custom data).

Details: Export guide.

Accurate “Found N items” counts

The preview count is now accurate for customers, pages, and companies with filters. Before, it showed the total without filters. Large filtered results for these entities show at least 2,500. See Shopify limits.

Customers

Addresses are now created, updated, and deleted one by one (by Address ID). When a new-customer row matches an existing customer by email or phone, its addresses are added to the existing ones instead of replacing the whole list. See Customers.

Collections and translations

  • Collections: integer metafield conditions now accept values beyond ±2,147,483,647. See Collections.
  • Translations: the Metafield resource type is no longer offered for new exports (Shopify deprecated it). Existing exports that use it keep working. See Translations.