How should eco DTC announce a price increase without a trust crash?
Quick answer
Tell subscribers and recent buyers before the PDP flips. Name one true cost driver in a scoped sentence. Do not invent a climate story to justify the number. Decide grandfathering or a short last-buy window first. Then sync email, PDP, feed, ads, and support macros the same hour. How to set the floor lives in premium pricing. Temporary sale posture lives in ethical Black Friday. Checkout duty lines live in Shopify Markets.
Vs other pricing and comms guides
| Guide | Job |
|---|---|
| Premium pricing | List-price floor, value framing, tests. Mentions 5 to 8% increases; not a launch kit |
| Ethical Black Friday | Temporary Cyber Week posture, not a lasting list change |
| SKU sunset | Ending a product. Different reason, similar channel order |
| Shopify Markets | Duties and landed cost at checkout, not hero SKU list price |
| Win-back | Lapsed buyers. Do not hide an increase inside a win-back coupon |
| This guide | Announcing a list-price increase without a trust crash |
Name the reason (one, true)
| Driver | Say | Do not say |
|---|---|---|
| Materials / supplier | Named input cost rose; formula or construction unchanged unless it did | “More sustainable, so it costs more” with no delta |
| Freight / labor | Fulfillment or wage line, in one sentence | Vague “the world got expensive” |
| Tariff / duty on COGS | “Import cost on this SKU increased.” Keep it on the list price story | Blaming shoppers or wrapping it in climate copy |
| Currency | Home-market list vs Markets conversion, separately | Mixing FX with a values lecture |
| Margin repair | If that is the truth, say contribution was below the floor. See the break-even calculator | Dressing a margin grab as a new impact program |
If you cannot name the driver without a new eco claim, freeze the announcement and fix the substantiation folder first.
Notice calendar
- T-14 to T-10: lock SKUs, new prices, contribution, grandfather rule, claim freeze. Pause ads that show the old price.
- T-10 to T-7: wholesale and retail doors. Do not let a buyer see DTC cheaper than MAP the week you raise DTC.
- T-7: subscribers, VIP, and 90-day purchasers. Last-buy or locked rate if you promised it.
- T-3: site banner or PDP note for logged-out traffic. FAQ live.
- T-0 (same hour): PDP, Shopify compare-at off, Merchant Center, email footer, support macros.
- T+7 to T+14: kill leftover sale language. Do not stack a “sorry” coupon that trains a new floor. That is BFCM logic, not increase logic.
Steal this copy stack
| Asset | Must include | Must not |
|---|---|---|
| Email / SMS (consent) | What changes, when, why (one driver), what does not change, what the reader can do before T-0 | New cert or carbon lines invented for the send |
| PDP note | Effective date and the same driver sentence | Strikethrough theater that looks like a sale |
| FAQ | Subscribers, gift cards, preorders, wholesale | “Prices may vary” with no rule |
| CS macros | Paste-ready reason + grandfather policy + escalate if they allege bait | Agents inventing a greener justification |
Preorders already have ship-window rules in preorder trust. Honor the price you took payment at unless the contract said otherwise.
Who keeps the old price
- Active subscribers: lock the rate for a stated window (often 30 to 90 days) or until they skip. Silent billing at the new price is a no-go.
- Open checkouts / recovered carts: honor the quoted price through the abandon window you already run.
- Wholesale: MAP and cost changes on the line-sheet calendar, not a surprise Instagram post. See line sheets.
- Everyone else: notice plus optional last-buy, not a sitewide apology coupon.
Go / no-go and how to measure
| Call | When |
|---|---|
| No-go | You cannot name a true driver, ads still show the old price, or CS has no macro |
| Go | Driver is true, notice calendar is staffed, grandfather rule is written, PDP/feed/macros flip together |
| Partial go | New-customer list price only; subscribers locked; or one SKU family as a test |
Watch unsubscribe and spam complaints, price-related tickets per 100 orders, 60-day repeat of the notified cohort vs a quiet holdout if you have volume, and contribution after the new floor. A quiet inbox with collapsing repeat is still a crash.
Honesty is the discount
Eco buyers will pay more for the same product if the reason is real. They will not pay more for a sermon.
Frequently asked questions
How should eco DTC announce a price increase without a trust crash?
Notice subscribers and recent buyers before the PDP changes. Name one true cost driver. Grandfather or last-buy if you can. Sync feed, ads, and macros the same hour. Do not invent a climate story for the increase.
Should we blame tariffs or “sustainability”?
Name the real driver. Tariffs and freight are allowed when true. “Because we are more sustainable now” is only allowed if the product actually changed and you can prove it.
Do subscribers keep the old price?
Write the rule before you send. Silent autoship at the new rate is the failure mode. A stated lock window or skip option is the go path.
Should we add a coupon to soften the news?
Usually no. A same-week coupon trains a new floor. Last-buy at the old price is cleaner than 15% off the new price.
How is this different from the pricing strategy guide?
That guide sets the floor and value story. This guide is the announcement: who hears first, what you say, and how ops stay in sync.