Samir Boulahtit 1cf9fea40a feat(loyalty): transaction categories (what was sold) ...

Merchants can configure per-store product categories (e.g., Men,
Women, Accessories, Kids) that sellers select when entering loyalty
transactions. Enables per-category sales analytics.

Backend:
- New model: StoreTransactionCategory (store-scoped, max 10 per store)
- Migration loyalty_007: creates table + adds category_id FK on
  loyalty_transactions
- New category_service.py with CRUD + validation
- New schemas/category.py (Create, Update, Response, ListResponse)
- Admin CRUD: GET/POST/PATCH/DELETE /admin/loyalty/stores/{id}/categories
- Store CRUD: GET/POST/PATCH/DELETE /store/loyalty/categories
- Stamp/Points request schemas accept optional category_id
- Stamp/Points services pass category_id to transaction creation
- TransactionResponse includes category_id + category_name

342 tests pass.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-04-19 12:23:17 +02:00

..

__init__.py

…

card.py

feat(loyalty): transaction categories (what was sold)

2026-04-19 12:23:17 +02:00

category.py

feat(loyalty): transaction categories (what was sold)

2026-04-19 12:23:17 +02:00

pin.py

…

points.py

feat(loyalty): transaction categories (what was sold)

2026-04-19 12:23:17 +02:00

program.py

feat(loyalty): Phase 4.1 — T&C via CMS integration

2026-04-11 20:26:22 +02:00

stamp.py

feat(loyalty): transaction categories (what was sold)

2026-04-19 12:23:17 +02:00