ChannelWeave Blog

Channels Update — October 2026

Channels

Channels Update — October 2026

October 2026: practical inventory, purchasing, pricing and catalogue actions across Amazon, eBay, Shopify, WooCommerce, Discogs and Web.

By ChannelWeave

Published 8 October 2026. October is where peak-season plans meet operational reality. Stock is moving, promotional rules are live and catalogue changes can affect several selling surfaces at once.

Here is our latest briefing for Amazon, eBay, Shopify, WooCommerce, Discogs and Web, checked against official sources on 8 October. It covers new releases and earlier announcements whose October deadlines now matter. UK-specific dates are labelled; the operational recommendations are ours, not additional platform requirements.

Executive summary

  • Amazon: include the festive FBA fee in margin decisions from 15 October, and work backwards from the 28 October UK arrival target.
  • eBay: exclude scarce or low-margin listings before switching on an always-on bundle discount.
  • Shopify: use the new purchase-order reports to find open orders, unlinked transfers and receiving gaps.
  • WooCommerce: test the 11.2 product importer against real catalogue copies before using its new GTIN matching.
  • Discogs: confirm whether you have the updated or classic inventory tools before relying on draft imports or export history.
  • Web: keep one authoritative product source while Google unifies online and local product records.

Amazon

What changed

Two dates in Amazon’s published UK peak calendar now need action. The festive peak fulfilment fee applies to selected FBA orders delivered to UK buyers from 15 October 2026 to 14 January 2027. Amazon describes averages of £0.12 per parcel item and £0.07 per large or extra-large envelope item; the detailed rate depends on the item and fulfilment route. The fuel and logistics-related surcharge applies on top.

For Black Friday Week, UK FBA inventory should arrive at Amazon’s facilities by 28 October for Prime-badge readiness. That is an arrival target, not the day to dispatch the shipment. Source: Amazon’s official 2026 peak-season notice.

Inventory and selling impact

A promotion can raise unit sales while reducing contribution per order. Late inbound stock creates a second risk: inventory committed to FBA is unavailable to other Channels but may still miss the selling window.

What to do now

  1. Preview the actual peak fee for promoted SKUs in Amazon’s Revenue Calculator or FBA Fee Preview report; do not apply the published average to every item.
  2. Work backwards from 28 October using carrier collection, receiving and exception buffers.
  3. Reserve enough shared stock for non-Amazon orders and agree who can release that reserve.

eBay

What changed

eBay’s October UK seller news highlights bundle discounts for multi-item orders. Sellers can set discount tiers and exclude particular listings. The detailed guidance says the discount is always-on after opt-in, applies across different eligible items and automatically includes new listings unless they are excluded. It reduces item prices only; postage and combined-postage settings remain separate. Source: eBay UK Seller News, October 2026. Bundle discount guidance.

Inventory and selling impact

An always-on rule can quietly catch new stock. That is useful for replenishable lines, but risky for scarce items, consignment stock or products whose margin cannot support both the discount and delivery cost.

What to do now

  1. Build an exclusion list before enabling the discount: one-off items, low-stock lines and products already on promotion belong at the top.
  2. Model the deepest tier against item margin and actual combined-delivery cost.
  3. Check newly listed products during the weekly pricing review, because eligible listings are added automatically.

Shopify

What changed

On 6 October, Shopify added purchase-order data to Shopify Analytics. Three reports cover purchase order costs, purchase order transfers and purchases on order. The last of these identifies open, ordered purchase orders without linked transfers. The Purchase Orders page also summarises items ordered, acceptance rate and shipments due soon. Reports can be exported. Source: Shopify’s purchase-order analytics announcement.

Inventory and selling impact

The new reports make exceptions easier to find, but they do not replace receiving discipline. A supplier order, a transfer and stock physically accepted at a location are three different events.

What to do now

  1. Export purchases on order and assign every open purchase order with no linked transfer to an owner.
  2. Compare ordered quantities, transfer quantities and physically received units for late or partial deliveries.
  3. Use the cost report to recheck margin where supplier cost, estimated tax or received quantity changed.

