Loopit Documentation
Changelog
  • Getting Started
    • What is Loopit?
    • Key Concepts
    • Setting up Loopit
      • Logging into Loopit
      • Multiple vs Single Workspaces
      • Configure Your Workspace
        • Workspace Details
    • Quick Start Guide
    • Welcome to Loopit 2.0
      • Understanding Loopit's Pricing Structure
  • Assets
    • Overview
    • Categories
      • Managing Categories and Subcategories in Loopit
      • Understanding Categories and Subcategories
      • Managing Pricing Overrides in Loopit
    • Adding Your Fleet
      • Uploading Photos
    • Tracking
      • Meter Readings
      • Tracking devices
    • Fleet Management
      • Issues
      • Service reminders
      • Inspections
    • Price Overrides
      • Customizing Charge Pricing Across Packages, Categories, and Fleet
      • Package-level Prices
      • Category-level Override
      • Asset-level Override
      • Asset-level Ultimate Override
  • Bookings
    • Overview
    • Lifecycle of a Booking
      • Creating a Booking
      • Confirming a Booking
      • Activating a Booking
        • Before Activation
      • Editing a booking
        • Adjust the price
        • Schedule Booking Changes
      • Pausing a Booking
      • Ending a booking
      • Cancel a booking
    • Deposits
      • Collecting deposits
      • Refunding/Claiming deposits
    • Referral source tracking
    • Tracking booking owner/manager
    • Contracts
      • How to Append Terms & Conditions (T&Cs)
      • How to send signed copy of contract/agreement to customer?
      • Inserting Dynamic Variables in Contract Templates
  • Billing
    • Invoices
      • Overview
      • One-Time Charges & Invoicing
      • Tax Types & Rules
      • Downloading Invoices
      • Overdue Invoices
      • Statement of account
      • Emailing invoices
      • Ad Hoc Billing & Invoices
    • Payments
      • Overview
      • Stripe integration
        • AU Becs Direct debit
      • Payment retry - Dunning
      • Auto pay
    • Credit Notes
      • Overview
      • Applying credit notes
      • Auto-apply credit notes
    • Setting up your packages
      • Program Types
      • Packages
        • What are packages?
        • Creating a package
        • Charge types and models
        • Configuring delivery on packages
        • Charges per location
    • Add Ons
      • Mileage Billing
      • Claim Excess & Excess Reduction
    • Billing Items
  • Settings
    • Users
      • Roles & Permissions
      • Inviting & Assigning Users
      • Enabling & Disabling Users
    • Locations
      • Managing Locations
      • Invoice Customisation
      • Assigning Fleet Locations
      • Booking pickup date rules
    • Workflows
      • Overdue Invoice Reminder
    • Email templates
      • Merge Tags
      • Entity Types
      • Creating a Template
    • Contract templates
      • Creating a template
      • Assigning a Contract Template
    • Integrations
      • Xero
      • FrankieOne
      • Geotab
      • Telemax
      • Rentalmatics
      • Sumsub
      • Tessera MVR Search
      • Experian AU
      • Bonzah Insurance
    • Webhooks
    • Website
      • Facebook Meta Pixel
    • Booking Rules
  • Security
    • Security information
  • People/Companies
    • Creating a Person or Company
      • Creating a person
      • Creating a company
    • Emergency contacts and references
    • Document expiry notifications
Powered by GitBook
On this page
  • Why We Rebuilt Loopit
  • Familiar Workflows, Evolved
  • Then vs Now: Evolving Key Workflows
  • 💰 Direct Vehicle Rates and Category-Based Pricing
  • 🔄 Structured, Flexible Customer Lifecycle Management
  • 📈 Smarter Pricing Recommendations (Coming Soon)
  • 🏦 Accurate, Real-Time Payment Status for BECS
  • 🧑‍💼 Customer Assessment Tools Available On-Demand
  • 🚗 Dynamic, Intelligent Vehicle Availability
  • 🧾 Tailored Business Billing Solutions (Coming Soon)
  • 📦 Packages Power Flexible Go-to-Market Models
  • 💳 Fully Configurable Charges Engine
  • This Is Just the Beginning
  1. Getting Started

Welcome to Loopit 2.0

Loopit 2.0 marks the next evolution of our platform—rebuilt from the ground up to better serve the needs of modern mobility providers.

This isn’t just an update. It’s a foundational shift designed to overcome the limitations of our original platform (Loopit 1.0) and open the door to new, more powerful ways of working.

While the Loopit features you know and love have been carried across into the new version, they may have taken on a different form which is more efficient, scalable and powerful.


Why We Rebuilt Loopit

