Author: Sophie

We are experts in the eCommerce industry, specializing in high-quality plugin development. With years of experience, we deliver reliable and feature-rich modules for platforms such as Magento, PrestaShop, OpenCart, and Shopify. In addition to ready-made plugins, we also provide custom module development and tailored modification services to meet unique business needs. Our team stays ahead of industry trends, ensuring every solution we build enhances store performance, user experience, and overall functionality. With a strong customer-centric approach, we have become a trusted partner for businesses seeking powerful and scalable eCommerce plugin solutions.

OpenCart WhatsApp CRM and Order Notification Extension – Complete User Guide

1.0 Introduction

Order confirmation emails have a deliverability problem that most store owners do not think about until a customer complains. WhatsApp messages achieve open rates of 95 to 98 percent against email’s 20 to 25 percent, a difference that shows up directly in how many customers actually see the updates you send them. An OpenCart WhatsApp CRM Extension takes the manual work out of it, and alerts go to the customer at the right moment without your team needing to do anything.

The Knowband OpenCart WhatsApp CRM and Order Notification Extension ties your store to the WhatsApp Business API. New order confirmations and status change alerts are sent automatically. Your support team can chat with customers in real time from within the OpenCart admin. Promotional messages can also be sent to a segmented contact list at whatever time you schedule. A chat icon on your storefront puts your agents within reach of any visitor.

This guide documents every tab and field in the extension. Every setting is described exactly as it appears in the admin panel, whether you are doing a fresh setup or working through a specific configuration.

1.1 Who Is This OpenCart WhatsApp CRM Extension For

This extension suits:

Store owners who want WhatsApp order alerts to be sent automatically without needing a developer to set it up.
Support staff who need an OpenCart WhatsApp Live Chat Extension so they can reply to customer messages from the OpenCart backend.
Merchants who want an OpenCart WhatsApp Integration Extension that covers both automated notifications and outbound marketing campaigns in one place.
Agencies that are building OpenCart stores for clients who have asked for a WhatsApp Business API connected to their shop.

2.0 Installation Guide of the OpenCart WhatsApp Live Chat Extension

Step 1: Download the Extension

After purchasing, download the videomate.ocmod.zip file, which contains the complete video plugin for OpenCart.

1. Unzip the downloaded file; this will contain the videomate.ocmod.zip and necessary folders.
2. Go to the upload folder and locate the admin and catalog files.

3. Copy these files into the root directory of your OpenCart store

Step 2: Upload via Extension Installer

Go to Extensions > Extension Installer in your OpenCart admin panel.
Upload the videomate.ocmod.zip file.
Once installed, go to Extensions > Modifications, and click Refresh to apply changes.

Step 3: Assign User Permissions

Navigate to System > Users > User Groups, then edit your group and enable permissions for extension/module/videomate.

Step 4: Enable the Module

Navigate to Extensions > Extension Installer in your OpenCart admin dashboard.

2.3 Common Installation Issues

Upload fails: Your host is probably blocking the file size. Have them increase upload_max_filesize and post_max_size in the PHP settings to at least 32 MB.

Emails not going out: Go to System, then Settings, then the Mail tab. The extension uses the store’s default mail configuration unless you have set a different one at the form level.

Page looks wrong: Do a browser cache clear. Then reset the OpenCart theme cache using the blue cog icon on the Dashboard refresh panel.

3.0 Admin Panel Overview

The OpenCart WhatsApp CRM Extension adds its own section to the OpenCart admin sidebar after installation. Each tab in that section has a specific job:

Module/API Settings: This is where your WhatsApp Business API credentials go, along with the webhook configuration.
Templates: Where you write and submit templates to WhatsApp for review.
Order Settings: Decides which order-based WhatsApp alerts are active and when they are sent.
Order Status Trigger: Links each order status to the template that gets sent for it.
CRM: The live chat panel for two-way conversations with customers.
Contacts: Your full contact database, with import and export built in.
Lists: Groups of contacts that promotions get sent to.
Promotions: Builds and schedules outbound campaigns to your contact lists.
Agents: The support agents your visitors see in the storefront chat pop-up.
Chatbox Settings: Settings that control the floating WhatsApp icon on your storefront.
Message Logs: A timestamped record of all messages sent and received through the extension.

4.0 Module/API Settings of the OpenCart WhatsApp CRM Module

Nothing in the OpenCart WhatsApp Business API Extension works until this tab is filled in. Four credentials are required, and all four must be correct before the extension can send or receive anything.

4.1 WhatsApp API Settings

Enable Extension: You can easily enable/disable the plugin with this toggle. Turn it off, and the extension stops sending messages, and the storefront chatbox is removed.

Facebook App ID: Pull this from the Meta Developer Console. It identifies which Meta app the API request is coming from.

Facebook Access Token: This needs to be a permanent token, not the short-lived one shown in the API Setup tab. Head to Meta Business Settings, add a System User, give it full control over your app and WABA, then generate a token. The three permissions you need are whatsapp_business_messaging, whatsapp_business_management, and business_management. That token goes here.

WhatsApp Business Account ID (WABA ID): Your WABA ID lives in the Meta Developer Console, inside the WhatsApp section of your app. Copy it from there.

Phone Number: The registered WhatsApp Business number you want all messages to come from. Pick it from the dropdown.

Save the form once all four fields are filled. Any field left empty or entered incorrectly shows a validation error right away. An expired access token does the same.

4.2 Webhook Setup

Below the credential fields, the Configuration Information section shows a Webhook URL and a Verify Token that are specific to your store. These go into the Meta Developer Console.

In your Meta app, go to WhatsApp, then Configuration, and paste the two values into the webhook setup fields. After that, the extension picks up incoming messages and template status updates on its own.

The webhook is not strictly required to get started. If it is not set up yet, you can click Sync Templates inside the Message Templates tab at any time to manually pull the latest approval status from WhatsApp.

5.0 Order Settings

The Order Settings tab is where you control when the OpenCart WhatsApp Order Notification Extension sends messages and which templates it uses for them.

5.1 WhatsApp Order Settings

Enable New Order Message: When this is on, a WhatsApp message goes out to the customer every time a new order lands in your store.

Enable Order Status Message: When this is on, customers get a WhatsApp update each time their order status changes. Turning this on also adds a WhatsApp number field to the customer address form so shoppers can put in the number where they want to receive those updates.

5.2 New Order Message Templates

This section lists your store languages. For each one, pick the approved Utility template that sends when a new order is placed. The dropdown only pulls in Utility templates that WhatsApp has already approved.

If the dropdown has nothing in it, your templates are either sitting in the queue waiting on WhatsApp review, or they were categorised as Marketing instead of Utility. Create a Utility template in the Message Templates tab, wait for approval, then come back here and save your selection.

6.0 Message Templates

Templates used anywhere in the OpenCart WhatsApp CRM Extension are created and submitted here. WhatsApp has to approve a template before it can be assigned to any message flow. Both submission and status checking happen inside this tab.

6.1 Templates List

Every template tied to your WhatsApp Business Account shows up in this table. The columns cover Template ID, Name, Use Case, Category, Language, Status, and the date the template was created. Status can be Pending, Approved, or Rejected.

The Sync Templates button pulls the latest status data from WhatsApp whenever you need it. Search fields at the top let you filter by template name, category, language, or a date range.

6.2 Creating a New Template

Name: Use lowercase letters and underscores only. Spaces and special characters are not accepted.

Use Case: Pick the use case that fits: For Orders, For Marketing, or For Customers.

Category: Utility or Marketing. Any template assigned to order notifications has to be in the Utility category. WhatsApp reviews the body text and may move a template to Marketing if it reads like a promotion.

Language: Choose the language the template is written in. If your store serves customers in multiple languages, you will need a separate template for each one.

Header Type: Not required. You can leave it as No Header or add a Text, Image, Video, or Document header if the message needs one.

Message Body: The message itself. Bold, italic, and strikethrough options are in the editor toolbar. Use Insert Variable to drop in things like the customer’s name, their order ID, or the order total. The Body Preview below the editor shows you how the finished message reads as you build it.

Footer: An optional line of smaller text that sits below the main body.

Enable CTA Button: Switch this on to attach a CTA button to the message. You will need to fill in the Button Text and the URL it points to.

Hit Save when the template is ready. WhatsApp gets it for review right away. Straightforward templates are usually clear in a few minutes. More complex ones can take a few hours. Once it is approved, it shows up in Order Settings, Order Status Templates, and the CRM template list.

7.0 Order Status Triggers

Each order status in OpenCart can be paired with a Utility template in this tab. When an order hits a status that has a template assigned, the extension sends that message to the customer as an automated WhatsApp update.

Every status your store uses is listed in the table: Awaiting check payment, Payment accepted, Processing in progress, Shipped, Delivered, Canceled, Refunded, and the rest. Each row shows whether notifications are on or off and which template is currently mapped to that status.

Hit Edit on any row to change it. Toggle Enable WhatsApp Notification on, pick a Utility template for each store language from the dropdown, and save. The row reflects the change straight away.

8.0 CRM: Live Two-Way Chat in Best WhatsApp CRM Extension

The CRM tab is the live chat section of this OpenCart WhatsApp Live Chat Extension. Your contact threads sit in a sidebar on the left. Click on any one of them to bring up the full conversation on the right.

Two tabs are at the bottom of the chat window: Message and Template. The message is for free-text replies, though this only works during the 24-hour window that opens when a customer sends you something first. After that window closes, swap to the Template tab. Approved Marketing templates can go out from there at any time.

Automated order alerts sent by the extension also show up inside the relevant contact thread. That way, your support team always has the full picture of what the customer received before they start a reply.

9.0 Promotions

The Promotions tab is for outbound WhatsApp campaigns. You pick the list of contacts, choose the template, set when it goes out, and the extension takes it from there.

9.1 Creating a Promotion

Name: An internal name so you can tell this campaign apart from others. It is not included in the message the customer receives.

Contact List: Choose which WhatsApp List this campaign targets. Every contact on that list will get the message.

Template: Pick an approved Marketing template from the dropdown. Marketing category templates are the only ones that appear here.

Schedule at: The date and time you want the campaign to go out. It has to be in the future. If you leave this blank, the campaign runs on the next CRON trigger instead.

Save it. The campaign will sit in the list with a scheduled status. The CRON command at the top of the Promotions page needs to be added to your server if you want campaigns to send automatically. It checks for pending campaigns every minute.

After a campaign runs, the Sent and Failed numbers fill in. The WhatsApp Business API bills you per message, so it is worth sending to a small group of 10 to 20 contacts first, just to see what the actual cost looks like before you go to the full list.

10.0 WhatsApp Contacts

Every phone number the extension can message is stored here. A contact needs a phone number and a name at a minimum. Linking to an OpenCart customer account is optional.

10.1 Adding a Contact Manually

Phone Number: Start with the country code, no leading zero, no spaces or dashes. An Indian number, for example, would be entered as 919310436362.

Name: Whatever name you want displayed for this contact in the extension.

Click Save when done.

10.2 Importing Contacts in Bulk

Click Download Template to get the CSV file in the right format. Add your contact data to it, come back to WhatsApp Contacts, and click Import Contacts to upload the file. Numbers that are already in the extension get their records updated. Numbers that are not in there yet get added as new contacts. Export to Excel and Export to CSV are both available if you need to pull the whole contact list out.

11.0 WhatsApp Lists

A WhatsApp List is just a named group of contacts. Promotions target one list at a time. To create one, click Add new list, type a name, and save it. If you mark a list as Default, new contacts get added to it automatically.

You assign contacts to lists from the WhatsApp Contacts tab. One contact can be in more than one list at the same time.

12.0 Chatbox Settings

This tab is for the floating WhatsApp icon on your storefront. When a visitor clicks it, a pop-up appears listing the agents you have set up. They tap Chat next to whoever they want to speak with, and it opens a WhatsApp conversation on their phone.

Enable Chatbox: Switch this on to show the icon on the storefront, or off to hide it.

Icon Position: Where the icon sits on the screen. Options include Bottom Right and Bottom Left.

Theme Color: The main color used for the icon background and the pop-up header. It defaults to WhatsApp green, which is #25D366.

Header Title: The text shown at the top of the chat pop-up. The placeholder example is “Chat with us”; enter whatever heading you want your visitors to see when the popup opens.

Sub Title: A short line shown below the header title. Use this to set response time expectations or any brief supporting text.

Greeting Message: The opening message displayed to visitors inside the chat pop-up before they select an agent. Accepts plain text. A WhatsApp emoji picker and formatting options are available in the bottom right of the text area.

Online Text: The label shown on agent cards when the agent is available. Defaults to “Online.”

Offline Text: The label shown on agent cards when the agent is not available. Defaults to “Offline.”

Hit Save Settings once you have made your changes.

13.0 WhatsApp Agents

Agents are the people your storefront visitors see in the chat pop-up. Each agent card has a name, a department or role, and a Chat button. When a visitor taps that button, it opens a WhatsApp conversation with that agent’s number on their device.

Active: Controls whether this agent is visible in the storefront popup.

Agent Name: The name shown on the agent card. Capped at 50 characters.

Contact Number: The agent’s WhatsApp number, country code included (for example, +919876543210). If you use the same number as the one in the API Settings, conversations from this agent also appear inside the CRM tab.

Department: The team name or role shown under the agent’s name. Up to 50 characters, and it can be set differently per language.

Display Order: A number that controls where this agent appears in the pop-up. The lower the number, the higher up the agent shows.

Avatar Type: Pick a Predefined Avatar from the available options, or upload an image of your own.

14.0 Message Logs

The Message Logs tab keeps a record of every message that has passed through the OpenCart WhatsApp Messaging Extension, both sent and received. Each row tells you the Direction, the phone number it involved, the template used if any, a preview of the message text, the WhatsApp Message ID, the delivery status, and the timestamp.

Order alerts, CRM replies, and campaign messages all end up in this list. A success status means the WhatsApp API received and accepted the message. The date range, phone number, and template filters make it easy to find a specific message. When something is not delivering the way it should, this tab is the right place to start looking.

15.0 Frequently Asked Questions

Q: What is the OpenCart WhatsApp CRM Extension, and what does it do?

The Knowband OpenCart WhatsApp CRM and Order Notification Extension connects your OpenCart store to the WhatsApp Business API. Order confirmations and status change alerts go to customers on WhatsApp automatically. Your team handles live customer conversations from inside the OpenCart admin through the CRM tab. You can run scheduled WhatsApp campaigns to contact lists through the Promotions tab. A storefront chatbox lets visitors tap through to your support agents on WhatsApp directly.

Q: Does the OpenCart WhatsApp Messaging Extension require a WhatsApp Business Account?

Yes, it does. The OpenCart WhatsApp CRM Extension needs a WhatsApp Business Account, a phone number registered as a WhatsApp Business number, and a Meta Developer App that has WhatsApp Business API access set up. All three are needed before the API Settings tab can be completed and before the extension can send anything.

Q: How does the OpenCart WhatsApp Order Notification Extension send alerts when a new order is placed?

When Enable New Order Message is switched on in Order Settings, the OpenCart WhatsApp Order Status Extension sends an approved Utility template to the customer each time an order goes through. For status updates, turn on Enable Order Status Message as well. That puts a WhatsApp number field on the customer address form. Once a customer fills it in and their order moves to a status that has a template mapped in Order Status Templates, the message goes out to that number straight away.

Q: Why are no templates showing in the Order Settings dropdown of the OpenCart WhatsApp CRM Extension?

Order Settings only lists Utility templates that have been approved by WhatsApp. An empty dropdown usually means templates are still in the review queue or sitting in the Marketing category by mistake. Head to Message Templates, build a Utility template, wait for the approval to land, then go back to Order Settings. The Sync Templates button is there if you want to pull the latest approval status without waiting for the webhook.

Q: How does the live chat work inside the OpenCart WhatsApp Live Chat Extension?

