The size you actually wear
- An order confirmation the size you chose, in your own inbox
- A top, a bottom, a shoe the three sizes worth keeping, kept
- Every drop after pieces in your size come first, and Sunday asks when it has none
How it works
Setup takes about three minutes, and everything after it happens in a chat you already have.
Sign in with Google, then answer a short quiz: the looks you keep, the brands you want, the ceiling on what a whole look should cost. Add one photo if you want to see things on yourself.
Sunday reads your taste and your derived sizes, then searches the catalog for pieces that are in stock where you live and sit inside your budget.
The render arrives first, then every piece with its brand, its price and a link. Reply in plain words and the next drop moves toward you.
The try-on
Share one photo and every look arrives rendered on you. Without one, a drop carries the pieces' own product shots.
A try-on render is a very good sketch. It gets the garment, the colour, the drape and the proportion on your frame close enough to tell whether a thing is worth your money.
It is not a mirror. It will not tell you how a collar sits on your neck by three in the afternoon, or how a knit behaves after a wash. Sunday would rather say that plainly than sell you a render as a photograph.
The photo stays attached to your account and is used to put looks on you. Replace it whenever you want, and every drop after that is rendered on the new one.
A look rendered by Sunday, assembled from items in stock at the time it was sent. Rendered pieces: Vuori Bridge Button Down $78 · Zara Striped Bloomer Pants $89.90.
Sizes and wardrobe
Connect the inbox your order confirmations land in, and Sunday reads your sizes out of them.
The same emails say what is already in your wardrobe. Sunday tags those pieces so a drop can be built around them, and so it stops recommending you something you bought two months ago.
Anatomy of a drop
Every drop that lands is the same three things, in the same order.
It opens with the outfit rendered on the photo you gave at setup, so you judge the clothes on your own body. Skip the photo and you get clean product shots instead.
Sample The layout of a drop. The named shirt and trousers are real pieces, rendered from the live catalog; the remaining prices arrive with a real drop.
The whole look
Every piece is named, with its brand, its price and a link to the brand's own page, and the total sits at the bottom. Sunday never touches your card.
The render doubles as the fit check. Sunday reads your size from orders you have already placed, so a fit note reaches you before you buy rather than after.
How taste is learned
Nothing is preloaded, so every drop after the first is shaped by what you said about the last.
You answer a short set of questions. Sizes, a budget, the brands you want and the ones you do not. It is deliberately thin, because it is a starting point and not a profile.
One outfit, built from items in stock in your region and inside the ceiling you set. It is a guess made from your answers, and Sunday treats it as one.
Too expensive. Wrong colour. Not that brand. Every answer is recorded against the piece, the brand and the category it came from, and it moves the next drop.
Connect the inbox and Sunday reads the order confirmations already sitting in it: what you bought, what size you bought it in, and what is therefore already in your wardrobe.
Muted brands stop appearing. Sizes stop being a question. What you skipped stops coming back, and the fit notes Sunday keeps for each brand start doing the quiet work.
Control
Everything Sunday does sits beside everything it will not, because both are the product.
One exception, and it is opt in: the errand, Sunday's premium tier, where Sunday does the buying inside the ceiling you set. By invitation.