Skip to main content

CASE STUDY · PROPR

E-COMMERCE · FASHION

An online store.Tailored to measure.

A commerce platform built from scratch — catalog to checkout, in three languages, with same-day delivery.

PROPR is a premium loungewear and sleepwear brand: women's and men's collections, gifting, and packaging that is part of the product. The experience starts long before the garment is worn. A brand like that cannot live on a generic store template, so we built a dedicated commerce platform.

Onezero Labs owns the product end to end: design and UX, an SSR storefront, backend, catalog and inventory, cart and checkout, payments, a content management system, media infrastructure, localization, analytics and infrastructure.

languages
3
each with its own layout direction
cutoff
11 AM
Order by 11 AM — delivered today
checkout
3
Details, address, payment
templates
0
Built from scratch. No Shopify theme.

01 / Project overview

Before you wear PROPR,you experience PROPR.

The PROPR home page — a couple in striped pajamas, an announcement bar with the same-day delivery promise, and the women, men, about and gifting menu
livepropr.com · home

The brand is built on detail: micro-modal fabric, precise tailoring, the box, the ribbon. The site had to feel the same way — quiet, precise, free of noise — while doing the hard work of a real store: inventory, variants, card payments, region-based delivery, three languages and both writing directions. The shopping experience follows a few rules:

  • Typography and a cream ground before any effect
  • Large imagery, few words
  • Zero friction on the way to payment
  • The same experience in every language
  • A delivery promise shown on every page

02 / What we built

A complete commerce platform.Not a theme.

Instead of fitting the brand into the limits of an off-the-shelf platform, we built the platform around the brand. Every layer — from the storefront to the admin — was written for PROPR:

  • DESIGN
    Product design and UX
  • WEB
    React storefront with SSR
  • API
    Backend, API and data model
  • CATALOG
    Catalog, collections and variants
  • STOCK
    Inventory and sold-out states
  • CART
    Server-side cart
  • CHECKOUT
    Three-step checkout
  • PAY
    Secure payment integration
  • DELIVERY
    Region and cutoff delivery engine
  • CMS
    A dedicated CMS
  • MEDIA
    Media pipeline and responsive images
  • I18N
    Three-language localization
  • GROWTH
    Newsletter, discount codes and GTM
  • SEO
    SEO, performance and accessibility
  • INFRA
    Infrastructure, CDN and launch

03 / The challenge

Feel like a boutique.Run like a system.

A small luxury store has to meet the same standards as a large one, without an IT department. The system had to:

  1. Keep a boutique feel at online-store speed.
  2. Work in three languages, each with its own layout and typography.
  3. Manage color, size and stock without selling an item that just sold out.
  4. Promise same-day delivery by region and by order time.
  5. Take card payments securely, without card data touching our servers.
  6. Close for weekends and holidays, then reopen on its own.
  7. Let the brand team edit content, announcements and promotions without a developer.
  8. Stay fast and indexable — SSR, light images, schema.
  9. Enforce discount rules: first order only, single use.

04 / The solution

From the collectionto the door. One flow.

The journey is designed so every step leads to the next: browse the collection, pick a variant, cart, a three-step checkout and payment — then the promise is kept the same day.

  1. 01

    Choose a collection

    Signature, Grace, Allure, Sable, Poise.

  2. 02

    Open a product

    Gallery, fabric, care and a size guide.

  3. 03

    Pick color and size

    Stock is validated when the item is added.

  4. 04

    Review the cart

    A drawer opens with a free-shipping progress meter.

  5. 05

    Check out as a guest

    Details, address, then payment. No account required.

  6. 06

    Add the extras

    Discount code, gift note and a separate billing address — all optional.

  7. 07

    Pay inside the processor

    The card form runs in the payment provider's iframe.

  8. 08

    Confirm the order

    Confirmation email and shipping updates follow.

05 / Storefront and catalog

A product pagethat feels like the fabric.

The product is the hero: a large zoomable gallery, the name, the price, color and size, and tabs for fabric, care and the size guide. All of that content comes from the catalog, and every image is served in the size the screen actually needs.

  • CMS-managed collections and banners
  • Product gallery with zoom and image navigation
  • Color and size variants tied to stock
  • Sold-out and select-a-size states
  • Fabric, care and size-guide tabs
  • Responsive WebP images with blur placeholders
  • SSR, so every page is served complete to search engines and to people
  • Titles, descriptions and SEO per page and per language

06 / Cart and checkout

Three steps.Zero surprises.

The cart lives on the server, so stock, price and shipping stay correct even if the shopper comes back an hour later. Checkout is three clear steps, with a fixed order summary.

  • Server-side cart
    Expiry handling, including a clear state when the cart has expired.
  • Stock check on add
    If the last unit just sold, the shopper hears it immediately.
  • Free-shipping meter
    Shows how far the order is from the free-shipping threshold.
  • Guest checkout
    No account required.
  • Three steps
    Details, then address, then payment.
  • Delivery notes
    Shipping within the brand's market, with instructions for the courier.
  • Gift note
    A personal note that ships inside the box.
  • Billing details
    A separate billing address and invoice name, when needed.
  • Discount codes
    First order, single use, and error messages that say why a code failed.
  • Order lock
    Details freeze once the order is created.
  • Rate limiting
    Repeated attempts are slowed down.
  • Email updates
    Order confirmation and shipping status.

