HOCO B2B
Team tasksAnis

SRV-43 — Loyalty contract extension

Extend the V2 contract with every loyalty operation of change request 04, so mobile and design start in parallel.

FieldDetails
Task codeSRV-43
PhaseP4 — V2 evolutions
Product scopeV2
StatusPlanned
StartSun 24 Jan 2027
DueMon 25 Jan 2027
ResponsibleAnis — Full-stack developer
Co-responsibleImad
Effort1 person-day(s) planned · 3 from scratch · size S
Area · appServer · server
Depends onSRV-29
UnblocksSRV-44, MRA-21, DES-31
Milestones—

Summary

Extend the V2 contract with every loyalty operation of change request 04, so mobile and design start in parallel.

Description

Change request 04 (client loyalty document and letter of 6 Nov 2026), not yet accepted or priced by HOCO. Adds to packages/contracts the 18 reseller and 25 back-office operations of the full programme, the new enums, and the additive voucherCode and cashbackAmount of cart.checkout, and publishes them on the mock server. LoyaltySummary moves to qualified purchases and configured levels. Out of scope: implementation (SRV-44 to SRV-50).

Subtasks

#SubtaskOwner
1Reseller operations: objective, levels, history, cashback, campaigns, missions, challenges, badges, referral, occasion, chests, wheel, reviewsAnis
2Back-office operations: dashboard, accounts, rules, simulate, recalculations, levels, campaigns, missions, challenges, badges, referrals, prize tables, reviews, occasionsAnis
3Level references as ids in place of the enum LoyaltyLevel in V2 schemas; note the V1 fields to migrateAnis
4Additive voucherCode, cashbackAmount and optional referralCode at sign-upAnis
5OpenAPI regeneration, oasdiff check, mock examplesAnis
6Contract review and Dart client regenerationImad

Deliverables

  • packages/contracts/src/{loyalty.ts,admin/loyalty.ts} extended
  • openapi.json minor version with CHANGELOG
  • Updated mock-api-staging

Acceptance criteria

  • Every new loyalty operation of endpoints.json exists with its method and path
  • No reseller response carries a reward stock, prize stock, budget or places-left number (STK-07, BR-99)
  • oasdiff reports no breaking change for V1 clients
  • Imad signs off the review

Requirements covered

RequirementTitleRelease
LOY-03Configurable levels: Standard at sign-up, then levels from qualified purchases over a configurable periodV2
LOY-06Missions and challenges: daily, weekly, monthly, seasonal; commercial, interaction, surprise and personalisedV2
LOY-07Monthly ranking: configurable criterion and Top N, reviewed results, prizes and home highlightV2
LOY-08Earning rules: barème by product, category, brand, quantity or amount, set in the back-officeV2
LOY-14Cashback balance, earning and use at checkoutV2
LOY-15Referral of new resellers with fraud controlsV2
LOY-18Gift chest with configured prizes, odds and budgetV2
LOY-19Wheel of fortune, optional, one spin per entitlementV2
LOY-21Personal objective: progress to the next level on the homeV2
LOY-22Full history: separate ledgers, one combined viewV2
LOY-23Back-office administration: every rule without a developer, reseller view, manual adjustmentsV2
LOY-24Programme dashboardV2
LOY-25Rule versioning: new operations only, or recalculationV2

API surface

Test measures

  • Contract diff test against endpoints.json
  • Spectral lint and oasdiff in CI

Risks

  • Decisions D-45 to D-63 are open: fields stay generic where the policy is not settled

KPI

  • Delivered by Mon 25 Jan 2027 within 1 person-day(s).
  • Every acceptance criterion above demonstrated before hand-off; linked requirements' acceptance criteria pass.
  • Zero open critical defects, permission gaps or data-integrity regressions at sign-off.

Generated from content/plan/tasks.json by scripts/generate-team-tasks.mjs. Dates are computed by the scheduler (Sunday–Thursday weeks, holidays excluded) — change the plan, not this page.

On this page