Google Merchant API Sync

Edition: CS-Cart & Multi-Vendor · Latest version: 1.0.0 · Compatible with: CS-Cart & Multi-Vendor 4.17.2 – 4.21.x, PHP 7.4 – 8.3 · Changelog: view

Pushes products, prices and stock from CS-Cart and Multi-Vendor to Google Merchant Center through the Merchant API, and shows Google’s status and item level issues next to every product.

What it does

Sends your products to Merchant Center with the Merchant API (productInputs), one API data source per country and language.
Initial full sync, then incremental sync when a product is saved, its price or stock changes, or it is disabled or deleted. Removed products are deleted at Google.
Safe retries: a timeout never creates a duplicate offer; failed work is retried after 5 minutes, 15 minutes, 1 hour, 3 hours and 12 hours; quota answers (HTTP 429) are respected.
Attribute mapping: GTIN, MPN, brand, condition, colour, size, gender, age group, and the Google product category per category (per storefront in Ultimate).
Reads back the Google status (approved, pending, partly approved, disapproved) and the item level issues, with Google’s help link, in a filterable list.
Multi-Vendor: one marketplace-level connection; vendors’ products are included with a vendor filter. Vendors cannot see or change the connection.
Ultimate: targets and mapping per storefront; products shared with a storefront are included, and every link uses that storefront’s own domain.
Links are always https and never depend on how the cron job runs; the Storefront URL setting pins the host.
“Remove all from Google” takes every offer of a target off Google (batch delete, idempotent); deleting a target or changing its language or feed label removes the old offers first.

Why direct sync, and how it fits with the file feeds

Google’s Content API for Shopping reached its sunset on 18 August 2026 and its endpoints are being switched off; the Merchant API is the replacement (Google’s sunset notice: developers.google.com/shopping-content/guides/sunset). File feeds are a different channel and keep working. Use the file-feed add-ons (Product Feed Pro for Google Merchant Center, Multichannel Product Feeds) when you want a scheduled file; use this add-on when you want changes at Google within minutes, products removed at once, and the status and issue report in your admin. Use one channel per country and language. If a file feed and this add-on both send the same country and language, Merchant Center receives every product twice with the same offer ID, and the two copies conflict. Let the feed serve some countries and this add-on others, or set the Offer ID prefix setting here and use a different feed label. The add-on shows a warning while one of our feed add-ons is active. It can read the Google category mapping of Product Feed Pro as a fallback.

Compatibility

CS-Cart and Multi-Vendor 4.17.2 to 4.21.x (Ultimate and Multi-Vendor editions).
PHP 7.4 to 8.3, depending on your CS-Cart version.
You need your own Google Cloud project with the Merchant API enabled, and a production Merchant Center account with a verified website. Google requires every Cloud project to be registered as a developer for the Merchant API once (an unregistered project gets HTTP 401 on every call); the Connection page registers it for you. Test accounts cannot be registered, and Google offers no sandbox, so a real account is needed to connect.
One connection means one Merchant Center account, which belongs to one website. Use targets for the countries and languages of that domain; storefronts on different domains need their own Merchant Center accounts (and their own installation).
The queue needs a cron job (a command line or a secret web address; see Configuration).

Next steps

Google, Google Merchant Center and Google Shopping are trademarks of Google LLC; this add-on is not affiliated with or endorsed by Google.