Skip to main content

Catalog FAQ

1. Do we need to send Krestor an updated feed daily?​

Not for a Proof Schedule. While full integrations involve regular updates to the product catalog, this is usually not necessary for a Proof Schedule. Occasionally, we do ask for an updated product catalog when a large percentage of the product ids flowing in from our beacon are no longer matching up with the items in the product catalog. When this happens, we'll ask you to send us an updated catalog.

2. What does Krestor mean by "facets"? Aside from id, name, image_url, and group_ids, what kinds of fields should we include for each product?​

  • Fields that your users can filter or sort products with on your current search results and browse pages
  • Fields that you'd like to create boost/ bury/ slotting rules with
  • Examples: Brand, Color, Type, Material, Size, Ingredients, Diets, Price, Make, Model, etc.

5. Do we need to send images/image URL’s for the POC?​

Yes. For this proof of concept, we need a single image url for each product. If variation's of a product are different colors or look different in some other way, please provide image urls for each variation.

5. Do we need to send store-level inventory and pricing?​

Not for a Proof Schedule. We'll add this type of information during a full integration.

5. Do we need to send variation-level pricing?​

Not for a Proof Schedule. We'll add this during a full integration.

6. Can we send you our catalog via FTPS or REST API?​

There are some special cases where using FTPS or using our REST API to manage a catalog does make sense during a Proof Schedule, but this is rare. These are the methods for managing catalogs that our active customers use; however, correctly managing catalogs with these methods takes time to learn for your team and time to support for our integration engineers. To save engineering time across teams, we recommend that you use one of the options listed on the Catalog Transfer page for the Proof Schedule.