Central Restaurant Products’ Cody Bell Shares How He Uses the New Industry Tool

What did it take on your end to get Central Restaurant Products set up to use the repository?
We were lucky enough to have the data foundation in place to begin working with the FEDA data repository. A lot of it is just making sure that our internal data is organized so that we can take the data coming from the repository, match that up with our internal SKU nomenclature and then make sure it fits our data naming conventions and standards.

What do you like about using the data repository so far?
I like the simplicity of it, along with the ability to pull in several data filters at once to filter down the data before exporting out. I’m also a fan of being able to schedule automated downloads within the repository.

What are some ways Central Restaurant Products is using the data repository? Has it been easy to incorporate the product data across your operations?
Our pricing analyst has been working with the API functionality of the data repository to pull in reports when vendors update their pricing data so that we can stay on top of pricing changes. On the product data side, we are in the process of getting automated downloads set up to validate how we best utilize that information at a  regular cadence.

The FEDA Data Repository is one new tool distributors are using, but what other upcoming technologies are on your radar?
ETL (extract, transform, load) tools are at the forefront of how we want to improve the speed of our data management. Time is money; the less time it takes for us to transform the data provided by the FEDA repository into something we can provide to our customers, the sooner we can start seeing the benefits of the data provided.

What advice can you give to other dealers that want to start using the data repository? What should they do or what do they need to do to get the most out of this tool?
The most important thing I recommend to other dealers is you need to really know your in-house data. Where and how is it currently managed? Is it set up in a way where it can easily be mapped to the FEDA repository? Do you have the staff or resources in place to manage and transform this data once you get it? The cleaner your ERP/PIM data is, the easier it will be to capitalize on the data provided from the FEDA repository.