My intent: the main action is creating a control rule, but a wrong rule blocks legit discounts at checkout and kills orders. I didn’t want to push merchants into that on day one, so I used a video to explain instead. Does this pass? If not, what’s a merchant-safe way to guide to completion without forcing a live rule?
Label and disable premium features (4.3.7) — gated features must be non-interactive with no active plan.
What I have: no free plan. Merchants can open and explore every feature; plan requirement shows on Save.
My intent: let merchants see and evaluate the full feature set before paying.
Does this pass? If not, how do I let merchants evaluate before paying while staying compliant?
Your rule is currently in draft mode and does not affect checkout. Test it before enabling enforcement.
In Preview mode , changes made here are temporary and will not affect checkout.
Hi @Alan_G, could you help me with these two BFS updates? I’m a bit stuck on how to approach the onboarding change, and on keeping the app interactive without requiring a subscription.
Also — is @Senior_Dev’s suggestion the way to go, or do I really need to block all in-app interaction and force billing first before the user interact with the app?
Hey @webx47, I can offer some clarity on these points.
4.2.2: video-only doesn’t pass. Merchants need to be guided to their first meaningful outcome, not just shown how the app works. @Senior_Dev’s draft-mode suggestion is the right call, a rule in draft that doesn’t affect checkout until explicitly enabled counts as completion.
On 4.3.7, the explore-then-bill-on-Save doesn’t pass. The specific pattern this requirement is designed to prevent is merchants taking the time to set up a feature only to find out at Save that they need to pay. Making everything non-interactive is one solution, but there are a few other options that could work better for your use case. You could enforce a paid plan upon install before redirecting to the app, so merchants know upfront that it’s a paid app. Or you could add a free plan that allows saving as draft, then require a paid plan to publish. A third option is making a small portion of your features available for free to allow saving and previewing, with the rest requiring a paid plan.
I think I’ll move forward with “paid plan upon install.”
On onboarding — my app covers a lot of ground:
Controller route: 6+ unique components that each control something different, plus a custom rule builder that ranges from basic to fairly complex.
Discount route: users can create, view, and manage discounts made in the app, and the discount creation page itself has a lot going on.
Gift card routes: users can create gift cards with different types of constraints.
Margin analytics: users first initialize a report, which can take anywhere from 1 minute to 10 hour depending on store size (it fetches all the data, processes it in the DB, then surfaces the reports).
Given all of this, what would an ideal onboarding guide look like?
You mentioned in your first post that your main action is creating a control rule. Could you make that the “first meaningful outcome” but created as a draft?
The guide here also has some other onboarding suggestions that may work as well since your app covers a lot of ground:
Is the dashboard enough on its own, or should I also add a quick guide inside each route as well?
And I’ve kept a small optional video next to the checkout extension step (you can see it in the video)—does having that little video alongside the action CTA feel helpful, or is it just clutter?
