Dynamic pricing changes an amount using rules and data defined by the business. Applying it to a subscription requires knowing what changes, when the calculation happens, who is affected and how customers are informed before collection. The gateway processes a payment; the logic determining its amount belongs to the system managing the offer.
For a digital business operating from Andorra, start with the practical need. Several plans, a change at the next renewal or a usage rule may be enough. At AndorPay, we review how to connect the payment journey to that decision within the integration's actual capabilities.
Not every change is dynamic pricing
Switching plans, consuming more units and revising commercial terms are different situations. Calling them all “dynamic” can hide the work required and confuse the buyer's expectations.
| Situation | What causes the change | Main work |
|---|---|---|
| Plan change | Selection of another option | Effective date and access |
| Usage-based collection | Consumed units | Measurement and period calculation |
| Offer revision | Newly defined terms | Versions and communication |
| Dynamic rule | Data changing the amount | Traceable calculation and limits |
A monthly plan with a stable amount remains a subscription even if another plan has different terms. You do not need artificial intelligence to apply a rule either. Start with an explanation you can give customers before discussing software.
Define the variable and its purpose
A rule needs inputs, a calculation point and an expected result. If the amount depends on consumed units, you need a usage record. If it depends on a selected configuration, retain that choice and when it took effect.
Saying that pricing “adapts” is insufficient. Explain which action or condition can change it. Buyers should be able to anticipate the relationship between service use and the next payment without knowing the technical implementation.
Include boundaries and exceptions. What happens if a value is missing, late or impossible? An incomplete calculation should not silently become a final charge. Establish review or an explicit handling rule for those cases.
Retain the calculation actually used
To answer a question, your team needs to reconstruct the period's amount. Keep the rule version, input data, calculation date and result approved for collection. Recalculating months later with current data may produce a different explanation from the original purchase.
Imagine a service whose scope depends on active users at period close. Define “active”, the measurement date and how added or removed users are treated. Without those rules, two people can reach different results using the same account list.
If the definition changes later, preserve the previous version for closed periods. This history has an immediate customer-service benefit: your team can explain a discrepancy using facts rather than inventing a reason after payment.
Keep adjustments visible as well. Correcting an input should leave enough context to distinguish the original calculation from the approved correction. Overwriting the final amount without the reason makes later questions harder to resolve.
Coordinate changes with the subscription period
Before applying a new rule, distinguish new purchases from existing subscriptions. Establish the effective date and treatment of a period already underway. The current website should not be the only reference for conditions accepted earlier.
A policy may retain current-period terms and apply a change at the next renewal where appropriate. If another behaviour is needed, define its effect on access, calendar and amount. A commercial decision does not automatically update all those components.
The WooCommerce product and subscription documentation illustrates that catalogue entries and individual subscriptions are different concepts. Check their relationship in your own integration too: editing a product record does not itself prove a correctly applied customer change.
Explain the effect the buyer will see
A useful message states what changes, when and the next action. If the change depends on consumption, customers need a recognisable summary. If it depends on selecting another plan, they need to understand the features and effective date.
Avoid explanations describing only technology. “Our algorithm updated your terms” does not help someone understand the payment. Use service language: users, sessions, scope or period, together with a specific date where one has been determined.
Keep the offer, pre-payment summary and confirmation consistent. If a screen shows a provisional calculation, label it accordingly. Do not present a final figure and later change it without an understandable reason and an applicable process.
Identify the integration work
The application needs to produce a valid amount associated with the customer, plan and period. Collection must use the supported journey for that case. The financial result then returns to business operations to update the relevant records and service state.
Our API documentation sets restrictions on amounts and distinguishes plan-change operations. These contracts should not be read as a general dynamic-pricing engine. External calculation, scheduling and compatibility are reviewed within the setup scope.
Separate a requested change from a confirmed change. A request may be scheduled for later or conflict with an outstanding action. The application should explain its actual state instead of claiming that a new period is active before that has been verified.
Also define who owns the calculation. If your product already produces approved amounts, the work differs from building those rules for the first time. Making that boundary explicit gives the implementation a concrete starting point.
When a simpler structure meets the need
If customers fall into stable groups, clear tiers may be sufficient. If the difference comes from units, usage-based billing may fit. If you want to revise an offer occasionally, versioning and communication may solve the problem without a variable calculation for every payment.
Our subscription plan guide covers features and limits. Our usage-based billing guide covers measurement and closing periods. Choose according to the decision you actually need to make.
Added complexity brings work: recording inputs, explaining differences, handling exceptions and testing changes. Introduce it when it solves a concrete service problem. A clear offer does not need to become difficult to maintain in order to appear sophisticated.
Test rules before collecting their results
Prepare input examples and expected outcomes. Include normal, absent, repeated and late data. Test a rule change between periods and verify that the earlier period retains its original explanation.
Then test payment. The approved amount should belong to the correct customer and period. A pending outcome needs follow-up on the same transaction. A repeated notification must not produce another delivery or another charge.
Check cancellation or a plan change while a calculation is ready. The integration needs to establish which rule remains valid and prevent conflicting actions. These cases show whether commercial logic and scheduling are connected in practice.
What to bring to a model review
Prepare a description of the service, the variable you want to use, the calculation point and two situations producing different results. Add how the customer will see the difference and which system holds the data.
That information lets us review the payment journey and define the required work. Commercial setup terms are prepared privately. Tell us what needs to change in your subscriptions, and we can assess its connection with AndorPay.
Frequently asked questions
Is switching plans dynamic pricing?
It is the selection of another option, which may have different terms. It does not necessarily require a dynamic calculation. Coordinate the effective date, next payment and new access rights.
Does the gateway calculate the appropriate price?
Processing payment and determining the amount are different responsibilities. Calculation belongs in the tool holding the necessary rules and data, and its result must fit the available payment contract.
Does this model always improve revenue?
There is no guaranteed result. It may address an offer requirement while also adding management and explanation. Define the problem and verify the journey before increasing complexity.
