Vibecode Shopify
track this build5 steps, step by step0%NOT REALLY · don't bother
price $25/moyou'd save $300/yrbuild time not realistically solocategory 🛒 commercereplaced by 0 people
You can build a small store, but Shopify's product is hosted checkout, payments, tax/shipping integrations, app marketplace, fraud/risk tooling, and merchant operations.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Shopify. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Shopify indie build ## Goal Build the smallest trustworthy replacement for the core Shopify workflow for one developer or a tiny team. ## Scope For a tiny shop, build catalog/cart/checkout via Stripe, order emails, and simple admin; do not expect Shopify parity. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - trusted checkout - payment risk - app marketplace - themes - shipping/tax integrations - POS - support - scale If those capabilities are essential, use Medusa instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build me a small self-hosted shop for a handful of products, the honest small slice of Shopify. Requirements: - Node + Express + better-sqlite3 on a VPS; products in products.json (slug, name, price, images, stock count), server-rendered catalog and product pages. - Cart in a session cookie; checkout hands off entirely to Stripe Checkout (keys in .env). Never touch card data. - Stripe webhook records the order, decrements stock, and emails me and the buyer via Resend (key in .env). - An /admin page behind basic auth: order list and a mark-shipped button that emails the buyer with an optional tracking number. - Flat shipping rates per region in a config file; sold-out products stay visible but cannot be bought. - No customer accounts, no telemetry; orders stay in my SQLite file. - Out of scope: discount engines, multi-currency, POS, and tax automation. Use Stripe Tax for tax; do not write tax logic. - README: Stripe webhook setup, a plain warning that I am now the fraud department, and a note that this is not Shopify, whose trusted checkout, payment risk handling, and app ecosystem cannot be rebuilt; if volume grows, move to Shopify or Medusa rather than growing this. ## Required capabilities - payment processor - tax/shipping logic - database - hosting - emails - inventory/order admin ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of Shopify. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Shopify indie build ## Goal Build the smallest trustworthy replacement for the core Shopify workflow for one developer or a tiny team. ## Scope For a tiny shop, build catalog/cart/checkout via Stripe, order emails, and simple admin; do not expect Shopify parity. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - trusted checkout - payment risk - app marketplace - themes - shipping/tax integrations - POS - support - scale If those capabilities are essential, use Medusa instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build me a small self-hosted shop for a handful of products, the honest small slice of Shopify. Requirements: - Node + Express + better-sqlite3 on a VPS; products in products.json (slug, name, price, images, stock count), server-rendered catalog and product pages. - Cart in a session cookie; checkout hands off entirely to Stripe Checkout (keys in .env). Never touch card data. - Stripe webhook records the order, decrements stock, and emails me and the buyer via Resend (key in .env). - An /admin page behind basic auth: order list and a mark-shipped button that emails the buyer with an optional tracking number. - Flat shipping rates per region in a config file; sold-out products stay visible but cannot be bought. - No customer accounts, no telemetry; orders stay in my SQLite file. - Out of scope: discount engines, multi-currency, POS, and tax automation. Use Stripe Tax for tax; do not write tax logic. - README: Stripe webhook setup, a plain warning that I am now the fraud department, and a note that this is not Shopify, whose trusted checkout, payment risk handling, and app ecosystem cannot be rebuilt; if volume grows, move to Shopify or Medusa rather than growing this. ## Required capabilities - payment processor - tax/shipping logic - database - hosting - emails - inventory/order admin ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of Shopify. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # Shopify product brief ## Problem You can build a small store, but Shopify's product is hosted checkout, payments, tax/shipping integrations, app marketplace, fraud/risk tooling, and merchant operations. ## Product outcome For a tiny shop, build catalog/cart/checkout via Stripe, order emails, and simple admin; do not expect Shopify parity. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - payment processor - tax/shipping logic - database - hosting - emails - inventory/order admin ## Explicit non-goals for v1 - trusted checkout - payment risk - app marketplace - themes - shipping/tax integrations - POS - support - scale ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting brief Build me a small self-hosted shop for a handful of products, the honest small slice of Shopify. Requirements: - Node + Express + better-sqlite3 on a VPS; products in products.json (slug, name, price, images, stock count), server-rendered catalog and product pages. - Cart in a session cookie; checkout hands off entirely to Stripe Checkout (keys in .env). Never touch card data. - Stripe webhook records the order, decrements stock, and emails me and the buyer via Resend (key in .env). - An /admin page behind basic auth: order list and a mark-shipped button that emails the buyer with an optional tracking number. - Flat shipping rates per region in a config file; sold-out products stay visible but cannot be bought. - No customer accounts, no telemetry; orders stay in my SQLite file. - Out of scope: discount engines, multi-currency, POS, and tax automation. Use Stripe Tax for tax; do not write tax logic. - README: Stripe webhook setup, a plain warning that I am now the fraud department, and a note that this is not Shopify, whose trusted checkout, payment risk handling, and app ecosystem cannot be rebuilt; if volume grows, move to Shopify or Medusa rather than growing this. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Shopify capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Shopify indie build ## Goal Build the smallest trustworthy replacement for the core Shopify workflow for one developer or a tiny team. ## Scope For a tiny shop, build catalog/cart/checkout via Stripe, order emails, and simple admin; do not expect Shopify parity. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - trusted checkout - payment risk - app marketplace - themes - shipping/tax integrations - POS - support - scale If those capabilities are essential, use Medusa instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build brief Build me a small self-hosted shop for a handful of products, the honest small slice of Shopify. Requirements: - Node + Express + better-sqlite3 on a VPS; products in products.json (slug, name, price, images, stock count), server-rendered catalog and product pages. - Cart in a session cookie; checkout hands off entirely to Stripe Checkout (keys in .env). Never touch card data. - Stripe webhook records the order, decrements stock, and emails me and the buyer via Resend (key in .env). - An /admin page behind basic auth: order list and a mark-shipped button that emails the buyer with an optional tracking number. - Flat shipping rates per region in a config file; sold-out products stay visible but cannot be bought. - No customer accounts, no telemetry; orders stay in my SQLite file. - Out of scope: discount engines, multi-currency, POS, and tax automation. Use Stripe Tax for tax; do not write tax logic. - README: Stripe webhook setup, a plain warning that I am now the fraud department, and a note that this is not Shopify, whose trusted checkout, payment risk handling, and app ecosystem cannot be rebuilt; if volume grows, move to Shopify or Medusa rather than growing this. ## Required capabilities - payment processor - tax/shipping logic - database - hosting - emails - inventory/order admin ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# Shopify product brief ## Problem You can build a small store, but Shopify's product is hosted checkout, payments, tax/shipping integrations, app marketplace, fraud/risk tooling, and merchant operations. ## Product outcome For a tiny shop, build catalog/cart/checkout via Stripe, order emails, and simple admin; do not expect Shopify parity. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - payment processor - tax/shipping logic - database - hosting - emails - inventory/order admin ## Explicit non-goals for v1 - trusted checkout - payment risk - app marketplace - themes - shipping/tax integrations - POS - support - scale ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting brief Build me a small self-hosted shop for a handful of products, the honest small slice of Shopify. Requirements: - Node + Express + better-sqlite3 on a VPS; products in products.json (slug, name, price, images, stock count), server-rendered catalog and product pages. - Cart in a session cookie; checkout hands off entirely to Stripe Checkout (keys in .env). Never touch card data. - Stripe webhook records the order, decrements stock, and emails me and the buyer via Resend (key in .env). - An /admin page behind basic auth: order list and a mark-shipped button that emails the buyer with an optional tracking number. - Flat shipping rates per region in a config file; sold-out products stay visible but cannot be bought. - No customer accounts, no telemetry; orders stay in my SQLite file. - Out of scope: discount engines, multi-currency, POS, and tax automation. Use Stripe Tax for tax; do not write tax logic. - README: Stripe webhook setup, a plain warning that I am now the fraud department, and a note that this is not Shopify, whose trusted checkout, payment risk handling, and app ecosystem cannot be rebuilt; if volume grows, move to Shopify or Medusa rather than growing this. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Shopify capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent · this prompt is generated from the build plan · improve it via PR
They pay because ecommerce failures cost real revenue and trust.
xtrusted checkout
xpayment risk
xapp marketplace
xthemes
xshipping/tax integrations
xPOS
xsupport
xscale
share on X ↗"I just replaced Shopify ($25/mo) with one prompt"
Don't feel like building it? These folks already made it free.
BagistoA proper Laravel storefront and admin; the free bit ends where hosting and Laravel operations begin.open source↗
Magento Open SourceA vast store engine for anyone who thought running WooCommerce did not involve enough infrastructure.open source↗
OpenCartOld-school PHP commerce that still does the whole job instead of selling you ten add-ons first.open source↗all 5 free alternatives to Shopify →· no votes, no pay-to-list · just what's real
Shopify pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| starter | $5/workspace | — | Simple online store and product links; 0 staff accounts; 5% transaction fee with Shopify Payments. |
| basic | $25/workspace | $19/workspace | Unlimited products; 10 inventory locations; 0 additional staff accounts; 2% fee when using a third-party payment provider. |
| grow | $65/workspace | $49/workspace | Unlimited products; 10 inventory locations; up to 5 staff accounts; 1% third-party-provider fee. |
| advanced | $399/workspace | $299/workspace | Unlimited products; 10 inventory locations; up to 15 staff accounts; 0.6% third-party-provider fee. |
| plus | $2300/workspace | — | Starts at $2,300/month; unlimited staff; up to 200 inventory locations, 9 expansion stores and 20 POS Pro locations; 0.2% third-party-provider fee. |
free tierno free tier; 3-day trial, then a promotional $1/month for 3 months before standard pricing
billingStarter is monthly only; Basic/Grow/Advanced offer monthly + annual; Plus uses 1- or 3-year contracts
hidden costsStarter charges a 5% transaction fee with Shopify Payments; POS Pro is $89/month per location on non-Plus plans; synced marketplace orders above 50/month cost 1% up to $99/month; third-party gateway fees (2%/1%/0.6%/0.2%) are on top of the provider's processing fees; apps, themes and domains can add recurring costs.
verified 2026-08-14 · source ↗
Vibecode Shopify
Not really. Shopify's value is not the code: . See the honest breakdown above.
How much does Shopify cost?
Shopify costs about $25/month (Basic, checked 2026-08-14), which is $300 per year.
What do I lose by replacing Shopify?
Honestly: trusted checkout; payment risk; app marketplace; themes; shipping/tax integrations; POS; support; scale. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Shopify?
Yes: Bagisto (A proper Laravel storefront and admin; the free bit ends where hosting and Laravel operations begin.) Magento Open Source (A vast store engine for anyone who thought running WooCommerce did not involve enough infrastructure.) OpenCart (Old-school PHP commerce that still does the whole job instead of selling you ten add-ons first.) All 5 curated free alternatives are at vibecodeit.com/shopify/alternatives. The prompt is for when you want it exactly your way.