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.
You installed PrestaShop MCP Server, connected your account and copied the server URL.
But how do you know it actually works?
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.
I installed PrestaShop MCP Server on a development store because I wanted to test a simple read-only MCP tool.
The store was already connected to PrestaShop Account. The required modules were installed. The domain was available over HTTPS.
Then the setup stopped at Step 3 — Account & data sharing — with this message:
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.
You have installed the PrestaShop MCP Server module.
The required modules are enabled, your store is connected to PrestaShop Account, and the setup page asks you to connect an AI application.
This is where MCP can start to feel more complicated than it really is.
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.
Order not created after a successful payment? Here’s why this can happen with payment modules and how to recover the order without charging the customer twice.