Can I vibe code Kiwi Sizing?

kiwisizing.com·size-recommendations·$7/mo·tiered

CLONE — YOU CAN REBUILD THE FEATURE

Kiwi Sizing charges a recurring subscription for static table rendering and basic user-input fit matching. The core feature—showing a modal with garment dimensions and dynamically converting inches to centimeters—requires minimal JavaScript and a clean CSS layout. Their AI recommendation feature collects customer body inputs (height, weight, age) and maps them to standard body measurement distributions before matching against the product's dimension matrix. Unless you need out-of-the-box size templates for hundreds of third-party apparel brands, building this natively via Shopify Theme App Extensions or simple Alpine.js modals eliminates the software dependency entirely.

Share X LinkedIn

The verdict

CLONE

Replaces

$15/mo

Vibe code score

7/10

MVP build time

1 weekend

Full replacement

2 weeks, including Shopify Theme App Extension and JSON metafile integration

Editorial opinion, produced with a published methodology from public information. Not a statement of fact about the vendor. How we score · Report an error · Pricing checked 2026-09-03

01

Why this verdict

Displaying measurement tables and toggling unit conversions on product pages is trivial frontend work. The fit recommendation engine can be built using standard mathematical interpolation or simple heuristic matching against garment specs stored in product metafields.

Verdict

CLONE

Vibe code score

7/10

Moat strength

1/10

02

What it really costs

Sticker price versus what a real store ends up paying.

Entry$7/moTypical store$15/mo≈ estimated · 2026-09-03
Freefree / quote2 size charts, standard table layout
Premium$7/moUnlimited size charts, unit conversion, layout customizer
Ultimate$15/moAI fit recommender engine and custom sizing rules

Billed monthly based on active size charts and access to advanced recommendation features.

Where this number comes from
Captured
2026-09-03 (21 days ago)
Verified by
crawler

Assumptions: Billed monthly based on active size charts and access to advanced recommendation features.

03

The one-shot build prompt

Paste it into your agent of choice. Nothing else needed.

The one-shot build promptbuild it on Lovable
Build a lightweight, self-hosted Size Chart and Recommendation engine for a Shopify store as a Theme App Extension.

1. DATA STRUCTURE
- Define a Shopify Product Metafield namespace `custom.size_chart` containing JSON data:
  - `unit_default`: "in" or "cm"
  - `measurements`: Array of objects containing `size` (string), `chest` (min/max object), `waist` (min/max object), `hip` (min/max object).
  - `fit_type`: "slim", "regular", or "oversized".

2. FRONTEND WIDGET (VANILLA JS / ALPINE.JS)
- Inject a "Size Guide" button adjacent to the variant selector on product pages.
- On click, open an accessible modal containing:
  - A toggle switch for units (Imperial/Metric) that dynamically recalculates values using 1 inch = 2.54 cm.
  - A clean HTML table displaying garment dimensions per size.
  - A tab to switch to the "Fit Recommendation Calculator".

3. FIT RECOMMENDATION LOGIC
- Questionnaire steps: Gender, Height, Weight, Preference (Tighter, Standard, Looser).
- Estimate body specs using standard BMI body ratio baselines if exact body measurements are not provided.
- Match the calculated chest/waist targets to the stored `custom.size_chart` ranges.
- Output a clear recommended size with a confidence percentage and explanation (e.g., "Based on your inputs, size Medium will fit standard. Size Large for a looser fit.").

4. PERFORMANCE AND STYLING
- Script size must remain under 15KB gzipped.
- Zero external CSS dependencies; rely on web components or scoped Shadow DOM styles matching theme CSS variables.
- Load asynchronously without triggering Cumulative Layout Shift.

5. OUT OF SCOPE
- External admin portal (all charts must be configured via standard Shopify Product Metafields).
- PDF processing or vision-based scanning.

$ each button prefixes agent-specific run instructions · build your own product, never copy proprietary code, trademarks or designs

04

Scorecard

Deterministic scoring, same method for every product.

Vibe code score

7/10

Moat strength

1/10

Technical difficulty3/10
Operational burden4/10
Integration depth2/10
Data advantage3/10
Network effects1/10
Compliance load0/10

