January is the quietest your back office gets all year. The holiday rush is over, returns are working their way through, and there's a natural pause before the year picks up speed. It's the best window you'll have to step away from daily firefighting and decide where you want your store to be in twelve months. But there's a gap between setting goals and setting goals you'll actually hit by December, and most New Year plans for online stores die in that gap by March.

This is a planning guide, not a pep talk. The aim is a set of goals that are specific enough to act on, modest enough to survive a busy spring, and, the part most planning advice skips, tied to things you can actually change from inside PrestaShop. A revenue target you can't trace to a lever you control is just a wish with a number attached.

Last updated: June 2026.

Why most e-commerce goals fail by March

The pattern is predictable. In January, store owners set ambitious targets: "double revenue", "launch in three new countries", "redesign the whole site". By March, daily operations have eaten the calendar and the grand plan is forgotten until next January. The goals didn't fail because the owner was lazy. They failed for specific, fixable reasons:

  • Too vague. "Grow the business" isn't a goal, it's a mood. Without a number and a date, you can't measure progress or know when you've arrived.
  • Too ambitious. Doubling revenue in a year is possible but unlikely for an established store without a fundamental shift in strategy or real investment. Targets you privately know are unrealistic breed discouragement, and discouragement breeds abandonment.
  • No mechanism. "Increase email subscribers by 40%" is specific, but how? A goal with no lever attached is a fantasy. Every target needs a "and I'll do this to get there", ideally something concrete in your store.
  • Too many goals. Five major goals competing for the same limited hours means none of them gets the attention it needs. Focus beats breadth, every time.

A framework that actually survives the year

A planner notebook, blank calendar and small growth chart laid out on a wooden desk with coffee
A realistic planning framework: map goals onto a calendar in January so they survive past March.

Step 1: review last year honestly

Before you set a single new goal, understand where you actually are. Pull the data, and on PrestaShop most of it is already sitting in your back office, no extra tools required:

  • Revenue, month by month. Not just the annual total. In Stats → Sales and orders (and the dashboard's date-range picker), look at the monthly shape: which months carried you, which dragged. That shape is the raw material for next year's promotion calendar.
  • Traffic and conversion by channel. Stats → Visitors and the conversion-rate panels tell you what brought your best customers, and which traffic converted versus just browsed.
  • New versus returning customers. Stats → Best customers and Customer accounts show how much of last year leaned on repeat buyers. A number that quietly decides how hard you have to work for growth.
  • Best sellers and dead stock. Stats → Best-selling products tells you where the money came from; the long tail of zero-sale SKUs tells you what to clear or cut.
  • Operations. Average fulfilment time, return rate, support volume. Where did you actually struggle, as opposed to where it felt busy?

This review isn't about judgement, it's about evidence. The honest picture of where you are is what makes the next step's goals realistic instead of aspirational.

Step 2: choose three goals, maximum

Three is roughly the most significant goals you can chase while still running the shop day to day. Pick the three with the biggest impact and let the rest wait. For most small and mid-sized stores they fall into three buckets:

  • A revenue target. A specific number, informed by last year. A 15–25% year-over-year increase is ambitious-but-reachable for a store that's already growing, though the right figure depends entirely on your starting point and market, so treat that band as a sanity check, not a rule.
  • An operational improvement. Cut fulfilment from three days to one. Reduce the return rate. Automate something that currently eats ten hours a week. Recurring promotions are a classic example (more on that below).
  • A growth initiative. Launch in one new market, not three. Add a product category. Start publishing content. One new front, done properly.

Step 3: break each goal into quarterly milestones

An annual goal is too far away to drive what you do on a Tuesday in February. Break each one into quarter-sized chunks you can check against:

Example, "Grow revenue 20% (from 200K to 240K)":

  • Q1: tidy analytics, optimise the top 20 product pages, set up the year's automated promotions so seasonal sales fire without you.
  • Q2: start content (two posts a month), test a small paid budget, run a spring clearance on slow stock.
  • Q3: scale whatever worked in Q2, and, this is the one everyone leaves too late, prepare Q4.
  • Q4: execute the holiday campaigns you built in Q3 and protect your margin through the peak.

Each quarter has concrete, finishable items. At the end of each one you can tell, honestly, whether you're on track, and adjust before it's too late.

Step 4: name one thing per month

Inside each quarter, pick the single most important action for each month: the thing that, if nothing else gets done, still moves the goal forward. Write it down where you'll see it. January: set up clean analytics and a baseline. February: optimise your five best-selling product pages. March: build and schedule your first automated promotion so it runs itself for the rest of the year. One clear priority a month beats a twenty-item list you stop reading by the 5th.

Revenue goals: work bottom-up, not top-down

Don't pick a number because it sounds good. Calculate what's actually reachable. Revenue breaks down into three levers:

Revenue = Traffic × Conversion rate × Average order value

Say last year you had roughly 100,000 visitors, a 2% conversion rate, and a 65 EUR average order, about 130,000 EUR. To reach 156,000 EUR (a 20% lift) you could push any single lever hard, or, far more realistic, nudge all three a little:

  • Traffic +20% (to 120,000), everything else flat; or
  • Conversion 2% → 2.4%, traffic flat; or
  • Average order 65 EUR → 78 EUR, traffic flat; or
  • The sane version: traffic +10%, conversion +5%, AOV +5%, which compound together to roughly the same place without any one number needing a miracle.

The combined route matters because two of those three levers, conversion and average order value, are things you change inside PrestaShop, not things you have to buy from an ad platform. That's where the planning gets concrete.

Turning goals into PrestaShop levers

This is the step generic New Year advice never reaches: connecting "grow AOV 5%" to an actual setting in your store. Here's how the common goals map onto things you control from the back office.

If your goal is…The lever in PrestaShopWhere it lives
Lift average order valueProduct bundles, volume cart rules ("spend 100, get 10% off")Catalog → Discounts (Cart rules); product combinations
Run seasonal promotions without manual workScheduled cart rules / specific prices with start and end datesCatalog → Discounts; product page → Pricing → Specific prices
Clear slow or dead stockCategory-, supplier- or manufacturer-targeted catalog price rulesCatalog → Discounts → Catalog price rules
Protect margin during salesExcluding key products from blanket discountsCart rule conditions / specific-price scope
Win back lapsed customersPersonal voucher codes for a customer segmentCatalog → Discounts → New cart rule
Add a new revenue lineDigital gift cards / vouchersModule-driven, sold as products

Two PrestaShop mechanisms do most of this heavy lifting, and they're worth understanding before you plan the year around them. Cart rules (Catalog → Discounts) are vouchers and conditional discounts, "10% off orders over 80 EUR", "free shipping this weekend", a personal code for a specific customer. Specific prices (set on the product's own edit page, under Pricing → Specific prices) override the price for a particular context, a product or combination, optionally narrowed to a customer, group, currency, country, shop or quantity threshold, with optional from/to dates. For category-, supplier- or manufacturer-wide reductions you reach instead for catalog price rules (Catalog → Discounts → Catalog price rules). If your year's plan involves any discounting at all, and for most stores it does. These are the foundation. The full mechanics are worth a read before you build a campaign: see running a sale in PrestaShop with cart rules and specific prices.

