Point of Sale (POS)

Unlike a generic retail register, Brilloo’s POS is built around car wash services, branch pricing, and the customer journeys you already manage in the dashboard. Every completed sale can reinforce loyalty rules you configured and feeds reporting you see in analytics.

Key points

• Checkout uses your company and branch service catalog (including add-ons where you offer them).
• Sales are attributed to the branch where the register session runs.
• Customer identity can be attached to a sale so visits and rewards align with the right profile.
• Reservation details can be reconciled with in-person checkout so online bookings and lane sales stay in sync.
• Managers and owners still oversee configuration, users, and reporting from the business dashboard.

What staff see at checkout comes from how you set up services in Brilloo. Branch-level overrides and company-wide services work together so each location sells the right wash packages and prices.

Example: Lavado Bronce and Lavado Premium show “buy 5, get 1 free” and an Active status.

Example: Centro has 2 active services and Montejo has 3.

Key points

• Define base services and options before expecting a smooth lane experience—unclear catalogs slow staff and confuse totals.
• If a service is disabled for a branch, it should not appear for that location’s POS.
• Price changes roll out based on how your catalog is scoped (company vs branch); communicate updates before shift change.
• Add-ons and bundles should match what your team actually delivers to avoid refunds and voids.
• Keep naming consistent between the customer booking app and POS so customers recognize what they purchased.

Packages let you sell multiple services or add-ons as a single item with special pricing. Staff select the package at checkout, and the system tracks stock (if configured) and applies vehicle type restrictions automatically.

Key points

• Create packages per branch with bundled services and pricing—staff see them alongside individual services at the POS.
• Set vehicle type restrictions (sedan, SUV, truck, etc.) so packages only appear for eligible vehicles.
• Track inventory of package components (retail products) when stock is configured at the branch.
• Package sales appear in reporting just like individual services, making it easy to measure bundle performance.
• Only owners and branch managers can create or edit packages; cashiers can sell them at checkout.

Owners and branch managers can create branch promotions that apply automatically at checkout when the cart includes the required services or products and the schedule matches. Staff do not configure promotions—they only see the discount on the ticket.

Example: “Martes a mitad de precio” is active at 50% on Tuesdays and requires standalone Lavado Bronce, not a package.

Key points

• Choose a percent or a fixed amount, then pick the services or retail products that must be in the cart.
• Schedule by date range, weekdays, or days of the month. Date-range promos activate and expire automatically.
• Packages do not count toward the required items—customers must add matching à la carte lines.
• The register picks the best matching promo for the cart; the ticket shows the savings.
• Only owners and branch managers can create, pause, or edit discounts.

Company-level membership plans are sold at the register to a real customer, then redeemed later as $0 washes. There is no auto-renewal: buying again issues a new membership number.

Example: “Membresía Lavados Premium” lasts 1 month and can be sold at any branch where the service is active.

Example: At Centro, membership MBR-2608-00001 has 9 of 10 washes left. Later redemptions ring up at $0.

Key points

• Create plans with catalog services, validity, company or sold-at-branch redeem scope, and limited or unlimited allowances.
• Staff and managers can create a customer at checkout (name and phone; email if you will send the card).
• After payment, print the card or send it by email and/or WhatsApp. The sale still completes if a channel fails.
• Membership sales count as revenue that day. Later redemptions are $0 and do not move the cash drawer.
• Customers see remaining washes under My memberships. Loyalty and promos do not apply to covered services.

Exact screens can evolve, but the mental model for staff is: start a sale, build the line items, confirm the customer when possible, take payment, then finalize or print the ticket.

Example: Counter customer, sedan, Centro branch: Lavado Bronce $100, discount −$50, total $50 in cash.

Key points

• Start a new sale when a vehicle reaches the pay station or counter.
• Add line items from the catalog; adjust quantity or packages per your policies.
• Attach the customer when you can (search by phone, email, or name) so the visit counts toward loyalty.
• For booked customers, align the sale with the reservation when your workflow supports it so status and revenue stay accurate.
• Collect payment using the methods your business accepts; confirm the total before completing.
• Complete the sale to generate a ticket or receipt record staff and customers can refer to.

Not every sale needs a full customer profile. Brilloo's POS defaults to a Counter customer (no profile) with a vehicle type for washes—and you can add several washes on the same ticket.

Example: Sedan/compact at Centro. The sale does not earn loyalty or send notices until you attach a customer.

Key points

• Start a sale without attaching a customer profile when speed matters more than loyalty tracking; pick the vehicle type for washes.
• Add more than one service (or quantity greater than 1) on the same walk-in ticket.
• Loyalty coupons require a linked customer profile and apply to the first matching service unit.
• Walk-in sales still generate tickets and feed into branch revenue reports.
• For loyalty-conscious businesses, train staff to encourage profile creation so repeat customers get credit.

The POS records what was charged and how it was paid. Your broader payment setup (e.g. cards, transfers, cash) depends on your Brilloo billing and any connected processors—train staff on which tender types you allow at each site.

