¿Puedo vibecodear WooCommerce Subscriptions?

PARCIAL · un fin de semana

precio $23.25/mesahorrarías $279/añotiempo de build un fin de semanacategoría 🛒 comercioreemplazada por 0 personas

The actual hard part of recurring billing lives at the payment processor, not in this plugin: Stripe Billing already does tokenization, renewal attempts, SCA, proration and dunning. So an agent can absolutely wire a small self-hosted checkout plus webhook listener plus entitlement table in a weekend, and for one product with two or three plans that is genuinely enough. What you cannot one-shot is the part that makes this extension worth a license: living inside WooCommerce so that orders, coupons, taxes, shipping, emails, reports and forty other plugins all understand a subscription. If you already run a real Woo store, replacing this means rebuilding the glue, not the billing. If you just want money to arrive monthly for something you built, you never needed WordPress in the first place.

el prompt

Build a minimal self-hosted recurring billing service for a single product. No WordPress, no WooCommerce.

Stack, non negotiable: Node 20, TypeScript, Express, SQLite via better-sqlite3, Stripe Node SDK, plain server-rendered EJS templates. No React, no ORM, no Docker.

Scope, in:
- A plans.ts file defining three hardcoded plans (monthly, annual, lifetime) each with a Stripe Price ID pulled from env.
- GET /pricing renders the plans and a Subscribe button per plan.
- POST /checkout/:plan creates a Stripe Checkout Session in subscription mode (or payment mode for lifetime) and redirects to it.
- POST /webhook with raw body parsing and signature verification. Handle checkout.session.completed, customer.subscription.updated, customer.subscription.deleted, invoice.payment_failed. Upsert into a subscriptions table: stripe_customer_id, email, plan, status, current_period_end, cancel_at_period_end.
- GET /portal creates a Stripe Billing Portal session for the logged in customer so plan changes, cancellation and card updates are Stripe's problem, not yours.
- Magic link auth only: POST /login emails a signed token, no passwords. Log the link to stdout in dev instead of sending mail.
- GET /api/entitlement returns JSON with active true or false plus plan and period end, so another app can gate features on it.
- GET /admin, protected by a single ADMIN_TOKEN from env, listing subscribers with status and next renewal, filterable by status.
- Idempotent webhook handling: store processed event IDs and ignore repeats.

Scope, out: multi gateway support, tax calculation beyond Stripe Tax, proration math of your own, coupons, shipping, invoices you render yourself, any telemetry.

Secrets in .env: STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, STRIPE_PRICE_MONTHLY, STRIPE_PRICE_ANNUAL, STRIPE_PRICE_LIFETIME, ADMIN_TOKEN, APP_URL. Commit a .env.example, never a filled .env.

Deliver a README with exact steps: create products in the Stripe dashboard, run stripe listen to forward webhooks locally, seed a test subscription, and how to flip to live keys. Include a script that replays a saved webhook fixture so the handler is testable without Stripe.

$ ábrelo en tu agente (prompt listo, tú das enter) o cópialo crudo

Se puede en parte

Ahorro de referencia: US$279/año si dejas de pagar WooCommerce Subscriptions.

Quiero que lo armen →

por qué la gente sigue pagando

Because their store is already WooCommerce, and in that world this extension is the thing every other plugin, theme and gateway expects to be present. Paying once a year to have renewals, dunning emails, subscriber lists and coupon rules behave like normal Woo orders is cheaper than maintaining a parallel billing system that has to be kept in sync with the store forever. People building something new from scratch have a much easier time: point Stripe or Paddle at it and skip all of this.

qué pierdes

xIntegration with the WooCommerce order, coupon, tax and shipping machinery, so subscriptions are no longer just orders your other plugins understand

xGateway breadth: you are married to one processor instead of the dozen Woo supports

xCustomer-facing plan switching, pausing, resubscribing and prorated upgrades in your own UI, unless you accept the hosted portal as-is

xAdmin reporting, renewal calendars and bulk actions over thousands of subscribers

xYears of edge case handling for partial renewals, mixed carts, manual renewals and payment method migrations

arte previo · úsalo en vez de construir, si prefieres

Nada que valga la pena señalar. Por eso existe el prompt.

compartir en X ↗"Acabo de reemplazar WooCommerce Subscriptions ($23.25/mes) con un prompt"