What's new in Glovebox

Only for operators in the United Kingdom and Ireland. Nothing changes for New Zealand or Australia.

A business customer's deposit and balance payments each get their own VAT invoice the moment the money is taken: numbered in your invoice sequence, dated to the payment (which is the tax point), showing each line's share of that payment, the VAT at each rate and the total. The customer downloads it from the Documents section of their booking page. Consumers keep the single booking invoice.

Behind the scenes every UK and Irish hire payment now records its VAT as a share of the booking's lines, so a deposit on an Irish booking with reduced-rate hire and exempt insurance carries the right VAT for each.

Only for operators in the United Kingdom and Ireland. Nothing changes for New Zealand or Australia.

Booking confirmation, not a VAT invoice. A VAT invoice issued when a booking is made would fix the VAT on the whole hire that day, months before the money arrives. The booking document is now titled Booking confirmation and says it is not a VAT invoice. VAT invoices are issued for each payment received, and for each paid post-hire charge, with the tax point on them.

Say what a post-hire charge is for. Fuel, a fine or PCN, a toll, cleaning, a late return, damage: the treatment follows the reason, so a charge raised without one is refused. Tolls now have their own type; most toll roads carry VAT.

Arrangement fee on third-party insurance: off by default. Adding your own fee on top of a motor premium makes you an Insurance Premium Tax intermediary who must register. The fee is only itemised if you switch it on in Settings, Localisation and taxes, and confirm you are registered for IPT.

Company customers. In Ireland a business customer's 35 days count across everyone who hires under that business, not just the named driver.

Onboarding. The UK threshold now mentions the next-30-days test, Ireland's says "this calendar year or last", and both say a business not established in the country has no threshold.

Only for operators in the United Kingdom and Ireland who are registered. Refunds to consumers are recorded with their VAT share so your return can be adjusted, with no document. Nothing changes for New Zealand or Australia.

Only for operators in the United Kingdom and Ireland. Nothing changes for New Zealand or Australia.

Business bookings. At checkout, and later from their booking page, a customer can say the booking is for a business and give the business name and VAT number. The VAT invoice then names the business and shows its VAT number above the driver's name. This is the customer's own statement; nothing is inferred.

Onboarding. The "Are you registered for VAT?" question now states your country's threshold: £90,000 in any rolling twelve months in the UK; €42,500 in the current or previous calendar year in Ireland.

Only for operators in the United Kingdom and Ireland. Nothing changes for New Zealand or Australia.

Only for registered operators in the United Kingdom and Ireland. Nothing changes for New Zealand or Australia.

Only for operators in the United Kingdom and Ireland. New Zealand is unchanged; Australia was already switched off under the RBA rule.

New Zealand and Australian signups are unchanged.

Only for operators in the United Kingdom and Ireland. Nothing changes for New Zealand or Australia.

Only for operators in the United Kingdom and Ireland. The export reads the figures on each document and never recomputes them. A hire over 30 days to a private customer who belongs in another country is flagged, because the place of supply moves to that country; the days-outside-country field is for your adviser's use-and-enjoyment apportionment. Neither changes what the customer was charged. Nothing changes for New Zealand or Australia.

Only for operators in the United Kingdom and Ireland whose billing currency is not the tax authority's (for example a Northern Irish operator pricing in euro). Operators billing in sterling or euro see nothing new, and nothing changes for New Zealand or Australia.

Only for operators in the United Kingdom. Nothing changes for Ireland, New Zealand or Australia.

A booking landing used to reach you by email only. Now it also reaches the Glovebox app, if you have it: a quiet notification naming the customer and the reference, which opens straight to that booking.

Quiet on purpose. It will not break through a Focus mode and it will not wake you. A booking arriving at 2am is news in the morning, not an emergency.

It never joins your alerts. The alerts list is for things that are wrong and that somebody closes off. A booking is never resolved, so putting it there would make that list mean two different things at once.

Nothing changes if you do not use the app, and the operator email is unchanged.

Closing a not-recorded movement on the reconciliation screen writes the same thing a handover writes: the hire goes on, or the hire is finished. It is a handover, recorded from the paper sheet instead of at the vehicle.

It was not treated as one. The screen only checked that you belonged to the workspace, so a contractor who cannot run a pickup or a return in the app could still close one here.

Now both ask the same question. Owners, admins and staff can close a movement from paper. Contractors cannot, and a movement they are not allowed to close is skipped rather than failing the whole batch, so the rest of the sheet still goes through.

Until now the first you heard about a hire coming home was either the wall display or the car itself in the yard. Settings › Tracking now has a switch: Tell me when a vehicle is nearly back.

With it on, each vehicle on hire sends one notification when it is about a kilometre from the depot it is due back at and still closing, saying roughly how many minutes away it is. One per return, so a car that spends ten minutes in traffic on the last stretch tells you once.

It uses the same arriving calculation as the ops board wall, so the phone and the wall can never disagree about which cars are on their way in.

Off by default, because it is one more notification for every hire that comes home, and only you know whether that is useful at your volume. These arrive quietly, below the alerts that mean something is wrong, and they do not sit in the alerts list waiting to be actioned: the booking is the thing that needs closing off, not the notification.

Settings › Tracking rebuilds the list of ways alerts reach you out of the boxes on the page. Alerts to the Glovebox app on your phone had no box, so every save quietly deleted them. Change your overdue grace period, and phone alerts stopped, with nothing on screen to say so.

The page now has an On your phone row alongside Email and Text message. It starts ticked, and you can untick it. Workspaces whose phone alerts had already been switched off this way have been switched back on.

Turning it on here does not start notifying anybody by itself. A phone still has to be signed in to the Glovebox app, and each person still chooses which alerts their own phone may interrupt them for.

Three things the Glovebox app can now ask for. Nothing changes on the website, and nothing new is written anywhere: these only read.

Your day. Today's pickups, returns and transfers in time order, with the balance owing and the flight details already on the booking. It comes from the same place as the Coming Up screen and the printed week sheet, so the phone cannot tell you something different from the wall.

Booking search. By customer name, registration or booking reference, the same fields the search box on the website uses.

Your other workspace. If you run more than one brand, the app is told how many urgent alerts are open in each of them, not only the one on screen. Until now there was no way to learn that the other brand needed you without switching to it and looking.

Each of these follows the permissions you already have. Contractors do not see the operator's day or the booking list, which stay with owners, admins and staff.

One quiet fix came with it: the app was told your role in the workspace you had open, and nothing for any other workspace you belong to. It now knows all of them.

Only for operators in the United Kingdom and Ireland. Nothing changes for New Zealand or Australia.

Under Settings, Localisation and taxes there is a new table, What tax applies to each charge. Each kind of charge shows the treatment it carries on new bookings and post-hire charges: standard rate, reduced rate (Ireland only), exempt, or outside the scope of VAT. The defaults come from your country; change a line only on your accountant's advice. Documents already issued keep what they were issued with.

Only for operators in the United Kingdom and Ireland. Nothing changes for New Zealand or Australia.

Confirmation and receipt emails, balance reminders and receipts, bond hold and capture notices, over-mileage and post-hire charge requests, cover upgrade offers and payment requests, airport transfer confirmations, cancellation notices and the pre-arrival guide now print amounts in pounds or euro. The price breakdown says "(ex VAT)" and "Total (incl. VAT)" when you are registered, and carries no tax wording at all when you have told us you are not. The "Amount (NZD)" line on receipts shows your own currency code.

