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 media errors can be found in the Catalog Exceptions page in the web application. These guidelines apply to images, video, and .pdf files.
If your retail trading partner does not use advanced catalog services to manage their products, refer to Working with media for basic catalog for media guidelines.
Looking to add media to your products? You can load media using the Add Products template, the Catalogs API, or directly through the web application. For information about adding media directly through the web application, see Adding media to SKUs and products.
Product media vs. item media
| Product media |
Product media should be used to showcase the various products you sell. You can add many different product media to each item in the web application. TIP: Product-level media 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 media option when adding media to an item. |
| Item media |
Item media should be used to showcase the individual items/variations within a product group. Unlike product media, item media should be specific for each item in the web application. |
Tip: Retailers using advanced catalog services will have media 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 file 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 media across the same product group (AIR_SNEAKER).
Image file requirements
- Rithum supports the following file formats for images:
- JPG
- JPEG
- PNG
- GIF
- WEBP
- 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.
- The images must not exceed a size of 50mb per file.
Video file requirements
- Rithum supports the following file formats for video:
- WEBM
- MP4
- MPG
- MOV
- M4V
- WMV
- The media files must not exceed a size of 50mb per file.
PDF file requirements
- Rithum supports only .PDF files for text/graphic files.
- The PDF files must not exceed 50mb per file.
Media Hosting Requirements
Media must be hosted in a PUBLIC repository/site. If you aren't sure how to host media online or do not have an internal hosting site that's public, you can use one of the following services:
- AmazonAWS
- Box
- BOXcloud
- Cloudfront
- Drive.google.com
- Dropbox
- Cnetcontent.com
- Flickr
- Google Drive
- 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 media files are downloaded. In some cases, the Basic/Level 1/Free contract with any service may not meet the platform's expectations for availability.
Image or video URL requirements
You can always upload media files directly in the web application. However, if you want to upload via the Catalog API or Add Products Template, you must upload via a media URL, which will need to meet the following requirements:
- You must use HTTPS. Here's an example: https://www.dropbox.com/s/85dxl67o4xinmlj/FW5033-MFW5223-M1.jpg.
- You must not include spaces in the URL. Using hyphens (-) or underscores ( _ ) is recommended to create more stable media links. Here’s an example: https://www.dropbox.com/s/009988/ABC_12-12.jpg.
- The media URL must:
- Be a valid format.
- Link to raw media data (not a media view).
- Lead to a downloadable media file. If the system cannot download the media, the URL will fail.
- If media is rejected by the upload tool, you can visit the URL provided in the file to confirm the media will render in the browser (you must not be logged in to your media hosting site). When viewing media, there should not be additional navigational links/buttons on the page; only the media should show in the browser window.
- Be aware that media preview pages with download buttons and other icons are not direct links to the media.
- You must provide a new URL for each updated media. If you replace an existing media file with a different media file, you must provide a new URL for the updated media. You can not reuse the existing media’s URL for the updated media. This is to ensure that the media will be processed for compliance and meets the system’s and the retailer’s requirements.
If you're using Dropbox to host your media:
Dropbox will automatically create a direct media link with a dl=0 extension at the end of each URL, which will result in an media error. You must change the dl=0 value to dl=1. Valid media URLs should look like this: https://www.dropbox.com/s/85dxl67o4xinmlj/FW5033-MFW5223-M1.jpg?dl=1.
If you're using Google Drive to host your media -
Use one of the following formats for your media URL:
Comments
You say one can use drive.google.com but that system does not point at the actual image file. so how is it used?
Please sign in to leave a comment.