Docs

Billing Center

Resource Packages

About packages

1. Resource type

According to the type of effect packaging, it can be divided into three types: decreasing, periodic and mixed:

resource type	explain
diminishing type	The total amount is fixed, and the balance continues to decrease with the deduction until the balance is cleared or expires;
periodic	The total amount is fixed in each reset cycle, and the balance is continuously reduced with the deduction, and it cannot be transferred to the next cycle. The balance at the beginning of the next reset cycle is restored until it expires;
mixed type	The total amount is fixed in each reset cycle, and the balance is continuously reduced with the deduction, and the balance of future cycles can be deducted in advance until the total balance is cleared or the effect package expires;

2. Deduction rules

2.1 deduction logic

After the amount of the cloud product instance is generated, the effect package will be used for deduction first, and the excess part will be deducted by issuing a bill; when the following conditions are met, the effect package can be used for deduction:

The effect package supports the deduction of volume-based billing items for the amount generated;

During the generation time period of the amount corresponding to the amount billing item, the effect package is in the "effective" state;

In addition to the above general rules, there are the following special rules:

If the effect package specifies a deductible instance, the effect package can only deduct the amount of the specified instance, and cannot deduct the amount of other instances;

Preemptive instances do not support the use of reserved instance vouchers;

The relevant deduction rules for non-platform unified effect packages such as enterprise live broadcasts are subject to the cloud product description;

Financial custody scenario:

For the volume-based billing example of the sub-account, the effect package of the sub-account can be used to deduct, or the effect package of the main account can be used to deduct, and the sub-account's own effect package is preferred for deduction;

The billing instance of the main account can only be deducted by the effect package of the main account, and cannot be deducted by the effect package of the sub-account;

Dropshipping & agency business scenarios:

For the billing instance of the end point customer, the effect package under the name can be used for deduction;

Dropshipping & agency partners inherit the end point customer's effect package deduction amount, and cannot use their own effect package to deduct the end point customer's amount;

In the direct selling scenario, dropshipping & consignment partners can still use their own effect packages to deduct their own billing instance usage;

2.2 Priority of deduction order

If there are multiple deductible effect packages under the user name at the same time, the system will deduct according to the following priority: expiration time > resource type > effective time ;

Priority is given to using effect packages with early failure time; for periodic effect packages, failure time refers to the end time of the current reset cycle;

If the failure time is the same, the cyclical effect package will be deducted first, and then the decreasing effect package will be deducted.

If the effect package type and expiration time are the same, the effect package with the earlier effective time will be used for deduction; for the periodic effect package, the effective time refers to the start time of the current reset cycle;

Last updated: 2025.07.17 21:30:38