Only for operators in the United Kingdom and Ireland. Nothing changes for New Zealand or Australia.

VAT invoices. A registered operator's invoice is titled VAT invoice, shows your VAT number, the tax point, each line's net amount and VAT rate (standard, reduced, exempt, or outside scope), the VAT at each rate, the total VAT, and the total, all in pounds or euro. Exempt and outside-scope amounts are shown on their own and never counted in the VAT.

Not registered? No VAT, anywhere. If you told us you are not VAT registered, your documents are a plain Invoice or Receipt: no VAT number, no VAT line, no "incl. VAT" wording.

Post-hire charges and over-mileage receipts print from their own figures, so a fuel recharge in Ireland shows 23% while the hire shows 13.5%.

Quotes and rental agreements use your currency and say "incl. VAT" where it applies.

Only for operators in the United Kingdom and Ireland. Nothing changes for New Zealand or Australia.

The booking widget now prints every price in your currency: the daily rate and total on each vehicle card, the early estimate, extras and protection options, location fees, the one-way fee, the running total and deposit, and promo-code savings. Rounding and layout are exactly as before; only the symbol follows your country.

Only for operators in the United Kingdom and Ireland. Nothing changes for New Zealand or Australia.

Customer portal. Every amount a customer sees on their booking page (the total and what it includes, extras, protection and insurance, the excess, bond messages, additional charges and the pay-balance button) prints in pounds or euro. Tax wording follows your registration: "(incl. VAT)" and "Includes VAT of …" when you are registered, and no tax wording at all when you have told us you are not.

Your website. All five themes print "From £149" (or €) on fleet cards, group and vehicle pages, the sticky mobile bar and the booking page, with "incl. VAT" or nothing beside it. The "(NZD)" note on vehicle pages now shows your own currency code.

Only for operators in the United Kingdom and Ireland. Nothing changes for New Zealand or Australia.

Each line carries its own VAT treatment. A booking is no longer taxed as one lump. Hire, extras, protection, insurance, fees, and later each post-hire charge, is recorded with the treatment it was sold under: standard, reduced, exempt, or outside the scope of VAT. Insurance from a third party is exempt, and when the cover has a premium and an arrangement fee they are shown apart. A fine or toll passed on is outside scope; damage is too. The defaults come from your country and can be adjusted later.

Ireland's 35-day rule, worked out for you. A passenger-vehicle hire takes the reduced rate when this hire plus the same customer's hirings from you in the past twelve months come to 35 days or fewer; longer than that, or any van or pick-up, takes the standard rate. Mark a vehicle group as a goods vehicle in Fleet, Vehicle groups. If an accountant tells you otherwise for one booking, the Hire VAT rate field on the booking pins it.

Post-hire charges ask what they are for. Fuel, a fine or toll, cleaning, a late return, damage, or other: pick one when you raise the charge and the right treatment follows.

A retained cancellation fee is recorded as a taxable supply, ready for the documents that come next.

Only for operators in the United Kingdom and Ireland. Nothing changes for New Zealand or Australia.

Glovebox's default rental agreement is a New Zealand-law document. For a hire in the UK or Ireland it is the wrong contract, so it is no longer generated there. Add your own terms, or link to them, under Settings, Rental agreement; the banner on your dashboard says so until you do.

Until then, a booking that would normally get an agreement is marked as not having one, with the reason shown on the booking, and you are emailed. Payments, confirmations and everything else carry on as normal.

Sometimes you want to know about one particular vehicle: the car that keeps going missing, the one on loan to a friend of the business, the one you simply want to keep an eye on this week. Open the vehicle, and under Status & access turn on Tell me when this vehicle starts and stops moving.

From then on that vehicle tells you when it pulls away, and tells you again once it has been parked for five minutes. The wait before the stop is deliberate, otherwise every red light and every petrol station would be a notification. These two arrive quietly, below the alerts that mean something is wrong, and they do not sit in the alerts list waiting to be actioned: a vehicle pulling away is news, not a job.

Leave it off for the rest of the fleet. Across every vehicle it would be dozens of notifications a day, and the one alert you need to see would be buried in them.

It works on movement rather than ignition, because that is what the trackers report reliably. On one vehicle we checked over three days, movement was on every single position and ignition on about one in seventy, often arriving only once the vehicle was already up to speed.

Until now, anybody who could sign in to your workspace could open a pickup or a return and complete it, whatever their role. That included contractors, who are usually cleaners and prep staff rather than counter staff.

That is fixed. Roles now decide:

• Contractor cannot run a handover, charge damage or release a bond. Handover buttons no longer appear for them.
• Staff can run pickups and returns, release a bond in full, and charge damage. Every damage charge is recorded against the person who entered it.
• Owner and admin can do all of that, and are the only roles who can mark a hire complete when no handover was recorded.

Two things are now written down that were not before: who released the bond, and who recorded the damage. Both appear on returns completed from today. Earlier records show no name rather than a guessed one, because a guess in an audit trail is worse than a blank.

Nothing changes for an owner or an admin working on their own, and no existing booking was altered.

The app could tell you something was wrong. It could not tell you where everything was.

Fleet is a new tab. The map at the top shows every vehicle that has reported a position, with anything needing attention marked in red. Under it is the full list, in the same order, and each row opens that vehicle: its map, where it has been recently, and the hire it is on.

Two switches live on that page, and they used to be on the website only:

• Starts and stops moving, the watch for a vehicle you want to keep an eye on this week.
• Nearly back at the depot, which can now be set per vehicle rather than for the whole workspace. A vehicle follows the workspace setting until you decide otherwise, and there is a button to put it back to following along.

Only an owner or an admin can change them. Staff can see the map and the list, because knowing where a vehicle is helps anyone, but choosing which vehicles raise alerts changes what everybody else's phone does.

The states on the map and in the list come from the same place as the fleet page on the website and the ops board, so the phone and the wall cannot disagree about whether a vehicle is overdue.

Unauthorised movement was by far the loudest alert, and almost every one was a staff car on a real errand. Open a vehicle and, under Status & access, turn on Expected to move without a booking for staff, courtesy and shuttle cars. Movement Glovebox can already explain, such as a transfer or a service job, no longer alerts either, and one journey is one alert: it stays open between stops and closes once the vehicle has been still for half an hour.

The power cut alert had never fired. It now reads what the trackers actually send, but only for a tracker you have marked as wired to constant 12V, because on an ignition-switched feed losing power just means the engine is off. Settings › Tracking lists each tracker as Constant power or Confirm wiring; until you confirm a unit, its alert stays silent.

Overdue alerts stop at 48 hours, after which a booking is unclosed paperwork rather than a late car. Who acknowledged and who resolved each alert is now recorded against it.

Leave the dashboard open on a screen and it now stays current on its own.

Every minute: today's pickups, returns and on-hire count; the flight board; the activity feed; and the fleet map.

Every five minutes: Next up, Needs attention, Coming up and Latest bookings.

A card only refreshes while it is actually on screen, so a long dashboard scrolled past does not keep asking for cards you cannot see, and a tab you have left in the background slows right down rather than refreshing at full rate.

If you had got into the habit of reloading the page before a handover to make sure the list was current, you no longer need to.

