# NVG-BEA-013 — AR Try-On & Service Visualisation — PLACEHOLDER (no development)

**Status: PLACEHOLDER — 2026-07-26. Full spec pending a product definition session with
Muhannad. Development explicitly NOT started, per the BRD.**

## What the BRD says
An add-on the shop purchases as a **consumable** (alongside SMS notifications, WhatsApp
notifications, Bulk SMS campaign, Bulk WhatsApp campaign): usage limit per bundle,
re-purchasable once consumed.

## To be defined before development
1. AR provider / SDK selection.
2. Which service categories support AR visualisation.
3. How shops upload/select AR models for their services.
4. Full functional requirements, business rules, acceptance criteria.
5. Usage limit per purchased bundle + pricing. [Owner: Muhannad]

## Readiness notes from the current codebase (for when the spec lands)
- **The consumable-add-on pattern already exists**: SMS/WhatsApp fees are charge types on
  the immutable `charge` ledger (`Charge::TYPE_SMS_*`/WA, `meta.count` billing), quotas
  live in plan features / posting-limit patterns, and the Detailed Charges report
  (NVG-BEA-006) already anticipates "AR try-on fee" as a future charge type — adding a
  `TYPE_AR_TRYON` line item will surface automatically in both portals' reports once
  labeled in the two `chargeDescription()` maps.
- Plan feature gating is enforced via `EntitlementService` + `EntitlementFilter`
  (NVG-BEA-003) — an AR feature key would slot into the same catalogue.
- Purchases/consumption would follow the subscription/charge rails (Paymob MOTO or bank
  transfer) built in NVG-BEA-003.
- The api/ tier is a shared mobile contract — any AR endpoints must be additive and
  coordinated with the mobile team (same rule as BEA-010/011).

**Nothing else to do until the definition session.**