The CRM tab in the OpenCart WhatsApp Messaging Extension shows all contact threads on the left side. Click a contact to open the conversation. Use the Message tab to type a reply while the 24-hour window from the customer’s last message is still open. Once that closes, the Template tab is the way to reach them; any approved Marketing template can be sent from there, regardless of when the customer last wrote. Automated order alerts from the extension appear in the thread too, so your team always has context.

Q: Can I run WhatsApp marketing promotions through the OpenCart WhatsApp CRM Extension?

Yes, through the Promotions tab. Go there, click Add new promotion, give it a name, pick a Target List, choose a Marketing template, and set a time in the future for it to go out. The CRON command on the Promotions page needs to be on your server for campaigns to send automatically; it checks every minute for anything due. Before sending to your whole list, send it at a small group of 10 to 20 contacts first to see what the API costs look like.

Q: How does the OpenCart WhatsApp Business API Extension connect to WhatsApp?

The OpenCart WhatsApp Order Status Extension also available on Opencart Marketplace with Price $49.99, connects through four fields in the Module/API Settings tab: your Facebook App ID, a permanent Access Token, your WhatsApp Business Account ID (WABA ID), and your registered phone number. On top of that, you paste the Webhook URL and Verify Token shown in the Configuration Information panel into your Meta Developer Console. With those two steps done, the OpenCart WhatsApp Business API Extension handles message sending, template approval tracking, and incoming messages without any further manual input.

Q: Can I bring existing contacts into the OpenCart WhatsApp Order Status Extension from a spreadsheet?

Yes. Open the WhatsApp Contacts tab and click Download Template to get the CSV in the right layout. Put your contact data into it, then upload it using Import Contacts. If a phone number is already in the extension, that contact’s record gets updated. Anything new gets added. Once the contacts are in, you can assign them to WhatsApp Lists and target them in your next promotion.

Q: A template was rejected inside the OpenCart WhatsApp CRM Extension. What now?

Go to Message Templates and look at what the rejected template says. WhatsApp will reject templates that put sales or promotional language inside a Utility template, contain anything inaccurate, or go against its commerce policies. Delete the rejected one, fix whatever the issue was in the body text, and submit a fresh template. If the tone was the problem, write the body more like a factual update and less like a sales message.

Q: Which versions of OpenCart work with the Knowband WhatsApp CRM Extension?

The Knowband OpenCart WhatsApp CRM Extension runs on OpenCart 3.x. If you need compatibility details for versions released after this guide was written, the extension product page on the Knowband website will have the most current information. You can also contact the Knowband support team directly.

16.0 Conclusion

The Knowband OpenCart WhatsApp CRM Extension, also known as the OpenCart WhatsApp CRM and Order Notification Extension, is a full OpenCart WhatsApp Integration Extension. Order alerts go out on their own. Live support runs through the CRM tab. Campaigns reach targeted contact lists on a schedule you define.

The only thing that happens outside the extension is pulling your API credentials from the Meta Developer Console. After that, templates, order mappings, contact lists, agent profiles, and promotions are all handled from inside OpenCart.

For help getting set up or questions about any feature, the Knowband support team is at support@knowband.com. There are also documentation pages and setup videos on the Knowband website.

The Benefits of WhatsApp Business Integration for PrestaShop Ecommerce Stores

Email built ecommerce communication, but WhatsApp is rapidly reshaping it. With message open rates reaching 95-98% compared to email’s 20-25%, the channel difference is not marginal; it is structural. For PrestaShop store owners still relying entirely on email for order updates, customer support, and promotional campaigns, that gap is quietly costing real revenue every month. Here is what adding a good WhatsApp CRM solution for PrestaShop to your store, like Knowband’s PrestaShop WhatsApp CRM and Order Notification Module, actually changes, and why it matters for each part of your operation.

1. Automated Order Confirmations That Customers Actually See

Order confirmation emails get buried. Spam filters catch them. Customers check their inbox hours later and still are not sure if the order went through, so they open a support ticket or they call.

When WhatsApp order notifications are shared the moment a purchase is placed, that cycle stops. The customer gets a message on the app they already check dozens of times a day, within seconds of completing checkout. For stores processing a meaningful order volume daily, eliminating “did my order go through” tickets alone is worth the integration.

The Knowband PrestaShop WhatsApp CRM Module handles this through approved Utility templates mapped to specific order events. No manual trigger is needed. The message goes out, the customer sees it, and the conversation is already logged inside your admin.

2. Real-Time Status Updates That Reduce Inbound Support Volume

Order status changes are the single most common reason customers contact eCommerce support teams. Shipped? Delivered? Delayed? Without a proactive notification, they ask.

Every order status in PrestaShop, from Payment Accepted to Shipped to Delivered to Cancelled, can be mapped to a specific WhatsApp message template. When the status changes in your back office, the alert reaches the customer automatically. They are not hunting for a tracking link buried in their inbox. They receive a message the same way a friend would send one.

This is post-purchase communication done correctly: proactive, channel-native, and requiring nothing from your support team to trigger.

3. A Live Chat Panel Inside PrestaShop, Not on Someone’s Phone

Most PrestaShop stores that handle WhatsApp customer messages do so poorly. One team member manages conversations from a personal phone. Context disappears when someone else needs to step in. Nothing is logged against the customer record.

The PrestaShop WhatsApp Business API integration moves all of that into the admin via a dedicated CRM tab. Every contact thread is visible to your team. Replies go out from the admin panel. Automated notifications appear in the same thread, so agents can see exactly what a customer received before responding.

When the 24-hour free-text window closes, agents send an approved WhatsApp message template directly from the same interface. No tool-switching. No lost context.

4. WhatsApp Marketing Campaigns Built Into Your Store Admin

Promotional campaigns typically require a separate platform, a separate contact list, and manual coordination between your store data and your messaging tool. That friction reduces how often teams actually run them.

The module’s Promotions tab removes that gap. Build a contact list from your customer database, select an approved marketing template, set a schedule, and the CRON job handles delivery. Contact list segmentation means you target the right group, not every customer at once.

WhatsApp campaign conversion rates in eCommerce markets consistently run well above email equivalents. The platform’s built-in read behavior does most of the work; the PrestaShop WhatsApp CRM Module removes the operational overhead.

5. A Storefront Chat Widget That Connects Visitors to Real Agents

Pre-purchase questions kill conversions. A visitor who cannot get a quick answer to a shipping query or a product question will leave. A generic contact form does not solve this; response times are too slow, and the channel is the wrong one.

The Knowband PrestaShop WhatsApp live chat addon places a configurable floating icon on your storefront. Visitors click it, see available support agents by name and department, and tap to open a WhatsApp conversation directly on their phone. The exchange happens in real time, without any login or form.

Agent display order, avatars, department labels, and icon styling are all configurable from inside the PrestaShop backend. The widget works on both desktop and mobile, which matters given how much eCommerce traffic arrives from phones.

6. Full Message Tracking for Improved Customer Support Management

When a customer claims they never received a shipping notification or a conversation needs to be reviewed, having a searchable record matters. Manual WhatsApp exchanges on personal phones leave nothing you can retrieve.

Every message the PrestaShop WhatsApp CRM Module sends or receives is recorded, including direction, phone number, template name, delivery status, and timestamp. Filtering by date, number, or template makes it fast to pull a specific record.

For stores managing disputes or customer escalations, this log is a practical resource, not just a convenience.

7. Centralized Contact Management With Bulk Import

Running WhatsApp campaigns requires a contact database. Building one manually is slow. The PrestaShop WhatsApp CRM Module’s Contacts tab supports CSV bulk import, so existing customer lists come in without manual data entry.

Each contact links to a PrestaShop customer account and can be assigned to one or more named WhatsApp Lists. Campaign targeting works through those lists, one promotion, one list, no overlap.

Excel and CSV export options are included, so the contact database can also feed into other tools when needed.

Why This Channel Gap Will Only Widen

WhatsApp has crossed 3 billion monthly active users, and 88% of messages are read within five minutes of delivery. Email cannot compete on speed or attention at that scale. For any PrestaShop store still routing customer communication through email alone, the distance between where customers are and where the store’s infrastructure sits grows every quarter.

The PrestaShop WhatsApp Business API integration module, also known as the PrestaShop WhatsApp CRM and Order Notification Module by Knowband, covers the full range of communication touchpoints, automated confirmations, status updates, live support, promotional campaigns, and storefront chat, from a single installation. The Knowband PrestaShop WhatsApp CRM Module requires no developer for setup; the only work that happens outside PrestaShop is generating your Meta API credentials.

If you are already handling customer WhatsApp messages manually, the PrestaShop WhatsApp live chat addon can be the right choice for you.

PrestaShop WhatsApp CRM Module – Complete User Guide

1.0 Introduction

Most customers already have WhatsApp on their phones. They check it more often than email, and they respond faster there, too. For a PrestaShop store, that creates a real opportunity to reach customers where they actually pay attention.

The Knowband PrestaShop WhatsApp CRM Module ties your store directly to the WhatsApp Business API. Order confirmations go out automatically when a purchase is placed. Status change alerts fire when an order ships or is delivered. Your support team chats with customers in real time from the PrestaShop admin. And when you want to run a promotional campaign, you can send an approved marketing template to a segmented contact list on a schedule you control.

This guide walks through every section of the PrestaShop WhatsApp Integration Module. Whether you are setting it up for the first time or trying to configure a specific feature, every tab and field is documented here, from what is visible in the admin panel.

Compatible with PrestaShop 1.7.x through 9.x.

1.1 Who Is This Module For

This module works well for:

Store owners who want automated WhatsApp order notifications set up without relying on a developer.
Support staff who need to chat with customers from inside the PrestaShop backend.
Marketing teams that send WhatsApp promotions to specific customer groups.
Agencies handling PrestaShop builds for clients who need WhatsApp Business API integration.

2.0 Installation Guide of the PrestaShop WhatsApp CRM Module

2.1 System Requirements

PrestaShop 1.7.x, 8.x, or 9.x
A WhatsApp Business Account that is active
A phone number registered as a WhatsApp Business number
A Meta Developer App with WhatsApp Business API access configured

2.2 Installing the PrestaShop WhatsApp Module

Open your PrestaShop admin panel. Head to Modules, then Module Manager, and hit Upload a Module at the top right.
Pick the ZIP file you got from Knowband and click Open. PrestaShop takes it from there, uploads the file, and extracts everything automatically.
Once the upload is done, hit Install when it appears. After that finishes, click Configure to get into the module settings.
If the module does not show up on its own, type Knowband WhatsApp CRM into the Module Manager search bar and hit Configure from there.

2.3 Common Installation Issues

Upload fails: Your server’s PHP upload limit is probably too low. Ask your host to bump upload_max_filesize and post_max_size to at least 32 MB.

Module not visible after install: Clear the PrestaShop cache under Advanced Parameters, then Performance. Run the Module Manager search again.

Configuration page looks broken: Clear your browser cache and the theme cache under Design, Theme and Logo, then Advanced Settings.

3.0 Admin Panel Overview of the PrestaShop WhatsApp CRM Module

Once the PrestaShop WhatsApp Integration Module is installed, a dedicated menu section appears in your PrestaShop admin sidebar. Here is what each tab does:

Module/API Settings: Where you enter your WhatsApp Business API credentials.
Order Settings: Controls which WhatsApp order notifications fire and when.
Message Templates: Where you build and submit templates for WhatsApp approval.
Order Status Templates: Maps each order status to the template that gets sent.
CRM: The live chat panel for two-way messaging with customers.
Promotions: Runs scheduled campaigns to contact lists.
WhatsApp Lists: Named groups of contacts used as campaign targets.
WhatsApp Contacts: Full contact database with import and export options.
Chatbox Settings: Controls the floating WhatsApp icon shown on your storefront.
WhatsApp Agents: The support agents shown inside the storefront chat pop-up.
Message Logs: A record of every message sent and received through the PrestaShop WhatsApp Module.

4.0 Module/API Settings

Start here. Before anything else in the PrestaShop WhatsApp CRM Module works, you need to connect it to the WhatsApp Business API. There are four fields, and all four are required.

4.1 WhatsApp API Settings

Enable Module: The on/off switch for the whole module. Switch it off, and no messages go out; the chatbox disappears from the storefront.

Facebook App ID: Copy this from your Meta Developer Console. It tells the API which app is making the connection.

Facebook Access Token: This has to be a permanent token, not the temporary one shown during API Setup. To get a permanent token, go to Meta Business Settings, create a System User, assign your app and WABA with full control, and generate a token using these permissions: whatsapp_business_messaging, whatsapp_business_management, and business_management. Paste that token here.

WhatsApp Business Account ID (WABA ID): Found in the Meta Developer Console under your app’s WhatsApp configuration. This is the account ID for your WhatsApp Business Account.

Phone Number: Pick your registered WhatsApp Business number from the dropdown. Every automated and manual message goes out from this number.

Fill all four fields and click Save. Wrong or missing values show a validation error right away. An expired or invalid access token also triggers an error on save.

4.2 Webhook Setup

Scroll below the API form, and you will see the Configuration Information panel. It shows two things: a Webhook URL and a Verify Token, both specific to your store.

Take these over to the Meta Developer Console. Open your app, go to WhatsApp, then Configuration, and paste them into the webhook fields there. Once that is done, the module can receive inbound messages and pick up template approval status changes without you manually refreshing anything.

If you have not set up the webhook yet, you can still check template statuses by going to Message Templates and clicking Sync Templates. That pulls the latest approval data directly from WhatsApp.

5.0 Order Settings

This tab is where you decide when the PrestaShop WhatsApp CRM Module sends automated messages during the order process.

5.1 WhatsApp Order Settings

Enable New Order Message: Turn this on, and the PrestaShop WhatsApp Messenger sends a WhatsApp message to the customer every time a new order is placed on your store.

Enable Order Status Message: Turn this on, and customers get a WhatsApp alert each time their order status changes. A WhatsApp number field also appears on the customer address form so people can add the number where they want updates delivered.

5.2 New Order Message Templates

For each language your store runs, pick the approved Utility template you want to send when an order comes in. The dropdown only shows templates that are categorised as Utility and have been approved by WhatsApp.

Nothing in the dropdown? Either your templates are still waiting on WhatsApp review, or they are in the Marketing category instead of Utility. Build a Utility template in the Message Templates tab, wait for the approval, then come back here. Click Save once you have made your selections.

6.0 Message Templates

This is where WhatsApp message templates are built and submitted. Every template needs WhatsApp approval before it can be used anywhere in the module. The Knowband PrestaShop WhatsApp CRM Module handles the whole process from submission to tracking inside this tab.

6.1 Templates List

The table shows all templates connected to your WhatsApp Business Account. Each row has: Template ID, Name, Use Case, Category, Language, Status, and the date it was created. A template can be Pending, Approved, or Rejected.

Hit Sync Templates any time you want to refresh the approval status straight from WhatsApp. The search fields let you narrow down by name, category, language, or date range.

6.2 Creating a New Template

Name: Lowercase, underscores only. No spaces, no special characters.

Use of the Template: Choose For Orders, For Marketing, or For Customers, depending on where this template will be used.

Category: Choose MARKETING or UTILITY. Templates tied to order notifications must be Utility. If the body reads like a promo, WhatsApp may move it to Marketing on its own.

Language Code: Pick the language this template is written in. If your store has multiple languages, build one template per language.

Header Type: Optional field. Leave it as No Header or pick Text, Image, Video, or Document if you want something at the top.

Body: The main text of the message. Bold, italic, and strikethrough formatting is available through the B, I, and strikethrough buttons. Click Insert Variable to pull in things like the customer name, order ID, or order total. The Body Preview below the editor shows how the final message will look.

Footer: Optional. Text that appears below the body is rendered smaller.

Enable Button: Turn this on to add a button to the message. Fill in the Button Text and the Button URL.

Click Save when you are done. WhatsApp receives the template for review. Approvals usually come through within a few minutes, though some templates take a few hours. Once approved, the template is available in Order Settings, Order Status Templates, and the CRM template picker.

