> For the complete documentation index, see [llms.txt](https://sitesbyseth.gitbook.io/sitesbyseth-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sitesbyseth.gitbook.io/sitesbyseth-docs/showcase/size-finder.md). # Smart size finder "Find my size" is Showcase's built-in size recommendation tool. The shopper enters their **height** and **weight**, picks how they like things to fit, and the theme calculates a size — adjusted for how *this specific piece* is cut, and snapped to the sizes the product actually comes in. No size-chart squinting, no app subscription. ## Where it appears Automatically, on clothing — there's no on/off switch. A product counts as clothing when any of these is true: * Its **product type** is an apparel word (t-shirt, hoodie, jacket, pants, dress, knitwear, swimwear, and \~30 more). * Any of its **tags** is one of those words. * It has an option named **Size** (also recognized: *Größe*, *Taille*). If a product that should have the finder doesn't, add a tag like `hoodie` or `clothing` — or make sure its size option is actually called "Size." The trigger is a small ruler-icon **"Find my size"** link above the size pills on every story screen (homepage, product page, collections). ## How the math works, in plain words The finder thinks like a good shop assistant: 1. **Build** — from height and weight it estimates how much *room* the shopper needs around the chest/waist. This is the main driver: alpha sizes (XS → XXXL) each cover a band of builds, and the bands get wider at the top end, just like real size curves. 2. **Length** — height alone also matters: taller bodies need longer garments. Tall-and-slim shoppers get pulled *up* a size so sleeves and hems are long enough; short-and-broad shoppers are pulled *down* only slightly, because the garment still has to fit around them. 3. **The piece's cut** — your **fit profile** setting shifts the result: a piece that runs small pushes the recommendation up, an oversized cut pushes it down a full size. 4. **The shopper's preference** — they pick **Fitted / Regular / Oversized** in the finder; that nudges the result again. 5. **Snap to reality** — the result lands on the sizes this product actually has. Standard labels are understood in many spellings (S, Sm, Small, 2XL, XXL…). If the product uses non-standard sizes (numeric, one-size ranges), the finder maps proportionally across them. The result screen shows the **recommended size**, a note about the cut ("This piece runs small — we sized you up."), and — when the shopper sits just below a size boundary — a between-sizes tip ("You're between sizes — take L for a roomier fit."). It even **pre-selects the recommended size pill** on the product screen, so the shopper can add to cart immediately. Nonsense inputs are rejected (height must be 120–230 cm, weight 30–250 kg — or the imperial equivalents), showing "Enter your height and weight" instead of a fake answer. ## Units: cm/kg and ft/lb The finder opens in metric with an **imperial toggle** (`in / lb`). Switching converts any value already typed. Imperial height uses a smart input: the shopper just types digits and the apostrophe appears by itself — typing `511` becomes `5'11`. No format instructions needed. ## Your two settings per piece On every story block, the product page, and the collection page, under **Find my size**: * **How does this piece fit?** — `Runs small — size up`, `Slightly snug`, `True to size` (default), `Slightly roomy`, `Oversized cut — size down`. Be honest here; this is what makes the finder *this piece's* finder rather than a generic calculator, and it writes the explanation note the shopper sees. * **Garment type** — `Top / tee / hoodie` (default), `Bottoms / pants`, `Outerwear / jacket`, `Dress / one-piece`. This sets how strongly height pulls the size: length matters a lot for dresses and tops, less for bottoms. 💡 On the **collection page** these two settings apply to every product on the page — set precise per-piece values on the homepage story blocks and the product page, and leave the collection page at `True to size` unless the whole collection shares one cut. ## The size chart image Each story block and the product page also take an optional **Size chart image**. When set, a **"View size chart"** link appears inside the finder window; tapping it swaps to the chart with a "Back to size finder" link. Upload your chart as one clean image (about 1400px wide) — measurements table, garment diagram, whatever you use. ## Good to know * Products with no size option still get the finder if they're tagged as clothing — the recommendation then uses the standard XS–XXXL ladder. * The fit-preference buttons recalculate live once a result is showing, so shoppers can compare "Fitted" vs. "Oversized" instantly. * The finder never blocks purchase — it's a helper link, and the size pills work exactly the same without it. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://sitesbyseth.gitbook.io/sitesbyseth-docs/showcase/size-finder.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.