Channels Update — Amazon, eBay, Shopify, and Web | August 2026

Published 7 August 2026. August is a month for decisive operational follow-through. Amazon sellers need to turn event performance into peak-season purchasing decisions; eBay’s fashion-size enforcement and delivery-protection changes are now taking effect; Shopify has added new campaign and returns controls; and web merchants using Google’s Content API for Shopping have only days left before its shutdown.

This issue covers the most relevant current updates for Amazon, eBay, Shopify, and general web commerce, with practical actions for inventory, listing, order, fulfilment, and marketing teams.

Executive summary

• Amazon: the public seller update stream has not introduced a new August fee schedule; the immediate job is to close the Prime Day evidence loop and move into Amazon’s 10–12-week holiday product, inventory, and shipping-planning window.
• eBay: non-standard or missing fashion sizes can now place listings on hold, while eligible UK and US domestic sellers gain stronger protection when carrier delays cause Item Not Received enquiries.
• Shopify: Campaign Autopilot can now allocate spend to Microsoft Advertising in early access, while UPS return labels and app-added analytics annotations improve returns and operational measurement.
• Web: Google’s Content API for Shopping shuts down after 18 August 2026, making Merchant API cutover and product-feed reconciliation the month’s hard deadline.

Amazon

What changed

• No new August fee announcement has appeared in Amazon’s public seller blog as of 7 August: the latest operational posts remain July’s guidance on product margin, FBA fees, inventory management, and packaging. That makes disciplined execution more important than inventing a change that has not happened.
• The peak-planning calendar is already active: Amazon’s FBA holiday guide puts sellers 10–12 weeks before a major event into product selection, inventory preparation, shipping-plan creation, and financing decisions. The following 7–9-week window moves into stocking and sending inventory.
• Prime Day measurement should now drive the next buy: Amazon Ads recommends comparing campaign activity before, during, and after the event across impressions, clicks, and sales, and using longer-term sales measures where available.

Inventory and selling impact

• Revenue alone is not a replenishment signal: promoted volume must be separated from ordinary demand and tested against advertising, fulfilment, returns, fee, and customer-service costs.
• Peak purchase orders now compete with ageing-stock risk: buying too late creates receipt and availability problems; buying too broadly ties up cash and increases storage or removal exposure.
• Event halo demand needs a time limit: a short post-event uplift can justify a temporary reorder adjustment, but it should not become the permanent forecast without evidence.

What to do now

1. Close a Prime Day scorecard by ASIN: ordinary baseline, event units, stockouts, ad spend, return rate, fee stack, contribution margin, and post-event demand.
2. Split the Q4 purchase plan into proven winners, controlled tests, and no-reorder stock; give each group an explicit quantity, lead time, cash requirement, and owner.
3. Check FBA capacity, inbound timing, packaging dimensions, aged inventory, and removal candidates before approving the next shipment.
4. Set a date to reverse temporary event forecasts and campaign budgets unless the following weeks confirm sustained demand.

eBay

What changed

• Fashion listing holds begin in August: eBay says Add and Revise calls containing non-standard, non-compliant, or missing size values can leave new, revised, and existing apparel or footwear listings on hold until corrected.
• Automatic size conversion stops: warning code 21920467 is returned for non-standard values, and eBay no longer converts recognised alternatives such as “Small” into “S” on the seller’s behalf.
• Domestic delivery protection expands: for eligible UK and US domestic orders shipped on time with eBay labels, eBay can place Item Not Received enquiries into a waiting period when a carrier delay is outside the seller’s control. Seller rating protection applies and the buyer’s refund option is temporarily unavailable while the parcel remains in transit.
• Integrations receive a clearer delivery state: the Post-Order API can return ON_HOLD for the waiting period, with an estimated resolution date and provisional-refund indicators.

Inventory and selling impact

• A held listing has zero sellable channel stock: warehouse quantity may be correct, but the offer is hidden from search and cannot receive purchases, offers, or bids until the violation is resolved.
• Size vocabulary is now a publication contract: free text, house abbreviations, and values such as “see description” or “N/A” can interrupt availability across whole fashion ranges.
• Delivery protection depends on evidence: on-time handling, an eligible eBay label, tracking acceptance, and correct enquiry-state handling matter more than a manual promise that an order was dispatched.
• Refund automation must respect the waiting period: an integration that refunds every Item Not Received enquiry immediately can discard the protection eBay has added.

What to do now

1. Run a category-aware audit of every active apparel and footwear listing; replace custom, missing, and invalid size values with current eBay taxonomy values.
2. Treat warning 21920467 and listingOnHold as sellability incidents: remove the affected quantity from channel availability, repair the listing, republish, and reconcile the restored state.
3. Confirm domestic UK and US fulfilment workflows use eligible eBay labels and record the carrier’s first acceptance scan.
4. Update post-order handling so ON_HOLD, resolution dates, and provisional refunds are reviewed before issuing a duplicate or premature refund.

Shopify

What changed

