Stay organized with collections
Save and categorize content based on your preferences.
Merchant Feed provides your merchant inventory. Google attempts to match this
inventory with Google Maps locations.
To complete the Merchant Feed Ready milestone task, you need to successfully
build and upload
your Merchant Feed to the SFTP dropboxes. The SFTP dropbox is configured when
you provide your SSH key in Setup.
There is a Merchant SFTP dropbox for both Production and Sandbox environments.
Include a minimum of 25 merchants from your total merchants.
Set processing_instruction to PROCESS_AS_COMPLETE.
Fix all errors and warnings.
Merchant basics
Your Merchants Feed is an array of merchant definitions. Each merchant
definition requires the following data:
A unique ID
A name
GeoCoordinates or an address
Merchant matching and bookability
When a new merchant is added to your feed uploads, it can take time to process
and propagate to the frontend.
To verify that merchants are quickly matched and propagated, your
partners must have up-to-date Google Business Profiles for their venues, and the
data you use to define merchants is in alignment with their profiles.
Here, you can find the full
definition
and accompanying sample along with optional attributes that can assist with
automatic matching.
Merchant IDs
IDs must be unique within your organization. If you define a merchant and later
change the ID, that means you have created two merchant definitions in the
system. A new merchant with the new ID, and a deleted merchant with the previous
ID. This can cause venues to become unmatched until the automatic matcher can
process the change.
Merchant names
Merchant names and GeoCoordinates must reflect the actual name and address of
the venue. If your merchants don't have Google Business Profiles, work with
them to verify that the data you have is up-to-date. Merchant names must not
include pricing, menu items, or any other information other than the name of the
venue.
[[["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 2025-07-22 UTC."],[],[],null,["# Merchant Feed Ready\n\nMerchant Feed provides your merchant inventory. Google attempts to match this\ninventory with Google Maps locations.\n\nTo complete the Merchant Feed Ready milestone task, you need to successfully\nbuild and [upload](/actions-center/verticals/reservations/e2e/integration-steps/feeds#upload-feeds)\nyour Merchant Feed to the SFTP dropboxes. The SFTP dropbox is configured when\nyou provide your [SSH key in Setup](/actions-center/verticals/reservations/e2e/integration-steps/setup/public-ssh-key).\nThere is a Merchant SFTP dropbox for both Production and Sandbox environments.\n\nMerchant Feed task requirements\n-------------------------------\n\n- Minimum of one Feed [upload per day](/actions-center/verticals/reservations/e2e/integration-steps/feeds#upload-feeds) for seven days.\n- Include a minimum of 25 merchants from your total merchants.\n- Set `processing_instruction` to `PROCESS_AS_COMPLETE`.\n- Fix all errors and warnings.\n\n| **Note:** Don't use testing data to complete milestones. If you don't have a minimum of 25 merchants to build against, [contact support](https://actionscenter.google.com/support/cases) for next steps.\n\nMerchant basics\n---------------\n\nYour Merchants Feed is an array of merchant definitions. Each merchant\ndefinition requires the following data:\n\n1. A unique ID\n2. A name\n3. GeoCoordinates or an address\n\n### Merchant matching and bookability\n\nWhen a new merchant is added to your feed uploads, it can take time to process\nand propagate to the frontend.\n\nTo verify that merchants are quickly matched and propagated, your\npartners must have up-to-date Google Business Profiles for their venues, and the\ndata you use to define merchants is in alignment with their profiles.\n\nHere, you can find the full\n[definition](/actions-center/verticals/reservations/e2e/integration-steps/feeds/merchants-feed/samples-definitions#definitions)\nand accompanying sample along with optional attributes that can assist with\nautomatic matching.\n| **Note:** New merchants to the system can take up to two weeks to process and propagate to the frontend.\n\n### Merchant IDs\n\nIDs must be unique within your organization. If you define a merchant and later\nchange the ID, that means you have created two merchant definitions in the\nsystem. A new merchant with the new ID, and a deleted merchant with the previous\nID. This can cause venues to become unmatched until the automatic matcher can\nprocess the change.\n\n### Merchant names\n\nMerchant names and GeoCoordinates must reflect the actual name and address of\nthe venue. If your merchants don't have Google Business Profiles, work with\nthem to verify that the data you have is up-to-date. Merchant names must not\ninclude pricing, menu items, or any other information other than the name of the\nvenue.\n| **Note:** Though the system accepts both structured and unstructured addresses, it's best practice to use the structured format."]]