← All work
E-commerce platform · AI · Inventory Design, engineering & ML · End to end

nayokids

A curated kids-fashion platform that remembers every child — and grows with them.

nayokids.com
NAYO Kids Boutique homepage — editorial hero, 'The little things, done well'
Overview

NAYO is a curated own-brand children's store selling both individual pieces and complete, beautifully-boxed outfits. Under a quiet, editorial storefront sits a full commerce engine: a real-time inventory ledger, a personalization layer that learns each child, a machine-learning service, and a Seller Central the owner runs the whole business from — built for the Israeli market, top to bottom.

/for-you
Curated for You — style profile, member deals, Size Watch growth milestone, 'Because you loved' rail
Curated for You — Size Watch predicts the next size before the child outgrows the last one.
Intelligence & memory

It remembers every child.

Each family gets a store that learns. From real purchase and wishlist history it builds a style profile, recommends what fits the child's taste, and runs Size Watch — the outgrow predictor that quietly tracks each child up the size ladder and flags the next size before the current one stops fitting. It's the highest-intent moment in kidswear, turned into software.

◇Personal recommendations from real history
◇Size Watch — per-child outgrow prediction
◇Style profile & "Because you loved…" rails
◇Loyalty tiers, points & store credit
Recs from purchase + wishlist signals Predicts the next size per child Consent-gated — nothing tracked without opt-in
Seller Central · Inventory
Inventory — per-size stock matrix, reorder point, outfit-gating, movement ledger
Per-size stock, reorder points, and which outfits each piece is holding up — live.
The inventory engine

A warehouse that can't lie.

Pieces and outfits draw from one shared stock pool, so an outfit's availability is only ever the minimum across its parts — computed live, never cached. Every movement is written to an immutable ledger, and checkout reserves stock so two parents can't buy the last one. "Only 2 left" is a fact, not a guess — which, under Israeli truthful-scarcity law, is exactly what it has to be.

◇Immutable, append-only stock ledger
◇Availability = min() across outfit pieces
◇Checkout reservations — no overselling
◇Standalone vs bundle stock allocation
Zero oversell by design Truthful scarcity badges Reorder points & low-stock alerts
Seller Central · Overview
Command Center — income, orders, AOV, profit, acquisition-to-retention funnel
The Command Center — the whole business at a glance, run by the owner alone.
Seller Central

The owner runs everything.

A full back office, not a plugin. Revenue, funnel and margin at a glance; an outfit composer with live cost roll-up; theme studio, orders, reviews, coupons, tiers and consented analytics that feed the recommendation engine. Everything the owner needs to merchandise, price and restock — from morning coffee, on a phone.

◇Revenue, AOV, profit & funnel dashboard
◇Outfit composer with live margin
◇Orders, reviews, coupons & tiers
◇Consent-gated analytics, its own data
Under the hood

Many moving parts, one system.

A typed codebase end to end, a pure pricing core, a separate ML service that can fail without touching checkout, and a data layer built to scale from the live app to full production.

Frontend

TypeScriptReactNext.js (SSR)TailwindFramer Motion

Backend

Node.jsExpress / Route HandlersZodscrypt authBullMQ

Data & search

PostgreSQLPrismaRedisMeilisearch (he+en)

Intelligence

PythonFastAPIscikit-learnLightGBMlifelines

Commerce & infra

PayPlus / TranzilaGreen InvoiceCloudflare R2 + CDNSentry

Trust & compliance

PPL Amendment 13IS 5568WCAG 2.1 AAHebrew / RTL

Live today on a Node + React build with the immutable ledger, pricing engine, loyalty, heuristic recommendations and consent-gated analytics running in production — engineered to scale to the Next.js SSR + PostgreSQL + Redis + Meilisearch + FastAPI architecture below.

Browser Storefront + Seller Central Application — Next.js SSR pages · Route Handlers · pure pricing core · Zod boundaries PostgreSQL + Prisma system of record · ledger Redis reservations · cache · queue Meilisearch he + en index ML · Python + FastAPI off the request path Payments · Invoicing · Mail · Images (R2 + CDN) · Sentry all external, hosted — card data never touches the server
Security & compliance

Money and children's data get real protection. Payments run through a hosted, PCI-compliant provider so card details never touch the server; sign-in uses scrypt-hashed passwords; and the whole store is built to Israeli law — truthful scarcity, opt-in marketing, and PPL Amendment 13-aware consent.

◇PCI-compliant hosted payments
◇scrypt password hashing, token sessions
◇Consent-gated analytics (opt-in only)
◇Rate limiting on every auth path
◇Accessible — IS 5568 / WCAG 2.1 AA
◇Restore-tested automated backups

Want something like this?

Start a project