Use this guide to format your local inventory information for Merchant Centre. Google uses this data to know which shops have each of your products. Sharing your local inventory data in the correct format is important for creating successful ads and free listings for your products.
In this article
Product data attributes:
Note: Not providing a required attribute may prevent that particular product from showing up in results.
It can take up to 24 hours to sync your business locations to your Merchant Centre account, so we recommend that you upload your inventory feed 24 hours after linking accounts or after a shop code is changed or updated in your Business Profile.
Formatting your product data
Use English when submitting the names of attributes and the values for attributes that use supported values. For example, the availability [availability] attribute uses the supported values in stock, limited availability, on display to order and out of stock, which must be submitted in English in order for the system to read them.
Definitions
Required: Submit this attribute. If you don't, your in-store product won't be able to serve in local inventory ads and free local listings.
It depends: You may or may not need to submit this attribute depending on the product or the countries in which your products are shown.
Basic inventory data
|
Attribute and format
|
Minimum requirements at a glance
|
|
ID [id]
Your product's unique identifier
Required
Example
A2B4
Syntax
Max 50 characters
Schema.org property: Yes (learn more about merchant listing (product, offer) structured data on Google Search Central) |
- If you sell the same item in multiple shops, the same ID appears for multiple shop codes. You should include one ID
[id] attribute per shop and change the other attributes accordingly
- Use the same ID values in both your product data and local inventory data.
- Only include the products that are generally available for purchase in shops.
|
|
Shop code [store_code]
Your shops unique identifier
Required
Example
A2B4
Syntax
Max 64 characters
Schema.org property: Yes (learn more about merchant listing (product, offer) structured data on Google Search Central) |
- This attribute is case-sensitive
- Must match the shop codes that you submitted in your Business Profile.
|
|
Availability [availability]
Your product's availability in store
Required
Example
in_stock
Supported values
- In stock
[in_stock]
- Limited availability
[limited_availability]
- On display to order
[on_display_to_order]
- Out of stock
[out_of_stock]
Schema.org property: Yes (learn more about merchant listing (product, offer) structured data on Google Search Central) |
- Accurately submit the product's availability and match the availability to what is in your shops.
|
|
Price [price]
Your product's price in that shop
Optional
Example
15.00 GBP
Syntax
Schema.org property: Yes (learn more about merchant listing (product, offer) structured data on Google Search Central) |
- Submit price if your item has a different price per shop
- The inventory data price will override the price in the product data feed for the associated shop.
- Accurately submit the product's price and currency and match it with the price from your shops
- Ensure that the product can be purchased in store for the submitted price.
- For products sold in bulk quantities, bundles or multipacks.
- Submit the total price of the minimum purchasable quantity, bundle or multipack.
- For the US and Canada:
- Don't include tax in the price.
- For all other countries:
- Include Value Added Tax (VAT) or goods and services tax (GST) in the price.
|
|
Sale price [sale_price]
Your product's sale price
Optional
Example
15.00 GBP
Syntax
Schema.org property: No
|
- Meet the requirements for the price
[price] attribute.
- Submit this attribute (sale price) in addition to the price
[price] attribute set to the non-sale price.
- Accurately submit the product's sale price and match the sale price from your shops.
|
|
Sale price effective date
[sale_price_effective_date]
The date range during which the sale price applies
Optional
Example
(for UTC+1)
2016-02-24T11:07+0100/
2016-02-29T23:07+0100
Syntax
- Max 51 alphanumeric characters
- ISO 8601
YYYY-MM-DDThh:mm [+hhmm]YYYY-MM-DDThh:mmZ
- Separate the start date and end date with '/'
Schema.org property: No
|
- Use together with the sale price
[sale_price] attribute.
- If you don't submit this attribute (sale price effective date), the sale price always applies.
- Use a start date before the end date.
|
|
The loyalty programme [loyalty_program]
The loyalty programme [loyalty_program] attribute allows the setting up of shop-level member prices and local delivery in local inventory ads (in beta).
Optional (available for Australia, Japan, the United Kingdom, Germany, France, Canada, Mexico, Brazil and the United States only)
Example
my_loyalty_program:silver:10 GBP:”2025-05-11T00:01:59-0800/2025-06-21T22:13:59-0800”:free_member_delivery
Syntax
This attribute uses the following sub-attributes:
- Programme label
[program_label] (optional for single-tier merchants)
The loyalty programme label set in your loyalty programme settings in Merchant Centre.
- Tier label
[tier_label] (optional for single-tier merchants)
The tier label set in your programme settings in Merchant Centre, used to differentiate the benefits between each tier.
- Price
[price] (optional): The member-specific price for the programme and tier. This will be displayed alongside the non-member price to give shoppers an idea of the benefits of joining your programme. This attribute should be used for free-of-charge and paid memberships.
- Member price effective date
[member_price_effective_date] (optional): This sub-attribute allows merchants to specify when their member pricing benefit begins and ends.
- Delivery label
[shipping_label] (optional): This sub-attribute allows merchants to specify which offers are eligible for loyalty delivery. Choose your own definition for this value.
|
- Ensure that member prices are clearly accessible on your website for members, whether through a loyalty overview page, a dedicated event page or otherwise clearly communicated to members.
- Ensure that member prices match between your product data source, landing page and checkout.
- If you only have one tier in your loyalty programme, you don't need to submit the programme label
[program_label] and tier label [tier_label] attributes.
- Programme label
[program_label] and tier label [tier_label] are case-insensitive.
- Shop-level member pricing will override the price in the product data feed. If no shop-level member price is provided, the price from the product data feed will be shown.
- Only these five sub-attributes are supported in the local inventory feed. Adding additional sub-attributes such as loyalty points
[loyalty_points] will lead to a feed error.
|
|
Quantity [quantity]
The number of items in stock for the shop
Optional
Example
5
Syntax
Schema.org property: No
|
- If you choose to submit quantity and availability, inventory is classified based on the lower value between your availability and quantity.
- Google considers 'in stock' items to be those with three or more available, 'limited availability' to be one to two available and 'out of stock' to be 0.
|
Click and collect data
Add these attributes to your local product inventory feed for shop-specific collection information. Must be provided when using pick up today or pick up later with in-store inventory data.
|
Attribute and format
|
Minimum requirements at a glance
|
|
Collection method [pickup_method]
Specify the collection option for this item
 Optional shop-specific collection information
