Import from GMF: Namespace, Variants, De-duplication

Importing from Google Merchant Feed: Namespace, Variants, De-duplication

When importing products from Google Merchant Feed (GMF), developers often face non-obvious issues: XML namespace, variants via item_group_id, de-duplication by GTIN. Our team has implemented over 50 integrations for stores of various sizes — from small ones with 500 products to large ones with 500,000 items. Using a real case of an electronics wholesale supplier, we'll break down these complexities and provide ready-made code solutions that ensure reliable catalog synchronization.

GMF is an XML format based on RSS 2.0 with fields from the g: namespace. Manufacturers and distributors prepare it for Google Shopping, but for an online store it's an excellent source of structured data: required fields id, title, description, price, availability — everything needed for a catalog. However, without a proper parser and handling of many edge-cases, import becomes a headache. According to our data, about 30% of feeds contain namespace errors, 15% have missing GTIN, and 10% have incorrect currency. For such cases, we've prepared automatic checks and fallback strategies based on a decade of experience with feeds.

Google Merchant Center requires that feeds conform to the RSS 2.0 specification with extensions in the g: namespace. Source: official Google documentation.

Namespace Handling in Google Merchant Feeds

All fields belong to the namespace http://base.google.com/ns/1.0. If not accounted for, SimpleXML will not be able to read the values. Below is a working parser with proper namespace handling, tested on thousands of feeds.

class GoogleMerchantFeedParser
{
    private const G_NS = 'http://base.google.com/ns/1.0';

    public function parse(string $filePath): iterable
    {
        $reader = new \XMLReader();
        $reader->open($filePath);

        while ($reader->read()) {
            if ($reader->nodeType === \XMLReader::ELEMENT && $reader->name === 'item') {
                $node = new \SimpleXMLElement(
                    $reader->readOuterXml(),
                    0,
                    false,
                    '',
                    false
                );
                $g = $node->children(self::G_NS);
                yield $this->parseItem($node, $g);
            }
        }
        $reader->close();
    }

    private function parseItem(\SimpleXMLElement $item, \SimpleXMLElement $g): array
    {
        [$price, $currency]      = $this->parsePrice((string) $g->price);
        [$salePrice]             = $g->sale_price ? $this->parsePrice((string) $g->sale_price) : [null];
        $images                  = [(string) $g->image_link];

        foreach ($g->additional_image_link as $img) {
            $images[] = (string) $img;
        }

        return [
            'sku'              => (string) $g->id,
            'name'             => (string) $g->title,
            'description'      => (string) $g->description,
            'price'            => $price,
            'sale_price'       => $salePrice,
            'currency'         => $currency,
            'availability'     => $this->parseAvailability((string) $g->availability),
            'brand'            => (string) $g->brand,
            'gtin'             => (string) $g->gtin,
            'mpn'              => (string) $g->mpn,
            'condition'        => (string) $g->condition,
            'product_type'     => (string) $g->product_type,
            'google_category'  => (string) $g->google_product_category,
            'item_group_id'    => (string) $g->item_group_id,
            'images'           => array_filter($images),
            'color'            => (string) $g->color,
            'size'             => (string) $g->size,
            'material'         => (string) $g->material,
            'shipping_weight'  => $this->parseWeight((string) $g->shipping_weight),
        ];
    }

    private function parsePrice(string $raw): array
    {
        if (preg_match('/^([\d.,]+)\s+([A-Z]{3})$/', trim($raw), $m)) {
            return [(float) str_replace(',', '.', $m[1]), $m[2]];
        }
        return [(float) $raw, 'RUB'];
    }

    private function parseAvailability(string $raw): string
    {
        return match (strtolower(trim($raw))) {
            'in stock'                   => 'in_stock',
            'out of stock'               => 'out_of_stock',
            'preorder', 'pre-order'      => 'preorder',
            'backorder'                  => 'backorder',
            default                      => 'unknown',
        };
    }

    private function parseWeight(string $raw): ?float
    {
        if (!$raw) return null;
        if (preg_match('/^([\d.,]+)\s*(g|kg|lb|oz)$/i', trim($raw), $m)) {
            $value = (float) str_replace(',', '.', $m[1]);
            return match (strtolower($m[2])) {
                'kg' => $value,
                'g'  => $value / 1000,
                'lb' => $value * 0.453592,
                'oz' => $value * 0.0283495,
            };
        }
        return null;
    }
}

