Launch a PrestaShop store and learn from your first orders

What we would do

We would choose the next step around what is still unproven: demand, the order journey or the economics. Start with the shop you already have, including its version, theme, modules, stock data, payment and carrier integrations, target markets and the team handling orders. Check whether its existing tools can run the test before adding another module or expanding the catalogue.

Rehearse changes to checkout, tax, stock, emails or integrations on a private staging copy using representative products and destinations. Isolate test payments, customer messages and fulfilment exports from live systems. Keep the previous settings, record the checks that passed and plan a live switch with someone responsible for watching the resulting orders and restoring the configuration if the change fails.

For a mixed configuration backlog in an existing shop, the PrestaShop Full-Day Store Setup Service addresses agreed priorities within the scoped day, with no guaranteed task count; a complete store build and demand generation need separate scope.

Validate the product and its economics

Ask five questions before placing a substantial stock order: who wants the product, why they would buy from you, whether its contribution is viable, whether you can source it reliably, and whether you can ship it safely and economically.

Search trends, search-volume tools, marketplace reviews and competitor offers can suggest questions to test. Review counts reflect historical activity and can be misleading; they do not prove current attainable demand. A lack of competitors can mean several things, including a new opportunity or a difficult market.

State your proposed advantage in one sentence: product quality, specialist knowledge, compatible selection, delivery, support or price. Check whether you can deliver it at the tested price.

Cost the product beyond the supplier invoice. Include inbound freight, duties, packaging, payment fees, fulfilment, outbound freight subsidy, returns, acquisition, overhead and working capital. Set your own required contribution and break-even volume rather than adopting a universal net-margin percentage.

Order samples, assess supplier consistency and plan for lead times, minimum quantities and interruptions. A second qualified supplier can reduce dependency where practical. Large, fragile, liquid or battery products can require special handling and regulatory work. A dropship model still needs supplier and service validation.

Run a demand test with clearly defined signals

Accept backorders only when you can honour them

For a product-level test, set its quantity to zero and choose Allow orders under When out of stock in its stock settings, and use the back-order label for the promised dispatch estimate. If the product follows the global default, check Shop Parameters > Product Settings. Confirm the labels in your release. With stock management enabled, stock_available.out_of_stock controls the native backorder policy: zero denies backorders, one allows them, and two follows PS_ORDER_OUT_OF_STOCK. When stock management is disabled, this stock-policy check permits ordering regardless of that value; other purchasing restrictions still apply. A per-product choice does not itself change the global setting.

Publish a clear dispatch estimate and explain the arrangement before checkout. Native backordering uses ordinary checkout; it does not create a complete preorder-management system.

Payment timing depends on the method and its configuration. Separate paid orders, authorised payments, unpaid orders and cancellations. Ten placed orders are not necessarily ten captured payments or cash available for stock. Keep funds and processes available for refunds.

Capture availability interest

The optional official ps_emailalerts module can collect stock-notification requests and send availability emails when stock returns. The form requires enabled customer alerts, stock management and a product that does not allow backorders, as well as the appropriate rendered hook. Verify it on the actual product and combination. See the official Mail alerts implementation.

Stock alerts are held separately from newsletter registrations. Count the actual capture records under the appropriate shop and combination. A stock-alert request is interest, not an order or permission for unrelated marketing.

Use a clear landing page

Create a page under Design > Pages explaining the proposed product and its availability, with one honest call to action. Connect it to a real form or product page, then run a capped campaign aimed at the intended audience.

Ask About Product emails enquiries to the configured recipient; check whether your installed release also records enquiries in the back office before using those records to count demand. For that module's setup, use the module's setup guide.

Read test results without confusing interest and sales

Define the test budget, traffic audience, success measure and stop condition before starting. There is no universal session count or waiting period that establishes viability.

Use Best-selling products where available, product-specific reports or order-line exports for product sales. Catalog statistics mainly summarises the catalogue. Stats screens and visitor/referrer collection depend on installed modules and configuration.

Use landing-page analytics, access logs and form records to confirm successful visits and captures. Pages not found identifies broken destinations returning 404; it is not a successful-visit report.

If visits are high and adds or purchases are low, inspect audience quality, bots, availability, pricing, variants, page errors and tracking. That pattern alone does not isolate the offer as the cause.

Test analytics after consent acceptance, and confirm that refusal continues to block tracking where required. Search Console and analytics do not recreate all missing historical visits.

