# Mobile lots API warehouse validation - 2026-05-05

Validated locally against `http://demo.enterfarmaplus.test` using mobile API Bearer authentication.

Route note:
- The checklist route `/api/v1/pharmacy-reports/lots-overview` now works as a compatibility alias.
- The current mobile app route `/api/mobile/v1/reports/lots-overview` still works.

Result on the real mobile route:
- Login via `/api/mobile/v1/auth/login` returned `200`.
- `GET /api/v1/pharmacy-reports/lots-overview?warehouse_id=1&per_page=500` returned `200`.
- `GET /api/v1/pharmacy-reports/lots-overview?warehouse_id=2&per_page=500` returned `200`.
- `GET /api/mobile/v1/reports/lots-overview?warehouse_id=1&per_page=500` returned `200`.
- `GET /api/mobile/v1/reports/lots-overview?warehouse_id=2&per_page=500` returned `200`.
- Warehouse 1 returned 51 lots.
- Warehouse 2 returned 9 lots.
- All returned lot quantities matched `item_lots_group_warehouse.quantity` for the requested warehouse.
- No lot returned for warehouse 1 was foreign to warehouse 1.
- No lot returned for warehouse 2 was foreign to warehouse 2.

Sample proving it does not use global mixed quantity:
- Lot `102` / `0000`: warehouse 1 = `2`, warehouse 2 = `5`, global = `7`.
- Lot `118` / `LOTE-REAL-06859230`: warehouse 1 = `30`, warehouse 2 = `20`, global = `50`.
- Lot `120` / `LOTE-REAL-06980208`: warehouse 1 = `30`, warehouse 2 = `10`, global = `40`.

Conclusion:
- Warehouse filtering is valid on the active mobile endpoint.
- The checklist route is supported by a backend alias and returns the same warehouse-scoped data.