7.0 Order Status Templates

Every order status in PrestaShop can be mapped to a specific Utility template here. When an order reaches a status that has a template assigned, the PrestaShop WhatsApp Messenger sends that template to the customer as a WhatsApp order notification.

The full list of order statuses appears in the table: Awaiting check payment, Payment accepted, Processing in progress, Shipped, Delivered, Canceled, Refunded, and the rest. Each row shows whether notifications are Enabled or Disabled, and which template is currently assigned.

Click Edit on any row. Flip the Enable WhatsApp Notification toggle to Enabled, pick an approved Utility template from the dropdown for each store language, and save. The row updates to reflect the change right away.

8.0 CRM: Live Two-Way Chat

The CRM tab is the messaging center for this PrestaShop WhatsApp chat addon. All your contacts appear in a sidebar on the left. Clicking one opens the full conversation on the right.

At the bottom of the conversation, there are two tabs: Message and Template. The message is for free-text replies, but that only works inside the 24-hour window that opens when a customer sends you something first. Once that window closes, use the Template tab to send an approved marketing template that works at any time.

Every automated order notification the module sends also shows up in the CRM thread. Your support team can see exactly what a customer received and when, which makes it easier to respond in context.

9.0 Promotions

The Promotions tab is where you put together WhatsApp marketing campaigns. Pick a contact list, pick a template, set a time, and the module takes care of sending it.

9.1 Creating a Promotion

Promotion Name: An internal name you will recognise. It does not appear in the message.

Target List: Select one of your WhatsApp Lists from the dropdown. Every contact on that list gets the message.

WhatsApp Template: Select a Marketing category template. Only approved Marketing templates show up here.

Schedule For: Pick a date and time in the future. Past timestamps are not accepted. Leave the field empty if you want it to send on the next CRON run.

Click Save. The campaign shows as scheduled in the list. For it to send automatically, the CRON command shown at the top of the Promotions page needs to be added to your server. It runs every minute and picks up any campaigns whose scheduled time has passed.

Once a campaign finishes running, the Sent and Failed counts fill in. The WhatsApp Business API bills per message, so it is worth running a small test batch of 10 to 20 contacts before sending to your full list.

10.0 WhatsApp Lists

Lists are named groups of contacts. A promotion targets one list at a time. Click Add new list, give it a name, and save it. That is the whole process. You can mark one list as the Default if you want new contacts added to it automatically.

Contacts get assigned to lists from the WhatsApp Contacts tab. One contact can be on as many lists as you need.

11.0 WhatsApp Contacts

Every phone number you want to message through the module lives here. Each contact has a number, a name, and the option to link to a PrestaShop customer account.

11.1 Adding a Contact Manually

Phone Number: Country code first, no leading zero, no spaces, no dashes or plus signs (for example, 91xxxxxxxxxx for an Indian number).

Name: The display name for this contact.

Select PrestaShop Customer: Search for an existing customer account to link this contact to. Leave it blank if this is a standalone contact with no store account.

WhatsApp Lists: Pick one or more lists to add this contact to. Multi-select works here.

Click Save to add the contact.

11.2 Importing Contacts in Bulk

Click Download Template to grab the CSV format. Add your contacts, then come back and click Import Contacts to upload the file. If a number already exists in the module, that record gets updated. New numbers get added fresh. Export to Excel and Export to CSV are both available if you need to pull the full contact list.

12.0 Chatbox Settings

This tab controls the WhatsApp icon that floats on your storefront. Visitors click it, see a pop-up with your available agents, and tap Chat next to whoever they want to reach. That opens a WhatsApp conversation on their phone directly.

Show Chat Icon on Frontend: Turns the icon on or off.

Icon Position: Bottom Right, Bottom Left, or other available positions.

Distance from Bottom / Right / Left (px): How far the icon sits from each edge. Default is 20px on all sides.

Z-Index: Layer order relative to other elements on the page. Default is 9999.

Predefined Icon: Choose from available icon styles, including Animated Style.

Icon Size: Diameter in pixels. Accepted range is 16 to 128. The default is 50.

Primary Color of Icon and Chatbox: The main background color. Default is WhatsApp green, #25D366.

Hover Color of Icon: The color that appears when a visitor hovers over the icon. Default is #128C7E.

Background Color of Chatbox: The background of the chat popup. Default is #FFFFFF.

Text Color of Chatbox: Text color inside the pop-up. Default is #000000.

Border Color of Chatbox: The border around the pop-up. Default is #E0E0E0.

Border Width of Chatbox: How thick the border is in pixels. Default is 1.

Pulse Animation: When enabled, a pulsing ring plays around the icon.

Bounce Effect: When enabled, the icon bounces when a visitor hovers over it.

Click Save Settings when done.

13.0 WhatsApp Agents

Agents are the team members displayed inside the storefront popup. Each one shows a name, department, and a Chat button that visitors tap to open a WhatsApp conversation with that person directly.

Active: Show or hide this agent in the pop-up.

Agent Name: The name displayed in the pop-up, up to 50 characters.

Contact Number: The agent’s WhatsApp number with country code (for example, +91xxxxxxxxxx). If you use the same number as the one in the API settings, conversations also appear in the CRM tab.

Department: The team or role shown under the agent’s name. Up to 50 characters, and this can be different per language.

Display Order: The position of this agent in the pop-up relative to others. Lower numbers come first.

Avatar Type: Use a Predefined Avatar or upload a custom image.

14.0 Message Logs

Every message the PrestaShop WhatsApp CRM Module sends or receives is recorded here. Each row shows the Direction (Outbound or Inbound), the phone number, the template name if one was used, a preview of the message, the WhatsApp Message ID, the delivery status, and the date and time.

Order notifications, CRM messages, and campaign deliveries all show up in this list. A success status means the WhatsApp API accepted the message. Use the date, phone number, and template filters to narrow down what you are looking for. This is the first place to check when a message did not go through as expected.

15.0 Frequently Asked Questions

Q: What does the PrestaShop WhatsApp CRM Module do?

The Knowband PrestaShop WhatsApp CRM Module connects your PrestaShop store through a full PrestaShop WhatsApp Business API integration. New order messages and order status change notifications go out automatically via the WhatsApp Business API. Your team can handle two-way WhatsApp messaging with customers in real time from inside the admin. Marketing promotions can be sent to contact lists on a schedule. A WhatsApp chatbox widget on the storefront lets customers reach your agents directly on WhatsApp.

Q: Is a WhatsApp Business Account required for the PrestaShop WhatsApp live chat addon?

Yes, it is. PrestaShop WhatsApp Manager needs a WhatsApp Business Account, a registered WhatsApp Business phone number, and a Meta Developer App with API access. Without those three things, the API fields in Module/API Settings stay empty, the WhatsApp message templates cannot be submitted for approval, and the module cannot send anything.

Q: Why are no templates appearing in the Order Settings dropdown?

The dropdown in Order Settings only shows Utility WhatsApp message templates that WhatsApp has approved. If nothing is listed, either the templates are still pending review or they ended up in the Marketing category. Go to Message Templates, create a Utility template, wait for the approval to come through, then return to Order Settings. You can also click Sync Templates to pull the latest status without waiting for the webhook.

Q: How do WhatsApp order notifications PrestaShop stores send when an order status changes?

Once Enable Order Status Message is turned on, a WhatsApp number field appears on the customer address form. When a customer fills that in, and their order triggers an order status change notification mapped in Order Status Templates, the module sends the assigned WhatsApp order notifications to their number. You can assign a different template to each status.

Q: What is the difference between a Utility template and a Marketing template?

Utility templates are for messages tied directly to something the customer did, such as placing an order or having an order shipped. Marketing templates are for outbound promotional content sent to contact lists. Order Settings and Order Status Templates use Utility templates only. The Promotions tab and the CRM Template picker use Marketing templates only.

Q: How do I run a PrestaShop WhatsApp marketing Module promotion to a contact list?

Open the Promotions tab and click Add new promotion. Give it a name, pick a Target List, choose a Marketing template, and set a future date and time. For the PrestaShop WhatsApp marketing Module campaign to send automatically, paste the CRON command from the Promotions page into your server to enable the CRON job for WhatsApp campaigns. The CRON runs every minute and sends any campaigns due at that time. Before you run a big campaign, test it on a list of 10 to 20 contacts to get a sense of API costs.

Q: Can I import my existing contacts using the PrestaShop WhatsApp live chat addon?

Yes. Click Download Template in the WhatsApp Contacts tab to get the right CSV layout. Fill in your contact data, then upload it via Import Contacts. Numbers that already exist get updated. New numbers are added to the contact list. Once imported, contacts can be assigned to any WhatsApp List for WhatsApp contact list segmentation and use in promotions.

Q: How does the CRM live chat work in this PrestaShop WhatsApp live chat addon?

The CRM tab shows all contact threads on the left. Click any contact to open the full chat history. The Message tab lets you type a free reply as long as the customer messaged you within the last 24 hours, supporting real two-way WhatsApp messaging between your team and the customer. After that window closes, use the Template tab to send an approved Marketing template. All automated order notifications appear in the same thread, so your team has the full picture in one place.

Q: Which versions of PrestaShop does this PrestaShop WhatsApp Module support?

The Knowband PrestaShop WhatsApp CRM Module runs on PrestaShop 1.7.x, 8.x, and 9.x. Setting up PrestaShop WhatsApp Business API integration requires a Meta Developer App; full setup instructions are in the Meta Developer Console WhatsApp configuration section of this guide. Check the module product page on the Knowband website for any version-specific notes or updates that may have been released since this guide was written.

16.0 Conclusion

The Knowband PrestaShop WhatsApp CRM Module brings WhatsApp-based customer communication into your PrestaShop admin. Order alerts go out without manual effort. Your team handles support from the CRM tab without switching tools. Promotions reach customers on a list you control, at a time you set.

The only setup work that happens outside the PrestaShop WhatsApp Manager is generating your API credentials in the Meta Developer Console. Everything else, templates, order mappings, contact lists, agents, and campaigns, is configured from inside PrestaShop.

For any help with setup or questions about specific features, reach out to the Knowband support team at support@knowband.com. Product documentation and setup videos are also available on the Knowband website.

A Smarter Way to Migrate Your PrestaShop Store: Introducing the PrestaShop Catalog Import Export Module

If you manage a PrestaShop store with a large catalog, you already know this routine. Export a CSV, open it in a spreadsheet, make changes, re-upload it, redo the column mapping, and hope nothing breaks this time. Then do the whole thing again next week, from scratch, because none of that configuration was saved anywhere. The PrestaShop Catalog Import Export Module by Knowband is built specifically to fix this.

Merchants looking for a capable PrestaShop product import and export solution quickly find that the native importer covers the basics only. Combinations fail. Multi-language fields go missing. There is no scheduling and no way to automate any of it. The process consumes hours that keep adding up across every update cycle.

This post walks through where that friction actually comes from, what a proper catalog transfer workflow looks like, and how stores ranging from 200 to 50,000 products are handling it now.

Why PrestaShop’s Default Importer Is Not Good Enough for Real Catalog Work

The built-in CSV importer in PrestaShop handles a few sets of scenarios well. Uploading a basic list of new products without combinations, in one language, and for one-time imports.

The moment the catalog gets more complex, the gaps show up fast. Product combinations remain one of the biggest challenges during catalog imports, with merchants frequently reporting issues such as failed imports and incorrectly mapped attribute data in community discussions. Additionally, multilingual catalogs introduce another layer of complexity. Although PrestaShop’s default importer supports multilingual fields, managing translations through CSV files can become cumbersome as the number of languages and products grows. Merchants often need to invest extra time in preparing, validating, and updating language-specific data to ensure consistency across their catalog.

Beyond combinations and languages, the structural problem is repeatability. Every import starts over. There is no option to save a configuration, no option to automatically pull a file from an FTP location, and no transfer log to diagnose what went wrong when a batch fails silently.

What You Actually Need to Migrate a PrestaShop Store Successfully

Catalog migration between PrestaShop stores means moving from PrestaShop 1.7 to 8.x or 9.x, or splitting one store into two regional stores, which is the scenario where the native importer breaks down most completely.

Most merchants think migration means moving products. In reality, it means moving everything your store depends on to function correctly. Miss one piece and you are looking at broken pages, wrong prices, or customers seeing products in the wrong language.

Here is what a complete migration actually covers:

Your product data, including names, descriptions, SKUs, prices, tax rules, and visibility settings. Your category structure with parent-child relationships, friendly URLs, and category images intact. Product combinations and variants with size, color, material, combination references, price impact, and default combination settings all carried over correctly. Product images, including cover images, gallery images, and variant-specific images in the right order. Manufacturers, suppliers, features, and attribute groups with all their values and assignments. Stock quantities, availability settings, and out-of-stock behavior. SEO metadata, including meta titles, meta descriptions, and friendly URLs for every product and category, because losing these means losing months of search ranking work. And for multilingual stores, every translation needs to stay correctly linked to its language.

The PrestaShop Catalog Import Export Module by Knowband handles this as a seamless transfer workflow. Export from the source store with combinations enabled, import into the destination store, and the module creates missing attribute groups and values automatically rather than throwing an error. Every language exports to the same file. No separate pass per locale, no manual field matching across files.

How Does the PrestaShop Import Export Module Profile System Work

The single feature that separates this from a basic transfer tool is the profile system. Every import or export configuration, data type, file format, language selection, column set, and FTP destination is saved as a named profile. Create it once. Run it whenever needed, or set it on a cron schedule and let it run without any manual involvement. This is what makes the PrestaShop Import Export Module genuinely useful for recurring catalog operations.

A store fetching pricing updates from a supplier feed can configure an import profile that points to the supplier’s SFTP location, runs daily via cron scheduling, and sends a completion email to the admin. If a row fails, the transfer logs show exactly which record failed and why, so only the affected rows need to be corrected and re-imported; the rest of the catalog is untouched.

That same logic applies to catalog backups. Each scheduled export generates a file timestamped and stored in the transfer history. If a bulk update produces unexpected results, a previous version can be downloaded directly from the logs and re-imported to restore the catalog to its prior state.

How Can You Bulk Update Prices in PrestaShop Without a Developer

One of the most time-consuming recurring tasks for any mid-size store is a price update across hundreds of products. The conventional approach involves either editing products one by one or attempting a CSV import that may or may not map correctly and may or may not touch only the fields that need changing.

With a PrestaShop Bulk Data Manager approach, the process is: export the catalog to XLSX, edit the price column in Excel, and import the file back with the same saved profile. The module updates only the columns that were mapped; prices change while descriptions and images remain exactly as they were.

For stores syncing from a supplier feed, even the manual edit step disappears. The supplier publishes an updated file to an FTP location, the scheduled import profile picks it up, and the catalog reflects the new prices before the store opens the next morning. No developer required, no file handling, no manual trigger.

Which File Formats Does the PrestaShop Catalog Import Export Module Support

Four file formats are supported for both import and export: CSV, XLSX, JSON, and XML. Most merchants will use CSV or XLSX for direct spreadsheet work and bulk price updates. JSON and XML become relevant when synchronising data between stores, connecting with third-party platforms, or building automated migration workflows.

Supporting all four in both directions means the same module covers the full range of catalog operations a store typically needs over a year, whether that means importing supplier feeds, migrating catalog data, synchronizing inventory updates, or exporting product information for external systems.

How Does the Module Handle Import Errors Before They Reach Your Live Store

Partial import failures are a real operational risk for stores with large catalogs. The standard outcome with most basic importers is discovering that something went wrong only after browsing the catalog and noticing broken products, at which point the damage is already live.

The column mapping screen in this PrestaShop Automated Catalog Manager shows a live preview of the first rows of the source file before the import runs. Required fields not mapped are flagged before moving forward. Duplicate field assignments are blocked. When an import does run, and a row fails, the transfer log records the row number and the specific error. The PrestaShop Automated Catalog Manager ensures admins fix only what broke, re-import only the affected rows, and the live catalog is never touched beyond what was intentional.

