Loading tutorials…
Loading tutorials…
Kit Commerce lets you sell digital products (PDFs, courses, paid newsletter tiers) without a separate Stripe checkout or Gumroad. Done right, it's the fastest path to monetizing a Kit list. Done wrong, you'll fight Stripe disputes and broken subscriber gating for months.
Who this is forKit creators with 1,000+ engaged subscribers ready to monetize via digital products or a paid newsletter tier. If you're under 500 subscribers, focus on list growth first — commerce works once you have an audience.
What you'll need
Step 1
Kit → Earn → Commerce → Connect Stripe. Authorize. Kit uses Stripe Connect — you keep full control of your Stripe account.
Kit → Earn → Commerce → Get Started.
Click "Connect Stripe." Kit opens a Stripe Connect OAuth flow — log in or create a Stripe account.
Authorize Kit to create charges on your behalf. Kit Commerce uses Stripe Connect, so funds go directly to your Stripe balance (with Kit's platform fee taken via Stripe).
Kit's platform fee: 3.5% + standard Stripe processing (2.9% + $0.30 in the US). Total: ~6.4% + $0.30 per transaction. Lower than Gumroad (10%) but higher than direct Stripe (2.9%).
After connection, verify in Kit → Earn → Commerce → Settings → Stripe status = "Connected" with the right account ID.
Step 2
Kit → Earn → Products → + New Product. One-time, subscription, or pay-what-you-want. Pick the right model for the offer.
Kit → Earn → Products → + New Product.
Choose product type: One-time (lifetime access), Subscription (recurring monthly/yearly), or Pay-what-you-want (PWYW).
For digital downloads (PDFs, templates): One-time. For paid newsletters: Subscription. PWYW only works for established creators with strong audience trust — most should avoid.
Set price: in USD, the most-tested price points are $9, $19, $29, $49, $97, $197. Default to one of these — round numbers convert better than $24 or $33.
Product page content: name, tagline, hero image (square, 1200x1200+), bullet list of what's included, full description (300-500 words), 2-3 testimonials if available.
For paid newsletter tier: include "What you get" and "How often" — clarity beats vagueness.
Step 3
For digital products: upload the file. For paid newsletter tier: configure tag-based content gating.
For one-time digital products: Product → Settings → Files → upload the deliverable (PDF, ZIP, MP4). Max 5GB per file.
For paid newsletters: Product → Settings → Subscribed Tag → auto-apply a tag like `subscribed:paid-newsletter` to buyers. This tag gates which broadcasts they receive.
In your broadcast workflow: when sending paid-only content, select 'has tag subscribed:paid-newsletter' as the recipient segment. This ensures only paying subscribers receive paid content.
For course access (more complex): integrate with Thinkific/Teachable/Podia via webhook. Kit Commerce handles payment; the course platform handles access.
Test delivery: buy your own product with a test card (Stripe test mode). Verify file download / tag application / access works end-to-end.
Step 4
Kit auto-generates a checkout page. Customize headline, copy, testimonials, and FAQ. This is your sales asset.
On the product → Public page tab → Edit.
Headline: lead with the outcome, not the format. "Build a 10K newsletter in 90 days" beats "The 50-page newsletter growth guide."
Hero: 3D mockup of the product (use Placeit, Smartmockups, or hire a designer for ~$50). Photo mockups outconvert plain text by 30-50%.
Bullet list: 5-7 specific deliverables. "12 templates" beats "lots of templates." Numbers convert.
FAQ: anticipate the 3-5 most common objections. Pricing, refunds, time commitment, fit, format.
Money-back guarantee: offer 7-30 day refund. Removes purchase risk. Refund rates run 2-5% on digital products — far cheaper than the lift in conversion.
Publish. Open the checkout URL in incognito on desktop + mobile. Verify it renders cleanly and the buy button works.
Step 5
When someone buys, they should: receive the product, get a thank-you email, get tagged correctly, exit any "buy" sequences.
Kit → Automate → Visual Automations → + New.
Trigger: "Purchases a Product" → choose your product.
Step 1: Add tag `lifecycle:customer` + tag `purchased:product-name`. (For paid newsletter: also apply `subscribed:paid-newsletter`.)
Step 2: Remove from any active launch sequences ("Remove from sequence: Launch Sequence v1").
Step 3: Send thank-you email (immediate). Subject: "Welcome — here's [product]." Body: download link OR access instructions, plus a personal note.
Step 4: 2-day delay → check-in email. "How's it going? Reply if you hit any issues."
Step 5: 7-day delay → ask for testimonial. "What's working for you so far?" Testimonials gathered this early are the strongest social proof for future launches.
Step 6
A real launch sends 5-7 emails over 7-14 days. Tease → reveal → social proof → close. Skip this and you launch quiet.
Build a launch sequence (separate from the welcome sequence): Tease (2-3 days pre-launch), Reveal (launch day), Social Proof + FAQ (Day 3-5), Last Chance (Day 6-7).
Total: 5-7 emails over 7-14 days. Compress to 5-7 days for time-limited launches; extend to 14 days for evergreen products.
Use a 'launch' tag (`behavior:launch-interest`) applied via a click action in a pre-launch broadcast. Subscribers who click get into the launch sequence; others stay on the main list.
After launch: keep the product page live and the checkout open for evergreen sales. The launch sequence ends; the product persists.
Budget time: a real launch is 20-40 hours of work (copy, design, sequence build, customer support). Don't underestimate.
Step 7
Test purchase, file delivery, tag application, and refund flow before announcing. Set up refund automation.
Use Stripe test mode: Kit → Earn → Commerce → Settings → enable test mode. Test card: 4242 4242 4242 4242.
Buy your own product. Verify: payment processes, file delivers (or tag applies for paid newsletter), thank-you email arrives, customer tag is set.
Test refund: in Stripe Dashboard → refund the test charge. Verify Kit auto-removes the customer tag (Kit listens to Stripe webhooks).
Once tested, disable Stripe test mode and you're ready for live transactions.
Refund policy: post it on the product page. Default is 14-day refund, no questions asked. Generous refund policies LIFT conversion more than they cost in refunds.
Monitor Stripe disputes weekly. One unhandled dispute can freeze your Stripe payouts for weeks.
Common mistakes
Underpricing the first product
What goes wrong: Pricing at $9 or $19 leaves real money on the table. Most digital products convert at similar rates from $19 to $49. Pricing at $19 instead of $49 = 60% revenue loss with no compensating volume gain.
How to avoid: Default to $29-49 for digital products and $5-15/month for paid newsletter tiers. Test higher before lower. If conversion drops at higher prices, fall back — but don't default to cheap.
No post-purchase automation
What goes wrong: Buyers don't get tagged. They keep receiving the launch sequence with the same offer. Looks unprofessional. 5-15% of buyers complain or request refund.
How to avoid: Build the post-purchase automation (tutorial step 5). Set it up BEFORE the first launch. Non-negotiable.
No refund policy on the product page
What goes wrong: Buyers hesitate at checkout. Conversion drops 15-30%. Even those who buy file Stripe disputes when they're unhappy because they don't know how to request a refund.
How to avoid: Post a clear refund policy: "14-day refund, no questions asked. Email hello@yourname.com." Conversion lift outweighs refund cost by 5-10x.
Skipping the launch sequence (quiet launch)
What goes wrong: Posting the product link in one broadcast and one tweet captures 10-20% of available launch revenue. A proper 5-7 email sequence captures 50-80%.
How to avoid: Build the launch sequence (tutorial step 6). Send 5-7 emails over 7-14 days. Most creators are uncomfortable promoting this much — push through it. The revenue justifies it.
Not testing the buy flow before announcing
What goes wrong: Launch day arrives. Buyers click checkout. Stripe key is in test mode, or the file delivery is broken, or the customer tag isn't applied. 100-500 frustrated buyers and a launch ruined.
How to avoid: Always run an end-to-end test (Stripe test mode → real purchase → file delivery → tag application → refund) BEFORE announcing. 30 minutes of testing prevents launch-day catastrophe.
Sending paid-newsletter content to everyone
What goes wrong: Paying subscribers see free subscribers getting the same content. They feel cheated. Churn rate spikes from 5%/mo to 15-20%/mo.
How to avoid: Always send paid-only broadcasts to the paid-tier segment (`has tag subscribed:paid-newsletter`). Use Kit's recipient filtering — never assume the right segment by default.
Recap
Done — what's next
How to build a ConvertKit/Kit sequence that converts subscribers
Read the next tutorial
Hand it off
A first product launch is 20-40 hours of work and the difference between $0 and $10K-50K of revenue. A specialist who's launched 20+ Kit products will handle pricing, copy, sequence, and testing — typically $800-2,000 of one-time work at $14-16/hr. Most creators recover that on launch day.
See specialist rates
Kit takes 3.5% of each transaction. Stripe takes their standard processing fee (2.9% + $0.30 in the US). Total: ~6.4% + $0.30 per transaction. Lower than Gumroad (10% on basic plans) but higher than running Stripe directly (2.9%).
No — Kit Commerce is digital-only. For physical products, use Shopify (with a Kit integration for email) or a service like Beehiiv's native commerce. Kit is built around digital deliverables, paid newsletters, and course access.
Buyers are tagged automatically (e.g., `subscribed:paid-newsletter`). You gate broadcasts by sending only to that segment. Stripe handles recurring billing; Kit listens for webhook events to update tags on cancellation/refund. Same pattern as Substack paid tiers but using your existing Kit list.
Default $29-49 for most. Mini-products ($9-19) sell volume but don't compound. Premium ($97-297) needs strong social proof. Test at multiple price points — most creators underprice by 30-60% out of fear. Higher prices often convert similarly with much better revenue.
Yes — but plan for it. Export existing customer list from Gumroad. Import to Kit with their `customer` tag. Switch product URLs gradually (keep Gumroad live for 30 days while transitioning). Lifetime-access customers can stay where they bought; new customers go through Kit.
You can't fully — paid newsletter delivery is by email, not by login. Subscribers could forward emails. Most creators accept ~10% leakage as the cost of doing business. If sharing becomes systemic, use Kit's `Resubscribe link` per email + per-subscriber unique unsubscribe tokens to identify forwarders.
ConvertKit
Sequences are Kit's automated email series — the equivalent of Klaviyo flows or Mailchimp automations. A well-built welcome sequence captures 60-80% of available new-subscriber revenue. Most DIY sequences capture 15-25%. The difference is cadence, triggers, and exits.
ConvertKit
Sequences are linear; automations are branching. The Visual Automations builder is where Kit becomes genuinely powerful — but also where most DIY accounts build complex flows that break silently and lose subscribers in dead-ends.
ConvertKit
Kit doesn't have lists — everyone is one subscriber pool. Tags + segments do the work. A well-designed taxonomy lifts broadcast revenue 30-50%. A messy taxonomy is the #1 reason creators feel stuck on Kit.
ConvertKit
DIY Kit is a great call — until it isn't. A 5,000-subscriber list with no welcome sequence, no segmentation, and no monetization is leaving real money on the table every month. Here's the honest framework for when to hire.