EC Pro describes equestrian software that brings lesson schedules, horse allocation and rider information into a shared system, alongside online bookings and payments. It says the system is built for equestrian centres, riding schools and therapy centres, and lists payment gateways and finance integrations, naming QuickBooks and Xero, among its features. Its UK pricing page sets out three tiers and distinguishes subscription arrangements from booking fees. These published categories are useful prompts for a buyer. They are not evidence from an Equanine product test, and the evaluation method below is our independent editorial analysis.
Start with a real sequence of work
Before comparing software, write down one ordinary booking from enquiry to completion. Include the information collected, who approves it, how people and resources are assigned, how payment is recorded and what happens when plans change. Then add an awkward but plausible variation, such as an instructor becoming unavailable. A vendor demonstration should follow your sequence rather than only the order of its feature menu.
Watch the handovers closely. If a booking changes, which screens and people receive the updated information? Can staff distinguish a draft from a confirmed arrangement? Is the reason for a change visible to the person taking over? These questions help reveal whether the proposed system matches your actual responsibilities.
Ask about control and continuity
- Permissions: who can view information, change a booking, adjust charges or amend a record?
- History: can an authorised user see what changed and resolve conflicting entries?
- Export: what information can the business retrieve, in which format, and how is access handled when a contract ends?
- Support: what help is available during the hours the centre operates, and how are urgent issues escalated?
Ask the provider to demonstrate the answers using sample data. Avoid putting real customer information into an informal sales exercise. If the system connects to accounting, payments or another service, establish which organisation supports each connection and what the user does when information does not transfer as expected.
Compare the complete commitment
A monthly subscription is one part of the decision. Ask about transaction charges, optional functions, training, setup work and any cost attached to changing plans or retrieving records. Confirm which charges fall on the business and which appear at customer checkout. Evaluate terms against the centre’s own booking pattern instead of assuming the cheapest headline package will suit it.
Implementation also needs an owner inside the business. Decide which records to bring across, who checks them and how staff learn the new routine. Test a small set of agreed scenarios before changing the whole operation. Document any gaps and the workaround accepted by the team.
The buying decision should end with evidence from the demonstration, written answers and a clear implementation plan. A feature list describes possibilities. A carefully chosen working example shows whether those possibilities fit the people who will depend on the system each day.
