Prepare a product for approval
Product approval status shows whether a product is ready for the sales flow you want to use. Approval readiness is not only a status label. It reflects whether the product details, delivery, pricing, checkout, and business setup are complete enough for real buyers.
Use this guide before launch, before affiliates send traffic, and before finance or support teams depend on the product being live.
Product statuses
| Status | Meaning | What teams should assume |
|---|---|---|
| Pending approval | The product is not yet launch-ready. | Do not send paid traffic or affiliate traffic yet. |
| Active | The product is enabled for the intended sales flow. | Checkout, delivery, and reporting paths should be tested. |
| Inactive | The product is paused. | New buyers should not be sent to old links without a replacement. See inactive products. |
What approval readiness includes
| Area | Why it matters for approval |
|---|---|
| Product details | Name, description, category, and sales page URL should match the real offer. |
| Product type | Course, ebook, software, service, and link-delivery products need different setup. See create product. |
| Delivery | Buyers must receive what checkout promises. Configure delivery or member access before launch. |
| Pricing | A product without a working plan and offer cannot complete a meaningful test sale. |
| Checkout | Checkout links and published checkout pages must reflect the live offer. |
| Business workspace | Incomplete business or finance setup can block selling or payouts later. |
| Team access | Launch collaborators should have the right roles and product access. |
Approval readiness workflow
- Confirm you are in the correct business workspace.
[Screenshot: App header — correct business workspace selected.]
- Create the product and choose the correct product type.
[Screenshot: Product type selector — correct type tile selected for the offer.]
- Complete product details, category, and sales page URL.
[Screenshot: Product details form — name, category, and sales page URL filled in.]
- Configure delivery:
- External members area or MemberKit
- Ebook delivery
- Link delivery
- Or the delivery model described in delivery options
[Screenshot: Delivery settings saved — method matches product type.]
- Create the first plan, offer, and checkout link.
[Screenshot: Plan, offer, and checkout link connected to the product.]
- Publish and test the checkout page.
[Screenshot: Checkout builder — published status with delivery promise visible.]
- Run one complete buyer test through first-sale workflow standards.
[Screenshot: Test purchase approved in Sales — buyer path complete.]
- Review product status and launch checklist items in before-launch checklists.
[Screenshot: Before-launch checklist — product, pricing, checkout, and delivery items checked.]
- Share the product with support, finance, and affiliates only after the test path works.
[Screenshot: Internal launch doc — official checkout link shared with teams.]
What to verify before treating a product as launch-ready
| Check | Why it matters |
|---|---|
| Checkout shows the correct offer and price | Wrong pricing creates refund and dispute risk. |
| Delivery works after an approved sale | Payment without access is one of the most common launch failures. |
| Business and finance setup are progressing | Bank account and withdrawal setup should not be deferred until after sales start. |
| Tracking is ready | UTMs, pixels, and webhooks should be tested before campaign traffic. |
| Inactive or pending products are excluded from campaigns | Old links can send buyers to the wrong state. |
Best practices
- Treat approval readiness as a launch gate, not a cosmetic status.
- Test the buyer path, not only the seller dashboard.
- Align checkout copy with actual delivery and pricing.
- Document which checkout link is the official launch link.
- Review coproducer or affiliate setup before partners promote the product.
Common mistakes
- Sending traffic while the product is still pending approval.
- Completing product details but skipping delivery testing.
- Creating pricing before the product type and delivery model are decided.
- Letting affiliates promote a product before checkout and access are verified.
- Assuming Dashboard activity alone proves the launch is healthy without checking Sales and buyer access.
FAQ
Can I send traffic before approval is complete?
What should I do if a product stays pending approval?
Review missing product details, delivery setup, pricing, business data, and any approval requirements shown in the product or business workspace. Use buyer access troubleshooting if payment works but access does not.
Does active status mean every old link still works?
Not always. If you changed pricing or paused the product, review inactive products and link impact and retest important links.
Where should I run the final launch test?
Follow complete your first-sale workflow and confirm the sale in Sales, then verify delivery and finance readiness.