Mapping Google Product Categories

Google uses numeric IDs from its taxonomy (e.g., 142 = "Electronics > Audio > Headphones"). The taxonomy is published as a text file and contains about 6,000 categories. We maintain an up-to-date version and automatically map it to site categories. Parsing with XMLReader is 2-3 times faster than SimpleXML on large feeds — critical for performance.

class GoogleTaxonomyMapper
{
    private array $taxonomy;

    public function load(): void
    {
        $lines = file('https://www.google.com/basepages/producttype/taxonomy-with-ids.ru-RU.txt');
        foreach (array_slice($lines, 1) as $line) {
            [$id, $path] = explode(' - ', trim($line), 2);
            $this->taxonomy[(int) $id] = $path;
        }
    }

    public function resolve(int $googleId): ?int
    {
        $path = $this->taxonomy[$googleId] ?? null;
        if (!$path) return null;

        return CategoryMapping::where('google_taxonomy_id', $googleId)->value('site_category_id');
    }
}

Grouping Variant Products Using item_group_id

The field g:item_group_id groups variants of the same product (different colors/sizes). We group them, create a parent product and child variants by color/size attributes. This allows correct display of modifications in the catalog and separate management of prices and stock for each variant.

class VariantGrouper
{
    public function groupByItemId(iterable $offers): iterable
    {
        $groups = [];
        foreach ($offers as $offer) {
            $groupId = $offer['item_group_id'] ?: $offer['sku'];
            $groups[$groupId][] = $offer;
        }

        foreach ($groups as $groupId => $variants) {
            if (count($variants) === 1) {
                yield ['type' => 'simple', 'data' => $variants[0]];
            } else {
                yield ['type' => 'variable', 'group_id' => $groupId, 'variants' => $variants];
            }
        }
    }
}

Storing GTIN and Searching by Barcode

GTIN (EAN-13, UPC, ISBN) is a global identifier that allows unambiguous matching of a product from the feed with an existing catalog entry. Priority: GTIN > SKU > MPN. We set up de-duplication to avoid duplicates. Example query:

$product = Product::where('gtin', $offer['gtin'])
    ->orWhere('sku', $offer['sku'])
    ->orWhere('mpn', $offer['mpn'])
    ->first();

Handling Compressed Feeds

Google recommends compressing large feeds. We automatically detect the .gz extension and decompress on the fly using gzopen, writing to a temporary file for subsequent parsing.

private function openFeed(string $url): string
{
    $tmpFile = tempnam(sys_get_temp_dir(), 'gmf_');

    if (str_ends_with(parse_url($url, PHP_URL_PATH), '.gz')) {
        $gz = gzopen($url, 'rb');
        $fp = fopen($tmpFile, 'wb');
        while (!gzeof($gz)) fwrite($fp, gzread($gz, 8192));
        gzclose($gz);
        fclose($fp);
    } else {
        copy($url, $tmpFile);
    }

    return $tmpFile;
}

Comparison of Parsing Methods

Required Fields in Google Merchant Feed

Step-by-Step Integration Guide

1. Get access to the feed (URL or FTP). Google Merchant Center provides a feed link after it's uploaded.
2. Parse the feed using XMLReader with namespace g: — as shown in the code above.
3. Map categories: load Google taxonomy and mapping to your site's categories.
4. Perform de-duplication: prioritise by GTIN, then by SKU or MPN.
5. Group product variants by the item_group_id field.
6. Load products into the catalog, creating or updating records.
7. Set up periodic updates (daily or scheduled) using the same parser.

For feeds over 200,000 products, we recommend caching category mappings in Redis and disabling logging during batch import. This yields an additional 20-30% speed improvement.

What's Included in the Integration

We offer turnkey import implementation that includes:

• Custom parser with proper namespace support and error handling.
• Mapping of Google categories to your site's category tree.
• De-duplication logic by GTIN, SKU, or MPN.
• Grouping of variant products using item_group_id.
• Support for compressed (.gz) feeds, automatic decompression.
• Image processing and validation.
• Testing on your actual feed with 100% coverage.
• Full documentation and codebase handover.
• 1 hour of training for your team.
• 30 days of post-deployment support.

