Skroutz vs Google Shopping: Why One Feed Doesn't Fit Both
Same products, two completely different XML formats. Here's what actually differs between a Skroutz feed and a Google Shopping feed — and how to stop maintaining both by hand.
Edit XML Free →Skroutz vs Google Shopping: Field-by-Field Differences
- Tag naming. Google Shopping uses g:id, g:price, and g:availability with the g: namespace prefix. Skroutz uses plain tags like Id, Price, and Availability — no namespace, different casing.
- Availability values. Google expects values like in stock, out of stock, or preorder. Skroutz expects a numeric stock quantity or its own availability codes.
- Category structure. Google Shopping requires mapping to the Google Product Taxonomy using the google_product_category tag. Skroutz uses its own category tree, matched separately during onboarding.
- Identifiers. Google strongly prefers GTIN, MPN, and brand for identifier-exists compliance. Skroutz requires a manufacturer or brand field and often a local SKU.
- Price formatting. Google requires price and currency in one field, for example 15.00 EUR. Skroutz typically separates price and currency, or expects plain decimal values.
Because the tag names, required fields, and even category systems differ, a feed built for one rarely validates on the other without manual rework — which is exactly what field mapping automates.
Generate Both Formats from One Source
- NodeXML knows the tag structure Skroutz and Google Shopping each require and maps your fields automatically.
- Match your product categories to each marketplace's taxonomy without manual lookup tables.
- Get a g:-namespaced feed for Google and a plain-tag feed for Skroutz, both generated from the same source.
- Update your source feed once — both outputs update automatically.
FAQ
Q: Can I use my Google Shopping feed directly on Skroutz?
A: Not without changes — the tag names, availability values, and category system are different. You’ll need to remap the fields for Skroutz’s format.
Q: Do I need to redo my category mapping for each marketplace?
A: With NodeXML, you map once and it applies the equivalent category structure to each marketplace output.
Q: Which fields cause the most validation errors between the two?
A: Availability values and category IDs are the most common mismatches, since each marketplace expects different formats and taxonomies.