cancel
Showing results for 
Search instead for 
Did you mean: 
CommunityJedi22
Community Manager
Community Manager

As you work to complete the QA process in IM to utilize the Kroger API, you could receive CIC responses letting you know areas that require your attention and correction per item. Here is one of the most common CICs and how to correct it in Item Management.

Product Images Error: Users encounter CIC messages for these issues most often for product images during this process:

  • Exactly One Primary front-facing image is required.
  • Only  Product Images (Type of Information = Product Image) will be sent to Kroger.
  • There are 6 total image spots available. The Primary image + 5 remaining images can be used to best highlight the Brand's product.
  • Select Front, Back, Left, Right, Top, or Bottom angle for each image. Do not duplicate Image Facing.

How to Resolve: Work through the CIC error message(s) while referencing the Kroger Style Guide.  Image requirements for the API are the same as VIP rules.  

  • Use each of the images facing only once.  
  • Approval just needs one main image.  
  • You will not be able to send more than 6 images to Kroger.  
  • The background can only be white or transparent
  • Avoid marketing claims such as “best seller”, “number 1 recommended”, within imagery." 
  • If your product has more than 6 images, you can designate which ones you want to be sent to Kroger as the first 6.  You can do so by using RDD attributes for Kroger for the intended images.  Learn more about RDD for Kroger here.

For best practices, images should appear in the following order:

  1. Main image
  2. Back Alternate Image
  3. Additional Product Angel Alternate Images.  These are only if needed to show product details or helpful information. We do not need to show these angles if they are not useful to the customer (example: top of a milk carton).
  4. Infographic Alternate Image.
  5. Lifestyle/Environmental Alternate Image

Be sure to review the Kroger Style Guide for preferences and best practices.

Comments
eholt
New Community Member

Hello,

I am new to using Kroger API. We previously submitted all e-comm image updates via Kroger VIP. I would add the new image, then submit leaving the Item Submission Reason Code blank in order to not generate a new IMF.

I cannot see that anything has migrated over for our items with the top off info/Kroger attributes from VIP into Item Management. I need to update e-commerce imagery ASAP on quite a few items, but I don't want to have to populate all the Kroger attributes in order to submit without errors. Is there a way to update e-comm images for Kroger only without having to fill out all attributes for every item we need to update? Do we have to submit to the Certification GLN (0838016000123) first if we are just updating imagery? If not, do we publish to the other Kroger GLN (0838016000116))?

Val
Community Support

Hello @eholt, thank you for reaching out to our customer community.  Welcome.

We have just created ticket CXTECH-104805 to find the best way to assist with your inquiry. We will be reaching out through out ticketing system with more details for the request. Thank you.

JCLoackerUSA
New Contributor

I have followed the guidelines, but I am still getting an error message stating the below during the 2nd GLN phase of the publication.  Anyone know yet how to resolve?

ErrorCode:null; Error:[ ImageOrientation: FRONT ]Error while extracting Asset [https://dam.loacker.com/damapi/digitalAssetPreview/410897_big_638307_multipack-tortina-21gx6-origina...]

alien
Community Support

Hello @JCLoackerUSA  and thank you for utilising our customer community.

It could be that Kroger has issues with extracting that image from our system.

It could be that it does not meet Kroger's image requirements Kroger Product Image Requirements or that it was uploaded in a way Kroger does not accept or might have been corrupted.

You can try to remove and reupload or replace the image after you check if there is nothing wrong with the image file.

Thank you and have a great day.

DHood1
New Contributor

There's a inconsistency we've noticed between what the requirements say and what is actually being accepted by Kroger within Item Management regarding images that aren't Product Images.

Per the requirements it is noted that "Only  Product Images (Type of Information = Product Image) will be sent to Kroger." However, when communicating with Kroger directly through buyers & MDM personnel they are both asking & receiving images that are not just the product images. For example a common request in apparel is a sizing chart image especially with products that don't follow a standard S-2XL range. This is a business request and because of the strict requirement of using API only for publications, this business request is attempted to be satisified through this procedure.

For size charts or color pallets they are labeled as "Size Comparison" and "Colour palette" respectively. They are loaded to our SKUs to fulfill the business request and as far as we can see Kroger is at least accepting them and internal Kroger MDM personnel are seeing them appear in their system. However, whenever we encounter publication challenges with errors that are not related to images, the L1 tech support team keeps pointing to these non "Product Image" images as the cause for the errors. This doesn't explain why SKUs that have the Size chart and color palette passed API certification and is seen by Kroger personnel. 

If images other than Product Image are coming through and being accepted by Kroger itself, why is it still being listed in documentation as a requirement that only Product Images are accepted in IM? The practical evidence suggests they can and are. 




Maria
Community Support

Hello @DHood1 

Thank you for using our community!  Welcome!  

Thank you for providing this additional context. To help us investigate the behavior you are seeing, could you please provide a GTIN where a non-Product Image (such as a size chart or color palette) was successfully accepted by Kroger and one that was not? 

We can review the specific example and confirm how these images are being handled through the API.

 

Version history
Revision #:
1 of 1
Last update:
‎08-06-2025 02:38 PM
Updated by:
 
Contributors