Skip to main content

Samsara Premium Integration: Setup Guide

This is a guide to help you set up the Alvys + Samsara Premium Integration. This integration enables automatic check-in/check-out at stops, bi-directional data sync between Alvys and Samsara, and driver document collection through the Samsara Driver app.

Written by Alvys Admin


What You Get

With Samsara Premium, your dispatchers and drivers benefit from:

  • Automatic stop check-in and check-out using Samsara geofences (no manual entry required)

  • Bi-directional data sync between Alvys and Samsara: dispatched trips in Alvys automatically appear as routes in the Samsara Driver app, and driver updates (BOL numbers, weights, pieces, documents) sync back to Alvys in real time

  • Document collection at stops: drivers upload required documents (PODs, BOLs, etc.) through the Samsara app and they flow directly into Alvys

  • Real-time route updates: any changes made by dispatch in Alvys (stop additions, reorders, appointment time changes) are instantly reflected on the driver's Samsara screen


Prerequisites

Before enabling the Premium integration, you must have:

  1. An active Samsara account with the Samsara Driver app in use by your fleet

  2. The standard Alvys + Samsara ELD integration already connected (this is the base integration that syncs vehicle locations, HOS, and ELD data)

  3. Drivers linked between both systems: every driver that will use the Premium integration must be linked to an existing, active driver in Samsara. If a driver ID is missing, the route will not sync. If an Alvys driver is linked to the wrong Samsara driver ID (for example, Alvys driver "Alice" carries Samsara driver "Bob's" ID), the route will show as assigned to the wrong driver in Samsara.

  4. Samsara Premium enabled: Discuss with your dedicated Customer Success Manager, and they can assist in setting you up.


Step 1: Generate a Samsara API Token

Generate the API token through the Alvys app in the Samsara App Marketplace. This is the recommended approach because the token is created with the exact permissions Alvys needs — you do not need to configure scopes manually.

  1. Log in to your Samsara Dashboard

  2. Open the App Marketplace

  3. Find and install the Alvys app

  4. Generate the API token from the Alvys app

  5. Provide the token to your Alvys implementation contact, or enter it in the Samsara integration settings within Alvys.


Step 2: Configure Geofences in Samsara (Optional)

Geofences are not required for the integration, but they improve the accuracy of automatic check-in and check-out. Where a geofence is not configured, Alvys falls back to a default radius of 300 meters from the location pin.

If you want to fine-tune arrival and departure detection:

  1. In the Samsara Dashboard, go to Geofences

  2. Create a geofence for each shipper, consignee, yard, or terminal location your drivers visit

  3. Make sure the geofence name or address matches what your dispatchers use in Alvys so the systems can correlate correctly

Tip: If you already have geofences configured in Samsara for other purposes (e.g., yard management or visibility), those same geofences will work for auto check-in/check-out. You do not need to recreate them.


Step 3: Verify Driver Matching

For the integration to work correctly, drivers must be linked between the two systems. A trip must have a driver assigned to sync to Samsara. If the assigned driver is not linked a driver in Samsara, the route will not sync; if it points to the wrong Samsara driver, the route will appear assigned to that driver in Samsara.

Your Alvys implementation contact can help you verify that your drivers are properly linked.


Step 4: Define Your Document Requirements

Document collection at stops is self-serve and configurable — you can set it up yourself, and your Alvys implementation or support team can guide you if needed. Before go-live, decide:

  • Which document types are required at each stop type (e.g., pickup stops require a "Depart Pickup" confirmation and a BOL; delivery stops require a "Delivery" confirmation and POD upload)

  • Which fields are mandatory vs. optional for your drivers to complete before they can close out a stop

The following fields can be captured through the Samsara Driver app and synced back to Alvys:

  • Bill of Lading number, Seal number and other references

  • Weight

  • Commodity description

  • Pieces count

  • Trailer number

  • Detention events

  • Notes

  • Document uploads (BOLs, PODs, photos)


Step 5: Driver Training

Before go-live, make sure your drivers are prepared:

  1. Install the Samsara Driver app on their phone or tablet (available on iOS and Android)

  2. Drivers will see dispatched routes appear automatically in the Samsara app once a trip is dispatched and assigned to them in Alvys

  3. Train drivers on:

    • How to view route details and stop instructions

    • How to upload documents at each stop

    • How to fill out task fields (BOL, seal, weight, pieces, etc.)

    • That arrival and departure will be tracked automatically via geofences (no need to manually check in/out at locations with a geofence configured)

Important: Document upload can be required, optional, or not configured at all — it depends on how you set up your tasks for your tenant's needs. If you make document upload a required task, drivers must complete it to close out a trip, so make sure your team understands which documents are expected at each stop type.


How It Works Day-to-Day

Once everything is configured:

  1. A dispatcher dispatches a trip in Alvys and assigns a driver

  2. Alvys automatically pushes the route to Samsara, including all stops, appointment times, reference numbers, and special instructions

  3. The driver sees the route in their Samsara Driver app with full stop details

  4. As the driver arrives at and departs from geofenced locations, check-in/check-out timestamps sync back to Alvys automatically

  5. The driver uploads documents and fills out fields (BOL, weight, pieces, etc.) through the Samsara app

  6. All driver-submitted data and documents sync back to Alvys in real time

  7. If dispatch makes changes to the trip in Alvys (adds/removes stops, changes appointment times, reassigns), those changes are pushed to Samsara immediately

In-App Samsara Flow:


FAQ

Do I need to pay Samsara anything extra for this integration?The Premium integration comes with an additional per load fee. Please contact your Customer Success Representative for details or book a call here!

Which fields can I configure for the Driver to fill out and submit?Load References, Stop References, Stop Commodity (fully configurable Units of Measure), Driver Notes, Trailer Number, Documents (BOL, POD, Lumper Receipts, etc.)

What if a driver does not have the Samsara Driver app?The driver must have the Samsara Driver app installed and be logged in for routes to appear and for data to sync. Without the app, the integration cannot function for that driver.

What happens if a geofence is not set up for a location?Geofences are optional. Where one is not set, Alvys uses a default radius of 300 meters from the location pin to mark auto check-in/check-out.

Can I use this if I have split loads?Yes. Alvys handles splits automatically. Each leg of a split is pushed as a separate route to Samsara, and documents are tied to the load level so nothing is lost during splits or re-dispatching.

What if a driver ID does not match between Alvys and Samsara?If the driver ID is missing, the route will not sync. If an Alvys driver is linked to the wrong Samsara driver ID, the route will appear assigned to the wrong driver in Samsara. Contact your Alvys implementation team to resolve any driver ID mismatches before go-live.


Need Help?

Contact your Alvys account representative or reach out to your implementation team to get started with activation and configuration.

Did this answer your question?