Pickup had a fixed set of six photo slots and return had a single free-form upload, so the two could not be compared angle for angle. Both flows now walk through the same guided tiles, twelve by default: front 3/4, driver side, rear 3/4, passenger side, windscreen, wheels and tyres, underbody, roof, interior, cargo area, odometer and fuel, and existing damage. Add more photos takes anything beyond the tiles, at either end.

At return, each tile shows the pickup photo faded behind it, so you are matching the shot rather than remembering it. The return is saved as a handover record of its own, alongside the pickup.

If a location needs a different set, open it under Settings › Locations and fill in Guided photo slots on its Handover tab. Leave it empty to keep the standard set.

When an extra came off a booking the customer had already paid, the booking kept saying Paid in full and nothing offered the difference back. The header badge now reads Overpaid by the amount, and the Payments tab shows an Overpaid card with a Refund overpayment button. The amount defaults to the overpayment and cannot exceed it; give a reason and Glovebox refunds it against the most recent card payment with enough left, records it on the ledger and the timeline, and brings the paid figure down to match.

Refunds now also count against what was paid wherever the paid figure is shown, so a booking that has been refunded no longer reads as fully paid.

The dashboard had no path into the pickup or return flow. Every row linked to the booking page, and you went looking from there. Now a Next up card sits at the top with the next three movements that are actually waiting on someone, each carrying the step it needs: Start pickup on a confirmed booking, Start return on a hire that is out, with Call and View booking beside it. Every row in the upcoming list carries the same button.

A return past its time reads in red as Overdue with the time it was due. A return whose pickup was never completed keeps its row and says why the button cannot start yet, rather than looking live and bouncing you back. The card looks across the whole upcoming range, so a quiet afternoon still leaves an entry point to tomorrow's first pickup, and it disappears when nothing is waiting.

Updated 1 October: the surname now comes first and the reference is shortened to its last four digits; see "The fleet calendar is easier to read at a glance".

Every booking bar on the fleet calendar has been relabelled. Where it used to show a first name and the last four characters of the reference, it now shows the full reference, the surname, and the route.

The reference comes first because it is what you search for and what you read out on the phone, and it is now shown in full rather than cut to its last few characters. The surname comes next because a busy month has four Sarahs in it and only one Rangi-Thompson. The route comes last, as CHC→AKL for a one-way, or @OAM for a hire that starts and ends somewhere other than the vehicle's usual base. A hire that begins and ends at the vehicle's own base shows no route at all, because that would only repeat the row it is already sitting in.

Narrow bars drop parts rather than shortening them, so you will never see half a reference — a short bar shows just the surname, and a very short one the customer's initials. The full detail is always on the hover card.

If your depots do not have short codes yet, the location settings page now suggests one from the name as you type, and tells you that the code appears on calendar bars. Codes are limited to six characters and stored in capitals, which is how they have always been displayed — previously a longer code could be saved and then quietly appear shortened.

On the fleet calendar you can now pick a booking up and drop it where you want it. Drag it sideways to shift its dates, or drop it on another vehicle in the same class to move it onto that van. An unallocated booking can be dragged straight onto a vehicle to allocate it.

Dragging never saves anything on its own. Letting go opens a summary of exactly what would change: the old dates and the new ones, the old vehicle and the new one, anything that would stop the move, and what it does to the total. Nothing is written until you press Move booking, and everything is checked again at that moment — so if somebody else took the van while the summary was open, the move stops rather than double-booking it.

You choose how it is priced, the same way you do when you change a hire's dates on the booking itself, and with the same default — keep the booked price:

• Keep the booked price. The total the customer agreed to. Nothing about the money changes.
• Keep their daily rate for the new dates. Their rate times the new number of nights: no season change, no last-minute premium. Useful when you are moving a booking to suit yourself.
• Reprice at current rates. Quote the new dates as if booked today.

Each option shows the total it would produce, so you are choosing between numbers rather than guessing. If you pick Reprice at current rates and the booking's stored total has drifted from what your rates say today, the modal tells you how much of the change is the move and how much is that gap closing — the gap is already there and gets applied by any repricing, whether you move the booking or not. Keeping the booked price or their daily rate leaves it alone. For a bespoke amount, open the booking.

A few moves are refused outright, because the calendar is the wrong place to make them: dropping a booking on a different vehicle class, moving a completed or cancelled booking, and swapping the vehicle on a hire that is already out. A booking where the customer chose that specific vehicle asks you to tick an override before the swap goes through. On a touch screen the same swipe is how you scroll the calendar, so dragging is a mouse and trackpad gesture.

The fleet calendar page was printing its name twice — once as the page heading and again at the top of the calendar itself — and on the one screen where vertical space turns directly into visible vehicles, that cost about three rows. There is now one title.

On a 1920×1080 screen in compact density you should see 30 vehicle rows where you saw 26.

Separately, the main navigation sidebar can now be collapsed on desktop. Use the toggle beside the workspace name; it shrinks to an icon rail and your choice is remembered. On a 1440-wide laptop that hands about 160 pixels back to the grid, which is another couple of days of fleet on a normal week view and considerably more on the longer ranges.

Nothing is hidden by either change. The sidebar starts expanded exactly as it does now, so if you prefer the labels you never have to touch it.

The fleet calendar has two new range buttons alongside Day, Week and 30 days: 90 days and 180 days. They work the same way as the others, starting from whatever date the calendar is showing.

This is for the planning you do before a season rather than the dispatch you do on the day. At 90 or 180 days you can see where the gaps are across the whole fleet, which vehicles are quiet in the shoulder months, and how the one-way runs stack up over a summer, without clicking forward a fortnight at a time and trying to hold the picture in your head.

A few things change at those widths because the columns get very narrow. Dates along the top are labelled weekly instead of daily, so the row stays readable. The depot colour strip along each vehicle row is hidden past 60 days, where it is too thin to tell one depot from another. The bars themselves, their colours, the one-way arrows and the hover card all work exactly as they do in the shorter views.

Day, Week and 30 days are unchanged.

Every group heading on the fleet calendar — 2 Berth, 4 Berth and so on — now shows a count for each day across the timeline: how many of that class are still free to sell.

A day where nothing is left shows a red 0. A day down to its last vehicle or two is amber. Everything else is a plain grey number. Hovering any of them spells it out — "4 Berth: 2 of 6 free".

The count subtracts everything that stops a vehicle going out: hires, holds, maintenance and transfer legs. It also subtracts unallocated bookings, because those already have a customer and will take one of the vehicles as soon as somebody assigns a plate. So the number is what you could still sell, not how many rows happen to look empty.

It sits inside the group heading rather than adding a row of its own, so it costs you nothing in visible fleet, and it is worked out from exactly the same bars drawn underneath — it can't drift from what you can see.

Clicking a booking bar on the fleet calendar opens its detail panel. That panel now carries the two actions you actually use while looking at the grid:

Start pickup appears on a confirmed booking and takes you straight into the handover screen.

Start return appears on a booking that is on hire. If the pickup handover was never completed, the button is shown greyed out with the reason underneath — "Complete the pickup handover first" — rather than looking available and then bouncing you back.

Everything else is one click away on Open booking, which is deliberate. The booking page has a great many actions and copying them all onto the calendar would just make a worse version of that page. The calendar keeps the handful that belong with a grid view.

Unallocated bookings keep the existing "Allocate vehicle" picker, and the Call button is unchanged.

