THE FIRST THIRTY DAYS

A price rise done well takes about a month, most of it spent on the people who already buy from you.

1. Week one: the mathContribution per unit for every SKU above a tenth of revenue, with this month’s landed cost and the duty sheet (chapter 12). Break-even volume per SKU (chapter 3). Sort SKUs by how well customers know their prices (chapter 6). Fill in the loyalty tax table (chapter 9).
2. Week two: the planSet each SKU’s rise, and decide where a tier does the job better (chapter 7). Write the reason in one sentence (chapter 5). Decide grandfathering and its end date with the tool (chapter 8). Write the price protection policy (chapter 10). Choose the comparison and save the baseline (chapter 14). Send the subscriber notice to counsel.
3. Week three: the customersFix the loyalty tax rows where a stranger wins. Brief support. Send subscriber notices inside your strictest notice window. Email recent and repeat buyers with the stock-up window. Disclose any pack changes on the product pages (chapter 11).
4. Week four: the switchChange the prices on the date. Check every place a price appears: product pages, collection pages, bundles, subscription plans, marketplace listings, ads and email flows. Read every price-related ticket. Start the weekly scorecard.

At day thirty you’ll know early volume against break-even and what customers are saying. The answer comes at day 90 and day 180.

Customers first, then the site. Math before both.

Do this

• Put the four weeks on the calendar today, with an owner for each line, and the day-90 and day-180 reads at the end. If the same person owns pricing, email and support, give them this guide.