Skip to content
Ecomwith
← Back to archive
2026-W36-ACoverage 8/31/2026 — 9/6/2026Viewing: Public edition

Ecommerce Weekly | Defaults are changing, and not choosing is a choice

August 31–September 6, 2026: Search Console AI control, AI Max auto-upgrade, Amazon FBM offer actions, Shopify cart MCP and CBP supply-chain comments

Several changes this week are about defaults. On August 31 Google opened Search Console’s AI-features control to every website worldwide, with “Include” as the default. Google Search campaigns using automatically created assets or campaign-level broad match began auto-upgrading to AI Max in September. Amazon US started acting on individual FBM offers for performance problems. Shopify stopped maintaining the old Storefront MCP cart tools. CBP opened comments on import supply-chain disclosures. A store that makes no choice accepts the platform’s default. Verifiable primary material was thinner this week than the previous two, so we keep five topics, and for each one state what the default is, what happens if you do nothing and what to read back this week.

Ecomwith Editorial · Ecommerce growth and AI-search researchVerified through 9/7/2026, 12:00:00 PM
Editorial linePublic

The week’s main story: platforms changed defaults, so confirm which one you accepted

Open the editorial line and its boundaries

In the week of August 31 several changes shared one feature: the platform changed a default. Search Console gave every site a switch to leave AI Overviews and AI Mode, with Include as the default. Google Search campaigns still using automatically created assets or campaign-level broad match began auto-upgrading to AI Max in September, with some features on by default. Amazon US began deactivating a single FBM offer when it puts Account Health at risk.

Two items are infrastructure. Shopify maintained the old Storefront MCP cart tools only until August 31, so apps building agent shopping need to move to UCP Cart MCP. CBP issued an advance notice seeking comments on import supply-chain disclosures, including whether online marketplaces and final recipients should be identified.

The useful work this week is to check each default: is it what I want, and if not, when it changes, who changes it and how the change is read back.

Verified facts

  • Google Search Console: as of August 31 the AI-features control is available to every site worldwide, with Include, Exclude or Inherit settings covering AI Overviews, AI Mode and generative AI in Discover.
  • Google Ads: Search campaigns using automatically created assets and campaign-level broad match auto-upgrade to AI Max from September; DSA auto-upgrade was pushed in June to begin February 2027.
  • Amazon US: from August 31, if an FBM offer puts Account Health at risk, Amazon temporarily deactivates that offer without affecting other listings or overall Account Health.
  • Shopify: get_cart and update_cart on Storefront MCP were maintained until August 31; the replacement is UCP Cart MCP.
  • CBP: on September 2 it issued an advance notice on heightened import disclosures for supply-chain visibility, with comments due December 1; it is not a rule in force.
Evidence note: primary material was thinner this week, so we keep five topics. The August 31 version of TikTok’s Branded Content Policy could not be verified from the official text and is left out.

Impact read

Macro judgment: defaults decide the outcome for most stores. Visibility in AI search, match scope in Search ads and the granularity of Amazon performance enforcement all changed their default rules this week. Spend resources first on confirming each default serves you; such checks usually take an hour and pay off more than chasing new features.

What changedPublic

1. Search Console’s AI-features control goes worldwide: Include by default, and exclusion has a cost

The Google Search Console help page says, “As of August 31, 2026, we’ve rolled out this control to all websites worldwide.” It has three settings: Include (the default for all properties; content can appear as links and help ground AI responses), Exclude (links and content are kept out of these features, with no traffic or impressions from them), and Inherit from parent (the default for properties with a parent). It covers AI Overviews, AI Mode and generative AI features in Google Discover. The setting is not a ranking or inclusion signal for other parts of Search and does not affect AI training (that is Google-Extended); blocking Search entirely needs noindex. Changes generally apply within one to two days. Google’s June 3 announcement began with a UK test and was updated on August 31 to say it had rolled out worldwide; the companion generative AI performance report shows impressions, pages, countries, devices and dates, without clicks or queries.

What this means

Impact read

For the first time a site can choose between appearing in AI Overviews and AI Mode and staying out of them entirely, and Google says the choice does not affect regular ranking. The switch is symmetrical: excluding also gives up the impressions and traffic those features bring.

What it means for an independent brand

For most independent stores, product and collection pages appearing in AI answers are a chance to be recommended and compared, so keeping the default is usually sensible. Content-led sites that rely on original long-form pages and worry about AI answers replacing clicks are the ones that may consider excluding. Either way, read the generative AI performance report for which pages and countries get impressions before deciding.

Hold off on

Avoid this week

  • Do not set a whole property to Exclude before reading the generative AI performance report.
  • Do not treat this switch as a way to block AI training; that is what Google-Extended does.
