PrestaShop Theme Selection & Fit Assessment evaluates a proposed theme against your catalogue, installed modules and essential requirements before purchase. You name the candidates and priorities; an expert reviews their fit with your store.
A polished demo does not show how your real catalogue and customisations will behave. The assessment checks loading weight, module display positions, update risks and whether a child theme protects your changes.
The listed scope covers up to three candidates, scored consistently against your requirements. Your client panel receives a PDF within 3 to 5 working days for one candidate or 5 to 10 for a shortlist, with 14 days of email clarification. Theme licences, installation, migration, design and fixes are separate.
Documented fit and maintenance risks guide the purchase before you commit to a theme for your store.
What does the PrestaShop Theme Selection & Fit Assessment cover?
PrestaShop Theme Selection & Fit Assessment turns an expensive, hard-to-undo theme decision into a scored, store-specific verdict.
- The demo illusion: why a demo may not reveal migration problems.
- Speed under your conditions: weight, delayed first display, page-experience impact.
- Fit with what you run: module display positions, override exposure, child-theme viability.
- Durability: author activity, update signals, readiness for later versions.
- The verdict: one candidate or a shortlist of up to three, scored against your must-haves.
- The deliverable: ranked findings on a set timeline, and what follows the decision.

Why is the vendor demo unable to answer the question?
Because the demo is not your store. A demo may run on a clean installation with ten sample products, studio photography and no third-party modules. Under those conditions, a theme may appear faster and simpler to use than in your store. Your store brings a real catalogue, real images, a set of installed modules and years of customisation, and that is the ground on which the theme will actually live.
The costly discoveries, the missing display positions, the override pile, the sluggish product page, normally surface after purchase and migration. This review exists to surface them before.

How fast will it really be on my store?
Speed is measured under realistic conditions, not on the empty demo. The review weighs what the theme loads, identifies the files that hold up the first display, and estimates the likely effect on Google's page-experience measurements for a store shaped like yours, candidate by candidate.
The consequence is a performance bill known before purchase. A theme that would cost you a second on every product page is a fact in the report, not a discovery in next quarter's rankings.

Will it work with my modules and my customisations?
Fit is checked against your actual installation. The modules you run need specific display positions in a theme; the review verifies the candidate provides them. Override-heavy construction is flagged, because it is the pattern that lets a routine update overwrite your custom work. And the review answers whether a clean child theme carries your changes through future releases, which decides how expensive every later update will be.
This is the difference between an opinion about a theme and a verdict about a theme on your store. The same theme is a good buy for one merchant and a trap for another; the review tells you which one you are.

Which candidate wins, and by how much?
Durability joins the technical findings: how active the author is, how regularly the theme is updated, and how ready it is for later platform versions. Everything is scored against the must-have requirements you state, so the verdict reflects your priorities, not a generic checklist.
With a shortlist, every candidate passes the identical examination and the scores land in one comparison, so the decision stops being a coin toss between three demos and becomes a ranked answer with reasons attached. The listed price covers a shortlist of up to three candidates; a larger field is quoted separately.

What do I receive, and who is this for?
A report whose findings are ranked before they are described, so the first page tells you the decision and the risks in order, with a like-for-like score for each candidate and a performance estimate under your conditions. It arrives as a PDF and stays in your client panel, with child-theme and multistore considerations covered for stores that need them, within 3 to 5 working days for a single candidate and 5 to 10 working days for a shortlist. A 14-day email window covers clarification questions.
The assessment happens before any money reaches a theme author: the licence stays yours to purchase once the verdict is in. Installing or migrating to the winner is the separate PrestaShop Theme Installation & Setup Service, which picks up exactly where the assessment stops, with the findings on child-theme viability and module positions feeding straight into the setup. Design work, customisation and fixes to your current theme sit outside the review.
It serves merchants about to buy a theme, migrate to one or commission a redesign, owners whose current theme has become a maintenance trap and who want the next one to be safe, and agencies wanting an independent technical read before recommending a theme to a client.

