ARC

The product may be unsuitable where:

• The primary requirement is software-based device compliance and remote administration
  • For patching, configuration management, app deployment, remote wipe, and compliance reporting, a UEM or MDM platform is the appropriate primary tool.
• The device fleet is small or low-value
  • A hardware locker deployment may not deliver a positive return where shrink and downtime costs are low.
• The environment cannot reliably support kiosk operations
  • Inadequate power, extreme environmental conditions, or unreliable network connectivity can undermine kiosk-based solutions.
• The requirement is broad asset management beyond device fleets
  • For keys, tools, and highly regulated assets requiring per-item identification and mature audit controls, a specialized asset-locker vendor may be a better fit.
• The procurement process requires publicly posted security certifications prior to engagement
  • If procurement policies require publicly available SOC 2 or ISO certificates, the vendor’s public documentation may be insufficient without an NDA-based security review.

Current limitations based on public documentation

• Public documentation is primarily marketing and quick start materials; detailed technical limitations such as API constraints, offline modes, and uptime SLAs are not enumerated publicly.

Features on the roadmap

• Roadmap items are not reliably documented in public sources. Procurement teams should request a current roadmap under NDA if roadmap alignment is material to selection.

Scale limitations

• Vendor materials and social posts suggest the ability to support large rollouts, but detailed scale limits (for example, devices per kiosk, concurrent operations, or dashboard performance benchmarks) are not published.

Security and compliance gaps

• Public evidence of SOC 2 or ISO certifications was not found in the primary vendor sources reviewed. Procurement teams should request:
  • SOC 2 reports or attestations, if available
  • Penetration test summaries
  • Data flow diagrams and hosting details
  • Documentation for SSO, SCIM, and audit logging

API limitations and integration constraints

• Public API documentation was not found in the materials reviewed. Vendor blog posts reference work with clients on API development; confirm current API capabilities and integration support during procurement.

• A design focused on charging, storage, dispensing, and custody tracking for shared devices rather than general-purpose locker storage
• Self-service access workflows for frontline employees combined with manager/admin tooling for inventory and exception handling
• Device readiness logic described in vendor materials, such as dispensing devices with higher battery level first and detecting battery or port issues
• Analytics and alerting functions for unreturned or damaged devices as described in vendor content

• Established asset-control vendors may provide broader asset variety support and more mature access control and audit capabilities
• Some smart-locker platforms emphasize explicit ITSM workflow integration (ServiceNow, TopDesk) and deeper IT operations integration in published materials

Vendor-published case study and whitepaper materials

• The vendor provides a PDF report titled "The Impact of Device Management on Enterprise Productivity & Bottom Line Revenue" in multiple versions on the vendor site.
• These materials discuss topics such as purchases of spare device pools due to loss or damage, productivity impacts when employees lack devices, and ARC reporting surfacing device pickup gaps.
• Critical evaluation: These reports are vendor-produced. In the absence of transparent methodology regarding sample size, time period, customer selection, and controls, ROI and shrink metrics should be treated as directional and subject to validation.

Deployment scale example (vendor-reported operational detail)

• A vendor social post describes a rollout across Sam’s Club locations: over a thousand ARC units deployed in several hundred clubs across many states and territories, reportedly completed ahead of schedule.
• Critical evaluation: This example suggests the vendor reports the ability to manage large deployments, but it is vendor-provided reporting rather than independent verification of long-term operational outcomes.