Catalog only
Stores, retail, and shopping
Google Places Thailand store POIs and hours.
Strongest commercial enrichment layer for store name, address, coordinates, business_status, opening_hours, phone, website, photos, price level, rating, reviews, and operational status. It is not a Thai legal business registry and must not be used as an open canonical database.
Commercial
Google Places API with field-mask controlled place details, nearby/text search, place IDs, and commercial terms
Paid/commercial API; account credits or trial terms may vary
On request for search/open-now; weekly for key store detail refresh; monthly for place matching
2026-05-11
Usually needs payment, partner approval, or a commercial agreement before production use.
page reference only
store/place ID, name, Thai/English aliases, brand, operator, legal entity, DBD number, RD VAT/VRT flag, regulated license, category, format, address, floor/unit, lat/lon, opening hours, phone, website, products, GTIN, price, inventory status, reviews, rating, photos, source ID
Medium-high for discovery and context; operational reliability depends on endpoint stability.
Runtime truth
Catalog only
Not yet
No runtime entity scope yet.
No live observation ingestion yet.
Not wired into active decisions yet.
Profiled in the atlas and public pages, but not yet connected to live graph computation.
How this helps travel recommendations
Turns shopping and essentials planning into source-backed confidence: where the store is, whether it is open, whether the business/license/tax status can be validated, whether products or prices are official context or private inventory, and which source can actually prove the claim.
Endpoint and API notes
Strongest commercial enrichment layer for store name, address, coordinates, business_status, opening_hours, phone, website, photos, price level, rating, reviews, and operational status. It is not a Thai legal business registry and must not be used as an open canonical database.
Open the source endpoint or documentation. Return to the Thailand data atlas.
Developer reference
Use OSM as the free shop POI spine, Google/Longdo/NOSTRA/Foursquare for licensed POI and hours enrichment, brand locators for chain branches, DBD/RD for legal and tax identity, FDA/Excise/OTOP/Thong Fah/ETDA for regulated and special store types, DIT/MOC/BOT/TPSO for price context, GS1 for products, and marketplace APIs only with seller/partner authorization.
Refresh weekly and record the publication date separately from fetch time.
Turns shopping and essentials planning into source-backed confidence: where the store is, whether it is open, whether the business/license/tax status can be validated, whether products or prices are official context or private inventory, and which source can actually prove the claim.
OSM/Overpass, Google Places, Longdo, NOSTRA, Foursquare, brand locators, mall directories, Open DBD, GDX/DBD, Revenue Department VAT/VRT datasets, ETDA, Thai FDA, Excise, DIT/MOC, TPSO/BTEI, BOT, GS1 Thailand, OTOP, Thong Fah, Shopee, Lazada, LINE MAN/Wongnai, and retailer/chain partner feeds.
Example request
# Verify the documented store endpoint before production use.
curl -L "https://developers.google.com/maps/documentation/places/web-service/legacy/details" -H "Accept: application/json"Failure modes
- There is no single all-store Thailand API.
- Business registry records do not prove every physical branch or opening hours.
- VAT branches can be offices, warehouses, or non-public establishments.
- POI records do not prove legal entity, VAT status, or regulated license.
- Brand locators are accurate but siloed by chain.
- Hours, holiday closures, mall hours, and temporary closures are volatile.
- Store inventory and exact shelf price are usually private unless a retailer or marketplace authorizes access.
- Official price datasets are usually category/market context, not branch-level shelf prices.
- Commercial POI/review/photo APIs have licensing and caching limits.
- Dashboard markup or public-page layout can change without notice.
- Free registration, keys, or rate limits can interrupt automated refresh.
Last checked and source confidence
Last checked: 2026-05-11.
Source confidence: Treat this profile as strongest for the exact role named above. It is weaker when the source is stretched into live availability, legal proof, or traveler-fit decisions it does not directly prove.