Customer records
One record per customer that the rest of the platform — sales, POS, invoicing — points at.
Farexa CRM keeps customer records with their lead source, order history, and running balance — and captures inquiries straight from your tenant website — so the people you sell to are a record, not a contact list in someone's phone.
Plenty of businesses lose customers not to competitors but to their own filing. The contact is in one person's phone, what they ordered is in the invoices, what they owe is in the accountant's head, and how they found you is nowhere. Farexa CRM puts those together on the customer record: who they are, the lead source that brought them, the orders they've placed, and the balance they're carrying.
That record isn't a silo — it's the customer the rest of the platform already uses. An order raised in Sales or a sale at the POS counter attaches to it and builds an order history, and the customer statement shows their balance and what's outstanding without anyone reconciling by hand. Inquiries captured from your tenant website land as records too, so a lead from the public site becomes a customer you can actually follow up, rather than an email that gets buried.
It's deliberately a working customer record for an operating business, not a heavyweight sales-automation suite. What it does, it does honestly: identify the customer, track where they came from, show what they've bought and what they owe, and connect the inquiry on your website to the record you sell against.
One record per customer that the rest of the platform — sales, POS, invoicing — points at.
Capture where each customer came from, so you can see which sources actually bring business.
Orders from Sales and POS attach to the customer, building a history of what they've bought.
See a customer's running balance and outstanding amounts, and produce a statement without hand-reconciling.
Inquiries from your tenant website land as records, so a public lead becomes a customer you can act on.
Book appointments tied to the customer, so bookings and records aren't separate systems.
Customer access follows branches and roles, so teams see the customers that are theirs.
The same customer feeds orders, invoices, and statements, so nobody keeps a parallel list.
No, and it doesn't pretend to be. It's a working customer record for an operating business: customer details, the lead source that brought them, their order history, and their balance — plus inquiries captured from your website. It's honest about being a customer record rather than a sales-automation suite.
Yes. Each customer carries a lead source, so you can see which channels actually bring paying business rather than guessing.
Yes. Orders from Sales and POS attach to the customer, building order history, and their statement shows the running balance and outstanding amounts without hand-reconciling.
Yes. Inquiries submitted on your tenant website land as records, so a lead from the public site becomes a customer you can follow up rather than an email that gets lost.
Yes. Appointments tie to the customer record, so bookings live with the customer rather than in a separate calendar.
Book a walkthrough and see lead source, order history, balance, and website inquiries come together on the customer.