GPS Fleet Tracking & Telematics
Geotab Add-In vs Add-On: What the Two Words Mean and Which One You Need
Geotab uses two words that sound alike for two different things. An Add-In is software that runs inside MyGeotab or Geotab Drive; an Add-On is hardware that plugs into the GO device's IOX port. Here's what each does, how each is built and installed, examples of both, and how to tell which one solves a given problem.

Add-In: Software Inside the Platform
An Add-In is a piece of software built on Geotab's SDK that runs inside MyGeotab, as a new page or panel, or inside the Geotab Drive app on the driver's device. It reads and writes the fleet's data through the same API everything else uses. Bus Route Progress, Timeline Map, GeoDocs, ELD Info and Ruleset Switcher are Add-Ins. Geotab and Marketplace partners publish them, and a reseller with developers — High Point GPS builds custom ones — can write an Add-In for a single fleet's workflow. Installing one is a configuration step in the fleet's MyGeotab database; nothing goes in the vehicle.
Add-On: Hardware on the IOX Port
An Add-On is a physical device that connects to the GO device through its IOX expansion port and sends data up through the GO device's connection. IOX-BT for Bluetooth tags, IOX-NFCREADERA for driver ID, the DIDCOM BLEG gateway and temperature sensors, the PTO reader, cameras that connect through IOX, and the Keyless module are Add-Ons. They are installed in the vehicle by an installer, and the data they produce appears in MyGeotab as new streams the platform's rules and reports can use. Many Add-Ons come with a companion Add-In that displays their data.
Which One Solves the Problem
If the fleet already has the data and needs to see or use it differently — a better view, a report, a workflow, a document, a driver-facing screen — the answer is an Add-In. If the fleet needs data the GO device does not have — a temperature, a door, a driver's identity, a PTO state, video — the answer is an Add-On, usually with an Add-In to present it. A parent app for a school bus is an Add-In; the card reader that records the child boarding is an Add-On.
Buying and Building
Both are listed on the Geotab Marketplace, where the distinction is visible in the listing type. Add-Ins are often licensed per database or per vehicle per month; Add-Ons are purchased hardware plus, sometimes, a plan. Custom Add-Ins are a development project against the SDK; custom Add-Ons are rare, since the IOX ecosystem covers most sensors. High Point GPS supplies and installs Add-Ons and builds and deploys Add-Ins for fleets across Quebec, Ontario and the northeastern US.
Frequently asked questions
What is a Geotab Add-In?
Software built on Geotab's SDK that runs inside MyGeotab or Geotab Drive, adding pages, panels, reports or workflows using the fleet's existing data.
What is a Geotab Add-On?
Hardware that plugs into the GO device's IOX port, such as Bluetooth readers, driver ID, sensors, cameras and the Keyless module, adding data the GO device does not collect on its own.
Do I need an installer for an Add-In?
No. Add-Ins are enabled in the MyGeotab database. Add-Ons are installed in the vehicle.
Can a reseller build a custom Add-In?
Yes. Resellers with developers, including High Point GPS, build Add-Ins for a single fleet's workflow against the SDK.
Where do I find them?
On the Geotab Marketplace, which lists both types, and through your reseller.
Related solutions & products
Continue reading
- GPS Fleet Tracking & Management Software overview →
- What Is GeoDocs? Fleet Document Management Inside MyGeotab →
- What Does a Geotab Reseller Do? How Buying Through a Partner Works →
- Bus Route Progress: The MyGeotab Add-In That Shows Which Buses Are On Route, Late or Parked →
- IOX-NFCREADERA: Driver ID by NFC Tap, So Every Trip Has a Name on It →
- More in GPS Fleet Tracking & Telematics →
Get a free quote
What are you looking for?