Stay organized with collections
Save and categorize content based on your preferences.
Data Transmission
A Local Feed Partnership provider can send product, inventory, sales or store
data by calling the API or by uploading files.
A file upload in fact would ingest data for the same offer that doesn't need to
be updated as frequently, like product descriptions and images.
If the merchant sub-accounts are part of your MCA account, access is granted by
default. Data needs to be accurate and refreshed periodically.
Product, inventory data and store identification are the main sets of data
required:
Product data refers to the offer static values (description, size, colour
etc..). This data can be refreshed within a 30 days window. Google uses GTINs
as strong identifiers to ingest merchant's offers, most of the offers should
have one. A provider could only provide GTINs using the POS provider endpoint
and Google will match the offer automatically. In case the GTIN is not
available, a combination of different signals make the ingestion easier. More
information on the product data specification page.
Inventory data refers to quantity and price.While quantity is no longer a
required attribute, availability is now instead. This data should be refreshed
as soon as it changes on the merchant's side to strive for the best possible
user experience. This is store-specific information. More information on the
inventory data feed specification.
Store identification refers to the store code either from the Google
Business Profile linked to the Merchant Center account or from a dedicated
store feed if it is not possible to get access to the Merchant's Google
Business Profile account. This information is necessary to map offers to a
particular store in the Google ecosystem. More information on the Store data
specification page.
If regular updates for inventory data are not possible, alternatively a
Local Feed Partnership provider can use:
Sales data to provide a list of all products sold within a set time
period. This is used to predict price and quantity for offers uploaded.
Generally, as a Local Feeds Partnership provider you need to make sure you have
permission to submit data on your merchant's behalf.
From a technical perspective, while for submitting product data an LFP Provider
needs administrator permissions on the account (either through an MCA - sub
account relationship or by having direct access to the Merchant Center Account),
for submitting inventory, sales and store data, an LFP Provider just needs to be
selected as LFP provider by the merchant. This means linking their Merchant
Center Account to the LFP provider account.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-09-03 UTC."],[[["Data can be sent via API (recommended) or file uploads for less frequent updates like product descriptions and images."],["Product, inventory, and store identification data are the primary data sets required for Local Feed Partnership providers."],["Product data (descriptions, size, color) can be refreshed within 30 days and should ideally include GTINs."],["Inventory data (availability, price) should be updated as frequently as possible, ideally in real-time when changes occur on the merchant's side."],["Store identification data links offers to specific stores using either Google Business Profile or a dedicated store feed."]]],["Local Feed Partnership providers send merchant data via API (recommended) or file uploads. Data includes product (static details, refreshed within 30 days), inventory (price and availability, frequently updated), and store identification (store codes from Google Business Profile or dedicated feed). If inventory updates are infrequent, sales data can be used to predict quantity and price. Providers need appropriate permissions to submit data; either admin rights or being selected as the LFP provider. Accurate data with periodic refreshes is crucial.\n"]]
