Skip to main content

Filename Transformations Export

Downloading Images with Channel Specific Naming Formats

Brynlee Weibell avatar
Written by Brynlee Weibell
Updated yesterday

I. Overview

II. Prerequisites

III. Setting Up the Channel Template

IV. Publishing to the Channel

V. Important Notes


I. Overview

Filename transformations in PXM allow users to customize how image files are named when exported from the platform. This is especially useful for meeting the specific naming conventions required by different retail channels (like Amazon or Chewy). Using image stacks and mapping tools within PXM, you can define a pattern using attributes (like ASIN or SKU) and add delimiters (like -MAIN or .PT01) to automatically generate properly formatted filenames. Once set up, these transformations streamline exports and help ensure compliance with retailer requirements.


II. Prerequisites

Channel Requirements

  • Image Sizes: Obtain the required image sizes (e.g., 3000x3000 pixels).

  • File Naming Conventions: Determine the desired file naming conventions for each image within the stack.

    • For example: "ASIN.MAIN.jpg", "SKU_PT01.png" etc.

  • Image Modifications: Determine if cropping, background color, or padding is required for the images.

Image Stack Creation

  • Ensure the necessary image stack has been created within PXM.


III. Setting Up the Channel Template

Create a New Channel Template

  • Navigate to Settings > System Settings > Channels in PXM.

  • Create a dedicated channel specifically for filename transformations (e.g., "Filename Transformations Channel").

  • It is recommended to create a unique channel template for each different channel’s requirements.

  • From there, upload the Filename Transformation Template (Reach out to your CSM if you don't already have this).

Map Image Attributes and Sizes

  • Map Required Attributes: Within the Filename Transformation template, map the Image Stack positions of the images.

  • For the mapping of the Filename, you will select MAP, then toggle to "Multiple Attributes". Note that we will use both attributes, and delimiter as a default value field.

  • Map the required image attributes (e.g., map the "asin" attribute) if applicable.

  • Define Delimiters: Define the default value to be used in the filename (e.g., ".main").

  • Map Image Size Requirements: Map the image size requirements (e.g., 3000x3000 pixels).

  • Additional Requirements: If necessary, map any cropping, background color, and padding requirements.

Image Resizing Options Documentation

  1. Crop: Allows cropping images based on standard HTML/CSS syntax.

    • Specify crop positioning using formats like:

      • center

      • top

      • bottom

      • left

      • right

      • Compound positions: center:center, center:top, center:bottom, left:top, right:bottom

    • Examples:

      • Crop to center: center

      • Crop to bottom-right: right:bottom

  2. Background Color: Sets a background color using HEX values if the original image contains transparency.

    • Format: #RRGGBB

    • Examples:

      • White background: #FFFFFF

      • Black background: #000000

      • Blue background: #3498DB

  3. Padding: Adds padding around the resized image using CSS syntax in pixel values (px).

    • Format examples:

      • Single value: 10px (applies equally to all sides)

      • Two values: 10px 20px (top/bottom, left/right)

      • Three values: 10px 15px 20px (top, left/right, bottom)

      • Four values: 10px 20px 15px 25px (top, right, bottom, left)

    • Examples:

      • padding: 20px – Adds 20px padding on all sides.

      • padding: 10px 15px – Adds 10px padding to top/bottom and 15px to left/right.

      • padding: 5px 10px 15px 20px – Adds specific padding to each side individually.

Example Filename Mapping: If the client requires filenames in the format "asin.main," map the "asin" attribute and append the delimiter ".main."

  • Repeat for All Images: Ensure that all images within the image stack have their respective attributes, sizes, and filenames mapped correctly.

  • Save Changes: Save all changes to the channel template.


IV. Publishing to the Channel

Select Items for Transformation

  • Choose the products in PXM that require filename transformations.

Initiate Batch Action

  • Use "Batch Actions" (Or Elipses button) to "Publish to Channel."

Configure Publishing Options

  • Select the "Filename Transformations Channel" template.

  • Ensure the "Download" option is selected.

  • Choose the appropriate filename transformation template that was previously created.

  • Select the correct image stack that the client requires.

  • Enable the "File Transformation" option.

Execute Publishing

  • Click "Continue" to initiate the publishing process.

Retrieve Transformed Files

  • PXM will send an email notification once the transformed files are ready for download.

  • Download the generated folder.

Verify Filenames and Image Sizes

  • Open the downloaded folder and verify that the filenames have been correctly transformed (e.g., "asin.main").

  • Confirm that the image sizes, cropping, padding, and background color meet the client's requirements (e.g., 3000x3000 pixels).


V. Important Notes

  • Processing time may vary depending on the number of items being transformed.

  • Thoroughly test the filename transformation setup to ensure accuracy.

  • Keep organized channel templates to make the process repeatable.

  • Always double-check client requirements.

Did this answer your question?