VTEX to Google Shopping Feed Automation
VTEX separates products, SKUs and specifications across several APIs. Exporting that structure by hand produces flat feeds that lose variants and technical attributes. IRONFEED reassembles the catalog before Google sees it.
Group complex multi-SKU catalogs, map VTEX specification fields to Google attributes and refresh the feed as soon as the catalog changes.
Why the default VTEX sync breaks
Variants flattened into duplicates
Without item_group_id, every VTEX SKU competes as a standalone product and Google treats near-identical entries as duplicate offers.
Specifications never reach the feed
Color, size, material and model live in VTEX specification groups. Generic exports drop them, so required apparel attributes are missing.
Stale catalogs after every price rule
Trade policies and price tables change often. A nightly export leaves Merchant Center advertising yesterday's prices and availability.
Live in three steps
Connect your store
Authorize IRONFEED through the platform app or a scoped API key. The catalog is read directly, with no export files to maintain.
Set transformation rules
Map fields, build titles, normalize images and prices, and define custom label and exclusion rules once. They run on every sync.
Publish the live feed URL
Register the IRONFEED URL in the destination channel. Every refresh delivers a validated catalog with no manual re-upload.
VTEX → Google Shopping attribute mapping
| VTEX field | Google Shopping attribute | IRONFEED automated handling |
|---|---|---|
| sku.id | id | Stable per-SKU identifier across catalog rebuilds |
| product.id | item_group_id | Automatic variant grouping from the parent product |
| specification.Color / Size | color, size | Specification extractor with value normalization |
| categoryTree | google_product_category | Category-path to Google taxonomy matcher |
| sellers[].commertialOffer.Price | price, sale_price | Seller and trade-policy aware price selection |
Google Merchant Center errors this integration prevents
Missing value [google_product_category]
Your internal category tree is built for navigation, not for Google's 5,000-node taxonomy. Nothing in a storefront maps one to the other automatically.
View fix & ruleMissing value [color] / [size] / [age_group] / [gender]
Variant options are free-text in every storefront. One catalog has Colour, another Color, a third stores the shade inside the title, and none of them carry age_group or gender at all.
View fix & ruleMismatched value [availability]
Stock is the fastest-moving attribute in any catalog. Scheduled exports lag behind sales, and backorder or pre-order states have no direct equivalent in the storefront's boolean stock flag.
View fix & ruleVTEX to Google Shopping FAQs
See what your VTEX feed looks like to Google Shopping
Run the free audit and get the failing checks, product counts and the exact rule that fixes each one.