Plan

What it is

Plan is the "product" template a user can subscribe to. After checkout, the system creates a Subscription instance from one Plan.

Where to find it

Admin → Plans: list, add, publish / unpublish
Public → Subscribe: only published plans are visible
Admin → Plan Settings: global upgrade / expiry policy

Operator-relevant fields

Field	Meaning	Effect
Name	Shown to the user	Updating it updates everywhere.
Price	¥	The amount the user is charged.
Quota	Internal units	Total allowance for the period; after exhaustion the plan's discount no longer applies.
Validity	Days	After expiry → "plan expired" status, but calls still work until quota runs out.
Discount multiplier	Number	Multiplies the deduction while the plan is active.
Description	Rich text	Shown on the subscribe page.
Status	Published / unpublished	Unpublished stops new subscriptions; existing ones are unaffected.
Recommended	Toggle	Shows the "Recommended" badge on the public card.

Plan vs Subscription

Plan: the template — name, price, quota, validity.
Subscription: an instance — a user subscribing to a Plan at a specific moment. One user can hold multiple over time.

Upgrades and differentials

When switching from Plan A to a higher-priced Plan B:

If B.price > A.price, a differential order is created (prefix UP)
Remaining days / quota are pro-rated into the new plan

Upgrade rules are maintained in Plan Settings.

GET /api/plan/ — list (admin)
GET /api/plan/list — list (public)
POST /api/plan/ — add
PUT /api/plan/ — update
DELETE /api/plan/:id — delete