# Shopgraph

> Deploy your own e-commerce decision-memory SaaS — flat-priced where Triple Whale bills on GMV, and derived capture where Shopify's free annotations stop.

Source page: https://saascode.ai/products/shopgraph
Machine-readable record: https://saascode.ai/products/shopgraph.md

One-time purchase · full source code · self-hosted by the buyer.

Price: $149 (one-time)

## How to read this document

Written for a model auditing this product on a buyer's behalf. Two labels
appear throughout and they mean different things:

- **measured** — produced by a script reading the product's own source tree
  or database at the stated date. The method is named beside each number.
- **stated** — written by the seller. True or not, it is a claim, and this
  document does not ask you to treat it as evidence.

The live demo is the strongest verification available from outside: it runs
the same source a buyer receives. Nothing to sign up for — the public side is
open, and the seeded credentials below get you into each role.

## What it is

Shopgraph records the decisions an e-commerce seller makes — ad campaigns, listing edits, restock calls — bound to what those decisions produced: conversion lift, organic-ranking movement, the consequence of a stockout. Then it makes the whole history answerable in plain language.

## Live demo

Two doors into the same running instance, and the same source a buyer
receives. There is no account to create; the public side is open, and the
seeded credentials below sign you into each role.

- **Guided (recommended):** https://saascode.ai/demo/shopgraph — our shell, with a role switcher and
  the credentials in the menu. Best for a person.
- **Direct:** https://shopgraph.saascode.ai — the product on its own, no chrome.
  Best when you are relaying steps to someone, or fetching a page.

3 roles seeded on the demo (of the 4 the schema defines — the build data below counts them all). Credentials are published deliberately: these
are demo accounts on a public demo instance, and a reviewer who cannot get
in cannot verify anything.

- **Seller's teammate** (`member`) — `jordan.kim@demo.com` / `demo123`
  Records decisions and reads the timeline.
- **Seller owner** (`org_admin`) — `user@demo.com` / `demo123`
  Runs the account: decisions, connectors, plan, team.
- **Platform admin** (`super_admin`) — `admin@demo.com` / `demo123`
  The backend: every seller account and its settings.

Or open a role directly: https://saascode.ai/demo/shopgraph?role={role}

## Measured build

*measured — each number names the method that produced it.*

- **roles: 4** — distinct roles accepted by the role CHECK constraint: admin, member, org_admin, super_admin
- **tables: 54** — distinct CREATE TABLE statements across every applied migration
- **migrations: 54** — .sql files in supabase/migrations
- **page modules: 69** — files named page.tsx under src/app, excluding node_modules and .next
- **source lines: 109,663** — lines of code (comments and blank lines excluded) across 793 TypeScript files (99,710) and 70 SQL files (9,953); node_modules and .next excluded
- **api route files: 159** — files named route.ts under src/app/api
- **http operations: 215** — exported HTTP method handlers across those files, de-duplicated per file, OPTIONS excluded as CORS preflight
- **schema graph: 54 tables, 88 relationships** — parsed from the applied migrations

A large number here is scope, not quality. It says the product models a
real domain rather than a CRUD skeleton; it says nothing about code
quality, duplication, test coverage or maintainability, and should not be
read as if it did.

Release: v1.0.0 · built 2026-06-27

## Complete capability inventory

9 capabilities. Each summary is *stated* — selected from the
product's own buyer documentation, or written by the seller where marked.

### Connectors & the Context API

- **Shopify connector (V1.0)** — Shopify is the connector in this version — connected by authorisation, kept current by webhooks and a scheduled sync, so decisions can be bound to real store metrics rather than to numbers typed in by hand.
- **Context API (agent-queryable)** — The seller's decision corpus, exposed to their own AI agents through an authenticated API and a machine-readable bridge.

### Decisions & questions

- **Decision timeline** — Every decision in order, with its outcome where one exists. This is the surface for a seller reconstructing a season: what did we actually change between March and June.
- **Similar-decision retrieval (semantic + FTS)** — Retrieval runs two ways at once — semantic similarity and full-text search — because the two fail differently.
- **NL chat over own history (RAG, zero-hallucination)** *(seller-authored)* — Plain-language questions answered strictly from the seller's own recorded decisions and outcomes. When the history holds no answer it says so, rather than producing a plausible one.
- **Query-template library (run prebuilt)** *(seller-authored)* — Prebuilt questions a seller can run against their own decision history without composing anything — the ones every store asks eventually, available before they know to ask them.
- **Unlimited decision history** — A decision is recorded with what was changed, when, and why. Later, the outcome attaches to it — the metrics that moved, and by how much.
- **Custom query templates** *(seller-authored)* — Saves a seller's own recurring question as a template, so the analysis they run every month is one action rather than something reassembled from memory each time.

### What it is

- **Decision capture + outcome** — Every seller already has analytics telling them what happened. Almost none can answer what they did that caused it.

## What each system gives the operator

*stated.*

- **Connectors & the Context API** — Your own AI agents can read what the store already learned.
- **Decisions & questions** — You can ask what happened last time you tried this, and get the real answer.
- **What it is** — The reasoning behind past changes stops leaving with the person who made them.

## The problems it was built to solve

*stated — the seller's argument, given in full so you can judge it.*

### The reason behind a past change is still there when you need it.

Every store runs the same experiment more than once. A price moves, a bundle is tried, a channel is tested — and eighteen months later somebody proposes it again, with no memory of the first attempt or why it was abandoned. The knowledge lived in a spreadsheet, a Slack thread and one person's head, and at least one of those has left. The cost is not the failed experiment; it is paying for the same lesson twice, at full price, with confidence.

### When the record does not contain an answer, it says so.

