#mameluc_best-practices
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
๐ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1276543672300732447
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
I don't recommend creating a price for each device. Assuming each device costs the same amount, you can just use 1 price and change the quantity of that item on the subscription depending on how many devices the customer has
Really I recommend storing device id's in your database
But how does the customer know for which devices he has paid?
I do have a device table ๐
I guess my question is how to tie a bunch of unique devices to a subscription
If the user has 10 devices but don't want to pay for 1 of them
If you're keeping track of this in your database, then you can present the data to your customer in your app
I mean it's up to you. You can have device id tied to a price, but imo that unnecessarily complicates things
It'd be easier to keep track of this in your database
And just change the quantity of the subscription item depending on how many of the devices they're paying for
ok makes sense, just a bummer that then I can't show on the invoice which devices the user is paying for
Yeah up to you. If that's a requirement, then it does make sense to have each device be its own item
Thank you for your help ๐