A DTC subscription brand gets an email from Recharge: "effective in 60 days, your platform fee is increasing by 32 percent." The brand is doing $3M in annual subscription GMV. The new fee structure adds $14K to the annual line item. The ops team has six weeks to decide whether to absorb the increase or migrate to Shopify Subscriptions.
This is an incident pattern I've helped DTC operators work through several times. The mechanics are specific, the decision tree is compressed, and the negotiation lever is real if you know to use it. What actually happened, step by step.
The pressure situation
A subscription-vendor price change is a classic forcing function. You didn't ask for it, the timing isn't ideal, and every option has a cost. Three real options:
- Absorb the increase. Pay the new fee, keep operating. No engineering cost, higher ongoing spend.
- Negotiate. Threaten migration credibly, see if the vendor gives a price hold.
- Migrate. Move to Shopify Subscriptions inside the grace period. Engineering cost upfront, lower ongoing spend.
The right option depends on the math and the timeline. For most brands between $2M and $10M in subscription GMV facing a 20-plus percent increase, the negotiation-then-migrate path is the expected-value winner.
For the full migration-playbook context, see Recharge to Shopify Subscriptions: a migration playbook.
Day 0: read the email carefully
Price-change notices have specifics that matter:
- New pricing formula. Is it a flat monthly increase or a percent-of-GMV increase? Percent-of-GMV is worse at scale.
- Effective date. 60 days is the common window. 30 days is worse. 90 days is generous.
- Grandfather terms. Some notices offer to grandfather existing pricing if you commit to an annual contract. Read carefully; these often tie you in longer.
- Contract obligations. Current contract may have exit terms (30-day notice, annual renewal clauses). Check before planning.
Calculate the annual cost delta. If it's under 10 percent, probably absorb. If it's 20 percent or more, the math shifts toward migration.
Days 1-7: run the options math
A honest TCO comparison for a brand at $3M in subscription GMV:
Option 1: Absorb the increase
- Annual incremental cost: $14K
- Engineering cost: $0
- Net 3-year cost: $42K
Option 2: Migrate to Shopify Subscriptions
- Migration cost: $20K (80-120 engineering hours + ops time)
- Annual fee on Shopify Subscriptions: near zero (native, no per-transaction fee beyond base Shopify processing)
- Net 3-year cost: $20K upfront, near-zero ongoing
- Payback period: Year 2
Option 3: Negotiate then decide
- Try to get a 6-12 month price hold
- If successful: plan the migration as a Q3 or Q4 project instead of a crisis
- If unsuccessful: proceed with Option 2
Option 3 is the expected-value choice for most brands. Even a 50 percent negotiation success rate, yielding a 6-month price hold, moves you from crisis-mode migration to planned-project migration. That's worth trying.
Days 8-14: negotiate
This is the step most operators skip. They assume a vendor price change is non-negotiable. It often isn't.
The negotiation approach:
- Contact your account rep directly. Email works; call is better.
- State the price change makes the math work for migration, specifically to Shopify Subscriptions. Name the alternative explicitly.
- Ask for either a hold on current pricing for 12 months, or a smaller increase on a longer contract.
- Be prepared to walk. The threat only works if it's credible.
Typical outcomes:
- 6-12 month hold on current pricing in exchange for a commitment to review again then. Common for accounts over $50K/year in Recharge fees.
- Smaller increase (half the original amount) in exchange for an annual contract. Worth considering if the contract has reasonable exit terms.
- No flexibility. The vendor genuinely has no room to move. This happens; proceed with migration.
“The negotiation succeeds about half the time on larger accounts. That's a free option, and most operators never pick it up.
”
Days 15-30: commit and prep
If negotiation failed or produced an unacceptable offer, commit to migration. Begin the four-week playbook. Week 1 of the playbook is Day 15-21 of the pressure timeline.
- Export all Recharge data (customers, subscriptions, line items, charge history).
- Reconcile against Shopify.
- Begin billing-schedule mapping.
If you're on a tight timeline, consider bringing in contract engineering help to compress the work. A two-person team can cut the migration to three weeks from four.
Days 31-60: cutover before the price hits
The cutover needs to land before the new pricing takes effect. For a 60-day grace period:
- Day 31-45: finish data mapping, run dry-run simulations.
- Day 46-49: cutover weekend. Freeze Recharge, import into Shopify Subscriptions, monitor first charge cycle.
- Day 50-56: validate. First post-cutover billing cycle should complete clean.
- Day 57-60: decommission Recharge. Disable webhooks, remove theme snippets per the uninstall checklist for theme cleanup, uninstall the app. Price change never takes effect on your account.
What breaks in a compressed timeline
Compressed migrations have specific failure modes beyond the general migration gotchas:
- Skipped billing-schedule dry run. The 60-day window tempts operators to skip the four-cycle simulation. Don't. Double-charges in the first post-cutover cycle cost more than the price increase.
- Incomplete email flow updates. Klaviyo flows referencing Recharge portal URLs stay pointing at the old URLs. Customer service volume spikes when customers click broken links.
- CAPI dedup drift. If your CAPI integration was tied to Recharge events, the migration breaks the dedup chain. See CAPI for subscription commerce for the pattern to maintain event-ID continuity.
- First-cycle customer-support load. The week after cutover is a support-heavy week. Staff for it. Customers will email "my subscription changed" even if it didn't.
The lesson for stack decisions going forward
A price-change event is a forcing function. It's also a good time to audit whether other apps in the stack are on similar thin ice. Apps that raised prices once will raise them again. Run the Shopify app stack hub decision framework across the rest of your stack, not just subscriptions. Apps that fail the "portable data, clean API, no checkout lock" filters are candidates for proactive migration before they issue their own price notice.
If you want a formal audit of the rest of your stack while you have the migration energy up, the DTC Stack Audit produces a prioritized list.
Can you really negotiate a Recharge price change?
Yes, about half the time on larger accounts (over $50K/year in platform fees). The lever is a credible migration threat. Smaller accounts have less negotiation leverage but can still sometimes get smaller increases or longer commitments at the current price.
Is 60 days enough time to migrate to Shopify Subscriptions?
Tight but possible for a mid-market brand. The standard four-week playbook leaves two weeks of buffer for negotiation and decision-making at the front. Brands with complex subscription logic (build-a-box, prepaid multi-plan) may need the full 60 days or an absorb-one-month bridge.
What if negotiation fails and we can't finish migration in time?
Absorb one month at the new pricing, finish the migration cleanly, then uninstall. One month of increased fees is cheaper than a botched cutover. Tell Recharge you're migrating and ask if they'll extend the grace period (sometimes they will, especially if the account is meaningful to them).
Are Bold Subscriptions or other alternatives worth considering?
For most brands, Shopify Subscriptions is the cleanest migration target in 2026 because it's native and has no per-transaction fee beyond base processing. Bold is viable but less strategically aligned, since you're moving away from a third-party subscription app and into another third-party subscription app. The Shopify-native path has better long-term platform fit.
Will the migration affect my current customers' billing continuity?
Handled correctly, no. The subscribers keep their plans; next-charge dates are preserved; pricing stays the same. Handled poorly, customers see double charges, missed charges, or broken portal links. The billing-schedule mapping step in Week 2 of the playbook is the specific work that prevents the bad outcome.
Sources and specifics
- Pricing examples reflect illustrative numbers for mid-market DTC brands. Your actual math depends on current contract and new terms.
- Negotiation success rates reflect observed outcomes on accounts over $50K/year in platform fees.
- Migration timing reflects the four-week playbook covered in Recharge to Shopify Subscriptions.
- For full app-stack context, see the Shopify app stack hub and the DTC Stack Audit product.