Thanks for the reply. The multi-image configuration is already set up and working based on the available matrix options.
The issue I’m facing is related to how image filenames should be constructed when matrix items have different sets of custcol fields.

For example, we have around 10 different custom options across items, but not all items use all of them. Some items only use 2 or 3 options. Despite naming the images correctly, images sometimes appear on the PDP even before options are selected.

My question is:

What naming convention should I follow when items don’t have the same number of options?

For example:
Base format: ItemName-option1-option2.jpg

But in our case:

• Item A has: Size = 1, Color = Blue, Logo = True (no Material)

• Item B has: Material = Foam, Logo = False (no Size or Color)

If the system expects image filenames in a specific order (e.g., Size = option1, Color = option2, Material = option3, Logo = option4), how should I name images for Item A and Item B, considering that not all options are used?

Should I include empty values or just skip the unused ones?
e.g.,

• ItemA-1-Blue--True.jpg (with two dashes for missing Material)

• ItemB---Foam-False.jpg

Any guidance on how SuiteCommerce matches image names to matrix option selections when the number and order of options vary would be very helpful.

Thanks!

Thank you for your explanation! I can see where you’re coming from, but I think there may be a misunderstanding in how the image matching logic works in SuiteCommerce.From what I’ve observed and tested:The image filename pattern is indeed: ItemName-option1-option2.jpgThe system first matches the item name, and then applies logic based on the matrix options that are actually in use for that itemIt doesn’t require placeholders for unused optionsFor example:If ItemA uses Size, Color, and Logo → image name: ItemA-1-Blue-True.jpgIf ItemB uses only Material and Logo → image name: ItemB-Foam-False.jpgThere’s no need to include dashes or blank slots for Size and Color in the ItemB filename, since they aren’t defined as options for that item.Let me know if you’ve seen official documentation suggesting otherwise — I’d be happy to review it together. But based on our configuration and test results, SuiteCommerce only evaluates the options defined and active on the matrix item when matching images.

Thanks, Mia — that makes sense, and I appreciate the clarification.

I haven’t found any official documentation regarding the need for placeholders or how blank/unused options are handled, but in our accounts, we’ve consistently seen issues where the image naming and matching logic don’t seem to work as expected for matrix items. Even when we followed the structure you described, the reordering behavior didn’t apply to any configured items.

That led me to suspect the issue might be related to unused options not being included in the filenames — although as you pointed out, that shouldn’t be necessary. So it might be something specific to the client’s account or configuration, since I haven’t found any other obvious cause.

Thanks again for your help — it’s been really useful!