When on, the app forces a starting-cash count the first time it opens each day, and a cash count at close — neither can be skipped. Turn off only if you don't run a cash drawer.

Hours are 0–23 (e.g. 7 = 7am, 19 = 7pm). The morning open is asked on the first login of the day; the close-out is forced once the clock passes the close hour. Each morning suggests last night's counted cash — or this default float if there's no prior close.

Turns on the tools for each kind of business. Laundromat adds Quick Sale and Inventory (stock levels, restocks, low-stock alerts). Pickup & delivery is the routes switch for the whole store: off hides the Route screen, routes and route customers, drivers, delivery orders and the route reminders.

Delivery tickets then pick a slot; a full slot can't be picked. The slot is the stop's time window on the Route screen and in the driver app, and the route optimizer visits the earlier windows first. Leave empty for no slots.

The Route screen's map needs a tile provider. OpenStreetMap's own servers are donated community infrastructure — their usage policy doesn't cover apps like this one, and they return 403 Forbidden once they flag you.

Esri works with no sign-up and is the default. But the free keyless endpoints are a courtesy, not a commitment — Carto used to be one and now stamps API KEY REQUIRED across every tile. For a shop running deliveries daily, spend two minutes on a free MapTiler or Geoapify key: those are provisioned for app use and won't be pulled out from under you mid-route.

Check the preview below before you save — a provider that has started refusing or watermarking tiles shows it here rather than on the road.

Example: 1 point per $1 spent, worth 5¢ each — 100 points redeems for $5.00 store credit. Store credit works even when loyalty is off.

Members pay monthly at the counter (Customers → profile → Collect). While paid up they get the discount on every ticket and no delivery fee. The delivery fee goes on delivery tickets automatically; 0 = free delivery for everyone. Price changes apply to new members; current members keep the price they joined at.

Codes apply from Add discount → Promo / referral code, or typed / scanned into the New Order item search. Uses and revenue are counted from the tickets that used each code. A code used in a Marketing automation is tracked here too once you add it.

Every customer's code is on their profile (REF + customer number). The referrer gets the credit when the new customer's first ticket is saved.

Customers who pass either threshold get a “Suggested VIP” prompt on their profile. VIP is a recognition badge — it does not auto-apply a discount.

Texts go through a small backend (a Supabase Edge Function, send-sms) that holds your Twilio keys. Your Twilio Auth Token never lives in this app. The URL and shared secret below are already filled in — just deploy the function, then tick Enable and untick Mock. Keep “mock” on to preview messages without sending. Full steps: SUPABASE-MESSAGING-SETUP.md.

Provider keys stay on your backend function. This app only sends customer, ticket, and message payloads. Email uses a separate Supabase Edge Function, send-email, which sends through your Hostinger mailbox (SMTP) — see SUPABASE-MESSAGING-SETUP.md.

Every message this app sends by itself, and the exact words. Order notices are service messages: they go to a customer even without a marketing yes, ignore the one-a-day marketing limit, and quiet hours (9pm to 8am) only delay them. Promotions need the customer's yes and always end with how to stop. Check the wording with your lawyer: texting and email rules differ by state.

Texts: a customer who replies STOP is switched off for texts at once. Emails: the unsubscribe link in every promotion carries that customer's own code (?u=CODE, or put {token} in the address); your unsubscribe page passes it to the app, which switches that customer off. Until the page exists, the link opens a mail to your reply address.

A cashier is stopped by the rules below and a manager types a PIN. The window shows what is being approved. A manager or owner who is signed in is not asked, but the action is still written to the log. Press Save settings at the bottom to keep your changes.

Take a business's customers (with store credit and points), orders and payments, prices and safe settings out as one zip file, or bring such a file (or an older backup) into this business. Nothing is ever copied between businesses on the server: the file goes from the owner of one to the owner of the other. You see what will happen before anything is written, and nothing here is overwritten.

Export the price list or the customer list from Spot, CleanCloud, Compassmax or a spreadsheet as a CSV file (first row = column names), then choose it here. A price list needs an item name and a price column, and usually a category. You see what will happen before anything is saved. Customers already here (same phone or email) are never overwritten, and nothing is ever deleted.

Data is stored in this desktop app first. Export backups regularly, or enable cloud sync with database/ezpos-supabase-schema.sql.

The POS keeps your tickets in this browser's storage. This asks the browser not to clear it when the disk runs short.

Customers tap, insert or swipe their card on a card reader at this store (Stripe WisePOS E or Reader S700). Card details go from the reader to Stripe: this POS never sees them. Needs the internet; cash keeps working without it.

Receipts should print by themselves, with no print window. That needs the POS opened from its desktop icon (made by SETUP-TILL.bat) and the receipt printer set as the Windows default printer.

Pick a folder once and a backup file is saved there every day, so clearing the browser or losing this profile does not lose your tickets and cash. Chrome and Edge only.

Fills the app with ~6 months of sample customers, receipts, and payments (about $10k collected per month) so you can explore reports and screens. Every demo record is tagged and can be cleared again.

Edit item names, prices, piece counts, pictures, and which items show at the counter.

ezcleanersplus.com and this POS share one Supabase project. Nothing to paste or configure here:
• Pickup requests from the website land in Orders → Web Bookings. "Start Order" finds or creates the customer.
• Website accounts have their own page: Web Members in the menu. Customers start, switch, pause and cancel their own wash & fold plan online (paid by card through Stripe). No approval is needed. Their plan is copied onto the linked POS customer automatically, so member pricing and the pounds meter work at the counter.
• Customers see their tickets (Received → Ready) on their website account once this terminal syncs.
Needs cloud sync plus a staff cloud login (Settings → Cloud Sync), because customer data is staff-only.

Send account link (on each customer's profile and after checkout) emails or texts the customer a one-tap link that opens their ezcleanersplus.com account already signed in: live order status, plan, card on file and preferences. It replaces the old "Customer view" and "Live link". Needs cloud sync and a staff cloud login.

Cards are handled by Stripe. This app never sees a card number.
• Customers add or change their card themselves on their website account (Billing tab), and monthly plans bill that card automatically.
• To charge a saved card for a one-off job, or to send an invoice, use Bill a customer.
• To send someone a link to start a wash and fold plan, use Membership sign-up text.