Marketplace seller updates: announcing fee and policy changes to sellers

Most changelog advice assumes your readers are users — people who chose your product and can leave it. A marketplace’s most important readers are neither. Sellers — the merchants, hosts, drivers, and creators who list on your platform — are businesses running on your rails. A settings tweak for you is a margin change for them: edit a fee schedule and thousands of small companies have to reprice inventory; adjust search ranking and somebody’s best-selling listing quietly stops selling. Announcing changes to sellers is changelog writing with someone else’s profit-and-loss statement in the blast radius, and it deserves its own discipline.

This guide covers the seller side of platform communication: fee changes with worked examples, effective dates that respect business cycles instead of sprint cycles, the legal notice floor many platforms now operate under, ranking changes you can’t fully explain, and the channel mix that makes an announcement a record instead of a rumor. It’s the business-user counterpart to announcing policy changes (consumer terms) and announcing pricing changes (your own prices).

Sellers are counterparties, not users

Three readers open every seller announcement:

  • The full-time seller. Your platform is their income. They read with exactly one question — what does this do to my numbers, and by when? — and they will build a spreadsheet within the hour. If your announcement doesn’t contain the math, their spreadsheet becomes the authoritative version of your change.
  • The multi-homing seller. They list on three platforms and your announcement is an input to next quarter’s question: where does inventory and effort go? A vague fee announcement doesn’t just annoy this reader — it reads as risk, and risk gets priced by moving volume elsewhere.
  • The seller-tool vendor. Repricers, profit dashboards, and accounting integrations encode your fee schedule in their code. A fee change breaks their calculators the way an API change breaks a client — give them the same courtesy: a machine-readable feed and precise effective dates. (If you watch changelogs from the other side, see monitoring vendor changelogs — seller tools are that guide’s reader in the wild.)

What makes this audience unlike any other: sellers mostly can’t churn. Their reviews, sales history, and inventory pipeline live on your platform, so a change that would make a consumer quit makes a seller stay — and resent it. The distrust doesn’t show up in retention dashboards. It shows up as forum megathreads, screenshots in trade press, and complaints to regulators. Which yields the first writing rule: the screenshot test. Every fee announcement you publish will be cropped to its first paragraph and posted somewhere hostile. Write that first paragraph so the screenshot is accurate on its own — the real number, the real date, no softening preamble for the crop to amputate context from.

Fee changes: show the math on a real sale

The iron rule for fee announcements: never percentages alone — always a worked example. “Final value fees in Home & Garden increase from 11.0% to 11.9%” is technically complete and practically useless. Add the sale: “On a $40 item, your fee goes from $4.40 to $4.76 — 36 cents more.” Sellers will do this arithmetic anyway; doing it first, on a representative sale, is both a courtesy and a credibility move. When your numbers and their spreadsheet disagree, they trust the spreadsheet — and stop trusting you.

Watch the percentage-points trap. A fee that moves from 10% to 12% went up two percentage points — but the fee itself got 20% bigger, and a hostile reader will always quote the bigger framing. Say both versions yourself (“0.9 points — about an 8% increase in the fee on a typical sale”) and nobody gets to accuse you of hiding either one.

Two more mechanics that separate a fair fee announcement from spin:

  • Publish the whole schedule, as a diff. A blended headline (“average fees rise less than 1%”) conceals the category that took a four-point hit. Show the full per-category table with changed rows marked — the unchanged rows are information too, and the seller in the worst-hit category will find their number within minutes whether you print it or not.
  • Update the calculator first. If your platform offers a fee calculator or revenue estimator, it must show the new numbers (with an effective-date toggle) before the announcement links to it. An announcement whose own calculator contradicts it is the fastest self-inflicted credibility wound in marketplace communication.

Effective dates: business cycles, not sprint cycles

A seller absorbing a fee or policy change has real work to do: reprice a catalog (maybe thousands of listings, maybe via API and tools that also need updating), renegotiate supplier terms, decide what to stop selling. Lead time is not a courtesy — it’s the difference between a change sellers can plan around and one that simply takes money out of in-flight business.

There’s also a legal floor. The EU’s Platform-to-Business Regulation (P2B, 2019/1150) requires platforms to give business users at least 15 days’ notice of terms changes — longer where the change requires technical adaptation — and several other jurisdictions have followed with their own platform-transparency rules. Treat 15 days as the floor, not the target: it is barely enough time to reprice a large catalog. 30–90 days for fee changes is the norm among platforms that sellers describe as predictable. (Not legal advice; your counsel decides the minimum. Your changelog decides whether anyone believes you met it — a dated, unedited permalink is the receipt.)

Three timing rules on top of the floor:

  • Never retroactive. Orders placed before the effective date settle under the old fees; existing listings get a grandfathering window or an explicit migration date. Retroactive application is the single fastest way to turn an announcement into a legal exhibit.
  • Never mid-peak. A fee change effective November 15 toward holiday sellers — or the week before regional tax deadlines toward invoice-sensitive categories — reads as extraction timed for maximum leverage, because it is. Freeze changes through your sellers’ peak the way you freeze deploys through your own.
  • Announce more than once. The breaking-change cadence maps directly: announcement at T−30 or more, reminder near T−7, and the entry updated on the effective date — same URL throughout, so every reminder and news story points at one record.

Ranking changes: announce the change, not the weights

Search and ranking changes are the announcements platforms most want to skip — publishing exact weights invites instant gaming — and the ones silence damages most. Sellers watch their traffic dashboards daily. When visibility drops on the 14th and no entry exists, every seller generates their own explanation, and the explanations are always worse than the truth: the algorithm is rigged, big sellers get protected, someone flipped a switch to sell more ads.