If your current reporting lacks product and checkout events, Google Analytics GA4 can supply them. Verify a test product view, basket change and purchase against the matching shop records, and check that any browser and server purchase reporting counts the transaction once before using it to judge campaign results.

Build a focused catalogue that customers can use

A defined audience can help you choose products, write advice and find suitable marketing channels. Specialisation is a strategy to test; it does not guarantee better rankings, conversion, margins or survival.

Assess the reachable market, purchasing frequency, service needs, competition and your knowledge. No SKU range proves that a niche is viable. A small specialist range and a larger catalogue can each work under different economics.

1. Build a coherent category tree under Catalog > Categories using buyer language.
2. Use attributes for choices that create combinations, such as size or colour. Use features for descriptive specifications.
3. Configure relevant faceted filters through the installed search/filter implementation.
4. Maintain brand and supplier data and link genuinely compatible related products.
5. Write accurate descriptions, photographs, availability, dimensions and buying advice before expanding the range.
6. Publish an About page and useful comparisons or how-to content that reflect real knowledge.

For a coffee-equipment range, colour might be a selectable combination while burr diameter is a comparison feature. Ask someone to find a grinder for their brewing method and a compatible spare part using your categories, filters and descriptions. If they cannot establish compatibility without asking you, improve those details before adding more products.

Go deeper into useful accessories, consumables and upgrades when demand supports them. Add adjacent categories deliberately. Neither page count nor a narrow topic alone confers search authority.

Review the live-store settings

Audit active payment methods rather than assuming the same defaults on every installation. An offline payment order can exist while still awaiting payment.

Under Advanced Parameters > Performance, set template compilation and Smarty caching separately. “Never recompile” is a compilation choice, not the cache switch. Plan cache clearing after template deployments. Test CSS/JavaScript optimisation options one at a time with your theme and checkout.

Turn public debugging off for production. Debug mode changes diagnostics and execution behaviour; it does not universally disable all caches. Review application, Smarty, server and CDN caching separately, including customer-specific pages.

Set friendly URLs, canonical-host behaviour and metadata before launch, generate a sitemap through the installed tool and verify Search Console. Organic growth has no guaranteed timetable. Check HTTPS configuration before publishing permanent redirects.

Resolve business and legal requirements before selling

Business registration, tax identification and banking requirements depend on your jurisdiction and legal structure. Incorporation is not a universal requirement for every trader. For example, UK sole traders are not generally required to hold a separate business bank account, although bank terms and recordkeeping still matter. See UK business banking guidance.

For qualifying sellers established in only one EU Member State, a combined €10,000 threshold can affect the place of taxation for eligible cross-border B2C goods and certain electronic services. Check its conditions and current and previous calendar years. Destination VAT can apply in other circumstances or by election. OSS is an optional reporting simplification, not mandatory from every first foreign sale. Use the Commission's OSS guidance with advice for your transactions.

Check consumer disclosures, withdrawal, privacy, cookies, product safety and accessibility for the markets you target. The European Accessibility Act has applied to in-scope services since 28 June 2025, subject to exemptions and national implementation. Use the EU compliance guide for the practical scope checks.

Do not rely on the archived Legal Compliance module as a maintained compliance solution. GDPR tooling and a consent layer can support parts of your workflow; they do not complete the legal work for you.

For newsletter acquisition, use a documented opt-in and a working unsubscribe process. Email-marketing rules vary by country and recipient type. In the UK, a products-and-services soft opt-in can apply when all its collection, similar-offer and opt-out conditions are met; it is separate from GDPR consent. Check the ICO electronic-mail rules before relying on that exception.

Prove the first orders end to end

Use the first few orders as a controlled operational check. They are real revenue and real obligations, even when you also use them to learn.

Keep an order acceptance worksheet

Record the tester, shop configuration, product and combination, destination, payment method and result for each journey. Use the worksheet on staging, then verify the agreed live journey under your provider's production-testing rules. Keep a failed check open with an owner and a next action.

At 20 minutes each, five orders require 100 minutes of fulfilment work. Whether that is sustainable depends on staffing, contribution and other work. Measure your actual capacity before increasing campaign spend.

Invoices are managed under Orders > Invoices. Delivery-slip settings and batch PDFs are under Orders > Delivery Slips. Thermal carrier labels normally come from a carrier integration or label service, rather than these core PDFs.

Use early orders to improve service and fulfilment

Keep a list of recurring questions, delivery problems, returns and stock discrepancies. Improve the relevant product information, size guide, delivery estimate or help text, then check whether the problem recurs.

