Gym turnstile software integration is the connection that lets a gate check your membership records before it opens. The gate reads a card, a fingerprint or a face, asks the software whether that member is allowed in, then opens or stays shut. If you already run FitZone Pro gym management software or other membership software, the job is to link the gate to that record. You don't replace the system your staff use every day.
1What does gym turnstile software integration actually do?
A gate on its own only knows how to open or stay shut. It does not know who has paid. Your membership software knows that. The integration passes the answer from one to the other each time someone walks up.
The gate can act on four statuses:
- Active: the gate opens.
- Expired: fees have lapsed, so the gate refuses entry.
- Frozen: the member is on hold, so the gate refuses entry until the freeze ends.
- Suspended: the gate refuses entry until staff reinstate the member.
Without the link, someone at the desk checks names by eye, or the gate stays open and you hope for the best.
2How does a turnstile read your membership records?
A member record holds a name, a plan, a branch, a status and a member ID. A gate does not read names. It reads a credential: an RFID card, a QR code, an NFC tag, a fingerprint or a face template.
The link between the two is the pairing. At enrolment, the credential number or biometric template is stored against the member ID. When the member scans in, the gate sends the credential to the software, or checks its own copy of the list. The software finds the member ID and returns the status.
How does a member's credential get paired with their record?
At the front desk, the steps are short:
- Open the member record and confirm the plan and branch.
- Present the card, tag, finger or face to the enrolment reader.
- Save the credential against the member ID.
- Walk the member through the gate and confirm it opens.
Lost cards need care. Cancel the old credential in the software first, then issue and pair a new one. Check that the gate actually refuses the old card. A cancellation can reach the software straight away but reach the gate only at the next sync.
Branch changes are the other common case. The new branch's gates must accept the record. If your setup uses branch-level access, update the branch before the member's first visit, or the gate will refuse them.
For how attendance data can drive fee checks, see linking biometric attendance to gym membership fees.
Should the gate check live or use a local list?
In a live check, the gate asks the software every time a credential is read. In a local list, the gate holds a copy of member statuses and refreshes it at set intervals, usually called a sync.
A live check is current. A payment that fails at 9:00 should refuse entry at 9:01. The weakness is the network. If the connection drops, a live-only gate stops or refuses everyone.
A local list keeps working when the internet is down. The weakness is age. Between syncs, a member who has just lapsed can still get in. A list refreshed every few minutes behaves very differently from one refreshed overnight.
Many setups use both: a live check where the network is reliable, and a local list as the fallback. Ask which mode the vendor or developer uses and how often the list refreshes. Write the answer into the scope.
3Which integration route should a gym choose?
There are three routes. The right one depends mainly on your membership software, not the gate, although the gate's controller still has to match whichever route you pick.
| Route | Best when | What it needs | Main risk |
|---|---|---|---|
| Native vendor driver | Software is on the gate vendor's list | Supported version, maintained driver | Updates break the link |
| Protocol bridge | Gate uses Wiegand, RS485 or TCP/IP | Bridge or controller, confirmed protocol | Protocol assumed, not confirmed |
| Custom connector | Software is custom, old or unlisted | API or database access, a developer | Depends on who maintains it |
If your software is a common platform on the gate vendor's list, start with the driver. If it is custom-built or old, a custom connector is often the cleanest route. Each route has its own cost and failure pattern, covered below.
Native driver: does a ZKTeco gate work with your software?
It can, when your software is on the gate vendor's supported list. The driver can then connect the two through configuration rather than new code. This is usually the quickest route.
Check three things. The software name and exact version must be on the list. Find out who updates the driver when gate firmware or your software changes. Confirm the vendor supports every branch you run.
For ZKTeco hardware, see our ZKTeco gym software page. That page covers ZKTeco hardware only. Confirm your controller model and protocol against it and against your written scope before you order.
Which protocol does my gate need: Wiegand, RS485 or TCP/IP?
Gates talk to their controllers using wire protocols. Wiegand is an older format common on card readers. RS485 is a serial line that runs over longer cable. TCP/IP is a network connection. Some gates use a simple relay, a contact that closes to open the barrier.
A bridge or controller sits between the gate and the software. It takes the decision from the software and turns it into a signal the gate understands.
Confirm the protocol on the order. Never assume it. Many gates support more than one, and the choice changes the controller and the wiring. A mismatch found after installation costs far more than a question asked before ordering.
Custom connector for your software
Use this route when the software is custom-built, very old or on no vendor's list. A connector reads member status through an API, or through a read-only database connection where no API exists. It then drives the gate through a controller or relay.
A connector is code. It needs documentation, tests and a named person to maintain it. We can scope a connector for your software; see our API development services. The scope, price and launch date are agreed in writing before work starts, and you own the code.
4What should you ask a vendor before you order?
Get these answers in writing before you sign.
| Question | Why it matters |
|---|---|
| Which membership software and version are supported? | A version not on the list can break at the next update |
| Which protocol does the gate use: Wiegand, RS485, TCP/IP or relay? | The wrong protocol means the wrong controller and wiring |
| Who maintains the driver after a firmware change? | Firmware updates break links, so you need a named owner |
| What happens when the network or power drops? | It decides whether members are stuck or let in |
| Can event logs be exported, and in what format? | Logs settle disputes and support audits |
| Are anti-tailgating and auto-reset included? | Stops two people following one card through a single read |
| Is the scope written, with a fixed price and launch date? | Without them, every change becomes an open-ended bill |
5What happens when a payment lapses or the internet drops?
A card payment fails, and the software marks the member expired. At the next check or sync, the gate refuses them. When they pay, the status returns to active and the gate opens. Test that path before go-live.
The failure cases are rarer, but they are where owners get caught out.
Can the gate block members with lapsed fees?
Yes, if the integration is set up that way. Confirm it rather than assume it. Settle the blocking rules with your membership software vendor or developer before you configure the gate. Decide which status triggers a block and whether there is a grace period. Our guide on blocking gym members with expired fees at the door walks through those rules in more detail.
Before go-live, run this test with a test member:
- Set the member to active. Confirm the gate opens.
- Set the member to expired. Confirm refusal within your agreed sync time.
- Renew the member. Confirm the gate opens again.
- Repeat steps 2 and 3 for frozen and suspended.
- Cancel a card and issue a new one. Confirm the old card is refused and the new one opens.
- Try the card at a branch the member does not belong to.
Record each result. Anything that fails goes back to the developer before cutover.
Offline mode and staff override
Ask what the gate does with no network. A local list keeps current members working. New enrolments usually wait until the connection returns.
Staff need a way to open lanes when the system fails, such as a key or a manager's code. Log every override with the time and a reason, and make sure lanes lock again once it ends.
6What happens during a power cut or fire alarm?
Power cuts and fire alarms need a planned answer. Ask whether the controller has battery backup, and find out what the gate does when power is lost or an alarm sounds.
Do not assume the gate fails open or fails closed. Ask your local fire authority and building inspector which fail-safe mode applies to your building. Get that answer in writing before the gate is specified. Then ask the vendor or developer to set the gate to that mode and test it.
7How much does gym turnstile software integration cost in USD?
These figures are indicative. They come from published price guides from turnstile sellers, access control cost guides and installers, not from quotes. The sources are not dated in a way we can verify, so treat them as starting points and check current prices before you budget. Hardware sellers dominate these guides, and software work is rarely priced on its own.
| Item | Range (USD) | Source type |
|---|---|---|
| Gate hardware, tripod, per lane | $200–$1,400 | Turnstile seller price guides |
| Gate hardware, flap barrier, per lane | $450–$3,000 | Turnstile seller price guides |
| Gate hardware, speed gate, per lane | $1,300–$8,000 | Turnstile seller price guides |
| Installation labour, per unit | $500–$2,000 | Turnstile installer cost guides |
| Software licence and maintenance, per door, per month | $30–$200 | Access control cost guides |
The turnstile integration cost line is missing from that table on purpose. Some published guides put it as a percentage of hardware, and the two we reviewed disagree on the percentage. That makes it too unreliable to quote. Treat any percentage rule as a rough sanity check, and price the integration from a written scope.
Hardware prices also vary widely between suppliers. Some guides quote vendor turnstile pricing well above the ranges shown, which is one more reason to get a written scope before you budget.
For a rough software estimate, use the software development cost calculator. It gives a starting point, not a quote. For a wider view of build costs, read custom software development cost in 2026.
Worked example: one lane and three lanes in USD
Both examples use flap barriers, one door per lane and twelve months of licence. The integration line is shown separately because it comes from a written scope.
| Line | One lane | Three lanes |
|---|---|---|
| Gate hardware (flap) | $450–$3,000 | $1,350–$9,000 |
| Installation | $500–$2,000 | $1,500–$6,000 |
| Licence, first 12 months | $360–$2,400 | $1,080–$7,200 |
| Subtotal before integration | $1,310–$7,400 | $3,930–$22,200 |
| Integration | From written scope | From written scope |
The subtotal is your spend before the software link. It is not an estimate of the integration, which depends on your membership software, gate protocol and offline rules.
The integration line may not scale in a straight line with the number of lanes. Ask the developer to price shared work, such as the connector or driver, separately from per-lane work, such as configuring each controller.
Estimating your own integration line
A written scope needs these details:
- Number of lanes and gate type
- Membership platform and exact version
- Gate controller and protocol
- Number of branches, and whether they share one account
- Offline and fail-safe needs, including what the fire authority requires
- Reports and log exports you need
With those, a developer can price the integration line. Without them, any figure is a guess.
8Can one dashboard run gates across several branches?
Yes, if your membership software supports several branches and the gates report back to it. One dashboard can then show member status and gate events across sites. Confirm multi-branch support in writing for your software version and each gate type. Do not assume it.
This suits chains with branches in New York, Austin, Raleigh or Denver, and multi-site owners in the Greater Toronto Area. The prices in this article are in USD, taken from third-party sources. If you budget in Canadian dollars, convert on the day you ask for a quote, because exchange rates move.
For US teams, see our software development for US companies page.
9What privacy rules apply to fingerprint and face data?
Privacy rules for fingerprint and face data differ by state, province and city. This article does not give legal advice. Check the rules for your location with a qualified adviser before you collect biometric data.
What you can control is the design. Ask where the biometric template is stored: on the gate, in your software or with the vendor. Ask who can see it, including staff roles, vendor support and developers. Ask how long it is kept, and what happens to it when a member leaves. Get the answers in writing.
Card and QR credentials usually hold less personal data than a fingerprint or face template, so they raise fewer questions. For how face-based entry works in practice, see gym software with face recognition entry.
10Who owns the access logs, member data and integration code?
You do. At Treevoxa, the client owns the code and the accounts. That belongs in the written scope before work starts, not at handover. Ask for four things:
- Log export in a documented format such as CSV, with timestamps, gate IDs and the result of each read.
- Data location: where member records and logs are stored, and in which country.
- The driver or connector code, with a short document on how to run and update it.
- Admin accounts for the gate system, the software and any hosting, held in your company's name.
11How does a project run from quote to a working gate?
A typical Treevoxa project runs in this order:
- Written scope. Lanes, gate type, protocol, software version, branches and offline rules are written down. The fixed price and launch date are agreed before work starts.
- Pilot on one lane. Install and connect one lane, then run the test cases above.
- Testing. Check active, expired, frozen and suspended members, a reissued card, a wrong-branch card and an offline period. Log every override.
- Cutover across lanes. Brief staff, switch the remaining lanes and keep a manual fallback ready for the first week.
- Handover. The code and accounts go to you.
Treevoxa has offices in Toronto, Thornhill, London and New York. If you want a written scope for your gates, send your details through our contact page.
12Where to start with gym turnstile software integration
This week, start your gym turnstile software integration by checking your membership software version against the gate vendor's supported list. Then export a sample of member statuses, so you can see exactly what the gate would need to read.