Can I vibecode Metorik?

KINDA · weekend project

price $25/moyou'd save $300/yrbuild time a weekendcategory 📊 analyticsreplaced by 0 people

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 prompt

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.

$ open in your agent (prompt prefilled, you press enter) or copy it raw · this prompt is generated from the build plan · improve it via PR

why people still pay

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.

what you lose

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

prior art · use these instead of building, if you'd rather

Nothing worth pointing at. That's why the prompt exists.

share on X ↗"I just replaced Metorik ($25/mo) with one prompt"