Commerce · App Starter
Ecommerce Template
A complete online store — storefront, cart, orders, inventory — generated into a codebase with no platform fees attached.
Describe what you sell and how, and Dual7 generates this store around it: seven connected entities, a fast storefront, a real admin, and an order pipeline, shipped as a full-stack app you deploy yourself. No transaction percentage, no theme sandbox, no plugin marketplace between you and a feature.
- 7 core entities
- Storefront + admin
- Code you own
- Vibe + Governed modes
01 · Data model
What's inside: the data model
Under every store that scales cleanly is a schema that got variants, inventory, and orders right on day one. These seven entities are that foundation — generated into your codebase, where a weird product type is a migration you write, not a limitation you inherit.
| table | what it holds |
|---|---|
products | What you sell — title, description, images, status, and the variant set that carries the actual prices. |
variants | The purchasable units: size, color, format, each with its own SKU, price, and stock position. |
collections | Merchandised groupings — new arrivals, sale, gift guide — curated by hand or by rule. |
carts | In-progress baskets tied to sessions or customers, the raw material of abandonment recovery. |
orders | Placed purchases with line items, totals, payment state, and fulfillment status — the spine of the admin. |
discounts | Codes and automatic promotions with scopes, limits, and windows — rules you can read, not a black-box engine. |
inventory | Stock levels per variant per location, decremented at checkout and reconciled on receipt. |
02 · Screens
Signature modules
Storefront and admin
01A customer-facing catalog with product pages, collections, and search, plus an operator admin over the same tables. Change the storefront by editing components in your repo — no theme language, no locked sections, no marketplace dependency for a layout change.
Cart and checkout
02A persistent cart flows into a checkout you control end to end: address, shipping choice, payment via your processor, confirmation. Because checkout is your code, the field your business needs — a gift note, a delivery date, an age check — is an edit, not an app.
Order lifecycle
03Orders move through payment, fulfillment, shipment, and delivery with status history at every step. Refunds and partial fulfillments are modeled, not improvised, and every state change is queryable for the ops report you'll eventually want.
Inventory tracking
04Stock decrements at purchase, restores on cancellation, and reconciles on receiving. Low-stock thresholds flag reorders before sellouts, and oversell protection is a database constraint — the kind of guarantee a spreadsheet can't make at 2 a.m. on launch day.
03 · Process
How it works
- 1You
Describe your catalog and how you sell
Physical or digital, five products or five thousand, one-off or repeat purchase — describe it plainly. The starter shapes the schema, storefront, and checkout to match.
- 2Vibe mode
Shape the store in Vibe mode
Iterate conversationally on the generated store: restructure product pages, add a field to checkout, define a discount rule. Every change is real code you can diff before it goes live.
- 3Governed mode
Go live through the governed pipeline
Ship to your own hosting through approval gates, with an audit trail of what changed and who cleared it. Your catalog, orders, and customers live in your database from the first sale.
04 · Fit
Who the Ecommerce starter is for
Brands done with platform math
Percentage fees on every order, monthly tiers, paid apps for basics — rented commerce compounds against you as you grow. When the store is code you own, growth changes your hosting bill by dollars while the platform math would have taken points of revenue.
Merchants whose products don't fit the mold
Made-to-order dimensions, deposits, quote-then-buy, mixed digital and physical — the products platforms handle awkwardly are usually the profitable ones. A generated store starts from your selling motion, so the awkward case is the designed case.
Agencies building client stores
Generate each client a store shaped to their catalog and hand them the repository, instead of assembling the same plugin stack again and hoping this quarter's platform update doesn't break it. The deliverable is a codebase, which is what clients think they're paying for anyway.
Developers who'd rather extend than fight
If you've ever patched around a checkout you couldn't touch or scraped your own store's API for a report, you already know the argument. Here the store is a normal app in your stack — extend it with the tools you use everywhere else.
05 · Yours
Customize it, own it
Make it yours
Start by making the catalog yours: rename entities to match the merchandise — products to pieces, collections to drops — and add the attributes your buyers filter by, whether that's material, roast level, or compatibility. Vibe mode turns those requests into schema, admin, and storefront changes in one pass.
Then go as deep as the business demands: subscriptions on top of orders, a wholesale price tier, a bundle builder, loyalty points. The generated app is an ordinary full-stack codebase with no runtime dependency on Dual7, so your team ships store features the way they ship anything — branch, review, deploy.
Why a starter, not a subscription
A hosted store platform is a landlord: it sets the fees, owns the checkout, and holds your customer list in a database you query through a metered API. This starter generates the whole store — schema, storefront, admin, business rules — as source in your repository. The margin you keep and the data you hold are structural, not promotional.
In exchange you operate an application, and Dual7's governed pipeline keeps that honest — gated deploys, an audit trail, and regeneration for structural changes so the codebase evolves deliberately instead of accreting patches. Ownership with guardrails, not ownership as a dare.
06 · Industries
Industry versions
Food & Beverage Store
A store that understands perishables — pickup windows, lot tracking, and rush-day order flow — in code your brand owns.
Digital Products Store
A storefront for files — presets, fonts, courses, plugins — with licensing and delivery built in and no marketplace taking a cut.
Fitness & Wellness Store
A store built for repeat purchase — subscriptions, stacks, and flavor-level stock — generated into code your brand controls.
Ecommerce template — frequently asked questions
What do I get when I start from this ecommerce template?
A working store generated into a codebase you own: products with variants, collections, carts, orders, discounts, and inventory, plus a storefront, an operator admin, and a checkout wired to your payment processor. You deploy it on your infrastructure and keep every sale's data in your database.
How do payments work?
Checkout integrates with your own payment processor account, so funds settle directly to you and Dual7 never sits in the money flow. There's no added transaction percentage — the economics are between you and your processor.
Can it sell digital products as well as physical ones?
Yes — variants can represent files and license grants as easily as shelf stock, and fulfillment adapts per product type. There's a dedicated digital products version of this starter with download delivery and licensing modeled in; see the variant page.
Will it handle my catalog size and traffic?
The generated store is a standard modern web stack that scales the way your hosting scales — and because you own the code, so do the levers: caching, search indexing, image pipelines. A launch spike is a capacity decision you make, not a plan-upgrade prompt.
How is this different from open-source ecommerce platforms?
Open-source platforms hand you a huge generic codebase to configure downward. This starter generates upward from your catalog and selling motion — the store contains what your business needs and nothing it doesn't, which is the difference between owning a codebase and inheriting one.
Can I migrate my existing products and orders in?
The schema is plain relational tables, so a CSV export of products, variants, customers, and order history maps in directly. Owning the schema means the migration script bends to your data instead of your data bending to an importer.
Related
Dual7 App Starters
Build your Ecommerce on your terms
A complete online store — storefront, cart, orders, inventory — generated into a codebase with no platform fees attached. Describe your version to start — the output is a project you own.