Screen_Shot_2014-05-30_at_1.37.33_PM

THE SALSIFY SMARTER MERCHANDISING BLOG

Publishing 1000+ Products to a Retailer in 1 Month - A How to Guide

Posted by Erin Paugh on 8:00 AM on February 15, 2016

Someone from your executive team just came over to you with the strategic opportunity to sell through a new retailer. Awesome. But wait. They need product content. And good product content, at that.  In…4 weeks. Seems impossible, right?

Not only is it possible, but there’s actually a way to breeze through the process with less stress and more success. Here at Salsify, we’ve learned and perfected our know-how and technique which we’ve used to help our customers go from panic to success in under a month.

In order to accomplish a task of this size, you must break it up into focused, detailed deliverables week by week. Here’s how:  

Week 1: Get ready

  • Establish your strike team – who will I go to for content and when will I go to them?
  • Create a project plan – define your end goal, determine who will be on the critical path each week, gain a strong understanding of where your product content lives
  • Know which products you want to push to the new retail channel

Week 2: Understand the retailer requirements

Retailers often have a wide variety of product attributes that you can map your product content to.  Some of these attributes are required.  Others are optional.  It’s important to have an understanding of which attributes you absolutely must have product content for and which you do not. Every retailer is different.  For example, Walmart and Target might not have the same required attributes and even if they have similar requirements, they are often looking for different formats for these required attributes.  

Multiple_Retailer_Requirements-01.png
Jet.com and Google Shopping not only have many different required attributes, but even the same required attributes are given different names.

Salsify has schemas in place to help customers understand the unique requirements that retailers have.  These schemas not only include the retailer’s attributes but also the way in which these attributes need to be formatted.

Week 3: Connect the dots

  • Map your product content to each channel’s requirements.
  • Submit your content. Wait. Hear back from the retailer on what needs to be edited, what is missing and what you could add.    
    • Most retailers have validation built in where they will come back to you with the gaps, therefore, the sooner you send content over, the sooner you will hear back on what you need to tweak.
    • Salsify handles retailer validation directly within the platform through its Readiness Report capability. Users are able to quickly see which products meet a retailer’s requirements and from there, make changes to their content so that it will be accepted by the retailer.

New_Balance_Product_Page_Marked_Up-01-1.png

Retailer Reports catch every little gap and error, ensuring that you get your content is 100% accurate when you publish to a sales channel.

Week 4: Fill in the missing data and the additional data

  • Gather the data you were missing- often times product content is stored in multiple locations that are maintained by different people. Yikes! By using workflows to complete a gap analysis, you can not only determine where the product content is but also who is responsible for gathering that data.

Pasted_image_at_2016_02_03_03_06_PM.png

Readiness Workflows let you assign an owner to every last task, ensuring that no content slips through the cracks.

  • Add in the lower priority content – Salsify’s platform helps you figure out the information you need to fill in optional attributes for your products. This can differ from retailer to retailer.
  • Resubmit your products to the channel.

Week 5: Vacation in the Bahamas

Or, more likely, respond to the next fire drill.



Topics: Internal Management, Ecommerce, Product Content


Subscribe to Salsify's Decoded: Contemporary Commerce Blog
Liked this blog post? Get many more like it delivered right to your inbox.

comments powered by Disqus