Plan the promotion calendar in January, not the night before

The single highest-leverage thing you can do in your January planning session is map the year's promotions onto a calendar, once, and then build them so they run on their own. Most owners instead scramble the day before each sale, which is how Black Friday discounts go live at the wrong percentage and Valentine's bundles never get built at all.

Start by laying the whole year out: which dates you'll actually promote, and which you'll deliberately skip. A realistic seasonal map keeps you from over-discounting your margin away in a quiet month. See the seasonal sales calendar for when to run promotions through the year. The big anchors most stores plan around:

Once the calendar is fixed, the trick is to build each promotion ahead of time and let PrestaShop run it. Cart rules and specific prices both take a from and to date, so a sale can be configured in January and go live in November on its own. No late-night logins, no "did I remember to turn it off?" the morning after. That's exactly the kind of ten-hours-a-week task worth automating into a goal: scheduled discounts that start and stop automatically walks through the setup. For limited-window urgency campaigns, flash sales done without being manipulative covers the honest version of the countdown timer.

Goals that lift AOV: bundles, gift cards and protected products

If one of your three goals is average order value, and for a store with steady traffic it's often the cheapest lever to move, three PrestaShop tactics deserve a place in the plan:

  • Bundling. Grouping complementary products into a single, slightly-discounted package lifts the order value without a sitewide price cut. The mechanics and the merchandising both matter: product bundling, selling more by grouping products together.
  • Gift cards. Digital vouchers are a clean new revenue line, paid for now, redeemed later, and a natural fit for the gifting seasons on your calendar: adding digital gift cards to your store.
  • Discount discipline. Growing revenue while margin shrinks is a hollow win. Decide upfront which products never go on sale, your newest, your highest-margin, your supplier-restricted lines, and exclude them from blanket promotions: why some products should never go on sale.

Goals beyond revenue