Who Should Use the PrestaShop Catalog Import Export Module

Not every PrestaShop store needs this. If the catalog is under 100 products, changes rarely, and migration is a one-time event, the built-in importer may be sufficient.

The PrestaShop Catalog Import Export Module earns its place for stores managing medium to large catalogs where catalog operations recur weekly or more often, stores running multilingual setups where translation preservation is not optional, agencies managing multiple PrestaShop installations who need consistent, repeatable transfer workflows, and any merchant currently spending developer time on what should be a self-service admin task.

For those operations, the module pays for itself quickly, not in a theoretical ROI calculation, but in the hours it stops consuming every update cycle.

The full feature set, pricing, and compatibility details are available on the PrestaShop Bulk Data Manager product page. Compatible with PrestaShop 1.7.x through 9.x, with no coding required.

PrestaShop Order, Customer and Address Import Export Addon – Complete User Guide

1.0 Introduction

Managing order data across stores and partner systems is one of the most time-consuming tasks a PrestaShop admin faces. Migrating to a new store means recreating order history by hand. Sending daily order files to a warehouse or finance team means logging in, exporting, and sending on a schedule that someone has to maintain. Fixing corrupted records after a failed transfer means hours of cleanup with no clear record of what went wrong. The Knowband PrestaShop Order, Customer and Address Import Export Addon serves as a powerful PrestaShop Bulk Migration Module, handling all three challenges with ease. It transfers orders, customers, and addresses between PrestaShop stores and external systems in CSV, XLSX, JSON, and XML, with cross-store identity resolution, FTP/SFTP delivery, scheduled automation, and a full audit log. No developer is needed at any step.

This guide covers every tab, wizard step, and setting so you can configure the PrestaShop Order, Customer and Address Import Export Addon and start transferring order data on day one. Compatible with PrestaShop 1.7.x through 9.x.

1.1 Who Is The PrestaShop Bulk Migration Module For

The Knowband PrestaShop Order, Customer and Address Import Export Addon is built for:

Store owners migrating from an existing PrestaShop installation who need to bring the full order history across.
Operations teams that rely on a PrestaShop scheduled order export to send regular files to warehouses, fulfilment partners, or accounting systems.
Admins who need PrestaShop bulk order management for correcting records, exporting a set, editing in Excel, and re-importing the corrected file.
Any organisation that needs a verifiable record of every order data movement for audit or compliance purposes.

2.0 Installation Guide

System Requirements

PrestaShop 1.7.x, 8.x, or 9.x
PHP 7.2 or higher

Installing the Module

Head to your PrestaShop back office and go to Modules, then Module Manager. Find the upload option at the top right of the screen. Select the ZIP file from your account and confirm. PrestaShop processes the upload on its own.

Once the upload finishes, hit Install on the prompt that follows. The module configuration screen opens right after. If the module does not appear, type Order Import Export into the Module Manager search and click Configure.

Common Installation Issues

Upload fails: The server is rejecting the file size. Ask your host to raise upload_max_filesize and post_max_size to at least 32 MB.
Module not visible after install: Clear the PrestaShop cache under Advanced Parameters, then Performance and search again.
Configuration page looks broken: Clear your browser cache and the PrestaShop theme cache under Design, then Theme and Logo, then Advanced Settings.

3.0 Admin Panel Overview

The Knowband PrestaShop Order, Customer and Address Import Export Addon adds four main tabs to the back office:

General Settings: Module preferences, sample template downloads, performance limits, and CRON configuration.
Export: Create and run export profiles using the three-step wizard.
Import: Create and run import profiles using the three-step wizard.
Transfer Logs: A full history of every import and export run with status, record counts, and row-level error detail.

4.0 General Settings Tab

The General Settings tab has four sub-tabs: Preferences, Template Files, Limits and Speed, and Scheduled Cleanup.

4.1 Preferences

Module Enable/Disable: The main toggle for the entire PrestaShop Bulk Migration Module. When set to Disabled, all scheduled CRON import and export tasks pause automatically. The manual Export and Import wizards in the back office continue to work normally regardless of this setting.

Maximum Visible Columns: Sets how many columns appear at one time in the import mapping table. Range is 1 to 20. Use the arrow controls in the mapping interface to scroll through the remaining columns.

Maximum Visible Rows: Controls how many sample data rows appear in the import mapping preview. Range is 1 to 50.

Import Batch Size: The number of rows the module processes per AJAX request during an import run. Range is 10 to 500. Lower values reduce timeout risk on shared hosting environments where large imports hit PHP execution limits.

Click Save Settings to apply.

4.2 Template Files

The Template Files sub-tab provides ready-to-fill sample files for each supported entity in all four formats. Download a template before building your first import file to confirm the column layout.

Three entities are available:

Orders: CSV, JSON, XML, XLSX
Customers: CSV, JSON, XML, XLSX
Addresses: CSV, JSON, XML, XLSX

Each sample contains realistic, fully populated data across every supported column. Templates are generated from the live column catalogue and stay updated with any schema updates.

4.3 Limits and Speed

Max Records Per Download: The maximum number of records exported per file. Range is 100 to 50,000. Increase only when server memory allows.

Max Upload Size (MB): The maximum import file size the module accepts. Range is 1 to 200 MB.

Click Save Settings to apply.

4.4 Scheduled Cleanup

Keep Files For (Days): Import files older than this number of days are deleted automatically by the cleanup CRON. Range is 1 to 30 days.

Cleanup CRON URL: Paste this URL into your server’s cron manager to delete old temporary import files on a schedule. The example runs daily at 2 AM.

Export Profiles CRON URL: Paste this URL into your server’s cron manager to run every export profile flagged as CRON-enabled. Pick any frequency that suits your PrestaShop scheduled order export needs, for example, daily at 3 AM.

Import Profiles CRON URL: Paste this URL into your server’s cron manager to run every FTP-source import profile flagged as CRON-enabled. Upload-source profiles are manual-only and are skipped automatically when this URL runs. Example: daily at 4 AM.

All three URLs are token-secured. Only requests carrying the correct token trigger the operation.

5.0 Export Tab: Three-Step Wizard

The Export tab lists all saved export profiles and provides the wizard for creating new ones. Each row in the list shows the profile name, data type, file format, and last run status. Click the run button to execute a profile immediately. Click Edit to change its settings.

Step 1: Transfer Settings

Profile Name: A unique label that identifies this profile in the Export listing.

Output File Label: The base name of the generated file. The extension is added automatically. Supports dynamic tokens (see Section 10).

Data Type: Choose what to export: Orders, Customers, or Addresses.

File Format: CSV, XLSX, XML, or JSON. CSV and XLSX open directly in any spreadsheet application. XML and JSON suit system integrations.

Shop: Limits the export to records belonging to the selected shop in a multi-shop setup.

Date Range (optional): Filter by order creation date. Leave blank to export all records.

Record Order (optional): Control the row sequence in the output file. Sort by ID, Reference, Date Created, Date Updated, Total Paid, or State, ascending or descending. Leave on default to use database order.

Optional Column Sections: Three independent toggles control whether full column blocks are included in the export.

Include invoice address details: When off, only the Invoice Address ID is exported. When on, all invoice address columns are included.
Include shipping address details: When off, only the Shipping Address ID is exported. When on, all shipping address columns are included.
Include payment details: When off, only the payment module name is exported. When on, the payment amount, currency, method, and transaction ID columns are included.

Scheduled Run (Enable CRON): When on, the Export Profiles CRON URL runs this profile automatically and stores the generated file under the Transfer Logs tab.

Export Destination: Choose File System to save the file locally for download from the Transfer Logs page. Choose FTP/SFTP to push the file to a remote server after each run. A local copy is also kept as a fallback download when FTP/SFTP is selected.

FTP/SFTP Settings (when FTP/SFTP destination is selected):

Transfer Protocol: FTP, FTPS (FTP over TLS), or SFTP (SSH). SFTP is recommended for production environments.
Server, Port (auto-updates when the protocol changes: 21 for FTP, 990 for FTPS, 22 for SFTP).
Username and Password (stored encrypted at rest).
Absolute Path to Folder on the remote server. The folder must exist and be writable.
Passive Mode: On by default. Recommended to keep on so firewalls do not block transfers.
Test Connection button: validates credentials against the live server before the profile is saved.

Output Style: Universal comma for most applications, semicolon for European Excel, or tab-separated for data tools.

List Glue: The separator used for multi-value fields. Pipe, Slash, or Comma.

Narrow Orders By (optional filters):

Order Status: filter by one or more statuses.
Carrier: filter by one or more carriers.
Currency: filter by one or more currencies.
Payment Method: filter by one or more payment modules.
Total Paid Range: include only orders within a minimum and maximum total paid value (tax included).

Leave any filter empty to include all records for that dimension.

Click Next Step to proceed.

Step 2: Choose Fields

Select the fields to include in the export from 155 available columns. Use Select All, Deselect All, or Reset to Defaults as needed. Required fields cannot be deselected. Drag rows to reorder the columns in the output file.

The 155 available fields span six sections: order data, customer data, address data, payment data, and product line data.

Step 3: Generate File

Review the export summary, data type, file format, file label, and field count. Click Build and Download to generate the file immediately, or save the profile and let the CRON run handle it on schedule.

6.0 Import Tab: Three-Step Wizard

The Import tab lists all saved import profiles and provides the wizard for creating new ones.

Step 1: Source Settings

Profile Name: A unique label for this profile in the Import listing.

Data Type: Orders, Customers, or Addresses. Customers and addresses update existing records on match. Orders are always created anew; existing orders cannot be updated through this module.

File Format: CSV, XLSX, JSON, or XML.

Output Style and List Glue: Must match the settings used when the file was exported.

Shop: Imported orders are always created under the selected shop.

Source: Upload File for a one-time manual import from a local file. FTP/SFTP to pull the file from a remote server. FTP/SFTP source is required for CRON-driven import runs.

FTP/SFTP settings: Same fields as the export wizard, protocol, server, port, username, password, remote file path, passive mode, and test connection.

CRON: Only available for FTP source profiles. When on, the Import Profiles CRON URL fetches the file from the remote path and runs the import automatically without manual intervention.

Click Save Profile to save without running, or Next Step to proceed to mapping.

Step 2: Map Columns

The PrestaShop Bulk Migration Module reads the uploaded file and auto-matches column headers to PrestaShop fields. From the live module, 154 of 155 columns are matched automatically from recognised header names.

The mapping screen shows the first rows of the file as a live preview so the admin can verify data before committing. Required fields are marked with an asterisk. Search columns by name using the search field above the table.

Review the auto-matched assignments and adjust any that need correcting. Common naming variants from external systems are recognised automatically in most cases.

Step 3: Run Import

Mapping confirmed. Click Start Import to begin. The module processes the file in batches based on the Import Batch Size setting in Preferences. A progress indicator shows the current status.

Click Save Profile before starting to preserve the column mapping for future runs of the same file structure.

7.0 Cross-Store Identity Resolution

Migrating orders between PrestaShop installations is the most complex use case for any PrestaShop store migration module. Raw database IDs for customers, addresses, and products differ between stores and cannot be used as transfer identifiers.

The PrestaShop order migration addon resolves all three entity types using identifiers that remain stable across installations:

Customers are matched by email address. No match creates a new account using the name, email, and a system-generated password. The customer resets credentials and accesses their account on the new store immediately.

Addresses are matched by a composite hash built from first name, last name, address line one, postcode, city, and phone. No match creates a new address record from the imported data.

Products and combinations are matched by product reference and combination reference. An unresolvable reference rejects the entire order, no partial writes, no line items pointing at missing products.

A full export from one store imports cleanly using this PrestaShop store migration module into a separate installation without any manual remapping of accounts, addresses, or product IDs.

8.0 Data Integrity and Validation

The importer enforces order-level atomicity. If any line item within an order fails validation, the entire order is excluded from the batch. No partial order record is written to the database.

Every rejection produces a precise log entry:

Row 23: column “currency_iso” contains “USDD”, expected a 3-letter ISO 4217 code (e.g. USD, EUR, GBP). Row 41: column “customer_email” contains “not-an-email”; a valid email address is required.

Fix only the affected rows in the source file and re-import them. The rest of the batch is unaffected.

9.0 Transfer Logs Tab

Every import and export operation writes a log entry to the Transfer Logs tab. Each row shows:

ID: Sequential run number.
Type: Export or Import.
Entity: Orders, Customers, or Addresses.
Format: CSV, XLSX, JSON, or XML.
Status: Completed or Failed.
Records: How many records the run processed.
File: The filename, with a download link for export files.
Date: When the run started.

Filter the log by ID, type, entity, format, status, or date range using the controls at the top of the table.

Past export files can be re-downloaded directly from the log without re-running the export. Row-level error detail is accessible for any run that produced failures.

10.0 Dynamic Filename Tokens

Output file labels support nine runtime tokens that expand at the point of generation:

orders_{DATE}.xlsx produces orders_20260608.xlsx
{SHOP}orders{DATETIME}.csv produces mystore_orders_20260608_143215.csv

Available tokens: {DATE}, {DATETIME}, {TIME}, {YEAR}, {MONTH}, {DAY}, {ENTITY}, {FORMAT}, {SHOP}.

11.0 Frequently Asked Questions

Q: What is the Knowband PrestaShop Order, Customer and Address Import Export Addon, and what does it do?

The Knowband PrestaShop Bulk Migration Module is a bulk order data transfer tool that imports and exports PrestaShop orders, customers, and addresses in CSV, XLSX, JSON, and XML. It handles cross-store identity resolution, reusable transfer profiles with saved column mapping, FTP and SFTP file delivery, CRON-based scheduled automation, 155 exportable fields, email notifications, and a full transfer log with row-level error detail. Compatible with PrestaShop 1.7.x through 9.x.

Q: How do I migrate orders from one PrestaShop store to another?

Create an export profile on the source store and download the orders file. On the destination store, create an import profile, upload the file, confirm the column mapping, and run the import. The PrestaShop order migration add-on resolves customers by email, addresses by composite hash, and products by reference. No manual remapping of accounts, addresses, or product IDs is needed between the two stores.

Q: What happens if a product reference in the import file does not exist in the destination store?

The entire order containing that line item is excluded from the import. No partial order record is written. The Transfer Logs tab records the row number, column name, and the specific value that could not be resolved. Fix only the affected rows and re-import them.

Q: What file formats does the PrestaShop Bulk Migration Module support?

CSV, XLSX, JSON, and XML, all four in both import and export directions. CSV and XLSX open in any spreadsheet application. JSON and XML suit system integrations and API-based partners.

Q: How does the scheduled PrestaShop order export work via CRON?

Enable CRON on any export profile, set the destination to FTP/SFTP, and copy the Export Profiles CRON URL from General Settings into your server’s cron manager with the required interval. Every CRON-enabled PrestaShop bulk order management profile runs automatically on that schedule, pushes the file to the configured server, and sends a completion notification. Upload-source import profiles are manual-only and are skipped automatically when the Import Profiles CRON URL fires.

Q: Can I filter which orders get exported?

Yes. The export wizard includes filters for order status, carrier, currency, payment method, and total paid range. A date range filter narrows exports to a specific creation window. Apply any combination of filters and leave the rest blank to include all records for those dimensions.

Q: How does FTP and SFTP file delivery work?

Export profiles push files to FTP (port 21), FTPS (FTP over TLS, port 990), or SFTP (SSH, port 22). Import profiles pull files from FTP or SFTP on a schedule. Credentials are stored encrypted. A test connection button validates the connection before the profile is saved. If a push fails, the file saves locally, and a notification email explains the failure.

Q: What is the PrestaShop order backup module feature?

Every import and export run writes a log entry to the Transfer Logs tab with date, filename, entity type, status, and record counts. Past export files re-download from the log without re-running the export. This gives organisations with audit or compliance requirements a complete, timestamped record of all order data movements.

Q: How many fields can be exported per order using the PrestaShop Bulk Migration Module?

