# Krafthub Retail — store introduction

Updated 9 November 2026. Entry: `stores-refresh-frontend/review.html`.

## Purpose and content

Demo is the primary route. Hero: “SELL IN STORE. GET FOUND ONLINE.” The introduction focuses on the benefit: “The POS for yarn stores that helps crafters find their way to you.” Three numbered, clickable benefit rows replace the old four onboarding steps: mobile checkout, local discovery, and patterns delivered to the customer’s library. “Store” and “crafters” are used consistently.

The owner explicitly confirmed on 9 November 2026 that Tap to Pay, receipts and patterns delivered to customer libraries are ready for store use. This confirmation supersedes older prototype notes for marketing wording; this landing-page task did not audit the production services. No cash-register conformity, free service, monthly price, supported-device range, or existing POS integration is claimed.

The primary Book a demo action opens a 20-minute invitation with Eric. It explains the walkthrough and uses a prefilled email draft to eric@krafthub.art. Nothing is sent automatically and no appointment is confirmed by the page. The note invites the owner to bring an inventory export and discuss pricing and the move from their current system, without promising every export format is supported. Create store account remains secondary; login stays in the header. Both account destinations still use explicitly labelled preview dialogs until production URLs are supplied.

## Layout and product illustration

Preserves the two-column composition, large black typography, numbered rows and fine rules, lime primary action, original user-provided store photo and footer. The product illustration adds a restrained cream surface from the existing tokens. Below 960px the columns stack; very narrow screens stack the photograph above the product illustration.

The former second demo action is replaced by three manually selected views: At the counter, On the map, In their library. These are labelled illustrative screens, using example products and prices. They are HTML/CSS illustrations, not screenshots of the production app. No payment, barcode scan or account mutation happens inside them. There is no autoplay. The counter view also shows the customer-library connection and a static example address (alex@example.com); it is not an input and collects no customer information.

The 553 kr sale example consists of 474 kr yarn and a 79 kr digital pattern. These are illustrative product prices, not Krafthub subscription pricing. The map is schematic, not a geographic claim. The original shopper image is unchanged. The new yarn and sweater photos are copied from the existing supplier-onboarding assets without editing.

Tabs support click/touch, left/right arrows, Home/End, selected-state semantics and a single tab stop; captions update politely. The left benefit buttons and right tabs stay synchronized. Benefit buttons have native Enter/Space activation and descriptive text. On stacked mobile layouts, activating a benefit reveals and focuses the selected illustration, respecting reduced motion. The visual hint reads “See how it works”. All dialog close buttons and native Escape behaviour remain. The footer finder retains fictional examples and requests location only after an explicit click.

## Files and integration

Buildless HTML, `onboarding.css`, `onboarding.js`, shared `tokens.css` / `styles.css`, and `assets/`. The source ZIP contains the same page as `store-onboarding/index.html`.

Connect verified production login/account URLs during integration. Replace the illustrative product views with real product captures when available if desired. Keep the pricing discussion before stock import or paid activation. Production stock search, fiscal services and payments are outside this page’s implementation.

## Verification for this revision

JavaScript syntax, HTML structure, tab/label relationships, local asset references, sample arithmetic, mailto destination, terminology and source whitespace checked. Heading widths checked against the supplied font at representative 320–1920px widths. Keyboard/click tab transitions, synchronized benefit selection and mobile reveal behaviour checked with a lightweight DOM harness; this is not a real-browser interaction test. Dialog event handlers were inspected in the source.

The session previously denied browser access to the local preview. No alternative browser route was used to bypass it. Current visual rendering, device layouts and real-browser interactions remain unverified. Historical screenshots do not validate this revision.
