Hey Justin. I’m poking at this again. In practice, few customers have purchased multiple installs, so I decided to not worry about multiple purchases. But then I realized that testing whether purchasing a server installation is difficult if a user can do it only once. . .
So it appears that serialize_product is what determines if a product is subscribed, which determines whether you can purchase it.
I guess what needs to happen here is to have subscribed not get set to true of the product that they have purchased is a one-time product? It’s not immediately clear to me how to do that, as it looks like that information is at least a table-join away (or maybe another request away?).
What I’ve done for now is hacked the templates to just always show the payment link/button (something like {{#if product.subscribed_JP_disabled}}), and that’s allowing me to make multiple purchases, for what it’s worth.