Subscription plans
Plans are based on restaurant scope, locations, POS terminals, KDS or Expo screens, workflow modules, API usage and agreed onboarding requirements.
Billing Terms.
Commercial billing boundaries for Limvero subscription plans, add-ons, provider fees and overdue accounts.
Billing rules
These rules explain how restaurant subscriptions, add-ons and provider-specific fees are separated.
Currency and taxes
Public launch prices are listed in UAH. Taxes, withholding, bank fees and currency conversion charges are handled according to the invoice and local law.
Provider fees
Payment acquiring, fiscalization, SMS, delivery marketplace, hardware and other third-party provider charges are separate from Limvero subscription fees.
Billing cycle
Billing cycle, renewal date, payment method, due date and annual or monthly commitment are confirmed in the order form or subscription agreement.
Add-ons and changes
Additional locations, terminals, KDS screens, imports, integrations or support packages may be prorated or quoted separately before activation.
Overdue invoices
Overdue accounts may receive payment reminders, feature restrictions or tenant suspension after reasonable notice and account review.
Billing operations
Billing operations are managed through Platform Admin controls and customer-specific commercial agreements.
Platform Admin billing
Limvero tracks tenant plans, subscriptions, invoices, usage counters, invoice status changes and billing automation in Platform Admin.
Auditability
Plan changes, invoice status changes, suspension actions and billing automation are designed to leave reviewable platform audit records.
Provider integration boundary
Billing provider reconciliation remains provider-specific and is enabled only after the selected payment or billing provider is contracted.
Billing terms work together with the signed agreement, pricing page, refund and cancellation policy, and tenant offboarding workflows.
Plan a clean restaurant rollout.
Talk through locations, POS devices, kitchen workflow, menu migration, API needs and security review before launch.