Aislepoint POS — Retail, Grocery & Mini-Mart POS Software Website (Frontend + Backend)

8 pages and a real lead-capture backend — this is a DYNAMIC website for a retail / grocery / mini-mart POS software company: every product page (features, checkout & loyalty, inventory, WhatsApp, pricing, FAQ) is static editorial content with HTML/CSS product mockups, while the "Book a Demo" form writes to your own database in real time. Design: forest green + lime + tangerine, Space Grotesk + DM Sans, hard-offset "sticker" shadows, zig-zag receipt paper, barcode stripes and a bento dashboard hero built in HTML — no screenshots to replace. 1. Home (index.html) — bento hero (basket scan, low-stock alert, loyalty, payments), feature ticker, 6 feature cards, stats, an interactive product catalogue (12 photo products, category chips, barcode search, live receipt), checkout receipt, stock table, WhatsApp, testimonial. 2. Features (features.html) — all 11 features: barcode scanning, SKU management, stock in/out, purchases & suppliers, low-stock alerts, returns & refunds, discounts & promotions, loyalty, cash/card/digital payments, manpower & expense entry, WhatsApp invoices & notifications. 3. Checkout & Loyalty (checkout.html) — scanning basket, payments / returns / promotions, loyalty tiers, a print-ready 80mm receipt. 4. Inventory (inventory.html) — stock table, supplier purchase order, alerts, manpower & expenses, daily profit summary. 5. WhatsApp (whatsapp.html) — invoice / order / ready / offer messages with phone mockup. 6. Pricing (pricing.html) — 3 plans and comparison table. 7. FAQ (faq.html) — 10 questions. 8. Book a Demo (demo.html) — the real demo request form. WHOSE DATABASE, WHOSE EMAIL PROVIDER. Yours, not this platform's. Before anything here does something real: 1. Create a Postgres database anywhere you like — Vercel Postgres, Supabase, Neon, or your own server — and run schema.sql against it once. 2. In your Vercel project's Settings -> Environment Variables, set: DATABASE_URL your database connection string RETAIL_DEMO_REQUESTS_ADMIN_KEY any secret string you choose Optional, for automatic email confirmations on new requests: RESEND_API_KEY from your own Resend (resend.com) account RETAIL_DEMO_REQUEST_FROM_EMAIL an address on a domain verified in that account Without the two optional variables set, requests still save correctly — no confirmation email sends, that's all. MANAGING DEMO REQUESTS. Once published, this purchase's library page shows a "Manage live data" panel — paste in your RETAIL_DEMO_REQUESTS_ADMIN_KEY to see every demo request as it comes in, mark it contacted, and delete ones you've handled. MANAGING YOUR PRODUCTS. The same "Manage live data" panel has a second table for the Home page catalogue (retail_products, served by api/retail_products.ts). With the same admin key entered, add, edit and delete your products: name, category, price, a short description line, an optional badge, and a photo uploaded straight from your computer (resized in your browser and stored in your own database, so there's no separate file storage to set up). While the table is empty the catalogue shows its built-in samples; as soon as you add your first item, your list replaces them. Your categories become the filter chips, and prices use the currency symbol already written on the page. Changes appear on the live site on the next page load, with no republish needed. SPAM PROTECTION. The demo form includes a hidden honeypot field real visitors never see or fill — checked both client-side and in api/retail_demo_requests.ts; filled submissions are accepted but silently discarded. WHAT YOU CAN CUSTOMIZE, HONESTLY: - Every page's copy, prices, mockup contents, images and layout — through the same AI-guided editor as any other template, no coding. - One optional field at a time on the "retail_demo_requests" resource (for example, "number of SKUs" or "current POS"), through the "Backend customization" panel once purchased. - The POS screens on this site are marketing mockups, not a working POS. Building real checkout, stock sync, payments or WhatsApp sending isn't something the editor automates — every purchase includes the full source code so you or a developer can extend it. INTERACTIVE CATALOGUE & 80MM PRINTING. The Home page product catalogue really works in the browser: tap products to build a basket, filter by category, search by name or barcode, remove lines, and press "Print receipt · 80mm". The Checkout & Loyalty page has a print-ready sample receipt with its own Print button. Both open the browser print dialog with a page exactly 80 mm wide (72 mm printable, black monospace, height sized to the receipt) — select your thermal receipt printer and its 80mm roll paper size, margins none. Product names, prices, barcodes and categories are ordinary text you can edit; the cart reads them straight from the page, and VAT comes from the "5%" on the receipt. Sales rung up here are a demo, not a connected POS: the cart itself stores and sends nothing. PREVIEW LIMITATION. The demo form calls a real endpoint that only exists once deployed — this platform's preview has no backend, so it shows a friendly "try it once deployed" message here. That's expected. The catalogue shows its built-in samples here for the same reason. CLAIMS & COMPLIANCE. Statistics, prices, store counts and the testimonial are realistic placeholders — replace them with your own verified figures before publishing. The announcement strip offer ("free barcode scanner") is placeholder copy — change or remove it. WhatsApp claims assume the WhatsApp Business Platform with customer opt-in. The product name, stores and people named are fictional. IMAGES. All photography is real, licensed-for-web Unsplash stock, self-hosted under /content-images. The checkout photo constant (IMG.checkout) depicts identifiable people and is not used on any page by default — if you add it, replace it before commercial use (right-of-publicity, not copyright). All other photography shows products, shelves and hands only and may be kept as-is.