Google Shopping Feed Template: The UK SME Guide

You've updated a product price on your website, but Merchant Center still shows the old figure. A popular item has gone out of stock, yet the listing keeps attracting clicks. Then disapprovals appear, and nobody can tell whether the problem sits in the spreadsheet, the ecommerce platform, shipping settings or the product page.

That's why a Google Shopping feed template needs to do more than hold product rows. For a UK SME, it should act as a controlled operating process for product information, with VAT-inclusive GBP pricing, accurate availability and documented ownership of updates. Get that structure right and you give Shopping ads and free listings dependable data. Get it wrong and even a well-managed campaign can send shoppers to an inconsistent buying experience.

Why Your Feed Is More Than Just a Spreadsheet

A feed is the connection between your catalogue and Google's commerce surfaces. It supplies the product details used for Shopping ads and free listings, so a missing attribute or stale value can affect whether an item is eligible and whether the information shown to shoppers is trustworthy. The Google Merchant Center feed guidance from PPC Geeks is useful background, but the operational point is straightforward: the feed reflects how well your business controls its product data.

Consider a retailer selling home accessories. The website changes a lamp from one price to another during a promotion, while the manually maintained feed keeps the previous value. A shopper clicks the listing, reaches the product page and sees a different price. That creates a customer service problem even if Merchant Center hasn't yet issued a formal disapproval. If stock changes during the same period, the feed can also promote an item that can't be bought.

Treat product data as a process

The spreadsheet is only one part of the system. Someone must decide which platform owns the price, how VAT is applied, when availability is refreshed, who checks warnings and what happens after a correction. Without those decisions, the same SKU can carry different values in the feed, website, checkout and shipping configuration.

A strong template gives every product a stable row structure and makes exceptions visible. It should help a team answer practical questions quickly:

• Which source is authoritative? Is the price pulled from Shopify, WooCommerce, an ERP or a manually approved promotion file?
• Who checks the exceptions? Assign responsibility for missing identifiers, broken URLs, price differences and unavailable products.
• What happens after an edit? Reprocess the feed and confirm that the landing page and Merchant Center values agree.

Practical rule: Never judge feed quality from the spreadsheet alone. Check the product page and checkout, because that's where the shopper experiences the data.

A compliant feed therefore protects more than account status. It reduces the chance that ad spend supports products with inaccurate pricing, unavailable stock or incomplete information. It also creates a reliable base for later decisions about product groups, margins and campaign priorities.

Building Your Google Shopping Feed Template

Start with a Google Sheet if you manage a smaller catalogue and need a transparent working format. Google Sheets is commonly used for smaller catalogues, while CSV, TSV and XML are also supported, as outlined in UK Google Shopping setup guidance. The format matters less than disciplined field mapping, validation and update ownership.

Map the core attributes first

For the UK, build the header row around these 11 core attributes:

1. id. Give every SKU a stable identifier. Do not change it just because a title or price changes.
2. title. Describe the product clearly, including the details that distinguish one item from another.
3. description. Use accurate product information that matches the landing page.
4. link. Point to the relevant product page, not a generic category page.
5. image_link. Use the main product image that shoppers will see.
6. price. Format the value in GBP and make it VAT-inclusive for UK listings.
7. availability. Reflect the actual stock state, such as in stock, out of stock or preorder where applicable.
8. condition. State whether the item is new, refurbished or used.
9. brand. Use the actual manufacturer or brand information.
10. gtin/mpn. Provide the relevant identifier where one exists.
11. google_product_category. Apply an appropriate Google category to help classify the product.

Use the column names consistently. Don't mix internal labels such as “stock status” with the required availability field unless your export process translates them reliably. Keep formatting rules beside the template, including allowed availability values, identifier handling and the treatment of variants.

Add UK checks before submission

The price column should show the amount a UK shopper expects to pay, with VAT included and the currency expressed as GBP. Review shipping settings separately and confirm that delivery costs match the checkout experience. Many feed problems become operational rather than editorial here, because a perfectly written title can't compensate for inconsistent commercial information.

Google Sheets works well when one person can review changes and the catalogue doesn't change constantly. As the range of products, variants and promotions grows, add controlled fields such as product type, variant grouping and custom labels. The guide to custom labels for Google Shopping explains how those fields can support more useful campaign segmentation.

A practical template should also include a change log. Record who changed a price, when availability was updated and whether the item was reprocessed after the edit. That small discipline turns a static file into an auditable workflow.

For a visual walkthrough of feed construction, use the video below.

Avoiding the Synchronization Trap

The most persistent feed failures aren't always caused by one bad field. They often happen because the website, catalogue export and Merchant Center update at different times. A corrected spreadsheet won't solve the problem if the next platform export overwrites it with the old value.

Use a fixed verification sequence after any significant product-data change:

1. Check the landing page first. Confirm the product is available, the displayed price is correct and the page loads without an access problem.
2. Compare the source data. Match the website value against the row in the feed, including currency, decimal formatting and stock status.
3. Check delivery settings. Make sure the shipping information in Merchant Center agrees with what the shopper sees at checkout.
4. Reprocess after the correction. Don't assume an edit has taken effect just because the source file changed.
5. Review diagnostics. Look for account-level warnings before working through individual items.

