HOCO B2B
Team tasksAnis

DSH-14 — Back-office — commercial push, new catalogue, flash-sale fields, complementary products & smart-notification settings

Back-office screens for document 03: commercial push and new catalogue kinds in BO-57 with the push / inbox-only split, the Vente flash toggle in BO-50, complementary products and the new-arrival flag in BO-28, smart rules, action labels and settings in BO-58.

FieldDetails
Task codeDSH-14
PhaseP1 — V1 build & integration
Product scopeV1
StatusPlanned
StartMon 23 Nov 2026
DueTue 24 Nov 2026
ResponsibleAnis — Full-stack developer
Co-responsible—
Effort0.75 person-day(s) planned · 3 from scratch · size S
Area · appBack-office · dashboard
Depends onDSH-04, DSH-09, DSH-10, SRV-40
Unblocks—
Milestones—

Summary

Back-office screens for document 03: commercial push and new catalogue kinds in BO-57 with the push / inbox-only split, the Vente flash toggle in BO-50, complementary products and the new-arrival flag in BO-28, smart rules, action labels and settings in BO-58.

Description

HOCO picks a product and an audience and sends a commercial push (SN-23); publishes a new catalogue edition (SN-19); runs flash sales of 2 h to 48 h (SN-18); configures complementary products (SN-14); and tunes the smart notifications without a deployment. All of it extends existing pages (BO-28 from DSH-04, BO-50 from DSH-09, BO-57/58 from DSH-10) with the fields of SRV-39 and the server behaviour of SRV-40.

Subtasks

#SubtaskOwner
1BO-57: Type selector (Message, Push commercial, Nouveau catalogue), target picker, action label, « Acheteurs de la catégorie » criterion, recipient split (push / inbox only) before sending, PDF upload for the catalogueAnis
2BO-50: « Vente flash » toggle with quick durations 2 h / 6 h / 24 h / 48 h, exclusivity with « Offre du jour », FLASH_SALE_DURATION error mappingAnis
3BO-28: « Produits complémentaires » picker (max 5, drag to order, no self) and « Annoncer comme nouveauté »Anis
4BO-58: smart events in Règles (group, priority, switch), Bouton d'action in Modèles, « Notifications intelligentes » settings tab (caps, windows, delays, thresholds), auditedAnis

Deliverables

  • apps/dashboard/src/app/(app)/communication/announcements/* (kinds), communication/notifications/* (smart tab)
  • apps/dashboard/src/app/(app)/promotions/[id]/* (flash toggle), catalog/products/[id]/* (complements)

Acceptance criteria

  • A commercial push to wilaya 31 shows the recipient split before sending and matches the delivery log after (NOT-16)
  • A 72 h flash sale cannot be saved; a 6 h one appears on the reseller Ventes flash tab at its start (PRM-07)
  • A product cannot list itself or more than 5 complements (NOT-15)
  • Changing the weekly cap in BO-58 applies to the next dispatch and is audited (NOT-17)

Requirements covered

RequirementTitleRelease
NOT-10An action button (label and deep link) on every reseller notificationV1
NOT-11Catalogue notifications: new arrival, new catalogue, trending product of the weekV1
NOT-15Complementary product suggestions from pairs configured on the productV1
NOT-16Commercial push: HOCO picks a product and an audienceV1
NOT-17Anti-fatigue rules: promotional push caps, priority, merge, quiet hours, opt-out per groupV1
PRM-07Flash sales (2 h to 48 h) with countdown and the promotion tabs Promotions / Flash SalesV1

Screens

ScreenNameApp
BO-28Product editorBO
BO-50Promotion editorBO
BO-57AnnouncementsBO
BO-58Notification templates & rulesBO

API surface

Test measures

  • Component tests of the recipient split and the flash duration picker
  • Playwright: create a flash sale, send a commercial push to a test reseller, see it in the reseller web inbox

Risks

  • Commercial pushes used as a mass-marketing channel — the caps still apply and the split makes it visible

KPI

  • Delivered by Tue 24 Nov 2026 within 0.75 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