HOCO B2B
Team tasksAkram

DES-16 — Day 16 — Back-office: CRM

Resellers list and map, reseller 360°, create/edit, validation queue, follow-ups, segments.

FieldDetails
Task codeDES-16
PhaseP0 — Foundations (cadrage, UX/UI, architecture & contract)
Product scopeV1
StatusPlanned
StartMon 9 Nov 2026
DueMon 9 Nov 2026
ResponsibleAkram — UI/UX designer
Co-responsible—
Effort1 person-day(s) planned · 1.25 from scratch · size S
Area · appBack-office design · design
Depends onDES-15
UnblocksDSH-03, DES-17
Milestones—

Summary

Resellers list and map, reseller 360°, create/edit, validation queue, follow-ups, segments.

Description

Day 16 designs the back-office CRM, one place for every reseller and prospect from first contact to active account. That includes reviewing the customer type each reseller declared at sign-up (AUTH-11). The screens are BO-09 list, BO-10 map, BO-11 reseller 360°, BO-12 create/edit, BO-13 account validation queue, BO-14 follow-ups and BO-15 segments; BO-09, BO-10, BO-11 and BO-13 are bespoke and the others template pages. Inputs: cahier §4.2 and §15.5, CRM-01…12, FLD-14, IVT-03, AUTH-11, the ResellerStatus (10 values) and CustomerType enums, and the operations admin.resellers.*, admin.tasks.*, admin.segments.crud and admin.invitations.list. The customer type is only changed by the back-office, with a reason, and audited. Consumer: Anis's DSH-03 (BO-09…15).

Subtasks

#SubtaskOwner
1BO-09 Revendeurs et prospects: table with REV- number, store, owner, phone 0555 12 34 56, wilaya / commune, ResellerStatus and CustomerType pills, delegate, last order, potential; filters (status, zone, wilaya, commune, délégué, segment, potential, customer type, activity); saved views; bulk assign, status change and export; list/map toggleAkram
2BO-10 Carte des revendeurs: status-toned circle markers with store glyph, clusters, zone polygons, filters shared with BO-09, side list synced, legendAkram
3BO-11 Revendeur 360° header: name, REV-000123 with copy, ResellerStatus and CustomerType pills, delegate, zone, quick actions (call, WhatsApp, new task, new order on behalf, suspend)Akram
4BO-11 tabs: Aperçu, Commandes, Factures et paiements, Visites et rapports, Relances, SAV et retours, Historique, Documents et photos, Invitation (6-step funnel); each tab's data source annotatedAkram
5BO-11 « Modifier le type de client » action: modal with the new type, a required reason and an audit note, then a history line « Type de client : Détail → Demi-gros — par … »Akram
6BO-12 create/edit (Form template): duplicate phone check with link to the existing record, wilaya → commune, GPS map picker, business type, potential, customer type, delegate and zone assignment, documents and photosAkram
7BO-13 Validation des comptes (bespoke): queue oldest first; side-by-side review with façade photo, GPS on a map, declared customer type to confirm or correct, documents, duplicate suspicion; approve (toast with « Annuler » for 6 s) or reject with a required reason; empty queueAkram
8BO-14 Relances (List template): overdue, due today, upcoming and done tasks; assignee; TaskType; complete and reschedule. BO-15 Segments: rule builder (potential, business type, brands sold, activity) with a live member countAkram
9Page specs for the template pages: columns, filters, row and bulk actions, permissions, empty-state copyAkram
10Feasibility: 360° tab queries, map clustering, duplicate check UX on create and validationAnis

Deliverables

  • Claude Design › Back-office › BO · CRM with BO-09…BO-15 (bespoke pages fully designed, template pages as filled page specs)
  • BO-11 tab → data source annotation and the customer-type change flow
  • BO-13 validation review layout with approve/reject states

Acceptance criteria

  • The validation queue shows the declared customer type with confirm and correct actions
  • A customer-type change always requires a reason and leaves a history line (AUTH-11)
  • All 10 ResellerStatus values and 3 CustomerType values render with enums.json labels and tones
  • The duplicate-phone check is visible on create, edit and validation
  • Every template page has a filled page spec (columns, filters, actions, permission, empty copy)
  • Anis's review answer is OK or OK with notes

Requirements covered

RequirementTitleRelease
CRM-09Account validation by an authorised user (approve / reject with reason)V1
CRM-11CRM list and map views with filters (status, zone, wilaya, commune, delegate, segment, potential, activity) and exportV1
CRM-12Reseller 360° page: orders, invoices, payments, visits, reports, tasks, interactionsV1

Screens

ScreenNameApp
BO-09Resellers & prospects listBO
BO-10Resellers mapBO
BO-11Reseller 360°BO
BO-12Reseller create / editBO
BO-13Account validation queueBO
BO-14Follow-ups & tasksBO
BO-15SegmentsBO

Test measures

  • Walkthrough of the field-signup → BO-13 approval → BO-11 path with Anis
  • Table density check at 1280 with 9 columns (no page-level horizontal scroll)
  • Check the filters against CRM-11 and the 360° content against CRM-12

Risks

  • The 360° page gets too dense — use tabs with counts and keep the Aperçu tab to 6 key facts plus the activity feed.

KPI

  • Delivered by Mon 9 Nov 2026 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