The thin coloured strip along the bottom of each vehicle row tells you which depot the vehicle is at. Until now it drew every position the same way, and it was drawing three quite different things.

Solid now means confirmed: somebody recorded a handover at that depot, or marked a transfer leg completed.

Dashed means assumed. The booking says the vehicle should be back — it went out and was never checked in, or no handover was recorded at either end and the return date has passed — so it is probably at that depot, but nothing has confirmed it. This is usually right. It is also exactly the case where a one-way fleet loses track of a vehicle, so it is now visibly a weaker claim rather than looking identical to a confirmed one.

No strip at all means nothing has been recorded for that vehicle yet. Previously it drew a solid strip at the vehicle's configured base, which read as "this vehicle is at Christchurch" when all it really meant was "Christchurch is where this vehicle is set up to live". The base is still shown on the row's location chip, which is what that chip has always been for.

Hovering any segment tells you which of these it is. The legend has been updated to match.

Nothing about where vehicles actually are has changed — only how plainly the calendar admits what it knows.

A pass over the fleet calendar grid, aimed at what you can take in without stopping to decode it.

Bookings lead with the name. A bar now reads Tu'ipulotu · 3102 rather than KO-3102 · Tu'ipulotu, and the reference is shortened to its last four digits. Every reference on your screen starts with the same prefix and differs only at the end, so a column of them all looks alike; names don't. The full reference is still on the hover card and the booking itself.

Weekends are shaded and each column shows its weekday, so you can see the shape of a week without counting across. Today is a green circle on the date.

The availability row above each group only prints a number when it matters — a red 0 when you're sold out and an amber 1 when you're down to the last one. Days with two or more free are a plain tint with no digit, because a row of 3s and 4s competes with the bookings underneath for your attention. Hover any day for the exact count and date.

The vehicle column is leaner. The model name is gone from each row — the group heading directly above already says it — which fits about three more vehicles on screen. In compact density the plate and the branch code now share one line. Group headings read "12 vehicles · 83% booked" rather than "· 12 · 83%".

The thin depot-coloured strip along the bottom of each row has been removed. At that height it read as a dotted underline rather than a timeline, and on a multi-branch fleet every row had one. Where each vehicle is still shows in its row, and a branch change still shows as "CHC → AKL". The gap between two hires is now a subtle hatched block in line with the bars, so it reads as time the vehicle isn't available rather than as another booking.

The fleet calendar used to be held to the same width as every form and list in the admin — a sensible limit for a page of text, and a waste on a timeline where each extra centimetre is another day on screen. On a wide monitor roughly a thousand pixels sat empty beside it. The calendar now spans the full width of the window.

Its height was fixed too, which was wrong in both directions. On a laptop the timeline ran past the bottom of the screen, so the last rows could only be reached by scrolling the whole page — which pushed the date header out of view as you went. On a tall monitor it stopped short and left blank space underneath.

The timeline now measures where it sits and fills whatever is left of the window. On a 2560×1440 screen that is about 78% more width and 28% more height than before, and everything stays reachable inside the calendar's own scrollbar instead of moving the page around. Because it measures rather than assumes, it keeps adjusting as the controls above it change.

The fleet calendar shows bookings with no vehicle yet in a lane above each group's vehicles. Until now that lane looked identical in two situations that mean quite different things.

If a group sells by class — you take the booking by berth size and pick the plate later — that lane is just your normal working list. It stays amber and reads "Needs allocation", as it always has.

If a group sells a specific vehicle, a booking sitting there with no vehicle is a mistake: you promised that van and nothing is assigned. Those now show a red warning and read "No vehicle assigned", so they stand out instead of blending into routine work.

Unpaid bookings awaiting payment are unaffected on both kinds of group. They keep their own muted row, because chasing an allocation for a booking that might still lapse isn't work worth creating.

Self-collection asks the customer to photograph the vehicle before it gives them the lockbox code. That set included a dashboard shot and a fuel-gauge shot, and both of those need the customer to be inside the car, which they cannot be until they have the key.

The fuel gauge was the clearest case: on most vehicles the instrument cluster is dark with the ignition off, so there was nothing to photograph even with the doors open. Whatever was being submitted to get past that screen was not a usable record of the fuel level, which matters if fuel is ever questioned at return.

Those two photos have moved. The walk-around now asks for the four outside angles only, and the dashboard and fuel gauge are captured at the end, on the same screen as the odometer, once the customer is in the car with the key. They hold the "good to go" screen the same way the odometer does, and the "I can't read the odometer right now" button still records whatever was captured if something is genuinely unreadable.

Nothing about the lockbox code changes: it is still released only after the outside photos, the bond and the signed agreement. A customer part-way through a pickup when this lands keeps any dashboard or fuel photos they already took and will not be asked for them again.

Your automated emails, the pre-arrival reminder, the pickup-day reminder, the pre-check-in invite, the balance-due warning and the rest, go out in a batch. If one customer's email address had been marked undeliverable (usually a long-dead address that had bounced before), that single address could make the whole run stop, so other customers silently missed their reminder.

That's fixed. A bad address is now skipped on its own, the rest of the batch carries on, and the address is remembered so we don't keep trying it.

When an address is undeliverable, the booking now shows "Email not deliverable" so you can see it at a glance. If the customer gives you a corrected address, updating it clears the flag automatically, and there's a "Retry this email address" button on the booking if you want to try the same address again.

Nothing changes for customers whose email works. This only affects addresses that were already bouncing.

If your rates are GST-inclusive, the rate you set is the price your customer pays, so a three-day hire should be exactly three times it. On some hire lengths it came to a cent less: a $179/day vehicle quoted $536.99 for three days instead of $537.00.

The engine was converting the inclusive rate to a GST-exclusive figure and back again, and losing a cent in the rounding. It now works from the inclusive price directly, so the total is the rate times the days, every time, and the GST line and the ex-GST subtotal always add up to it.

The GST line itself was also being rounded down rather than half-up, which understated it by a cent on some amounts. That is corrected too, so what you declare matches what you charged.

Bookings already taken are unaffected. This changes new quotes only.

Operators in New Zealand and Australia are now always set to GST-inclusive pricing, since both countries require customers to be shown a price with GST in it.

When you set a vehicle group to Individual vehicles, your Glovebox booking page already showed one card per car. The fleet grid embedded on your own website did not: it still showed one tile for the group, so the cars were bookable individually but invisible individually.

That grid now matches. Each bookable car in an individual-mode group appears as its own tile, with its own photo where it has one, its own price for the dates searched, and a Book button that opens the booking page with that car already chosen.

Groups sold as a class are unchanged: one tile, one "from" price, because the customer is buying the class and any car in it will do. A fleet with some of each shows both, side by side.

Two things worth knowing. The tile shows the car's make and model, never its registration plate, which stays a fleet-internal detail. And if you want to link to one specific car from a Facebook post or a page you built yourself, every vehicle has its own page on your Glovebox site with photos, specs and a Book button that pins that car.

Full details in the help centre: Sell individual vehicles instead of a class.

Until now every vehicle group was sold the same way: the customer booked the group, any vehicle in it satisfied the booking, and you assigned the car. That is right for a fleet of interchangeable cars, and it is unchanged.

It was wrong for operators whose vehicles are genuinely different to a customer. The advice was to put each differently-priced vehicle in its own group, which worked but left you managing a group per car.

