Audience: Suppliers

Here are some guidelines to accelerate the product setup process using advanced catalog services and to ensure your products meet basic system requirements as well as your retailer’s requirements. These products will be processed for compliance, and any image errors can be found in the Catalog Exceptions page in the web application.

If your retail trading partner does not use advanced catalog services to manage their products, refer to Working with images for basic catalog for image guidelines.

Looking to add images to your products? You can load images using the Add Products template, the Catalogs API,  or directly through the web application. For information about adding images directly through the web application, see Editing your products.

Product Images vs. Item Images

Product Images

Product images should be used to showcase the various products you sell. You can add many different product images to each item in the web application. 

TIP: Product-level image fields should only be used if you're also using the Product Groups feature. See Variant SKUs and Product Groups for more information. If you're not using the Product Groups feature, use the item images option when adding images to an item. 

Item Images

Item images should be used to showcase the individual items/variations within a product group. Unlike product images, item images should be specific for each item in the web application.

Tip: Retailers using advanced catalog services will have image attributes with the images prefix, e.g. images.front_image, images.back_image, images.profile_view. Attributes with the images prefix must contain values that are unique across each item. Attributes with the product prefix must contain values that are the same across all variations.

Correct Example:


In this example, the supplier has correctly placed the color-specific images in the images.main column, and used the same image to represent the entire product group.

Incorrect Example:


In this example, the supplier has mistakenly used model-specific image variations (red, gray_peach, etc.) as product images across the same product group (AIR_SNEAKER).

Image Requirements

  • Rithum supports the following file formats for any sized images:
    •  JPG
    • JPEG
    • PNG
    • GIF
  • We recommend providing very high resolution images with a max width of 2000px, and/or max height of 2000px. Your trading partner may have specific image size requirements, so be sure to check their requirements if your images are not compliant.
  • You must not include spaces in the image title. Using hyphens (-) or underscores ( _ ) is recommended to create more stable image links. Here’s an example: ABCDE_1234-1234.jpg.

Image Hosting Requirements

Images must be hosted in a PUBLIC repository/site. If you aren't sure how to host images online or do not have an internal hosting site that's public, you can use one of the following services:

  • AmazonAWS
  • Box
  • BOXcloud
  • Cloudfront
  • Dropbox 
  • Flickr  
  • Google Photos
  • Imgur    

 Important: Be aware that public hosting repositories/sites may have their own restrictions and limitations for data downloads, and this may affect how, or the speed at which, your images are downloaded. In some cases, the Basic/Level 1/Free contract with any service may not meet the platform's expectations for availability.

Image URL requirements

You can always upload image files directly in the web application. However, if you want to upload via the Catalog API or Add Products Template, you must upload via an image URL, which will need to meet the following requirements:

  • You must use HTTPS. Here's an example:
  • You must not include spaces in the URL. Using hyphens (-) or underscores ( _ ) is recommended to create more stable image links. Here’s an example:
  • The image URL must: 
    • Be a valid format.    
    • Link to raw image data (not an image view).    
    • Lead to a downloadable image file. If the system cannot download the image, the URL will fail.    
    • Be an actual image file (JPG, JPEG, PNG, or GIF. Not a PDF) when downloaded by the system.
  • If images are rejected by the upload tool, you can visit the URL provided in the file to confirm the image will render in the browser (you must not be logged in to your image hosting site). When viewing images, there should not be additional navigational links/buttons on the page; only the image should show in the browser window.
  • Be aware that image preview pages with download buttons and other icons are not direct links to the images.
  • You must provide a new URL for each updated image. If you replace an existing image with a different image, you must provide a new URL for the updated image. You can not reuse the existing image’s URL for the updated image. This is to ensure that the image will be processed for compliance and meets the system’s and the retailer’s requirements.

If you're using Dropbox to host your images:
Dropbox will automatically create a direct image link with a dl=0 extension at the end of each URL, which will result in an image error. You must change the dl=0 value to dl=1. Valid image URLs should look like this:

Was this article helpful?
3 out of 6 found this helpful


1 comment
  • You say one can use but that system does not point at the actual image file. so how is it used?

    Comment actions Permalink

Please sign in to leave a comment.