StoreStatus

Schema

One storefront's desired/observed/discrepancy status.

Everything beyond storeId is optional, so this same shape doubles as the response of pauseStores / unpauseStores — those can only state desired firsthand from what they just wrote, never a live re-read of the platform (observed) or a recomputed discrepancy, so they omit those fields rather than fabricate them. Call fetchStoreStatuses next for the observed view.

Fields

storeIdstring
The Store.id this status describes. Always present.
desiredDesiredStoreStatus
The state configured in OneTablet. Always present.
observedObservedStoreStatus
What the delivery platform last reported. Present on reads; absent on the pauseStores / unpauseStores response, which does not re-read the platform.
discrepancyDiscrepancy
Whether desired and observed disagree, and how to fix it. Present on reads; absent on the pauseStores / unpauseStores response.
lastPolledAtstring<date-time>
When OneTablet last refreshed observed. Reason about staleness against this before acting. Absent on the pauseStores / unpauseStores response, which never sets observed.