155 fields are available across order data, customer data, product line data, address data, and payment data. Per-section toggles let admins include or exclude the full invoice address block, the shipping address block, and the payment detail block independently to keep files lean when full columns are not needed.

Q: Is the PrestaShop Order, Customer and Address Import Export Addon compatible with PrestaShop 9?

Yes. The PrestaShop Order, Customer and Address Import Export Addon works with PrestaShop 1.7.x through 9.x. Check the product page for the most current compatibility details.

12.0 Conclusion

This addon covers every order data transfer need from one back-office panel. Export any combination of orders, customers, and addresses to the format each receiving system needs. Import complete order history into a new store without manual account remapping. Schedule everything via CRON and push files automatically via FTP or SFTP.

Every run is logged with the PrestaShop order backup module, keeping every entry timestamped. Every failure gives a precise, fixable error message. Every export file stays available for re-download. For support, custom development requirements, or PrestaShop addon services, reach out to the Knowband support team or visit the Knowband product page directly.

Also available on Prestashop Addons – https://addons.prestashop.com/en/data-transfer-backup/98144-advanced-order-customer-address-data-migration.html

PrestaShop Smart Admin Assistant – Complete User Guide

1.0 Introduction

Managing a PrestaShop store means working with data every day. Orders, stock levels, customer registrations, abandoned carts, revenue, coupon activity, the numbers keep coming. Running the same data checks every day means going through the same steps each time: open a report, set the filters, wait for the page, and do it all over again the next morning. It adds up to a lot of time spent on something that should take seconds. The Knowband PrestaShop Smart AI Admin Assistant removes that friction. It places an AI-powered chat interface directly inside your PrestaShop back office. Type a question in plain English, get an answer from your live store data in seconds, no SQL knowledge, no report navigation, no developer required.

This user manual covers every tab and setting so you can configure the module, connect your AI provider, and start querying your store data on day one. Compatible with PrestaShop 1.7.x through 9.x.

1.1 Who Is This Module For

The PrestaShop Smart Admin Assistant is built for:

Store owners who check the same figures every morning and want a faster way to do it.
Operations managers who need instant answers on orders, stock, and revenue without digging through reports.
Stores with multiple admin staff where different roles need different levels of data access.
Any merchant who wants AI-powered PrestaShop back office analytics without a developer on call.

2.0 Installation Guide

System Requirements

PrestaShop 1.7.x, 8.x, or 9.x
PHP 7.2 or higher
A working API key from OpenAI, Anthropic, or Google

Uploading and Installing the Module

Step 1: Log in to your PrestaShop back office, go to Modules, and open Module Manager.

Step 2: Find the “Upload a Module” button at the top right, select the ZIP file you downloaded from Knowband, and confirm. PrestaShop takes it from there.

Step 3: Once the upload finishes, an Install button appears. Click it. The module configuration screen opens on its own once installation is done.

Step 4: If nothing appears after install, type Smart Admin Assistant into the Module Manager search bar and hit Configure.

Common Installation Issues

Upload fails: Server upload size limit is too low. Ask your host to increase upload_max_filesize and post_max_size in the PHP settings to at least 32 MB.

Module not visible after install: Clear the PrestaShop cache under Advanced Parameters, then Performance, then search for the addon again.

Configuration page appears broken: Clear your browser cache and the PrestaShop theme cache under Design, then Theme and Logo, then Advanced Settings.

3.0 PrestaShop Smart AI Admin Assistant: Admin Panel Overview

The PrestaShop Smart AI Admin Assistant has eight tabs across the top of the configuration page:

Settings: Core preferences, SQL toggles, voice input, language, log retention, schema cache.
AI Provider: Connect OpenAI (ChatGPT), Anthropic Claude, or Google Gemini using your API key.
Widget Layout: Customise the chat widget appearance with a live preview that updates as you make changes.
Database Views: Choose which data categories the AI is allowed to query.
Access Control: Manage which admin profiles are permitted to open the assistant.
Predefined Chips: One-click question buttons for quick daily checks.
Query History: A running log of every query, showing the employee, how long it took, and whether it succeeded.
Sessions: Complete chat threads per employee.

Together, these tabs cover everything from PrestaShop Smart Store Analytics and reporting to data access control and session history.

4.0 Settings Tab

4.1 General Settings of the PrestaShop AI Dashboard Module

Enable Chatbot: Toggle the PrestaShop Smart AI Admin Assistant on or off. All settings are preserved when disabled; re-enabling them brings everything back instantly.

Enable Predefined Chips: Toggle the quick-click question buttons on or off inside the chat widget.

Chips Default State: Collapsed means the chips panel will be hidden when the widget first opens. Expanded means all chips will be visible as soon as the assistant loads.

Max Result Rows: The maximum number of rows the AI may return for any one query.

The range runs from 1 to 1000, with 100 as the default. Push it higher for detailed data pulls, keep it lower when you just need a quick figure.

Show SQL Query Toggle: When set to Yes, the assistant displays the exact SQL it generated beneath each answer. This is the core PrestaShop back office analytics transparency feature; admins see precisely how every answer was produced.

Allow SQL Edit and Re-run: When set to Yes, admins can edit the generated SQL directly in the chat and re-run it. Useful for adjusting a date range, threshold, or filter without typing a new question from scratch.

Voice Input: Enables the microphone icon in the chat input. Admins can speak questions instead of typing, using the browser’s Web Speech API. This voice input admin feature for PrestaShop works best in Chrome on a desktop.

4.2 Language Settings

Use Back-office Language: The assistant matches the language your PrestaShop admin panel is currently running in.

Use Custom Language: Choose a fixed response language which will not change based on the language the back office is set to. Useful when individual staff members work in a language different from the one in which the back office is configured.

4.3 Log and Cache Settings

Log Retention (days): Decides how many days of query history the module holds before deleting old entries. Default is 90 days. The cleanup runs on its own schedule without any manual database work.

These settings help the PrestaShop Smart Insights Module maintain accurate and up-to-date query records at all times.

Schema Cache TTL (minutes): The schema is the structure map of your database that the AI reads to build accurate queries. This setting controls how long the map is cached before the addon fetches a fresh copy.

Refresh Schema Now: Triggers an immediate schema refresh on demand. Run this after adding a new module, upgrading PrestaShop, or any change that alters the database structure.

Click Save Settings to apply all changes on this tab.

5.0 AI Provider Tab

The AI Provider tab is where you link the module to your preferred AI service. OpenAI (ChatGPT), Anthropic Claude, and Google Gemini are all supported. This multi-AI provider support means you are not locked into a single vendor. You supply your own API key, and the addon connects directly to your chosen provider.

5.1 Choosing Your Provider

Click the provider button, OpenAI (ChatGPT), Anthropic Claude, or Google Gemini, to select it. The settings below update to show fields for that provider.

5.2 How to Get Your API Key

OpenAI

Go to platform.openai.com and sign in or create an account.
Select API Keys from your profile menu. Hit Create new secret key, name it, and confirm. Copy the key right away since OpenAI only shows it once.
Paste it into the OpenAI API Key field in the module. This connects the PrestaShop OpenAI back office integration directly to your account.

Anthropic Claude

Go to console.anthropic.com and sign in or create an account.
Click API Keys in the left sidebar.
Click Create Key, give it a name, and copy the key shown.
Paste it into the Claude API Key field. The PrestaShop Claude AI back office connection is established as soon as the key is saved.

Google Gemini

Go to aistudio.google.com and sign in with a Google account.
Click Get API key in the top left.
Click Create API key, select a project, and copy the generated key.
Paste the key into the Gemini API Key field in the addon. The PrestaShop Gemini Admin Module integration activates immediately after saving.

5.3 Selecting a Model

OpenAI models:

GPT-4o Mini (Fast and Cheap): A solid choice for everyday admin queries.
GPT-4o (Balanced): Handles more complex questions that involve multiple tables.
GPT-5.5 (Most Capable): The strongest option for detailed analytical work.

Anthropic Claude models:

Claude Haiku 4.5 (Fast and Cheap): Works well for straightforward daily checks.
Claude Sonnet 4.6 (Balanced): Sits between speed and depth for most use cases.
Claude Opus 4.7 (Most Capable): Use this when queries involve several joined tables or layered conditions.

Google Gemini models:

Gemini 3.5 Flash (Fast and Capable): The recommended pick for general store queries.
Gemini 3.1 Flash-Lite (Fastest and Cheapest): Best suited for stores where keeping API costs low is the priority.

5.4 Temperature Setting

This controls how strictly the AI sticks to factual output. At 0, responses are as precise as possible. At 1, there is more variation in how answers are phrased. For store data queries, 0.3 works well as a starting point. Drop to 0.0 if you need the most literal, consistent results.

Click Save Provider Settings to apply.

6.0 Widget Layout Tab

The Widget Layout tab controls how the chat window looks inside the back office. A live preview panel on the right updates in real time as you adjust each setting.

Position: Where the chat bubble sits on screen. Default is Bottom Right.

Chatbot Name: The label shown in the widget header. Default is Smart Admin Assistant.

Greeting Message: The opening line the assistant shows when the widget is opened. Default reads “Hello! Ask me anything about your store.”

Bubble Icon: A custom image for the floating chat button. Square PNG, 64×64 px, maximum 2 MB.

Chatbot Avatar: The image that appears beside bot messages inside the chat window. Square PNG, 48×48 px, maximum 2 MB.

Widget Width and Height (px): Controls the size of the chat panel. Default is 400 wide by 560 tall.

Colour Settings: Six individual controls for Header, Chat Bubble, User Message, Bot Message, Background, and Text colours. No CSS editing needed.

Click Save Layout to apply.

7.0 Database Views Tab

7.1 What Are Database Views

Database views in PrestaShop are pre-built MySQL structures that join and simplify relevant tables. The PrestaShop AI back office module works through these views rather than querying raw database tables directly, so the AI can give accurate answers without any risk of touching data it should not. Every view is read-only. The assistant can retrieve information but cannot change, remove, or add anything.

Turning off a view removes it from what the assistant can query. The MySQL view itself stays in the database unchanged, so switching it back on works immediately.

7.2 Available Database Views

Orders Overview: Order records including customer details, currency, status, and totals. Provides real-time order data for admins without any report generation.
Order Line Items: Individual product lines within each order, with quantities and prices.
Customers: Customer accounts with group membership, gender, and last visit date.
Products: Product data covering name, stock, price, category, and image information.
Specific Prices / Product Discounts: Price overrides set at the product level. Off by default.
Categories: Category names and the hierarchy they sit in.
Shopping Carts: Both active and abandoned carts, with customer and currency details.
Cart Rules / Coupons: Discount rules with usage data, free shipping flag, and conditions.
Stock Availability: Stock levels per product and combination with readable combination names. Powers PrestaShop stock insights AI queries about low and out-of-stock items.
Employees: Back-office user accounts and profile information.
Customer Addresses: Full address records with country, state, and linked customer names.
Carriers / Shipping Methods: Active delivery carriers. Off by default.
Manufacturers / Brands: Brand records with descriptions and product counts.
Product Combinations / Variants: Variant-level data, including stock, reference, and attribute names.
Product Attributes and Values: Attribute groups such as Colour and Size, with all associated values.

Click Save and Create Views to apply. The module builds the MySQL views for each domain you have switched on.

8.0 Access Control Tab

The Access Control tab controls which back-office users can see and open the PrestaShop Smart Admin Assistant.

Toggle: Enable role-based access by limiting the chatbot to particular employee profiles.

When on, a profile list appears. SuperAdmin always has access and is not listed. Tick the additional profiles: Logistician, Translator, and Salesman. Profiles left unticked cannot see the assistant. Leaving all profiles unticked with role-based access restricts the assistant to SuperAdmin only.

This employee access control feature for PrestaShop makes the PrestaShop Store Management AI capability available only to the staff roles that need it.

Click Save Access Settings to apply.

9.0 Predefined Chips Tab

Predefined chips are quick-click question buttons inside the chat widget. Clicking a chip sends the saved question to the AI instantly, no typing needed.

They are one of the most practical features for PrestaShop Smart Store Analytics, covering the most common store performance questions admins ask every day.

9.1 Default Chips in the PrestaShop Smart AI Admin Assistant

The module ships with ten predefined quick query chips that are active and ready to use from the first login:

Orders Today: How many orders were placed today?
Revenue (30d): What is the total revenue in the last 30 days?
Cancelled Orders: How many orders were cancelled in the last 30 days?
Abandoned Carts: How many abandoned carts are there in the last 30 days?
Active Customers: How many active customers do we have?
Out of Stock: Which active products are currently out of stock?
Low Stock (less than 5): Which products have fewer than 5 units in stock?
No SKU Products: How many products do not have a SKU reference?
Free Shipping Coupons: Are there any active coupons that offer free shipping?
New Customers (This Month): How many customers registered this month?

9.2 Adding a Custom Chip

Click Add Chip to open the edit panel.

Label: The short text that shows on the chip button itself. For example: Weekly Revenue.

Question: The full question that gets sent to the AI when someone clicks the chip. For example: What is the total revenue for the last 7 days?

Position: Sets where this chip sits in the list. Lower numbers come first.

Active: Yes, puts the chip in the widget. No hides it without removing the configuration.

Click Save Chip to confirm. Each existing chip has Edit and Delete buttons on its row for making changes or removing it entirely.

10.0 Query History Tab

The Query History tab keeps a log of every question submitted through the PrestaShop admin AI chatbot, functioning as a complete admin session history log for back-office data requests. Each row shows:

Date: When the question was asked
Employee: The admin account that sent it
Question: The full text of the query
Rows: The number of data rows the answer contained
Time (ms): How long the query took to run, in milliseconds
Provider: Which AI provider processed the query, displayed as a labelled badge
Status: Shown as a green badge for success or a red badge for an error
SQL: The generated SQL is available to view directly in the row

Use the status and date filters at the top of the tab to narrow the list. Export to CSV or Excel with the buttons above the table. Click Purge Old Logs to immediately delete entries older than the Log Retention setting.

11.0 Sessions Tab

The Sessions tab stores complete conversation threads per employee. Each session shows the employee name, start time, and message count. Click View to open the full conversation, questions, and responses displayed chronologically in a pop-up. Useful for auditing how the assistant is being used or picking up context from a previous session.

12.0 Analytics Dashboard

The Analytics Dashboard is also the core feature of the PrestaShop AI Admin Assistant, which is added in the version 1.0.1, giving store owners a single, live screen for revenue, orders, customers, and stock the moment they open their back office. Being as a PrestaShop AI Dashboard Module, it removes the need to dig through order lists or export spreadsheets from the default prestashop just to understand how the store is performing. Here, widgets are grouped into three categories:

Key Metrics: KPI cards covering revenue, order volume, and customer activity
Charts & Trends: visual breakdowns of how sales move over time and across categories
Lists & Tables: ranked views such as top-selling products and low-stock warnings

Each employee can decide which widgets show up on their own dashboard and arrange them however suits their work using the module configuration. You can change the setting from the dashboard settings in the Prestashop Analytics & Reporting Module, like which order states count toward revenue are configured so that numbers stay consistent across the whole team. Together, this makes the module one of the more complete options for PrestaShop AI Backend Analysis, combining reporting, forecasting, and inventory intelligence in one place.

12.1 Analytics Dashboard Settings

You’ll find these controls under Settings → Dashboard Settings. This is the central configuration screen for Knowband Smart AI Admin for PrestaShop, and every option here applies store-wide, across all employee accounts. Individual staff can still adjust their own widget selection and layout from the dashboard’s Customize panel, but the calculations behind the numbers are governed here. Use this section to define how revenue is calculated, which time frame the dashboard opens with by default, its visual theme, and whether it becomes your new back office landing page.

12.2 Dashboard Settings in Smart AI Admin

Revenue Order States

This setting determines which PrestaShop order states are counted as revenue throughout the dashboard, feeding every sales-related widget including Revenue, Orders, Average Order Value, Best Sellers, Top Customers, and Coupon Usage.