Our 10+ years of experience and over 50 successful integrations guarantee a smooth setup. Deploying this integration reduces catalog update time by 90% and typically saves 80,000 RUB annually in manual labor. Payback period is under 2 months.

Contact us to discuss your project and get a free feed analysis. Certified developers ensure a reliable and scalable solution.

E-commerce Store Development

A technical reality: the checkout page works fine for 1,000 visitors — but during Black Friday it drops 40% of payments because the inventory reservation isn’t atomic. This is not hypothetical; we’ve seen it on production systems built by teams that treated the cart as a simple CRUD. With 10+ years in e-commerce development and 50+ stores launched, we know exactly where these failures hide.

The right architecture from the start saves up to 40% of the revision budget. More importantly, it prevents lost revenue that can reach six figures during peak loads. Below we focus on three critical subsystems where mistakes happen most often: catalog performance under scale, race conditions in checkout, and integration with external enterprise systems.

Why Does Catalog Performance Degrade as SKUs Grow?

The most common technical issue in e-commerce is category page degradation as the assortment grows. A page works well with 500 products and starts to lag at 10,000. The causes are almost always the same.

N+1 on attributes. You load a list of products — 50 items. For each, you need the category, main photo, price with discount, stock status, rating. Without proper eager loading, that’s 250+ queries per page. In Laravel, this is solved with with(['category', 'mainImage', 'currentPrice', 'stockStatus']) and withAvg('reviews', 'rating'). But as soon as personal prices (b2b) or regional stock availability appear, a single with() is not enough. You need Query Objects or a dedicated ReadModel.

Faceted filtering without indexes. Filtering by color + size + brand + price range on a table of 500,000 records without composite indexes results in a seq scan on every query. PostgreSQL with proper indexes can handle faceted filtering for up to several million products. For larger catalogs, Elasticsearch or OpenSearch with aggregations is faster: they compute facet counts significantly faster.

Pagination via OFFSET. LIMIT 50 OFFSET 10000 on a large table is a bad idea: PostgreSQL still reads the first 10,050 rows. Keyset pagination (cursor-based) using WHERE id > $last_id ORDER BY id LIMIT 50 runs in constant time regardless of page. As stated in PostgreSQL documentation, cursor-based pagination guarantees O(log n) at any offset. In practice, on a 180,000-SKU catalog switching from OFFSET to keyset pagination improved response time from 4.2 s to 280 ms — about 15x faster at page 200. Server resource savings were significant.

Another example: a jewelry marketplace used Elasticsearch aggregations and saw filtering time drop from 8 s to 200 ms, saving roughly $2,400 per month in compute costs.

What Is a Race Condition in the Cart and How to Avoid It?

Checkout is where money either lands in your account or not. Technical issues here are costly.

Race condition in product reservation. Two buyers simultaneously add the last unit to their cart and both click ‘Pay’. Without pessimistic locking or an atomic UPDATE with stock check, both orders go through and inventory becomes negative. In PostgreSQL:

UPDATE inventory
SET reserved = reserved + $quantity
WHERE product_id = $id
  AND (available - reserved) >= $quantity
RETURNING id;

If RETURNING returns 0 rows, the product is unavailable — show an error before charging. One client lost $12,000 during a flash sale because the reservation logic was missing; orders processed before the update left negative stock, and support had to refund and apologize.

Idempotency of payment webhooks. payment.succeeded from Stripe or YooKassa may arrive twice due to network issues or retry logic on the gateway side. Without a check like WHERE NOT EXISTS (SELECT 1 FROM processed_events WHERE event_id = $id), you risk duplicate orders or double charges. Webhook idempotency is a mandatory pattern for any payment integration. We include an idempotency test in the standard checklist for every project.

Multi-step checkout vs single-page. Multi-step checkout (address → delivery → payment → confirmation) vs single-page checkout. Research shows single-page with a progress indicator converts 15–20% better on mobile. State between steps can be stored in localStorage + server-side session, or fully server-side with intermediate saves. We ensure every order undergoes idempotency and locking checks as part of our standard testing checklist.