WooCommerce

What changed

WooCommerce 11.2 was released on 7 October. With “Update existing products” enabled, the Product CSV importer can now match by GTIN, UPC, EAN or ISBN when no product ID or SKU is supplied. Matching follows ID, then SKU, then global unique ID. A non-blank identifier that matches nothing is skipped instead of creating a new product, and a match to a different product type is refused. Import cleanup is also limited to placeholders created by that import rather than running site-wide orphan cleanup. Source: WooCommerce 11.2 release notes.

Inventory and selling impact

Identifier matching can reduce duplicate products, but only when the identifiers are unique and attached to the right pack size and variation. A skipped row is safer than an accidental create, yet it still leaves the intended update unapplied.

What to do now

  1. Test 11.2 with the live theme and extensions on a staging copy before upgrading the production shop.
  2. Run a small CSV containing a known SKU match, a known GTIN-only match, an unknown identifier and a variation; inspect every result.
  3. Review skipped rows explicitly and correct the source file rather than removing identifiers to force a match.

Discogs

What changed

Discogs revised its inventory and CSV support guidance on 21 September. The updated inventory page can select every listing matching the current filters across all pages, then bulk-change status, details or prices. Its updated CSV tool can import additions as Draft or For Sale, and keeps the last five exports for 30 days. Discogs also documents a classic experience: imports there go For Sale and exports follow a separate email-delivery process. Source: Discogs inventory guidance. Discogs CSV guidance.

Inventory and selling impact

The dangerous assumption is that every account has the same tool. A file intended as a private review set can become sellable if it is imported through a flow that defaults to For Sale.

What to do now

  1. Identify whether the account shows the updated or classic inventory experience before preparing a bulk change.
  2. Export a complete inventory snapshot and retain it with the import file and review notes.
  3. Where draft-on-import is available, state DRAFT explicitly; do not rely on a blank status.
  4. After import, verify a sample in the buyer-facing Marketplace and reconcile the file’s external IDs to the physical copies.

This is Discogs’ own inventory workflow. ChannelWeave’s Discogs tools remain manual/file-based; this update does not announce automatic Marketplace publishing or live stock synchronisation.

Web commerce

What changed

Google’s current Merchant Center guidance describes a move towards a single multi-channel product representation for online and physical-store marketing. Newly created Merchant API product data sources are multi-channel by default. Google warns that submitting the same product through more than one primary data source can cause processing errors, and says no action is required for merchants outside the affected API, BigQuery and specialised local-data configurations unless they receive a related email. Source: Google Merchant Center’s multi-channel product update.

Inventory and selling impact

Core product identity should be shared, while availability can still differ by store. Duplicate primary sources, mismatched IDs or case-sensitive store codes can make a product appear missing or conflict with another record.

What to do now

  1. Do not rebuild a feed solely because of this update; first confirm whether Google has notified the account or the setup uses an affected integration.
  2. For affected feeds, document the authoritative primary source for each product and remove accidental duplicate submissions.
  3. Sample online and local availability using the exact product IDs and store codes supplied to Google.

Cross-channel operator checklist

Give these checks an owner and a date this week:

  • Peak margin: recalculate contribution using the fee and discount that will actually apply.
  • Inbound stock: distinguish ordered, dispatched, received and sellable quantities.
  • Identifiers: check SKU, GTIN and external IDs against the exact item or variation.
  • Bulk actions: test a small set, retain an export and verify the public result.
  • Feeds: keep one authoritative product source and investigate duplicate submissions.

The aim is not to add another report. It is to make every promotion, import and replenishment decision traceable back to the stock and margin that support it.

Sources and scope

The official sources are linked beside each update. Information was checked on 8 October 2026; later changes are outside this issue. Confirm account eligibility, rollout state and current platform terms before acting. These are seller-operating recommendations, not announcements of new ChannelWeave integration capabilities.

Start with the cornerstone guide

For the full Channels overview, start here.

The complete guide to multichannel e-commerce platforms