Starting an Online Store: 15 Things Nobody Tells You Before You Begin

Every "how to start an online store" guide makes the same promise: pick a platform, add products, start selling. The platform part is genuinely the easy bit — PrestaShop installs in an afternoon. What nobody tells you is everything that sits around the store: the legal setup that's painful to retrofit, the back-office settings that quietly cost you sales if you leave them on default, the costs that don't appear on any pricing page, and the timeline that's two or three times longer than you expect. We run PrestaShop shops ourselves, so this list is the briefing we wish someone had given us before launch day — grounded specifically in PrestaShop, not generic e-commerce platitudes.

This is the pre-launch reality check. It deliberately stops where the next chapter begins: once you have your first orders, what to focus on in the early days takes over, and scaling past that is a separate problem entirely.

1. Your first sale will take longer than you think

Many new stores can go weeks or months without a single sale, and that's normal, not a sign the store is broken. A brand-new domain has no organic traffic, no email list, and no reputation, so every visitor has to be earned. The mistake we see is merchants tearing the store apart in week two — changing the theme, rewriting prices, abandoning the whole plan — before there's enough data to learn anything. Give it at least 90 days on a coherent strategy before you judge it. Use the quiet early weeks to fix the boring fundamentals below rather than to panic.

2. A fresh install still needs its live-store settings reviewed — you have to turn the shop ON correctly

A fresh PrestaShop install has a stack of default settings that are wrong for a live store, and nobody warns you. The big ones live in Shop Parameters → General and Shop Parameters → Maintenance: maintenance mode, the Enable Shop toggle, and — easy to miss — the SSL options under Shop Parameters → General where you must tick both Enable SSL and Enable SSL on all pages or customers will hop between http and https mid-checkout. The demo products and the default "starter" sample data should be removed before launch, not after. And the single most-forgotten one: the offline payment modules. PrestaShop ships ps_checkpayment ("Payments by check") and ps_wirepayment ("Bank wire") enabled by default — these are real offline methods, not test stubs, so if you leave one on without meaning to, a customer can place a confirmed order and simply never send the cheque or transfer. Review what's active under Payment → Payment Methods before you go live.

3. Performance is a setting, not a hope

PrestaShop is fast when configured and slow when not — and the defaults during development are the slow ones. Before launch, go to Advanced Parameters → Performance and turn on Smarty caching (set to "Never recompile"), enable CCC (Combine, Compress and Cache for CSS/JS), and if your host supports it, switch the cache to a real backend rather than the filesystem. Leaving debug mode on (_PS_MODE_DEV_ in config/defines.inc.php) in production is a classic launch-day blunder — it disables caching and exposes errors to visitors. So what? Faster pages generally improve conversion by keeping people in the funnel rather than losing them before they ever see a product, and Core Web Vitals can affect your Google search performance — so the work tends to pay twice.

4. Do the boring legal setup before you sell anything, not after

Selling online is a business, and the legal scaffolding is far harder to retrofit once orders are flowing. You need a registered business entity, a business bank account, and a tax number; in the EU you may need to register for VAT even as a sole trader, and you'll need to handle cross-border VAT (OSS) once you sell to other EU countries. Inside PrestaShop, this maps to concrete configuration: tax rates and tax rules under International → Taxes (the Taxes and Tax Rules tabs), country and zone settings under International → Locations, and the legal CMS pages (terms, privacy, returns, legal notice/imprint) under Design → Pages. PrestaShop's built-in Legal Compliance module helps assemble the mandatory notices, but it doesn't replace actual legal advice for your market.

5. "Free shipping" is not free — and PrestaShop makes the trade-off explicit

Someone always pays for shipping; if you advertise it as free, that someone is you, straight out of your margin. The useful PrestaShop detail nobody mentions: you don't have to choose between "charge shipping" and "give it away." Under Shipping → Preferences you can set a free shipping threshold (free over €X), which nudges average order value up to cover the cost, and under Shipping → Carriers you control billing by price or by weight per carrier and zone. Model the real number before you flip it on — the deeper costing question is its own topic, covered in the e-commerce costs nobody talks about.

6. SEO is a long game — but the structural decisions are made at launch

You won't rank in a month; a new domain typically takes 6–12 months to earn meaningful organic traffic. What nobody tells you is that the highest-leverage SEO work happens at launch, not later — because it's about structure you'll regret changing once URLs are indexed. Switch on Friendly URLs under Shop Parameters → Traffic & SEO before any page gets crawled, set your canonical/redirect behavior there, and fill the SEO fields (meta title/description, friendly URL) on every category and CMS page from day one. A clean, human-readable URL structure and an auto-updating sitemap submitted to Search Console are launch-day tasks, not someday tasks. Use paid traffic to carry you while the organic curve slowly builds.

7. Your real competitor is inertia, not the shop down the street