Default Period

Sets the time range the dashboard loads with by default. Choose from Last 7 Days, Last 30 Days, Last 3 Months, Last 6 Months, or Last 1 Year.

Colour Theme

Controls the visual styling of the dashboard. Available themes include Indigo (default), Ocean, Emerald, Rose, Dark, and Custom.

List Rows

Sets how many rows appear in each list- or table-based widget across the dashboard, including Best Sellers, Top Customers, Slow Movers, Reorder Suggestions, Churn Risk, Low Stock Alerts, Coupon Usage, and Brand Performance.

Churn Window

Defines the number of days a customer must be inactive before they appear in the Churn Risk widget, one of the module’s dedicated customer retention tools.

Low Stock Threshold

Sets the quantity at or below which a product is classed as “low stock” across the Low Stock, Low Stock Alerts, and Reorder Suggestions widgets. This threshold underpins the dashboard’s Stock Insights AI, the module’s dedicated engine for surfacing inventory risks before they become lost sales.

Replace Default Dashboard

Enable this option to have the Analytics Dashboard take over as your PrestaShop back office home page, opening automatically for every employee immediately after login. When disabled, PrestaShop’s native dashboard remains the default landing screen, and the Analytics Dashboard can still be opened separately from the admin menu whenever it’s needed. This is what makes the module function as a true PrestaShop AI Module Back Office replacement rather than a bolt-on report you have to remember to check.

Customising Your Dashboard

Every employee can rearrange their own dashboard independently, without affecting anyone else’s view.

Click Customise (the widget library icon) on the dashboard. Drag widgets to reorder them within their group (Key Metrics, Charts & Trends, or Lists & Tables). Close the panel to see your updated layout in place. If you’d rather start over, click Restore Default to reset the dashboard to its original configuration.

12.2 Key Metrics (17 widgets)

As a PrestaShop Admin Analytics AI toolkit, the Key Metrics group is where store owners get their fastest daily read on the business, before digging into charts or lists.

Revenue shows total order value for the chosen period and the order states defined in your dashboard settings, paired with a daily trend line and a percentage change against the prior period. This is the module’s built-in PrestaShop AI Sales Report Module output, always visible from the moment you log in.

Orders: Displays the number of orders placed within the selected period, along with a trend line and percentage change, giving you the volume side of the store’s order analytics at a glance.

Avg. Order Value: Calculated as total revenue divided by total orders, this metric gives store owners an immediate pulse check without opening a spreadsheet. If pricing or promotions shift customer spending, it shows up here first.

Items Sold: Total units sold across all orders in the selected period. Useful for tracking sales volume on its own terms, separate from revenue, particularly when running discounts or bundle offers.

Items per Order: Shows the average number of items per order, helping you understand whether customers are typically buying single items or shopping in bulk.

Discounts Given Totals the value of vouchers, cart rules, and reward discounts applied in the selected period, with a percentage change against the previous period so you can track how promotional activity is trending.

Taxes Collected: Reports total tax collected on orders during the selected period, useful when reconciling figures for accounting or compliance.

Shipping Revenue Totals the shipping fees collected from customers over the selected period, with a percentage change shown against the prior period.

Refunded Value Tracks the total value of orders marked as refunded within the selected period, giving visibility into returns and revenue lost to them.

New Customers: Counts customers who created an account during the selected period, pulled directly from registration data. This metric lets store owners see the real-time effect of acquisition campaigns without waiting on a manual export.

Repeat Customers: Counts customers who placed two or more orders within the selected period. This figure feeds directly into the module’s customer retention view, offering a quick read on loyalty without manually cross-checking order histories.

Returning Buyer Rate: The percentage of buyers in the period who ordered more than once, calculated as repeat customers divided by total unique purchasers. It’s a fast way to see whether retention efforts, from email campaigns to loyalty schemes, are actually turning first-time buyers into repeat business.

Total Customers shows the full customer count registered in the store to date, independent of the selected period. As a live snapshot, it always reflects the current total the moment the dashboard loads.

Active Products shows how many products are currently enabled and available for sale on the storefront, giving a quick read on active catalogue size when auditing inventory.

Out of Stock Flags enable products currently sitting at zero quantity, so stockouts are caught immediately rather than discovered after a customer tries to order.

Low Stock Counts enabled products at or below the low-stock threshold set in Analytics Dashboard Settings, acting as an early warning for reordering before a product actually runs out. This is one of the widgets that makes Stock Insights AI genuinely useful day to day, rather than just a static report.

Units in Stock totals the quantity held across every enabled product in the store, giving a single figure for overall stock volume. Best read alongside Low Stock and Out of Stock for a full inventory picture.

12.4 Charts & Trends (Includes 9 widgets)

Revenue Trend plots revenue over time as a line chart, shown daily for periods up to six months and monthly for a full year. It’s a visual companion to the store’s sales figures, making spikes, dips, and seasonal patterns easier to spot than in raw numbers alone.

Revenue Forecast looks at the last 90 days of trading and projects likely revenue for the next 30 days, based on recent momentum rather than the period currently selected. Powered by the same engine behind the module’s PrestaShop AI Backend Analysis, this helps store owners plan stock orders, cash flow, and marketing spend ahead of time, grounded in actual sales data rather than guesswork.

Orders Trend Charts order volume over time using the same daily-or-monthly logic as Revenue Trend, giving a volume-based counterpart to the revenue chart.

Payment Methods: Breaks down revenue by the payment option customers actually chose at checkout. If one method is quietly outperforming the rest, it’s worth understanding why; if another is barely used, that’s often a sign it needs more visibility or trust-building at checkout.

Sales by Country: A straightforward bar chart of revenue by shipping destination, and a genuinely useful one for spotting where a store’s real geographic strength lies, especially when weighing up new shipping zones or ad spend.

Order Status: Lists every active order state with its revenue and order count side by side, making it easy to see at a glance where orders currently stand, whether still processing, stuck pending, or already delivered.

Sales by Carrier Breaks revenue down by shipping carrier, so you can see which ones your customers actually choose. Worth reviewing periodically, especially when renegotiating rates or deciding whether a new carrier is worth adding.

Sales by Day of Week Groups total revenue by weekday across the whole selected period, not just the past week. Patterns often surface here that aren’t obvious day to day, such as a Thursday that consistently outsells the rest, useful when planning promotions or staffing.

Sales by Hour Shows exactly when customers are most likely to buy, which takes the guesswork out of timing flash sales, email sends, or live chat support.

12.4 Lists & Tables (8 widgets)

Best Sellers ranks products by units sold, showing reference, quantity, and revenue side by side. A quick way to see exactly which products are carrying the business.

Slow Movers Lists active products with the fewest sales in the selected period, helping store owners identify stock that needs a promotional push, a price adjustment, or removal from the catalogue.

Top Customers ranks customers by total revenue alongside order count, giving a clear view of who to prioritise for loyalty perks, personal outreach, or dedicated account management.

Churn Risk Flags high-value customers who haven’t ordered within the configured Churn Window, along with their lifetime value and last order date. This is the core of the module’s retention toolkit, helping store owners re-engage customers before they’re gone for good.

Low Stock Alerts: Lists every product at or below the configured stock threshold, or already out of stock, with reference and quantity, giving an early warning before a bestseller disappears from the shelf.

Reorder Suggestions: Calculates suggested reorder quantities for products sold in the last 30 days, based on current stock, average daily units sold, and remaining days of stock cover. Store owners can use this to restock the right amount, avoiding both overstocking and stockouts.

Coupon Usage shows every voucher redeemed during the selected period, along with number of uses and total discount value, making it easy to see which promotions are actually driving orders versus which ones are just cutting into margin.

Brand Performance Ranks manufacturers by revenue and units sold, rounding out the dashboard’s view of what’s actually driving the store, down to the brand level.

13.0 Frequently Asked Questions

Q: What is the PrestaShop Smart AI Admin Assistant, and how does it work?

The PrestaShop Smart AI Admin Assistant by Knowband lets store admins ask plain-language questions about their store data and receive instant answers. It connects to the live database through pre-built read-only MySQL views, sends the question to the chosen AI provider: OpenAI, Anthropic Claude, or Google Gemini, which generates and runs a SQL query and returns the result in natural language. It brings real-time data access to any back office user without requiring technical knowledge.

Q: Which AI providers does the PrestaShop Smart Admin Assistant support?

The module supports OpenAI (GPT-4o Mini, GPT-4o, GPT-5.5), Anthropic Claude (Haiku 4.5, Sonnet 4.6, Opus 4.7), and Google Gemini (Gemini 3.5 Flash, Gemini 3.1 Flash-Lite). You supply your own API key, and the module connects directly. No subscription to the module’s own AI service is needed. You pay only for actual API usage. All models integrate with the PrestaShop AI Sales Analytics Addon to deliver accurate, fast answers from your live store data.

Q: Can the PrestaShop Smart Admin Assistant modify or delete store data?

No. The assistant accesses the database through pre-built MySQL views, read-only by design. It cannot update, delete or insert any data through the chat interface. Every answer is a read-only retrieval from your live PrestaShop store. It is therefore a safe tool for back office automation without any risk of storing data.

Q: What can I ask the PrestaShop Admin AI Module?

You can ask natural language queries about orders, customers, revenue, stock levels, abandoned carts, discount coupons, product combinations, employee accounts, shipping carriers, brands, and categories. The experience is similar to asking ChatGPT, but every answer comes directly from your live store data. This covers order management, inventory tracking, and no SQL store reporting, all from the back office.

Q: How do predefined chips work in the PrestaShop Smart Admin Assistant?

Predefined chips are quick-click buttons inside the chat widget of the PrestaShop admin AI chatbot. Each chip sends a pre-saved question to the AI when tapped. The default set covers orders today, revenue, abandoned carts, low stock, out-of-stock products, active customers, new customers, cancelled orders, free shipping coupons, and products missing a SKU. Custom chips can be added, edited, or removed from the Predefined Chips tab. This is one of the most useful features of the PrestaShop AI Reporting Module for running daily store checks.

Q: What does the SQL visibility feature of the PrestaShop admin AI chatbot do?

When Show SQL Query Toggle is enabled, the assistant displays the SQL it generated beneath each answer. With Allow SQL Edit and Re-run also on, the admin can modify that SQL in the chat, adjusting a date, threshold, or filter, and re-run it immediately. It effectively turns the PrestaShop AI Sales Analytics Addon into a SQL-free reporting tool that any team member can work with directly. This is especially useful for PrestaShop AI backend analysis without requiring a developer.

Q: How does role-based access control work?

Open the Access Control tab and switch on Restrict the chatbot to specific employee profiles. SuperAdmin always has full access and does not appear in the list. From there, tick any additional profiles you want to include, such as Logistician, Salesman, or Translator. Any profile left unticked will not see the assistant in their back office.

Q: What is the schema cache, and when should I refresh it?

The schema cache in the PrestaShop Smart Insight Module holds a structural map of your database so the AI knows which tables and columns to use when building queries. It generates automatically during the first chat session and updates on the interval set in Schema Cache TTL (24 hours by default). After installing a new module, upgrading PrestaShop, or making any change that affects the database structure, use Refresh Schema Now to pull a fresh copy straight away.

Q: How can I get an API key to work with the PrestaShop Admin AI Module?

OpenAI: go to platform.openai.com, open API Keys from your profile menu and create a new key. Anthropic Claude: go to console.anthropic.com, open API Keys from the sidebar and create one. Google Gemini: go to aistudio.google.com, press Get API key and create one from there. After you have the key, copy it into the appropriate field in the AI Provider tab and save.

Q: Is the PrestaShop Smart Admin Assistant compatible with PrestaShop 9?

Yes. The module runs on PrestaShop 1.7.x through 9.x. The product page has the latest compatibility information.

Q: How does the PrestaShop AI Reporting Module help with sales reporting in PrestaShop?

PrestaShop AI sales report module lets the admin get the revenue, orders and conversion data through a simple chat interface instead of running reports manually. For teams looking for the best PrestaShop admin AI tool to replace dashboards, this module has daily reporting, stock checks and customer data all in one place.

13.0 Conclusion

The Knowband PrestaShop Smart AI Admin Assistant brings AI-powered PrestaShop back office analytics to any store without requiring SQL knowledge, developer access, or third-party solutions. Ask in plain English, get answers from live store data, see the SQL behind every result, and configure the PrestaShop Admin Analytics AI Addon in minutes.

Predefined chips turn the daily store check into a one-minute task. Role-based access keeps the right data in front of the right staff. Query History keeps a complete audit trail of everything asked.

For support, custom requirements, or add-on development, contact the Knowband team directly.

Get the Knowband PrestaShop Smart Admin Assistant and start querying your store data from day one.

How to Run a Post-Purchase OpenCart Survey Without a Single Line of Code

Most unhappy customers say nothing. They finish their order, have a bad experience, and never come back. You never find out what went wrong. For an OpenCart store, this is a real problem; the platform gives you no built-in way to ask customers how they feel.

OpenCart comes with a basic contact form and a product review option. Neither one collects post-purchase feedback properly, and neither lets you ask specific questions after an order. Many store owners use external tools like Google Forms instead, but these send customers away from your store. Others just never ask at all.

A dedicated survey solution for OpenCart keeps everything inside your store. You build the form in the admin panel. The right OpenCart Survey Plugin takes care of form creation, display, email alerts, and spam blocking, all from one place.

Why an OpenCart Survey Plugin Fills a Gap That Native Features Cannot

The built-in OpenCart features were made for support requests and product ratings, not for understanding the full customer experience. A product review only tells you what someone thought about a product. A contact form only collects complaints. Neither one tells you about the checkout process, the delivery, or whether a first-time buyer will return.

Surveys placed on the order confirmation page get far more responses than survey links sent by email days later. On-page surveys see completion rates of 15 to 20 percent on average. Email survey links often get under 5 percent. Where you place the form matters more than what you ask.

Knowband’s OpenCart Form Builder Extension solves this from inside the back office, with no separate platform, no extra subscription, and no technical skills required.

How to Set Up Your First Survey Using an OpenCart Survey Plugin

Building a satisfaction survey takes five steps inside the Forms section:

Step 1: Create the form. Click Add New Form and give it a name. You can set a URL slug for the form page and share that link in emails or support tickets, or add it to your site manually. On the front end, a button can open the form as a pop-up on the same page instead.

Step 2: Pick a layout. One column works best for satisfaction surveys. It keeps questions in a clear, top-to-bottom order, which reduces the chance of customers leaving before finishing. Two or more columns are available for longer forms, where related fields make sense next to each other.

Step 3: Add your questions. A good starting point: a radio button for the overall satisfaction rating, a dropdown for the product or order type, and a text box for written comments. Add a file upload option if you want customers to send photos of any product issues.

Step 4: Set up email alerts. Each form sends its own email notification. Choose which inbox receives the alert when a customer submits. Use BCC to copy additional team members. Turn on the auto-responder so customers get a short confirmation straight away, even one line works.

Step 5: Set up the thank-you page. After submission, show a short message or redirect to another page. Keep it simple, just let the customer know their feedback was received.

Where to Place Your OpenCart Survey for the Highest Completion Rate

The Placements tab inside each form controls where the form appears on your site. This is where the OpenCart customer feedback plugin displays logic. Pick the page type: Home, Product, Checkout, Information, or Search. Then choose the position on that page: top of content, bottom of content, left column, right column, header, or footer. The form shows up on every page and position you select.

For a post-purchase survey, put it on the Checkout page at the bottom of the content area. This places the form on the order confirmation page, right after a customer completes their purchase. The experience is fresh, the customer is still on your site, and there is nothing to influence their buying decision because the order is already done.

The Settings tab lets you choose between an inline form and a pop-up that opens when a customer clicks a button. The floating button option keeps that button visible in the corner of the screen as the page scrolls, and the form stays easy to reach without getting in the way.

Keeping Your OpenCart Survey Results Spam-Free

