How to set a revenue goal for your Shopify store (and actually keep it)
Last updated: 2 August 2026
A revenue goal you keep is three things, and the number is only the first: a target your own data can defend, one to three weekly behaviors that plausibly move it, and an explicit list of work you will stop doing to make room. Goals fail at the third item far more often than the first.
Step 1 — set a target your numbers can defend
Take your run-rate over the last 90 days, project it across your cycle, and add only the improvement you can name a reason for. If the target needs a 40% lift and you cannot say which factor delivers it, you have not set a target — you have set a hope. (The full arithmetic is in Is my Shopify sales target realistic?.)
Pick a cycle length you can see the end of. Four weeks is long enough for a change to show and short enough that missing it is recoverable.
Step 2 — choose one to three weekly behaviors
A behavior is something you do on a schedule, not an outcome you want. The difference is whether you can tick it off on a Friday.
| Not a behavior | A behavior | | --- | --- | | "Improve conversion rate" | "Rewrite the top 5 product pages — one per week" | | "Get more traffic" | "Publish 2 comparison posts a week for the top-selling category" | | "Increase AOV" | "Add a bundle to the 10 best sellers by week 2" |
Three is the ceiling, and it is a real ceiling. Four behaviors in a four-week cycle means each gets one week of attention, which is the same as doing none of them properly.
Step 3 — write the cut list
This is the step that decides whether the goal survives. Your weeks are already full; new work displaces old work whether or not you choose which. So choose: name two or three things you will explicitly not do this cycle — the newsletter redesign, the second sales channel, the packaging refresh.
A plan without cuts is not a plan, it is an addition to a backlog.
Step 4 — check in weekly, against pace
Once a week, compare where you are to where the target says you should be at this point in the cycle, then decide one thing:
| What the pace says | The decision | | --- | --- | | On pace (within ~10%) | Hold. Change nothing. | | Slightly behind | Intensify — same behaviors, more of them. | | Behind and the behavior clearly is not moving the number | Swap that behavior. | | Behind with everything running as planned | Revise the target down, on the record. |
That last row is the one people skip, and it is the one that keeps goals credible. Revising a target down mid-cycle with the reason written next to it is honest. A target you quietly stop mentioning teaches everyone that targets do not matter.
Who this is not for
- Stores whose problem is not focus. If revenue is flat because checkout has been broken for a month, fix that. This is for stores doing many reasonable things and none of them decisively.
- Teams that need a forecast, not a goal. A forecast predicts; a goal commits. This is the second one.
- Anyone who will not do step 3. Steps 1, 2 and 4 without cuts produce a slightly better-documented version of what you already do.
Common questions
Monthly or quarterly? Set the direction quarterly, run it in four-week cycles. A quarter is too long to feel a miss coming.
What if I hit the target in week 2? Close the cycle and set a new one. A finished goal you keep coasting on is just a longer week off.
Should the whole team have the same goal? One goal per cycle, yes — sub-targets per person are fine as long as they multiply back to it.
Paceloop runs exactly these four steps: it pressure-tests the target, builds the behaviors and the cut list from your diagnosed constraint, and holds the weekly check-in with one of those four recommendations. Install free — the audit, activation, and your first two check-ins cost nothing.