A customer enters a discount code at checkout, but PrestaShop refuses to apply it.
The coupon exists, it’s active, and it may even work perfectly in your own test account.
Before looking for a checkout bug, open the Cart Rule and check its conditions. PrestaShop validates more than the coupon code itself, and a small restriction can be enough to reject it.
A birthday coupon sounds simple: give the customer a discount and send a nice email.
But someone needs to check birthdays every day, generate the coupons, and make sure the emails go out on time. And what if the customer already has another discount? Or has never placed an order?
Your store gets orders, but the review section stays quiet.
That does not necessarily mean customers are unhappy. They received their order, tried the product and moved on. Returning to your store to write a review probably was not on their to-do list.
Switching to a new reviews module in PrestaShop? One thing you probably don’t want to lose is all the reviews your customers have already written.
Not every order in a PrestaShop store needs to earn loyalty points. If products have different profit margins, rewarding every purchase at the same rate can make some orders much less profitable. Before launching a loyalty program, it’s worth deciding which purchases should earn points, how much those points are worth, and when customers can use them.
Let’s say your store gives customers one point for every €10 spent. Each point is worth €0.20 when converted into a discount voucher.
That means a €100 order earns €2 in potential rewards.
Sounds reasonable, doesn’t it?
Want to give new customers a discount when they sign up for your PrestaShop store?
For example, you could offer €5 off their next purchase or a 10% welcome discount.
PrestaShop lets you create discount codes with Cart Rules, but it doesn’t automatically generate and email a personal coupon when someone registers.
If you have a PrestaShop store with hundreds of products, adding GPSR information manually can quickly become a headache.
Imagine you have 500 products from 15 manufacturers. You need to check manufacturer contact details, assign EU responsible persons where required, and add safety warnings in several languages.
Editing every product separately? That’s a lot of unnecessary work.
When a customer removes a product from their PrestaShop cart, it doesn’t always mean they’ve lost interest. Sometimes they want to buy some items now and keep others for another day. A Save for Later option lets them move products out of the cart without losing their selection.
I think this situation gets overlooked when we talk about abandoned carts.
To reward customers for referring friends in PrestaShop, a store needs to define three things: how to identify the person who made the referral, when the referral counts, and who receives the reward. This can be done with referral links or codes, rewards triggered by registration or orders, and incentives for the existing customer, the new customer, or both.
The mechanics sound simple. In practice, a referral program quickly raises a few questions that are easy to overlook.
You give a customer a 10% coupon after their first order.
They use it.
So you send another 10% coupon after the second order. They use that one too.
After a while, you have to ask an uncomfortable question: are you actually building retention, or just teaching customers to wait for a discount?