.svg){kind=small}
Turn any standard bike into an app-based rental product.
The OC33 Horseshoe Lock gives non-IoT bikes the missing hardware layer for self-serve rentals. Pair it with Levy Fleets and riders can unlock from the app, start trips, get tracked by GPS, follow parking rules, and relock to end the ride just like the rest of your platform, whether you deploy it as a horseshoe-only lock or with the optional cable.
Works with standard bikes that have no built-in IoT.
Uses the lock's own GPS for trip and parking validation.
Lets operators launch on mixed brands under one app.
Keeps billing, support, and fleet operations in Levy Fleets.
Hardware
Two OC33 deployment options
Show operators the lean horseshoe-only setup or the OC33 paired with the auxiliary cable on the same connected platform.
Quoted connectivity
4G, GPS, BLE, Type-C, OTA and BLE updates.
Rider entry points
App unlock, server command flow, and optional RFID access.
Fleet visibility
Real-time location, trip distance, and parking enforcement signals.
Ride completion
The trip can be gated on a successful relock before it closes.
Before retrofit
A standard rental bike is just a manual asset.
No built-in telematics or native rental controls
Manual key handling or staff unlocks
No live trip visibility for operations teams
No automatic ride close-out validation
After OC33 + Levy Fleets
The bike becomes a first-class rental vehicle in your platform.
App-based unlock tied to rider identity and payment
Live GPS, trip distance, and ride state inside Levy Fleets
Parking-zone enforcement using the lock's own location
Required physical relock before trip completion
Platform capabilities
The lock is the hardware. Levy Fleets is the product.
OC33 is most valuable when it plugs into the complete operating stack: rider app, payments, fleet map, trip state, service tooling, and operator controls in one place.
Start And Unlock In The App
Riders discover the bike, scan the QR code or tap in the app, and unlock the physical lock without staff involvement.
Real-Time GPS Trip Tracking
Each OC33-equipped bike reports location so trips, distance, and live fleet position show up directly in Levy Fleets.
Parking Zone Compliance
End-of-trip rules can be tied to the device GPS so riders are pushed back into valid parking areas before a ride can close.
Required End-Of-Ride Relock
The rental flow can require the user to physically relock the bike before the trip is considered complete.
Same Billing Stack As The Rest Of Your Fleet
Unlock fees, ride charges, passes, wallet balances, and payment collection all stay inside the existing Levy rider experience.
Brand-Agnostic Retrofit
Use the same platform across mixed bike brands instead of replacing frames or waiting for OEM IoT integrations.
Rental flow
Built for how operators actually launch retrofit bike fleets.
This page is not about swapping the whole bike. It is about adding the minimum hardware needed to make an existing bike rentable through the same app and backend you already use.
01
Mount OC33 In The Right Configuration
Install the OC33 as a horseshoe-only lock or pair it with the auxiliary cable when the deployment needs an extra capture point.
02
Connect It To Levy Fleets
Provision the lock in your fleet, attach a rider-facing QR code, and assign pricing, zones, and operating rules.
03
Rider Unlocks And Starts The Trip
The user starts from the app, the lock opens, and the ride begins with location and trip state tracked in real time.
04
Trip Ends Only After Compliance
Levy checks the parking location and relock state so a rider cannot simply walk away without securing the bike.
Key operating rule
End the trip only after the bike is back in policy.
Because the device owns location and physical lock state, Levy Fleets can enforce a cleaner close-out flow: approved parking location, successful relock, and then billing completion. That matters for standard bikes where manual returns create the most operational leakage.
GPS-backed parking rules
Validate whether the rider is inside the allowed service or parking area.
Physical relock confirmation
Close rides only after the OC33 lock is back in a secured state.
Configuration options
Show both lock packages on one sales page.
The OC33 story is stronger when buyers can immediately see the two ways you can deploy it: a cleaner horseshoe-only lock, or the same OC33 paired with the cable for added capture flexibility.
Simplest retrofit package
OC33 Horseshoe-Only
Use the core OC33 lock body on its own when you want the cleanest install and a straightforward app-based lock workflow on a standard bike.
Cleaner visual footprint on the bike
Best when a single integrated lock point is enough for the program
Same Levy unlock, trip, GPS, and billing flow
Added lock-path flexibility
OC33 Horseshoe + Cable
Add the cable when operators want the OC33 to secure around more than the integrated horseshoe capture alone.
Adds an auxiliary cable to the OC33 setup
Useful when the deployment needs more physical capture flexibility
Keeps the same connected rental flow inside Levy Fleets
Hardware fit
OC33 is a practical retrofit lock, not a custom bike rebuild.
The quoted OC33 configuration centers on cellular connectivity, onboard GPS, Bluetooth access, remote management, and a rugged waterproof enclosure. That is exactly the hardware profile you want when converting existing bikes instead of redesigning them.
Quoted hardware
OC33 core lock platform
Why this model works for standard bikes
You do not need OEM drive-system access to create a rental workflow. The lock, device GPS, and Levy software layer are enough to manage start, billing, trip tracking, and end-of-ride compliance on a normal pedal bike, with or without the auxiliary cable.
Connectivity
4G, GPS, and BLE in the quoted configuration for cloud reporting plus nearby rider interaction.
Weather readiness
IP67 enclosure suited to outdoor rental operations where locks live on the vehicle, not in a warehouse.
Unlock options
App, server, and optional NFC or RFID workflows support both consumer and closed-fleet deployments.
Upgradeable fleet hardware
OTA and BLE upgrade support is important when devices are already deployed in the field.
Quoted OC33 configuration
- Model: OC33 Horseshoe Lock (SIMCOM7600A)
- Connectivity: 4G + GPS + BLE
- Unlock methods: app, server, NFC/RFID card unlock
- Durability: IP67 waterproof
- Charging: Type-C
- Power: optional 6400mAh battery configuration
- Firmware management: OTA + BLE upgrade support
- Optional upgrades: dual-frequency GPS, RFID, paired cable lock
Power profile
Optional 6400mAh battery configuration and Type-C charging for cleaner field service.
Tracking accuracy
Dual-frequency GPS support is available when tighter location performance is needed.
Rider access
QR on the bike stays compatible with Levy's standard rider acquisition and unlock flow.
Ideal deployments
Built for operators who already have bikes and need the rental layer next.
If you have interest from partners but the bikes themselves are not natively connected, this is the clean path to pilot, prove demand, and scale under one fleet platform.
Hotels and resorts converting guest bikes into self-serve rentals
Campuses and municipalities standardizing mixed bike fleets
Apartments and private communities launching amenity bike share
Existing bike operators retrofitting legacy inventory instead of replacing it
Single platform outcome
Standard bikes, connected bikes, and the rest of your fleet can all live in the same Levy experience.