2 weeks ago
Hi,
We are an apparel company setting up item management through XML with Kroger. Unfortunately, the available XML samples don’t cover apparel use cases, so I’m hoping someone can help clarify a few questions.
In the XML structure, do I need to define both the pre-pack and its components under <CatalogueRequest><Document><item>, and then establish the relationship at the end using the pattern/child quantity structure? Or should I only use <CatalogueRequest><Document><item> to define the pre-pack and then just define the relationship using the pattern/child structure?
Also, when specifying the quantity of child items, which link should be used—the GDSN link or the item link?
2 weeks ago
Hello! Welcome to the Community!
Yes the correct formatting would be define the "pack" followed by the components within the pack.
To create your XML for apparel items please use our example XML's attached in the link below to structure your XML to ensure it's valid.
https://community.1worldsync.com/t5/Connectivity-Docs/ct-p/ConnectivityDocs
Combined with the sample XMLs please utilize the Item Management Participant Dictionary (IM PD) along with the Kroger Attributes (attached) that show the attribute XML Names and Flex/XML Structure type. I've attached below the link to our Participant Dictionary and Kroger Attribute sheet as well.
https://community.1worldsync.com/t5/Troubleshooting-Attribute/Kroger-Attribute-Sheet/ta-p/10496
The Kroger specific attributes will be in the "Flex group". The "Flex type" for each attribute is listed in the attached Kroger Attribute sheet. Lastly, the XML Structure Type in the Participant Dictionary are listed in the "Data Source XML Guide" tab.
Thanks
2 weeks ago
Thank you for your reply. Unfortunately, none of the samples in the XML file address apparel or my specific questions regarding pre-packs. Additionally, the Kroger attribute sheet does not seem to cover apparel-related requirements.
We recently completed our migration, and I was able to identify some of Kroger’s mandatory fields, such as the Kroger family tree code and Kroger code.
For context, our pre-pack typically contains 7 items (2 Small, 2 Medium, 2 Large, and 1 XL).
In terms of the XML structure, could you please clarify the following:
<CatalogueRequest><Document><item>, and then establish the relationship at the end using the pattern/child quantity structure?<CatalogueRequest><Document><item> and then define the components and their quantities solely through the pattern/child structure?
Also, when specifying the quantity of child items, should the reference link be the GDSN link or the item link?
Thank you for your guidance
a week ago
Hello @gasemipour,
Thank you for reaching out.
I can confirm that a ticket has already been created for your request under CXTECH-112641, and an agent has responded. Please check your email and follow up with them if you have any additional questions.
Regarding your question on component quantities, these should be defined using the NumberOfPiecesInSet component attribute. This attribute marks the beginning of the component-specific attributes.
For additional clarity, you may find it helpful to review a component item in IM. You can cross-reference the IM UI attribute names with the corresponding IMPD XML names, and refer to the sample XML to see how the attribute is structured and applied in context.
Thank you.