#hrwells789
1 messages · Page 1 of 1 (latest)
Hi there 👋 charging per table sounds like a reasonable approach here, as your price seems to be based around the number of tables reserved.
I don't think I'm grasping the concern with charging on a per-table basis, can you try elaborating on that to help me understand why that approach won't work for your scenario?
Thanks for your reply.
Our software provides QR code ordering to restaurants. So a given restaurant would be able to create a unique QR code for each table they have.
Therefore, we want to charge a monthly fee based on the number of tables.
Sounds like charging them in a per-seat fashion (where each "seat" is a table) is the right approach then. You can create a Price representing how much you charge for one table, and then set the quantity to scale the price accordingly.
Ah ok I misunderstood the seat to be a user
Ah, gotcha, you can think of "per-seat" to be equavilent to "per-unit". Sometimes different terms get thrown around depending on what industries someone typically works with.