One to One Plus vs Sortly

One to One Plus

A K-12 asset management and help desk platform focused on 1:1 device programs, sold as a single subscription with all core features included and an actively developed native mobile app on both iOS and Android.

Where One to One Plus is strong

• ● A genuinely strong native mobile app on both iOS and Android, using the phone camera as the scanner with no hardware sled — assignment and collection, full ticket create/update/close, photo and video damage capture, and adding or removing parts with a live availability check. It is actively developed, with Face ID login, in-ticket attachments, and mobile-only ticket forms all shipping within the last year or so.
• ● The only product in this comparison with native insurance program management: coverage applied to eligible incidents, claim status and coverage limits tracked, and approved claims offsetting invoice balances. Premiums are a charge type and insurance forms are an e-signature document type.
• ● Simple, honest packaging — one subscription, all core features, no module upsells. Among K-12 asset vendors that is genuinely uncommon and removes a whole category of procurement surprise.
• ● More than a dozen named integrations covering SIS (Infinite Campus, PowerSchool, Skyward, Ascender), MDM (Google Admin, Microsoft Intune, Mosyle, Jamf Pro, PDQ Deploy), identity (Active Directory plus Google and Microsoft SSO), and payments (MySchoolBucks, Rycor).
• ● Purpose-built end-of-year tooling: bulk turn-in for large-scale collection, cart, room, and inventory-area location granularity, and building-level audit reconciliation sheets.
• ● Funding source works as both a field and an audit dimension, with Title I and E-Rate named, plus e-signatures for agreements, AUPs, handbooks, and insurance forms, and scheduled report email delivery.

What to check before you buy

• No purchase order or receiving workflow. The asset record carries passive procurement metadata such as vendor details and purchase dates, but there is no PO object, approval routing, or receive-against-PO step.

  Basis: verified three ways — no PO page, no site search hit, and absent from the vendor's own module overview

• No parent-facing portal. Families are reached by email — invoices are delivered with view tracking — and when a family pays, that happens on the third-party processor's site rather than in One to One Plus. A staff and student self-service ticket portal does exist; the gap is specifically family-facing.

  Basis: vendor invoices and payments documentation describes email delivery plus third-party payment

• No Clever, ClassLink, or OneRoster support is listed among their published integrations — rostering runs through direct per-vendor SIS connectors instead.

  Basis: vendor integrations page, which names no rostering standard or roster broker

• Payment collection is entirely third-party — MySchoolBucks and Rycor are the named processors — so the fee record and the money live in different systems.

  Basis: vendor integrations and payments pages name MySchoolBucks and Rycor

• Warranty data is stored on the asset record, but no claim workflow, expiration alerting, or vendor RMA process is documented.

  Basis: vendor asset management documentation treats warranty as an asset attribute

• Reporting depth is a recurring theme in reviewer feedback despite the product shipping a report builder — buyers appear to judge this area harshly.

  Basis: recurring theme in public review-site feedback

• Hosted SaaS only — there is no self-hosted or on-premises option and no source availability.

  Basis: vendor sells a hosted subscription with no self-host offering published

• MDM integration is ingest-oriented: device data is imported and kept in sync, with no documented reviewed write-back of OU moves, disables, or deprovisions into Google Admin.

  Basis: vendor integrations page describes device data being imported, updated, and synced into the platform

How Chalk compares with One to One Plus →

Sortly

The friendliest inventory app in this comparison and the easiest to actually start using — built for supply closets and job sites, priced by how many items you have, which is exactly the wrong meter for a 1:1 fleet.

Where Sortly is strong

• ● Every price is on the page, including a genuinely free tier, with no demo gate anywhere in the funnel.
• ● The lowest adoption cost in this comparison by a distance: folders, tags, photos and custom fields, usable by a building secretary in an afternoon without an IT project behind it.
• ● Strong mobile — iOS and Android with offline access, barcode and QR scanning, and label generation from inside the same app, so counting is a phone job rather than a scanner-hardware purchase.
• ● Alerting that fits consumables well: low stock alerts for reordering and date-based alerts for maintenance and repair schedules, with in-app and email notification.
• ● More reporting than the price suggests — activity history, inventory summaries, user activity, low stock and item-flow reports, saved custom reports, and report subscriptions delivered on a schedule.
• ● Real integration surface for a product this simple: webhooks, an API, QuickBooks Online, and Slack and Microsoft Teams notifications, plus purchase orders, pick lists, and check-in and check-out.

What to check before you buy

• Pricing meters unique items, and a 1:1 district's item count is its student count. At 5,000 items the published tier is $299 per month, and anything past 10,000 items is Enterprise quote-only — a mid-sized district is off the published ladder on device count alone.

  Basis: Vendor pricing page item limits: 100 free, 500 Advanced, 2,000 Ultra, 5,000 Premium, 10,000+ Enterprise.

• User licenses are metered too, and tightly: 1 user free, 2 on Advanced, 5 on Ultra, 8 on Premium. A technician team plus building staff crosses into Enterprise quickly.

  Basis: Vendor pricing page user-license limits per tier.

• No help desk or ticketing of any kind. A district running Sortly still buys a service desk somewhere else, and the two never see each other.

  Basis: Absent from the vendor's published feature list, which covers inventory, alerts, reporting and integrations.

• No MDM or device integrations at all. The published integration list is QuickBooks Online, Slack, Microsoft Teams, webhooks and an API — so ChromeOS, Intune and Jamf data is typed or imported, and serials go stale between imports.

  Basis: Vendor features page lists no device-management or directory connectors.

• No SIS or rostering integration and no student, guardian or enrollment concepts — nothing notices a transfer, a withdrawal or grade rollover.

  Basis: Absent from the vendor's feature list and from its industry positioning, which addresses inventory rather than student records.

• Check-in and check-out is item custody, not a school-year loan: no due dates on a student device agreement, no e-signature, no damage fee, no family balance and no loaner pool workflow.

  Basis: Vendor documents check-in/check-out alongside pick lists and stock tracking, with no agreement or fee concepts published.

• It is an inventory product rather than an IT asset lifecycle product — warranty expiry, depreciation, ChromeOS auto-update expiration and refresh planning are not in the published feature set, though generic date-based alerts can approximate some of it.

  Basis: Vendor features page covers custom fields, alerts and reports; no warranty, depreciation or lifecycle module is published.

• Hosted SaaS only, with no self-hosted option, and no SSO or SAML in the published feature list — so it sits outside your single sign-on estate in both directions.

  Basis: No self-host or source distribution is offered on the vendor site, and SSO does not appear on the features or pricing pages.

How Chalk compares with Sortly →

The third option: Chalk

If you are weighing One to One Plus against Sortly, Chalk belongs on the same shortlist. It is the open-source K-12 IT stack: device inventory that fills itself in from Google Admin, Intune, and Jamf against a roster synced from your SIS, a 1:1 circulation desk with agreements and fees, repairs with parts and costs, a help desk that already knows who is asking, and a built-in SAML/OIDC identity provider.

• ✓ Self-host it free forever under AGPL-3.0 — the entire feature set, one binary, your infrastructure — or use the hosted version, priced by fleet size with no per-seat or per-student fees and the price ladder published.
• ✓ Built only for K-12: students, buildings, custody, funding sources, and ChromeOS auto-update expiration are native concepts, not custom fields.
• ✓ Writes back to Google Admin as a reviewed diff — every OU move, disable, and deprovision previewed before it executes — and serves a OneRoster 1.1 API so other district systems can pull the roster from Chalk.
• ✓ Fees are assessed and tracked without touching payment cards, keeping the asset system out of your PCI scope.