#zen

1 messages · Page 1 of 1 (latest)

flat skiff
#

Hello @dense bear !

If each combination has a different price associated with it then you wouldn't have a choice but to add the variable price for every single combination in every product. But if there are combinations which cost the same e.g. product A in A5 in pink, and product A in A5 in blue - then you wouldn't need to create a separate product. You could create a Product for product A, and Price_1 for A5, Price_2 for A6, etc

You can't modify the price of a Price in the API. This is not something that is supported as there's no corresponding parameter on the API.

If you want to change the amount associated with a Price, you would create a new Price object and start using it instead. You could also make the old one inactive for example.

The lookup_key on Price lets you define a custom alias for your Price in your code. That way instead of hardcoding the price id price_123 in your code and having to update it to use price_abcd, you can transfer the old lookup key from the old price to the new one and have your code seamlessly start using the new one automatically. The idea is that you either cache the Price id associated with a lookup key based on webhooks for example or use the List Prices API and the lookup_keys parameter to quickly find the latest price id associated with a given lookup key.

dense bear
flat skiff
#

yeah, so if you have a different image that is charged differently, you should create another product for it