Skip to content
CatalogBadge
Get started

Setup guides

Set up CatalogBadge with PrestaShop

PrestaShop connects with a Webservice key: you create it once with read access to your catalog, and CatalogBadge reads your products directly on every update. Nothing is installed in your shop and we never write to it. Works with PrestaShop 1.7 and 8.

1. Create a Webservice key

  1. In the back office, open Advanced Parameters, then Webservice. Set Enable PrestaShop’s webservice to Yes and save. Friendly URLs must be on (Shop Parameters, Traffic & SEO), because we call https://your-shop/api/.
  2. Choose Add new webservice key and Generate a key. Give it a description such as “CatalogBadge, read only”.
  3. Under Permissions, tick only the View (GET) column for: configurations, currencies, countries, languages, products and stock_availables. Leave every other column empty. Save and copy the key.
  4. If the test below says the key is refused although it is right, your host strips the Authorization header: set Enable CGI mode for PHP to Yes on the same Webservice page.

What we read

  • One item per active product, with PrestaShop’s product id as the id. Combinations are not separate items yet.
  • Prices as PrestaShop computes them for a customer, with tax: the regular price, and a specific price (your sale) as the sale price.
  • Photos from your shop’s public image files (/img/p/…), which open without the key; the cover photo first.
  • The name and short description in your feed’s language when the shop has it, the brand, and stock when you manage stock.

2. Connect the key in CatalogBadge

  1. Create your account on app.catalogbadge.com and choose Onboard a store. Add the store with any product feed URL it already has (the wizard checks it and shows sample prices). If it has none yet, write to us and we add the store with you.
  2. Open the store, then Connection. Under Connect with a key, pick PrestaShop, enter your store address (the https address your shop opens on) and paste Webservice key.
  3. Choose Test and connect. We make one read with the key before saving it; if the read fails, nothing is stored and the page says why.
  4. The next update first checks that at least 95 % of the products your feeds already publish keep their ids in PrestaShop. Then the store reads PrestaShop directly and your feed URLs stay the same. If fewer ids match, the store keeps its feed and the Overview says how many matched.

The key is stored sealed, never shown again, never put in a URL and never logged. To stop, choose Disconnect on the same page, or delete the key in PrestaShop: the next update then stops and your published feeds stay exactly as they were.

3. Put your branded feed where your ads read it

Your feed URLs are on your store’s Overview page under Feed URLs, each with a copy button. Treat them like a password: anyone with the URL can read the feed.

Where your ads runFeedWhere to paste it
Meta (Facebook and Instagram)meta-full.xmlCommerce Manager, your catalog, Data sources. If the catalog already reads your store’s feed URL, edit that data source and replace the URL with ours, so your ad sets keep the same catalog. Otherwise add a scheduled data feed with our URL. Steps: Meta guide.
TikToktiktok-full.csvTikTok Ads Manager, Assets, Catalogs: add products with a data feed schedule, set it to hourly and the update method to Replace, so a product that leaves the feed leaves the catalog. Steps: TikTok guide.
Snapchatsnap-full.xmlSnapchat Ads Manager, Catalogs: add a product source with a scheduled feed URL and a daily schedule. Steps: Snapchat guide.
Pinterestpinterest-full.xmlFirst turn on the Pinterest 2:3 size in Rules, under Sizes and language. Then in Pinterest Ads, Catalogs, add a data source with our URL. Pinterest reads it once a day. Steps: Pinterest guide.

Each platform picks up the branded images on its next fetch; the first one can take a few hours. Never delete and re-create a catalog to switch: your ads keep pointing at the old one.

Questions? Write to hello@catalogbadge.com.