Decision: a high-certainty new control. For product-led stores the Include default is usually the right choice; the first job is reading the report, not changing the switch.

Decision boundary

This applies to every site verified in Search Console; impact is medium for content-led sites and low for product-led stores. This week’s action: export the generative AI impressions by page and country that the report currently holds, mark the shares for product, collection and content pages, and put them beside organic clicks for the same period. If content pages get many AI impressions while clicks fall clearly, test Exclude on a separate sub-property. The judgment changes if Google adds click data to the report, or if excluding changes regular search traffic.

What changedPublic

2. AI Max auto-upgrade begins: automatically created assets and broad-match campaigns first, DSA later

Google’s April 15 announcement, updated June 11, says Search campaigns using automatically created assets (ACA) and the campaign-level broad match setting continue to auto-upgrade to AI Max starting September 2026, while DSA sunset and auto-upgrade move to begin February 2027. The Google Business announcement page lists the defaults after auto-upgrade: ACA campaigns get search term matching and text customization on by default, and campaign-level broad match campaigns get search term matching on by default; Google expects eligible upgrades to conclude by the end of September and recommends upgrading voluntarily first. That page still carries the original DSA wording, so DSA timing follows the June 11 update.

What this means

Impact read

In September, with no action from the advertiser, these campaigns switch to AI Max settings. Search term matching widens what triggers an ad, and text customization writes ad copy from landing pages and assets. The more the system takes over, the more it matters that product facts and brand claims on landing pages are accurate.

What it means for an independent brand

For retail Search campaigns still on ACA or campaign-level broad match, search term reports after the upgrade may show many more new queries, and ad copy may include wording you never wrote. Regulated categories (health, finance and similar) and brands sensitive about claims face higher risk. Campaigns already on standard keywords and self-written ads are unaffected.

Hold off on

Avoid this week

  • Do not keep scaling after the auto-upgrade without reviewing search terms and generated copy.
  • Do not assume the whole account is unaffected in September just because DSA was delayed.
Decision: a high-certainty default switch. The focus is reading back search terms and generated copy after the upgrade, and deciding whether negatives and brand exclusions are needed.

Decision boundary

This applies to Search advertisers still using ACA or campaign-level broad match; impact is medium and confidence high. This week’s action: check weekly which campaigns have been upgraded and note the upgrade date; compare the four weeks before the upgrade with the period after it on the number of search terms and the spend and conversion share of new terms, and spot-check 20 AI-generated ad texts for inaccurate claims. If new-term spend rises while cost per conversion worsens, add negatives or turn off the feature in a controlled experiment. The judgment changes if upgraded campaigns keep stable or better cost per conversion and new-customer share.

What changedPublic

3. Amazon US deactivates individual FBM offers: enforcement gets finer, so watch each SKU

Amazon announced in Seller Central that from August 31, 2026, if an FBM (fulfilled by merchant) offer puts Account Health at risk, Amazon will temporarily deactivate that offer; only the affected offer is deactivated, and other active listings and overall Account Health are not affected. The four policies evaluated are Cancellation Rate, Late Shipment Rate, Order Defect Rate and On-Time Delivery Rate; the post gives no numeric thresholds. A warning email comes first with the issue and steps to resolve it; reactivation runs through Other Policy Violations on the Account Health dashboard. Some sellers replying to the post questioned whether the notice period matches what they understand the terms to require.

What this means

Impact read

Before, one product’s fulfillment problems could drag on the whole account; now Amazon confines the problem to that offer. For sellers this lowers the risk of account-wide action, but a problem SKU can be pulled on its own before peak season, and the post does not state triggers or deactivation length.

What it means for an independent brand

Brands selling the same products through Amazon FBM and an independent store need SKU-level fulfillment metrics, not account averages. When warehouse and fulfillment are shared (for example one 3PL shipping both store and FBM orders), store shipping delays often signal FBM risk too.

Hold off on

Avoid this week

  • Do not watch only account-level averages; a single SKU’s problem is now handled on its own.
  • Do not just edit shipping templates after a warning email without finding the actual fulfillment cause.
Decision: a confirmed change in enforcement with medium impact for US sellers with a high FBM share. SKU-level monitoring matters more than account-level monitoring.

Decision boundary

This applies to US sellers using FBM; impact is medium, confidence high that the rule exists and low on threshold details. Action now: export 60 days of late shipments, cancellations and on-time delivery by SKU, list the worst 10, check whether they share inventory and fulfillment with the independent store, and set a separate handling time before peak season. The judgment changes if Amazon publishes offer-level thresholds or extends deactivation to other policy types.

What changedPublic

4. Shopify’s old cart MCP tools expire: agent cart access moves to UCP

