Navigating Salsify’s New Kroger New Item Setup API: A Guide for Brands
July 22, 2025
Jessica Bagby
Senior Director, Managed Services
Jessica is the Senior Director of Managed Services with a passion for helping brands fully leverage PIM to improve business processes and sell on digital shelf. Her wide range of experience in retail E-Commerce, digital merchandising, brand marketing and sales operations brings cross-functional knowledge to share with clients. Her favorite part of every project is getting to know each stakeholder to create strong relationships and build trust. In 2019, she was recognized by Salsify as a “Digital Transformer” based on her pioneering Salsify work in the sporting goods industry. Jessica lives in St. Louis, Missouri with her husband, and two kids. Their favorite weekends are spent at Table Rock Lake where they love to boat, water ski and hike.
There is a new way to send new items to Kroger, and brands now have an alternative to 1WorldSync for syndicating new items to Kroger – meet Salsify’s new Kroger NIS (new item setup) API!
Salsify has introduced a groundbreaking development for brands looking to streamline their product syndication process with Kroger: the new Kroger New Item Set-up API (also known as a Channel). This API promises enhanced efficiency and accuracy, but successful implementation requires thoughtful preparation. Here are Sitation’s Top 3 Ways to best prepare for initial Kroger NIS API configuration and syndication.
1. Embrace the Packaging Hierarchy
A crucial change for many brands, especially those that aren’t using Salsify for GDSN syndication currently, is the new requirement of setting up and reconfiguring your data model to include Packaging Hierarchy. A flat data model simply won’t meet the requirements for successful syndication through this new API.
Salsify’s Kroger channel requires a well-formed hierarchy that reflects the relationship between Eaches, Cases, and Pallets—even for non-GDSN clients.
- Packaging Hierarchy is Key: Brands must set up a robust packaging hierarchy to syndicate successfully. This is the only Salsify-supported API/channel outside of the GDSN connector, where a flat data model would not have met the requirements for readiness and syndication.
- Case Records are Essential: For many non-food brands and distributors, case-level data may be a new concept. Traditionally, this level of detail was only required for GDSN publications, but with this Kroger API, even categories like personal care or beauty will need to implement case records. Expect some change management here: your product teams will need to establish standards and governance around packaging hierarchies that they may not have had before.
2. Prioritize High-Quality Content
Content quality is paramount, and poor content quality may bust an organization’s timeline for getting onboarded. A rigorous, offshore QA process by Salsify will review all submitted content, and any inaccuracies will slow down your speed to market.
- Salsify’s QA Process: Salsify’s QA process rigorously reviews images and content for accuracy. With the QA process taking off-shore, companies may experience inconsistencies in feedback and timezone delays. Be prepared for multiple rounds of feedback – Sitation has seen inconsistencies on product records cause issues in product submissions that were not addressed or noted on initial channel feedback.
- Consistency across Digital Assets and Content is Critical: If the packaging verbiage does not match the written content, it will be flagged and sent back for correction. This can significantly delay your product’s journey to market.
- Configure the Content Quality Workflow for Proactive Review: Salsify’s content quality workflow acts as a “pre-review” before publishing to QA. This invaluable tool helps catch content issues early, allowing brands to be more proactive in fixing data discrepancies before they cause delays.
3. Understand the Kroger Review Process
Once your item passes Salsify’s QA, it moves into Kroger’s internal review. An Item Master Form (IMF) is generated and sent to the Kroger Category Manager (CM) for approval or rejection.
- IMF Generation: After passing Salsify QA, an IMF is generated and sent directly to the Kroger Category Manager.
- Acceptance or Rejection: The Kroger CM will either accept or reject the item based on their internal standards. Although this process should take 24 hours, it’s advised to allot an additional day or two.
The Bottom Line: Diligence and Proactivity
Salsify’s new Kroger New Item Set-up API offers a powerful solution for brands seeking efficient syndication of their product data. However, its effectiveness hinges on brands’ commitment to higher data quality and proactive management of their content and timelines.
- Content Quality: Be diligent about the accuracy and completeness of your content.
- Proactive Timeline Management: Anticipate the various review stages and allocate sufficient time for content creation, internal review, Salsify’s QA, and Kroger’s final approval.
By understanding and preparing for these key areas, brands can leverage Salsify’s new API to achieve faster and more successful product syndication with Kroger.
For more information and to prepare for your initial API configuration and syndication, please reach out. We are here to help you navigate this exciting new integration and successfully get your new items setup at Kroger via Salsify.