Product feedback

Our current workaround is to add the same billable metric to a plan multiple times and updating the tax rate per charge

When adding an add-on to a one-off invoice, have the ability to configure a service date or period that will be displayed in the invoice.

Some times, we need to charge an item once only such as integration fee for a specific feature and we don't want to send 2 invoices to our customer but one invoice with the subscription fee, the usages and the one-off items.

In addition to emails, we'd like to send payment reminders to customers via SMS.

Create a SDK function that able developer to get the subscription lifetime usage. currently We should call the API endpoint to get it and it make us to use two coding pattern in the code, SDK and API calls which is a kind of dirty coding in a project.

As a user, I want to schedule price increases. Consider the following example: My customer is on plan A, whose standard price is $1,000 per year. However, we have negotiated several discounts: 50% discount for the first year (i.e. total cost of $500); 25% discount for the second year (i.e. total cost of $750); and No discount afterwards (i.e. full price). I currently need to apply the first coupon and then wait until the end of the first year to apply the second one. It would be much more convenient if I could schedule ramp-ups when creating the subscription in the first place.

Invoices are not batched until the renewal period. This means if a customer has multiple subscriptions getting assigned at once or has a subscription plus an add-on fee, the invoices are generated and emailed individually. Second example related to this other feature request: https://getlago.canny.io/feature-requests/p/allow-add-ons-to-be-included-in-subscriptions

We use Microsoft Active Directory to manage user rights and permissions, so it would be great if we could use it to control access to Lago as well (i.e. signups and logins).

When we onboard our clients we need to create them an account in Lago and retrieve their API keys. It would be nice if an endpoint existed so that we can create the accounts and get the keys via API.

To comply with upcoming EU requirements, enrich the PDF invoices with machine readable XML data so that accounting software can parse invoices right away (without AI) (it's also actually useful). There is a great variety of 'standards' to choose from (xRechnung, ZUGFeRD, Peppol …). Please make that available in the community edition.