Revenue matters, but it isn't the only number worth a goal. Worth considering:

  • Profitability. A goal to add three points of gross margin can beat a 10% revenue increase, because revenue growth means nothing if the margin behind it is thinning.
  • Customer satisfaction. Measurable through review scores, surveys, return rates. Happy customers are repeat customers, and repeat customers are the cheapest revenue you'll ever earn.
  • Operational efficiency. Time per order, support resolution time, stockout frequency. Every hour you claw back here is an hour for growth work. Which is exactly why automating recurring promotions belongs on the list.
  • Personal sustainability. If you're working 70-hour weeks, "get to 50 without losing revenue" is a legitimate, even essential, goal. Burnout is the largest single threat to a small store; it deserves to be named explicitly, not left to chance.

The monthly review rhythm

Put a recurring 30-minute appointment in the calendar, say, the first Monday of each month, and run the same short review every time:

  • How did this month's key metric track against the goal?
  • What worked, and what didn't?
  • Is the current plan still the right plan, or does it need a nudge?
  • What's next month's one thing?

That half-hour ritual outperforms an elaborate annual planning offsite that's forgotten by February. It keeps the goals alive, allows course correction while it still matters, and slowly builds the habit of thinking strategically alongside running the shop rather than instead of it. Your back-office dashboard should surface the key numbers at a glance so the review stays quick and data-driven, if checking your figures means digging through five reports, fix that first; the data is the foundation everything else stands on.

Frequently asked questions

How many goals should I set for the year?

Three, maximum. Three is roughly the most significant goals you can chase while still running the shop day to day, usually a revenue target, an operational improvement, and one growth initiative. Five major goals competing for the same limited hours means none gets the attention it needs. Focus beats breadth, and three clear goals carry you further than twenty ambitious ones gathering dust by February.

Is doubling revenue a realistic New Year goal?

Rarely, for an established store, without a fundamental shift in strategy or real investment. A 15–25% year-over-year increase is ambitious-but-reachable for a store that's already growing, though the right figure depends entirely on your starting point and market, so treat that band as a sanity check, not a rule. Targets you privately know are unrealistic breed discouragement, and discouragement breeds abandonment by March.

How do I turn a revenue target into something I can actually act on?

Work bottom-up using Revenue = Traffic × Conversion rate × Average order value, then nudge all three a little rather than pushing one heroically. Two of those levers, conversion and average order value, are things you change inside PrestaShop, not things you buy from an ad platform. Map each goal to a concrete back-office lever: bundles and volume cart rules for AOV, scheduled cart rules for promotions, catalog price rules for clearing dead stock.

When should I build my year's promotions?

In your January planning session, not the night before each sale. Cart rules and specific prices both take a from and to date, so a sale can be configured in January and go live in November on its own. Build each promotion ahead of time and let PrestaShop run it. See scheduled discounts that start and stop automatically. Lay the whole year's calendar out first, including the dates you'll deliberately skip.

What's the difference between cart rules, specific prices and catalog price rules?

Cart rules (Catalog → Discounts) are vouchers and conditional discounts, "10% off orders over 80 EUR", a personal code for one customer. Specific prices (set on the product's own edit page under Pricing) override the price for a particular context, optionally narrowed to a customer, group, country or quantity, with optional from/to dates. Catalog price rules (Catalog → Discounts → Catalog price rules) apply category-, supplier- or manufacturer-wide reductions. The full mechanics are in running a sale in PrestaShop.

The best plan is the one you actually follow. Keep it to three goals, tie each one to a lever you can pull from your own back office, build the year's promotions while January is quiet, and check in once a month. Three clear, mechanised goals will carry you further than twenty ambitious ones gathering dust in a planning doc. And when this year's plan turns into next year's, and the decade's, the same discipline scales up cleanly: a worked example of setting goals for a new decade of e-commerce.

Tags: PrestaShop SEO
Share this post:
David Miller

David Miller

Founder, mypresta.rocks

David Miller is a PrestaShop specialist with over a decade of hands-on experience and the founder of mypresta.rocks, a software studio in Tychy, Poland. He builds and maintains a catalogue of 152 PrestaShop modules, including 21 "Revolution" suites spanning SEO, checkout, security, performance, marketing, search, support, and warehouse operations, that improve real stores every day, all tested against PrestaShop 1.7.8, 8.x, and 9.x. He also acts as caretaker for production stores turning over millions in annual sales, so his work is judged on live revenue, not demos. His experience runs the full breadth of ecommerce, performance, security, SEO, and marketing, and reaches beyond PrestaShop to WooCommerce, Shopify, and custom-built systems. On the blog he writes about the code-aware side of PrestaShop: what the platform really does under the hood, what breaks in production, and which fixes hold up.

Comments

No comments yet. Be the first!
Enjoyed this article?

Get our latest tips, guides and module updates delivered to your inbox.

You may unsubscribe at any moment. For that purpose, please find our contact info in the legal notice.

Loading...
Back to top