03-01-2023 03:44 PM
GS1 recently made changes to image facing, changing the values from words (like “Front”) to numeric (“1”). 1WS also backported the changes throughout our product catalogue. We have adopted the changes via our 1WorldSync feed and this is now causing failures in VIP.
Can you advise if and when Kroger will adopt the new GS1 Image Facing standard?
03-01-2023 05:00 PM
Hello @marisolburt . I am checking on this for you and will get back to you.
03-02-2023 01:56 PM
Fortunately, This change was in the February 2023 release where GDSN added an attribute for Image Facing, which replaces the setup which has been used by Kroger. In the Kroger version the valid values were words, Front, Left, FrontCentre, FrontLeft. GDSN changes these to be 1, 2, 3, 7, 8, 9 to match the 17th position of the file naming convention.
The values for FrontCenter, FrontLeft, etc, now are split into 2 attributes: image facing as mentioned and image orientation type code. The orientation is the plunge angle for the image, Center, Left, Right, No Plunge.
Current Kroger validation rules in PI do not allow for more than one Front Image. Since the attribute image facing only has the Front and not the Front Center, etc., some folks are getting errors that they have too many Front images. We are working to correct this quickly on our end.
The only work around at the moment is to make sure there is only 1 image that has the following combination- Image Facing of "1" for "front" and Image Orientation Type code of "N" for "No Plunge" or is left null. The issue is Image orientation having both of these values. It needs to be only one of these for a Front image.