Available for projects & agency overflow · Quick reply, from the person who does the work

Send a message contact@allaux.fr
FR EN TR
allaux.
Emergency Discuss my project

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.

Describe my issue Send a message

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.

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

Describe your need in one minute

A few targeted questions so I can reply with an estimate rather than another questionnaire.

objectif
version
emplacement (facultatif)
existant (facultatif)
echeance (facultatif)
Please provide an email or a phone number so I can get back to you.

Please provide an email or a phone number so I can get back to you.

Frequently asked questions

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.

Related pages