# Partner Tier & Frontend Alignment

## Tier changes (elevation / adjustment)

Partner tier changes (e.g. Local → State, State → Zonal) are **manual and admin-driven**:

- Use **PUT /api/admin/partners/{id}** with body `{ "tier": "Zonal" }` (or `"State"`, `"Local"`, `"Advert"`).
- The backend updates the partner’s `tier_id` and does not auto-create audit notes. Any internal note or approval workflow can be recorded outside the API (e.g. in your admin process).

## Frontend changes required (tower-paints-frontend)

If the frontend repo is separate, apply these so the app matches the API and business rules:

1. **Category: plaster → plasterboard**  
   In product and sales forms (e.g. `CreateProduct.jsx`, `SalesSubmitForm.jsx`, `CreateSale.jsx`), change the category option from `value="plaster"` / label "Plaster" to `value="plasterboard"` / label "Plasterboard" so it matches the API (`plasterboard`).

2. **Create Partner: tiers from API**  
   Load tiers from **GET /api/partner-tiers** and show all four options: **Zonal**, **State**, **Local**, **Advert**. Send either `tier_id` or `tier` (name) when creating a partner. Do not use or map Standard/Premium/Enterprise.

3. **Roles**  
   Use roles **zonal**, **state**, **local**, **advert** (and **admin**) for routing, sidebar, and login redirect. Replace any single **partner** role with these four tier-based roles.

4. **Promotions**  
   Promotions are out of scope; remove or hide any promotion UI and do not rely on promotion APIs.
