SRV-12 — Pricing engine

SummaryCopy Anchor Link

Three selling prices per variant (super-gros, demi-gros, détail) chosen by the reseller's customer type, VAT, price history; prices withheld from guests; promotions applied on top by the cart engine.

DescriptionCopy Anchor Link

The 17 Oct decision replaces segment price lists with three selling prices per variant, one per customer type (PRC-01, PRC-02, PRC-04, PRC-05; cahier §4.3, §4.7, §8): priceSuperGros, priceDemiGros, priceDetail in integer centimes HT, plus vatRate (default 19 %), recommendedPrice and the restricted purchasePrice. This task implements the price resolver used by catalog, cart, orders and assisted orders — the reseller's Reseller.customerType selects the base price, promotions are applied on top by the cart engine (SRV-19 hook), guests get null — the HT/VAT/TTC computation and rounding rules for lines and documents, the PriceChange history for every price edit with admin.variants.priceHistory, margin computation for authorised staff, and cache invalidation when a price or a reseller's customer type changes. Per-reseller agreements and level prices stay V2 (PRC-03); quantity tiers are dropped. Out of scope: promotion rules (SRV-19) and the pricing UI (DSH-04).

SubtasksCopy Anchor Link

DeliverablesCopy Anchor Link

• apps/server/src/modules/pricing/{resolver.ts,tax.ts,price-history.service.ts,router.ts}
• packages/shared/src/money.ts (centimes arithmetic, VAT, formatting 1 250,00 DA)
• Pricing rules section in /docs/srs/business-rules updated with the rounding rule

Acceptance criteriaCopy Anchor Link

• A SUPER_GROS, a DEMI_GROS and a DETAIL reseller each see their own price for the same variant, and never another type's price (PRC-02, PRC-05)
• A guest sees price null on every catalog and promotion read (AUTH-10)
• Every price edit creates one PriceChange row per changed price with actor and timestamp (PRC-01, AUD-02)
• Order and invoice totals equal the sum of rounded line totals: HT + VAT = TTC to the centime (PRC-04)
• Changing a reseller's customerType in the back-office re-prices their cart on the next cart.get

Requirements coveredCopy Anchor Link

ScreensCopy Anchor Link

API surfaceCopy Anchor Link

Test measuresCopy Anchor Link

• Unit tests for resolver and tax rounding with edge cases (1 centime lines, 0 % VAT)
• Property test: sum of line TTC equals document TTC
• DB test for PriceChange writes on concurrent edits

RisksCopy Anchor Link

• HOCO decides TTC display late — the display rule is a setting and amounts are always stored HT with VAT, so only presentation changes

KPICopy Anchor Link

• Delivered by Sun 18 Oct 2026 within 0.5 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.