PrestaShop Platform

Running a self-hosted store means product, stock, and order data lives entirely inside your own PrestaShop installation, with no built-in connection to marketplaces, comparison shopping engines, or advertising channels. Connecting PrestaShop to Feedance gives you a way to keep that catalog and stock data flowing outward without manually exporting files or maintaining custom scripts.

Once connected, Feedance can pull your product and inventory data on a regular basis and turn it into feeds formatted for the channels you sell on, while also keeping order information available for reconciliation. This is especially useful for PrestaShop merchants managing large catalogs, frequent price or stock changes, or multiple sales channels alongside their own storefront.

Feedance connects directly to your PrestaShop store using secure, key-based authentication. You generate an API key inside your own PrestaShop back office and grant it access to the specific store resources Feedance needs. Once that key is entered into Feedance, the connection is established without installing a custom plugin or modifying your store's codebase.

From that point on, Feedance uses the connection to read your catalog and stock data and to keep order information up to date, respecting the permissions granted to the key. Because the connection is credential-based rather than file-based, there is no need to manually generate or upload CSV or XML exports.

Feedance works with three categories of data from any connected platform, including PrestaShop:

Feedance does not access or modify other PrestaShop data such as customer records, coupons, or shipping and tax configuration.

• The webservice API is off by default. PrestaShop ships with its API disabled; it must be turned on and a key generated under Advanced Parameters > Webservice before any external tool, including Feedance, can connect.
• Resource permissions are granted individually. An API key only exposes the specific resources (such as products, stock, or orders) it has been explicitly given access to, so a key created for one purpose may need its permissions expanded.
• Combinations carry their own stock. Products with variants (size, color, and similar options) store quantity data separately for each combination rather than a single quantity on the base product, which affects how inventory needs to be read for accurate feeds.
• Multi-shop setups scope data by shop. Stores running PrestaShop's multi-shop feature manage stock and catalog data per shop or shop group, so the shops an API key can see will determine which products, stock, and orders are available to sync.

1. In your PrestaShop back office, go to Advanced Parameters > Webservice and enable the webservice feature.
2. Generate a new API key and grant it permission to access your product, stock, and order resources.
3. In Feedance, start a new store connection and select PrestaShop as the platform.
4. Enter your store URL and the API key, then let Feedance verify the connection.
5. Review the products, inventory, and orders Feedance has pulled in, then configure your feed settings and channel exports.

Feedance syncs your PrestaShop products, inventory, and orders on a regular automated schedule after the initial connection, so your feeds reflect recent catalog and stock changes without manual re-exports. Exact sync frequency can vary by plan and store size, and you can also trigger a manual sync in Feedance if you need your latest PrestaShop changes reflected sooner.

1. Keep product references/SKUs consistent across all combinations so channels can match variants correctly.
2. Fill in complete product data in PrestaShop, including titles, categories, and images, before syncing, since incomplete listings are more likely to be rejected by marketplaces and ad channels.
3. Make sure combination-level stock is enabled and accurate if your catalog relies on product variants, so inventory feeds reflect real availability.
4. If you use PrestaShop's multi-shop feature, review which shops your API key covers periodically to avoid missing or duplicated listings.
5. Check order status mapping regularly so downstream reporting and reconciliation stay accurate as your store grows.