New Year 2030: Setting Goals for a New Decade of E-Commerce

A new decade is a tempting moment to write down big intentions. The problem with most New Year goals for an online store is not ambition — it is that they never touch the back office. "Grow the business" and "increase revenue by 20%" sound like goals, but neither tells you which screen to open on Monday morning. This piece is the opposite: every goal here connects to something you can actually configure, measure, or schedule in PrestaShop, so the plan survives past January. For the year-round version of this — the calendar that decides when each promotion runs — pair it with our New Year planning guide for online stores.

Start with numbers your store already records

Before you set a single target, read your baseline from data PrestaShop is already collecting. You cannot improve average order value or retention if you do not know today's figure, and a goal without a starting number is just a wish. Two places to look:

• Stats dashboard (Stats in the back office, or the Dashboard for the headline KPIs). PrestaShop ships average order value, conversion rate, net profit per visitor, and new-vs-returning customer counts out of the box. Set the date range to last year so your targets are anchored to reality, not a guess.
• SQL Manager (Advanced Parameters → Database → SQL Manager) when the stock charts do not break a number down the way you need. A short query against the ps_orders table grouped by customer ID, for example, tells you exactly what share of orders came from people buying a second time — your real retention rate, not an industry average.

Write the baseline next to each goal. "Lift AOV from €42 to €48 by Q3" is a goal you can check; "increase AOV" is not.

Revenue is the score, not the strategy

Revenue growth is an outcome — it is what happens when the underlying drivers move. Goals land better when they target those drivers directly, and in PrestaShop most of them map to a specific tool you already own.

Average order value — the lever with the lowest cost

Lifting AOV needs no extra traffic and no extra ad spend, which is why it is often the most efficient goal on the list. PrestaShop gives you several native ways to push it:

• Spend-threshold discounts via cart rules (Catalog → Discounts → New cart rule). Set a Minimum amount condition — say €60 — and a free-shipping or percentage reward, so the customer sitting at €48 has a concrete reason to add one more item. The threshold sits a little above your current AOV by design.
• Bundles that package complementary products at a combined price, which raises the basket and the perceived deal at once. We cover the mechanics — fixed bundles vs. cross-sell prompts — in product bundling: selling more by grouping products.
• Cross-sell blocks ("Customers who bought this also bought…") on the product and cart pages, which nudge the order higher without a discount at all.

Goal shape: pick one mechanism, run it for a full quarter, and compare AOV in the Stats dashboard before and after. A modest AOV gain compounds across every order you take, so treat it as a structural change, not a one-off promo.

Retention — cheaper than the equivalent in new customers

Winning a second purchase from an existing customer usually costs far less than acquiring a new one, so a retention goal tends to pay back harder than a same-sized acquisition goal — though the exact ratio varies wildly by niche, so measure yours rather than trusting a quoted multiple. a loyalty/rewards module can carry this:

• Loyalty points and reward vouchers if your store uses a loyalty/rewards module, turning each order into credit toward the next one.
• Targeted cart rules limited to a customer group — issue a "welcome back" voucher to people whose last order was over 90 days ago (build the segment in SQL Manager, then attach the rule to that group).
• Gift cards, which bring both the buyer and the recipient into your customer base. If you do not have a voucher product yet, see gift cards for PrestaShop: adding digital vouchers.

Goal shape: define retention as "share of customers placing a second order within 12 months," read the current figure from SQL Manager, and aim for a few points higher. Small movements here change profitability more than the same movement in traffic.

Less dependence on paid traffic

If most of your visitors arrive through ads, you are renting your audience and the rent only goes up. A goal to grow the unpaid share — SEO, direct, email — is really a goal to own your demand. On the technical side that means clean URLs, a current sitemap, and meta data that actually describes each page; our financial reporting module helps you see the channel mix clearly so "60% organic" stops being a vibe and becomes a tracked line.

Operational goals you can wire into the back office

Not every goal is a sales metric. Some of the ones that pay back hardest are about removing friction and reclaiming your own time.