Important: From 1 September 2024, collection method [pickup_method] is optional to enable click and collect for your offers.
Example
buy
Supported values
- Buy
[buy]
- Reserve
[reserve]
- Deliver to shop
[ship to store]
- Not supported
[not supported]
Schema.org property: No
|
- Optional for all of the items in your feed that can be collected in store.
- The inventory collection method will override the collection method in the product data feed for the associated shop.
|
|
Collection SLA [pickup_sla]
Specify the expected date that an order will be ready for collection, relative to when the order is placed.
Required shop-specific collection information
Example
same day
Supported values
- same day
[same day]
- next day
[next day]
- Two-day
[2-day]
- Three-day
[3-day]
- Four-day
[4-day]
- Five-day
[5-day]
- Six-day
[6-day]
- Multi-week
[multi-week]
Schema.org property: No
|
- Required for all of the items in your feed that can be collected in store.
- Accurately submit the product's collection SLA and match the collection SLA from your landing page and checkout pages.
- The inventory collection SLA will override the collection SLA in the product data feed for the associated shop.
|
Local delivery
|
Attribute and format
|
Minimum requirements at a glance
|
|
Local delivery label [local_shipping_label]
Optional
The label that you assign to a product to help assign correct delivery costs in your Merchant Centre account settings
Example
Same day
Syntax
Max 100 characters
Schema.org property: No
|
- If you want to enable same-day delivery where only some of your in-store inventory in a particular shop is available for same-day delivery, the local delivery label
[local_shipping_label] attribute must be added to your local inventory data.
- The value submitted for this attribute should be the name of the same-day delivery label or labels that you've created in your account-level same-day delivery settings.
- Each same-day delivery label represents one unique group of same-day delivery settings and will be added to the selected eligible products in your local inventory data.
- This attribute is optional if either all of your shops and all of your products offer same-day delivery, or if all of your products in a list of eligible shops offer same-day delivery.
|