How to Add a Size Guide to Your PrestaShop Store

PrestaShop still powers a large share of independent European fashion stores, yet its default toolkit has no native size guide feature. Merchants either hardcode a single image into every product description or skip the guide entirely — and both choices quietly inflate returns. Getting this right matters more now that return costs and compliance rules are both tightening.

Why PrestaShop Merchants Default to a Broken Pattern

Ask ten PrestaShop store owners how they show sizing information and most will describe the same workaround: a JPEG of a size chart, pasted into the product description or a CMS page, linked from a text sentence like "see our size guide." It works, technically. It also breaks the moment a store sells more than one category of apparel, because a single chart can't represent a fitted dress, a relaxed hoodie, and a pair of jeans with the same numbers.

This matters because apparel and footwear already carry return rates well above the retail average, with shoes consistently among the highest-return categories, per industry reporting. A generic chart pasted into every product page doesn't just look dated — it actively under-serves shoppers trying to size a specific garment type, and that ambiguity shows up later as a return.

Adding a Size Guide via Module vs. CMS Block

PrestaShop gives you two realistic starting points, and picking the wrong one early creates cleanup work later.

CMS block approach. Create a page under Preferences > CMS, write the chart as an HTML table, and link to it from a "Size Guide" tab or a footer link. This is the fastest path and requires no module installation. Its limitation is structural: a CMS page is one static document, so it cannot be different per category, per product, or per brand without you manually duplicating pages and links.

Module approach. A dedicated size-guide module hooks into displayProductActions or a similar product-page hook and renders the chart contextually — meaning it can check the product's category or a custom attribute and swap in the right table automatically. This is more setup work upfront but scales cleanly as the catalog grows past one or two product types.

If your catalog is genuinely one product type — say, only t-shirts — the CMS block is defensible. The moment a store carries outerwear, footwear, and fitted basics under one roof, the module route (or a purpose-built widget) stops being optional.

Supporting Per-Category Charts Without Duplicating Work

Here's the operational problem most PrestaShop stores hit around their second or third apparel category: someone has to maintain N different chart images or tables, keep them in sync across languages if the store is multilingual, and remember to attach the right one to each new product. That's a manual process with no guardrail against error — a jeans chart accidentally linked to a jacket product is an easy, silent mistake.

A more durable setup ties the chart to a product attribute or category ID rather than to a hardcoded link per product. Practically, that means:

• Group products by fit type (fitted, regular, oversized) rather than just category name, since fit — not garment type — is what actually determines which measurements matter.
• Store chart data as structured rows (bust, waist, hip, or foot length) rather than a flat image, so it can be reformatted, translated, or reused in the interactive step below.
• Version the chart data separately from the product description, so updating a size chart doesn't require editing every product's text.

This groundwork pays off directly when you move to an interactive tool, because most size-recommendation systems expect exactly this kind of structured, per-category data rather than a JPEG.

Upgrading From a Static Chart to an Interactive Guide

A static chart answers "what are the measurements for a size M jacket." It does not answer the question shoppers actually have, which is "what size should I buy." That gap is where bracketing behavior starts — buying two sizes with the intent to return one — a habit reported by roughly half of Gen Z shoppers, per NRF survey data. A chart that requires a shopper to self-measure with a tape measure and cross-reference a table is friction most people quietly abandon in favor of guessing.

An interactive guide instead asks a few quick inputs (height, weight, fit preference, or existing brand sizes the shopper already owns) and returns a direct size recommendation for that specific product. The difference isn't cosmetic — it changes the decision from "here's data, you interpret it" to "here's your size." For PrestaShop specifically, this typically means embedding a widget via a module or a script tag on the product template, rather than rebuilding the CMS-page pattern with more fields.

Where YourSizer Fits

YourSizer integrates into PrestaShop as a size and virtual try-on widget that sits on the product page next to (or replacing) a static chart. Instead of maintaining separate chart images per category, brands feed in per-category or per-fit measurement data once, and the widget handles the category-specific logic — a jeans product asks different questions than a jacket product, without a developer building that branching manually.

For stores mid-migration from a CMS-block chart, YourSizer can run alongside the existing chart initially, so there's no hard cutover risk. The tool doesn't fabricate sizing where none exists — it works from the same measurement data a well-organized per-category chart already requires, which is why the groundwork described above (attribute-based grouping, structured chart data) directly reduces integration time.

Frequently Asked Questions

Does PrestaShop have a built-in size guide feature?

No. PrestaShop's core does not ship a native size-guide block or field type. Merchants rely on CMS pages, product description HTML, or third-party modules to add one, which is why the pattern varies so widely between PrestaShop stores compared to platforms with a built-in sizing field.

Can one size chart work for an entire PrestaShop catalog?

Only if the catalog is genuinely uniform in fit and garment type, which is rare beyond single-category stores. A chart built for a fitted dress will mislead a shopper buying a relaxed hoodie, since the reference points (bust vs. chest, for example) and ease allowances differ by garment. Most multi-category apparel stores need at least a small set of charts grouped by fit type, not one universal table.

Is a module always better than a CMS block for size guides?

Not always — a CMS block is a reasonable choice for a small, single-category store where setup speed matters more than scalability. The tradeoff shows up as the catalog grows: a module or widget-based approach avoids the duplicated-page maintenance burden that a CMS-only setup accumulates over time, and it's easier to later attach interactive sizing logic to a module hook than to a static page.

Conclusion

A size guide on PrestaShop starts as a small decision — CMS block or module — but the real cost shows up months later, in how much manual work it takes to keep charts accurate across a growing catalog. Structuring chart data by fit type from the start, rather than by product name, is what makes both a clean per-category setup and a future move to an interactive tool straightforward instead of a rebuild. For related fixes, see how to add a size recommendation widget to Shopify for the equivalent pattern on another platform, and how to read a size chart correctly for the measurement logic that any chart, static or interactive, ultimately depends on.