Use Orders > Shopping Carts to inspect carts without an associated order, while remembering that saved carts are not all failed checkout attempts. Combine that view with actual funnel checks and customer feedback.

Review sales and channel data with its collection limits. Where available, use the best-selling products report for the test period to spot products that may deserve stock or more visible placement, and compare contribution, availability and promotion effects before favouring them. Develop a few measurable acquisition tests rather than spreading an unmeasured budget across many channels.

Use order-list bulk actions for supported status changes. Generate batch delivery-slip PDFs on the dedicated Delivery Slips page. Batch picking and packing if it fits your promised dispatch times.

Choose packaging sizes from the products and carrier constraints, and organise a packing station around the work you time. Automate repetitive tasks such as stock alerts, accounting exports and appropriate customer messages only after their rules are clear.

Ask for honest reviews or feedback after customers have had time to use the product. Timing depends on delivery and the product; no order-count milestone is required. Apply applicable communication rules and publish reviews fairly. Track actual repeat purchases alongside stated satisfaction.

Work through a failed checkout before increasing spend

In this hypothetical launch test, a guest adds a coffee grinder and a compatible spare part, enters a supported delivery address and reaches checkout with no carrier available. Enquiries suggested interest, but this basket cannot become a sale. Keep the campaign capped while you resolve the failed journey.

1. Record the product combinations, quantities, packed weight, destination, customer group and expected delivery service. Keep the error and the checkout stage so the developer can repeat the same case.
2. Reproduce it on staging with the current theme and carrier modules. In this example, the destination zone is enabled, but the weight calculated from the basket's product and combination data falls outside the carrier's configured ranges and its out-of-range behaviour disables that carrier. Record the calculated weight separately from the physical packed weight used for carrier limits and costs. Confirm the intended price and service, then correct that range rather than changing unrelated checkout settings.
3. Retest the original basket, weights around the changed boundary and a destination you do not serve. The intended baskets must receive the agreed quote; the excluded destination must remain excluded. Repeat the affected payment, stock and order-email checks.
4. Record the previous carrier settings and apply the validated change in the planned live window. Repeat the agreed checks and have the responsible person watch subsequent orders for missing delivery options or unexpected charges.

At your first-month review, compare eligible checkout attempts with completed paid orders, list any repeat carrier failures and reconcile actual packing and delivery costs against the amount allowed in your pricing. Read the same product, destination and channel where your reporting permits it. A useful result is a working delivery quote in the agreed cases and fulfilled orders that meet your contribution and dispatch targets. If checkout now works but orders remain weak, return to the audience, offer and price tests before increasing spend.

What to ask the developer or agency

1. Which existing modules, integrations, theme changes and imported data affect the failed journey, and which configuration was tested?
2. Can you show the original failure, the scoped change and the passing result for that exact basket?
3. What will you change at the live switch, what can be restored safely, and who checks the orders afterwards?
4. Which backlog items remain, who owns them and which ones prevent the planned launch?

Decide when to expand

Budget for hosting, maintenance, services and any modules your requirements justify. Check compatibility, support, security and total maintenance cost rather than treating a large module count as a launch requirement.

Review contribution, cash flow, stock funding, fulfilment capacity and acquisition cost together. Do not finance a loss-making first order with assumed future lifetime value before you have repeat-purchase data.

Set a launch review date and spending limit suited to your market. Investigate early failures immediately, but avoid rebuilding the theme or catalogue every few days without a testable reason.

Expand advertising or stock in steps once the order journey works and the economics support it. Keep enough cash and operational capacity for refunds, returns and supplier delays.

Questions owners ask

Can I test a new product while my existing shop keeps selling?

Yes. Limit the test to the intended products and audience, and separate its records from established sales. Check that a stock, carrier or payment change does not alter unrelated products or other shops in a multistore installation.

Do orders from friends prove demand?

They can help you exercise the order journey. Record purchases encouraged by a personal relationship or an exceptional discount separately, because they may not represent strangers buying at your intended terms.

Can I launch with unfinished tasks?

Sort the backlog by its effect on customers. Resolve failures in taking payment, charging the correct total, meeting selling obligations or delivering what you promise before accepting affected orders. Cosmetic improvements can have a named owner and a later review date.

Should I copy the staging database back at launch?

An existing shop may have gained customers, orders, payments and stock movements since the copy was made. Apply the tested configuration or a planned migration that preserves those live records. A rollback must also protect orders taken after the switch.