Your First 100 Orders: What to Focus On in the Early Days

Your PrestaShop store is live and the first orders are trickling in. The stretch from order one to order one hundred is not really about money — at this volume it can't be. It's the only window where you can watch every part of your operation run for real, on small enough numbers that you can still inspect each order by hand. Get into the habit of reading what those orders are telling you now, and you reach order 101 with a store you actually understand. Coast through them on autopilot and you arrive at the same number with a hundred receipts and no lessons. This guide is about what to look at, where to find it in the PrestaShop back office, and which decisions are worth making this early — and which are not.

If you haven't opened the doors yet, the honest pre-launch checklist lives in 15 things nobody tells you before you begin. This post picks up the moment real orders start landing.

Orders 1–10: prove the plumbing works end to end

Your first ten orders are validation, not revenue. The single most expensive mistake at this stage is assuming that because the store looks finished, the money, the emails, and the labels all flow correctly. They often don't, and a real customer is the worst person to discover it for you. Walk every one of these in the back office while you still have time to read each order line by line.

• Confirmation emails actually send — and look right. PrestaShop's core sends the order-confirmation mail (from the PaymentModule class when payment is validated), rendering the templates under mails/. After your first order, go to Advanced Parameters → E-mail, send a test email to confirm delivery works, then place a real order against yourself and confirm "Order confirmation" actually arrived. Open the email itself: are product names, the price, VAT line and shipping all correct? A surprising number of new stores have SMTP misconfigured under Advanced Parameters → E-mail → Set my own SMTP parameters and silently send nothing. Place that test order before you trust it.
• The money landed, after fees. Open the order in Orders → Orders, note the total, then reconcile it against your payment provider's dashboard (Stripe, PayPal, your acquirer). The gateway figure will be lower — that gap is the processing fee, and it's the first of the costs that quietly eat your margin. Those hidden costs deserve their own read: e-commerce costs nobody talks about.
• Order statuses move the way you think they do. PrestaShop's order-status workflow (Shop Parameters → Order Settings → Statuses) decides which emails fire and when. Confirm that "Payment accepted", "Processing in progress" and "Shipped" each trigger the customer email you expect — and that none of them fire twice. A status that emails on every save is a classic early annoyance.
• Stock decrements correctly. Check the product in Catalog → Products → Quantities before and after the order. If you sell the same SKU in several combinations, confirm the right combination dropped. Getting this wrong early means overselling later.
• Time yourself fulfilling. Pack the first few orders with a stopwatch running. Finding the product, packing it, generating the delivery slip from Orders → Delivery Slips, printing the label, handing it to the carrier — how long, honestly? Twenty minutes per order is survivable at five a week and impossible at five a day. You're measuring this now so future-you knows what to fix first.
• The customer's post-purchase view works. Log in as a test customer and follow your own order: is the tracking number attached to the shipment, does "Track this order" resolve, does the order history page render? The whole experience after "thank you" is more load-bearing than most owners expect — what happens after the order matters.

Orders 10–50: read the patterns PrestaShop is already recording

Once the plumbing is proven, the job changes from checking to listening. By order fifty you have enough data points that patterns start to surface, and PrestaShop has been logging most of them for you without being asked.

What people actually buy — not what you hoped

Go to Stats → Best-selling products and set the date range to cover your whole run so far. The product you built the homepage around may be languishing while a near-afterthought is carrying you. Don't argue with it — lean in. Move the real winners into a featured position, reorder your Home category, and make sure those products are the ones your "Popular" block surfaces. The "Catalog evaluation" stat in the same menu flags products with no image, no description, or no sales — fix those before adding anything new.

One related early temptation: piling on more products to look bigger. Resist it. Ten products with real photos, honest descriptions and correct combinations outsell a hundred half-finished ones, and a wide thin catalogue is exactly what triggers the next problem. If you're still deciding what belongs in the catalogue at all, validate before you invest: how to validate products before you invest, and on why a tight range wins, why specializing beats trying to sell everything.

Where customers actually come from

Open Stats → Visitors origin and Stats → Best referrers. If most of your first orders trace back to one Instagram post, that's not a tie-breaker — that's your answer about where the next month's effort goes. Spreading yourself evenly across five channels at this stage just means doing five things badly. Make sure the data is trustworthy first: connect Google Search Console and verify Google Analytics is firing (install and configure a Google Analytics or GA4 module under Modules — confirm the tracking ID is set and that it isn't being blocked by your cookie-consent banner before you trust a single number).

The questions customers keep asking