New merchants obsess over the other store selling similar products. The honest competitor map is different: it's Amazon's convenience, it's the customer's "I'll buy it later" that becomes never, and it's the trust deficit a brand-new store starts with. Your job isn't to beat a rival on features — it's to give a stranger a reason to buy from you, today. Two PrestaShop-specific levers matter most early: a credible About Us page (the most underestimated page on your store) and visible trust signals at checkout. Choosing where you can actually win is the strategy question — and the answer is usually narrower than you'd like, which is why specializing beats trying to sell everything.

8. You'll spend more to acquire a customer than their first order earns you

If you spend €10 in ads to win a customer whose first order nets €5 of margin, you lost €5 — and that's the normal case, not a failure. The whole model only works if that customer comes back, which is why you can't decide an ad budget without knowing your customer lifetime value — the number that should drive all your marketing. Don't set a customer-acquisition budget on launch day before you've read that one; it's the single financial figure most new stores get wrong.

9. Returns are part of the business, not an exception

Returns can be material, especially in fashion and apparel where they run high; treat returns as a line item you budget for, not a surprise. PrestaShop has the machinery built in — enable Merchandise Returns (RMA) under Customer Service → Merchandise Returns so customers can request returns from their account and you can manage the state transitions cleanly. A generous, clearly-stated policy usually lifts sales more than it costs, but only if your logistics can absorb it. The wider craft of handling what happens after the box ships is covered in the post-purchase experience.

10. You'll need more modules than the core ships with — budget for it

PrestaShop's core is genuinely solid, but a production store needs a handful of additions the core doesn't bundle: web analytics (GA4), GDPR cookie consent, real SEO tooling, email/marketing integration, and usually performance or security hardening. The trap nobody warns about is the second-order cost: cheap or abandoned modules that break on the next PrestaShop upgrade and quietly cost you days. Budget a real number for essentials at launch and weight it toward modules that are maintained against current PrestaShop versions, because a module that fails silently after an upgrade is more expensive than one that cost more upfront.

11. Mobile isn't optional — and you have to test the checkout on a real phone

For many consumer stores, mobile is often the majority of traffic — check your analytics — and a store that's awkward on mobile is losing a large share of its buyers. PrestaShop's default themes are responsive, but "responsive" and "actually usable thumb-first" are not the same thing. Walk the full early-days checkout flow on a real device — Chrome DevTools emulation hides keyboard, autofill, and tap-target problems that only show up on actual hardware. The checkout is where mobile friction turns directly into lost revenue, so it's the screen to test last and hardest.

12. Email is the only marketing asset you own

Social followers are rented and ad audiences vanish the day you stop paying; your email list is the one channel you keep. Start collecting addresses from launch day — a newsletter block, an account-creation opt-in, an exit offer — even if the list starts at ten people, because those ten are worth more than a thousand passive followers. Wire up a real provider early via something like Mailchimp or Klaviyo rather than bolting it on later, and remember the legal angle: opt-in consent must be explicit and logged. The payoff compounds once you start using it for retention, which is its own discipline — see building a customer retention strategy.

13. Legal compliance is broader than GDPR alone

Depending on where you sell, "compliant" means more than a cookie banner: GDPR data handling, cookie consent, terms and conditions, a privacy policy, a return policy, an imprint/legal notice, correct VAT handling, distance-selling and right-of-withdrawal disclosures, and accessibility expectations that are tightening across the EU. In PrestaShop, the consumer-facing pieces live in the CMS pages under Design → Pages and in the Legal Compliance module's pre-checkout notices; the data-protection side is handled by PrestaShop's official GDPR module (psgdpr), which you install and configure from Modules → Module Manager, plus your hosting choices. Set these up before launch — retrofitting consent and notices after you've already collected customer data is the hard way.

14. Your first design will be wrong, and that's fine

Don't spend three months perfecting the store before launch. Ship with a clean, professional theme and let real customer behavior tell you what to change — assumptions are almost always wrong about what confuses people. The PrestaShop-friendly way to learn this cheaply is session-recording tooling like Microsoft Clarity, which shows you exactly where visitors hesitate, rage-click, or abandon. A "perfect" design built on guesswork loses to a good-enough design corrected by data. Launch, watch, iterate.

15. Revenue is not profit — and cash flow is what actually kills stores

A store turning over €10,000 a month sounds healthy until you subtract product cost, shipping, ad spend, platform/hosting/modules, and payment-processing fees — and then taxes, refunds, and your own salary on top. Plenty of stores fail not because sales were missing but because the owner never noticed they were losing money on each order. Track every cost, know your margin on every product, and find your break-even point before you scale anything. This is deep enough to deserve its own treatment, so don't shortchange it: understanding your real numbers is the post that turns this from a warning into a working model.

The good news

None of this is insurmountable — millions of stores cleared the same learning curve, and PrestaShop gives you every setting you need to do it properly. The difference between the shops that make it and the ones that don't is rarely the product or the platform; it's doing the unglamorous fundamentals well: correct settings, honest costing, real legal setup, good photography, a tested checkout, and the patience to give it more than two weeks. Launch before you feel ready — you never will — fix the items above first, and let real customers, not hypotheticals, tell you what to do next.