Fee changes need a notice path sellers can find
You update commission, payout timing, or payment fees in the admin. Sellers find out when their remittance shrinks. If the only notice is a changelog buried under Help, you did not communicate—you hoped.
Before any seller fee or payout rule changes, ship an in-product notice with effective date, old versus new numbers, a worked example, and a durable link sellers can reopen later. Email alone is not enough. After go-live, keep the notice pinned until the first remittance cycle clears and staff the inbox that will catch the confusion.
Before: the quiet admin edit
Someone with admin rights changes a percentage. Or payment processing fees move because a processor raised theirs. Or you shorten the payout hold. The configuration screen saves. A ticket is closed. Marketing has a launch to finish. Legal says the terms URL was updated.
Sellers are selling. They will meet the new math on remittance day. If sellers only learn from the remittance, the product failed the notice.
Processor pass-throughs deserve the same path even when "it is not our margin." Sellers experience one remittance number. Whether the dollar went to you or to a processor is your explanation burden, not their research project.
Decision guide
Before vs after a fee change
| Consideration | Before (quiet edit) | After (notice path) |
|---|---|---|
| Discovery | Sellers see it on remittance. | In-product notice before effective date. |
| Math | Adjectives in a blog post. | Old vs new with a $100 example. |
| Record | Undated help article. | Versioned policy URL from the banner. |
| Payout UI | Old rate in tooltips. | Schedule-as-of DATE on the screen. |
| Support | Improvises answers. | Shared script through first cycle. |
After: a notice path you can point to
Build the path before the effective date—not after the first angry thread lands.
In-product: a banner or inbox item on the seller home and payout screens, visible without digging through Help. Effective date in the seller's timezone. Old fee versus new fee in numbers, not adjectives. One worked example: "On a $100 item, commission was $X; starting DATE it is $Y; estimated payout on that item moves from $A to $B."
Durable record: a policy page with version date that the banner links to. Sellers screenshot. Support needs the same URL weeks later.
Email / push: send, but do not rely on them alone. Filters eat marketplace mail. Assume thirty percent never see it.
Contractual: if your terms require advance notice, the product clock and the legal clock must match. Do not let engineering ship early because the config was ready.
This belongs in how you operate marketplaces, not in a one-off Slack reminder.
For sellers in multiple countries, localize the example currency and date format. A USD example emailed to a seller who settles in another currency creates avoidable distrust even when the percentage is fair.
Sequence of work
Fee-change notice timeline
- T−21
Legal and product lock effective date and copy.
- T−14
Banner, email, and policy URL live for sellers.
- T−7
Support drills the script; tooltips updated in staging.
- T0
Config changes; notice stays pinned.
- T+cycle
First remittance clears; review ticket tags; then unpin.
If sellers only learn from the remittance, the product failed the notice.
Before vs after on the payout screen
Before: payout history shows a lower number; tooltip still cites the old rate; help center article is three clicks deep and undated.
After: payout screen shows "Fee schedule as of DATE" with a link; pending balances estimated with the new rule labeled estimated; a dismissible but re-openable notice remains through the first full remittance cycle.
Sellers who price in thin margins will change list prices or leave. That is their right. Surprising them is how you earn public threads you cannot moderate fast enough.
If you offer fee holidays or promotional rates for new sellers, show when the holiday ends in the same notice system. Surprise cliffs after month three are fee changes by another name.
Staff the week the math lands
Support and seller success need a short script: what changed, why (processor, policy, or both), what is unchanged, and whether there is a grandfather window. Measure tickets tagged fee or payout in the two weeks after effective date. If volume spikes, the notice path was invisible—not "sellers don't read."
Related: plan for weeks payouts stop as a separate failure; fee-change notice is the ordinary Tuesday version of respecting seller money.
Leadership should read a sample of seller replies that week—not only a ticket count. Tone tells you whether the notice was findable. If replies start with "I had no idea," the banner failed regardless of whether legal considers notice delivered.
Legal and product share one clock
Put the effective date in the engineering ticket, the legal notice, and the banner copy as the same ISO date. When those three drift, sellers receive three stories. Assign one owner who can slip the config if notice is late—never the reverse.
If a processor forces an emergency pass-through with little warning, say so plainly in the banner. Sellers forgive urgency paired with honesty more than silence paired with a smaller remittance.
What to put in the worked example.
Use round numbers sellers can recompute: item price, commission rate old/new, estimated payment fee old/new if relevant, and net to seller. Show one domestic example and, if you settle cross-border, one note that FX and local taxes are separate lines. Avoid marketing adjectives ("improved economics"). Sellers can tell.
If different categories have different rates, say which categories move on which date. A global banner that hides a category carve-out will be screenshotted as bait-and-switch even when your terms were precise.
Finance should certify the worked example numbers the same way they certify a price list. A wrong example in a banner is worse than no example: sellers will recompute and post the error. One finance initials line on the notice ticket is enough ceremony.
Secondary sellers and agencies who operate on behalf of brands need the notice too. If your marketplace allows staff users, fan the banner to every user with payout or finance roles—not only the original account email. Many fee-change blowups start with "our bookkeeper never got that email."
When fees decrease, use the same path. Selective silence on decreases and loud process on increases trains sellers to assume the worst. Consistency builds the habit of reading your notices.
Archive the banner screenshot and policy PDF with the release ticket so future disputes do not depend on memory. Six months later, someone will ask what sellers were told—and you will want the artifact.
Coordinate with paid ads and recruiting messages the same week: if your acquisition copy still quotes the old take-rate, you are advertising a price you no longer offer. Marketing, product, and finance share one fee sheet for a reason—use it.
Close the loop by emailing sellers who opened a fee ticket a short confirmation that the notice path now lives under Help → Fees with the dated example. That reply turns a complaint into proof you listened.
Put this into practice
Upcoming fee or payout change on your roadmap? Build the banner, example, and policy URL first. Change the config second. If your seller admin cannot pin notices yet, that is the story—not the percentage. Talk to us when the marketplace admin needs that path designed in.
Related work: Paddle8.
Add "seller notice path" to the definition of done for any pricing config change in your admin. No path, no merge. That single rule prevents most remittance surprises.
We build alongside the people doing the work.
Bring us the problem you’re thinking about.