# 3. Bulk License Pricing User Type: **Super Administrator** Source: *Mi Digital Academy - Education CRM Features Document* --- ## 3. Bulk License Pricing ### 3.1 Tiered Pricing by License Volume **What it does:** Sets the tiered pricing by license volume: the price per license is set by the volume tier (the 10-50, the 51-200, the 201-500, the 500+), so the institute (or the enterprise) gets a better price per license as the volume increases. The Super Administrator defines the volume tiers (the count range, the price per license) so the bulk pricing is structured by the volume and the price is explicit per tier. **Sub-features:** - Volume tier: the tier per volume (the count range, the price per license) - Tier scope: the price is per license (the price per license in the tier) - Tier pricing: the pricing (the price per license decreases with the tier) - Price definition: the price defined by the Super Admin (the count range, the price per license) - Price application: the price applied (the license count determines the tier, the price is the tier's price) - Price record: the price recorded (the institute, the count, the tier, the price) - Audit logging of the price definition and the changes **Super Administrator User Journey:** 1. Super Admin defines the volume tiers: the count ranges (the 10-50, the 51-200, the 201-500, the 500+) and the price per license per tier (the price decreases with the tier); the price is per volume. 2. Sets the tier scope: the price is per license (the price per license in the tier); the scope is the license. 3. Sets the tier pricing: the pricing (the price per license decreases with the tier); the pricing is the volume reward. 4. Saves; the volume tiers are live, and the license count determines the tier (the price is the tier's price). 5. An institute buys the bulk licenses (the count, e.g., 150); the count determines the tier (the 51-200), and the price per license is the tier's price; the purchase is the price. 6. The price is recorded: the institute, the count, the tier, and the price; the record is the proof. 7. For a price change (a tier's price updated), Super Admin changes the price (the new price, the time); the change is recorded. 8. The price definition and the changes are audit-logged with the tier, the price, and the timestamp. **Rules & Edge Cases:** - The volume tier is per volume (the count range, the price per license); the price is explicit per tier. - The tier scope is the price per license (the price per license in the tier); the scope is the license. - The tier pricing is the volume reward (the price per license decreases with the tier); the pricing is the incentive. - A price change (a tier's price updated) is recorded (the new price, the time); it is auditable. - The volume tiers are visible (the count ranges, the prices per license); the bulk pricing is managed. - Price definition and changes are audit-logged with the tier, price, and timestamp. ### 3.2 Custom Enterprise Pricing **What it does:** Sets the custom enterprise pricing: for the large enterprises (the 500+ licenses, or the special cases), the pricing is custom (negotiated, not the standard tier), so the enterprise gets a price that fits its scale and its terms. The Super Administrator defines the custom pricing (the enterprise, the count, the price, the terms) so the enterprise pricing is structured and the custom terms are recorded. **Sub-features:** - Custom price: the price per enterprise (the enterprise, the count, the price, the terms) - Enterprise scope: the price is for the enterprise (the count, the terms) - Custom terms: the terms (the payment, the duration, the support) - Price definition: the price defined by the Super Admin (the enterprise, the count, the price, the terms) - Price application: the price applied (the enterprise's purchase is the custom price) - Price record: the price recorded (the enterprise, the count, the price, the terms) - Audit logging of the price definition and the changes **Super Administrator User Journey:** 1. An enterprise requests the bulk licenses (the count, e.g., 1000). Super Admin defines the custom price: the enterprise, the count, the price, and the terms; the price is per enterprise. 2. Sets the enterprise scope: the price is for the enterprise (the count, the terms); the scope is the enterprise. 3. Sets the custom terms: the terms (the payment, the duration, the support); the terms are the deal. 4. Saves; the custom price is live, and the enterprise's purchase is the custom price. 5. The enterprise buys the bulk licenses (the count, the custom price); the price is the custom price (the custom price applied, the terms met); the purchase is the price. 6. The price is recorded: the enterprise, the count, the price, and the terms; the record is the proof. 7. For a price change (a custom price updated), Super Admin changes the price (the new price, the new terms, the time); the change is recorded. 8. The price definition and the changes are audit-logged with the enterprise, the price, and the timestamp. **Rules & Edge Cases:** - The custom price is per enterprise (the enterprise, the count, the price, the terms); the price is explicit per enterprise. - The enterprise scope is the count and the terms; the scope is the enterprise. - The custom terms are the deal (the payment, the duration, the support); the terms are the structure. - A price change (a custom price updated) is recorded (the new price, the new terms, the time); it is auditable. - The custom prices are visible (the enterprises, the counts, the prices, the terms); the enterprise pricing is managed. - Price definition and changes are audit-logged with the enterprise, price, and timestamp. ### 3.3 Discount Eligibility for Bulk Purchases **What it does:** Sets the discount eligibility for bulk purchases: the discount for the bulk purchase (the volume discount) is set, so the institute (or the enterprise) gets the discount for the bulk purchase (the discount is the incentive for the volume). The Super Administrator defines the discount eligibility (the count, the discount) so the bulk discount is structured and the eligibility is explicit. **Sub-features:** - Discount eligibility: the eligibility per count (the count, the discount) - Discount scope: the discount is for the bulk purchase (the volume discount) - Discount definition: the discount defined by the Super Admin (the count, the discount) - Discount application: the discount applied (the bulk purchase gets the discount) - Discount record: the discount recorded (the institute, the count, the discount) - Discount change: the discount changed (the count, the discount updated) - Audit logging of the discount definition and the changes **Super Administrator User Journey:** 1. Super Admin defines the discount eligibility: the count (the license count) and the discount (the volume discount); the discount is per count. 2. Sets the discount scope: the discount is for the bulk purchase (the volume discount); the scope is the bulk. 3. Sets the discount tiers: the count tiers (the 10-50, the 51-200, etc.) and the discount per tier; the tiers are explicit. 4. Saves; the discount eligibility is live, and the bulk purchase gets the discount (per the count). 5. An institute makes the bulk purchase (the count, e.g., 300); the discount is applied (the count determines the discount, the discount is given); the purchase is the discount. 6. The discount is recorded: the institute, the count, and the discount; the record is the proof. 7. For a discount change (a count's discount updated), Super Admin changes the discount (the new discount, the time); the change is recorded. 8. The discount definition and the changes are audit-logged with the count, the discount, and the timestamp. **Rules & Edge Cases:** - The discount eligibility is per count (the count, the discount); the discount is explicit per count. - The discount scope is the bulk purchase (the volume discount); the scope is the bulk. - The discount tiers are explicit (the count tiers, the discount per tier); the tiers are the structure. - A discount change (a count's discount updated) is recorded (the new discount, the time); it is auditable. - The discount eligibility is visible (the counts, the discounts); the bulk discount is managed. - Discount definition and changes are audit-logged with the count, discount, and timestamp.