Freshfold POS — Laundry & Dry Cleaning POS Software Website (Frontend + Backend)

8 pages and a real lead-capture backend — this is a DYNAMIC website for a laundry & dry cleaning POS software company: every product page (features, order tracking, WhatsApp, billing & customers, 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: airy ice-blue and cobalt/aqua palette, Plus Jakarta Sans, soft rounded "bubble" cards, a five-stage status pipeline and punched garment tags built in HTML — no screenshots to replace. 1. Home (index.html) — centered hero with app mockup and WhatsApp toasts, stats, bento feature grid, an interactive price-list catalogue (12 garment/service tiles, category chips, search, live drop-off slip), order flow, WhatsApp, delivery, reviews. 2. Features (features.html) — 10 feature cards: customer registration, garment entry & tagging, status tracking, pickup/drop-off, item-wise pricing, express/regular, delivery, WhatsApp notifications, WhatsApp invoices, outstanding balances. 3. Order Tracking (tracking.html) — garment tags, Received -> Delivered status board, pickup & delivery route list, express service. 4. WhatsApp (whatsapp.html) — phone mockup with status updates and PDF invoice, reminders, setup steps. 5. Billing & Customers (billing.html) — item-wise price list, a print-ready 80mm invoice, outstanding balance ledger, customer registration. 6. Pricing (pricing.html) — 3 plans and comparison table. 7. FAQ (faq.html) — 10 grouped 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 LAUNDRY_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 LAUNDRY_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 LAUNDRY_DEMO_REQUESTS_ADMIN_KEY to see every demo request as it comes in, mark it contacted, and delete ones you've handled. MANAGING YOUR PRICE LIST. The same "Manage live data" panel has a second table for the Home page catalogue (laundry_products, served by api/laundry_products.ts). With the same admin key entered, add, edit and delete your garment and service prices: 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/laundry_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 "laundry_demo_requests" resource (for example, "orders per day" or "current system"), through the "Backend customization" panel once purchased. - The POS screens on this site are marketing mockups, not a working POS. Building real order tracking, WhatsApp sending, payments or a customer portal isn't something the editor automates — every purchase includes the full source code so you or a developer can extend it. INTERACTIVE PRICE LIST & 80MM PRINTING. The Home page price-list catalogue really works in the browser: tap garments to build a drop-off slip, filter by category, search, remove lines, and press "Print receipt · 80mm". The Billing page has a print-ready sample invoice 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 slip) — select your thermal receipt printer and its 80mm roll paper size, margins none. Item names, prices, categories and the slip header are ordinary text you can edit; the cart reads them straight from the page, and VAT comes from the "5%" on the slip. 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, customer counts and reviews are realistic placeholders — replace them with your own verified figures before publishing. WhatsApp claims assume the WhatsApp Business Platform with customer opt-in. The product name, businesses and people named are fictional. IMAGES. All photography is real, licensed-for-web Unsplash stock, self-hosted under /content-images. No photo shows an identifiable face; all may be kept as-is or replaced at your discretion.