LexiFlow ยท Templates and documents
Document quotas and billing: current behavior
A document is one generated output file, not an entire CSV batch or flow. The public pricing cards use the active plans stored in the application.
What the usage counter currently tracks
The standard generation form checks your remaining monthly allowance and increments usage for template generation and each template in a flow. Its current counter can also increase when generation fails. CSV, API, onboarding and regeneration paths do not consistently use this same counter. These differences are implementation limitations, not a promise of unlimited use.
When the allowance resets
Usage is recorded by calendar month in the application timezone, using a YYYY-MM period. It resets for a new calendar month; it is not tied to your subscription renewal date. Generating again through the standard form consumes usage again. Downloads do not increment this counter.
When paid access becomes active
The application applies subscription and plan changes when it receives and processes the corresponding verified Paddle webhook. Completing checkout and seeing the return page does not itself prove activation. The code does not establish a general rule that all upgrades wait until the next billing cycle.
Cancellation and plan changes
Cancellation is requested for the next billing period through Paddle. Check your account and checkout details for actual plan-change timing and charges. If a change is not reflected after payment, contact support.
API, signatures and users
Stored plans include feature labels and max_users. The current code does not establish consistent API quota checks, a dedicated API rate limit, a signature allowance or team-seat enforcement. Contact support to confirm requirements instead of treating marketing labels as guaranteed limits.
Taxes and checkout
Paddle processes checkout. Review the currency, taxes and final total shown there before paying; the public plan price alone does not establish a tax-inclusive amount.