E-commerce · 2025

YodiBrodi

Customers design the shirt. The shop handles everything after that.

RoleFreelance, end to end
StackNext.js, Stripe, Postgres
ScopeStorefront, designer and admin
StatusLive

The problem

A custom apparel shop is really two businesses stapled together: a storefront selling blanks, hats and Pokémon singles, and a print floor turning customer artwork into screen-printed and embroidered goods.

Both halves were being run by hand. Artwork arrived by email and text, orders lived in a spreadsheet, addresses were retyped into a carrier site, and nobody could tell you who the regulars were.

The approach

The storefront carries a designer: pick a blank, upload your art, place it, and choose screen printing or embroidery. What the customer approves is what reaches the press, so nothing is redrawn from a description in an email.

Everything after checkout is wired together. Payment captures, the artwork and placement land on the print queue as a job ticket, the cheapest label is bought and emailed, tracking goes out, and lifetime rewards points are credited to the account without anyone opening a tab.

What happens after pay

01payment capturedwebhook
02art queued to pressjob ticket
03label boughtcheapest
04points creditedlifetime

Built in, not bolted on

Design it in the browsercustomer
Screen print or embroideryper job
Lifetime rewards tiersnever expire
Orders, stock and shippingone admin

Outcome

Artwork stopped arriving as email attachments and fulfillment stopped being a daily chore. The shop takes custom work and card orders through the same checkout, and the rewards tiers give returning customers a reason to come back to it.

Next upModora