Seasonal promotions in PrestaShop: a practical calendar

What we would do

We would choose the events your shop can fulfil profitably, then build the simplest offer that fits each one. Start with existing categories, native packs and dated price or cart rules. Add automation when maintaining the tested schedule becomes the problem. A small team with manual stock updates needs a different campaign from a shop with reliable warehouse synchronisation and staff watching orders throughout the event.

The route depends on your installed PrestaShop version and discount interface, theme, checkout, pricing modules, stock and feed integrations, customer data, destination markets and available staff. Inventory existing offers and the system that controls prices before adding another scheduler. A connector that overwrites prices or stock can undo an otherwise correct campaign.

Make the change on a staging copy that represents that setup. Isolate customer emails, payments, warehouse exports and feed publishing, then rehearse launch, checkout, expiry and reversal. Record the approved settings, switch them into production in a planned window and keep the previous configuration available. Nominate someone to check the live result and pause the campaign if it fails.

Choose a campaign your team can support

If an existing module needs setting up for the agreed campaign, the PrestaShop Module Installation & Configuration Service covers its installation, agreed configuration and relevant journey checks.

Build a calendar for your market

Choose events that fit your catalogue, your customers and your fulfilment capacity. A launch, useful buying guide or bundle can be a campaign without a price cut. Leave room for normal trading between promotions.

Use this as a menu, not a requirement to run every event. For example, test a study-space campaign for furniture, a spring project guide for garden products or a budget-planning campaign for business buyers. Treat those ideas as hypotheses for your audience.

For each chosen event, record the market, dates, objective, offer, eligible products, margin floor, stock allocation, preparation deadline and responsible person. Add the email sequence, landing page, banners and recovery plan. Keep last year's configuration beside its results so you can adapt it.

Prepare Black Friday and other traffic peaks

Work backwards from your launch date. The following schedule is an example. Adjust it to the size of your changes and your team's testing time.

Test the complete customer journey

Use your own traffic history and campaign forecast to define load scenarios. Measure response times, errors, PHP worker saturation, database work and payment-provider latency. In staging, exercise category and product pages, add to cart, addresses, carrier selection, a sandbox payment, any payment callback or webhook, the resulting order status and the order confirmation. Include mobile browsers. Isolate staging email and payment credentials so tests do not reach customers.

Ask your host what happens when the measured workload grows: worker limits, CPU throttling, database capacity and scaling lead time. Check certificate expiry and external uptime alerts. A homepage monitor alone does not confirm that checkout works.

Configure each cache layer deliberately

• Under Advanced Parameters > Performance, review Smarty compilation and caching. For a stable production release, avoid forced recompilation. If you choose never to recompile, include compiled-template clearing in your deployment process.
• Test smart cache for CSS and JavaScript with your theme, checkout and consent controls. Apache optimisation applies to an Apache deployment; Nginx settings belong in the server configuration.
• Check OPcache in the web PHP service. To enable it, change the active PHP configuration and reload the relevant service. Invalidation handles stale bytecode; clearing a disabled cache does not enable it. Follow the PHP OPcache configuration reference.
• Native caching options include Memcached integrations when the relevant PHP extension is available. Redis needs an additional integration. Smarty cache, query/object cache, full-page cache, OPcache and PHP session storage have different roles.
• A full-page cache or reverse proxy needs correct customer, currency, language and price variation. Exclude personalised cart, checkout, account and payment responses. Cached browsing can reduce aggregate database demand; test checkout capacity separately.

Right-size product images and check mobile loading. Profile expensive SQL before changing database settings or deleting records. Old cart rows alone do not prove a bottleneck.

During the freeze, execute the tested campaign configuration. Route urgent security fixes through testing and a rollback plan. Assign who can pause an offer, change ad budgets and communicate an incident.

If preparation starts late

Keep the launch date only if the essential checks fit the time remaining. Reuse a working layout and offer mechanism, narrow the range and defer an optional redesign, migration or new discount interface. A smaller campaign with verified prices and delivery terms is a workable late-start plan.

1. Confirm the promoted stock, fulfilment capacity and contribution floor. Remove products whose availability or costs you cannot verify.
2. Complete the customer journey with the chosen offer, an existing voucher and a protected product. Check the payment result and the order received by staff, including any stock or warehouse hand-off.
3. Rehearse the start and end on the copy, then approve the production settings, cache actions, messages and feed submission. Leave time for the external platforms you use to process changes.
4. Check that the named people can monitor launch and act on an error. Reduce the campaign or postpone it if checkout, pricing or dispatch remains unresolved.

