A second course creates a new question: can each buyer open exactly what they paid for? Write that promise first, then check it from the learner’s side.
Practical worksheet · One-time purchases · Official sources checked September 8, 2026 · No affiliate links
Decide what buying B includes
Call your existing course A and the new course B. Is B a separate purchase, an upgrade, or a bundle that includes A? Tell the buyer which it is. This worksheet starts with two separate purchases: buying one does not include the other.
Before changing anything
Record the current A offer, course resource, access type and release conditions. Keep that reference so you can check that A still behaves as promised.
Four people. Four access checks.
Use these as expected results for separate, immediately available courses. A locked future lesson is different from a lesson the learner never bought.
01 / Bought A only
A should open.
B should stay restricted.
02 / Bought B only
B should open.
A should stay restricted.
03 / Bought both
A and B should open.
Neither purchase should remove the other.
04 / Bought neither
Paid lessons should stay restricted.
Public previews may remain visible.
Selling a bundle? Change the expected results before testing. If buying B includes A, the B buyer should open both. The cards are a starting scenario, not a rule for every offer.
Connect each offer to its intended course
In systeme.io, an order form’s digital product can include a course resource and its access type. Check the actual resource selected for B; a new page title alone does not establish a different access promise. See the official course-selling instructions.
For this simple scenario, start with clearly named separate course resources. A single course with selected-module offers is another documented option, but needs different checks. Full, partial and drip access behave differently; choose the type that matches your offer.
Try it without confusing access with payment
Use separate test email addresses you control for the four cases. Keep them out of unrelated campaigns. For each test learner, open a clean browser session and sign in only as that learner. Try a lesson in A and a lesson in B—including a direct lesson link, not only the dashboard.
How to create an access-only test
With permission, use controlled manual test enrollments. systeme.io documents Assets → Courses → select course → Add student. Match the selected access type to the test case. Saving sends an access email, so use only your own test recipients. Follow the official manual-enrollment steps.
Use one identity for A, one for B, one for both, and a permitted learner identity with neither enrollment. If you cannot create the last case without granting access, leave that case untested. A signed-out check is useful but does not replace a signed-in learner with no enrollment.
Manual enrollment tests access only. It does not show that buying B creates the correct enrollment automatically. Keep payment → enrollment marked untested until you observe that complete route in a supported test environment or an explicitly funded live test.
Save one result per learner
Copy the short test record
Offer version / date / tool and plan:
Private test-identity reference:
Enrollment route: manual / supported payment test / live purchase
Expected A / B access and release timing:
Actual A / B lesson result, including direct links:
Device / signed-in account / evidence reference:
Result: matched / mismatch / untested
Next fix / owner / recheck date:
Keep addresses, orders and private lesson/access links out of anything you publish. This is copyable text; this page does not store entries.
A mismatch is a reason to pause
If the wrong lesson opens, stop sending buyers to the affected offer while you investigate the resource and enrollment settings. Do not bulk-remove existing buyers. If a promised lesson fails to open, use the recovery guide below.
Already have a blocked buyer? Use the course access recovery guide. If the four access checks match, keep the record and verify any remaining purchase-triggered step with the delivery checklist.
What this worksheet establishes
The four-case structure is an editorial test plan for two separate short courses, not completed product testing. We have not created these enrollments, made a purchase, or observed A/B lesson access for this article. Timing, expiry, bundles and upgrades require expectations specific to the offer; this worksheet does not certify launch readiness.
The linked official instructions were checked September 8, 2026. Their configuration descriptions do not prove your own settings work. The illustration is original and conceptual, not a software screenshot.
Torimonn SaaS Notes 