Seal Subscriptions bug - Variants change resets the Selling Plan

Retired Boards Appdev Subscriptions
,

Topic summary

Bug: On a subscription product with two Selling Plans (every 2 weeks or monthly) and variant options, changing the variant resets the selected Selling Plan back to the default (2 weeks). This risks poor UX and accidental orders on the wrong cadence. A screenshot of the selector UI is referenced.

Ideas/workarounds discussed:

  • Consider reversing the selection order so variants are chosen before the Selling Plan, though no implementation details were provided.
  • A technical approach can capture the selling_plan ID in JavaScript, but would require duplicating the pricing logic from price.liquid in JS and updating the displayed text, which is not ideal.

Recent update: A respondent apologized for the delay and asked for the question to be resubmitted with current details if the issue persists.

Status: No confirmed fix in the thread. The key open question is how to persist the selected Selling Plan across variant changes without duplicating theme pricing logic in JavaScript.

Summarized with AI on December 11. AI used: gpt-5.
1

I have sent this query to Seal Subscriptions but thought I’d try my luck here.

I have set up my subscription rule with two Selling Plans ( send every ‘2 weeks’ or send ‘monthly’) for a product that has two variant options which the customer selects from a drop down, as per the image below.

The customer is likely to first select their selling plan, and then select their variants - BUT there is a bug in that when the variants are changed the selling plan goes back to the default option of ‘2 weeks’.

This is a) not good for UX and b) a customer could miss the change and end up with the wrong order.

Does anyone have a fix or any ideas? TIA

One better but not perfect idea would be to switch around the selections so the customer is choosing their variants first, but I don’t know how to do this.

Screen Shot 2021-04-13 at 4.14.30 pm.png
Screen Shot 2021-04-13 at 4.14.30 pm.png400×368 13.8 KB

2 Likes
2

Hey SGMM,

I want to apologize for not getting back to you about this in a timely manner.

If this problem is still relevant to you, can I ask that you submit this question again? (with information about your current situation)

Sincerely,
J-ROM

3

Same here. I can capture the selling_plan ID in JS, but then I would need to duplicate the logic from price.liquidin JS and replace the calculated text value.

Can someone look at this again?