Set up a course product
Course products deliver lessons or learning content, usually through a members area. Buyers expect access to classes after payment is approved.
Use this guide when you are launching a course, training program, or recorded class library. For MemberKit-specific callback steps, continue with connect MemberKit for delivery after the delivery step below.
When a course product fits
| Use a course product when | Use another product type when |
|---|---|
| The buyer receives lessons or a members area | Delivery is only a PDF file. See ebook delivery. |
| Content is structured as classes or modules | Access is mainly one or more URLs. See link delivery. |
| You use MemberKit, AtomicMembers, or another members platform | The offer is 1:1 guidance. See mentorship product setup. |
Full setup workflow
- Confirm you are in the correct business workspace.
[Screenshot: App header showing the active business name and workspace switcher.]
- Open Products in the sidebar.
[Screenshot: Products sidebar item selected — product list visible.]
- Click New product or the equivalent create action.
[Screenshot: Products list page with New product button visible.]
- On What will you sell?, select Course.
[Screenshot: Product type selector — Course tile selected; subtitle reads "Lessons in a members area."]
- Complete product details: name, description, category, and sales page URL.
[Screenshot: Course product details form — name, description, category dropdown, and sales page URL fields.]
- Open delivery or members area settings for the product.
[Screenshot: Product delivery tab — members area settings entry point.]
- Choose External members area or AtomicMembers when available.
[Screenshot: Delivery settings — External members area vs AtomicMembers options for a course product.]
- If using an external platform, select the platform (for example MemberKit) and add the callback URL.
[Screenshot: External members area setup — platform dropdown and callback URL field filled in.]
- Save the product and confirm delivery settings persisted.
[Screenshot: Product saved confirmation — delivery settings stored.]
- Complete product approval details if the product is not yet approved.
[Screenshot: Product approval section with required fields and submission status.]
- Create the plan and offer for the course.
[Screenshot: New plan form connected to the course product — price, billing type, and offer name.]
- Create a checkout link for the offer.
[Screenshot: Checkout links list with a course product link and copy button.]
- Open the checkout builder, review copy about course access, and publish.
[Screenshot: Checkout builder preview showing course delivery promise and published status.]
- Run a test purchase through the real buyer path.
[Screenshot: Test checkout — course purchase payment submitted.]
- Confirm the sale is approved in Sales.
[Screenshot: Sales detail for a test course purchase with approved status.]
- Confirm the buyer received access in the members area (MemberKit, AtomicMembers, or external platform).
[Screenshot: MemberKit or members area showing the test buyer with course access granted.]
[Screenshot: Dashboard or Finance — first course sale reflected in reports.]
Delivery options for courses
| Option | Use it when |
|---|---|
| External members area | Course content lives in MemberKit or another platform |
| MemberKit | You already use MemberKit for lessons |
| AtomicMembers | You deliver inside AtomicPay's integrated members area when available |
| Link delivery | Rare for courses; only when access is URL-based without a members area |
What to verify before launch
| Check | Why it matters |
|---|---|
| Product type is Course | Wrong type breaks delivery expectations |
| Callback URL matches the right course | Buyers land in the wrong members area otherwise |
| Checkout copy mentions how access is delivered | Reduces support tickets after payment |
| Test used an approved sale | Pending PIX should not be treated as delivery success |
| Webhooks fire on the correct event if automations depend on them | External systems may provision too early or not at all |
Best practices
- Configure members area delivery before sending launch traffic.
- Test with the same payment method buyers will use.
- Document which members course maps to which AtomicPay product.
- Pair course setup with team product access when collaborators manage only some products.
Common mistakes
- Selecting Course but configuring ebook or link delivery instead.
- Publishing checkout before callback delivery is tested.
- Granting access when payment is still incomplete. See incomplete payments.
- Using a staging callback URL in a live product.
FAQ
Should I use MemberKit or AtomicMembers?
Use MemberKit or another external platform when your lessons already live there. Use AtomicMembers when you deliver inside AtomicPay and that option is available for your account.
Can a course be sold as a subscription?
Yes. Define renewal and access rules before launch. See one-time vs subscription pricing and subscription billing.
What if the buyer paid but has no course access?
Start with troubleshoot buyer access after purchase, then verify callback URL, sale approval, and members area mapping.