-
ReferenceSVC-THEME-FIT
-
Service typeAdvisory
-
Turnaround2–4 business days
-
DeliverableTheme scorecard + recommended/acceptable/avoid verdict + risks list
-
Access neededTheme/shortlist & requirements; admin optional (installed themes only)
-
PrestaShop versions1.6 / 1.7 / 8 / 9
-
ImplementationQuoted separately
-
NDA / DPAAvailable on request
-
FocusCompatibility, child-theme safety, performance, accessibility (EAA/WCAG)
A pre-purchase or pre-migration scorecard for compatibility, child-theme safety, performance and accessibility.
We review candidate themes against your exact PrestaShop version, must-have modules and real requirements, not the vendor's empty demo. You get a recommended, acceptable or avoid verdict with the risks that would bite after purchase or migration.
Version & customisation safety
Whether the theme can survive your PrestaShop version and future updates.
- PrestaShop 1.6 / 1.7 / 8 / 9 support and upgrade path
- Maintenance activity, release cadence and known version issues
- Child-theme strategy and override volume that could wipe changes or collide later
Module, hook & business-fit coverage
Whether your real modules and flows can render where they need to.
- Hook coverage for trust, delivery, upsell, B2B and checkout modules
- Multistore, multilingual, group-price and tax-display behaviour
- Layout positions where buying decisions are actually made
Performance, UX & accessibility
The costs a good-looking demo can hide.
- Asset weight, render-blocking CSS/JS and Core Web Vitals headroom
- Mobile and checkout journey quality under realistic conditions
- EAA/WCAG basics: contrast, focus, keyboard path and screen-reader landmarks
How it works
-
Intake Day 1You send theme links, documentation, must-haves, PrestaShop version and key modules.
-
Technical review Days 1-3We assess demos, docs and installed signals against compatibility, performance, UX, accessibility and maintenance.
-
Scoring Day 3Each candidate is scored against weighted criteria and your stated must-haves.
-
Handover Final dayYou receive the scorecard, side-by-side comparison, risks and next-step guidance.
How the recommendation is bounded
This is a decision document, not an installation or build. The value is a defensible verdict before you spend the larger budget.
The verdict is explicit enough to prevent a bad purchase
A sample scorecard can read: Theme B - PS 1.7 only / child-safe partial / heavy assets / weak accessibility - Avoid. Red flags include missing hooks your modules depend on, no release in 12+ months, no PrestaShop 8/9 support, heavy overrides, or a render-blocking payload no cache can fully rescue.
Related services
Is accessibility really necessary?
Increasingly yes. EAA/WCAG failures are a legal and commercial risk, especially around contrast, focus and keyboard paths.
Will this tell me if the theme is fast?
It flags performance risk and asset/CWV headroom. Full application profiling belongs in the Performance Audit.
Do you need admin access?
Only for a theme already installed on your store; a candidate review needs demo links, docs and requirements.
Can you review a theme before I buy it?
Yes. We assess demo, documentation and technical signals before you commit to purchase or migration.
Do you recommend a specific theme?
We compare the shortlist against your requirements and can say none of them are suitable if that is the honest verdict.
Can you review a theme I've already bought or built on?
Yes. We can review a theme you have already bought or already built on, and apply exactly the same scored, requirements-based verdict to what you are running today. The review isn't only for greenfield theme selection. It's just as useful when you have inherited a theme, taken over a store, or started to suspect your current theme is holding you back.
What the review of an existing theme tells you
- Whether it's worth keeping. An honest read on whether your current theme is a solid foundation to keep investing in, or a long-term liability.
- What its risks are, performance debt slowing your pages, fragile or absent child-theme support that makes safe customisation hard, accessibility gaps against EAA / WCAG, and whether the codebase is still actively maintained for current PrestaShop.
- Whether a child theme or a switch is the better path, if the bones are good, we can confirm that customising via a proper child theme keeps you update-safe; if not, we tell you plainly that a switch is the lower-risk route.
Why this matters: many merchants only discover a theme's real limitations after they have built content, configured modules and customised templates on top of it. Reviewing what you already run lets you make that call deliberately rather than reactively, before you sink more work into a shaky base, or conversely before you needlessly throw away a theme that just needs a sensible child-theme approach.
This is well suited to stores that didn't choose their current theme, that are weighing a redesign, or that simply want an independent technical opinion on the theme they already depend on, with the risks laid out clearly so the decision stays yours.
What does the Theme Suitability Review check?
The Theme Suitability Review measures a theme, or your shortlist of candidates, against your real requirements, not the polished marketing screenshots on a demo page. A theme that looks fast and flexible with twelve sample products can behave very differently once it is carrying your full catalogue, your modules and your traffic. We close that gap before you commit.
What we actually inspect
- Performance under real conditions, how the theme renders on a realistic catalogue size rather than a stripped-down demo, including the weight of its CSS/JS, how it handles category and product listings, and where it is likely to drag Core Web Vitals down.
- Child-theme-ability. Whether you can customise the theme through a proper child theme and still take upstream updates safely, or whether every change means editing core theme files that the next update will overwrite.
- B2B support, how well it copes with requirements such as customer groups, specific pricing, tax display and account-driven catalogues if your store is not purely B2C.
- Accessibility, alignment with EAA / WCAG expectations, which matters both legally and for usability across your audience.
- Mobile quality, genuine responsive behaviour and touch usability, not just a layout that technically reflows.
- Update cadence. Whether the theme is actively maintained for current PrestaShop, or an abandoned codebase that will quietly become a liability.
Why it matters: the theme is one of the hardest things to change after launch. It touches every page, every conversion path and your long-term maintenance cost. Choosing on looks alone is how stores end up locked into performance debt or a dead codebase. This review surfaces those risks while you still have a free choice.
It suits merchants comparing themes before a build or replatform, agencies vetting a client's preferred theme, and anyone who wants an independent, technical read on a PrestaShop theme rather than a sales pitch.
What do I receive from the Theme Suitability Review?
You receive a scored verdict on each theme against your specific requirements, with the trade-offs and risks made explicit before you commit. Not discovered weeks after launch when they are expensive to undo.
What the deliverable looks like
- A clear assessment of each theme (or each candidate on your shortlist) measured against the criteria that matter to your store, so you can compare like for like rather than on first impressions.
- The risks named plainly. Performance debt that will hurt page speed and Core Web Vitals, poor or fragile child-theme support that blocks safe customisation, accessibility gaps against EAA / WCAG, or an abandoned codebase that won't keep pace with PrestaShop.
- A practical read on whether a theme is a sound foundation, a manageable compromise, or something to avoid.
Why this is valuable: the most damaging theme problems are the ones you can't see in a demo. A theme can look perfect and still be impossible to customise without breaking updates, or slow once your real catalogue is loaded, or quietly unmaintained. By the time those surface in production, you have usually already invested in content, configuration and customisation on top of it.
The point of the review is informed choice. You decide with eyes open, keep, customise, or switch, and you go into the decision knowing exactly what you are taking on. We make no promises about a particular outcome; we give you the honest technical picture so the decision is yours to make on solid ground. It is the difference between choosing a theme and inheriting its problems.
Easy return - no questions asked
Install, set up and take profit
Priority Help & Satisfaction Over Sales
Who builds and maintains this module
Built and maintained by David Miller and mypresta.rocks. David Miller has worked with PrestaShop since 2013, and the company behind this shop has been registered since 3 December 2018. Every module in this catalogue is our own work, so your questions to support reach the people who wrote the code. The changelog on this page lists every update with its date.
More modules
Compliance & Legal
PHP2Shell: what PrestaShop shops should do about CVE-2026-109618 and CVE-2026-109619, even when they cannot upgrade
News & Updates
What's new at mypresta.rocks: September 2026
News & Updates
What's new at mypresta.rocks: August 2026
News & Updates
PrestaShop 9.2 native One Page Checkout: what it does and when you need more
News & Updates
Introducing Expert Services: PrestaShop audits before you buy another module
News & Updates

















