The local products inventory feed is a list of the products you sell in each store. Some attributes are required for all items, some are required for certain types of items, and others are recommended.
Inventory price and quantity can change frequently and on a store-by-store basis. Please increase the feed frequency to carry out more frequent updates of your inventory data. Please contact our support team using the contact form in case you encounter issues with your feed frequency.
To submit product data through API, learn more about the Google Content API.
Submit local product inventory feeds
File type: The local product inventory feed is available as a tab delimited text file, XML file or via API.
Create a new local product inventory feed: To create and register a new local product inventory feed, follow these instructions.
Important: Some attributes in this local product inventory feed spec contain spaces and underscores. To make sure you submit attributes with correct characters and spacing, follow the guidelines below for your file type:
- Tab-delimited feeds: Spaces are required. If the attribute has underscores, use a space instead of the "_".
- XML API or JSON API: Underscores are required, and are converted into whitespace when received.
Summary of attribute requirements
| Attribute | Submission requirements | |
|---|---|---|
| Required inventory details |
Store code Quantity |
Required for all products. Note: The store code If you’re implementing the merchant-hosted local storefront (full) feature, then you must submit the price |
| Optional inventory details |
Recommended as applicable to each item in your feed to give more details about price, quantity, and availability. Note: If you choose to submit availability |
|
| Optional store pickup details |
Pickup method Pickup SLA |
Recommended as applicable to all of the items in your feed that can be picked up in-store. |
Required inventory details
These attributes describe basic inventory information per item per store.
[store_code] - The store identifier from Business Profiles
A unique alphanumeric identifier for each local business. This attribute is case-sensitive and must match the store codes that you submitted in your Business Profiles.
When to include: Required for all of the items in your feed.
| Type | Text (string) |
| Text/tab delimited example | Store123 |
| XML example | <g:store_code>Store123</g:store_code> |
[store_code] submitted through the Shopping Content API that contain leading zeroes will be truncated (i.e. 001 -->1, 090 --> 90), which will lead to a mismatch between your inventory data and Business Profiles. You can instead submit your inventory data using delimited feeds or remove leading zeros from the store codes in your Business Profiles.[id] - An identifier of the item
A unique alphanumeric product identifier for an item across all of your stores.
If you sell the same item in multiple stores, the same ID appears for multiple store codes. You should include one ID [id] attribute per store and use the quantity [quantity] attribute to indicate how many of each item is in stock in that store.
If you have multiple feeds of the same type for one country, IDs of items within different feeds must still be unique. If your SKUs are unique across your inventory and meet the requirements below, we suggest you use your SKUs for this attribute.
When to include: Required for all of the items in your feed.
| Type | Text (string) |
| Text/tab delimited example | 421486 |
| XML example | <g:id>421486</g:id> |
Important:
- Use the same ID values in both your primary and local product inventory feeds.
- Starting and trailing whitespaces and carriage returns (0x0D) are removed.
- Each sequence of carriage return (0x0D) and whitespace characters (unicode characters with the whitespace property) is replaced by a single whitespace (0x20).
- Only valid unicode characters are accepted, excluding the following characters:
- Control characters (except carriage return 0x0D)
- Function characters
- Private area characters
- Surrogate pairs
- Non assigned code points (in particular any code point larger than 0x10FFFF)
- When an item is submitted, the ID
[id]attribute can't change when you update your data feed or be used for a different product at a later point in time. - Only include the products that are available for purchase in stores.
[quantity] - The number of items in stock
The number of items in stock for the store. If you submit items that are temporarily out of stock, include a value of "0" for this attribute.
When to include: Required for all of the items in your feed.
| Type | Integer |
| Text/tab delimited example | 4 |
| XML example | <g:quantity>4</g:quantity> |
Important:
- Google considers "in stock" items to be those with 3+ availability, "limited availability" to be 1-2, and "out of stock" to be 0.
[price] - Price of the item
The regular price of your item. If you submit a price value here and in the local products feed, this price will override the price in the local products feed for the associated store.
When to include: Required for all of the items in your feed.
| Type | Number (Currency is automatically assigned based on the country where the store is located.) |
| Text/tab delimited example | 299.99 |
| XML example | <g:price>299.99</g:price> |
Optional inventory details
You can use these attributes to give additional information about the price, quantity, and availability of your items.
[sale_price] - Advertised sale price of the item
The advertised temporary sale price that denotes a store-specific override of the price [price] attribute in this feed and the local products feed.
We recommend submitting the sale price effective date [sale_price_effective_date] attribute for any items with sale prices, as this will determine when your sale price should be live. If the sale price effective date isn't submitted, the sale price will be in effect for that item for as long as it is submitted in your feed.
| Type | Number |
| Text/tab delimited example | 279.99 |
| XML example | <g:sale_price>279.99</g:sale_price> |
[sale_price_effective_date] attribute.[sale_price_effective_date] - Date range during which an item is on sale
The dates during which the advertised sale price is effective.
Learn more about sales price definitions
| Type | Text (string), ISO8601, with start and end dates separated by a forward slash (/) |
| Text/tab delimited example |
UTC example: 2021-07-19T17:00:00/2021-07-27T05:00:00 All time values use the 24 hour format. |
| XML example | <g:sale_price_effective_date>2021-07-19T09:00-0800/2021-07-26T21:00-0800</g:sale_price_effective_date> |
[availability] - Availability status of the item
- 'in stock': Indicates that the item is in stock at your local store.
- 'out of stock': Indicates that the item is out of stock at your local store.
- 'limited availability': Indicates that only a few items are left in stock at your local store.
- 'on display to order': Indicates that the item is on display to order at your local store (for example: a refrigerator that needs to be shipped from a warehouse). For items on display to order, submit the value 'on display to order' along with the value "1" for the quantity
[quantity]attribute.
Important:
- Google considers "in stock" items to be those with 3+ quantity, "limited availability" to be 1-2, and "out of stock" to be 0.
- If you use a different value, your item won't be processed. The value you provide for this attribute may or may not appear on Google as submitted.
[availability] attribute with the value ‘out of stock’ and the quantity [quantity] attribute with the value "0."| Type | Text (string). Must be one of the 4 accepted values: 'in stock', 'out of stock', 'limited availability', or 'on display to order'. |
| Text/tab delimited example | in stock |
| XML example | <g:availability>in stock</g:availability> |
Optional store pickup details
Add these attributes to your local product inventory feed for store-specific pickup information.
[pickup_method] - Store pickup option for the item
Specify the pickup option for this item.
- 'buy': The entire transaction occurs online.
- 'reserve': The item is reserved online and the transaction occurs in-store.
- 'ship to store’: The item is purchased online and shipped to a local store for the customer to pick up.
- 'not supported': The item is not available for store pickup.
| Type | Text (string). Must be one of the 4 accepted values:
'buy', 'reserve', ‘ship to store’ or 'not supported' |
| Text/tab delimited example | buy |
| XML example | <g:pickup_method>buy</g:pickup_method> |
[pickup_sla] - Item store pickup timeline
Specify the expected date that an order will be ready for pickup, relative to when the order is placed.
- 'same day': Indicates that the item is available for pickup the same day that the order is placed, subject to cutoff times.
- 'next day': Indicates that the item is available for pickup the following day that the order is placed.
- '2-day': Indicates that the item will be shipped to a store for a customer to pick up in 2 days.
- '3-day': Indicates that the item will be shipped to a store for a customer to pick up in 3 days.
- '4-day': Indicates that the item will be shipped to a store for a customer to pick up in 4 days
- '5-day': Indicates that the item will be shipped to a store for a customer to pick up in 5 days.
- '6-day': Indicates that the item will be shipped to a store for a customer to pick up in 6 days.
- ‘multi-week': Indicates that the item will be shipped to a store for a customer to pick up in one week or more.
| Type | Text (string). Must be one of the 8 accepted values:
'same day', 'next day', '2-day', '3-day', '4-day', '5-day', '6-day', or 'multi-week' |
| Text/tab delimited example | same day |
| XML example | <g:pickup_sla>same day</g:pickup_sla> |