Key points

• Always verbalize the total and payment type to reduce tender errors during rush periods.
• Split or partial payments follow your internal policy; document exceptions for the manager.
• If a customer disputes a charge, locate the sale in history before issuing a void or adjustment.
• Card-present vs manual entry rules depend on your processor—follow PCI-conscious habits your provider requires.
• Keep tips, fees, and wash packages clearly separated in notes if your accounting team expects it.

Each business operates in one company currency for services and POS: MXN, USD, COP, ARS, CLP, PEN, GTQ, HNL, or EC. Tickets and reports display that currency. Brilloo subscriptions are billed in MXN (Mexico) or USD (every other company currency).

Key points

• Set company currency during onboarding or while the business is still on a free trial; after trial it is locked.
• Customers see consistent pricing whether they book online or pay at the counter.
• OXXO and SPEI are available for Brilloo subscriptions in MXN only.
• Do not expect a different POS currency per branch—currency is company-wide.
• Unknown or missing currency in the UI falls back to MXN.

Completed sales become part of your branch history. That audit trail helps resolve customer questions, train staff, and support finance reviews.

Example: Counter-customer tickets at Centro and Montejo are listed with date, branch, and payment method.

Key points

• Tickets should identify branch, time, line items, and payment summary.
• Managers can review recent sales to spot pricing mistakes or training gaps.
• Customers may ask for a duplicate receipt—use the documented reprint or share flow your location adopts.
• Sale history complements analytics; spikes or drops often trace back to POS discipline.
• Align ticket numbering or IDs with any external cash drawer protocol you use.

Car washes still move a lot of cash. Brilloo supports structured close-out routines so owners compare expected cash to actual drawer counts. Mid-day partial cuts (drops to the safe) are justified on the final cash cut. Voids and adjustments should be permission-gated and rare.

Example: Centro, 22 Sep 2026: opening float $20. Memberships sold are listed separately, and redemptions do not move drawer cash.

Example: Centro has $20 available to withdraw. Recording the cut does not change the day’s sales.

Key points

• Run cash cuts at consistent times (shift change, end of day) so reporting stays comparable.
• Use partial cuts during the day to move cash to the safe; they do not change the day’s sold total.
• Only trusted roles should void, register partial cuts, or close the day—document the reason.
• Investigate repeated voids on the same employee or SKU as a training or fraud signal.
• Escalate large discrepancies before signing off the day.

Brilloo’s value is one story for the customer: they may book on the web app and pay at the POS, or walk in without a reservation. Staff should know how to recognize an arriving booking and convert it cleanly to a completed sale.

Key points

• Confirm the reservation window and vehicle details when linking a booking to checkout.
• If a booking no-shows, follow your policy for releasing the slot and recording revenue.
• Walk-ins should still attach a customer profile when possible for loyalty continuity.
• Late arrivals may need schedule adjustments—coordinate with the lane before promising times.
• Communication templates (email/push) complement what happens at the POS; keep messaging consistent.

Loyalty rules you configure (for example progress toward a free wash) depend on accurate visit tracking. The POS is often where qualifying purchases are confirmed.

Key points

• Explain to staff how a completed sale qualifies—or does not qualify—for progress.
• Redeeming a free or discounted reward should follow a clear manager-approved flow.
• If loyalty is scoped per branch vs company-wide, train teams to set customer expectations.
• Partial services or comps may need manual policy so loyalty stays fair.
• When something looks wrong, compare POS history with the customer profile before overriding.

Not every employee should change prices, void sales, or close the day. Map Brilloo roles to your real-world responsibilities and refresh training when you add services or promotions.

Key points

• Cashiers need fast catalog fluency; leads need override and exception tools.
• Owners and branch managers configure packages, discounts, inventory, voids, cash cuts, and partial cuts; staff checkout only.
• New hires should shadow a full cash cut before doing it alone.
• Document your wash’s SOP for busy Saturdays vs quiet weekdays.
• When permissions change, verify the employee logged out and back in so updates apply.

Lanes do not always have perfect Wi‑Fi. Brilloo is designed with real-world connectivity in mind; when offline modes apply, your job is to avoid double-charging and to sync as soon as the connection returns.

Key points

• Post clear signage when card terminals are down and you are cash-only.
• Never assume a sale synced—confirm pending states if the UI shows them.
• After an outage, reconcile queued actions before the next busy rush.
• Report repeated dead zones to leadership; mesh or LTE fallback may be cheaper than lost sales.
• Backup power for routers and terminals matters as much as the wash equipment.

A short leadership routine keeps POS data trustworthy for finance, marketing, and loyalty.

Key points

• Review yesterday’s cash variance and top void reasons.
• Spot-check three random tickets against lane notes or camera.
• Confirm today’s promotions or price experiments are live in the catalog.
• Scan booking vs walk-in mix to adjust staffing.
• Note training gaps and schedule a 10-minute huddle.

Keep learning

Related guides