Last Week: Field Mapping for AI Transformers and SKU Filters (July 1, 2026)

New Features

• Field Mapping settings on channel fields — every field on a channel now has a Field Mapping panel where you pick how it gets filled: AI Auto Detect (the default, scans all source data), AI Fields (whitelist up to 10 specific source fields for the AI to read from), Fixed Value (always use the value you set), or Off (skip the field entirely). Great for pushing new listings through faster when you already know which source field carries which piece of data.
• SKU inclusion and exclusion filters — the source products and source product variants pages have a new SKU filter that accepts a regex to match on, plus an exclusion regex to hide matching SKUs. Useful for slicing large catalogs down to a specific product family or hiding a range from a view. The filters modal also got a lighter, simpler layout.

Improvements

• Smarter option matching that skips the AI when it can — Select and MultiSelect fields now try exact, normalized, and size-equivalent matches (so "X Small" matches "x-small", and "2XS" matches "XX-Small") before falling back to AI. If the AI comes back empty (or embeddings haven't been built yet for a channel), a loose text search runs as a fallback so the field still gets a candidate value.
• Better default view on the source products page — the page now opens filtered to unlisted + active products so you land on the sellable items that still need a listing, instead of the full catalog.
• Cleaner markdown rendering in dark mode — descriptions, notes, and other markdown content now render with proper contrast in dark mode.
• Clearer error messages on Field Prompt pages — Field Prompt (Work Order) pages surface more specific error messages when something goes wrong, so you know what to fix.

Bug Fixes

• Fixed marketplace order cancellations being ignored when the marketplace sent the US spelling "CANCELED" instead of "CANCELLED". Both spellings are now accepted, so Target+ (and any other marketplace using the US spelling) cancellations flow through cleanly.
• Fixed the metafield API returning the same definition data twice — once nested and once flattened at the top level. The response now carries a single nested metafield_definition, cutting response size and preventing stale flattened fields from drifting out of sync.

API Updates

Version: 5.12.0

New endpoints

• PUT /api/stores/:store_id/channels/:channel_id/listings/:listing_id/variants/:variant_id — introduced last week; this week's release adds support for updating a listing variant's configurable option values through the same endpoint.

Updated/removed endpoints

• GET /api/stores/:store_id/products and GET /api/stores/:store_id/products/:product_id/variants — two new filters: sku_matcher (regex; keeps products/variants whose SKU matches) and sku_exclusion_matcher (regex; drops those whose non-null SKU matches).
• Channel field responses (.../channels/:channel_id/fields/...) — mapping_type gained a new "off" option (existing values are still ai_auto_detect, fixed_value, ai_fields). The ai_fields_use_vision boolean was renamed to ai_fields_fallback_to_summary, and every field now includes a mapping_summary object (method, label, detail, inherited) so consumers can render the same summary the app uses. (Breaking on the rename.)
• Metafield value responses (.../metafields) — the flattened definition_name, definition_description, definition_data_type, and definition_ignored fields were removed. Read the same values from the nested metafield_definition object instead. (Breaking.)

Notes for API consumers

• This is a minor api version bump (5.5.0 → 5.12.0). Two breaking changes: the metafield-value flattened definition fields are gone (switch to the nested metafield_definition), and ai_fields_use_vision on channel fields was renamed to ai_fields_fallback_to_summary. Everything else — the new off mapping option, mapping_summary, the SKU filters, and the variant option updates — is additive.