Device Management & MDM Operations3 min readUpdated September 2026

Kandji vs Rippling IT for a Brand Running Stores and an Office

For a brand running stores and an office, Kandji suits locking register tablets into a single app across every location, while Rippling suits corporate laptops whose software follows an employee's role. Neither removes the tension between store lockdown and office flexibility, so match each posture to the device rather than to the company.

Vendors Covered in this Article

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

One company, two very different device postures

A store device exists to run one app reliably and predictably, shift after shift, regardless of who's behind the register. A corporate laptop exists to let someone do a changing set of tasks across a normal workday. Applying the store's lockdown mindset to a corporate laptop frustrates the people who need flexibility to do their jobs, and applying the office's flexible mindset to a register tablet is how an associate ends up browsing the internet on a device that's supposed to be ringing up sales.

Kandji's case for locking down the store fleet

Kandji's supervised device profiles can lock a register tablet into a single app, block installs, and enforce the same configuration whether the device is in the flagship store or the smallest satellite location. For a brand opening new locations regularly, having that lockdown apply automatically the moment a new device is enrolled means a store manager never has to configure a register by hand or worry that one location quietly drifted from how every other one is set up.

Rippling's case for corporate staff who move between roles

On the corporate side, Rippling's tie between a laptop and an employee's actual role means the software and access on that laptop can update automatically as someone moves from a merchandising role into a buying one, without a separate IT request to reconfigure the device. For a brand with a corporate team that grows and reorganizes as the store footprint expands, that role-based tie removes a step that otherwise falls on whoever manages IT requests that week.

Where configuration drift actually creeps in across locations

Drift rarely happens all at once. It happens when one store's register gets a one-off app installed to solve a problem during a busy weekend, and that change never gets reverted or reported, so the device quietly diverges from every other store's configuration. Multiply that by a dozen locations and a device management platform's whole value, applying one configuration everywhere and catching anything that strays from it, is what keeps a dozen stores from becoming a dozen slightly different setups.

What a holiday staffing spike does to the store fleet

A retail brand's headcount at the register level can swell sharply for a few weeks around the holidays, with seasonal associates who need access to the same locked-down point-of-sale app as full-time staff but for a much shorter window. The device itself doesn't need to change for a seasonal hire since it's already locked to a single app regardless of who's using it, but the login or access tied to that seasonal employee should end cleanly when the season does. A platform tied to staffing records handles that cutoff more reliably than a manual process during the same weeks a store is already at its busiest.

A mistake that surfaces during a multi-location audit

The gap that tends to show up is a store that opened months ago on a rushed timeline, where a manager set up the register manually to hit an opening date and never went back to bring it fully into the standard enrollment process the rest of the chain uses. That store looks fine day to day until a multi-location review compares configurations and finds one location running settings nobody else has. Building a follow-up check into every store opening, a set number of weeks after the doors open, catches this before an audit does.

To keep both postures holding up across locations, check the following:

  • Lock each register tablet to the point-of-sale app and block installs, so every store runs the same configuration.
  • Enroll every new store's devices through the standard process, not a manual setup done to hit an opening date.
  • Schedule a follow-up check a set number of weeks after each opening to confirm the register fleet matches every other location.
  • Compare register configurations across stores regularly, to catch one-off apps installed during a busy weekend.
  • Keep corporate laptops flexible, with software and access that update as someone moves between roles.

Matching the posture to the device, not the company

There's no single right platform for a brand like this, because the two halves of the fleet want different things. A smaller chain with a handful of stores and a lean corporate team can run both halves on Kandji, using its supervised profiles for the floor and its standard baseline for the office. A brand with a larger, more fluid corporate team gets more value from Rippling's role-based tie on that side, while still relying on the same kind of locked-down profile for the store fleet regardless of which platform manages it.

Executive Capability Standard

What Good Looks Like

Every store register runs a locked-down, single-app profile that matches every other location's, and every corporate laptop's access updates automatically as the employee's role changes.

Building The Capability (5-Stage Skill Ladder)

1. Learn:Compare the current configuration of two or three store locations to confirm they actually match, rather than assuming they do.
2. Do Manually:Walk a checklist at each new store opening to confirm the register fleet is enrolled and configured to the same standard as existing locations.
3. Delegate:Assign one person to own store-fleet configuration across all locations, separate from whoever manages the corporate laptop fleet.
4. Automate:Deploy Kandji or Rippling so a new register's lockdown profile applies itself the moment it's enrolled, without a store manager configuring it by hand.
5. Buy:Schedule a recurring multi-location configuration audit so drift gets caught on a set schedule rather than during an unrelated investigation.

How to Get Started

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

Frequently Asked Questions

Should store registers and corporate laptops use the same device management setup?

They can run through the same platform, but the configuration should differ. Registers need a locked-down, single-app profile applied consistently across every location, while corporate laptops need enough flexibility to support a role that changes over time. Treating them identically usually under-serves one side or the other.

How does configuration drift happen across multiple store locations?

It usually starts small: one store installs a one-off app or changes a setting to solve a problem during a busy shift, and the change never gets reverted or reported. Over months and multiple locations, those small changes add up to stores that no longer match the standard configuration.

What should happen after a new store location opens?

Schedule a follow-up check a set number of weeks after opening to confirm the register fleet is fully enrolled and matches every other location's standard configuration, not just whatever got the store open on time. Rushed opening-day setups are where drift most often starts.

About the numbers

This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.

Related Guides