Vibecode Metorik
track this build5 steps, step by step0%KINDA · weekend project
The good news: every number Metorik shows you is already sitting in your own WooCommerce database, so nobody is gatekeeping your data. An agent can pull orders, customers and products through the Woo REST API into a local store and give you revenue charts, cohort and repeat-purchase views, product breakdowns and CSV exports in a weekend. The gap is everything that is not a chart: abandoned cart tracking needs a script on your storefront plus a capture endpoint, email automations need a sending domain and deliverability you do not have, and segment-driven campaigns need a rules engine that is a project of its own. Large stores also punish naive syncs, Metorik has spent years making that part boring. Build the dashboard, keep paying for the email side if that is why you signed up.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Metorik. 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 ===== # Metorik indie build ## Goal Build the smallest trustworthy replacement for the core Metorik workflow for one developer or a tiny team. ## Scope Syncs your WooCommerce orders, customers and products into a local database on a schedule and serves a dashboard with revenue, product, cohort and repeat-purchase reports plus CSV export. ## 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: - Abandoned cart tracking and cart recovery emails, which need storefront instrumentation plus real email sending - Automated email flows tied to customer segments, with templates, throttling and unsubscribe handling - Battle-tested incremental sync for stores with hundreds of thousands of orders - Subscriptions, refunds and tax edge case handling that Metorik has already hit and fixed - Mobile-friendly polish, live order feed and the everything-in-one-place feel If those capabilities are essential, use Metorik 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 a self-hosted WooCommerce analytics dashboard. Single repo, no accounts, no cloud services, no telemetry. Stack, no substitutions: - TypeScript, Node 20, Fastify for the API - SQLite via better-sqlite3 as the local warehouse - React with Vite for the dashboard, Recharts for charts, plain CSS - Zero auth: it binds to 127.0.0.1 and is meant to run behind your own network Config in .env only: WOO_BASE_URL, WOO_CONSUMER_KEY, WOO_CONSUMER_SECRET, SYNC_INTERVAL_MINUTES, PORT. Ship .env.example, never commit real keys. Sync worker: - Pull /wp-json/wc/v3 orders, customers, products with pagination and per_page=100 - Incremental by modified_after, persisted watermark per resource in a sync_state table - Retry with exponential backoff on 429 and 5xx, log progress to stdout - Store raw JSON plus normalized tables: orders, order_items, customers, products - Normalize currency to store currency, keep refunds as negative rows, exclude cancelled and failed orders from revenue by default with a toggle Dashboard pages: 1. Overview: revenue, order count, average order value, refunds, all with date range picker and previous-period comparison 2. Products: units and revenue by product and variation, sortable 3. Customers: lifetime value, order count, first and last order, repeat vs one-time split 4. Cohorts: monthly first-purchase cohorts with repeat purchase rate over following months 5. Export: CSV download of any table for the selected date range Explicitly out of scope: abandoned cart tracking, email sending, segment automations, multi-store, user accounts, hosted deployment. Deliver: npm run sync, npm run dev, npm run build, a seed script that generates fake orders so the UI can be demoed without a live store, and a README that states plainly what this does not replace. ## Required capabilities - A WooCommerce store with REST API consumer key and secret - Somewhere to run a small Node process and a database (a cheap VPS or your own machine) - Read access to the store over HTTPS - Optional: ability to add one script tag to the storefront if you want cart tracking ## 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 Metorik. 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 ===== # Metorik indie build ## Goal Build the smallest trustworthy replacement for the core Metorik workflow for one developer or a tiny team. ## Scope Syncs your WooCommerce orders, customers and products into a local database on a schedule and serves a dashboard with revenue, product, cohort and repeat-purchase reports plus CSV export. ## 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: - Abandoned cart tracking and cart recovery emails, which need storefront instrumentation plus real email sending - Automated email flows tied to customer segments, with templates, throttling and unsubscribe handling - Battle-tested incremental sync for stores with hundreds of thousands of orders - Subscriptions, refunds and tax edge case handling that Metorik has already hit and fixed - Mobile-friendly polish, live order feed and the everything-in-one-place feel If those capabilities are essential, use Metorik 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 a self-hosted WooCommerce analytics dashboard. Single repo, no accounts, no cloud services, no telemetry. Stack, no substitutions: - TypeScript, Node 20, Fastify for the API - SQLite via better-sqlite3 as the local warehouse - React with Vite for the dashboard, Recharts for charts, plain CSS - Zero auth: it binds to 127.0.0.1 and is meant to run behind your own network Config in .env only: WOO_BASE_URL, WOO_CONSUMER_KEY, WOO_CONSUMER_SECRET, SYNC_INTERVAL_MINUTES, PORT. Ship .env.example, never commit real keys. Sync worker: - Pull /wp-json/wc/v3 orders, customers, products with pagination and per_page=100 - Incremental by modified_after, persisted watermark per resource in a sync_state table - Retry with exponential backoff on 429 and 5xx, log progress to stdout - Store raw JSON plus normalized tables: orders, order_items, customers, products - Normalize currency to store currency, keep refunds as negative rows, exclude cancelled and failed orders from revenue by default with a toggle Dashboard pages: 1. Overview: revenue, order count, average order value, refunds, all with date range picker and previous-period comparison 2. Products: units and revenue by product and variation, sortable 3. Customers: lifetime value, order count, first and last order, repeat vs one-time split 4. Cohorts: monthly first-purchase cohorts with repeat purchase rate over following months 5. Export: CSV download of any table for the selected date range Explicitly out of scope: abandoned cart tracking, email sending, segment automations, multi-store, user accounts, hosted deployment. Deliver: npm run sync, npm run dev, npm run build, a seed script that generates fake orders so the UI can be demoed without a live store, and a README that states plainly what this does not replace. ## Required capabilities - A WooCommerce store with REST API consumer key and secret - Somewhere to run a small Node process and a database (a cheap VPS or your own machine) - Read access to the store over HTTPS - Optional: ability to add one script tag to the storefront if you want cart tracking ## 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 Metorik. 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 ===== # Metorik product brief ## Problem The good news: every number Metorik shows you is already sitting in your own WooCommerce database, so nobody is gatekeeping your data. An agent can pull orders, customers and products through the Woo REST API into a local store and give you revenue charts, cohort and repeat-purchase views, product breakdowns and CSV exports in a weekend. The gap is everything that is not a chart: abandoned cart tracking needs a script on your storefront plus a capture endpoint, email automations need a sending domain and deliverability you do not have, and segment-driven campaigns need a rules engine that is a project of its own. Large stores also punish naive syncs, Metorik has spent years making that part boring. Build the dashboard, keep paying for the email side if that is why you signed up. ## Product outcome Syncs your WooCommerce orders, customers and products into a local database on a schedule and serves a dashboard with revenue, product, cohort and repeat-purchase reports plus CSV export. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - A WooCommerce store with REST API consumer key and secret - Somewhere to run a small Node process and a database (a cheap VPS or your own machine) - Read access to the store over HTTPS - Optional: ability to add one script tag to the storefront if you want cart tracking ## Explicit non-goals for v1 - Abandoned cart tracking and cart recovery emails, which need storefront instrumentation plus real email sending - Automated email flows tied to customer segments, with templates, throttling and unsubscribe handling - Battle-tested incremental sync for stores with hundreds of thousands of orders - Subscriptions, refunds and tax edge case handling that Metorik has already hit and fixed - Mobile-friendly polish, live order feed and the everything-in-one-place feel ## 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 a self-hosted WooCommerce analytics dashboard. Single repo, no accounts, no cloud services, no telemetry. Stack, no substitutions: - TypeScript, Node 20, Fastify for the API - SQLite via better-sqlite3 as the local warehouse - React with Vite for the dashboard, Recharts for charts, plain CSS - Zero auth: it binds to 127.0.0.1 and is meant to run behind your own network Config in .env only: WOO_BASE_URL, WOO_CONSUMER_KEY, WOO_CONSUMER_SECRET, SYNC_INTERVAL_MINUTES, PORT. Ship .env.example, never commit real keys. Sync worker: - Pull /wp-json/wc/v3 orders, customers, products with pagination and per_page=100 - Incremental by modified_after, persisted watermark per resource in a sync_state table - Retry with exponential backoff on 429 and 5xx, log progress to stdout - Store raw JSON plus normalized tables: orders, order_items, customers, products - Normalize currency to store currency, keep refunds as negative rows, exclude cancelled and failed orders from revenue by default with a toggle Dashboard pages: 1. Overview: revenue, order count, average order value, refunds, all with date range picker and previous-period comparison 2. Products: units and revenue by product and variation, sortable 3. Customers: lifetime value, order count, first and last order, repeat vs one-time split 4. Cohorts: monthly first-purchase cohorts with repeat purchase rate over following months 5. Export: CSV download of any table for the selected date range Explicitly out of scope: abandoned cart tracking, email sending, segment automations, multi-store, user accounts, hosted deployment. Deliver: npm run sync, npm run dev, npm run build, a seed script that generates fake orders so the UI can be demoed without a live store, and a README that states plainly what this does not replace. ## 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 Metorik capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Metorik indie build ## Goal Build the smallest trustworthy replacement for the core Metorik workflow for one developer or a tiny team. ## Scope Syncs your WooCommerce orders, customers and products into a local database on a schedule and serves a dashboard with revenue, product, cohort and repeat-purchase reports plus CSV export. ## 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: - Abandoned cart tracking and cart recovery emails, which need storefront instrumentation plus real email sending - Automated email flows tied to customer segments, with templates, throttling and unsubscribe handling - Battle-tested incremental sync for stores with hundreds of thousands of orders - Subscriptions, refunds and tax edge case handling that Metorik has already hit and fixed - Mobile-friendly polish, live order feed and the everything-in-one-place feel If those capabilities are essential, use Metorik 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 a self-hosted WooCommerce analytics dashboard. Single repo, no accounts, no cloud services, no telemetry. Stack, no substitutions: - TypeScript, Node 20, Fastify for the API - SQLite via better-sqlite3 as the local warehouse - React with Vite for the dashboard, Recharts for charts, plain CSS - Zero auth: it binds to 127.0.0.1 and is meant to run behind your own network Config in .env only: WOO_BASE_URL, WOO_CONSUMER_KEY, WOO_CONSUMER_SECRET, SYNC_INTERVAL_MINUTES, PORT. Ship .env.example, never commit real keys. Sync worker: - Pull /wp-json/wc/v3 orders, customers, products with pagination and per_page=100 - Incremental by modified_after, persisted watermark per resource in a sync_state table - Retry with exponential backoff on 429 and 5xx, log progress to stdout - Store raw JSON plus normalized tables: orders, order_items, customers, products - Normalize currency to store currency, keep refunds as negative rows, exclude cancelled and failed orders from revenue by default with a toggle Dashboard pages: 1. Overview: revenue, order count, average order value, refunds, all with date range picker and previous-period comparison 2. Products: units and revenue by product and variation, sortable 3. Customers: lifetime value, order count, first and last order, repeat vs one-time split 4. Cohorts: monthly first-purchase cohorts with repeat purchase rate over following months 5. Export: CSV download of any table for the selected date range Explicitly out of scope: abandoned cart tracking, email sending, segment automations, multi-store, user accounts, hosted deployment. Deliver: npm run sync, npm run dev, npm run build, a seed script that generates fake orders so the UI can be demoed without a live store, and a README that states plainly what this does not replace. ## Required capabilities - A WooCommerce store with REST API consumer key and secret - Somewhere to run a small Node process and a database (a cheap VPS or your own machine) - Read access to the store over HTTPS - Optional: ability to add one script tag to the storefront if you want cart tracking ## 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
# Metorik product brief ## Problem The good news: every number Metorik shows you is already sitting in your own WooCommerce database, so nobody is gatekeeping your data. An agent can pull orders, customers and products through the Woo REST API into a local store and give you revenue charts, cohort and repeat-purchase views, product breakdowns and CSV exports in a weekend. The gap is everything that is not a chart: abandoned cart tracking needs a script on your storefront plus a capture endpoint, email automations need a sending domain and deliverability you do not have, and segment-driven campaigns need a rules engine that is a project of its own. Large stores also punish naive syncs, Metorik has spent years making that part boring. Build the dashboard, keep paying for the email side if that is why you signed up. ## Product outcome Syncs your WooCommerce orders, customers and products into a local database on a schedule and serves a dashboard with revenue, product, cohort and repeat-purchase reports plus CSV export. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - A WooCommerce store with REST API consumer key and secret - Somewhere to run a small Node process and a database (a cheap VPS or your own machine) - Read access to the store over HTTPS - Optional: ability to add one script tag to the storefront if you want cart tracking ## Explicit non-goals for v1 - Abandoned cart tracking and cart recovery emails, which need storefront instrumentation plus real email sending - Automated email flows tied to customer segments, with templates, throttling and unsubscribe handling - Battle-tested incremental sync for stores with hundreds of thousands of orders - Subscriptions, refunds and tax edge case handling that Metorik has already hit and fixed - Mobile-friendly polish, live order feed and the everything-in-one-place feel ## 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 a self-hosted WooCommerce analytics dashboard. Single repo, no accounts, no cloud services, no telemetry. Stack, no substitutions: - TypeScript, Node 20, Fastify for the API - SQLite via better-sqlite3 as the local warehouse - React with Vite for the dashboard, Recharts for charts, plain CSS - Zero auth: it binds to 127.0.0.1 and is meant to run behind your own network Config in .env only: WOO_BASE_URL, WOO_CONSUMER_KEY, WOO_CONSUMER_SECRET, SYNC_INTERVAL_MINUTES, PORT. Ship .env.example, never commit real keys. Sync worker: - Pull /wp-json/wc/v3 orders, customers, products with pagination and per_page=100 - Incremental by modified_after, persisted watermark per resource in a sync_state table - Retry with exponential backoff on 429 and 5xx, log progress to stdout - Store raw JSON plus normalized tables: orders, order_items, customers, products - Normalize currency to store currency, keep refunds as negative rows, exclude cancelled and failed orders from revenue by default with a toggle Dashboard pages: 1. Overview: revenue, order count, average order value, refunds, all with date range picker and previous-period comparison 2. Products: units and revenue by product and variation, sortable 3. Customers: lifetime value, order count, first and last order, repeat vs one-time split 4. Cohorts: monthly first-purchase cohorts with repeat purchase rate over following months 5. Export: CSV download of any table for the selected date range Explicitly out of scope: abandoned cart tracking, email sending, segment automations, multi-store, user accounts, hosted deployment. Deliver: npm run sync, npm run dev, npm run build, a seed script that generates fake orders so the UI can be demoed without a live store, and a README that states plainly what this does not replace. ## 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 Metorik 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
Because a store owner wants the abandoned cart email that actually sends, not a chart they built themselves. Reports are the easy half and they are the half you can replicate; the automation half means a warmed sending domain, unsubscribe compliance, segment rules and someone to blame when the flow misfires during a sale. Metorik also absorbs the pain of WooCommerce version drift, plugin conflicts and gigantic order tables, which is unglamorous work that quietly eats your weekends if you own it.
xAbandoned cart tracking and cart recovery emails, which need storefront instrumentation plus real email sending
xAutomated email flows tied to customer segments, with templates, throttling and unsubscribe handling
xBattle-tested incremental sync for stores with hundreds of thousands of orders
xSubscriptions, refunds and tax edge case handling that Metorik has already hit and fixed
xMobile-friendly polish, live order feed and the everything-in-one-place feel
Nothing worth pointing at. That's why the prompt exists.
share on X ↗"I just replaced Metorik ($25/mo) with one prompt"
Vibecode Metorik
Kinda. The core of Metorik is buildable in a weekend with the prompt on this page, but there are real gaps: Abandoned cart tracking and cart recovery emails, which need storefront instrumentation plus real email sending, Automated email flows tied to customer segments, with templates, throttling and unsubscribe handling. Read the honest list above before committing.
How much does Metorik cost?
Metorik costs about $25/month (Starter Plan, checked 2026-08-18), which is $300 per year.
What do I lose by replacing Metorik?
Honestly: Abandoned cart tracking and cart recovery emails, which need storefront instrumentation plus real email sending; Automated email flows tied to customer segments, with templates, throttling and unsubscribe handling; Battle-tested incremental sync for stores with hundreds of thousands of orders; Subscriptions, refunds and tax edge case handling that Metorik has already hit and fixed; Mobile-friendly polish, live order feed and the everything-in-one-place feel. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Metorik?
No mature open-source alternative worth pointing at, which is exactly why the one-shot prompt on this page exists.