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.
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.
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.
- Decision capture + outcome
- Similar-decision retrieval (semantic + FTS)
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.
- NL chat over own history (RAG, zero-hallucination)
- Query-template library (run prebuilt)
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.
- Context API (agent-queryable)
- Shopify connector (V1.0)
Amazon is deferred. It is declared in the roadmap and ships as a placeholder record rather than a working ingestion path in this release. Stated here because a connector list is exactly where a buyer assumes everything listed works.
The connector count is a plan limit; the multi-connector capability unlocks above the entry tier.
This is the piece that makes the corpus infrastructure rather than a destination. An agent drafting next quarter's campaign can consult what the last three produced, without a person retrieving it and pasting it in.
Available from the mid tier.
Semantic search finds the decision described in different words. Text search finds the exact SKU, campaign name or number that a semantic match would blur past. A seller asking about "the bundle thing we tried" needs the first; a seller asking about a specific listing code needs the second.
Custom templates are available on the top tier.
The outcome is a separate act from the decision on purpose. At the moment a campaign launches nobody knows what it produced, and a tool that demands the result up front gets used once.
Custom templates are available on the top tier.
Six months later the question is never "what was revenue in March". It is "we changed the title on that listing sometime in spring — did it help, and by how much?" Analytics cannot answer that, because the decision was never recorded next to the number.
Shopgraph is the record of the decision, joined to its result, and searchable by meaning rather than by remembering when it happened.
The platform underneath the product — counted in this product's own source, not claimed from a template. Where a row carries a list, open it to read the names behind the number.
Coinbase
dLocal
Flutterwave
Komoju
Mollie
NOWPayments
Opn
Paystack
ActiveCampaign
Customer.io
Segment
Canny
Amplitude
Custom Head Scripts
Pushover
Twilio SMS
Crisp
Tawk.to
Monday.com
fal.ai
Axiom
hCaptcha
Freshsales
Pipedrive
Salesforce
Pabbly Connect
AWS S3
Backblaze B2
Mux
QuickBooks
XeroHover a table to isolate what it touches; click one to read its relationships. The big nodes are what everything else hangs off. organizations is referenced by 47 tables because every single record in this product belongs to an organization, and that is what makes tenant isolation a property of the database rather than something the application has to remember on every query.
all 54 tables, as text
active_boosts · admin_notifications · announcement_dismissals · announcements · api_key_logs · api_keys · audit_logs · automation_log · automation_templates · chat_conversations · chat_messages · connector_sync_logs · credit_balances · credit_transactions · currencies · data_exports · data_imports · decision_embeddings · decision_metrics · decision_outcomes · decision_types · decisions · faq_categories · faq_items · feature_flags · inbound_webhooks · languages · marketplace_connectors · notification_log · notification_rules · notifications · organization_limit_overrides · organizations · plans · platform_secrets · platform_settings · product_purchases · products · provider_prices · push_devices · query_template_runs · query_templates · report_templates · roles · scheduled_tasks · subscriptions · theme_page_sections · theme_section_library · theme_sections · translations · user_sessions · users · webhook_logs · webhooks
The chassis, and anything particular to this product. 5 required, 2 optional.
No platform lock-in.
Postgres with row-level security and vector search for retrieval.
Decisions are embedded on capture. A fallback provider is supported so a single outage does not stop ingestion.
The grounded answering layer runs on it.
Supplied by the operator of the installation.
Configured by the operator, not hardwired.
Store sync and outcome collection run on a schedule. Without it decisions are still captured by hand and no metric attaches itself.
Already built — plug and play
Every provider integration in this list ships wired into the product. You bring your own keys, connect them in the admin, and go live — there is no integration code to write. Nothing is resold through us: the ongoing cost is whatever these providers charge you. Capabilities marked plan-gated elsewhere on this page unlock by plan, not by extra code.
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.