Google Merchant Feed vs Mirasvit Advanced Product Feeds: one channel, or every channel

Mirasvit sends a Magento catalogue to more than 130 shopping channels; Google Merchant Feed sends it to Google only. Both use Google's Merchant API v1. Here is when the narrow tool is enough and when it is not, with Amasty and Mageplaza for reference.

Guide

Most Magento stores that sell on Google Shopping use a feed manager: one extension that builds product feeds for many channels at once. Mirasvit Advanced Product Feeds is one of the established ones: its product page counts 265 reviews, 40 of them marked verified. Google Merchant Feed is ours and does one thing: it keeps a Magento catalogue in Google Merchant Center. The choice mostly depends on how many channels you sell on.

Everything about Mirasvit, Amasty and Mageplaza below was read on 2026-10-08 from the vendors' own pages and changelogs, and the Google API dates from Google's developer documentation. Prices change; check the vendor's page before you buy.

The short answer

Choose Mirasvit if you sell on more than Google: Meta, Bing, TikTok, marketplaces or regional price-comparison sites. Also choose it if you need supplemental, local inventory, regional inventory or promotion feeds, or if you run Magento 2.3.

Choose Google Merchant Feed if Google is your only feed channel and you do not need the breadth of a feed manager. It also suits a store that wants to choose per store view between a file Google fetches and pushing each product through the API.

The API question is settled for both

Google's Content API for Shopping reached its sunset on 2026-08-18. Requests without an extension started failing intermittently from 2026-09-01, and Google plans full decommissioning for early 2027, subject to revision. Merchant API v1beta was discontinued on 2026-02-28. Merchant API v1 is the current surface.

Both extensions use it. Mirasvit added "Google Merchant Center direct integration" through Merchant API v1 in version 1.13.0 (2026-05-12), and Amasty Product Feed migrated from Content API to Merchant API in 5.3.0 (2026-05-28). Google Merchant Feed was built on Merchant API v1 from the start. The API is not a reason to choose between these products.

Side by side

	Google Merchant Feed	Mirasvit Advanced Product Feeds
Price and licence	EUR 129.99; includes 12 months of updates and support, renewable; the licence to use it has no time limit	USD 179 (Open Source), 469 (Adobe Commerce), 759 (Cloud), including a year of updates and support; then USD 108, 282 or 456 a year for updates and support, cancel any time
Channels	Google Merchant Center only	130+ templates: Google, Meta, Bing, TikTok, Pinterest, eBay, ChatGPT and regional engines
How data reaches Google	Per store view: a static file Google fetches over HTTP (optional Basic authentication), or each product pushed over Merchant API v1 by a queue and cron	Feed URLs, FTP/FTPS/SFTP, and submission to Merchant Center through Merchant API v1
Merchant Center content	Products	Products, plus supplemental, local inventory, regional inventory, promotion, product review and merchant review feeds
File formats	XML (RSS 2.0), JSON, tab-separated	CSV, TXT, XML, JSON
Rules and checks	67 Google attributes mapped; per-product exclusion; feed preview; API log; a CLI dry run that prints the exact JSON body Google would receive	Filters by price, stock, category, SKU, images, any attribute; validation rules with quality status; email alerts; AI rewriting with your own key
Magento versions	2.4.7 - 2.4.9	2.3 - 2.4.9
Reviews	New, none yet	265 on its product page (4.9), of which 40 verified (4.7)

Where Mirasvit is the better choice

For most stores with more than one channel, it is. One extension, one set of rules and one schedule feed everything, where Google Merchant Feed would leave every other channel to another tool. Mirasvit also sends Merchant Center content types we do not support: local and regional inventory, promotions, reviews and supplemental feeds. It supports older Magento versions, it is actively maintained (1.15.15 on 2026-10-06), and it has a long review record.

Where Google Merchant Feed differs

It is narrower on purpose, and a few things follow from that.

What the price covers. Both include a year of updates and support in the first payment, both can renew it, and with both the extension keeps working whether or not you renew. Mirasvit renews updates and support at USD 108 a year on Open Source. Here, too, updates and support are renewable, and the licence to use the extension has no time limit.

Delivery is chosen per store view. One store view can publish a file that Google fetches, needing no credentials, while another pushes each product through the API with its own Merchant Center account. Each store view can also point at a sandbox account.

What it sends is visible before it is sent. The dry run prints the exact request body. Three fields Google's Merchant API v1 has no place for (tax, tax category, ships-from country) are written to the feed file only, and the documentation says so rather than dropping them silently.

What it does not do. No other channels, no promotion or local inventory feeds, no supplemental feeds. Our FAQ lists these as reasons to choose something else.

Amasty and Mageplaza, for reference

Amasty Product Feed: USD 249 for the first year on Open Source, then USD 155 a year. It covers several channels and syncs with Merchant Center through Merchant API since 5.3.0. Amasty states that the Merchant API upload needs an active subscription.
Mageplaza Product Feed: USD 179 on Community, then USD 89.5 a year. It covers Google, Meta, Bing, Amazon and eBay and has 56 reviews at 5.0. Its release notes speak of a "Google Shopping API" without saying whether that means Merchant API or the sunset Content API; ask the vendor if API sync matters to you.

Sources, read 2026-10-08

How Google Merchant Feed works is in its documentation; the extension is on its product page.