• Microsoft Advertising joins Campaign Autopilot: Shopify’s 4 August update lets early-access merchants create or connect a Microsoft Advertising account and run Performance Max campaigns alongside other connected channels. Autopilot allocates budget based on performance.
• UPS return labels are available in Shopify admin: US merchants can create a UPS return label from a fulfilled order, send it by email or shareable link, and use either Shopify’s discounted rate or their own connected UPS account. The label is charged only when scanned.
• Apps can annotate analytics charts: app-added notes can mark product launches, campaigns, supplier changes, warehouse changes, and other events against sales, units, returns, conversion, and fulfilment performance.

Inventory and selling impact

• Automated budget allocation still needs stock and margin boundaries: a campaign can scale demand towards a product faster than replenishment can follow, or favour revenue that does not meet the merchant’s contribution-margin floor.
• Returns become easier to initiate but still need an inventory state: creating a label should move expected stock into a return-in-transit state without making it available to sell before receipt and inspection.
• Annotations improve causality, not the underlying data: marking a supplier or warehouse change helps explain a metric movement, but SKU, order, return, and fulfilment records still need to be correct.

What to do now

1. If testing Campaign Autopilot, cap the trial budget and exclude or suppress products with low cover, uncertain replenishment, weak margin, or known feed problems.
2. Review Microsoft campaign output by product and contribution margin, not only revenue or return on ad spend.
3. Map UPS label creation, first scan, receipt, inspection, refund, restock, quarantine, and write-off into one visible returns workflow.
4. Add annotations for campaigns, supplier changes, warehouse moves, product launches, and policy changes, then compare the same periods across units sold, returns, fulfilment speed, and margin.

Web commerce

What changed

• Google’s Content API for Shopping shuts down after 18 August 2026: Merchant API is now the primary programmatic interface for Merchant Center product data. Merchants using a third-party provider such as Shopify’s Google & YouTube app should have the migration handled by that provider, but custom integrations need direct action.
• Product writes use a new contract: Merchant API separates submitted ProductInput data from the processed, read-only Product, requires a data source for write operations, and moves product attributes into a productAttributes object.
• Bulk behaviour changes: Content API’s customBatch method is not available. Google directs integrations towards asynchronous or HTTP batching, and product status is now returned through the processed Product resource.
• Product freshness remains an operating requirement: Google says API-managed products should be refreshed at least every 30 days, and landing-page structured data should agree with feed price, availability, and condition.

Inventory and selling impact

• A missed migration can stop catalogue updates: stale price and availability data can lead to disapprovals, wasted advertising, overselling, and product visibility that no longer matches the storefront.
• Successful submission is not successful publication: the processed Product resource and issue data must be reconciled after Google applies rules and supplemental sources.
• Feed and website truth must converge: Merchant Center, structured data, the visible product page, checkout, and the inventory source should agree on offer identity, price, currency, condition, and availability.

What to do now

1. Identify every direct Content API call before 18 August: products, statuses, inventory, promotions, accounts, reports, and custom batch jobs.
2. Move product writes to ProductInput, store the required data-source name, and reconcile the processed Product plus issues before declaring an offer healthy.
3. Replace custom batching with bounded asynchronous or HTTP batching, preserving rate limits, retries, idempotency, and per-offer error reporting.
4. Run a cutover parity check for a representative catalogue: create, update, delete, price, availability, condition, local inventory, issue reporting, and 30-day refresh.
5. After cutover, monitor feed freshness and compare Merchant Center output with storefront structured data and live checkout stock.

Cross-channel operator checklist (August 2026)

• Close Amazon Prime Day performance by ASIN and approve Q4 purchasing from contribution-margin evidence.
• Separate proven Amazon replenishment from controlled tests and aged-stock exit plans.
• Clear eBay non-standard fashion sizes and monitor warning 21920467 and held-listing state.
• Preserve eBay delivery evidence and respect the new Item Not Received waiting period.
• Put stock-cover and margin limits around Shopify’s automated campaign allocation.
• Track Shopify returns from label creation through inspection and final stock disposition.
• Complete Google Merchant API migration and reconciliation before 18 August.
• Keep one weekly exception review for stockouts, held listings, late parcels, returns in transit, campaign overspend, stale feeds, and product-data mismatches.

Sources

• Amazon Selling Partner Blog — latest seller guidance
• Amazon — FBA holiday guide
• Amazon Ads — Prime Day 2026 advanced strategies and measurement
• eBay Developers Program — Q2 2026 newsletter
• eBay Developers Program — Size standardisation for fashion listings
• eBay Inventory API — ListingDetails and held-listing state
• Shopify Changelog — Microsoft Advertising in Campaign Autopilot
• Shopify Changelog — UPS return labels
• Shopify Changelog — App-added analytics annotations
• Google Merchant Center Help — Introducing Merchant API
• Google for Developers — Migrate from Content API to Merchant API
• Google for Developers — Migrate products
• Google for Developers — Add and manage products
• Google Merchant Center Help — Structured data markup