Each group now carries a Sell as setting.

Vehicle class is today's behaviour, and remains the default for every existing group. Nothing changes unless you choose otherwise. Class cards now say "or similar" after the group name, so it is clear a customer is booking a class rather than the pictured car.

Individual vehicles sells the car itself. Each vehicle in the group appears on your booking page as its own card, with its own photo and its own price for the dates searched. A vehicle can carry its own daily rate, and leaving it blank falls back to the group rate. Seasonal, length-of-hire and day-of-week pricing all still apply on top, so the per-vehicle rate is the starting number and not the final one.

Because the customer bought that specific car, the booking is locked to it. Automatic reallocation skips it, and changing the vehicle on the fleet calendar or the booking page asks you to confirm first, naming both cars. When you do change it the booking is repriced at the new car's rate, you are shown the difference, and both vehicles are written to the booking's history.

Switching a group back to a class is allowed at any time. Bookings already taken stay locked to their car, because changing a setting does not change what those customers were sold, and you are told how many.

A vehicle saved without a group now gets a group of its own automatically rather than being refused. Two commands help with the tidy-up: vehicles:assign-orphan-groups gives existing groupless vehicles a group (and reports before it writes anything), and vehicle-groups:single-vehicle-report lists the one-car groups you may want to merge back together.

Full details in the help centre: Sell individual vehicles instead of a class.

Four things on the tracking maps, on the booking Tracking tab and on Fleet tracking.

Top speed now shows during the hire. There was already a top speed figure, but it was only worked out at check-in, so it sat empty for the whole hire and only filled in once the car was back. It now reads the tracker's own records as they come in, so you can see the highest speed so far while the car is still out, along with when it happened. It covers the whole hire, and if you swap the vehicle partway through you see only the speeds from the car that is actually on the booking.

The route draws in red. The trail showing where the car has been used the same green as the dot showing where it is now, so the two ran together as one colour. The trail is red now and the current position stays green, so it is obvious which is which.

Open in Google Maps. The satellite imagery we use has no street names on it, so "where is it exactly" often meant guessing from the shape of the roads. There is now a button on the vehicle card and on the booking Tracking tab that opens that exact position in Google Maps, with street names, in a new tab.

Clicking a vehicle no longer hides it. On Fleet tracking, clicking a car in the list zoomed to it but put the dot underneath the detail card on the right. The map now allows for the card, so the vehicle lands in the part of the map you can actually see. Fit fleet does the same.

The map on your dashboard, and the one on Fleet tracking, could come up as an empty box: the frame and the LINZ credit were there, but no map underneath and no vehicles on it.

It depended on how you got to the page. Opening it fresh, or reloading, worked. Clicking through to it from somewhere else in the admin, which is how you would normally get there, could leave the map blank until you reloaded. It was more likely on a phone.

Both maps now wait for the mapping library to finish loading instead of giving up on it, so they draw either way. Nothing about your vehicles, positions or alerts was affected: this was only ever the map failing to draw.

Ask Claude to read your site and it sees what Site Studio sees: the theme and brand colours, every built-in page's words (home, fleet, about, FAQ, terms), contact details, socials and opening hours, the menu, and whether the site is live, with the preview link.

Then tell it what you want. "Make it the Coastal theme with our navy." "Write the about page: two vans in 2019, twelve today, airport pickups." "Add an FAQ about taking the van on the ferry." "We're closed Sundays." "Publish it." Each proposal comes back as a preview with the before, the after, any warnings (a very light brand colour, a headline that will wrap on a phone, a site going live with no rated vehicle group yet) and a link to the page. Nothing is saved until you say yes in the conversation.

One thing to know: a Glovebox website has no draft copy. Once the site is live, a change you confirm is public straight away, exactly as saving in Site Studio is, so look at the preview first. Logo, favicon and photos, custom domains, custom pages and customer reviews stay in the admin.

Ask Claude "what do I need to do this week?" and it reads the same Coming Up sheet and dashboard you do: every pickup, return and transfer by day with the customer, the vehicle, any balance owing and anything to fix first; the Needs Attention list (overdue returns, unpaid deposits, unsigned agreements, missing licences, bonds not held); and the fleet items falling due, such as a WoF expiring, a low RUC balance, or a service overdue.

Ask "how's the fleet?" or "what's due on #8?" and it lists each vehicle's WoF or CoF, rego and insurance dates, its RUC balance against your threshold, its service schedules with what is due by kilometres and by date, any open jobs, whether it is off the road, and the last odometer reading. "What's been done to #8?" gives the completed jobs with cost, provider and invoice reference.

