Pmitz / Product guide

Plans and limits in your product

A plan determines which existing features a customer can use. A limit determines how much they can use, over what period, and in which customer, user, subscription, or group context.

What Pmitz applies

Pmitz brings together three decisions in the path of an application action:

  1. Is the feature included in the configured plan?
  2. Does the requested amount fit the applicable limit?
  3. What usage has the application reported for this context and period?

You define the products, features, plans, and limits. Your application supplies consistent customer context, performs the feature, and explicitly reports its successful use.

Plan membership makes features available, while a usage check determines whether another action fits the allowance.
Conceptual illustration. Pmitz applies rules to features you have already implemented.

A music-service example

The example is an imaginary music application. It illustrates Pmitz’s rules; it is not a Pmitz music product or a customer case study.

Original planExisting featuresMonthly downloads
FreeMusic with ads, one listener10
PremiumAd-free music, family sharing100 shared by the family

With 70 downloads already reported under Premium, 30 remain under the original 100-download limit.

Plan changes

Suppose the music company makes two changes:

  • Feature change: Free gains the already implemented family-sharing feature. Its own monthly download limit stays at 10.
  • Limit change: Premium keeps family sharing and increases its monthly download allowance from 100 to 200.

Pmitz can apply changed plan membership and applicable limits through the feature checks your team has integrated. Your team still needs to make the changed configuration available. The music feature itself is not created or rewritten by Pmitz.

Free gains an existing family-sharing feature; Premium's download allowance increases from 100 to 200 per month.

A repeated old check can still stop someone at 100 even after your offer promises 200. Using shared definitions and reusable checks addresses that integration problem; it does not automatically replace old application code or guarantee instantaneous propagation.

Check, use, record

After the Premium limit changes to 200, the same family still has 70 downloads used:

StepResponsible systemWhat happens
CheckPmitzDownloads are included. One more download fits, with 130 remaining.
UseYour applicationPerforms one download successfully.
RecordPmitz, explicitly called by your applicationUpdates the period total to 71 used and 129 remaining.

The next decision uses the updated recorded total. Pmitz does not independently observe a download or discover that an application action succeeded.

Explore the interactive example or start the developer guide .

Customer-specific terms

The same Premium feature may have a standard limit of 200 downloads, while one customer has an agreed allowance of 500.

Customer contextUsedApplicable limitAnother download
Standard Premium200200Declined
Agreed customer exception200500Permitted

Pmitz supports user-specific limit overrides and user, subscription, or directory-group contexts. Your integration supplies the relevant context and configured rule. These exceptions are useful packaging tools; they are not exclusive to Pmitz.

Monthly totals and occupied slots

A monthly quota and a capacity limit count different things.

Monthly downloads

Last month7 / 10
This month0 / 10

A new calendar window has a separate total. Earlier records can remain while retained.

Saved playlists

4 / 10

Illustrative occupied slots. Creation uses a slot; a reported deletion frees one.

For monthly downloads, a calendar-month limit selects the current period. Last month’s seven downloads do not consume this month’s ten-download allowance. The first report in the new window creates or updates that period’s total. A missing current-period record is treated as zero usage by the default strategy.

For saved playlists, a count limit can describe ten occupied slots. The application reports successful creation to add one, and successful deletion to reduce one. Deleting a playlist can free a slot; deleting a downloaded song does not, by itself, reverse a monthly download.

Usage records are totals, not an activity journal

The supplied recording strategy updates a relevant total instead of creating an immutable event for each song. Records describe the limit, time window, units, expiration, and relevant product/feature/context metadata. They do not contain song names, event identifiers, historical plan snapshots, or saved reasons for past decisions.

Earlier period totals can remain in storage. Repository date criteria can retrieve retained records, while the normal usage API exposes current status and remaining units. A historical report or individual-event audit needs application evidence or an implemented extension.

The default strategy sets a timed record’s expiration to the period end plus three months; unwindowed counts have no expiration. Cleanup is an explicit repository operation. Actual retention depends on storage, strategy, and the cleanup policy; this is not a permanent-history or fixed SaaS-retention promise.

Responsibilities

ResponsibilityWho owns it
Choose commercial plans and pricesYour company
Establish identity and general role permissionsYour identity and authorization systems
Supply subscription status and customer contextYour integration and relevant subscription or billing system
Check configured plan membershipPmitz
Resolve and check applicable limitsPmitz
Perform or decline the actual featureYour application
Report successful use or an applicable reductionYour application calls Pmitz
Update the reported usage totalPmitz
Payments, invoices, and taxesYour billing system
Network and infrastructure protectionYour infrastructure and gateway systems

Supported contexts do not, on their own, establish combined hierarchical enforcement. Configurable rules do not imply a shipped nontechnical editor, an analytics dashboard, or ready-made billing connectors.

Evaluate the complete flow

Before agreeing production commitments, test the situations that matter to your integration:

  • Two requests arrive with one unit remaining.
  • A business action fails, is cancelled, or is retried.
  • A usage report is duplicated, or recording fails after business execution.
  • Several application instances share usage state.
  • Calendar periods change across time zones.
  • A plan changes while requests are in flight.
  • Pmitz or its database becomes unavailable.

The repository’s implementation and database tests support evaluating the product. They do not establish an atomic transaction spanning your business operation and usage reporting, automatic rollback of application activity, or production service levels.

Next steps

Integrate one feature , compare operating options , or read the complete product deck .