Loopit 1.0 helped pioneer the vehicle subscription category and enabled businesses around the world to launch flexible mobility services. But as we grew with our customers, we hit certain limitations—technical and operational—that couldn't be solved with incremental fixes.

Some of the key bottlenecks in 1.0 included:

  • Rigid configuration: Features were hard-coded for specific workflows, making it difficult to adapt to different business models.

  • Scalability issues: Performance degraded as fleets and subscriber bases grew.

  • Workflow fragility: Customizations often broke when trying to scale across different locations or teams.

  • Limited extensibility: Integrating with other systems or expanding into new rental/leasing models required significant workarounds.

Loopit 2.0 solves these challenges with a reimagined platform architecture—one that’s modular, configurable, and designed to grow with your business.


Familiar Workflows, Evolved

We know change can be disruptive, especially when it comes to features you rely on every day. With Loopit 2.0, some workflows may look different than what you’re used to. That’s intentional.

Every design decision has been shaped by real-world customer feedback and behavioural data collected over years of usage. While certain tools from 1.0 may no longer exist in the exact same form, their underlying purpose has been preserved—and enhanced—to be more:

  • Scalable: Work across locations, teams, and vehicle types without duplicating effort.

  • Extensible: Adapt and grow your service offerings, whether daily rental, long-term leasing, or subscriptions.

  • Efficient: Do more with fewer clicks, clearer workflows, and smarter defaults.

Have a workflow that feels unfamiliar? Let us know. Chances are, there’s a new and better way to achieve the same outcome—with more power behind it.


Then vs Now: Evolving Key Workflows

Below are a few common examples where 2.0 takes a different but deliberate approach:


💰 Direct Vehicle Rates and Category-Based Pricing

Before: Additive Pricing Model (Plan + Vehicle Premium)

In 1.0, the total vehicle cost was calculated by combining a subscription plan rate with a separate vehicle premium. This worked well for subscription use cases but became restrictive for broader rental applications.

✅ Now in 2.0: Each vehicle now has its own direct rate, and you can also define default rates by vehicle category (e.g., Economy, SUV, Luxury). Vehicles inherit category pricing by default but can be individually overridden as needed.

Why? This approach makes Loopit a true multi-modal platform, equally capable for rental, leasing, and subscription services. You gain finer control over pricing strategies without relying on additive structures—and can still achieve the same ultimate outcomes, now with more precision and flexibility.


🔄 Structured, Flexible Customer Lifecycle Management

Before: Immediate Booking Confirmation

In 1.0, when a customer submitted a booking request, it was automatically treated as confirmed—even if eligibility checks hadn’t been completed or vehicle availability changed. This often led to uncomfortable back-and-forth conversations with customers and resulted in vehicles being prematurely locked out of availability, hurting fleet utilisation.

✅ Now in 2.0: Loopit 2.0 introduces a clearer customer lifecycle flow with new stages: Quoted, Requested, Confirmed, Active, and Ended. These lifecycle statuses give your team better control over when a booking is actually confirmed and when a vehicle is actually reserved, while still keeping the process flexible enough to suit your internal operations.

Why? This change introduces structure without unnecessary rigidity—helping you prevent misunderstandings, improve vehicle utilisation, and manage customer expectations more professionally, much like a CRM.


📈 Smarter Pricing Recommendations (Coming Soon)

Before: In-Platform Vehicle Pricing Suggestions

In 1.0, Loopit provided automatic vehicle premium suggestions based on a calculation tied to a fixed plan price. While the pricing calculator was designed to be robust, it often defaulted to a simple range of around 0.3%–0.4% of the vehicle’s retail price. It also had limitations—such as assuming a base subscription plan price of $170—which didn’t suit every customer and sometimes resulted in premiums of thousands of dollars.

✅ Now in 2.0: At launch, Loopit 2.0 does not include the legacy pricing calculator. Instead, we’re developing a new approach that will deliver pricing suggestions based on real-world factors like seasonal demand, usage patterns, and residual value—giving you more accurate, flexible, and dynamic recommendations that drive both utilisation and revenue.

Why? Rather than relying on static calculations, we’re building a smarter pricing engine that adjusts to your business needs and market conditions. In the meantime, using a simple guide of around 0.35% of current retail price for vehicle premiums can serve as a helpful benchmark, along with our ROI calculator for validation.


🏦 Accurate, Real-Time Payment Status for BECS

Before: Immediate (But Inaccurate) Payment Status for BECS

In 1.0, invoices paid via BECS (direct debit) were immediately marked as Paid when the payment was initiated, even though BECS processing can take up to 4 days. If the payment later failed, the status would revert to Failed. This led to a false sense of payment success, created gaps in arrears reporting, and made it harder to track true outstanding balances.