During the event, investigate a slowdown using the prepared monitoring and host escalation route. Pause affected offers or paid traffic when necessary. Introduce an urgent fix through the tested reversal process rather than adding an untested cache or pricing module under load.

Choose and schedule the right discount

The paths below describe the established Cart Rules and Catalog Price Rules interface in modern PrestaShop. In PrestaShop 1.6, these tools are under Price Rules. PrestaShop 9.1 also introduces an experimental discount interface, disabled by default; test its workflow and module compatibility separately. See the PrestaShop 9.1 changes.

Specific prices affect the amount shown while browsing. Theme support and the pricing context determine how the previous price appears. Cart rules apply to a qualifying basket. Read the discount guide before mixing mechanisms.

1. Build and test each offer in staging. For a native unattended launch, save the production cart rule enabled, with a future start and enough available uses. A disabled rule stays disabled when its start date arrives.
2. Set validity dates and total/per-customer quantities under Conditions. Set priority and status under Information. Set the reduction, gift or free shipping under Actions.
3. Give specific prices and catalog price rules explicit start and end dates too. Ending a dated reduction stops that reduction; another eligible price may still apply. Editing a base price directly creates no automatic restoration.
4. For a Friday-through-Monday offer, set the end to Monday at 23:59:59 in the intended shop time zone. Check International > Localization and the configured time zone. PHP uses PS_TIMEZONE; some cart-rule SQL uses database time. Ask your host to check their alignment, including daylight-saving changes.
5. Test before, during and after the window. Refresh browser pages and plan cache expiry or purges at both boundaries. An already-open product page does not automatically update when a date passes.

Native dates are evaluated when the shop calculates eligibility; they are not a browser push or a scheduled base-price rewrite. Native rules do not repeat annually on their own, but you can reuse them by editing dates, quantities and conditions.

For rotations and campaign automation, use the Smart Dynamic & Scheduled Discounts help page or the Sales Revolution help page for the relevant module workflow.

Test stacking and protect your margin

Calculate the contribution after product cost, discounts, payment fees, fulfilment and any shipping subsidy. Check the actual basket total and the recorded order, not just the rule form.

• For an illustrative tiered offer, you could test 10% above €75, 15% above €150 and 20% above €250. Set compatibility so only the intended tier applies. Lower priority numbers are processed first in the established cart-rule system; priority alone is not a complete exclusion policy.
• For a category sale such as 20% off electronics, test a catalog price rule when the reduced price should appear while browsing.
• For free shipping above €50, check the minimum amount's tax and shipping basis, eligible carriers, countries and compatibility with other offers. Choose a threshold from your costs, not a presumed conversion advantage.
• For a percentage voucher, review Exclude discounted products. Test mixed baskets with specific prices and customer-group reductions. A restriction that makes products qualify for a rule is separate from the products receiving its reduction.
• Review old loyalty codes and standing vouchers before the event. Restrict incompatible offers deliberately and honour existing customer commitments.
• Test below, at and above thresholds; product combinations; guest and registered customers; currencies; customer groups; usage caps; and the final permitted redemption.

There is no universal native product flag that protects an item from every possible pricing mechanism. Keep a list of protected products and test each relevant offer. For module-based protection with separate voucher and catalogue scopes, use the Discount Exclusion Manager help page; its scope does not cover arbitrary base-price edits or every third-party pricing system.

Prepare the evidence behind a public saving

Before announcing a public price reduction, confirm whether the destination market requires a prior-price reference and which reductions fall in scope. Keep dated evidence for the relevant product or combination, shop, country and currency. A theme's crossed-out price alone does not establish the reference you may use in an advert.

Omnibus Price Compliance records public prices and displays supported prior-price references. Installation does not supply missing historical records: a reference stays hidden until there is enough evidence for the required period before the reduction starts, and cart references stay hidden when a cart rule applies. Agree the applicable evidence and presentation before the announcement, and check the storefront, campaign wording and feed together.

Prepare landing pages, feeds and messages