Shopify’s developer changelog (published June 24) states that get_cart and update_cart on the Storefront MCP server (https://{shop}.myshopify.com/api/mcp) are deprecated and maintained until August 31, 2026. The replacement is Cart MCP at https://{shop-domain}/api/ucp/mcp, implementing the UCP cart capability (dev.ucp.shopping.cart, version 2026-04-08), with create_cart, get_cart, update_cart and cancel_cart. update_cart uses PUT semantics, so every request must include the full line_items array.

What this means

Impact read

The interface that lets AI assistants add to and change a shopper’s cart formally switched to the UCP standard this week. The store itself needs no change; what is affected are self-built or third-party shopping agents, chat shopping apps and experiments built on the old tools.

What it means for an independent brand

Stores that used chat shopping, AI shopping assistants or their own agents should confirm these tools moved to the new Cart MCP. If not, those features may fail after August 31, and shoppers only see that adding to cart did not work. Stores without such apps need no action.

Hold off on

Avoid this week

  • Do not assume a third-party shopping app has migrated; test adding an item and changing quantity yourself.
  • Do not send only changed lines on the new interface; PUT semantics replace the whole cart with what you send.
Decision: a confirmed developer interface switch, medium impact for stores using agent shopping and none for others.

Decision boundary

This applies to Shopify stores using AI shopping, chat add-to-cart or their own agents; impact is medium and confidence high. Action now: on a test environment, run the shopping tool through add to cart, change quantity, remove an item and go to checkout, and confirm requests hit /api/ucp/mcp; ask the app developer for written confirmation of migration. The judgment changes if Shopify announces a grace period for the old endpoint, or if your tool never calls cart APIs.

What changedPublic

5. CBP seeks comments on import supply-chain disclosures: online marketplaces and final recipients may be identified

On September 2 CBP issued an advance notice of proposed rulemaking (ANPRM), “Heightened Import Disclosures for Supply Chain Visibility,” under Executive Order 14411, Strengthening Customs Enforcement. Possible measures CBP lists include identifying key parties in the importation process, improved business identifiers, collecting or retaining foreign export documentation and supply-chain tracing technologies. Comments are due by December 1, 2026 under docket USCBP-2026-1058. KPMG’s summary says CBP also asks whether online marketplaces or ultimate delivery recipients should be identified and whether to revise the manufacturer identification code (MID) system.

What this means

Impact read

This is not a rule yet; CBP is deciding whether and how to require fuller supply-chain information from importers. If it becomes a formal rule, the chain from factory to final delivery address could need declaring, with the largest effect on direct-to-consumer small parcels and marketplace sellers.

What it means for an independent brand

Stores shipping directly from abroad to US customers, or importing through third-party logistics, should start checking whether supplier, manufacturer and export-document information is complete and retrievable. No process change is needed now, but a customs broker or logistics partner can assess whether current systems could identify final recipients and platforms if required.

Hold off on

Avoid this week

  • Do not change current customs processes as if the ANPRM were an active filing requirement.
  • Do not wait for a formal rule before organizing supplier records.
Decision: a low-certainty future rule with high potential impact for brands with long US import chains and direct shipping. Now is the time to prepare records and consider comments, not to change processes.

Decision boundary

This applies to cross-border brands importing into the US or shipping directly to US customers; current impact is low, potential impact high, confidence medium. This week’s action: with the December 1 deadline in view, confirm with your broker whether to comment directly or through an industry association, and check whether manufacturer, exporter and MID details are complete for your top 20 SKUs. The judgment changes when CBP publishes a formal proposed rule with applicability thresholds such as value or importer type.

WatchlistPublic

Watchlist: GA4’s September 1 data gap; AI Mode’s new model briefly shows few links

Search Engine Roundtable reported on September 2 that September 1 traffic showed as zero in multiple Google Analytics accounts, which practitioners linked to processing of August 31 data. The article has no Google acknowledgment and does not say whether the missing day will be restored.

SER reported on September 3 that practitioners saw AI Mode on Gemini 3.8 Flash show almost no links or citations for some queries; Google’s Robby Stein replied on September 4 that it was not working as intended and a fix would roll out, and a practitioner saw links return the next morning.

Impact read

How to handle it: when comparing late-August and early-September traffic, check whether September 1 data has been restored and drop that day from comparison windows if needed. The AI Mode link issue was short-lived; it does not justify a content change, only a note when analyzing early-September AI referral traffic.

ImpactPublic

Defaults checklist: what you accept on each item

ChangeDefault stateResult if you do nothingCheck to run
Search Console AI-features controlIncludeKeep appearing in AI Overviews and AI ModeRead the generative AI report before deciding to exclude
AI Max auto-upgradeACA / broad-match campaigns upgradedSearch term matching and related features onRead back search terms and generated copy
Amazon FBM offer deactivationNew rule applies automaticallyProblem SKUs deactivated individuallyMonitor fulfillment metrics by SKU
Shopify cart MCPOld tools no longer maintainedUnmigrated agents fail to add to cartTest shopping tools on the UCP endpoint
CBP supply-chain ANPRMNo rule yetNot commenting leaves status quoOrganize supplier and MID records

Impact read

These five sit in search, ads, marketplace, agents and customs. They belong together because the handling is the same: confirm the default, then decide whether to change it. The first four defaults are already in effect and should be read back this week; the CBP item is a consultation, so preparing records is enough.

Counter-signals: if organic clicks tied to AI-feature impressions keep growing, excluding does not pay; if upgraded AI Max campaigns hold cost per conversion, there is no rush to turn features off.

Action planPublic

Baseline checklist: read back five defaults

Action card

Read the generative AI report before deciding on the AI-features control

Export the generative AI impressions by page and country that the report currently holds, mark the shares for product, collection and content pages, and compare with organic clicks for the same period.

Applies to
Independent stores verified in Search Console
Done when
A written conclusion exists: keep Include, or test Exclude on a sub-property.
Owner
SEO lead
Effort
45 minutes
Stop when
If the report has too little data, keep the default and do not test exclusion.
Review at
9/14/2026, 2:00:00 PM

Related resources

Action card

Read back campaigns already upgraded to AI Max

List auto-upgraded campaigns with their upgrade dates, compare the four weeks before the upgrade with the period after it on search-term count, new-term spend share and cost per conversion, and spot-check 20 generated ad texts.

Applies to
Search advertisers still on ACA or campaign-level broad match
Done when
Each campaign is marked keep, add negatives, or experiment with the feature off.
Owner
Paid search lead
Effort
60–90 minutes
Stop when
If a campaign has less than a week of post-upgrade data or too few conversions, do the copy check only and compare again before the end of September.
Review at
9/21/2026, 2:00:00 PM

Action card

List the 10 worst FBM SKUs by fulfillment

Export 60 days of late shipments, cancellations and on-time delivery by SKU, find the worst 10 and check whether they share inventory and fulfillment with the independent store.

Applies to
US sellers using FBM
Done when
All 10 SKUs have a cause and a matching action.
Owner
Marketplace ops and fulfillment lead
Effort
45 minutes
Stop when
Not applicable without FBM offers.
Review at
9/11/2026, 2:00:00 PM

Action card

Test one full agent shopping cart flow

On a test environment, run the shopping tool through add to cart, change quantity, remove an item and go to checkout, and confirm requests hit /api/ucp/mcp.

Applies to
Shopify stores using AI shopping or their own agents
Done when
All four steps succeed and the developer has confirmed migration.
Not for
Stores without such apps
Owner
Store developer or app owner
Effort
30 minutes
Stop when
Stop if the tool never touches cart APIs.
Review at
9/9/2026, 2:00:00 PM

Related resources

Action card

Decide this month whether to comment on the CBP ANPRM (due December 1)

Confirm with your broker whether to comment directly or through an industry association, and check manufacturer, exporter and MID details for your top 20 SKUs.

Applies to
Cross-border brands importing into the US or shipping directly to US customers
Done when
A comment or no-comment decision exists, with a list of record gaps.
Owner
Supply chain or compliance lead
Effort
60 minutes
Stop when
Not applicable without US imports.
Review at
9/28/2026, 2:00:00 PM

Related resources

SourcesPublic

Sources and method

Facts are limited to items published or taking effect between August 31 and September 6; the AI Max and Shopify Cart MCP notices were published earlier but took effect this week, so they belong here. Primary sources include Google Search Console Help, Google’s official blog and Google Business announcement page, Amazon Seller Central, the Shopify developer changelog and CBP’s press release; KPMG and Search Engine Roundtable add detail.

Verifiable primary material was thinner this week, so only five topics are kept. The specific changes in TikTok’s August 31 Branded Content Policy version could not be verified from the official text and are not included. All judgments and actions are editorial inference.

PrioritiesPublic

Priorities at the end: read back the defaults already in effect

PriorityTeams firstAction nowWhy
P1 | Read backPaid search teamsRead back campaigns already upgraded to AI MaxMatch scope and ad copy changed by default
P1 | Read backUS sellers using FBMList fulfillment-risk SKUsProblem SKUs are now deactivated individually
P2 | Read the reportSEO and content teamsRead the generative AI report before deciding on the controlExcluding also gives up impressions from these features

Avoid this week

  • Do not set the site to Exclude without reading the report.
  • Do not keep scaling AI Max budgets without reviewing search terms.
  • Do not change processes as if the CBP advance notice were a rule in force.

Sign in to continue with the analysis and execution cards available to your plan

You are viewing the Public edition. The server returns the sections available to your account, while unopened content stays out of public APIs and page source.

View plan access