Skip to content
High Point GPS

Glossary

High Point GPS Add-On Library

A catalog of Add-Ins and Add-Ons, built by High Point GPS and third-party developers, that extend what the platform can do. Built on the platform's open SDK, which is also what makes custom Add-Ins possible.

What High Point GPS Add-On Library means in practice

The High Point GPS add-on library is a catalogue of Add-Ins and Add-Ons, built by High Point GPS and third-party developers, that extend what the platform can do. It exists because the platform is open: outside developers, including partners like High Point GPS, can build on its public SDK instead of waiting for every feature to come from one vendor. Listings fall into recurring categories: safety and video, compliance helpers, fuel card integrations, dispatch and routing connectors, maintenance and diagnostics, and asset tracking extensions.

It helps to keep three tiers straight. Core platform features such as tracking, basic reporting and driver scoring come with the platform. Library Add-Ins are pre-built extensions you install. Custom Add-Ins are built for one fleet's workflow when nothing in the library fits. GeoDocs, for document management in the cab, is a library Add-In: it is built by High Point GPS and listed on the Geotab Marketplace.

Before installing anything, check what data access it requests, whether it has been updated recently and who supports it if it breaks. Then pilot it on a few vehicles before a fleet-wide rollout.

Read the full explainer

The definition above is the short version. The page below explains High Point GPS Add-On Library in depth, with the rules, numbers and examples behind it.

What's in the High Point GPS add-on library?

High Point GPS Add-On Library: common questions

Who supports an add-on library Add-In if something goes wrong?

It depends on the listing. Support can come from the original third-party developer, from the platform for its own listings, or from your installation partner if it helped implement the Add-In. Confirm who to call before relying on an Add-In for anything business-critical, because buyers often only discover the answer when something has already broken.

What is the difference between an add-on library Add-In and a custom Add-In?

A library Add-In is a pre-built extension, made by the platform or a third party, that any fleet can install to add a specific capability. A custom Add-In is built for one fleet's workflow, usually by a provider like High Point GPS, when nothing in the library fits. GeoDocs, for document management in the cab, is a library Add-In built by High Point GPS and listed on the Geotab Marketplace.

Should I pilot a new Add-In before rolling it out fleet-wide?

Yes. Testing on a small group of vehicles first surfaces data conflicts or performance issues while they are still easy to fix. An Add-In that behaves well on five vehicles usually scales fine to five hundred, but finding a problem during a pilot is far less disruptive than finding it after a full rollout.