# 7. Price History & Control

User Type: **Super Administrator**
Source: *Mi Digital Academy - Education CRM Features Document*

---

## 7. Price History & Control

### 7.1 Update Prices Over Time
**What it does:** Sets the update of prices over time: the prices are updated over time (the price changes, the new price is set), so the pricing reflects the current value (the price is updated per the business needs). The Super Administrator updates the prices (the item, the new price, the effective date) so the price updates are structured and the changes are explicit.

**Sub-features:**
- Price update: the update (the item, the new price, the effective date)
- Update scope: the scope (the item, the price)
- Effective date: the date (the date the new price is effective)
- Update definition: the update defined by the Super Admin (the item, the new price, the date)
- Price application: the price applied (the new price is applied from the effective date)
- Price record: the price recorded (the item, the old price, the new price, the date)
- Audit logging of the price updates

**Super Administrator User Journey:**
1. Super Admin updates the price: the item (the one the price is for), the new price, and the effective date (the date the new price is effective); the update is explicit.
2. Sets the update scope: the scope (the item, the price); the scope is the item.
3. Sets the effective date: the date (the date the new price is effective); the date is the timing.
4. Saves; the price update is live, and the new price is applied from the effective date.
5. From the effective date, the new price is applied (the new price is the price, the old price is the history); the price is the new price.
6. The price is recorded: the item, the old price, the new price, and the date; the record is the proof.
7. For another update (a price updated again), Super Admin updates the price (the new price, the new date); the update is recorded.
8. The price updates are audit-logged with the item, the old price, the new price, and the timestamp.

**Rules & Edge Cases:**
- The price update is per item (the item, the new price, the effective date); the update is explicit.
- The update scope is the item and the price; the scope is the item.
- The effective date is the timing (the date the new price is effective); the date is the control.
- A price update is recorded (the item, the old price, the new price, the date); it is auditable.
- The price updates are visible (the items, the old prices, the new prices, the dates); the price history is managed.
- Price updates are audit-logged with the item, old price, new price, and timestamp.

### 7.2 Control Price Visibility
**What it does:** Sets the control of price visibility: the visibility of the prices (the prices shown to the learners, the prices hidden) is controlled, so the pricing is shown per the business needs (the prices are visible or hidden per the item, the region, the time). The Super Administrator configures the visibility rules (the item, the visibility, the scope) so the price visibility is structured and the control is explicit.

**Sub-features:**
- Visibility rule: the rule (the item, the visibility, the scope)
- Visibility scope: the scope (the item, the region, the time)
- Visibility control: the control (the prices shown, the prices hidden)
- Rule definition: the rules defined by the Super Admin (the item, the visibility, the scope)
- Visibility application: the visibility applied (the prices are shown or hidden per the rule)
- Visibility record: the visibility recorded (the item, the visibility, the scope, the time)
- Audit logging of the visibility rules and the applications

**Super Administrator User Journey:**
1. Super Admin configures the visibility rules: the items (the one the rules are for), the visibility (the shown, the hidden), and the scope (the region, the time); the rules are explicit.
2. Sets the visibility scope: the scope (the item, the region, the time); the scope is the control.
3. Sets the visibility control: the control (the prices shown, the prices hidden); the control is the visibility.
4. Saves; the visibility rules are live, and the prices are shown or hidden per the rule.
5. A learner views the prices; the visibility is applied (the prices are shown or hidden per the rule); the visibility is the control.
6. The visibility is recorded: the item, the visibility, the scope, and the time; the record is the proof.
7. For a rule change (a visibility rule updated), Super Admin changes the rule (the new visibility, the new scope, the time); the change is recorded.
8. The visibility rules and the applications are audit-logged with the item, the visibility, and the timestamp.

**Rules & Edge Cases:**
- The visibility rule is per item (the item, the visibility, the scope); the rule is explicit.
- The visibility scope is the item, the region, and the time; the scope is the control.
- The visibility control is the shown or the hidden; the control is the visibility.
- A rule change (a visibility rule updated) is recorded (the new visibility, the new scope, the time); it is auditable.
- The visibility rules are visible (the items, the visibilities, the scopes); the price visibility is managed.
- Visibility rules and applications are audit-logged with the item, visibility, and timestamp.

### 7.3 Grandfather Existing Subscriptions at Old Prices (If Applicable)
**What it does:** Sets the grandfathering of existing subscriptions at old prices: when the price is updated, the existing subscriptions (the ones made at the old price) are grandfathered (they keep the old price for their duration), so the existing learners are not affected by the price change (the new price is for the new subscriptions). The Super Administrator configures the grandfathering rules (the grandfathering, the duration, the scope) so the grandfathering is structured and the rules are explicit.

**Sub-features:**
- Grandfathering rule: the rule (the grandfathering, the duration, the scope)
- Grandfathering scope: the scope (the existing subscriptions, the old price)
- Grandfathering duration: the duration (the duration the old price is kept)
- Rule definition: the rules defined by the Super Admin (the grandfathering, the duration, the scope)
- Grandfathering application: the grandfathering applied (the existing subscriptions keep the old price)
- Grandfathering record: the grandfathering recorded (the subscription, the old price, the duration, the time)
- Audit logging of the grandfathering rules and the applications

**Super Administrator User Journey:**
1. Super Admin configures the grandfathering rules: the grandfathering (the existing subscriptions keep the old price), the duration (the duration the old price is kept), and the scope (the existing subscriptions); the rules are explicit.
2. Sets the grandfathering scope: the scope (the existing subscriptions, the old price); the scope is the grandfathering.
3. Sets the grandfathering duration: the duration (the duration the old price is kept); the duration is the period.
4. Saves; the grandfathering rules are live, and the existing subscriptions keep the old price.
5. A price is updated; the grandfathering is applied (the existing subscriptions keep the old price, the new subscriptions get the new price); the grandfathering is the control.
6. The grandfathering is recorded: the subscription, the old price, the duration, and the time; the record is the proof.
7. For a rule change (a grandfathering rule updated), Super Admin changes the rule (the new grandfathering, the new duration, the new scope, the time); the change is recorded.
8. The grandfathering rules and the applications are audit-logged with the subscription, the old price, and the timestamp.

**Rules & Edge Cases:**
- The grandfathering rule is per subscription (the grandfathering, the duration, the scope); the rule is explicit.
- The grandfathering scope is the existing subscriptions and the old price; the scope is the grandfathering.
- The grandfathering duration is the period (the duration the old price is kept); the duration is the control.
- A rule change (a grandfathering rule updated) is recorded (the new grandfathering, the new duration, the new scope, the time); it is auditable.
- The grandfathering rules are visible (the subscriptions, the old prices, the durations); the grandfathering is managed.
- Grandfathering rules and applications are audit-logged with the subscription, old price, and timestamp.