#just-john_dynamic-price-product
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/1288910347733962753
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- john_stripejs-localhost, 2 days ago, 23 messages
- just-john_docs, 5 days ago, 23 messages
Hello! You're on the right track. You can specify ad-hoc Price data using phases.items.price_data instead of creating distinct Prices: https://docs.stripe.com/api/subscription_schedules/create#create_subscription_schedule-phases-items-price_data
You will need to create a Product, but you can reuse the Product for many different price_data specifications.
Example billing scenario for reference:
Customer books a stay today for Jan 1 through April 15. Rent and security deposit are $1000 We should bill them
- $2000 Jan 1
- $1000 Feb 1
- $1000 Mar 1
- $500 April 1
Okay, yes. This looks like it would be more efficient.
So in this case your suggestion is to create a product for each rental property, and then each time it is booked pass that as the property value in price_data .
You could do that, or you could create a single Product called "Rent" and use that for all rent across the board.
Depends on what would work best for your specific situation.
And then it looks like price_data is still creating a price object behind the scenes, but at least there's less dev overhead this way (and maybe 1 less api call to wait for?).
Yep, and the Price created that way won't clutter the Dashboard.
It'll be very much behind the scenes and out of the way.
Okay cool. So it actually is much more behind the scenes. Yes, that sounds like what we'd want.
What would be the pros/cons of this? Easier, since you can more or less hard code that product ID, but I assume you'd loose some visibility?
What considrations would you make in choosing "Rent" vs "individual property" for the product?
Hi ๐
I'm stepping in as my colleague needs to go soon. Can you clarify the current state of your question?
I showed what I'm working on and an inefficiency in the workflow and Rubeus gave an option that improves the situation.
However, it still leaves the question of how to handle the product creation which apparently cannot be avoided.
So my final questions remain.
This one
Correct. You can supply product_data as a nested parameter within price data.
And this one.
What considrations would you make in choosing "Rent" vs "individual property" for the product?
That is entirely up to you. What makes more sense for your business model and financial reporting?
What would be the pros/cons of this?
What is "this" in the above sentence?
Choosing to use one product for everything or one product per rental property.
I'd like to know the tradeoffs so we can choose what makes more sense for us.
As I mentioned, single product is less dev overhead, but I assume we loose some visibility/reporting ability.
If there are any specifics about the visibility/reporting that would be good to know about, or if there are any other differences I would like to know about them.
Sorry but all of this is about how you want your business to run. Your prior questions were about interacting with the APIs which is where we can help but I cannot offer any advice on these questions
The quesiton is still about the API
Not really, no
It is "what are the differences that would result from choosing a single vs dynamic products."
You would have separate Product IDs for each price
And what affect would that have on visibility/reporting?
- The products would not show up in your product catalog on the dashboard
- I don't know if the reporting would include the randon product ID or not
Okay thank you! I think that is everything.
Happy to shed what ๐ก we can ๐