Any form on a live website receives bot submissions over time. If spam fills your survey data, the results become unreliable. Spam protection in the OpenCart Form Builder Extension works at three levels.

Cloudflare Turnstile runs quietly in the background and blocks bots. Real customers see no puzzles or extra steps. The IP blocklist lets you block specific addresses or whole ranges using a wildcard. The email blocklist works the same way; one entry like *@mail.ru blocks every address from that domain.

Knowband includes pre-written patterns for the Spam Email Filter field, covering the most common spam sources. Copy them in, and they work immediately, no technical knowledge needed.

Turning Survey Responses Into an Email Marketing Sequence

The Synchronization tab inside each form connects Mailchimp integration and Brevo. Add your API key, choose the list, and every person who fills in the form gets added automatically. Brevo connects the same way.

A customer who gives a high rating is a good candidate for a review request. A customer who reports a problem can receive a follow-up message before they post a negative review anywhere else. Both of these can happen automatically from a single form submission, no manual work needed.

Every response appears in the Form Submissions panel with the date, the form name, what was filled in, and whether your team has already replied. You can reply directly from your admin panel. Exporting submissions regularly lets you track the customer satisfaction score over time and spot patterns across many responses.

Why the Right OpenCart Survey Plugin Pays Off Before Your Next Order Ships

The full setup, building the form, choosing placement, configuring email alerts, and turning on spam filtering, takes under 30 minutes the first time. No developer needed, no outside solutions to manage, no ongoing costs beyond the OpenCart Survey Plugin.

The OpenCart customer feedback plugin handles satisfaction surveys, product feedback, lead generation forms, support requests, and event sign-ups, all from one extension. Every day your store runs without a way to collect structured feedback is another day of useful customer data that you cannot get back.

PrestaShop Smart Admin Assistant: Top Use Cases for Store Owners in 2026

PrestaShop stores generate large volumes of operational data every day, from orders and customers to inventory, abandoned carts, revenue, and employee activity. While the data is readily available, getting to it means navigating multiple report pages, setting filters, and repeating the process for every single question. For admins checking the same figures daily, that time adds up fast. The Knowband PrestaShop Smart Admin Assistant sits inside your back office, and answers store questions in plain language, pulling results directly from your live database. No reports. No navigation. No SQL knowledge required. The module is launching soon. Here are the key use cases that show exactly how it changes day-to-day store management.

AI-Powered Natural Language Queries: No SQL Knowledge Required

Type a question in plain English, and the assistant returns the answer from your live store data within seconds. What makes this genuinely useful beyond convenience is the Show SQL Query feature. When enabled, the assistant surfaces the exact SQL it generated to produce the answer. A second setting, Allow SQL Edit and Re-run, lets the admin change that query and execute a revised version without writing SQL from scratch.

Before this, data requests involving multiple tables or custom filters sat in a developer backlog. Now, any admin can do that without any technical skills required.

Example: An admin wants to find customers who ordered at least three times but have not placed any order in the last 90 days, for a win-back campaign. They type: “Show me customers who ordered at least 3 times but have not placed any order in the last 90 days.”

The PrestaShop Smart Admin Assistant generates and runs this query:

SELECT

c.id_customer, c.firstname, c.lastname, c.email,

COUNT(o.id_order) AS total_orders,

MAX(o.date_add) AS last_order_date

FROM ps_customer c

JOIN ps_orders o ON c.id_customer = o.id_customer

GROUP BY c.id_customer

HAVING

COUNT(o.id_order) >= 3

AND MAX(o.date_add) < DATE_SUB(NOW(), INTERVAL 90 DAY)

ORDER BY last_order_date ASC;

The result is a table with customer name, email, total orders placed, and last order date. Every dormant repeat buyer in one view. The admin then adds a spend filter to focus on high-value customers first:

HAVING

COUNT(o.id_order) >= 3

AND MAX(o.date_add) < DATE_SUB(NOW(), INTERVAL 90 DAY)

AND SUM(o.total_paid) > 200  - admin adds this line

ORDER BY last_order_date ASC;

Re-run. Now, only customers who spent over 200 euros appear. Export from Query History. Win-back list ready. No developer, no phpMyAdmin, no waiting.

Database Views: Manage and Restrict AI Access to Store Data

The Database Views tab lets the admin choose which data domains the assistant is allowed to query. Available views include Orders, Customers, Products, Stock Availability, Shopping Carts, Cart Rules, Employees, Shipping Carriers, Product Combinations, and more.

Each view is a pre-built MySQL VIEW rather than a direct raw table query. This keeps things safe in two ways. The AI cannot modify any data because views are read-only. And because the joins are already built into each view, the answers come back more accurately than they would from querying raw tables directly.

Switch a view off, and the AI-powered admin assistant cannot reach that data, no matter the question. This is where PrestaShop back office analytics becomes properly controllable because the admin sets the limits, not the tool.

Example: A store owner wants the logistics team to use the PrestaShop Smart Admin Assistant for stock and order questions, but not customer personal data or employee records. Orders, Stock Availability, and Products stay on. Customers, Employees, and Customer Addresses go off. The logistics team can query what their role actually needs and nothing beyond that.

Role-Based Access Control: The Right Data for the Right Staff

The Access Control tab lets the store owner select which employee profiles can use the PrestaShop Smart Admin Assistant. Tick a profile, and it gets access. Leave all profiles unchecked, and access opens up for everyone. Tick only the ones that should have it, and the rest see nothing when they log in.

Example: A store with six admin accounts wants only the SuperAdmin and sales team to use the assistant. The store owner ticks those two profiles and leaves the rest unchecked. The translator and logistics staff log in, and the assistant is not visible to them at all. No code changes, no theme edits.

Predefined Chips: Daily Store Monitoring with One-Click

Predefined Chips are clickable question buttons that are present inside the chat widget. A predefined query runs instantly with a single click, eliminating the need for manual input.

The default set covers the most common daily checks: Orders Today, Revenue 30 Days, Abandoned Carts, Low Stock, Out of Stock, Active Customers, New Customers This Month, Cancelled Orders, Free Shipping Coupons, and No SKU Products. Every chip is editable, reorderable, and individually toggleable.

For stores running the same checks every morning, this alone saves significant time. The daily review that used to mean opening six different pages is now handled entirely through PrestaShop back office analytics in a single widget, in under a minute.

Example: A store manager checks four things every morning: today’s orders, this month’s revenue, products under five units in stock, and abandoned carts from the last 24 hours. All four are chips. The whole check is done in minutes.

Flexible AI Provider Selection: Choose OpenAI, Claude, or Gemini

The AI Provider tab gives the admin a choice between OpenAI, Anthropic Claude, and Google Gemini. Each requires the admin’s own API key and a model selection from that provider’s available tiers.

For Claude, the options are Haiku 4.5 for fast everyday queries, Sonnet 4.6 for a balance of speed and depth, and Opus 4.6 for complex multi-table work. OpenAI and Gemini follow the same tiered structure. Paying only for actual usage with no intermediary keeps running costs predictable regardless of store size. This is what makes the PrestaShop admin AI module genuinely accessible for stores that cannot commit to a fixed monthly AI subscription.

Example: Large-scale stores can use Haiku 4.5 for routine chip-based queries to maintain lower operational costs.. When the operations manager needs a detailed monthly breakdown across several joined tables, they switch to Sonnet 4.6 for that session and switch back after.

Voice Input, Widget Customisation, and Multilingual Support

Three features cover the remaining day-to-day usability of the PrestaShop Smart Store Management Addon.

Widget Layout puts every visual setting in one place: position, chatbot name, greeting message, avatar, width, height, and more. Changes reflect instantly in a live preview on the right. No CSS involved at any point.

Voice Input lets the admin ask questions out loud instead of typing. The Web Speech API built into the browser handles the transcription. For admins who move around, work on mobile, or simply find speaking faster than typing, this removes the last friction from getting a quick answer.

Chatbot Language gives the admin control over which language the PrestaShop Admin AI Module replies in. Setting it to Back-office Language ties the response to whatever language the admin panel is running in. Setting it to Custom Language lets the admin pick independently, which matters on multilingual teams where the back office language and the working language of individual staff members are different.

Example: A French-speaking operations manager works in a back office set to English for consistency across the team. Custom Language is set to French. The manager speaks a question using Voice Input and gets the answer back in French. Nothing in the back office configuration has changed.

Query History and Session Logs: A Full Audit Trail

Each question sent through the assistant lands in the Query History tab as a permanent record. The log captures the date, the employee, the question, the number of rows returned, response time in milliseconds, which AI provider ran it, the status, and the full SQL that executed.

Logs filter by date and status, and export to CSV or Excel. A retention setting purges entries older than a chosen number of days automatically, so the log table stays lean without manual cleanup. The Sessions tab keeps full conversation threads per employee for anyone who wants to review an earlier exchange or audit how the team is using the tool.

Example: A store owner gets an answer that looks off during the Monday morning check. They open Query History, pull up the exact query that ran, read the SQL, and spot that a database view was serving cached data. They hit Refresh Schema Now, rebuild the schema, and re-run with the correct result.

An AI smart admin assistant is most useful when it works from organised data Before you start asking it questions about sales or stock, it helps to know what your dashboard is already showing you. This guide to PrestaShop back office analytics explains which reports matter and how to read them without wasting time.

How the Knowband Smart Admin Assistant Improves Store Operations

Every feature covered here fills a gap that previously needed either a developer or a report that took too long to build. This PrestaShop admin AI module keeps the depth, the SQL still runs, the data is still live, and the controls are still precise, but the module removes the technical barrier between the admin and the information they need. For store owners spending more time in data analysis than on the business itself, the PrestaShop Smart Store Management Addon is the best practical fix.

The Knowband PrestaShop Smart Admin Assistant is launching next week. Stay tuned to find out more about the module and what it can do inside your back office.

PrestaShop Product Import Export Scheduler Pro – Complete User Guide

1.0 Introduction

Managing eCommerce manually is one of the most time-consuming parts of running an online store. Updating prices means opening products one by one. Migrating to a new store means starting from scratch. Syncing a supplier feed means downloading a file, converting it, and running an import that may or may not work cleanly.

The PrestaShop Product Import Export Scheduler Pro by Knowband replaces all of that. It is a complete PrestaShop Bulk Product Import Export Module that handles every direction of catalog data transfer, products and categories, in and out, in CSV, XLSX, JSON, and XML, from inside your PrestaShop admin panel without any coding, desktop software, or developer involvement.

What makes this PrestaShop Import Export Module different from basic transfer tools is the automation layer. Transfers are saved as named profiles. Profiles run on a schedule. Scheduled runs push files to FTP or SFTP servers automatically, send completion emails, and clean up after themselves.

Compatible with PrestaShop 1.7.x through 9.x.

1.1 Who Is This Module For

The PrestaShop Catalog Manager is built for:

Store owners managing medium to large catalogs of 100 to 50,000 SKUs.
Agencies managing multiple client PrestaShop stores.
International stores running multilingual catalogs.
Businesses syncing product or pricing data from supplier feeds on a schedule.
Any merchant who has struggled with PrestaShop’s native importer and needs a reliable combination and multi-language support.

2.0 Installation Guide

2.1 System Requirements

Before installing the module, confirm your environment meets the following:

PrestaShop version 1.7.x or 8.x or 9.x.x
PHP 7.2 or higher
MySQL 5.6 or higher

2.2 Uploading and Installing the Module

Step 1 – Upload the module: From your PrestaShop admin panel, go to Modules, then Module Manager, and click “Upload a Module” in the top right. Select the ZIP file downloaded from Knowband and click Open. PrestaShop uploads and extracts the files automatically.

Step 2 – Install: Once uploaded, click Install when prompted. After installation, you are redirected to the module configuration page.

Step 3 – Locate if needed: If the module does not appear automatically, search for Bulk Data Manager in the Module Manager search bar and click Configure.

2.3 Common Installation Issues

Upload fails: Your server upload size limit is too low. Ask your hosting provider to increase upload_max_filesize and post_max_size in the PHP settings to at least 32 MB.

Module not visible after install: Clear your PrestaShop cache under Advanced Parameters, then Performance, then search for the module again in Module Manager.

The configuration page appears broken: Clear your browser cache and the PrestaShop theme cache under Design, then Theme and Logo, then Advanced Settings.

3.0 Admin Panel Overview

Once installed, the PrestaShop Product Import Export Scheduler Pro has four main tabs in the admin panel:

General Settings: Preferences, template files, limits and speed, scheduled cleanup.
Export Profile: Create and manage export profiles.
Import Profile: Create and manage import profiles.
Transfer Logs: Full history of every import and export run.

4.0 General Settings

The General Settings tab has four sub-sections accessible from the left sidebar: Preferences, Template Files, Limits and Speed, and Scheduled Cleanup.

4.1 Preferences

This is the first screen you see inside the module.

Module Enable/Disable: Toggle the module on or off. When disabled, all scheduled CRON import and export tasks are paused.

Maximum Visible Columns: Sets how many columns are displayed at once in the import mapping table. Use the arrows to scroll through the remaining columns. Accepted range is 1 to 20. Default is 6.Maximum Visible Rows: Sets how many sample data rows are shown in the import mapping preview. This is for visual verification only and does not limit how many rows are imported. Accepted range is 1 to 50. Default is 10.

Import Batch Size: Sets how many rows are processed per AJAX request during import. Lower values reduce timeout risk on shared hosting environments. The accepted range is 10 to 500. Default is 100. For VPS or dedicated servers, increase this to 300 or higher to speed up large imports.

Click Save Settings to apply changes.

4.2 Template Files

This section provides ready-to-fill sample template files for every supported entity and format combination.

Two entities are available: Products and Categories. Each entity has four format buttons: CSV, JSON, XML, and XLSX.

Click the relevant button to download the template for that entity and format. Each template includes every column the PrestaShop Import Export Module recognises and uses safe placeholder data. Download a template, fill it in with your real product data, and import it back. Your upload file must follow the column layout shown in these templates.

4.3 Limits and Speed

Max Records Per Download: Sets the maximum number of records exported per file. Increase only if your server memory allows. Accepted range is 100 to 50,000. Default is 5,000.

Max Upload Size (MB): Sets the maximum import file size in MB. This works alongside your server’s PHP upload limit; whichever is lower takes effect. Accepted range is 1 to 200 MB. The default is 50 MB.

Click Save Settings to apply.

4.4 Scheduled Cleanup

This section generates the three cron URLs used to automate transfers and manages the automatic file cleanup.

Keep Files For (Days): Import files older than this many days are deleted automatically by the cleanup CRON. Accepted range is 1 to 30. Default is 7 days.

Cleanup CRON URL: Add this URL to your server’s cron manager to delete old temporary import files automatically. Example: run daily at 2 AM.

Export Profiles CRON URL: Add this URL to your server’s cron manager to run every export profile flagged as CRON-enabled. Pick whatever frequency suits your store, for example, daily at 3 AM.

Import Profiles CRON URL: Add this URL to your server’s cron manager to run every FTP-source import profile flagged as CRON-enabled. Upload-source profiles are manual-only and are skipped automatically. Example: daily at 4 AM.

Each URL has a Copy button for one-click copying. Paste the copied URL directly into your server crontab or into PrestaShop’s built-in Scheduled Tasks module.

Click Save Settings to apply.

5.0 Export Profiles

The Export tab lists all saved export profiles and allows you to create new ones. Each profile is shown with its ID, name, entity type, format, CRON status, and date added. Profiles can be edited using the Edit button on each row.

Click Add Export Profile to begin. The export wizard runs through three steps: Transfer Settings, Choose Fields, and Generate File.

5.1 Step 1 – Transfer Settings

Profile Name: A unique label that identifies this profile in the Export listing. Example: Weekly product feed.

Output File Label: Used as the base name of the generated file. The file extension is added automatically. Use letters, digits, hyphens, and underscores only. Example: products-daily.

Data Type: Select the store data you want to download, Products or Categories.

