# Store registration

How to register a new store (restaurant) from the app, and how to verify its phone. This reflects the API as of 2026-11-04 (staging): a merchant store name separate from the company name, a three-part address, a NIP for Poland, and the company lookup. Shared rules (headers, errors, phone format, image compression) are in [common.md](common.md). The rest of the restaurant app is in [restaurant-app.md](restaurant-app.md). The web form (Landing) already works this way and can be used as a visual reference.

## What changed

1. The merchant's own store name goes in `storeName` (a single language-neutral name instead of an Arabic and an English one; `nameDefault` / `nameAr` / `nameEn` still work).
2. The address is three fields (`street`, `buildingNumber`, `postalCode`) instead of one. The city comes from the zone the user picks.
3. **Poland needs a NIP** (the Polish tax number): asked for when the chosen country is Poland.
4. An optional **company lookup** fills in the form from the NIP. When it finds the company, the address and type are read-only and the **server** takes them from the registry when the store is saved.
5. **(2026-11-04)** The registry **no longer renames the store**. The store keeps the merchant's `storeName`; the official company name is returned separately in `companyName` with a `companyId` (stores sharing a NIP share one company). The store name is also **editable** afterwards on `PATCH /store`.
6. **(2026-11-04)** New `POST /store/resend/:id` to resend the registration OTP, with a 60-second cooldown.
7. Poland has about 1,020 cities now (it had 4), so the city picker must search and page.
8. Messages come back in four languages (`en`, `ar`, `pl`, `uk`).
9. **(2026-11-12)** The form now has a **Delivery and booking** block: `reservationsEnabled`, `reservationCancelHours` and `deliveryFee` (section 2). The web admin form already had them; the app did not. (The note that `defaultDeliverySource` is not sent is replaced by item 10.)
10. **(2026-11-19)** The form has **Default delivery source**: `PLATFORM` (Platform drivers) or `STORE_FLEET` (**Company fleet**, the label was "Store fleet"). With Company fleet the user must pick the **fleet company** (`fleetCompanyId`) from the new public `GET /driver-company/fleet-options`. Full spec: [update-2026-11-19-full.md, section 8](update-2026-11-19-full.md#8--store-registration-full-spec).

## Flow

1. Load the pickers: module and country.
2. **Country and NIP first.** The user picks the country. If it is Poland, show the NIP field (required) and the "Fetch company data" button; otherwise hide them. Fetching is optional, but it fills in the fields below, so the user should not type those before it.
3. The user picks the city, then the zone of that city.
4. Validate every field and compress the four images on the device.
5. `POST /store` (multipart). The API sends an OTP to the **store phone**.
6. Show the OTP screen. `POST /store/verify/{id}`.
7. The store is now verified but still `PENDING`. An admin must approve it before the owner can use it.

No token is needed for steps 1 to 6. Send the `Locale` header (`en`, `ar`, `pl` or `uk`).

If the user changes the country, or changes the NIP after a successful lookup, **unlock the fields and clear what the lookup filled in** (section 3).

## Screen layout

Fields in this order:

| # | Field | Required |
| --- | --- | --- |
| 1 | Country | yes |
| 2 | Module | yes |
| 3 | NIP + "Fetch company data" button | yes, **only when the country is Poland** |
| 4 | City | yes |
| 5 | Zone | yes |
| 6 | Store name | yes |
| 7 | Street name, Building number | yes |
| 8 | Postal code, Store phone | yes |
| 9 | Do you have a POS system? (then the POS system) | the system is required when "yes" |
| 10 | Type | yes |
| 11 | Minimum and maximum delivery time | yes |
| 12 | **Delivery and booking:** Reservations enabled, Cancel window (hours), Delivery fee | Reservations and Cancel window: yes (they have defaults); Delivery fee: no |
| 13 | Logo, Cover, the two registry documents | yes |
| 14 | Owner: name, email, phone, ID number, password, confirm password | yes |
| 15 | Who is registering (Owner or Legal agent) | yes |
| 16 | Referral code | no |
| 17 | Store location on the map | yes |
| 18 | Terms and conditions, submit | yes |

- Put a **label above every input**, not only a placeholder inside it. Mark required fields with a red `*` and the referral code with "(Optional)".
- Show each error under the field it belongs to.
- A read-only field looks read-only (grey background) and cannot be focused or edited.
- Right-to-left languages mirror the layout; the label stays above its field.

## 1. Pickers

| Field | Load from |
| --- | --- |
| `moduleId` | `GET /modules` |
| Country (not sent) | `GET /country?isActive=true&limit=100` |
| City (not sent) | `GET /city?countryId={countryId}&name={text}&limit=20&page=1` |
| `zoneId` | `GET /zone?cityId={cityId}` |

Country and city only narrow down the zone. The request carries `zoneId`, not the city. Send the `id` of the chosen row.

- **Countries** come with `phoneCode` and `phoneLength`: `{ "id": 1, "name": "Poland", "phoneCode": "48", "phoneLength": 9 }`. Poland is the country whose `phoneCode` is `"48"`. Do not recognise it by its name (the name changes with the language) or its id.
- **Cities.** Poland has about 1,020. Do not load them into one list: search as the user types (`name`) and load the next `page` on scroll. The response has `total`. The `name` is in the `Locale` language.
- **Zones.** `zoneId` is required, and **most of the new Polish cities have no zones yet**: on staging only Warsaw (4), Kraków (3), Gdańsk (1) and Lublin (1) have any. When the list is empty, say "Not available in this city yet" and do not let the user continue.
- **Do not show "select city first" when a city is already chosen.** That message is only for opening the zone picker with no city `id` yet. Once the city field shows a value, the app must already hold `cityId` (the numeric `id` from `GET /city`) and call `GET /zone?cityId={that id}`. Sending the city name (`cityId=Warsaw`) returns `400` `cityId must be a number…`.

## 2. Register

`POST /store` as `multipart/form-data`.

| Field | Required | Value |
| --- | --- | --- |
| `storeName` | yes* | The merchant's store display name, 2 to 100 characters. One name for every language. *Or send `nameDefault`, or `nameAr`+`nameEn`; one of the three is required. Not the company name. |
| `street` | yes | Text, up to 150 characters. |
| `buildingNumber` | yes | Text, up to 20 characters. Write an apartment after a slash: `12/3`. |
| `postalCode` | yes | 3 to 12 characters: letters, digits, spaces or dashes. |
| `nip` | **yes when the zone is in Poland** | The Polish tax number (section 3). |
| `phone` | yes | Store phone, [spaced format](common.md#phone-format). Must not belong to another store. |
| `type` | yes | `COMPANY`, `ORGANIZATION` or `FREELANCE` |
| `moduleId` | yes | From `GET /modules` |
| `zoneId` | yes | From `GET /zone` |
| `point` | yes | JSON string `{"lat":number,"lng":number}` for the pin the user **last** chose (overwrite on every map/search pick; the API does not cache a previous location). |
| `minDeliveryTime` | yes | Minutes, 10 or more |
| `maxDeliveryTime` | yes | Minutes |
| `reservationsEnabled` | no | `true` or `false` (text). Whether customers can book a table. Default `true`. Show it as a Yes / No select, pre-selected **Yes**. |
| `reservationCancelHours` | no | Whole number, 0 or more. Customers can cancel a booking up to this many hours before it. Default `2`. Pre-fill **2**. |
| `defaultDeliverySource` | yes | `PLATFORM` (Platform drivers) or `STORE_FLEET` (Company fleet). See "Delivery settings". |
| `fleetCompanyId` | **yes with `STORE_FLEET`** | Id from `GET /driver-company/fleet-options`. Do not send with `PLATFORM`. |
| `deliveryFee` | — | **Removed (2026-11-19).** The platform prices delivery by distance. Do not show or send it (still accepted and ignored for old builds). Free delivery is set later with `freeDeliveryOver` on `PATCH /store` ([restaurant app](restaurant-app.md#free-delivery)). |
| `vendor` | yes | JSON string, the owner: see below |
| `logo`, `cover` | yes | Image files (`multipart` parts named exactly `logo` / `cover`) |
| `commercialRegistryOrSelfEmploymentDocument` | yes | Image file part named exactly `commercialRegistryOrSelfEmploymentDocument` |
| `commercialRegistryOrSelfEmploymentCertificate` | yes | Image or PDF part named exactly `commercialRegistryOrSelfEmploymentCertificate` |
| `pos` | no | Text |
| `website` | no | A valid link |
| `referralCode` | no | Send only when the user typed one |
| `personHandlingTheRegistration` | no | `LEGAL_AGENNT`, `OWNER`, `ADMIN` or `EMPLOYEE` (spelled exactly like this) |

`vendor` is a JSON string, not separate fields:

```json
{
  "name": "Ahmed Ali",
  "email": "owner@example.com",
  "password": "Default@123",
  "phone": "+966 512345678",
  "idNumber": "44051401458"
}
```

- `name`: letters and single spaces only. The first word becomes the first name, the rest the last name. At least two names when the field is shown as required on the form.
- `idNumber`: any national ID / passport-style string, max 50 characters. **Not** Saudi-only — do not show or enforce “Must start with 1 or 2” (or a 10-digit `1|2|3…` pattern). The same rule applies to branch manager `vendor` on `POST /branch`.
- `password`: must be strong (upper and lower case, a digit and a symbol, at least 8 characters).
- `phone` and `email` must not belong to another owner.
- `vendor.phone` may equal the store `phone`. Show a warning, not an error ("Store phone is the same as the owner phone").

`point` and `vendor` must be valid JSON strings. A broken string returns `400` with `errors.invalidStringifiedJson {field}`.

### Name and address

- Send the store's own display name in `storeName` (2–100 chars). This is the merchant's name for the store, **not** the company name. `nameDefault` (and the older `nameAr`/`nameEn`) are still accepted; sending none of the three returns `400` "Store name is required".
- Send `street`, `buildingNumber` and `postalCode`. The API builds `address` itself from them and the city of `zoneId`, for example `King Fahd Road 12, Riyadh, 12345`. Do not send `address` together with them. An app that sends only `address` still works.
- Unknown fields are rejected with `400` `property X should not exist`.

### Delivery settings

`reservationsEnabled` and `reservationCancelHours` are saved exactly as sent, the same as on the admin form. They can be changed later on `PATCH /table-reservation/store/settings` ([restaurant app](restaurant-app.md#settings)) or `PATCH /store`.

**Delivery source (2026-11-19).** Show "Default delivery source" (required) with *Platform drivers* (`PLATFORM`) / *Company fleet* (`STORE_FLEET`). With Company fleet show a required "Fleet company" picker; hide and clear it when the user goes back to Platform drivers.

`GET /driver-company/fleet-options?name={text}&limit=20` (public, no token) returns only `ACTIVE` companies: `{ "message": "", "data": [{ "id": 4, "name": "Fast Fleet" }], "total": 1 }`. Optional `id={id}` returns that one company. Send the chosen `id` as `fleetCompanyId`.

`STORE_FLEET` without a company, or with one that is not `ACTIVE`, returns `400` "Company fleet needs an active fleet company"; an unknown id returns `400` "Fleet company not found". After registration only an admin can change the company (`fleetCompanyId` on `PATCH /store` is ignored for the restaurant).

Validation on the device: `reservationCancelHours` a whole number, 0 or more. A wrong value returns `400` on that field.

### Do not send

`status`, `verified`, `tax`, `commissionType`, `commissionValue`, `address` (with the three fields above), `companyRegistry` and `companyId` (set by the server from the NIP). Send `fleetCompanyId` only with `defaultDeliverySource: "STORE_FLEET"`.

### Success

`201`. `data` holds only what the next step needs:

```json
{ "message": "Created Store successfully", "data": { "id": 57, "phone": "+966 512345678" } }
```

Keep `data.id` and `data.phone` in memory for the OTP screen. Show the phone from `data.phone`, never from another field: if it is missing the OTP screen shows a broken number.

### Errors

The `message` comes translated into the `Locale` language; show it as it is.

| Status | `message` (`en`) | Cause |
| --- | --- | --- |
| `400` | Store name is required | No name |
| `400` | Store name must be at least 2 characters / must not exceed 100 characters | Name length |
| `400` | Address is required: send street and building number, or a full address | `street` and `buildingNumber` both missing |
| `400` | Postal code must be 3 to 12 characters: letters, numbers, spaces or dashes | Postal code |
| `400` | Street name must not exceed 150 characters / Building number must not exceed 20 characters | Too long |
| `400` | NIP is required for stores in Poland | Polish store without a NIP |
| `400` | Invalid NIP: it must be 10 digits with a valid check digit | Wrong NIP |
| `400` | The delivery zone must be in the company's city | The zone is not in the city of the company found by NIP |
| `400` | `enter valid phone like this +999 999999999` | Phone not in the spaced format |
| `409` | Store phone number is already used by another store | Store `phone` taken |
| `409` | Store name already exists | Name taken |
| `409` | User already found | Owner `email` or `vendor.phone` taken |

The messages about name length, street, building number and postal code are English in every language; the others are translated.

The four files upload before validation finishes, so a `400` or `409` can arrive late. Stop the loader in `finally`. Validate fields and the phone format on the device before the upload.

## 3. Poland: NIP and company lookup

### The NIP

The NIP is the Polish tax number. The EU VAT number is the same number with a `PL` prefix, so these all mean the same: `5261040567`, `PL5261040567`, `526-104-05-67`, `PL 526 104 05 67`. Strip `PL`, spaces and dashes, check it, and send the 10 digits.

**Check it on the device** (the API checks again): 10 digits; multiply the first nine by `6, 5, 7, 2, 3, 4, 5, 6, 7` and add them; the sum modulo 11 must equal the tenth digit, and must not be 10. For `5261040567`: `5·6 + 2·5 + 6·7 + 1·2 + 0·3 + 4·4 + 0·5 + 5·6 + 6·7 = 172`, and `172 mod 11 = 7`, the last digit.

- **Required** on `POST /store` when the zone is in Poland; not needed elsewhere.
- **Locked once saved.** It cannot be changed or cleared afterwards (section 5).

### The lookup

`GET /company/lookup?nip=5261040567` (no token, send `Locale`).

```json
{
  "data": {
    "nip": "5261040567",
    "regon": "011417295",
    "name": "T-MOBILE POLSKA SPÓŁKA AKCYJNA",
    "street": "ul. Test-Krucza",
    "buildingNumber": "12",
    "postalCode": "02-674",
    "city": "Warszawa",
    "voivodeship": "MAZOWIECKIE",
    "kind": "LEGAL_ENTITY",
    "active": true,
    "closedOn": null,
    "cityId": 1,
    "suggestedType": "COMPANY",
    "phone": "+48 224136000",
    "email": null,
    "website": null,
    "legalForm": "SPÓŁKI AKCYJNE",
    "startedOn": "1996-01-26",
    "sandbox": true
  }
}
```

| Status | Meaning | What to do |
| --- | --- | --- |
| `200` | Found. | Fill and lock the fields (below). |
| `400` | Not a valid NIP. | Cannot happen if the app checks first. |
| `404` | Valid NIP, not in the registry. | Show the message; the user types the details. The store can still be registered. |
| `429` | More than 20 lookups a minute. | Show the message; try again later. |
| `503` | The registry is down. | Show the message; the user types the details. |

The `name` and `street` come from the registry in Polish and are not translated. While `sandbox` is `true` the data is GUS test data, so streets read `ul. Test-...`.

### Pre-fill and read-only

When the lookup returns `200`, fill the form like this and make **these fields read-only**:

| From the response | Fill | Read-only |
| --- | --- | --- |
| `name` | **Company name** (show it as the official company name, not the store's display name). The merchant still types their own `storeName`. | yes (as the company name) |
| `street`, `buildingNumber`, `postalCode` | the same fields | yes |
| `cityId` | the city with that id (the user then picks a zone) | yes, **only when `cityId` is not `null`** |
| `suggestedType` | Type: `COMPANY` for a legal entity, `FREELANCE` for a sole proprietor | yes, **only when it is not `null`** |
| `phone` | Store phone, **only when it is not `null` and the field is empty** | no |
| `active: false` | nothing; show "This company has ceased operations" | |

- `cityId` is `null` when we do not serve that city: leave the city empty and editable. If an earlier lookup had filled a city, clear it.
- `phone` is filled only when it is a full Polish number. It is usually a landline, so let the user change it.
- `email`, `website`, `legalForm` and `startedOn` are about the company. Do not put the email in the owner's email field.

**Unlock and clear** the filled fields when the user edits the NIP after a successful lookup, changes the country, or a later lookup answers `404`, `429` or `503`.

### The server decides

The read-only look is only for the user. **On `POST /store` the server asks the registry itself.** When the registry knows the NIP, it replaces whatever the app sent for the **street, building number, postal code and type** with the registry's record, and saves that whole record with the store (`companyRegistry`). A request edited by hand gets the same result, so the app does not need to defend against it, and it never sends the registry data back.

- **The store name is NOT replaced.** The display name stays whatever the merchant typed in `storeName` / `nameDefault`. The official company name from the registry is saved separately in **`companyName`**, and the store is linked to a `Company` row (deduped by NIP) via **`companyId`** — several stores with the same NIP share one company. *(This changed on 2026-11-04; older docs said the registry renamed the store.)*
- The zone must then be in the company's city (when we serve that city), or the API answers `400`.
- When the registry does not know the NIP, or cannot be reached, what the user typed is saved as it is, `companyRegistry` is `null`, and `companyName` is whatever the merchant typed (or null).

## 4. Verify the phone

```
POST /store/verify/{id}
{ "phone": "+966 512345678", "otp": "1234" }
```

- `{id}` is `data.id` from the register response.
- `phone` is the **store** phone (`data.phone`), not `vendor.phone`. The OTP is sent to the store phone and the API looks the store up by `id` and `phone` together.
- Send `phone` exactly as it was registered, including the space.
- The OTP has 4 digits. Show "We've sent a 4-digit OTP to {phone}".

| Result | Meaning |
| --- | --- |
| `200` | Verified. Go to the "waiting for approval" screen. |
| `400` or `401` `Invalid verification code. Please try again.` | Wrong code, or `id` and `phone` do not match. Clear the boxes and let the user retry. |

### After verification

The store is `verified: true` and `status: "PENDING"` until an admin approves it. Logging in before that (`POST /authentication/login`, role `VENDOR`) returns:

| Response | Screen |
| --- | --- |
| `412` with `data.storeId`, `data.phone` | The phone was never verified. The API has just sent a new OTP to that phone, so open the OTP screen with those two values and do not ask for another one. |
| `401` | Verified but not `ACTIVE` (still pending approval, denied or expired), or the store was deleted: show `message` |

Choose the screen from the status code and the fields, never from the message text.

## 5. After registration: reading and editing

`GET /store/{id}` returns `nip`, `street`, `buildingNumber`, `postalCode` (empty for stores registered before this change), `address`, `companyRegistry`, and the company name/link **`companyName`** and **`companyId`** (both `null` for non-registry stores).

On the edit screen, with `PATCH /store`:

- Show the **NIP read-only**. A store that has none (an older one) can add it once. A different or empty `nip` returns `400` "NIP cannot be changed after it has been registered".
- **The store display name is editable**, even for registry-sourced stores — send it in `storeName` / `nameAr` / `nameEn`. *(Changed on 2026-11-04: the name used to be locked for registry stores.)* The **company name** (`companyName`) is not editable here; it comes from the registry.
- For a store whose company came from the registry (`companyRegistry` is not `null`), show the **type read-only**, and for the main store (and its default branch) also the **address fields**. Changing them returns `400` "These details come from the company registry and cannot be changed". Other branches keep their own address.
- Sending the stored value again is accepted.

### Resend the registration OTP

`POST /store/resend/:id` with `{ "phone": "+966 512345678" }` re-sends the OTP to the store phone (`:id` + `phone` must match the store). Errors: `Invalid verification code` when nothing matches, `ALREADY_VERIFIED` when the store is already verified, and a **60-second cooldown** `Please wait {seconds} seconds…` (`OTP_RESEND_WAIT`). Success message key `OTP_RESENT`. Put a "Resend code" button on the OTP screen, disabled for 60s after each send.

Branches (`POST /branch`) take one `address` (and `point` or `zoneId`), and inherit the NIP and the registry record from the main store. `vendor` login data is optional: omit it to manage the branch with the main store owner account; send it only when the branch needs its own manager login.

## 6. Texts to reuse

| Use | en | ar | pl | uk |
| --- | --- | --- | --- | --- |
| Button | Fetch company data | جلب بيانات الشركة | Pobierz dane firmy | Отримати дані компанії |
| Fields are locked | Company data comes from the official registry and cannot be edited, change the NIP to enter it manually | بيانات الشركة مأخوذة من السجل الرسمي ولا يمكن تعديلها، غيّر رقم NIP لإدخالها يدويًا | Dane firmy pochodzą z oficjalnego rejestru i nie można ich edytować, zmień NIP, aby wpisać je ręcznie | Дані компанії взято з офіційного реєстру, їх не можна редагувати, змініть NIP, щоб ввести їх вручну |
| Found, city matched | Company data loaded from the GUS registry. Choose the zone to continue | تم جلب بيانات الشركة من سجل GUS. اختر المنطقة للمتابعة | Dane firmy pobrano z rejestru GUS. Wybierz strefę, aby kontynuować | Дані компанії завантажено з реєстру GUS. Виберіть зону, щоб продовжити |
| Found, city not ours | Company data loaded from the GUS registry. Its city is not in our list: choose the city and zone | تم جلب بيانات الشركة من سجل GUS. مدينتها غير موجودة في قائمتنا: اختر المدينة والمنطقة | Dane firmy pobrano z rejestru GUS. Jej miasta nie ma na naszej liście: wybierz miasto i strefę | Дані компанії завантажено з реєстру GUS. Її міста немає в нашому списку: виберіть місто та зону |
| `404` | No company found for this NIP. Fill in the details manually | لم يتم العثور على شركة بهذا الرقم. أدخل البيانات يدويًا | Nie znaleziono firmy dla tego NIP. Uzupełnij dane ręcznie | Компанію з цим NIP не знайдено. Заповніть дані вручну |
| `503` | The company registry is unavailable right now. Fill in the details manually | سجل الشركات غير متاح حاليًا. أدخل البيانات يدويًا | Rejestr firm jest chwilowo niedostępny. Uzupełnij dane ręcznie | Реєстр компаній тимчасово недоступний. Заповніть дані вручну |
| `429` | Too many lookups, wait a minute and try again | عدد كبير من محاولات البحث، انتظر دقيقة ثم حاول مرة أخرى | Zbyt wiele zapytań, odczekaj minutę i spróbuj ponownie | Забагато запитів, зачекайте хвилину й спробуйте знову |
| Ceased | This company has ceased operations | هذه الشركة أوقفت نشاطها | Ta firma zakończyła działalność | Ця компанія припинила діяльність |
| Same phone | Store phone is the same as the owner phone | رقم هاتف المتجر هو نفسه رقم هاتف المالك | Telefon sklepu jest taki sam jak telefon właściciela | Телефон закладу збігається з телефоном власника |
| NIP required | NIP is required | الرقم الضريبي (NIP) مطلوب | NIP jest wymagany | NIP обов’язковий |
| NIP invalid | Invalid NIP: it must be 10 digits with a valid check digit | الرقم الضريبي غير صحيح: يجب أن يتكون من 10 أرقام برقم تحقق صحيح | Nieprawidłowy NIP: wymagane 10 cyfr i poprawna cyfra kontrolna | Недійсний NIP: потрібно 10 цифр і правильна контрольна цифра |

## 7. Compatibility

- Outside Poland nothing breaks: `nameAr`, `nameEn` and a single `address` are still accepted from older app builds.
- **Older app builds cannot register a store in Poland**, because they cannot send a NIP. Ship this change before Poland opens to the app.

## 8. Test data

On staging the registry is GUS's test service, so only some NIPs return a company, with made-up streets:

| NIP | Company | City (`cityId`) |
| --- | --- | --- |
| `5261040567` | T-Mobile Polska S.A. | Warszawa (1) |
| `5252344078` | Google Poland Sp. z o.o. | Warszawa (1) |
| `5270103391` | Microsoft Sp. z o.o. | Warszawa (1) |
| `6770065406` | Comarch S.A. | Kraków (2) |
| `5272525995` | Grupa Allegro Sp. z o.o. | Poznań (no zones) |
| `1234563218` | valid number, not in the registry | `404` |
| `5261040568` | wrong check digit | refused on the device |

A real registration creates a real store on staging, and needs a unique store phone and a new owner email, so use test values.

## Checklist

- [ ] Country and module load without a token; country first, NIP second
- [ ] NIP shown and required only when the country's `phoneCode` is `"48"`
- [ ] NIP checked on the device (check digit); `PL`, spaces and dashes removed before sending
- [ ] City picker searches and pages; an empty zone list shows "Not available in this city yet"
- [ ] Lookup fills the company name, street, building number, postal code, city and type as read-only; changing the NIP or country unlocks and clears them
- [ ] A `404`, `429` or `503` lookup leaves every field editable
- [ ] `point` and `vendor` are sent as JSON strings
- [ ] Delivery and booking block: `reservationsEnabled` (default Yes), `reservationCancelHours` (default 2); no `deliveryFee` (removed 2026-11-19); `defaultDeliverySource` sent; fleet company picker shown and required only with Company fleet
- [ ] Phone built with the shared helper, with the space
- [ ] Images compressed before upload
- [ ] `storeName` (or `nameDefault`), `street`, `buildingNumber` and `postalCode` for name and address; no `address`, `companyRegistry` or `companyId`
- [ ] Read the official company name from `companyName` (not from the store name); the NIP no longer renames the store
- [ ] Store name stays editable on `PATCH /store`; "Resend code" button wired to `POST /store/resend/:id`
- [ ] A label above every input; `*` for required, "(Optional)" for the referral code
- [ ] OTP screen shows `data.phone` from the register response
- [ ] Verify sends the store phone, not the owner phone
- [ ] Loader stops on every error path
- [ ] All four languages show their own texts, and right-to-left mirrors the layout
- [ ] Edit screen: NIP read-only; store name **editable**; type and (main store) address read-only for registry stores
