Agencies: what PrestaShop's native AI assistant changes

The arrival of AskAI, PrestaShop's native AI assistant, will get your clients talking. Some will ask why they should pay you if PrestaShop already has AI. The answer is a distinction of trade rather than a defence. Here's how to frame it, without inventing anything about what AskAI does or doesn't do.

An assistant lives in one store; an agency runs a portfolio

According to the announcement, AskAI is pre-installed in the back office of a store and used there in natural language. Excellent for the merchant running their store. But an agency doesn't work one store: it runs ten, thirty, fifty. Fifty assistants in fifty back offices is not a production tool, it is the same manual gesture fifty times over.

Publium takes the problem from the other end: one account, the whole portfolio, in a shared dashboard. That is the logic of our agency page and of managing SEO across several stores.

The question of access

A detail that matters day to day: using AskAI in a client's store means being in their back office, and the listing notes that administrator access may be required to connect the MCP Server. Multiplied across a portfolio, that means asking for, storing and rotating client credentials.

Publium's model avoids that: installing the module at the client is the only intervention on their store; after that, everything goes through the module's signed API. No back-office password to exchange, which your clients value as much as you do.

The technical prerequisite isn't neutral

The MCP Server requires PrestaShop 8.2+ and PHP 8.1+, plus ps_mbo, ps_accounts and ps_eventbus. In a real agency portfolio, some stores aren't there: older versions, migrations pending. Those stores can't use AskAI today; Publium's module targets a wider base. The native assistant doesn't cover all of your clients, whereas you do.

What you sell, and what an assistant doesn't produce

An agency engagement is sold on deliverables and regularity, not on "you can ask an AI". What Publium lets you bill and sustain:

• A blog pace per client: articles generated, reviewed, published and dated, with links to product pages built into the brief. That is the heart of industrializing your clients' content production.
• A differentiated catalog: supplier descriptions rewritten in batches, with SEO tags, deliverable in days rather than months.
• Steered SEO: Search Console per store, prioritized opportunities, dated actions.
• Proof: results reports and approval links to send the client, without them needing an account.

None of that is in AskAI's announced scope, which stays centered on on-demand management of the catalog, orders and customers inside one store.

The line to take with a client

Reuse it as is if you like: "AskAI is a useful assistant in your back office for one-off tasks. Our job is different: producing your content at the agreed pace, steering your ranking over time, and bringing you the proof every month, across all your stores rather than one." The nuance between the two is developed in AI assistant or sustained production, and the feature-by-feature comparison in Publium and AskAI, side by side.

Getting started

Pick one client whose catalog is well stocked and whose blog is dead, the most common case. Install the module, connect, and produce a first month: 4 articles plus the 20 priority product pages. Measure at 90 days, then industrialize across the rest of the portfolio.

To scope it on your own portfolio, let's talk, or just ask your question.