Routeless connects Google Sheets to websites and operational systems when a spreadsheet is the practical interface for staff. Asian Market Escondido reads a large POS-derived catalog and mapping tabs through the Sheets API for product search and guides. Separate Routeless product work uses read-write Sheets workflows for reviewed operational updates.
Evidence verified 2026-09-28 · Vendor facts reviewed 2026-09-28
Asian Market Escondido contains a production read-only Sheets API catalog with caching and degraded operation. A separate Routeless-owned product contains reviewed read-write Sheets API workflows.
The evidence supports direct Google Sheets API v4 reads and writes. Asian Market's runtime is read-only; staff or POS export processes populate its workbook. No Apps Script implementation is claimed.
The website batch-reads a POS-derived product tab plus department, aisle, override, and location tabs, normalizes the rows into a searchable catalog, and caches the result for repeated requests.
Evidence: Verified in Asian Market Escondido's catalog service, product-search route, product guides, and sheet setup script.
Separate workbook tabs hold department mappings, aisle rules, overrides, and location data so staff can change operational behavior without editing application code.
Evidence: Verified in the Asian Market catalog parser and setup script.
A Routeless product writes rows for staff review, reads approved corrections, and records whether the related update is ready or held.
Evidence: Verified in a Routeless-owned product with direct Sheets API reads and writes.
The verified systems use Google service accounts. Asian Market requests the read-only spreadsheets scope; read-write operational workflows use the full spreadsheets scope. Keys are decoded or loaded only in server processes, and the sheet must be shared with the service-account identity.
Google Sheets credentials remain server-side, use the narrowest viable scope, and rely on explicit workbook sharing rather than public-link access.
Asian Market can serve a recent catalog snapshot when a refresh fails. Read-write workflows keep an update pending until the Sheets operation and related review complete.
A bilingual product locator and guide system backed by a large POS-derived Google Sheets catalog and staff-controlled mapping tabs.
Yes. Asian Market Escondido uses a server-side Sheets API connection to read a large product catalog and mapping tabs for search and product guides. Caching and a stale-on-error policy keep the site usable during temporary API failures.
Usually not for transactions or high-concurrency writes. Sheets works well as a familiar staff interface, import source, review queue, or lightweight configuration layer when the application adds stable identifiers, validation, caching, and recovery.
Yes. The API supports multi-range reads and batched value or structural updates. Routeless has implemented both multi-tab catalog reads and read-write operational workbooks with inserted rows and validation controls.
The service account receives only the scope required for the workflow, and the workbook is shared directly with that account. Browser code never receives the credential.
The response depends on the workflow. A public catalog can serve a recent cached snapshot, while a write workflow should retain the pending job and retry with backoff. Neither should silently claim that a failed write succeeded.
Google Sheets official site. The Google Sheets name and logo belong to their owner. Inclusion documents Routeless implementation experience and does not imply partnership, certification, or endorsement.
Share the account access, records, expected events, and the workflow that must recover when delivery fails.