# STORE_NOT_FOUND

# STORE_NOT_FOUND

The `storeId` on the request does not resolve to a known store. The id is a well-formed Guid but no store exists for it.

## Summary

| Field | Value |
|---|---|
| HTTP status | `404` |
| `errorCategory` | `not_found` |
| `retryable` | `false` |

## When This Fires

- **`GET /v1/marketfront/stores/{storeId}`** — direct lookup by id.
- **`POST /v1/marketfront/orders/validate`** / **`/place`** — order references a stale or unknown `storeId`.

If the id isn't a well-formed Guid, the route returns `404` directly without a body.

## Recommended Action

Re-discover stores and resubmit with a current id:

1. `POST /v1/marketfront/stores/discover` — fetch the discovery list for the user's address.
2. Surface available stores to the user.
3. Resubmit using a `storeId` from the fresh list.

If the user came in via a deep link with a stale id, redirect them back to discovery rather than retrying.

## Example

```json
{
  "type": "https://developer.gett-tech.com/errors/STORE_NOT_FOUND",
  "title": "Not Found",
  "status": 404,
  "detail": "Store 'abc-123' not found.",
  "instance": "/v1/marketfront/stores/abc-123",
  "requestId": "req_abc123",
  "timestamp": "2026-04-27T14:30:00.000Z",
  "errorCode": "STORE_NOT_FOUND",
  "errorCategory": "not_found",
  "retryable": false
}
```