sumhound-briefing-2026-26 · Jun 22, 2026–Jun 28, 2026
What commerce operators should check this week.
A free, source-backed operating brief. This issue contains only reviewed changes with a concrete audience and action; empty sections are stated instead of filled with unverified news.
GraphQL Admin API 2026-10 removes priceRule from DraftOrderDiscountNotAppliedWarning. Integrations must use discountTitle and discountCode when handling draft-order discount warnings.
Admin API 2026-07 adds coversAllItems for authorized app-owned shipping profiles, allowing one profile to apply rates to every shippable variant and override explicit product assignments.
Discount UI extensions can now set whether app discounts apply to one-time purchases, subscriptions or both and limit the number of discounted subscription cycles.
Before adopting Admin API 2026-10, replace priceRule title and code reads in draft-order mutation response handling.View reasoning →
Shopify
Review any app-owned profile assignment logic and enable coversAllItems only when its rates should override assignments for the entire shippable catalog.View reasoning →
Shopify
If merchants configure subscription discounts through an extension, expose the two fields and test cycle-limit behavior at checkout before enabling them.View reasoning →
Shopify
Evaluate moving ERP references or handling instructions into validated transfer metafields and verify duplicate-transfer behavior before changing inventory workflows.View reasoning →
Shopify
Update logic that assumes every Market is regional, and test catalog availability and pricing output before creating channel-specific Markets.View reasoning →
Shopify
If label buying is part of fulfillment automation, add permission and terms checks, poll asynchronous results, and handle purchase failures before using the new mutation.View reasoning →
Shopify
Create or declare definitions for every app metafield used by customer-account extensions or headless storefronts and explicitly grant Customer Account API access.View reasoning →
Shopify
Where checkout rules rely on cross-merchant buyer context, assess the new input while applying data minimization and null-safe behavior for missing metafields.View reasoning →
Amazon
Refresh Product Type Definitions metadata and update listing validation for newly required attributes or changed enumeration values before retrying affected submissions.View reasoning →
Amazon
If you support IVP-enrolled US sellers, allow Amazon's new audience enum values in listing create and update payloads; otherwise no action is required.View reasoning →
Amazon
Refresh Product Type Definitions metadata, compare required fields and accepted values, and update Listings Items API or JSON feed validation for affected product types.View reasoning →
Amazon
Compare affected product-type metadata with listing payload validation and update newly required attributes or removed enumeration values before resubmitting failed listings.View reasoning →
One source-backed weekly email for the platforms you choose. Confirm by email; unsubscribe at any time. The public archive and analyzers remain free with no signup.