Blog
News, releases and case studies from AdCore Turbo
VTEX XML integration with Google Shopping: keep it, switch to the connector or use a feed manager
VTEX XML integration for Google Shopping: how the XML works, what VTEX recommends instead and when a feed manager makes sense for a large catalog.
Integration hub, PIM or feed manager: what each one solves in your catalog
A marketplace integration hub, a PIM and a feed manager look alike. What each solves in your catalog and which operational problem needs which tool.
Signs your catalog needs a PIM and what to evaluate before you buy one
When to get a PIM: the signs that spreadsheets, ERP and the store admin no longer handle your product data, and what to ask before you choose one.
AI product descriptions: scale without losing control of what goes live
AI product descriptions written from your attributes and reviewed by a person before going live: a process to gain scale without inventing data.
Product setup in VTEX: what to have ready before you publish
VTEX product setup without rework: how to prepare product, SKU, specifications, category and images before publishing to the store and the channels.
Disapproved products in Merchant Center: recurring causes and how to catch them early
Disapproved product in Google Merchant Center: identifier, price, image or missing attribute. How to find the cause and fix it in the product record.
Product feed for Google: the fields that decide whether an item shows up
Google product feed explained: what it is, which Merchant Center fields matter most and where a large catalog's feed tends to break before a rejection.
Product photos for e-commerce: one master file and one version per channel
Product photos for ecommerce organized as a master file and per-channel versions, linked to the SKU, so you stop cropping the same image over and over.
GTIN and EAN in e-commerce: what channels require and what to do with a SKU that has no code
GTIN and EAN: what the code is, why Google and marketplaces require it, and how to handle variations, bundles and products with no code before a rejection.
Product attributes: one dictionary for your store, marketplaces and Google
Product attributes describe every item in your catalog. How to build a dictionary by family that serves the store, marketplaces and Google at once.
Standardizing product data: where to start when the catalog has grown
Product data standardization: one rule for names, units and values, attributes out of the title, completeness by family and fixes made in batches.
What a Product Data Hub is and why retailers need one
Product data hub: one product record that the store, marketplaces and media channels read from. Fix a product once, instead of one spreadsheet per channel.
From one catalog to many channels: how modern feed management works
Product feed for many channels: how to translate your catalog to each destination's rules and what to expect from a feed manager before you buy one.
PIM and DAM in the same place: the hidden cost of separating product data and media
PIM and DAM for ecommerce: the PIM holds product data, the DAM holds photos, video and PDFs. Together, the photo is a SKU attribute and the patchwork ends.