
Smart Rental: API-first WheelSys Instead of Embed Booking Forms
- API-First Booking
- WheelSys ERP Integration
- WordPress & Sage
SMART RENTAL
Smart Rental's priority was technical honesty: to stop presenting an embed widget as a real integration. The website needed genuine WheelSys API bookings within a modern WordPress front end.
We delivered a Miles API-first build where WheelSys drives bookings and the Sage WordPress theme hosts the brand experience that operators can still edit.
- Client
- Smart Rental
- Timeframe
- Under 1 month
- Project type
- Miles · API-first rental
- Scope
- API booking UX, WheelSys integration, WordPress/Sage, performance
SMART RENTAL
Overview
This case study covers replacing an embed theatre with API-backed bookings, while keeping the public site on the familiar WordPress/Sage foundation.
Visitors get a coherent booking journey. Operations get WheelSys as the system of record via API — not an iframe that breaks styling and analytics.

The Challenge
Embed forms introduce a second UI inside the brand site. Smart Rental needed a single journey that belongs to the operator's stack.
Key challenges:
- Removing dependency on fragile third-party embeds
- Connecting WheelSys as a true API booking layer
- Maintaining brand UX whilst surfacing live booking states
- A maintainable WordPress alongside the integration



The Solution
We built Smart Rental as an API-first Miles project: WheelSys for bookings, WordPress/Sage for a resilient marketing site.
Key pillars:
1. True WheelSys API Integration
Booking actions communicate with WheelSys via API so that availability and reservations remain authoritative.
2. One Brand Journey
The public UI no longer switches to a foreign embed skin in the middle of the funnel.
3. WordPress Sage Still Editable
Marketing pages, SEO content, and campaigns remain in Sage WordPress without disrupting the API work.




Performance / Results
Integration quality that visitors can feel
The Smart Rental site feels like a single product because the booking layer is embedded, not bolted on.
WheelSys and WordPress remain the Miles constants — API-first delivery is the defining difference.

Key Metrics
- API-first delivery window< 1 month
- Booking modelWheelSys API
- Front foundationWordPress + Sage
Search engines and buyers reward specialisation. Smart Rental's story is the API-first Miles path.
Final Thoughts
If the booking UI is rented from an embed, the brand does not own the moment of conversion. Smart Rental takes it back.
Hellenic Technologies standardises on WheelSys and WordPress so that the hard work of integration becomes reusable across Miles projects.
Previous project
Sirius Rent a CarNext project
Rooted


