# Product combination bugs on PrestaShop (pricing, photos, display)

> A purchase price that doesn’t follow the right size, photos that need entering one by one for each colour, a selector that displays badly on mobile: a PrestaShop combination (a mix of attributes, say a size and a colour) is a record in its own right, with its own price, its own stock and its own photos. Most of these "bugs" start here.

- Source canonique : [https://allaux.fr/en/prestashop/problemes/declinaisons-produits-bugs](https://allaux.fr/en/prestashop/problemes/declinaisons-produits-bugs)
- Langue : EN
- Dernière mise à jour : 2026-09-30

## Direct answer

> Open the product in Catalogue > Products, Combinations tab: price, stock and images are set on each combination, never on the parent product. The lowest-priced combination is what the front office shows as the starting price. To attach a photo to a variant, tick it in the image list of that combination.

## A combination has its own fields

On a product page with combinations, each one (size, colour, material…) has its own purchase price, its own stock level, and can have its own photos, independently of the base product. During manual or bulk entry, it’s common to fill in only the base product’s purchase price and forget it on each combination, which then skews the margins calculated afterwards.

The "from £X" price shown on a product page with combinations is the price of the cheapest one, not the base product’s price. This is a frequent source of confusion: the base price exists in the database, but it isn’t what gets displayed once combinations exist.

## Why entering photos per combination takes time

Each combination can have its own images, separate from the base product’s photos. That’s why attaching dozens of images to dozens of combinations is slow by default in the back office: the standard interface handles this one combination at a time, with no bulk import built in for this specific case.

## The combination selector displaying badly on mobile

> A size or colour selector rendering badly on a small screen is most often down to a theme component that doesn’t load its JavaScript correctly on mobile, rather than a problem with the combinations themselves.

## Configuration or development?

Fixing a missing purchase price on a handful of combinations, or adjusting how the selector displays, is standard data entry or theme work. It becomes development when bulk entry needs automating — importing a purchase price per combination, or attaching dozens of photos per combination from a file rather than by hand, screen by screen.

## Related pages

- **CSS or responsive display bugs after a theme change** — When the display issue affects the whole theme, not just the combination selector. ([/prestashop/problemes/bugs-css-responsive-apres-theme](/prestashop/problemes/bugs-css-responsive-apres-theme))
- **Bespoke PrestaShop module development** — For automating a bulk entry of purchase prices or photos per combination. ([/prestashop/module-sur-mesure](/prestashop/module-sur-mesure))
- **PrestaShop shop loading slowly** — A large number of images per combination can also weigh down product page loading times. ([/prestashop/boutique-lente](/prestashop/boutique-lente))

## FAQ

### Why is the margin calculated on my combinations wrong?

Usually because only the base product’s purchase price was entered on creation, without carrying the correct purchase price over to each combination. Margin is calculated from each combination’s own purchase price.

### How do I attach around 130 photos per combination without doing it all by hand?

The standard interface attaches images one combination at a time. For a large volume, a script or import module that reads a file mapping combination reference to image avoids repeated manual entry.

### Why doesn’t the price shown on the product page match what I entered?

If the product has combinations, PrestaShop displays the cheapest combination’s price preceded by "from", not the base product’s price. That’s native behaviour, not a bug.

### The size selector doesn’t display correctly on mobile, is that linked to the combinations?

Rarely directly: it’s usually a theme script that doesn’t load correctly on a small screen. The issue lies in the display, not in the combination data itself.

### Can I change a product page with combinations just for mobile?

Yes, but that touches the theme, not the product record itself. It’s targeted development work on the responsive display, distinct from a data fix.