rocket
Meet
Merchant API
- the official successor to Content API for Shopping.
update
Get the latest
on new Merchant API features, bug fixes, and updates.
add_alert
Note: Content API for Shopping will be sunset on August 18, 2026.
REST Resource: pos
Stay organized with collections
Save and categorize content based on your preferences.
Resource: PosStore
JSON representation |
{
"storeCode": string,
"storeAddress": string,
"kind": string,
"storeName": string,
"phoneNumber": string,
"websiteUrl": string,
"gcidCategory": [
string
],
"placeId": string,
"matchingStatus": string,
"matchingStatusHint": string
} |
Fields |
storeCode |
string
Required. A store identifier that is unique for the given merchant.
|
storeAddress |
string
Required. The street address of the store.
|
kind |
string
Identifies what kind of resource this is. Value: the fixed string "content#posStore "
|
storeName |
string
The merchant or store name.
|
phoneNumber |
string
The store phone number.
|
websiteUrl |
string
The website url for the store or merchant.
|
gcidCategory[] |
string
The business type of the store.
|
placeId |
string
The Google Place Id of the store location.
|
matchingStatus |
string
Output only. The matching status of POS store and Google Business Profile store.
Possible values are: - "
matched ": The POS store is successfully matched with the Google Business Profile store. - "
failed ": The POS store is not matched with the Google Business Profile store. See matchingStatusHint for further details. Note that there is up to 48 hours propagation delay for changes in Merchant Center (e.g. creation of new account, accounts linking) and Google Business Profile (e.g. store address update) which may affect the matching status. In such cases, after a delay call pos.list to retrieve the updated matching status.
|
matchingStatusHint |
string
Output only. The hint of why the matching has failed. This is only set when matchingStatus=failed.
Possible values are: - "
linked-store-not-found ": There aren't any Google Business Profile stores available for matching.Connect your Merchant Center account with the Google Business Profile account. Or add a new Google Business Profile store corresponding to the POS store. - "
store-match-not-found ": The provided POS store couldn't be matched to any of the connected Google Business Profile stores.Merchant Center account is connected correctly and stores are available on Google Business Profile, but POS store location address does not match with Google Business Profile stores' addresses. Update POS store address or Google Business Profile store address to match correctly. - "
store-match-unverified ": The provided POS store couldn't be matched to any of the connected Google Business Profile stores, as the matched Google Business Profile store is unverified.Go through the Google Business Profile verification process to match correctly.
|
Methods |
|
Batches multiple POS-related calls in a single request. |
|
Deletes a store for the given merchant. |
|
Retrieves information about the given store. |
|
Creates a store for the given merchant. |
|
Submit inventory for the given merchant. |
|
Lists the stores of the target merchant. |
|
Submit a sale event for the given merchant. |
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-02-25 UTC.
[null,null,["Last updated 2025-02-25 UTC."],[[["\u003cp\u003eThe PosStore resource represents a physical store location and allows management of store information within the Merchant Center.\u003c/p\u003e\n"],["\u003cp\u003eStore data like address, phone number, website, business type, and Google Place ID can be stored and retrieved using this resource.\u003c/p\u003e\n"],["\u003cp\u003ePosStore enables integration with Google Business Profile for store matching and verification.\u003c/p\u003e\n"],["\u003cp\u003eSeveral methods, such as \u003ccode\u003einsert\u003c/code\u003e, \u003ccode\u003edelete\u003c/code\u003e, \u003ccode\u003eget\u003c/code\u003e, and \u003ccode\u003elist\u003c/code\u003e, are available to manage PosStore data, along with specialized methods like \u003ccode\u003einventory\u003c/code\u003e and \u003ccode\u003esale\u003c/code\u003e for inventory and sales data submission.\u003c/p\u003e\n"]]],["The PosStore resource represents a physical store with attributes like `storeCode`, `storeAddress`, `storeName`, and `phoneNumber`. It includes `matchingStatus` to indicate if a store is linked to a Google Business Profile, and `matchingStatusHint` for troubleshooting. Key actions involve managing store data, including creating, deleting, and retrieving information about stores. Other actions include submitting inventory or sale events and batching multiple calls. Additionally, users can list the stores and retrieve matching statuses for each.\n"],null,[]]