1. Create a seasonal category under Catalog > Categories, or an editorial landing page under Design > Pages. A product can belong to its normal category and the seasonal category. Give the campaign useful copy and a durable friendly URL.
2. For recipient, budget or interest filters, configure the appropriate product features and the Faceted Search module's category/filter template. A category does not acquire every gift filter automatically. Put editorial context on the category or landing page if it should not appear on the product elsewhere.
3. Link from the homepage, menu, campaign email and ads. Schedule a teaser separately from the price reduction. Coordinate banners, badges and landing-page copy with both the start and finish.
4. For Shopping feeds, keep the ordinary price accurate and submit sale_price and sale_price_effective_date where applicable. Check feed processing and landing-page prices. A sale annotation remains subject to Google's rules and is not guaranteed. See Google's sale-price requirements.
5. Prepare a message sequence appropriate to the event: teaser, preview or early access, main offer, reminder and a truthful last chance. Test rendering and links on mobile and common email clients. Set ad budgets, audience rules and scheduled social posts before launch.

Segment recent buyers, dormant customers, subscribers or people who bought in the same season previously. Export only the fields you need, use an authorised reporting workflow and apply your current consent and suppression rules. A newsletter flag alone may not capture every unsubscribe recorded in your sending platform. Keep service messages separate from promotional follow-ups.

When a feed or stock connector runs during the campaign, test its next scheduled update as well as the initial export. Confirm that it preserves the intended sale window and does not publish a cached price or replace the approved stock allocation. Record which integration owns the ordinary price, sale price and available quantity.

Submit relevant updated URLs through your normal sitemap process. Publishing early allows time for crawling but does not guarantee indexing, rankings or traffic.

After the event, remove campaign banners and prominent menu links. If you want a reusable search landing page, keep it accessible with useful off-season content. Deactivating a category can return a redirect, 404 or 410 according to its settings. It is not simply hiding a menu item.

For banner creation and its module-specific options, use the Banner Revolution help page.

Run a practical Valentine's campaign

Start with a focused gift selection, for example 10 to 20 suitable products, grouped by recipient, interest or price band. Use a category for browsing and an editorial page when the selection needs explanation. Test the campaign against actual stock and your last shipping dates before 14 February.

Possible offers include a dated LOVE10 code, a pair of complementary products or free express shipping above an illustrative €60 threshold. For the shipping offer, restrict the carrier and test the minimum amount. For a pair offer, configure both the qualifying products and the reduction target. Check compatibility if a code should work with free shipping.

Enable Offer gift wrapping under Shop Parameters > Order Settings and set the price and tax treatment. Its associated gift-message field appears during checkout, in the delivery step of the standard modern checkout. There is no separate native gift-message enable switch. PrestaShop 1.6 uses Preferences > Orders.

Native wrapping has a configured fixed fee. A normal cart rule does not conditionally remove that fee above a spend threshold. Choose free wrapping for the campaign, a separately modelled service product with suitable fulfilment handling, or an extension before advertising a threshold offer. Include materials, labour and tax when costing wrapping.

Use real carrier cutoffs in the homepage notice, relevant product content and checkout messaging. Change the message when standard delivery closes, then when express closes. Offer digital gift cards only if your gift-card workflow is configured and tested; payment checks and email delivery can delay availability. Native cart-rule vouchers alone are not a complete sellable gift-card system.

After the day, confirm discounts expired, remove seasonal banners, review remaining occasion-specific stock and record results. Send any promotional thank-you or next-purchase message only to eligible recipients.

Adapt back-to-school campaigns to local dates

Choose a real use for your products: a desk, chair and lamp for a study space; a device with its required accessories; lunchboxes and food containers; a skincare starter set; fitness essentials for returning routines; or suitable pet enrichment products for a changing household schedule. Avoid making health or behavioural promises from the seasonal theme.

Create a Back to School or Back to Routine category and add existing products without removing their normal assignments. Write useful copy, translate it and maintain the same appropriate URL across seasons. Add a few coherent bundles using native Pack of products where a fixed set fits. Combinations are variants of one product, not bundles.

Check official school, local authority and university calendars for each target region and year. Germany varies by state; the UK varies between nations and local authorities, including August returns in parts of Scotland. Spain and Italy also use regional calendars. Separate university and adult-course dates from school dates.

Translate content per language, but target specific prices using supported shop, country, currency, customer or group conditions. There is no language condition on a specific price, and a currency does not identify a country. Test how the shop establishes the customer's country before and after an address is entered. In multistore, verify shop associations and date windows for each market.

Compare a free-shipping threshold, an accessory offer and a modest reduction using your own contribution figures. Confirm bundle availability, product quantities and out-of-stock settings. Place a mobile test order from the campaign landing page and check speed with your production cache settings.

For a reusable customer-group segment, modern PrestaShop uses Shop Parameters > Customer Settings > Groups; Customers > Groups is a legacy location. Populate groups through supported administration or an appropriate integration, and review any pricing effects. Use the segment for relevant later campaigns only with the required permissions.

