XML product feeds for marketplaces and Google Merchant Center

I prepare product exports from stores, business systems or spreadsheets for selected sales channels. Work covers catalogue selection, field mapping, variants, images and scheduled updates. Checks include XML syntax, data content, link access and the actual import result.

Discuss this serviceWork included in this service

Feeds tailored to each channel

An XML extension does not make a file suitable for every platform.

  1. Format, purpose and delivery method

    I establish the platform, categories, language, country and delivery method, then review its current specification. XML, YML, CSV and APIs serve different purposes; we select a supported option. Product feeds describe offers, while orders and statuses require a separate integration when needed.

Preparing the product data source

A working feed starts with accurate product data, not merely an export module.

  1. Fields, categories and exclusions

    I review the CMS, spreadsheet or business system, mapping fields and identifying gaps. Categories, brands and individual products can be selected. Incomplete items can be excluded with reasons. Automated data and fields needing editorial work or owner confirmation follow separate rules.

Google Merchant Center product feed

Product data must match the landing page and target market requirements.

  1. Identifiers, price, availability and images

    I prepare the supported format and required attributes, including ID, title, description, URL, image, price and availability. Brand, GTIN, MPN and additional fields follow applicable rules and verified sources. Identifiers are not invented. Language, currency and variants are checked against landing pages, with delivery configured through supported settings.

XML for Rozetka, Prom.ua and other platforms

Categories and attributes must map to the receiving catalogue, not just your site menu.

  1. Adapting exports to the platform catalogue

    I review product creation and update workflows, offer structures, categories and attributes. Names, specifications, variants and images are mapped accordingly. Rozetka follows the chosen XML and Pricecreator workflow; Prom.ua uses its supported import. Each platform needs its own project-specific validation.

Variants, SKUs and stable identifiers

Renaming a product should not create a new offer on each update.

  1. Models, sizes, colours and bundles

    I define product and variant identities using the receiving rules, preserving source catalogue links. Images, prices and stock are checked per variant. Supported grouping is used where appropriate. SKU changes, duplicate merges and product withdrawal follow explicit rules to avoid unmanaged offers.

Links, images and product pages

The recipient must be able to fetch images and reach the correct product.

  1. Access and product matching

    I check page and image URLs, response codes, redirects and variant matching. Agreed image work covers cropping, backgrounds, colour, dimensions and optimization. Missing files and wrong contents are different errors that both need correction. Access settings account for automated-request protection.

Scheduled feed updates

File generation and platform retrieval schedules should work together.

  1. Updates without empty or partial files

    I configure generation, publication, result checks and failure notifications. We agree intervals, size limits and source-outage behaviour. A valid feed should not be replaced accidentally by a partial export. Large catalogues need processing suited to server resources and recipient limits.

Feed errors and rejected products

Valid XML can still contain wrong prices, categories or incomplete information.

  1. From platform diagnostics to source corrections

    I trace diagnostic messages to records and fix the source or export rules, then check the import again. Website, business-information and account-policy issues become separate tasks. A feed does not guarantee approval, reinstatement or ad delivery.

Feed preparation and delivery

Delivery includes export rules, an update process and documented limitations.

  1. Requirements and sample

    I review the source and specification, map fields and prepare a sample with representative products.

  2. Full export and import

    I configure generation and updates, then check structure, completeness and import into the agreed service.

  3. Handover and future updates

    I hand over the URL or file, rules and maintenance instructions. New channels and requirement changes receive separate estimates.

Product feed pricing

Pricing depends on sources, data quality, variants, channels and automation.

  1. Data preparation and export mechanism

    The scope separates module setup or generator development, data cleanup, images and channel connection. Existing modules may need configuration or development. Paid extensions and ongoing maintenance are separate. An estimate requires source details, sample products, catalogue size and the target channel.

Questions about product feeds

Not always. Recipients use different schemas and requirements. One source can generate separate channel feeds.

A file can be prepared, but seller and landing-page requirements still apply. Merchant Center needs an appropriate sales model and product pages.

Yes. I review the file, source, module and diagnostics, then correct the origin so updates do not reintroduce the error.

Yes. We define category, brand, stock or item rules and verify the receiving platform’s behaviour.

We check product origin and applicable identifier rules. Fake codes are not used; missing GTIN follows the permitted requirements.

Yes, when the source and platform support it. Intervals, checks and delay handling follow an agreed design.

Not necessarily. Suspensions can concern the website or business information. We review the notice separately; the platform decides.

This is a separate area. Campaigns and analytics can be added after catalogue preparation and account checks.

Other services for this project

  1. Catalogue and product content

  2. Ecommerce integrations

  3. Google Merchant Center preparation

  4. Rozetka store development service

Platform and service documentation

These are official sources for requirements and capabilities. Their applicability is checked before configuration; external service conditions can change.

  1. Google: product data specification

  2. Rozetka: seller documentation

  3. Prom.ua: working with product catalogues

Prepare feeds for your sales channels

Specify the catalogue source and target platforms. For an existing feed, describe the import problem.

    Form details are used to respond to your enquiry. See the policy on personal data processing.

    A general description and links are enough to begin. Do not send passwords, API keys or customer personal data through this form.