✅ Now in 2.0: In Loopit 2.0, BECS payments will now show as Processing until the payment outcome is confirmed as either Paid or Failed.

Why? This delivers far more accurate reporting, gives your team a clearer view of actual payment statuses, and strengthens your ability to manage arrears. You may notice a temporary increase in reported arrears, but this is simply a reflection of more precise tracking—not a change in the underlying payment outcomes compared to 1.0.


🧑‍💼 Customer Assessment Tools Available On-Demand

Before: Mandatory Customer Assessment During Sign Up

In 1.0, every new customer was automatically subjected to identity and credit checks as part of the onboarding flow. While this helped vet customers early, it also introduced significant friction—small issues like a typo in a street name or a missing middle name could cause an application to fail. Plus, businesses were incurring verification charges even when checks weren’t always necessary.

✅ Now in 2.0: In Loopit 2.0, customer assessments such as ID verification and credit checks are still available—but now at your team’s discretion, after customer signup.

Why? By decoupling assessments from the signup process, you gain greater control over when and how checks are performed. This reduces unnecessary costs, avoids blocking genuine customers for minor errors, and creates a smoother, faster onboarding experience while still maintaining your risk management standards.


🚗 Dynamic, Intelligent Vehicle Availability

Before: Static, Binary Vehicle Availability

In 1.0, a vehicle was either available or unavailable—based solely on whether it had an active booking. There was no ability to factor in future reservations, partial overlaps, or upcoming availability windows. This often led to underutilised fleet vehicles and more manual work to manage timing gaps.

✅ Now in 2.0: In Loopit 2.0, availability is no longer a simple "yes" or "no." Our new dynamic availability engine automatically calculates whether a vehicle is available based on the requested booking dates and duration. A vehicle can now be available for some timeframes and not others, without manual adjustments.

Why? This change maximises your fleet utilisation by intelligently offering vehicles based on real availability windows, not just whether they are currently booked. It reduces administrative effort, avoids wasted gaps between bookings, and helps you get more value out of every vehicle in your fleet.


🧾 Tailored Business Billing Solutions (Coming Soon)

Before: Aggregated Invoicing for Business Customers

In 1.0, business customers had the option to receive a single, consolidated invoice covering all vehicles booked under their account. While well-intentioned, adoption was low—our data showed that businesses actually preferred more control over individual booking payments while still maintaining overall fleet visibility.

✅ Now in 2.0: Aggregated invoicing is not currently available in Loopit 2.0 at launch. However, we are actively working on a redesigned module that better matches business customer needs—giving businesses the ability to manage payments at a booking level while maintaining fleet oversight and flexibility.

Why? Instead of forcing a one-size-fits-all solution, we’re designing a smarter approach that reflects how businesses actually want to manage their mobility budgets: with both granular control and high-level visibility.


📦 Packages Power Flexible Go-to-Market Models

Before: Plans Defined Static Service Tiers

In 1.0, plans were primarily used to create basic service levels—like "Small," "Medium," and "Large" subscription offerings—with fixed inclusions and pricing. Each plan was tied closely to a rigid structure, and multiple plans were often needed just to offer different pricing tiers.

✅ Now in 2.0: Packages replace plans and unlock a far more dynamic approach. Packages now define your business models—not just your service tiers. Whether you want to offer daily rental, monthly subscription, or even long-term leasing across the same fleet, you can configure and manage these through packages.

Why? Packages are designed to support true multi-modal offerings within a single platform. Instead of needing multiple plans to create pricing variations, smarter tools like tiered pricing and volume-based billing are now built directly into each package, giving you much more flexibility without added complexity.


💳 Fully Configurable Charges Engine

Before: Hardcoded, Limited Charge Types

In 1.0, charges like liability protection, swap fees, and overage fees were hardcoded throughout the platform, each with their own dedicated fields. This setup made it difficult to customise charges for your business—and nearly impossible to introduce your own charge types or adapt to new service models without workarounds.

✅ Now in 2.0: Loopit 2.0 introduces a brand-new Charges Engine that gives you complete control. You can now create and configure any type of charge you need—no restrictions. Whether you want dynamic overage fees based on how far a customer exceeds their allowance, different excess amounts per vehicle, or complimentary baby seats for select categories, it’s all possible.

Why? Instead of prescribing a fixed set of answers, we’ve given you the tools to design your own billing experience—scalable, flexible, and ready to grow with your business.


This Is Just the Beginning

Loopit 2.0 is built to evolve. While some familiar features may have changed, we’ve done so with intention—to give you more flexibility, more control, and ultimately more opportunity.

We’re committed to helping you navigate this transition with the support, resources, and guidance you need.

Last updated 17 days ago