File Format: Select CSV, XLSX, XML, or JSON. CSV and XLSX open directly in spreadsheet apps. XML and JSON suit system integrations.

Language(s): Select one or more store languages. Translated fields such as name and description will be exported for each selected language. Select All Languages to include every active language in the store.

Date Range (optional): Filter by creation date. Leave blank to export all records.

Record Order (optional): Controls the row sequence in the downloaded file. Leave on default to use database order.

Export product combinations (variants): When enabled, each product row is followed by a row for each combination. This adds the columns row_type, parent_reference, combination_reference, attributes, and impact_price. Enable this when you need a full product catalog, including all variants for re-import or migration.

Scheduled Run – Enable CRON: When on, the CRON URL configured in Settings will run this profile automatically and store the generated file under the Transfer Logs tab.

Export Destination – Send Generated File To:

File System: Saves the file locally. Admin downloads it from the Transfer Logs page.
FTP / SFTP: Pushes the file to a remote server after each run. A local copy is also kept for fallback download.

If FTP / SFTP is selected, the following fields appear:

Transfer Protocol: Choose FTP, FTPS, or SFTP. FTPS is recommended for production. FTP is plaintext. FTPS adds TLS over the legacy protocol.

FTP Server: The server address, for example, ftp.example.com.

FTP Port: Default is 21 for FTP, 990 for FTPS, and 22 for SFTP. The port auto-updates when the protocol changes.

FTP Username and FTP Password: Credentials for the remote server. The password is stored encrypted at rest.

Absolute Path to a Folder: The remote folder where the file is dropped. The folder must already exist and be writable.

Passive Mode: Recommended for FTP/FTPS so firewalls do not block transfers.

Click Test Connection to verify your credentials before saving.

Output Style: Choose the CSV delimiter, Universal comma, Windows/Excel semicolon, or Tab-separated.

List Glue: Separator used for multi-value fields such as Tags and All Category Names. Options are Pipe, Slash, or Comma.

If File System is selected, you just need to add the Sheet Lable.

Narrow By (optional filters):

Narrow by Category: Limit the export to products in selected categories only.
Narrow by Brand: Limit the export to products from selected brands only.
Narrow by Supplier: Limit the export to products from selected suppliers only.
Price Window: Include only products within a specified price range (excluding tax). Leave blank for no price filter.

Click Next Step to proceed to field selection.

5.2 Step 2 – Choose Fields

This screen shows every available product or category column as a checklist. Required fields marked with an asterisk cannot be deselected.

Click Select All to include every column.
Click Deselect All to clear all optional selections.
Click Reset to Defaults to restore the recommended default column set.
Drag rows to reorder the column sequence in the output file.

Available product fields include: ID, Reference, Name, Active, Product Type, Condition, Visibility, Available For Order, Show Price, Online Only, Available Date, Brand ID, Brand Name, Supplier ID, Supplier Name, Tags, Date Created, Short Description, Description, Weight, Width, Height, Depth, EAN-13, UPC, ISBN, MPN, Meta Title, Meta Description, URL Key, Cover Image URL, All Image URLs, Default Category ID, Default Category Name, All Category IDs, All Category Names, Price, Wholesale Price, Unit Price, Minimum Quantity, Low Stock Alert, Low Stock Threshold, Out of Stock Behaviour, and more.

Click Preview Data to see the first five rows of the export based on your current selection. Click Save Profile to save without downloading. Click Next Step to proceed to file generation.

5.3 Step 3 – Generate File

A Download Summary panel on the right confirms your settings: Data Type, File Format, File Label, and the number of Fields selected.

Click Build and Download to generate the export file immediately. The file is built and downloaded to your browser or pushed to the configured FTP/SFTP destination. The run is recorded in the Transfer Logs tab.

6.0 Import Profiles

The Import tab lists all saved import profiles. Each profile is shown with its ID, name, entity type, format, source type (Upload or FTP), CRON status, and date added.

Click Add Import Profile to begin. The import wizard runs through three steps: Source Settings, Map Columns, and Run Import.

6.1 Step 1 – Source Settings

Profile Name: A unique label that identifies this profile in the Import listing. Example: Daily product feed.

Data Type: Choose what type of data the source file contains: Products or Categories.

File Format: Select CSV, XLSX, JSON, or XML.

Output Style: Choose the CSV delimiter that matches the file being imported: Universal comma, Windows/Excel semicolon, or Tab-separated.

List Glue: Must match the glue used when the file was exported. This affects multi-value fields such as Tags, Categories, and Image URLs.

Language: Default language for rows that do not specify their language in a lang column (CSV/XLSX) or as a per-language tag (JSON/XML).

Import Options:

Update existing records when ID (or reference) matches: When checked, the module updates an existing product instead of creating a duplicate when a matching ID or reference is found in the file. This is the standard setting for all regular updates.
Force IDs from the file (use the same ID number): When checked, the module assigns the exact product ID from the file to the new record. Use only when migrating between stores where preserving the original ID is required.

Pick Source:

Upload File: One-time manual import, upload a file from your computer. Max upload size is 50 MB. Allowed formats: CSV, XLSX, JSON, XML.
FTP / SFTP: Pull the file from a remote server. This option is required for CRON-driven automated runs.

If FTP / SFTP is selected, the following fields appear:

Transfer Protocol: FTP, FTPS, or SFTP.

Server: The FTP server address.

Port: Default is 21 (FTP), 990 (FTPS), 22 (SFTP). Auto-updates when the protocol changes.

Username and Password: Credentials for the remote server. Password is stored encrypted at rest.

Remote File Path: Absolute path to the source file on the remote server. The file must exist at this exact path each time the cron fires. Example: /home/feed/products.xml.

Passive Mode: Recommended for FTP/FTPS so firewalls do not block transfers. Ignored for SFTP.

Click Test Connection to verify your FTP/SFTP credentials before saving.

Scheduling:

CRON: When on, the CRON URL in Settings fetches the file via FTP/SFTP and runs the import without manual intervention. CRON is only available for FTP source profiles.

Email Notification: When on, the admin email receives a one-line summary after each CRON run, the same template for success or failure.

Click Save Profile to save your settings, then click Next Step to proceed to column mapping.

If Upload File is selected, you just need to upload the file from your device.

6.2 Step 2 – Map Columns

This screen shows the column mapping interface.

The instruction at the top reads: Match each column from your file (top row) to the right PrestaShop field. Required fields are marked with an asterisk.

The module auto-matches columns wherever possible. A confirmation message at the top shows how many columns were auto-matched, for example: 47 of 47 columns auto-matched. Review the mapping below and adjust if needed.

Each column from your import file appears as a dropdown at the top of its column. The rows below show the actual data values from your file for visual verification. Use the search box to find a specific column by name. Navigate through all columns using the pagination arrows (for example, 1-6 / 47).

Assign each column header from your file to the correct PrestaShop field using the dropdown. Leave columns set to the auto-matched field if the mapping is correct. If a required field is not mapped, the module blocks the import and shows a warning before proceeding.

Click Save Profile to save the mapping. Click Next Step to proceed to the final step.

6.3 Step 3 – Run Import

The confirmation message reads: Mapping confirmed. Click below to start importing your data.

Click Save Profile to store the profile for future use without running the import now.

Click Start Import to begin. The import runs in batches as configured in General Settings. When complete, the Transfer Logs tab records the result, including total records, successful records, and any failed records with row-level error detail.

7.0 Transfer Logs

The Transfer Logs tab shows the full history of every import and export run through the PrestaShop Product Import Export Scheduler Pro. The tab heading in the module is Transfer History.

Each row in the log shows:

ID: The run identifier.
Type: Import or Export.
Entity: Products or Categories.
Format: CSV, XLSX, JSON, or XML.
Status: Completed, completed with failures, or failed. Partial runs show the record count as X / Y (Z failed) in red.
Records: Total records processed. For partial failures, the count shows how many succeeded and how many failed.
File: The filename of the generated or imported file. For export runs, the filename is a clickable link to re-download the file directly.
Date: The date and time the run completed.

Click Log on any row to view the full details of that run, including row-level error messages for any failed records. Fix only the affected rows in the source file and re-import those rows. The rest of the catalog remains untouched.

Additionally, exported files can be re-downloaded from the Transfer Logs section. In the File column, click the export file link to download it again. The files remain available for re-download until they are removed by the Scheduled Cleanup cron after the configured retention period.

8.0 Frequently Asked Questions

Question: What is the PrestaShop Product Import Export Scheduler Pro?

Answer: PrestaShop Bulk Product Import Export Module lets merchants import and export products and categories using CSV, XLSX, JSON, and XML files. It includes reusable profiles, column mapping with validation, FTP and SFTP file transfer, cron-based scheduling, email notifications, and transfer logs, all managed from the PrestaShop admin panel. Compatible with PrestaShop 1.7 through 9.x.

Question: How do I import products in PrestaShop using a CSV file?

Answer: Go to the Import tab and click Add Import Profile. Set the data type to Products, select CSV as the file format, upload your CSV file under Pick Source, and click Next Step. On the Map Columns screen, the module auto-matches columns where possible, reviews the mapping, adjusts if needed, and clicks Next Step. Click Start Import to run. Sample CSV templates are available from the Template Files section in General Settings.

Question: Can I import and export PrestaShop product combinations?

Answer: Yes. You can export the combination of the product variants by enabling Export Product Combinations (Variants) in the export profile Transfer Settings. Each product row is followed by one row per combination with attributes in a human-readable format. On re-import, the module creates missing attribute values and groups automatically. Full round-trip combination handling is supported, export from one store and import to another, cleanly.

Question: How do I automate PrestaShop product imports using cron jobs?

Answer: Create an import profile with FTP or SFTP as the source, enable CRON in the Scheduling section, and save the profile. Go to General Settings, then Scheduled Cleanup, and copy the Import Profiles CRON URL. Paste it into your server crontab or PrestaShop’s Scheduled Tasks module and set the interval. The profile runs automatically at every tick without any manual involvement.

Question: How do I migrate products from one PrestaShop store to another?

Answer: You can migrate a product from one prestashop store to another using the Knowband Prestashop Export/Import Scheduler Pro. Using import feature you can import all the prestashop product and categories in CSV, JSON, XML or XLSX format.

Question: What happens if an import fails or has errors?

Answer: The PrestaShop Catalog Manager does not fail silently. Every run creates a record in the Transfer Logs tab. Partial failures show the record count as X / Y with the number failed highlighted. Click the Log button on any row to see row-level error detail. Fix the affected rows in the source file and re-import only those rows. A completion email is sent for scheduled CRON runs, so the admin is notified without logging in.

Question: Is this compatible with the latest PrestaShop version?

Answer: Yes. The PrestaShop Product Import Export Scheduler Pro is compatible with PrestaShop 1.7. x through 9.x. Refer to the module product page for the latest compatibility information.

9.0 Conclusion

The PrestaShop Product Import Export Scheduler Pro by Knowband is a complete solution for catalog data management in PrestaShop. Four file formats, reusable profiles, FTP & SFTP with connection testing, full combination round-trip support, multi-language preservation, column mapping validation, row-level error logs, dated backup history, and automatic file cleanup, all from one PrestaShop Import Export Module, all from the admin panel, with no developer required.

For support, custom requirements, or PrestaShop addon development services, contact the Knowband team directly.

Get the PrestaShop Product Import Export Scheduler Pro and start running automated catalog transfers from day one.

One Page Super Checkout: A Simple Way to Reduce Abandonment and Increase Sales

A lot of OpenCart & Prestashop shops are losing their customers at checkout. And the reason behind it is that the general checkout process consists of an excessive number of steps and multiple fields to fill out. Research indicates that over 65% of online customers abandon the site during the checkout process when they find the process to be time-consuming or difficult to comprehend. When customers get frustrated, they stop buying, and the store loses an easy sale.

Hence, the easiest way to solve this issue is by using the OpenCart One Page Super Checkout by Knowband. This addon integrates all the checkout elements, including cart details, address, shipping, payment, and the order summary on a single page. With this, customers can make orders within seconds without switching several pages.

This smooth and fast experience reduces the number of drop-offs and increases conversions. With this addon, store owners can finally offer a checkout that customers enjoy using.

By integrating the Prestashop responsive one-step checkout addon, merchants can reduce cart abandonment and increase conversions. This powerful Prestashop fast checkout addon supports major payment gateways such as PayPal, Stripe, Authorize.Net, Braintree, Amazon Pay, Apple Pay, Google Pay, Square, Klarna, Worldpay, Mollie, Skrill, Neteller, Payoneer, and 2Checkout, providing shoppers with a variety of secure and convenient ways to pay. Offering multiple trusted payment methods helps build customer confidence and ensures more orders are completed successfully.

Benefits of the OpenCart One Page Checkout Extension

Quick Checkout, Increased Conversions.

Knowband’s OpenCart One Page Supercheckout Plugin has everything on a single page. Customers can fill in the details in a short time and complete the purchase without getting lost. Thus, once the checkout is made quicker, the conversion rate automatically increases.

Lower Cart Abandonment

Moreover, the PrestaShop Quick Checkout Module eliminates all those unnecessary steps that frustrate customers. No more loading new pages. No more long forms. This simple and clean screen keeps the customers on track and reduces the number of abandonments.

Better Mobile Shopping Experience

Most users today make purchases on mobile phones. The Responsive One Page Checkout Plugin for OpenCart is compatible with all screens, including mobiles, tablets, and desktops. Hence, customers can place their orders with ease, no matter the device they are using.

Fast Orders with Guest Checkout

Generally, when people are forced to create an account during checkout, they leave instantly. Using the Knowband Prestashop One Step Checkout Addon, customers can easily check out as guests.

Easy Setup With No Coding

The OpenCart Simplified Checkout Plugin does not need technical skills. The extension can easily be installed by store owners, and they can configure the entire extension in just minutes.

Integrate Your PrestaShop Store with AI Chat Support

Boost engagement and conversions with instant AI replies, multilingual support, and real-time order updates.

SHOP NOW

Features of the PrestaShop One Page Supercheckout Addon

Google Auto-Fill Support

The checkout form includes auto-fill to help customers enter their address faster. Thus, this reduces typing time and prevents mistakes, leading to a smoother buying process.

Social Login Support

Moreover, with the PrestaShop One Page Checkout Module by Knowband, customers can sign in using Facebook, PayPal, and Google. Thus, this saves them from creating new accounts and speeds up the purchase process.

Drag-and-Drop Field Customization

Store owners can fully customize the checkout layout. The OpenCart fast checkout extension allows adding, removing, and rearranging fields with simple drag-and-drop options. Hence, you can shape your checkout page based on your store’s needs.

Support for All Payment & Shipping Methods

The plugin works smoothly with all payment or shipping methods added to the store. In addition, admins can also customize how these methods appear by adding logos and short descriptions.

Cart Section Control

Moreover, store owners can choose what to display in the cart section on the checkout page. For example, they can show stock details or price information only to registered users while hiding them from guest users.

Responsive and Clean Layout

Last but not least, the OpenCart one-step checkout extension by Knowband provides a clean and organized layout that is easy to understand. This helps customers complete their order faster without getting confused.

Conclusion

Knowband has developed the Prestashop One Page Super Checkout Module, which is one of the strongest upgrades that any opencart & prestashop store can make in 2026. The module makes a slow, multi-step checkout process of checkout process fast and friendly for the customer. This module consists of great features such as social login, checking out as a guest, auto fill, drag and drop customization, and more.

This enhanced experience results in a reduction in the number of unfinished orders, increases successful orders, and improves customer satisfaction. Thus, Knowband’s OpenCart One Page Supercheckout Extension is the best option that you can invest in case you want to expand your opencart and prestashop store by reducing checkout friction and speeding up sales.

For more information, you can refer to the https://www.onepagesupercheckout.com/, here you can find the detailed information of Knowband’s One Page Supercheckout, which is available for Prestashop, Opencart & Magento 2.

Must Read

Gear Up for 2026 with the Next-Gen Knowband AI Content Generator Plugin