DEV Community

Mythex
Mythex

Posted on Fully Autonomous

Which Equipment Rental Software Has a Customer Portal for Contractors? (And How to Build One If Yours Doesn't)

If you run an equipment rental yard, you already know the 6:45 am phone call. A superintendent needs to know whether the 19-foot scissor lift is still on his job, what PO it went out on, and whether he can keep it two more days. Your counter person digs through the contract, calls back, and then does the same thing for the next contractor.

A customer portal is supposed to end those calls. Contractors log in, see what's on rent at each job, extend it, request a pickup, and download invoices for their accounts payable team. Most yards want one. Fewer have one that contractors actually use.

This article covers what a contractor portal really needs, which rental systems include one (as of November 2026), and how to build a simple portal on top of what you already have if your system doesn't. I work at Mythex, an AI app builder, which is one way to do the last part, so weigh that section accordingly.

What contractors actually use a portal for

Retail customers renting a carpet cleaner don't need a portal. Contractors with house accounts do, and their needs are specific. Talk to five of your biggest accounts and you'll hear the same list:

  1. "What's on rent, and on which job?" One list of open contracts, grouped by jobsite, with the date each item went out and the running cost. This is the number one reason a PM opens the portal.
  2. Extend or call off. A button to request an extension or a pickup, with the date, so the yard gets it in writing instead of a voicemail.
  3. PO numbers and who ordered it. Contractors' AP departments reject invoices without the right PO. If the portal shows the PO and the person who placed the order, half your billing disputes disappear.
  4. Invoices and statements. Download a PDF of any invoice or the monthly statement without calling the office.
  5. More than one person per account. The owner, two PMs, a superintendent and an AP clerk all need access, and the AP clerk shouldn't be able to order a 60-foot boom.
  6. New requests. A simple "I need X at this jobsite on this date" form. It doesn't have to be a full online store; most yards confirm availability by phone anyway.

Notice what's not on the list: online card checkout for every rental, live GPS on every machine, or a mobile app in the App Store. Those are nice. The six items above are what remove the phone calls.

Which rental systems include a customer portal

If you're choosing or replacing your rental system, check the portal before anything else. Based on each vendor's own pages as of November 2026:

  • Quipli lists a customer portal as a standard part of the platform. Its page describes customers viewing rental history and active orders, extending rentals, placing reservations, and viewing and paying invoices, with support for on-account billing and repeat-customer accounts. Quipli says it focuses on construction and general tool rental.
  • Point of Rental has a customer portal in which account customers can see online statements and invoices and review or print their contracts.
  • Larger rental ERPs (for example Wynne Systems' RentalMan or InTempo) are built for multi-branch operations. Their public pages say less about a contractor-facing portal, so ask in the demo exactly what a contractor can see and do, and whether it costs extra.

Whichever system you look at, run this test in the demo. Ask the vendor to log in as a contractor with three open contracts on two jobsites and show you:

  • open rentals grouped by jobsite,
  • the PO on each line,
  • an extension request and where it shows up for your counter staff,
  • a second user on the same account with fewer permissions.

If any of those takes more than a couple of clicks, your contractors won't use it.

If your system doesn't have one: build a thin portal on top

Many yards are on a system that works fine at the counter and has no portal, or one nobody uses. Replacing the whole rental system to get a portal is a big, expensive project. A cheaper option is a thin portal: a small web app that reads a daily export from your rental system and adds the six things contractors need.

The data you need is usually already exportable as CSV from your rental system's reports:

  • customers (account number, name),
  • open contracts (contract number, item, jobsite, date out, rate, PO, ordered by),
  • invoices (number, date, amount, status, PDF link if your system makes one).

You don't need live sync on day one. A file uploaded every morning is enough for "what's on rent"; most contractors check once a day.

Step-by-step with an AI app builder

Here's how that looks in Mythex. You type what you want in plain English, it builds the app with a Postgres database, shows a live preview, and publishes it to a URL or your own domain. The prompts below are the actual ones I'd type, in order.

1. The core portal

Build a customer portal for an equipment rental company that rents to contractors. Tables: accounts, account users, jobsites, open rentals (contract number, item, jobsite, date out, daily/weekly/monthly rate, PO number, ordered by) and invoices (number, date, amount, status, PDF link). A contractor logs in and sees their open rentals grouped by jobsite with days on rent and estimated cost to date, and their invoices with a download link. Add sign-in with email for contractor users, and make sure each user only ever sees their own account's data.

2. Roles inside a contractor account

Each account user has a role: Admin, Project Manager or Accounts Payable. Admins can invite and remove users on their own account. Project Managers can see rentals and send requests. Accounts Payable can see invoices and statements but cannot send rental requests.

3. Extensions, pickups and new requests

On each open rental add two buttons: "Request extension" (asks for the new end date) and "Request pickup" (asks for the date and site contact). Add a "New rental request" form: item or category, jobsite, start date, duration, PO number, notes. All requests go to a Requests list for yard staff with status New, Confirmed or Declined, and the contractor sees the status on their side.

4. The staff side and the daily import

Add a staff area only for our team. Staff can see all requests and change their status, and can upload the daily CSV export of open contracts and invoices from our rental system. The upload replaces open rentals and updates invoices by number. Show the time of the last upload on the contractor's page.

5. Polish

Use our company name and colors, add a jobsite filter, and send the contractor an email when a request is confirmed or declined.

Test it the way your customers will: create two contractor accounts, put two users on one of them with different roles, and try to see the other account's rentals. If you can, fix it before anyone real logs in. Then give it to one friendly contractor for two weeks before announcing it.

What you get, and the honest limits

What you get: a working portal with its own database, sign-in for your contractors that the app builds with that database, a staff area, and a published URL you can put on your own domain (for example portal.yourrentals.com). You can keep changing it by chat.

Limits to know before you start:

  • It's a second system. Your rental software stays the source of truth for contracts and invoices; the portal shows a copy. With a daily CSV, "what's on rent" can be up to a day old. Say so on the page. A live connection is possible if your rental system has an API, but that's a bigger job.
  • Requests still need a human. Extensions and new rentals land in a list; someone at the counter confirms them and enters them in the rental system. That's usually what yards want anyway.
  • Payments. Most contractor accounts pay on terms. If you want card payments in the portal, you'll connect your own payment provider, and that's worth doing only after the basics are in use.
  • Security is your responsibility. Test the "can I see another account" case yourself, use roles, and don't put anything in the portal you wouldn't put on a statement.

For teams

If more than one person at the yard will maintain the portal (say the operations manager and the office manager), put it in a shared team workspace rather than someone's personal account, so it doesn't leave when a person does. On Mythex that's the Business plan (from $50/month): a shared workspace, roles for your own staff, and Google Workspace sign-in for your team if you use Google. There's a page with example rental apps here: equipment rental apps built with Mythex, and plans are on the pricing page.

How to decide

  • Choosing a rental system anyway? Make the contractor portal a demo requirement, and run the four-step test above.
  • Happy with your rental system but it has no portal? Build a thin one on a daily export, start with "what's on rent" and "request extension", and add the rest once contractors use it.
  • Already have a portal nobody uses? Ask three contractors why. The answer is usually one of: they can't find the PO, the jobsite grouping is missing, or only one person per account can log in. Those are fixable.

The test of any portal is simple: after a month, do the 6:45 am calls drop? If yes, it's working, whatever it's built on.

Top comments (0)