05

What you keep, what you lose

The honest trade of rebuilding it yourself.

What you can actually replace

  • Interactive size chart modals with automatic unit conversion (in/cm)
  • Rule-based chart assignment by product tags, collections, or vendor
  • Basic body-measurement fit recommendation questionnaire
  • Customizable HTML/CSS table layouts for store branding
  • Multi-language translation support for table headings

What you lose

  • ×Pre-populated sizing templates for standard third-party apparel brands
  • ×Visual drag-and-drop table editor in a dedicated admin interface
  • ×Aggregated sizing benchmark data across external merchants
  • ×Automatic extraction of size charts from imported images or PDFs
  • ×Built-in analytics dashboards tracking chart views and sizing drop-offs

06

Why people still pay — the real moats

Moats

  • Cross-merchant measurement data used to fine-tune fit heuristics
  • Zero-code table creation interface for non-technical marketing teams
  • Turnkey theme compatibility without touching liquid templates

Hard parts

  • Designing responsive, accessible web components that do not cause Cumulative Layout Shift (CLS)
  • Structuring structured JSON schemas inside store metafields to handle multi-variant garment sizing
  • Writing precise interpolation algorithms to handle edge cases between discrete sizes (e.g., Medium vs Large)
  • Ensuring theme script injection runs asynchronously without slowing down First Contentful Paint (FCP)
  • Manually populating and updating garment dimension arrays across a broad product catalog
  • Handling customer support when body variance causes inaccurate automated fit suggestions
  • Maintaining custom UI styling across major theme updates or frontend migrations
  • Validating garment tolerances when suppliers update raw physical manufacturing specs

Build this instead

Shopify Metafield Chart Renderer

Store garment measurement JSON directly in Shopify Product Metafields and render them via a native Theme App Extension using vanilla JS.

Build this instead

Rule-Based Fit Calculator

Create an inline Alpine.js step form on the product page that compares user inputs against product measurement thresholds.

Build this instead

Headless Size Matrix API

Deploy a lightweight Cloudflare Worker that accepts body parameters and returns exact size matches based on configured store rules.

07

Prior art — do not start from zero

Existing projects and paid alternatives worth pricing first.

08

Open source alternatives to Kiwi Sizing

Self-hostable projects that cover most of the same ground. Free licence, your infrastructure, your on-call.

09

Have you actually replaced it?

One click, no account. It moves the ranking.

Community verdict

share on X ↗
Successful
0
Failed
0
Success rate
no data yet
Spend killed
$0/mo

10

Compare

Same category, different trade-offs.

11

FAQ

+Can I really replace Kiwi Sizing with an AI-generated app?

YES — IT IS A CONDITIONAL MODAL WITH A REGRESSION FORMULA. Displaying measurement tables and toggling unit conversions on product pages is trivial frontend work. The fit recommendation engine can be built using standard mathematical interpolation or simple heuristic matching against garment specs stored in product metafields. An MVP takes roughly 1 weekend; matching the product properly is closer to 2 weeks, including Shopify Theme App Extension and JSON metafile integration.

+How long does it take to rebuild Kiwi Sizing?

A usable internal version: 1 weekend. A version you would sell or bet a business on: 2 weeks, including Shopify Theme App Extension and JSON metafile integration, mostly spent on designing responsive, accessible web components that do not cause cumulative layout shift (cls).

+What do you actually lose by leaving Kiwi Sizing?

Pre-populated sizing templates for standard third-party apparel brands Visual drag-and-drop table editor in a dedicated admin interface Aggregated sizing benchmark data across external merchants

+Is it legal to build a Kiwi Sizing alternative?

Building a competing product with your own code is normal competition. Copying their code, trademarks, brand assets or scraping their platform is not. Use the prompt to build your own implementation of common features.

Written by EcomReStack research agent18 years in the Magento ecosystem. Last reviewed 2026-09-03.

Sources consulted

Scores are computed, not typed. Read the methodology.

One e-commerce SaaS teardown every week.

Honest verdicts, build prompts and overlooked vertical SaaS opportunities. No tracking pixels, no drip sequence, unsubscribe in one click.

free forever · no third-party tracking · the prompts stay public