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.

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 in your catalog 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 package stock when you offer limited-quantity promotions or seasonal bundles.
• Package sales appear in reporting just like individual services, making it easy to measure bundle performance.
• Update package contents or pricing from the dashboard; changes sync to all branches using that package.

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.

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 supports quick walk-in transactions where customer and vehicle details are optional—perfect for high-volume, quick-service scenarios or when customers prefer anonymity.

Key points

• Start a sale without attaching a customer profile when speed matters more than loyalty tracking.
• Optionally add customer name, phone, or vehicle details if the customer volunteers them.
• 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.
• Use walk-in mode for one-time visitors, tourists, or customers who decline to share contact info.

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.

If your business operates across regions or accepts multiple currencies, Brilloo's POS handles USD, MXN, EUR, and more. Prices display in the branch's configured currency, and reporting consolidates totals for cross-border analysis.

Key points

• Set the default currency per branch so staff see prices in the local tender.
• Customers see consistent pricing whether they book online or pay at the counter.
• Multi-currency sales feed into unified reporting with automatic conversion for company-wide views.
• Train staff on which currencies your location accepts and how to handle foreign tender if applicable.
• Currency configuration is managed in the dashboard; changes apply immediately to the POS.

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

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. Voids and adjustments should be permission-gated and rare.

Key points

• Run cash cuts at consistent times (shift change, end of day) so reporting stays comparable.
• Only trusted roles should void or heavily discount a sale—document the reason.
• Investigate repeated voids on the same employee or SKU as a training or fraud signal.
• Keep physical drawer policies (starting bank, drops) aligned with what you enter in software.
• 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.
• New hires should shadow a full cash cut before doing it alone.
• Document your wash’s SOP for busy Saturdays vs quiet weekdays.
• Rotate audits where a manager spot-checks random tickets against cameras or lane notes.
• 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