Rehearse a study-space bundle

Suppose your back-to-school selection contains a desk, chair and lamp. You want to sell the setup together while keeping each item available separately. Use a native Pack of products if the contents are fixed; use a guide linking the separate items when shoppers need to choose their own set. A category alone does not create a pack or reserve its components.

1. List the exact products or combinations, the quantity needed for each set and the stock source. Check what happens when a component also sells separately or its supplier feed changes availability.
2. Cost the complete parcel or parcels, including bulky-item delivery, packing and any shipping subsidy. Compare the pack's contribution with selling those items separately. Reject a proposed saving if the actual carrier cost takes it below your floor.
3. Configure the chosen pack-stock behaviour and out-of-stock policy. On the copy, order the set, then check the remaining pack and component quantities and the warehouse picking instructions.
4. Make a required component unavailable. Verify whether the configured policy blocks the pack or permits an explicitly described back-order. Check how cancellation or a return restores stock in the workflow your staff use.
5. Repeat for a destination where bulky delivery differs. If the chair cannot ship there, remove that destination from the offer or present a suitable alternative instead of promising the same set everywhere.

Keep the tested product references, expected quantities, order totals and delivery choices with the campaign record. You can then repeat the same checks when the supplier feed, pack contents or seasonal dates change.

Prepare Christmas gifts and fulfilment

Build recipient, price-band and interest selections early enough to check their products, links and stock. Maintain useful persistent pages without promising a ranking benefit. A CMS gift guide needs regular availability checks; catalogue categories with configured filters can support live browsing.

Name and photograph a bundle as a complete gift, such as a coffee-lover kit. Set its price and pack-stock behaviour deliberately. For gift cards, test purchase, recipient information, delivery timing, redemption and support handling before featuring them in last-minute messages.

Check gift wrapping, the associated checkout message and the warehouse instructions. Omitting prices from parcel paperwork is a fulfilment or extension workflow; selecting gift wrapping does not automatically suppress invoice information.

Base shipping cutoffs on carrier services, destination coverage, processing time, stock and holiday closures. Distinguish an estimate from a delivery guarantee. Review messages when cutoffs pass rather than leaving an expired promise visible.

For product-page estimates based on product or combination lead times, processing settings and default-carrier transit settings, use the Estimated Delivery Date help page; it shows estimates on product pages, in the cart and at checkout and saves the accepted estimate with the order. Test your installed release's destination and carrier settings: an estimate is not a delivery guarantee.

A possible sequence is gift-guide awareness in autumn, a separately prepared November sale, December gift sets, a reminder before the real shipping cutoff and digital alternatives afterwards. Choose frequency from your audience response. Use honest deadlines and stock quantities, including any countdown. Do not reset a supposed final deadline for each visitor.

Forecast from past sales, current demand, supplier lead times, carrying costs and markdown risk. Compare the cost of a stockout with the cost of excess stock. Prepare returns and support cover as well as dispatch. Continue monitoring checkout and payments through December.

Use a quiet season without assuming the cause

A gradual sales decline does not prove seasonality, and lower recorded traffic does not prove lower demand. Compare matching periods and account for changed campaign dates. Use the pattern below to choose an investigation before changing prices.

If demand is lower, choose useful work from a prioritised list: fix product copy, improve photography, write buying guides and FAQs, profile slow hooks and SQL, test updates, remove unused modules and prepare upcoming campaigns. Installed modules have different hooks and costs. On a private staging copy, enable _PS_DEBUG_PROFILING_ in config/defines.inc.php and compare category and product profiles to find costly hooks and SQL. Switch profiling off afterwards and confirm that debug mode and profiling are off in production.

Back up before maintenance and use staging. For database cleanup, set retention limits and inspect dependencies. Preserve order-linked carts and referenced guests. Core cart deletion also handles cart products, cart rules, customisations and associated files; deleting two tables manually is not equivalent. Do not truncate search indexes or operational logs as a generic speed fix.

For the supported cleanup workflow, use the Database Cleanup help page. Follow your retention obligations and confirm recovery before deleting data.

Commercial experiments can include a complementary bundle, suitable occasion gifts, a tested gift-card offer, business outreach or pre-orders with clear delivery terms. Cost each idea. A time-limited clearance can be reasonable; a blanket price cut is not a diagnosis.