An assistant over commerce data is only useful if it refuses to guess. A confident summary about last quarter's promotion that was not actually derived from last quarter's data is worse than silence, because it will be repeated in a planning meeting and acted on. The failure is invisible by design: nobody checks a plausible answer, and the decision built on it looks exactly like a well-informed one right up until the numbers come in.

### The store's decision history becomes something your automation can query.

Sellers are wiring AI into their operations, and every one of those agents starts with no knowledge of the business it is acting for. It does not know which promotions failed, which suppliers were dropped, or why the returns policy is what it is — so it makes suggestions that were tried and rejected two years ago. Each one has to be caught by a human who remembers, and the agent that was supposed to save time becomes something else to supervise.

## What it takes to run it

*stated — external services the buyer supplies and pays for directly.*

- **Node host** (required) — No platform lock-in.
- **Supabase** (required) — Postgres with row-level security and vector search for retrieval.
- **An embeddings provider** (required) — Decisions are embedded on capture. A fallback provider is supported so a single outage does not stop ingestion.
- **An AI provider key** (required) — The grounded answering layer runs on it.
- **A Shopify app registration** (required to connect a store) — Supplied by the operator of the installation.
- **A payment provider** (required to charge) — Configured by the operator, not hardwired.
- **A job scheduler** (required) — Store sync and outcome collection run on a schedule. Without it decisions are still captured by hand and no metric attaches itself.

## FAQ

**What exactly do I receive after purchase?**

The complete source repository behind the live demo — 109,663 lines across the application and its database, 54 tables defined by 54 migrations that the shipped scripts apply for you, plus the seed data, the demo accounts and the setup documentation. Not a subset and not a scaffold: the same code that runs the demo you just used.

**Is the live demo the same product whose source I receive?**

Yes. The Shopgraph demo runs the delivered release (v1.0.0), and the build figures on this page are measured from that same source — not from a showcase build kept separately.

**Can I test every account role before buying?**

Yes — all 3 of them: Seller's teammate, Seller owner, Platform admin. Each one is seeded in the live demo and reachable from the role board above, so you can inspect the product from the customer's side, the agent's side and the administrator's side before you decide.

**Is this a complete product or a starter template?**

Complete. 69 page modules and 215 HTTP operations, with authentication, roles, billing, an administration panel, background jobs and seeded demo data all wired and running. A template gives you the shape of an application; this is one you can deploy and start operating.

**Can I rebrand and modify it?**

Yes, without asking. The name, identity, copy, styling and code are yours to change. Rebranding and operating it as your own service is exactly what the licence is for.

**What does the licence allow?**

A perpetual, worldwide, non-exclusive, non-transferable licence to the product you bought and to every update released for it. The Standard licence covers one business — yours. If you deploy for clients, the Client licence covers up to five. You can modify it, rebrand it, deploy it and charge your own customers.

**Can I resell the source code?**

No. Reselling, redistributing, sublicensing or giving away the source itself is not permitted under either licence. You build and deliver products with it — the code stays with you.

**What services and ongoing costs are required?**

You bring your own accounts, so we never mark anything up and there is no ongoing cost to us beyond the purchase. Required: Node host, Supabase, An embeddings provider, An AI provider key, A Shopify app registration, A payment provider, A job scheduler. Optional: none. The table above says exactly what stops working without each one; most have usable free tiers at low volume.

**How difficult is deployment?**

Two ways, and most buyers use the first. The installer in your saascode dashboard walks it: you create free accounts at Vercel and Supabase, connect them, and it provisions the database, applies 54 migrations, seeds the data, deploys and verifies the result — you watch the steps go green. Or take the source and do it yourself with the shipped scripts and docs, which is the same sequence run by hand.

**What updates and support are included?**

Updates to that product for as long as we maintain it — no renewal fee and no expiry date on your access. Support covers download problems, defects in the code as shipped, questions about what the product does and how it is structured, and licence questions. It does not cover debugging your own modifications, building features for you, or setting up your hosting and third-party accounts.

**Why does a complete codebase cost $149?**

Because it was built once and is distributed many times. SaaSCode builds each product and ships the same finished release through the catalog, so the price reflects repeatable distribution — not a reduced codebase, an unfinished template, or what the same work would cost commissioned.

**Do I need to be a developer?**

No, for the normal path. You create free accounts at Vercel and Supabase, connect them to the installer in your saascode dashboard, and it does the deployment for you — provision, migrate, seed, deploy, verify. What it asks of you is creating two accounts and copying a token, not writing code. If you would rather deploy it yourself, or host it somewhere else, the full source and the scripts are yours to do that with. Running the product day to day needs no technical skill at all: that happens through its own interface, which is what the demo shows.

## Licence

The buyer receives the complete source and may deploy, modify and operate it
as their own SaaS, charging their own customers. The source itself is not
resold or redistributed: you build and deliver **with** it, you do not sell **it**.

## What this document cannot tell you

Stated plainly because a review that misses it is not a review:

- code quality, duplication, or architectural consistency
- test coverage
- query performance under load
- security posture beyond what the stack implies
- how maintainable it will be in a year

Scope is measurable from outside; implementation quality is not. Anyone
evaluating this should say so rather than infer quality from size.

## Written about it

- [Shopgraph vs Triple Whale](https://saascode.ai/inside/shopgraph-vs-triple-whale.md)
- [Road to Shopgraph](https://saascode.ai/inside/road-to-shopgraph.md)
- [Shopify E-Commerce Analytics and Decision Memory: What Every Tool Captures Without Being Asked](https://saascode.ai/inside/shopify-e-commerce-analytics-and-decision-memory-what-every-tool-captu.md)

## Links

- Catalog page: https://saascode.ai/products/shopgraph
- Product record: https://saascode.ai/inside/products/shopgraph
- Live demo: https://shopgraph.saascode.ai
- Every product: https://saascode.ai/llms.txt