If you allow changes, Claude can also record an odometer reading, top up RUC, log a service or repair as done (the schedule's next-due rolls forward and the vehicle comes back on the road), or book a vehicle in for work with an off-road window. As with every change through the connector, it shows you the before, the after and any warnings, such as a booking an off-road window would collide with, and applies nothing until you say yes. Servicing needs the Maintenance module on.

A new opt-in module lets you connect Claude (Desktop, Code, or claude.ai) to your own workspace. Generate a token under Settings › Claude connector, add it to Claude (for claude.ai, add a custom connector at https://mcp.getglovebox.co.nz/mcp and paste the token when asked), and ask things like "what's picking up this week", "revenue last month" or "how many Jimnys are free over Labour weekend".

Everything is read-only for now, and every answer comes straight from your own bookings, payments and availability. Revoke a token at any time, or switch the module off to stop every token at once.

When you generate a Claude connector token you can tick "Allow changes with this token". Claude can then propose three kinds of change: close a location on certain weekdays or dates, set the minimum booking lead time, or add a seasonal percentage rate for a date range.

Nothing is applied on the first pass. Claude shows you what would change, including anything it would override, and only applies it after you agree in the conversation. Every applied change is recorded on your workspace timeline, and seasonal rates added this way are capped at ±50% and marked as coming from the connector in Pricing.

Existing tokens stay read-only.

Add the Glovebox connector in Claude, click Connect, and you are brought to Glovebox to sign in with your usual account. Tick the workspaces you own, choose whether Claude may propose changes, and you are back in Claude. Own more than one business on Glovebox? Tick them all and Claude sees them on one connection.

Nothing to copy or paste. Each connection shows up under Settings › Claude connector, labelled with the date you signed in, where you can revoke it. Generating a token by hand is still there under "Advanced" for scripts.

Ask Claude something like "what should a 5-door cost over Christmas?" and it reads your demand pricing engine's suggestion for that group and those dates: the base rate, the suggested rate, and the reasons (how full the group is, how far out the dates are, how bookings are pacing). It works even if you keep the engine switched off, as advice only.

If you like the suggestion, say "apply it". Claude proposes a rate adjustment for that group and date range, shows it to you first, and applies it only after you say yes. Whatever is proposed is held inside the group's rate band from the demand pricing page. If the suggestion would go past your floor or ceiling, Claude says so and applies the bounded figure instead; only you can widen a band, and only in Glovebox.

Applied adjustments appear in Pricing marked as coming from the connector, and on your workspace timeline.

Use Claude with your workspace, under Help › Guides, walks through connecting Claude by signing in, what it can read (bookings, revenue, fleet, availability, locations, embed snippet), the four kinds of change it can propose with your approval, and how to disconnect.

The privacy policy now lists Anthropic (Claude) under "Who we share it with", with the same rule the connector applies: nothing is shared unless a workspace owner connects, and disconnecting stops it.

The flight data provider offers a predicted arrival based on a route's past performance, not live tracking. It was being shown as an estimate, which is how JQ171 read four minutes early all afternoon while it was running late.

Now only a real revised time from the airline or airport counts as an estimate. Without one, once the flight has departed the departure delay is carried across to the scheduled arrival; before departure, only the schedule is shown.

Every flight number on the dashboard's Flights card is now a link. It opens the flight on FlightAware in a new tab, showing where the plane is right now, so you can check an arrival before heading to the airport without leaving Glovebox.

Only real flight numbers are linked (an airline code and a number, like JQ171 or NZ0247). If a customer has typed an airline booking reference into the flight field instead, it stays as plain text.

You need time to roster a driver. Under Settings › Booking policies, set how many hours before pickup an airport transfer can still be added. Inside that window the transfer is withheld and the booking page says why, so customers are not left guessing.

Off by default; existing bookings are untouched.

A new setting under Settings › Website, called Your website, lets you say whether bookings run on your own website (with the embedded widget and fleet catalogue) or on a Glovebox-hosted site built in Site Studio.

It is a preference, not a migration: switching never publishes, unpublishes or deletes a site, it only changes which tools Glovebox puts in front of you.

Parking notices come to the registered owner, long after the driver has gone. FinePass closes that loop.

Switch it on under Revenue › FinePass. When a notice arrives for a vehicle that was on hire, Glovebox matches the plate and time to the booking and shows you a one-question review. Confirm it, and FinePass sends the notice to the driver with your handling fee added, chases payment, and pays you out through Stripe. The parking company only learns who the driver was once the cycle completes, and no customer list ever leaves Glovebox.

The module checks your rental agreement carries the disclosure clause before it connects.

If you embed both the fleet catalogue and the booking widget on your own website, the catalogue's Book now buttons and date search used to send customers to the Glovebox-hosted booking page. You can now set your own booking page URL under Settings › Website, and every link on the catalogue uses it. The vehicle group is carried across so the customer lands on the right car.

The Fleet app now has a bottom tab bar (Vehicles, Overview, Prep, Settings), and Prep this week is finally reachable from it.

Each vehicle card carries a due line, worst first: COF expired 12 Sep, RUC 900 km, Rego 3 Oct. Critical items are red, attention items amber, and a healthy vehicle shows its nearest expiries. A state chip says whether the car is on hire, in the yard or in transit.

On iPhone, the home-screen icon now opens already signed in instead of asking you to log in again.

Free Legs used to ride along with the Transfers module, so every operator with transfers saw Send to Free Legs whether or not they had an account. It is now its own module in the marketplace, free to switch on, with a Settings › Free Legs page showing your connection status and fleet mirroring. With it off, nothing Free Legs shows or runs.

If you were already signed in and opened your workspace's login page — from a bookmark, a link in an email, or just a new tab — Glovebox signed you out, showed the login form with your email filled in, and signed you back in when you submitted it. That looked harmless, but it invalidated every other Glovebox tab you had open: the next time you pressed save in one of them you got "Error while loading page", and your changes were not saved.

This is what was behind the report of the rental terms "reverting" after long edits. It could hit any page.

Now, opening the login page while signed in simply takes you to your dashboard. Nothing else changes.

If you have been caught by this: your saved content is intact, but edits made in a tab that showed that error did not go through. Reload the page before editing again.

If your website is on a getglovebox.co.nz address, its Fleet page — and the results page a customer lands on after picking dates on your homepage — returned a blank "403 Forbidden" from about 11pm on 14 September until this fix was deployed. Sites on your own custom domain were not affected.

The cause was a folder added for the Fleet mobile app that happened to share its name with your website's /fleet page, so the web server answered before Glovebox could. The folder has been moved, and there is now an automated check that stops any future folder from colliding with a page on your site.

No action needed on your side. If a customer told you the search "went to a 403 page", this was it.

iPhones save photos as HEIC by default. Glovebox accepted them but the upload preview refused the format, so the upload failed with an error. Fixed: HEIC and HEIF preview and upload like any other photo.

If you pasted your rental terms into the onboarding box as plain text, every consumer treated them as HTML and collapsed them into a single run-on block: the Settings editor, the rental agreement PDF, your public terms page and the Free Legs transfer agreement. Blank lines now become paragraphs and single line breaks are kept, everywhere the terms appear.

Two fixes to the cover upsell emails your customers receive before pickup:

• The "Upgrade cover" button opened an error page. The link in the email pointed at a host where the upgrade page could not work out which operator the booking belonged to, and failed. The page now resolves the operator from the booking itself, so every link — including the ones already sitting in customers' inboxes — works.
• The upgrade offer appeared twice. The email listed the same "Upgrade to Premium Excess Reduction" line two times. It now appears once. If you have customised the email template and left out the offer list, it is still added for you as before.

No action needed on your side.

Australian rental operators can now run on Glovebox. Signup asks for your country and your ABN, charges are taken in AUD and settle in your own Stripe account, invoices sync to Xero with Australian GST, and every time you see is in your own timezone.

New Zealand operators see no change.

Prices are stored ex-GST at two decimals and shown inclusive, and grossing them back up could land a cent out: a $90 a day by 19 days line printing as $1,710.02. The Pricing tab now derives each line from the inclusive figures the customer was charged, so the lines and the total agree.

The emails you get while setting up Glovebox were written for the old 90-day trial, so a few of them said things that are no longer true.

What changed

• No setup email mentions a trial or counts down to a date, because nothing expires.
• The "try booking your own vehicle" email used to say your booking page was live and that the payment went into your own account. Neither is true in a sandbox: the page is not public, the card payment runs in test mode and nothing is charged. It now says so plainly.
• Your welcome email states the sandbox rules in one line, so it is clear from the start that bookings are test bookings and no emails reach your customers.

One new email. Once your workspace can actually take a booking, you get a single message explaining what going live does — public booking page, live card payments, customer emails switched on — and what your plan costs, at your own fleet band's price. There is no deadline attached to it, and it is never sent to operators who are already trading or already live.

Editing a booking that already has a tax invoice no longer rewrites that invoice. Glovebox issues a new, sequential invoice number, keeps the superseded version, and shows both on the booking's Documents tab and in the customer's portal.

Xero stays consistent: an unpaid invoice is voided, a paid one gets a credit note, and the new invoice is synced in its place. Only money changes trigger a new version, so fixing a name or a note leaves the invoice alone.

Repricing also gained an option to keep the customer's original daily rate when the dates change.

Opening Go live from the sidebar returned a server error rather than the page. This affected every workspace, whatever state its billing was in, so nobody could reach the page that starts a subscription.

If you tried to go live recently and hit an error, nothing went wrong with your workspace or your billing. The page itself was failing to load, before it had read anything about your account. Nothing was charged and nothing was half-finished, so you can simply open it again and carry on.

The page now loads for every workspace, including grandfathered founding members, whose message about keeping their existing arrangement appears as it should.

Plenty of operators already have a website they are happy with and only want the booking engine, so they embed our widget rather than publish a Glovebox site. Until now the system did not count that as being ready to take bookings.

What that meant. If the widget was your booking page, your setup was treated as unfinished no matter what you did. The Go live page told you to publish a booking site you had deliberately chosen not to use, and it never offered you the button to start your subscription. Because going live was out of reach, your workspace stayed a sandbox, and in a sandbox every booking is recorded as a test booking, so a real customer could book through your widget without a payment being taken.

What changed. Having the widget embedded on your own site now counts exactly the same as publishing a Glovebox site. Either one satisfies the "somewhere to book" requirement, so you can go live on whichever you actually use. The setup checklist item now reads "Give customers somewhere to book" and ticks for either, and the Go live page names both options instead of only ours.

Nothing changes if you use a Glovebox site. This only widens what counts, it does not remove anything, and the other requirements are untouched: you still need a vehicle, a pickup location and a connected payment gateway.

Your Glovebox website has a proper Business info section now, under Website → Business info: your street address, opening hours (set per day, mark days closed), social links, a short one-line intro, and a map pin (latitude/longitude).

Fill it in and it flows through your whole site:

• Footer — your address, a click-to-call phone number, your socials and quick links appear on every page (no more near-empty footer).
• Contact page — a real address, an opening-hours table, your socials, and an embedded map, alongside the enquiry form.
• Header — a tap-to-call phone number.

Behind the scenes it also gives Google a much richer picture of your business — a LocalBusiness profile with your address, map location, opening hours and social profiles, plus proper breadcrumbs on your fleet and category pages. That's the kind of structured data that helps you turn up in local search and maps.

Nothing changes until you fill it in, and anything you'd already entered as free-text contact details still shows.

The homepage editor (Website → Pages → Home) has new trust sections you can turn on to help visitors book with confidence:

• Why choose us — a short strip of reasons to book with you (fair pricing, a well-kept fleet, quick booking — edit them to suit).
• How it works — the steps a customer follows, shown numbered, so first-time visitors know what to expect.
• Customer reviews — add real quotes from your own customers, with a name and a star rating. These are only ever the reviews you enter — nothing is invented, and the section stays hidden until you add one.
• Common questions — a toggle that pulls the first few questions from your FAQ page straight onto the homepage.
• Where to find us — a toggle that shows your address and an embedded map (using the address you set under Business info).

Each section only appears once it has content, so nothing changes on your live site until you fill it in. New sites start with sensible starter copy for the first two, ready to edit.

These sections show on the Studio, Coastal and Express themes; the Premium theme keeps its own built-in homepage layout.

The Book now button in the site footer was rendering on top of the Explore links on the Studio and Coastal themes — the vertical padding of the button was overlapping the "FAQ" link above it.

The button now behaves as a proper full-width button and sits below the links, with its label centred. No content or links changed — this is a styling fix only, and the Express and Premium themes were already correct.

Expanding a vehicle group in the fleet widget shows a strip of photo thumbnails, and clicking one swaps the large photo at the top of the card.

The strip left out the photo already on display, so once you clicked a thumbnail there was nothing to click to get the original back. The only way to restore it was to reload the page.

The strip now shows every photo in the group, including the one currently on top, and the one on display is outlined so you can see where you are. A group with a single photo shows no strip at all, since there is nothing to switch between.

Glovebox no longer runs on a 90-day free trial. There is no countdown, and nothing expires.

Instead, your workspace is a sandbox: free for as long as you want it. You can add your fleet, set your pricing, publish a booking page, write your emails and run bookings end to end. In a sandbox:

• every booking is a test booking;
• card payments run in test mode, so nothing is charged;
• no emails reach your customers.

When you are ready, Go live starts your subscription, makes your booking page public, switches payments to live and starts customer emails. Your test bookings are kept, but hidden from your reports so they never muddle your numbers. You can find it under Settings → Go live, and once your setup is finished it appears on your dashboard checklist too.

What this means for you

• If you are already taking real bookings, nothing changes. Your rate, your founding pricing and your access all stay exactly as they are.
• If you signed up on a trial that is still running, you keep every day you were promised — going live simply starts your subscription when those days run out.
• If you are still setting up, you now have as long as you like, with no deadline and no card needed to start.

A new strip at the top of your admin tells you which state you are in, so it is always clear whether a booking is real or a test. If a payment ever fails, you keep trading for 14 days while you sort it out; your existing bookings, payments and customer emails are never affected.

Two small improvements to website enquiries:

• Optional phone field — the contact form on your website now has an optional "Phone" field, so an enquiry can arrive with a number to call back on, not just an email address. It shows on the enquiry under Website → Enquiries.
• Delivery status — each enquiry now records whether the notification email was actually sent to you. The enquiry list has a "Mailed" column, and the enquiry detail shows "Emailed to you" (or "Not sent"). Because every enquiry is saved the moment it is submitted, you never lose a lead even if the email cannot be delivered — it is still waiting for you in the admin.

Nothing else changes: the form still works without a phone number, and existing enquiries are unaffected.

When you add a vehicle you can create its group inline, from the group dropdown. That form asked only for a name, so the new group arrived with no price. Setting one meant remembering to open the group editor afterwards, and until you did, that group was offered to customers at $0.00 a day.

The inline form now asks for the daily rate alongside the name, and will not create the group without one. Nothing else changes: the rate still lives on the group, every vehicle in a group still hires at the group's rate, and you can change it later in the group editor as before.

This mostly helps if you price each vehicle separately, which you do by giving each car its own group. That is now two fields on one screen rather than a round trip to the group editor for every car.

A vehicle's page had grown to six buttons across the top. Two of them were embed codes with near-identical names — "Embed code" and "Embed this vehicle" — with nothing on the button to tell you that one gives you a booking form and the other shows the car.

Log reading stays where it was, since it is the one you use regularly. Everything else — photo history, servicing record, both embed codes, and delete — now sits under a More menu next to it.

The two embed codes are now named for what they produce:

• Embed booking widget — the booking form, opening on the dates step, set to this vehicle.
• Embed vehicle card — a card showing this vehicle, priced at its group rate.

Nothing has been removed and no button has changed what it does.

Two improvements to your Glovebox website.

Enquiries are saved. When someone fills in your website contact form, the enquiry is now recorded in your admin under Website → Enquiries — with their name, email, message and which page they came from. It is saved first and the email to you is sent second, so even if an email hiccups, the lead is never lost. Enquiries are delivered to your site's contact email (or, if you haven't set one, to the account owner).

Analytics that work. Your Google Analytics, Google Ads and Meta (Facebook) Pixel IDs now live together in Website → SEO & analytics, and they load on your live public site straight away. Previously the analytics box on the website settings didn't feed your live site — if you'd added a code there and wondered why you saw no data, add it again here and it will start tracking.

We've also tidied a few rough edges: vehicles with no photo yet show a tasteful branded placeholder instead of a blank space, and your FAQ page now helps you show up in Google's FAQ results.

Your Glovebox website now works the way customers shop for a rental — by category, not by individual rego.

Fleet by category. The fleet page and your home page now show vehicle categories (your groups) — a representative photo, the key specs, and one honest "from" price that includes GST, the same figure your booking widget uses. No more three-different-prices, and never a "$0/day": a category we can't price yet reads "Price on request".

Search that filters. When a visitor picks dates on the home or fleet search, the fleet now shows only the categories actually available for those dates, at the price for that window, and carries the dates straight through to "Book". A new "Book" link in the header jumps them to it.

A page per category. Each category has its own page with its gallery, description, features and a Book button. Your old per-vehicle links (/vehicles/…) now permanently redirect to the category page, so nothing you've shared breaks and search engines follow along. The sitemap lists the category pages.

You can dress each category for your site — its own description, hero image, gallery and features — the same way you could a vehicle before.

An over-mileage charge email included a direct Stripe payment link. Stripe payment pages expire after about a day, so a customer who opened the email later landed on a blank "You're all done here" page and could not pay, with no obvious way forward.

The Pay button now points at a Glovebox link that opens a fresh Stripe payment page every time it is clicked, so it works whenever the customer gets to it. Nothing about the amount charged changes. If the charge has already been paid, the link now sends them to their booking with a note rather than a dead end.

The same expiring-link problem that affected over-mileage charges also affected other post-hire charges (excess kilometres, cleaning, tolls and similar). Both the emailed Pay button and the "Pay now" button on the customer portal pointed at a stored Stripe payment page that expires after about a day, so a customer coming back later landed on a blank "You're all done here" page.

Those buttons now open a fresh Stripe payment page every time they are clicked, so the customer can always pay. Nothing about the amount charged changes, and an already-paid charge sends them back to their booking with a note instead of a dead end.

You can now show your whole fleet on your own website — WordPress, Wix, Squarespace or hand-coded — with a single line of code. Go to Settings → Website → Embeds, choose your accent colour and button text, and copy the snippet. Paste it once where you want the fleet to appear.

Each vehicle group shows as a card with its photo, key specs and a "from" price (GST inclusive), and a button that takes the customer straight into your Glovebox booking widget with that group already selected. Dates and availability are handled in the booking widget, as always — the fleet page is your shop window.

The look is driven by your saved settings, so changing a colour or the button text never means re-pasting the snippet. There's a live preview on the settings page so you can see exactly what your visitors will see before you publish.

The embedded fleet widget laid its vehicle cards into as many columns as the page was wide, then left the unused columns empty. An operator with two or three vehicle groups saw their cards pinned to the left edge of a wide page with a large blank area to the right, which read as a broken embed rather than a small fleet.

The widget now sizes itself to a comfortable reading width, centres on the page, and only creates as many columns as there are vehicles to fill — so two cards sit centred and evenly sized instead of stranded. A larger fleet fills the grid and wraps exactly as before.

If your site deliberately places the widget full-bleed, you can widen or remove the limit from your own page with the --gf-max-width custom property.

The customer booking portal used to explain the excess-reduction upgrade twice: a "Your protection" card with a comparison table, and a separate "Reduce your excess before pickup" card with a "See upgrade options" button. They are now a single Your protection card, benefit first.

The card leads with the stake ("Your excess is $X if anything happens"), keeps the what's-covered comparison with the upgrade shaded, and puts the action inside the upgrade column: Upgrade for $X/day, with the total shown underneath. The button goes straight to the secure checkout, with no in-between page, and a compact version sits in the right-hand rail too. Once a customer upgrades, the card shows an Upgraded tag and collapses to their new cover. Nothing about the price or how upgrades are charged has changed, and customers on operators who are not set up for online card payments still see the comparison with a prompt to ask at pickup.

The customer booking portal now has a Your extras section that lists every add-on on a booking in one place: accessories, airport transfers, delivery and one-way fees, extra drivers, and, new here, the custom extras you add by hand. Each line shows the name, quantity and price (GST inclusive) with a subtotal, so a customer can see exactly what they are paying for. If a booking has no extras, the section says so rather than disappearing.

Custom extras used to be invisible to the customer even though they were on the total. If you ever add a custom line you would rather keep to yourself, the Add custom extra form now has a "Show on the customer booking portal" switch. Leave it on to show the line, or turn it off to keep it internal. Internal manual charges stay off the portal automatically.

A customer collecting on their own now signs your rental agreement as part of the flow, before the lockbox code is shown to them. They type their full name against the version of the terms they are shown, exactly as they would signing in the customer portal.

Until now a self-collection pickup could reach the code without a signature anywhere, which left the hire running on unsigned terms.

There is now a Help Centre at /help, covering getting started, bookings and availability, pricing, payments and bonds, locations, fleet and maintenance, pickup and self-collection, customer communications, Xero, and your website.

Every answer has its own page, there is a search box on every topic, and if you cannot find what you need there is a form at the foot of each page that reaches a real person.

Placing a second bond hold for a different amount on the same booking could return the first hold instead of creating a new one. Fixed.

You can now tell Glovebox when a location is shut. Open a branch under Locations and use Opening & closures to close it on specific dates, with an optional repeat-every-year for dates like Christmas, or on recurring weekdays such as every Sunday.

Customers cannot pick up or return at a closed location on a closed day, and the booking page enforces it for you. A hire can still run across a closed day, because the vehicle is out and it is only the counter that is shut, and you can still book those days manually from the admin.

A file upload that failed to write to storage could previously be swallowed rather than reported, which meant a photo could appear to save and then not be there later. Storage write failures now surface as real errors, so a failed upload is visible at the time rather than discovered when you go looking for the photo.

The vehicle edit screen had grown into one long scroll. It is now split into tabs, with a compliance summary you can read at a glance rather than hunting for.

Nothing moved out of the page, it is just easier to find. If you spend a lot of time in the fleet, this is the change you will notice most.

A customer can now collect their vehicle without anyone from your team being there. They open a link on their phone, work through the collection steps, and the vehicle's lockbox code is released to them.

You control when the code is released. The collection window is set by you, and the code appears only once the customer is inside it.

Self-collection is switched on per location, and only for vehicles that have a lockbox code recorded.

Broadcasts is for operational messages, sent by SMS or email. Think weather warnings, road closures, pickup reminders and recalls, not marketing.

You choose the audience by booking state, for example everyone on hire right now or everyone picking up in the next two days, and you can narrow it further by location or vehicle. Before you send, Glovebox shows you how many people each channel would reach, so you are not sending blind.

Opt-outs are respected. A customer who replies STOP is never messaged again. Every message sent is logged against the booking, which gives you a trail if a customer later says they were never told.

Broadcasts is switched on per workspace. Get in touch if you want it enabled.

Demand pricing is an optional layer on top of your existing pricing rules. It nudges your daily rate up or down based on fleet utilisation, how far ahead the booking is, and recent booking pace, all within minimum and maximum limits you set.

It is off by default, and it is deliberately explainable rather than a black box: every recommendation shows you which factors moved the price and by how much.

You can also run it in shadow mode first. Glovebox logs what it would have charged without changing what customers actually see, so you can watch it against real quotes for a few weeks before deciding whether to switch it on. Owners manage it at Revenue → Pricing → Automatic demand pricing.

Servicing and compliance now live alongside the fleet rather than in a separate spreadsheet. You can log maintenance jobs against a vehicle, record parts, and keep track of compliance dates.

When a vehicle goes in for work you can take it off the road from a set date, either until an expected return or open-ended. While it is off the road it is automatically unavailable to book, and it comes back into availability when you close the job, so nobody sells a hire on a car that is up on a hoist.

Glovebox now sends customers their pickup information ahead of time, so fewer of them arrive without knowing where they are going or what to bring.

The email carries the booking details along with the pickup instructions you have set on the location, which means the branch-specific detail such as where to park or which door to use goes out automatically instead of being retyped.