Review orders, conversion, average order value, acquisition source and contribution on a regular schedule appropriate to volume. Use weekly comparisons and matched seasonal periods for planning while keeping automated outage and payment alerts active.

Turn results into next year's plan

After each event, record revenue, contribution, returns, acquisition costs, checkout completion, fulfilment time and support load. Compare both the campaign and adjacent periods. A dip before or after an event can have several causes; it does not by itself prove customers waited for discounts.

Use a consistently configured analytics system for channel conversion and revenue. Native visitor, origin and sales panels are different reports. For repeat-order analysis, define a customer as returning only after a prior qualifying order, then separate first-order and repeat-order revenue for the same period and shop.

Choose a manageable set of goals, such as one financial goal, one operational improvement and one growth initiative. Base targets on capacity and demand. Break each into quarterly milestones and a concrete monthly action.

Revenue = sessions × orders per session × average order value
100,000 × 0.02 × €65 = €130,000
120,000 × 0.02 × €65 = €156,000
100,000 × 0.024 × €65 = €156,000
100,000 × 0.02 × €78 = €156,000

These are planning examples, not growth benchmarks. Increasing traffic by 10%, conversion by 5% relatively and order value by 5% gives a combined factor of 1.10 × 1.05 × 1.05 = 1.21275, about 21.3%. Check that your session, order and revenue definitions match and allow for refunds and costs.

An illustrative quarterly plan could establish clean reporting and improve key product pages in Q1, test content and a limited acquisition budget in Q2, prepare peak-season stock and campaigns in Q3, then execute and monitor them in Q4. Adapt that sequence to your trading year. For each milestone, record the baseline, owner, available budget, completion evidence and review date.

For example, a shop that repeatedly misses its shipping promise can make dispatch reliability the operational goal. Record the current order-to-dispatch pattern, assign the warehouse lead to correct stock and cutoff instructions, and review late orders and support contacts before the next campaign. If warehouse capacity remains the constraint, plan a narrower offer rather than treating extra traffic as the solution.

Map every target to an action: packs or appropriately scoped offers for basket value, dated rules for scheduled campaigns, catalogue rules for selected clearance stock, and suitable customer segments for reactivation. Include profitability, customer satisfaction, time per order, return rates and a sustainable workload.

For orders, refunds and recorded operating costs in the same reporting workspace, Financial Revolution provides profit, cash-flow and VAT reports. Include the relevant advertising, delivery and other expenses in the records before using a report to judge the campaign.

Hold a short monthly review: check the target, record what changed, decide whether the plan needs adjustment and name the next action. Reuse successful configurations with new dates and limits. Retire campaigns that did not justify their cost.

What to ask your developer or agency

Ask for a campaign record your staff can use during launch, not just confirmation that a module is enabled. Keep it alongside the calendar row and make the person responsible for each action explicit.

• Which shop version, discount interface, module releases and theme were tested? Does the copy include the pricing, warehouse and feed integrations that run on production?
• Which system writes each price and stock value, and can a later import overwrite the campaign? If automation needs a scheduled task, who checks that it runs?
• Where are the expected basket totals, protected-product checks and completed test orders? What happened at both date boundaries with the production cache configuration?
• Which exact settings move to production, who approves them and how do staff pause or withdraw the offer? Include the matching banner, email, feed and ad actions.
• Which failures trigger a pause or escalation, who can reach the host and payment maintainer, and who handles affected customers?
• Who confirms expiry, restores ad budgets, reviews fulfilment and records the result? Keep screenshots, configuration notes and redacted order references with that sign-off.

Questions owners ask

Can I copy the tested staging database over the live shop?

A running shop keeps receiving orders, customers and stock changes while you rehearse. Move the agreed campaign configuration through a controlled process that preserves those live records. A database replacement needs a separate synchronisation and cutover plan.

What if a wrong price appears after launch?

Pause the affected promotion and acquisition messages, keep the product and order references, and compare the displayed price with the basket and recorded order. Follow your agreed customer-service and escalation process before altering an accepted order; reverting a rule does not resolve orders already placed.

Can I extend a sale when stock remains?

Make that a fresh decision using the remaining stock, contribution and applicable price-reference requirements. Review the original end-date promise and explain any change honestly. Repeatedly renewing a supposedly final deadline undermines the message customers acted on.

Should people who already bought receive the last-chance email?

Decide that audience before scheduling. Where your reporting and sending platform support it, exclude customers who have already completed the intended campaign purchase, while keeping their necessary order messages. A later relevant accessory offer needs its own audience decision.