Product feedback

hi! we want to limit an applied coupon for a specific time (e.g. 30 days) - is this possible? I'm looking at deleting an applied coupon, but that doesn't sound right; i'd rather just terminate their applied coupon (without deleting it)

With the weighted sum billable metric, we have to send events with the sum to be added or subtracted. Ideally, we'd like to send the actual value it should be instead of only the sum amount to add/subtract. Right now weighted sum works like sending events with a value of “+100” or “-100”. That means if you send two additions and one subtraction you end up with a value of 100 and the weighted sum value is calculated based on the portion of time the amount spent as a “total” of that portion of time. This can cause issues if events get lost or if we need to reconcile the amount, because we don't know what the current total is of the weighted sum of values over time. We want to send what the total value should actually be and let Lago do the differentiation. So we’d send, 100, then 200, then 100 again which brings us to the same result.

We want the prices to be updated when we update them and Lago to do the prorata. Lago does not support it so we have to fall back to end of month updates. But what this means is that even at the end of month there is a buffer period where we can't really update the prices, we'll still announce it but it won't be visible since I have to wait for the end of the grace period. That's a lot of unhappy constraints on the pricing updates. When our competitors announce a price change on the 16th, usage is billed with past price from 1 to 15 and with new prices for the rest of the month.

As a company, we’d like to create a document that can be shared with our leads/customers to present a pricing proposal or agreement. This document should be reviewed and signed by stakeholders. Ideally, we’d like to automate this process in Lago and generate a one-off invoice or subscription accordingly with coupons, prepaid credits….

We have a need for multiple credit buckets (wallets). In our offerings we collect $X / year from our customers of which a part is for the fixed fee and then the remaining is for the usage. So, there is fixed fee credits and then credits for usage . Every month we need to deduct say, $A from the fixed free credits bucket and say, $B from the credits for usage bucket. We cannot have the same bucket for both. Once the user runs out of credits for usage, they will start paying. In future we may have different wallets for different class of service as well (a simple example could be like paying a mobile operator for voice and data from different wallets). In the invoice we need to show what is deducted from each wallet every month. It would be ideal if the invoice could also include what the balance was at the start of the month and then at the end of the month! Let me know if this feasible and/or you have questions around this.

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.

Ability to pause and resume subscriptions (sometimes after several billing periods) via the API and user interface as well. If a subscription is paused, the customer should not be billed. If the subscription is resumed over the course of a billing period, fees should be prorated.

Ability to add and switch between multiple payment profiles per customer without need to delete previous one, that gives the possibility to switch Stripe account for example. Also we can have a default set to true or false, to use that payment profile as default of not specified on API calls. Multiple payment profiles will give the ability to use multiple currencies per customer.

Currently we're able see to ongoing billing period but it would be nice to see in a daily view with some filtering & graph abilities.

Add invoice type (add-on/credit/subscription) column to Invoices page Add Manual as Payment Provider (and print info in invoices) Add invoice type filter http://localhost:8080/invoices/pendingFailed?invoice_type=credit (or may be something similar using UI) to show page with only unpaid top-up wallet invoices Add Mark Succeeded button directly to invoices grid Add user role Operator with access right to manage invoices and customer pages only (user role for staff who approve payments were succeeded) Ensure it's possible and have good UX: Operator can manage invoice statuses of manual payment provider only for add-on and top up wallet operations, restrict changing payment status for subscriptions (they are automatically processed using wallet balance) Do not try to implement this suggestion all-at-once. Do it step by step.