07 / Payments and security

The card nevertouches our servers.

The payment form runs inside the processor's iframe. Card number, expiry and CVV go straight to the acquirer. We only receive the outcome — approved or declined — and show it in a clear state. Development and QA run in sandbox mode with simulated charges.

  • Hosted payment iframe
  • Issuer-decline handling
  • Encrypted checkout
  • Sandbox for development and QA
  • Rate limiting and audit
  • Terms and privacy consent before payment
  • Cloudflare at the edge

08 / The delivery promise

Order today.Delivered today.

That promise is the heart of the brand, so it is not static text. The delivery engine knows the time, the address and the calendar, and shows the right message in the announcement bar, on the product page and in checkout.

  • Before 11 AM — arrives today, in eligible areas
  • After 11 AM — the next business day
  • Remote areas — a longer window, up to several business days
  • Shipping fee and the free-shipping threshold are managed in the CMS
  • Weekend and holiday closure windows, with a pause message on the store
  • The store reopens on its own when the closure ends
  • The same rules in every language
  • Email updates on package status

09 / Three languages, one store

The same store.In every language.

Localization here is not a string swap. It is writing direction, layout, typography, currency and URLs. Every language gets its own path, hreflang and canonical, and every text — from buttons to error messages — comes from a managed dictionary.

  • Three languages, each with its own layout direction and typography
  • A dedicated URL path per language
  • Automatic hreflang and canonical tags
  • A mirrored layout: menu, cart and gallery
  • A managed UI dictionary per language
  • Content, SEO and announcements per language
  • One currency, shown the same way in every language
  • A language switcher that remembers the choice

10 / Content management

The brand manages.No developer required.

Everything that changes often was moved out of the code into a dedicated management system. Pages are composed from sections, the catalog lives beside the content, and operational settings — shipping, announcements, popups, closure windows — are edited without a deploy.

  • Section-based pages: rich text, collection banners
  • Catalog: products, variants, stock, prices
  • Navigation and footer
  • Announcement bar
  • Newsletter popup and triggers
  • Shipping: fee, free threshold, regions
  • Weekend and holiday closure windows
  • UI string dictionary
  • SEO and social images per page
  • Media library with automatic renditions

11 / Marketing and growth

A first orderstarts with a personal invitation.

The marketing layer is wired into the product. A newsletter signup generates a personal discount code at the configured percentage, the popup opens on engagement rather than a blind timer, and measurement runs through Google Tag Manager with cookie consent.

  • Newsletter via Klaviyo
  • A personal first-order discount code
  • Popup triggered by active time on site
  • Google Tag Manager
  • Cookie consent
  • A dedicated gifting page
  • Open Graph tags for sharing

12 / Performance and infrastructure

Heavy imagery.A light site.

A fashion site lives on large photography, which is exactly what slows sites down. The media pipeline generates WebP renditions in several widths plus a blur placeholder for every image, then serves them through a CDN.

  • SSR and hydration
    Content is on the page before the app boots.
  • Per-route code splitting
    Each page loads what it uses.
  • WebP renditions
    640, 1280 and the original.
  • Blur placeholders
    No layout jump while images arrive.
  • CDN and analytics
    Cloudflare in front of the site.
  • Cloud media storage
    Images stored once, served close to the shopper.
  • Self-hosted fonts
    No extra round trip for type.
  • Prefetch
    Likely next pages start loading early.
  • Branded errors
    404 and error pages stay in the brand.

13 / The outcome

A store that looks like the brand —and runs like a system.

PROPR launched on a commerce platform of its own: a storefront in three languages, a catalog with variants and stock, cart and checkout, secure payments, a delivery engine that understands time, region and calendar, and a management system that keeps control with the brand.

The infrastructure can take new collections, languages, payment methods and markets without a rebuild, and without giving up the detail.

14 / Technology and capabilities

What's under the fabric

Every layer was built for real commerce: fast, secure, multilingual and ready for the next collection.

  • WEB
    React storefront with SSR
  • API
    Backend and API
  • CATALOG
    Catalog, variants and inventory
  • CART
    Server-side cart
  • CHECKOUT
    Three-step checkout
  • PAY
    Hosted payment iframe
  • DELIVERY
    Delivery engine and closure windows
  • PROMO
    Discount codes and usage rules
  • I18N
    Three languages, one codebase
  • CMS
    Dedicated CMS
  • MEDIA
    Media pipeline and WebP
  • GROWTH
    Klaviyo and GTM
  • SEO
    SEO, hreflang and schema
  • INFRA
    Cloudflare and cloud storage
  • A11Y
    Accessibility and localization
  • CICD
    QA and continuous delivery

Stack

  • E-commerce
  • Built from scratch
  • SSR
  • Same-day delivery
  • 3 languages
  • Server cart
  • Secure checkout
  • Hosted payments
  • Custom CMS
  • WebP pipeline
  • Klaviyo
  • Cloudflare

Got a similar idea?

When the templateis too small for the brand.

Onezero Labs builds commerce platforms for brands that want full control over the experience — from design, through catalog and payments, to delivery. If Shopify is no longer enough, or never fit, let's talk.

Not a template. A store tailored to the brand.