The honest middle — which is also roughly what P2B’s main-ranking-parameters transparency requirement points at — is to announce that a change happened, when it rolled out, which dimension it favors, and what a seller can do: “From March 4, listings with accurate handling times rank higher in category browse. If your handling times are accurate, no action needed. What didn’t change: keyword matching, review weighting.” No weights, no formula — but a seller whose traffic moved on March 4 can now correlate the date, conclude it wasn’t their pricing, and act on something concrete. That correlation is a service only a dated changelog can provide, and it’s the difference between “opaque” and “manipulative” in sellers’ mouths.

Policy changes: enforcement dates and grandfathering

Prohibited-item updates, quality thresholds, suspension and appeal changes — the policy-change craft applies (summarize the diff yourself, plain language over legal fog), plus three seller-specific mechanics:

  • Separate the effective date from the enforcement date. “Policy applies from May 1; enforcement actions begin June 1; existing listings created before May 1 have until July 1” gives sellers a compliance path instead of a cliff. A policy announced and enforced the same day is indistinguishable from a purge.
  • “A small number of sellers” is spin. Without a number, every seller assumes they’re in it. State the scope as precisely as you can — and answer the personal version in the dashboard: “3 of your listings are affected, listed here.” The public entry states the rule; the dashboard makes it personal.
  • Segment delivery, keep one record. Email only the affected categories if you like — but the canonical public entry covers everyone, because trade press, seller lawyers, tool vendors, and the seller who missed the email all need the same citable URL.

Channels: the notice, the record, the pressure valve

A seller announcement isn’t one message — it’s three artifacts with different jobs:

  • The notice — direct email to affected sellers. This is the contractual layer (often the legally required one) and it follows product-update-email discipline: subject states the change, body carries the worked example, link to the record. If the sender domain or template is changing too, that’s its own announcement.
  • The record — a dated entry on your public seller changelog, at a permalink, never edited in meaning after publication (append corrections; don’t rewrite). This is what news stories link, what counsel cites when the notice period is questioned, and what the screenshot test is written for. A dashboard banner points at it for everyone who doesn’t read email.
  • The pressure valve — a forum thread or Q&A where responses live. It absorbs the anger, surfaces edge cases you missed (there are always edge cases in a fee schedule), and keeps the record page itself clean. The anti-pattern is making the forum post the announcement: forum posts get buried by their own replies, can be edited invisibly, and read as informal precisely when sellers want something official.

A fee-change entry, in full

Final value fee change in Home & Garden — effective March 1

What’s changing: the final value fee in Home & Garden moves from
11.0% to 11.9% (0.9 points — about an 8% increase in the fee on a
typical sale).

Worked example: on a $40 sale, the fee goes from $4.40 to $4.76.
Full updated schedule: <link> (changed rows marked). The fee
calculator already reflects March 1 rates: <link>.

What’s not changing: fees in all other categories, listing fees,
and payment processing rates.

When: announced January 15. Applies to orders placed on or after
March 1. Orders placed before March 1 settle at the current rate.

Why: <one honest sentence — cost, mix shift, or strategy.
If you can’t write it, expect sellers to write it for you.>

What to do: repricing guide <link> · bulk price editor
<link> · questions in this thread <link>

Anti-patterns

  • “To serve you better.” A fee increase framed as a gift. Sellers run businesses; they can absorb “our costs went up” or even “we’re shifting monetization toward categories with heavier fulfillment use.” What they can’t absorb is being managed. Give the real reason or give none — see tone and voice on why spin reads louder than the number.
  • Effective immediately. Or worse, retroactively. Both convert a business change into a trust incident — and possibly a regulatory one.
  • Peak-season timing. The change lands when sellers have the least ability to respond and you have the most leverage. They notice the asymmetry.
  • The blended average dodge. “Fees decrease on average” while three categories rise sharply. The worst-hit sellers find their number anyway, and now the headline is a lie and a fee increase.
  • Forum-post-only announcements. Buried by replies, editable without trace, and unfindable in six months when someone asks what notice was given.
  • Deny-then-confirm ranking changes. Telling sellers nothing changed while dashboards show otherwise, then quietly confirming a “small relevance update” weeks later costs more trust than any honest day-one entry could.

Where Wakelog fits

The record layer of this playbook is exactly what Wakelog hosts: a dedicated seller-updates project with dated, permanent entries sellers and their tools can cite. Scheduled publishing (publish_at) lets you stage the entry for the exact notice date counsel signed off on; tags separate fee changes from policy and feature news so a seller can filter to what moves their margin; RSS and JSON feeds give multi-homing sellers and repricer vendors a subscription instead of a rumor mill; and the widget puts the announcement inside the seller dashboard where it can’t be missed. Honest boundary: Wakelog doesn’t send the contractual email notice (pair the entry with your email system) and doesn’t do per-seller “3 of your listings are affected” personalization — it’s the canonical public record the other layers point at.

Start your changelog — free   Next: announcing pricing changes →

Related guides

  • Announcing pricing changes: writing the update everyone actually reads
    The update everyone actually reads, with a calculator. Exact numbers before narrative, the next-renewal rule, grandfathering said out loud, free-tier changes as price increases from $0, and your changelog as the receipt.
  • Announcing policy changes: terms of service and privacy updates
    Summarize the diff yourself or a journalist will, three materiality tiers, absolute effective dates and never-shortened notice periods, archived prior versions, the suspicious-reader test, and the policy history as your questionnaire receipt.
  • Platform engineering changelogs: release notes for your internal developer platform
    A platform team ships a real product to the strangest user base in software: engineers who never chose it and can’t leave. Every release lands inside someone else’s repo, breaks builds on commits that touched nothing, and gets enforced by deadline. What a paved-road changelog announces, why entries should be findable by error message, and the template that keeps internal customers on the road.

Last updated 2026-08-02 · All guides