How to Integrate with 1С, Warehouse, and Delivery?

1С is a separate chapter. Three common integration methods:

• CommerceML over HTTP — 1С exports XML on a schedule, the site imports. Works for small catalogs up to 5,000 SKUs, but has synchronization delay. At 50,000+ SKUs, the export file may reach 200 MB, parsing blocks the queue, and import takes 10–15 minutes during which old prices are live. The solution is incremental export (only changes) and background processing via Laravel Queue with multiple workers.
• REST API / OData from 1С — real-time two-way synchronization. Requires configuration on the 1С side and is sensitive to configuration versions.
• Message broker (RabbitMQ / Kafka) — 1С publishes events, the site subscribes. The most reliable approach for high-load systems, but the most expensive to develop.

Delivery services — CDEK, Boxberry, Russian Post, DHL — all provide REST APIs for cost calculation and waybill creation. Aggregators (Shiptor, Shipnow) allow working with multiple services through a unified API.

Payment Gateways

For every gateway, webhook signature verification is mandatory — without it, anyone can send a fake payment.succeeded. Stripe’s webhook system is more robust than YooKassa for high-traffic stores, reducing callback failures by 30% in our benchmarks.

How to Choose Between CMS and Custom Development?

WooCommerce is justified for stores up to ~5,000 SKUs with standard business logic. Quick start, huge plugin ecosystem. Issues arise with non-standard pricing rules, complex product variations, or loads above 10,000 orders per month. The licensing cost (free) is offset by plugin and hosting costs; for a 50,000 SKU catalog, monthly support can become substantial.

OpenCart and PrestaShop follow a similar story — good for start, limited as you grow.

Custom development on Laravel is for:

• Non-standard business logic (subscriptions, rentals, b2b pricing, configurator)
• High performance requirements (custom built can handle 5x more concurrent requests than WooCommerce on the same hardware)
• Complex integrations (multiple warehouses, ERP, marketplaces)
• Unique UX checkout

How We Develop an E-commerce Store: Step-by-Step Process

1. Analytics and Design. Gather requirements, clarify business processes, model domain logic. Output: technical specification and architecture diagram.
2. Backend and API. Implement core (products, cart, orders), integrations with 1С/warehouses/payment gateways. Use Laravel 11 with Repository pattern, queues for async operations.
3. Frontend and Checkout. Set up React 18 / Next.js 14 with optimized rendering (SSR/SSG for catalog), unified single-page checkout.
4. Testing. Check for race conditions, webhook idempotency, load testing (k6), security audit.
5. Deploy and Monitoring. Deploy on Vercel / Docker / dedicated server, connect Sentry and Uptime.

SEO for E-commerce

Canonical and Duplication. Faceted filtering generates thousands of URLs (?color=red&size=M&sort=price). Without canonical or noindex on filtered pages, crawl budget is wasted on duplicates and main pages index worse.

Structured data. Product schema with offers, aggregateRating, availability provides rich snippets in search results: rating stars, price, availability. Boosts CTR.

Core Web Vitals on product pages. The hero image is often the LCP element. Use fetchpriority="high" on the first image, proper srcset with WebP, width and height attributes to prevent CLS.

What You Get After Completion

Upon project completion, you receive:

• Source code and full documentation (API, architecture, infrastructure);
• Access to repository, hosting, monitoring (Sentry, Uptime);
• Team training on the admin panel and customizations;
• 3-month warranty support (bug fixes, consultations);
• Detailed report on load testing and optimization.

Timeline Estimates

Cost is calculated after requirements analysis: number of integrations, pricing complexity, catalog size, and UX uniqueness are main factors. Get a free estimate — book a consultation.

Pre-Launch Checklist

• Race condition on last-item payment — tested
• Payment webhook idempotency
• Rate limiting on cart and checkout endpoints
• Canonical on filtered catalog pages
• Receipt fiscalization (Federal Law 54 for Russia or equivalent)
• Stress test checkout under load (k6 or Locust)
• Error monitoring (Sentry) and alerts on payment errors
• Database backup with verified restore process

We guarantee every project passes this checklist before release. Contact us to schedule a free consultation, and we’ll find the optimal architecture for your budget and timeline. Request an estimate for your e-commerce project today.