Keep a running list of every pre-sale and post-sale question. By order forty you'll see the same three or four repeating, and each repeat is a product page failing to do its job. Five "what size is this?" messages mean your size guide is missing or buried. Three "when will it arrive?" messages mean delivery information isn't visible before checkout. The fix isn't to answer faster — it's to make the question stop occurring: edit the product description, add the detail to Catalog → Products → Description, and surface shipping and returns where they're actually read. A maintained FAQ block carries a lot of this load once the patterns are clear. Answering quickly still matters while you're closing the gaps, and we mean it about that: why we answer every ticket within hours.

Carts that fill but don't convert

PrestaShop records this directly: Orders → Shopping Carts shows carts with no associated order, and Stats → Best-selling products plus the conversion figures on your dashboard tell you the scale. At this stage the usual early leaks are blunt — shipping cost that only appears at the final step, a missing payment method, forced account creation, or a store too new to look trustworthy. You don't need a sophisticated diagnosis yet: place a real order on your own phone, note every step that made you hesitate, and fix those first. Make sure guest checkout is enabled under Shop Parameters → Customer Settings and that your shipping cost is visible before the final step, not sprung at the end.

Orders 50–100: tighten the operation before volume forces it

By now the store works and you know its rhythm. This phase is about removing the manual friction that's bearable at five orders a day and miserable at twenty — while you still have the breathing room to set it up calmly.

Streamline fulfillment inside PrestaShop

• Batch, don't trickle. Use the bulk actions in Orders → Orders to change status and generate delivery slips for a whole batch at once, then pack once or twice a day rather than reacting to each ping.
• Print, don't cut. Keep paperwork and shipping labels separate: PrestaShop's delivery slip and invoice PDFs (configurable under Shop Parameters → Order Settings → Invoices) are document PDFs for your records, while thermal shipping labels normally come from a carrier module or label tool rather than the core document templates.
• Standardize packaging to two or three box sizes so weight-based carrier rules in Shipping → Carriers stay predictable and your shipping cost stops being a surprise on every order.
• Build a packing station where the label printer, tape, fillers and your most-sold SKUs are within arm's reach. It sounds trivial; it's the single biggest minutes-per-order win at this stage.

Automate the repetitive admin

Anything you do by hand on every order is a candidate for automation now. PrestaShop's own status workflow already handles "email the customer when the order ships" if you've wired your statuses correctly. Beyond that, the high-value early automations are low-stock alerts so you stop overselling, a post-purchase review request on a timer, and an accounting export so you're not retyping order totals into a spreadsheet. Where the native back office stops, that's exactly the gap our mypresta.rocks modules are built to close — chosen so configuration happens from your back office, not a developer invoice, and so they survive a PrestaShop upgrade instead of breaking at the next one. Whether to keep a task in-house or hand it off is itself a decision worth making deliberately: what to delegate and what to keep in-house.

Start banking social proof

Fifty fulfilled orders is enough satisfied customers to begin collecting reviews, and early reviews are worth more than later ones because they move you from "unknown new shop" to "shop other people have trusted." The simplest mechanism is a product-review request emailed 7–10 days after delivery — long enough that the product has arrived and been used. Your happiest early buyers are also your first showcase material; letting them speak for you is one of the cheapest forms of marketing a new store has: letting your best customers sell for you.

Five mistakes that quietly waste the first 100 orders

That last one is worth its own sitting before you set a single price, because "cost" includes a lot more than what you paid the supplier: understanding your real numbers.

The one question worth asking after each order

Through the whole first hundred, one signal outranks every dashboard: would this customer buy from you again? Not "were they satisfied" — actually return, at full price, without a discount to drag them back. If the answer is yes for most of your first hundred, you have a real business and can think about scaling. If it's no — they came for a coupon and the experience was forgettable — then more traffic only multiplies a leak, and the fundamentals come first.

You can ask directly, and you should. A short, plain email outperforms any survey tool: "Thank you for your order. We're a new store and your honest take is genuinely valuable to us — what did we get right, and what should we fix?" The replies will teach you more than a week of staring at Stats. That repeat-purchase instinct is the seed of every retention and lifetime-value decision you'll make later — when you're ready to formalize it, start with building a customer retention strategy and the number that should anchor your marketing, customer lifetime value.

The first 100 orders aren't a milestone to rush past — they're the only cheap, low-stakes laboratory your store will ever have. Spend them proving the plumbing, reading the patterns PrestaShop already records for you, and tightening operations before volume forces your hand. Do that, and the leap from a hundred orders to a thousand becomes an engineering problem rather than a panic — which is exactly the next chapter: scaling your PrestaShop store.