Pool Store POS Software for the Counter and the Route
Chemicals at the register. Water tests on the account. Routes on the schedule. One inventory, one customer record, one place to look.
A pool business runs two operations at once. Customers walk in for chlorine and a water test, and a crew opens the same gate on a weekly route. Most software picks one side. A pool store POS built as an operating system covers both, so the chemical you sold at 9am and the chemical used at 2pm come out of the same stock count.
Why a pool store needs more than a register
Walk into most pool stores and you will find two systems that never speak. A retail register at the counter tracks barcodes, tax, and card payments. A separate service platform tracks routes, recurring maintenance, and technician notes. Neither one knows that the customer standing at the counter is also on Thursday's route.
That split produces a predictable set of problems. Chlorine gets counted twice, once in the back room and again on a truck, and the two counts never match. A customer's water test from last week is not visible to whoever is ringing them up today. Equipment sales get tracked on a paper invoice while the install job lands in a calendar that nobody connects to the sale. And at month end, someone rebuilds revenue by adding two reports together.
The fix is structural, not a better integration. The counter and the route should read from the same customer, the same inventory, and the same payment record. That is what we build.
What the system handles
Configured around how a pool store actually sells, stocks, and services, not squeezed into a generic retail template.
Counter sales and barcode checkout
Ring up chemicals, parts, and equipment at the register with barcode scanning, tax rules, and cash or card tender. Retail sales post to the same customer record as their service history.
Chemical inventory with unit conversions
Track liquid chlorine by the gallon, tabs by the bucket, salt by the pallet, and parts by the each. Receive stock, adjust counts, and set reorder points so you stop guessing what to order before Memorial Day.
Water test history on the customer record
Attach every test result to the account. Whoever is at the counter can see what the water read last week, what was recommended, and what the customer actually bought, instead of starting cold.
Service routes and recurring maintenance
Weekly, biweekly, and seasonal routes scheduled against the same customer accounts. Crews see stops, gate codes, and pool details on their phone; completed stops feed billing automatically.
Recurring billing and card on file
Charge maintenance plans monthly without re-keying invoices. Cards are stored securely through Stripe, so a failed payment is visible the same day instead of at the end of the quarter.
Equipment sales with install jobs
Sell a pump, heater, or cleaner as a line item and immediately create the install job tied to it, with the serial number, warranty date, and service address attached to the customer.
Financing and installment payments
Split larger equipment purchases into scheduled payments. The balance, due dates, and remaining amount live on the customer record so nobody has to reconcile a spreadsheet at month end.
One dashboard for both sides
See counter revenue, route revenue, chemical margin, outstanding balances, and scheduled work in a single view rather than a register report plus a separate service report.
Why the usual two-tool setup keeps failing
Both off-the-shelf paths leave half the business uncovered. The gap is not a feature list, it is where the data stops.
A retail POS alone
- No route scheduling, so service work lives in a separate calendar
- No recurring maintenance billing or card on file
- No water-test history attached to the customer
- No install jobs, serial numbers, or warranty tracking
A field service platform alone
- No barcode checkout or counter register
- No chemical inventory with unit conversions
- No retail tax handling or in-store tender
- No equipment sales or financing at the counter
Chemical inventory that survives a Saturday
Pool chemicals are not ordinary SKUs. They are sold in gallons, pounds, buckets, and pallets, stored in two places at once, and consumed by a route that nobody wants to interrupt to count stock. The system is built for that reality.
How implementation works
Four to six weeks from workflow session to go-live, with the register often live first.
Workflow session
We map the counter, the route, the ordering cadence, and how installs and warranty work are handled today. This decides what the system must do, not what a template allows.
Data migration
Customers, chemical SKUs, equipment history, and open balances come across. Duplicate accounts created by the old two-system setup get merged.
Counter configured
Barcode layout, tax rules, tender types, receipt format, and card processing are set up so staff can start selling before the service side is finished.
Routes and billing
Recurring plans, route order, crew assignments, and card-on-file charging are configured against the migrated accounts, then tested on live stops.
Training
Front-counter staff and crews are trained separately, because they use different screens and care about different things.
Refinement
Two to three weeks of live use, then adjustments to inventory thresholds, route order, and reporting so the numbers hold through a full month.
Frequently asked questions
About pool store POS software and how it fits a retail plus service operation.
What is pool store POS software?
Pool store POS software runs the retail side of a pool business: barcode checkout, chemical and parts inventory, customer accounts, and payment processing at the counter. A complete system for a pool company also runs the service side, because most stores sell chemicals at the counter and clean pools on a route. When those two sides share one inventory and one customer record, you stop counting the same chlorine twice.
Can this handle both retail sales and service routes?
Yes. That is the reason to build rather than buy. Retail registers are built around product SKUs, while field service software is built around jobs. A pool business is both. In a unified system, a customer is one record, a chemical is one stock item, and a sale at the counter and a service stop on Tuesday both draw from and report against the same data.
Why not just use Square or Clover at the counter and separate service software?
You can, and many pool stores do. The cost is reconciliation. Retail POS systems do not schedule routes or bill recurring maintenance, and service platforms do not handle barcode checkout, unit conversions on chemicals, or counter tax. You end up exporting from two systems, and the inventory count in each is wrong in a different way.
How does chemical inventory work across the store and the truck?
Each chemical is one stock item with a location. Stock can sit in the store, on a specific truck, or both. When a route stop uses chlorine, the usage posts against the truck and can trigger a restock transfer from the store. You get one count that reflects reality, not a store count and a truck count that disagree.
Does it support recurring maintenance billing?
Yes. Plans can be weekly, biweekly, or seasonal, with a monthly or per-visit charge. Completed visits generate billing automatically, and a card on file can be charged on a schedule. Failed payments surface immediately, and the account shows the balance.
Can customers see their water tests and service history?
A customer portal is optional. When enabled, customers can view past water tests, service visits, equipment purchases, invoices, and remaining installment balances, and can pay online. It reduces front-counter phone calls for routine questions.
Does the register work offline?
Counter sales can be configured to keep accepting payments and queue records when the internet drops, then sync when the connection returns. Route-based work needs connectivity for scheduling and card-on-file charges, so mobile coverage along the route is part of the scoping conversation.
How long does a pool store POS implementation take?
Most builds run four to six weeks from the workflow session to go-live, depending on how many years of customer, chemical, and equipment history need to be brought across. Counter hardware, tax rules, and payment processing are usually configured in the first two weeks so the register can go live before the service side finishes.
Related Capabilities
These modules work together as part of your unified operating system
Ready to build your operating system?
Start with the onboarding process. We'll map your operation, configure your platform, and get you live in 4-6 weeks.
Start Onboarding