This procedure is intended for SFCC administrators responsible for managing product imagery and localized product assets.

Product imagery is managed directly from the product record, not from Page Designer.

Images are managed at the master reference / GEN Code level, meaning the 00... reference associated with the product family.

From the product record, administrators can:

• Upload new product images.
• Organize images within folders.
• Assign images to the product.
• Define a common image set.
• Override the common images for individual locales.
• Reorder images to control their display sequence.
• Maintain different image sets between markets when required.

Understanding Image Views

The Image Manager contains several views.

The two concepts to understand are:

view type = "large"

The large view is the common image set.

It acts as the default when a locale does not have its own images.

Locale-Specific Views

Separate views are available for individual markets, for example:

• Italy
• UK
• Australia
• France
• Germany
• Poland
• Singapore
• US
• Switzerland
• MENA

If no image is assigned to a locale-specific view, the images from large apply.

If images are added to a locale-specific view, that market can have its own image set instead of relying on the common images.

This makes it possible to maintain a global/default set while accommodating market-specific product imagery where necessary.

Product Images Are Not Managed in Page Designer

Do not look for the main product image gallery in Page Designer.

Product imagery is managed from:

Products and Catalogs → Products

and at the GEN Code / master reference level.

Understand the Fallback Before Localizing Images

Do not duplicate the same images into every locale simply because locale-specific views exist.

If a locale does not require different imagery, it can rely on the common large view.

Use a locale-specific view when that market genuinely needs a different image set.

Keep the File Structure Organized

Images should ideally be stored in appropriate folders rather than uploaded indiscriminately.

The folder structure and naming should help administrators understand what the assets represent and maintain a form of history over time.

Where relevant, distinguish between assets such as:

• Current and previous assets
• Sellable products
• Samples
• Travel sizes
• Goodies
• Market-specific assets

The objective is to keep the image library understandable for future administrators and make it possible to distinguish old assets from newer ones.

Lock and Unlock the Product

The product must be Locked before editing.

Once image management is complete, remember to Unlock the product so that another administrator can work on it.

1. Access Products

Navigate to:

Products and Catalogs → Products

Search for the product whose imagery needs to be managed.

2. Select the Master Reference

Product images are managed at the master reference / GEN Code level.

Open the corresponding 00... reference rather than managing the imagery independently from each sellable SKU.

3. Lock the Product

At the top of the product record, click:

Lock

This enables editing of the product.

Do not continue with the modification until the product is locked.

4. Locate Images

Remain on the product record.

Scroll below:

Long Description

Locate:

Images

Click:

Edit

The Image Manager opens in a pop-up window.

5. Understand the Image Manager

The Image Manager is divided into different working areas.

On the left, the product is displayed under:

base product

The central area contains the available image views, including the common large view and market-specific views.

On the right, the File Browser allows you to browse and manage the image files available for use.

6. Understand the large View

Locate:

view type = "large"

This is the common image view.

Images assigned here provide the common/default image set for the product.

When a locale does not contain its own image set, the images from large apply.

7. Understand Locale-Specific Views

Below the common view, locate the available locale-specific views.

For example:

view type = "Italy"

view type = "UK"

view type = "Australia"

and the other available markets.

These views allow a market to use a different image set.

Example

Suppose the product contains its standard imagery under:

large

and Australia does not have anything configured in its own view.

Australia relies on the common images.

If Australia requires a different set of product images, add those images under:

view type = "Australia"

The Australian product experience can then use that market-specific image set.

8. Browse Existing Images

On the right side of the Image Manager, locate:

File Browser

and the File folder structure underneath.

Click a folder to browse its contents.

The files contained within the selected folder appear in the File Browser.

Use the existing folder structure whenever an appropriate location already exists.

9. Choose the Appropriate Folder

Before uploading a new image, determine where it should be stored.

The existing library can contain folders dedicated to different asset types, products or markets.

Choose a folder that makes the asset easy to identify and retrieve later.

Where required, the structure should also make it possible to distinguish newer imagery from historical assets.

10. Manage Folders

Right-click the folder you want to manage.

A contextual menu opens.

From this menu, available actions include:

• Rename
• Delete
• New Folder...
• Add...

This allows administrators to maintain the file structure directly from the File Browser.

Do not create unnecessary folders when an appropriate location already exists.

11. Add an Image to the Selected Folder

Right-click the folder where the image should be stored.

Click:

Add...

A file selection window opens.

Select the required image from your computer.

The selected file is then added to the upload area underneath the folder.

12. Add Multiple Images When Required

You can prepare more than one image for upload.

Add the required images before starting the upload when several assets need to be introduced at the same time.

The selected files appear underneath the chosen folder.

13. Remove an Image From the Pending Upload

If you selected the wrong file or no longer want to upload one of the prepared images, use the red cross next to the corresponding file.

This removes it from the pending upload.

14. Upload the Images

Once the correct files have been added, click:

Upload

The selected images are uploaded into the chosen folder.

Remember that adding the file and uploading it are two separate actions.

Selecting a local file does not by itself complete the upload.

15. Locate the Uploaded Image

Once the upload is complete, browse the selected folder.

The newly uploaded image should now be available within the File Browser.

You can now assign it to the product.

16. Assign an Image to the Common View

To make an uploaded image part of the common product image set:

1. Locate the image in the File Browser.
2. Drag the image.
3. Drop it into:

view type = "large"

The image becomes part of the common image set.

Use this view for imagery intended to apply wherever no locale-specific image set has been configured.

17. Assign an Image to a Locale-Specific View

When a market requires its own imagery:

1. Locate the required image in the File Browser.
2. Drag the image.
3. Drop it into the appropriate locale view.

For example:

view type = "US"

or:

view type = "Italy"

The images assigned to that view create the locale-specific image set.

18. Add Multiple Images to a View

A product can contain several images within the same view.

Drag and drop each required image into the selected view.

This allows the storefront to display a complete product image gallery rather than only the primary packshot.

19. Reorder Product Images

The order of the images within a view can be changed.

Use drag and drop directly within the selected view to reorganize the images.

Arrange them in the sequence in which they should appear for that product and market.

This allows different markets to have not only different images, but also their own image sequence when required.

20. Review the Common and Local Image Sets

Before saving, review the configuration.

Check:

Common imagery

Does large contain the correct default images?

Local imagery

For every locale containing its own images, confirm that the intended market-specific set is complete and correctly ordered.

Empty locale views

If a locale intentionally relies on the common image set, it does not need its own duplicated images.

21. Save the Image Manager

Once the images have been uploaded, assigned and ordered correctly, click:

Save

This closes the image management step.

22. Apply the Product Changes

Saving the Image Manager is not the final saving action on the product record.

Return to the product page.

Scroll to the bottom of the page and click:

Apply

This saves the product changes.

23. Validate the Product Imagery

Check the relevant storefronts to confirm that the expected images are displayed.

Pay particular attention to markets with localized imagery.

Verify:

• The expected primary product image.
• The complete image gallery.
• The image order.
• Markets relying on the common image set.
• Markets with their own locale-specific image set.

A product can therefore legitimately display a different image gallery between markets when locale-specific views have been configured.

24. Unlock the Product

Once the image configuration is complete, return to the top of the product record and click:

Unlock

This releases the product and allows other administrators to edit it.

Do not leave the product locked after completing the task.

Quick Logic to Remember

Key principle: Product imagery belongs to the product's master reference, not to Page Designer. Maintain the common imagery under large, use locale-specific views only when a market needs its own image set, keep the File Browser organized, and always complete the workflow with Save → Apply → Unlock.