Wine Import & Retail
Above Wines
Above Wines (Wine Import & Retail): One commerce platform for the online shop, the register, wholesale buyers and the owner's back office.
Overview
Above Wines is an Italian wine importer in Irving, Texas, with a retail brand, Grappolo Wine Shop. We built one commerce platform that covers the online shop, the in-store register, a wholesale buyer portal and the owner's back office.
The brief
The brief was one platform where a single order can be followed across the shop, the register, wholesale and the owner's reports.
What we built
Online shop
A public storefront with a catalog, product pages, cart and checkout. Card payments connect to the Accept Blue gateway, and a refund credits the card before the order is marked refunded.
Web Development →Register
A touch register for the shop floor. Owners and managers can comp an item with a recorded reason, void a finished same-day sale and sign a customer up to the wine club at the counter.
Custom Systems Architecture →Wholesale portal
Wholesale buyers sign in to a portal with tier pricing, a quick-order pad, invoices and balances, and they can order wine by the bottle.
Custom Systems Architecture →Owner back office
An admin area with a dashboard, customer records, inventory, a pricing engine, accounting, reports and a blog editor. Goods carry a Food and beverage category, and non-alcohol goods are left out of the alcohol excise export.
Back-End Development & Infrastructure →Journal
The old blog moved across: 59 posts with their original addresses and dates, and 93 images rehosted on the new site.
SEO & Technical Optimization →How it helps
- One database sits behind the shop, the register and wholesale, so an order can be followed across all of them.
- Comps are limited to owners and managers, each one carries a reason, and a report shows them by reason and by staff.
- Non-alcohol items stay out of the alcohol excise export.
- The admin includes a blog editor for the journal.
Every figure on this page is a count from a build record or a test run. A business result goes on this site only when it traces to a source we can open on a call: Results.
What it runs on
Next.js and TypeScript, with Postgres on Supabase through Drizzle, deployed to Cloudflare. Sign-in is passwordless and row-level security is applied in the database. An encrypted nightly backup goes to Cloudflare storage, and a monitor raises an alert when something fails.
How the work ran
This is how we run every engagement. It describes the process, not a timeline for this project.
The audit
We map what you already run and show you where it leaks. You keep the map either way.
The plan
What we would change, in what order, what it costs, and what number we will judge it on. You approve before anything is built.
The build
Each piece goes live on its own, so you see progress weekly instead of waiting for a big reveal.
The run
Managed, measured, month to month. Every channel judged on what a booked job costs you.
Builds are quoted once and built once; retainers you can stop any month. The full process and the published prices: How we work.
Questions
Is there a long-term agreement?
What does a build like this cost?
Do you use AI on this kind of work?
Read the full charter: The AI Charter.