Implementation advice for Google Merchant Center feeds recommends synchronising feed updates with website price and availability changes. It also identifies automatic item updates and the Content API as ways to reduce mismatch risk. Newly uploaded products can remain pending for up to 72 hours while quality checks run, so plan changes with review time in mind.

Data should have one owner and several checks. If the website owns price and stock, the feed should inherit those values rather than recreate them manually.

A useful test is to select a sample of products after each deployment. Include a standard item, a variant, a promotional product and an item near the end of its stock. Compare the feed row, product page and checkout. This won't replace automated validation, but it catches mapping errors that a spreadsheet review can miss.

The Content API can help businesses push changes programmatically, particularly where inventory changes quickly. It isn't a substitute for governance, though. Poor source data sent automatically is still poor data, only distributed faster.

Spreadsheets vs. API Solutions

Google Sheets has a clear advantage for a small UK retailer. It's visible, familiar and easy to edit without a development project. It also gives a business owner direct control over titles, descriptions and category decisions while the catalogue is manageable.

The weakness appears when several people edit the file, prices change frequently or stock comes from a separate system. Manual updates can introduce inconsistent identifiers, overwritten changes and delays between the website and Merchant Center. A spreadsheet also relies heavily on someone remembering to check every relevant row.

An API-driven setup takes more planning at the start. You'll need dependable product mappings, error handling and someone who understands the ecommerce platform and Merchant Center relationship. In return, the system can pass price and availability changes from the source catalogue without asking a team member to maintain duplicate rows.

Don't choose an API because it sounds more advanced. Choose it when the cost of repeated manual checking, stale stock or delayed price changes is greater than the cost of building and maintaining the connection. The UK product feed management tools comparison can help frame that decision around catalogue complexity and operational capacity.

Turning Your Feed into a Profit Tool

Compliance gets products eligible. Commercial structure helps decide where advertising budget should go. A feed can classify products according to margin, stock position, seasonality, range priority or promotional status, provided those classifications come from real business data rather than guesswork.

Start by agreeing the labels with finance, merchandising and PPC teams. For example, a custom label could distinguish high-margin products from low-margin products, while another could identify clearance stock or a limited promotion. The exact label names don't matter. Consistent definitions do.

Build rules the campaign can use

A useful structure might look like this:

• Margin group. Separate products by the contribution they make after product costs.
• Stock group. Highlight products that need controlled exposure because availability is limited.
• Range priority. Identify core products, new arrivals and clearance lines.
• Promotion state. Mark products with an approved offer and a defined end date.

Apply the rules at the SKU or variant level where performance and profitability differ. Two colours of the same product might have different stock levels, while two products in one category can have very different margins. A category-level rule is efficient, but it can hide those differences if you apply it too broadly.

A feed should answer a budget question, not just a compliance question. Which products should receive more exposure, and which products should be restricted until their economics improve?

Keep commercial labels separate from required attributes. Don't put margin information into a title or description, and don't alter customer-facing copy to force campaign segmentation. Use custom labels and product groups to pass the internal logic into campaign structure while keeping the listing accurate.

Then connect campaign decisions to actual business outcomes. Review whether high-priority products generate profitable sales, whether clearance lines need different targets and whether low-margin products are absorbing spend without a commercial reason. Google Shopping ads management from PPC Geeks is one route for businesses that need feed structure and campaign management considered together.

Maintaining Feed Health Long-Term

A template stays reliable only when someone checks it on a schedule. The right cadence depends on catalogue activity, but a UK-focused audit approach recommends weekly diagnostics for high-volume feeds and monthly deep checks for smaller catalogues. Add extra reviews before seasonal peaks, platform migrations or major catalogue changes, as recommended in this Google Shopping feed audit checklist.

Use a layered diagnostic routine

Weekly checks should focus on immediate threats. Review account-level warnings first, then item-level disapprovals, price mismatches, availability issues and failed fetches. Account settings can affect many products at once, so fixing those warnings may be more effective than editing individual rows.

Monthly checks should examine the quality of the underlying data. Sample titles, descriptions, images, categories and identifiers across product types and variants. Look for repeated formatting errors, missing recommended attributes and products that have changed on the website but not in the source feed.

Before a seasonal peak, test the complete path from source catalogue to product page and checkout. Confirm promotional prices, delivery settings, stock rules and returns information. A feed that worked for the core range may fail when a new promotion introduces different data or timing.

After a migration, compare old and new identifiers, URLs, categories and variant relationships. Don't delete the previous process until the replacement has been checked in Merchant Center and against live landing pages.

Maintain a simple issue register with the affected SKU, error message, source of the correction, owner and resolution date. That record helps distinguish a one-off mistake from a recurring integration fault. It also makes handovers easier when the person who manages the feed is away.

Monitor warnings before they become a catalogue-wide interruption. Early diagnosis gives you more options than emergency manual editing.

Reprocess the feed after each material correction and confirm that the change reaches the product page, source file and Merchant Center. Keep the template rules documented, including VAT treatment, GBP formatting, shipping alignment, identifier policy and the process for automatic updates. That governance is what keeps a Google Shopping feed template useful after the initial upload.

PPC Geeks can review your product data, support Merchant Center, optimise feed structure and connect feed decisions with Google Shopping campaign management. Visit PPC Geeks to request an audit and discuss a practical plan for keeping your UK feed accurate, compliant and commercially focused.