• Cut support response time. If first replies average a day, a four-hour target resolves problems before they turn into returns or one-star reviews. Configure order-status emails and canned replies in the Customer Service tab so the common questions answer themselves.
• Lower the return rate. Most returns trace back to a mismatch between expectation and reality. Richer product descriptions, size guides, and honest photography do more than any returns policy. Set a target of a couple of points lower and track it against your orders carrying a returned state.
• Improve page speed. A faster store converts more of the traffic you already pay for. Enable Smarty caching and CCC (combine/compress) under Advanced Parameters → Performance, and compress images. Set a concrete number — "homepage under 2.5s" — and re-measure, don't eyeball it.
• Automate one promotion you currently run by hand. If you log in at midnight to switch a sale on, that is a goal hiding in plain sight. PrestaShop lets you set From and To dates on cart rules and specific prices so the discount starts and ends without you. The full method is in scheduled discounts that start and stop automatically.

Build the promotional year, not one-off panics

A store that plans its discounting calendar in January spends the rest of the year executing instead of reacting. The two native tools do almost all the heavy lifting once you understand which is which:

If the difference between those two has ever cost you an hour of trial and error, the ground-up walkthrough is running a sale in PrestaShop: cart rules, specific prices and discount strategies. With the mechanics settled, the planning question becomes when: lay the year out with our seasonal sales calendar so every promotion has a slot instead of arriving as a surprise.

A practical decade-of-discipline goal is to enter next year's tentpoles into PrestaShop now, with dates set:

• Q1: a New Year clear-out, then a short Valentine's campaign — quick, gift-led, easy to schedule.
• Q2–Q3: defend the quiet months with a plan for the summer slump, and a back-to-school push that reaches beyond the obvious categories.
• Q4: the big one. Decide your Black Friday automation and Christmas gift-guide approach early, because nothing about Q4 should be improvised.

Decide, on purpose, what never goes on sale

A goal that protects margin is just as valuable as one that grows revenue. Discounting everything trains customers to wait for the next code and erodes the value of your best products. Part of the year's plan should be a short list of items that hold their price — new releases, exclusives, anything where the discount would cost you more than it earns. The reasoning and the back-office way to ring-fence them is in discount exclusion: why some products should never go on sale.

Make the goals SMART — and PrestaShop-checkable

A goal you cannot read off a screen at quarter-end is a goal you will quietly drop. Specific, measurable, time-bound — and tied to something the store records:

• Vague: "improve retention" → SMART: "raise the share of customers with a second order within 12 months from 24% to 29% by December, using loyalty points and a 90-day win-back voucher" (read it in SQL Manager).
• Vague: "increase AOV" → SMART: "lift average order value from €42 to €48 by Q3 with a €60 free-shipping threshold and two bundles" (read it in the Stats dashboard).
• Vague: "do more promotions" → SMART: "have all four quarterly campaigns entered as dated cart rules by 31 January, so none is launched manually."

Review every quarter, against real data

Annual goals quietly fail without check-ins. Put a recurring 90-day review on the calendar and answer four questions against the actual numbers, not your memory of them:

• On track? Compare current KPIs to the trajectory you set, straight from the Stats dashboard.
• What worked? Double down on the campaign or change that moved a metric.
• What did not? Adjust or drop it — a scheduled cart rule that produced nothing is data, not failure.
• What changed around you? A platform update, a new competitor, a supplier issue may make a target obsolete.

Lean on your financial reporting for the hard figures so each review is a reading, not an argument.

The goal underneath all the others

If you keep one principle from a decade-opening plan, make it this: build something you can sustain. A store that grows fast and burns you out is worse than one that grows steadily and still gives you a life. Most of what is above is automation in service of that — dated cart rules instead of midnight logins, scheduled specific prices instead of manual price edits, a calendar instead of a scramble. Set the targets you can read off a PrestaShop screen, wire the promotions to run themselves, and review them four times a year. That is a plan that lasts a decade, not a quarter.