Written guide
Overview
Appmint Service Pricing shows which operation a price applies to, the unit being measured and whether it runs on the platform account or your own account. We will inspect a service’s calculation and agreement, then compare a controlled operation with its usage record.
1. Filter to the exact operation
Read one rate without confusing it with a product selling price
Service Pricing describes platform/provider operations. It is separate from Storefront → Pricing, which controls what shoppers pay for products. Open Service Pricing, search the operation you intend to use and select its row. Keep the same row's provider, billing model and account path together while reading the details.
| Check in Service Details | Why it matters before using the service |
|---|---|
| Provider and Operation | A provider can expose several operations with different rates. |
| Billing model and Currency | A recurring fee cannot be interpreted as a per-request fee. |
| Unit and Unit Size | A displayed unit may represent a batch, not one item. |
| Tier thresholds | The visible first-to-last range does not calculate your actual total. |
| Agreement | Inspect whether this specific service requires consent. |
| Platform / Your own account | Determines whether Appmint records the platform charge here or the external account bears it. |
Do not accept an agreement merely to explore the catalogue. Read the selected service first. If figures fail to load, use the error/retry state; a missing figure is not a zero-cost quote. Your organization's current catalogue is the rate source—this course deliberately does not freeze a sample monetary rate that can change.
Why this matters
Provider and operation matter: two services from the same provider can have different units, prices and account paths.
Follow these steps
Open Service Pricing. Search the service name and narrow All Providers and All Billing Models as needed. Read its row’s Service, Provider, Billing, Cost, Agreement, Account and This Month values. Open the row. In Service Details inspect Service Name, Provider and Operation; all is broader than a named operation. Record Currency, Billing Interval, Unit and Unit Size where shown.
Check the result: The price is tied to an identified operation and measurement rather than a guessed provider-wide rate.
2. Understand the displayed calculation
Why this matters
The catalogue supports free, one-time, recurring, per-use, per-unit and tiered models. The title or display string is not itself the arithmetic.
Follow these steps
Read the Pricing section for the selected service. For a unit model compare the displayed unit size and unit price with the intended usage amount. For recurring pricing note its billing interval; for tiered pricing read the displayed thresholds/rates before estimating. Keep missing values explicit. Inspect Account: Platform means the operation uses the platform account and is billed to the organization balance; Your own means it uses your provider account and is not billed here. That does not state the external provider charges nothing.
Check the result: The learner can interpret the actual selected price without assuming one model covers every service.
3. Accept or revoke the named agreement
Why this matters
Service Details exposes agreement state separately from pricing. Acceptance should be intentional and attributable to the company.
Follow these steps
Read Service Agreement in the selected service. Use the accept action only with authority and after reviewing the terms. Reopen and check the accepted state/time. For a controlled service whose dependency is understood, use the revoke action and confirm the new state after refresh. Return to its consuming feature and observe the actual effect; do not promise that revocation cancels already completed work or external charges.
Check the result: The displayed agreement corresponds to the saved service state.
4. Reconcile one real operation
Concept illustration: Service pricing describes an operation; usage records describe what was recorded. An advertised rate, recorded usage and collected payment are different facts. This is not an application screenshot or evidence that the action has run.
Why this matters
The monthly figure is accounting evidence, not proof of the task’s result. Keep both in view.
Follow these steps
Perform one authorized controlled operation from the relevant module, note its reference and observed result, then Refresh Service Pricing. Inspect This Month and the usage detail available through Services/Usage. Compare the operation, account path, unit and time window. If the result succeeded but usage is missing, retain both observations and inspect the service’s billing path. If a charge appears twice, investigate the operation references before repeating it. Use the actual account currency and units rather than a scripted universal rate.
Check the result: Operational success and accounting evidence are separately demonstrated.
Troubleshooting and recovery
Keep the exact record and operation visible when reading an error. Inspect persisted state before retrying a write; a timeout does not prove nothing happened. Correct the specific cause and verify the resulting record and consumer independently. An enabled feature, successful configuration save or administrative status is not proof of an external delivery, access boundary or money movement. Preserve unsupported behavior rather than simulating success.
Next steps
You can now use the module’s records and controls in context, and check the result at the point where it matters. Return to the relevant chapter for the advanced path and its verification.
Limitations and checks
Current service-pricing-catalog and Services agreement implementation inspected. Pricing data is runtime-provided. No charge, agreement change or monthly accounting reconciliation executed. Do not confuse the free Appmint applications with a provider’s optional metered services.