This is the page Operations forwards to you. No marketing — just how APXR connects to SAP, what it does and doesn't touch, how worker data is handled, and what your network needs to provide. Pilots begin in read-only shadow mode, so review runs in parallel with proving the worker experience.
Shadow Mode
Live SAP write access triggers a security review that no VP of Operations can waive — typically 4–10 weeks at an enterprise. We design around it: pilots start in read-only shadow mode, needing only minimal access while we prove the worker experience. An IT-prerequisites one-pager ships with the LOI, so your review starts on signature day instead of after kickoff.
SAP Integration
Deep SAP warehouse integration across SAP EWM and classic WM (LE-WM), configured per environment.
Native RFC, BAPI, and OData — the same integration layer used by certified SAP partner apps.
Bidirectional: pick lists pull from SAP; confirmations write back in real time.
No middleware and no custom server-side development required.
Never touches the database directly and never bypasses SAP business logic.
SAP remains the system of record at all times.
Pilot begins in read-only shadow mode; write-back enabled after security review.
Security & Data
Hosted on AWS, encrypted in transit and at rest.
No facial recognition. No individual worker shaming. Analytics are aggregate-first.
No PII stored beyond what's required for worker login and SAP user mapping.
Configurable data retention per customer.
Roadmap SSO with your identity provider — targeted Q4 2026.
SOC 2 readiness underway; Type I targeted post-pilot. DPA available on request.
Network & Infrastructure
Runs over your existing warehouse WiFi — WiFi 5 (802.11ac) recommended across pick zones.
No dedicated network infrastructure, edge servers, or on-prem compute required.
Barcode scanning and offline pick-list caching run on the device.
The adaptive LLM copilot runs in APXR's AWS cloud.
Offline mode caches the active pick list and queues confirmations during connectivity drops.
Queued confirmations sync to SAP automatically when connectivity is restored.
IT & Technical FAQ
The questions your security review will ask.
For the pilot, very little up front: we start in read-only shadow mode, which needs only minimal, scoped access while workers experience the system alongside your existing RF workflow. The deeper step — enabling live SAP write-back — requires SAP RFC connection credentials and network access for the devices, and it triggers a formal security review. At most enterprises that review runs 4–10 weeks and cannot be waived by Operations. We plan for it: an IT-prerequisites one-pager ships with the LOI so your review begins on signature day, not after kickoff. We handle the connector configuration; you control access and approvals.
No — and this matters for data integrity. APXR integrates with SAP EWM and classic WM (LE-WM) through SAP's native RFC and BAPI layer, the same integration method used by certified SAP partner applications, configured to your specific environment. Pick lists are pulled via standard SAP function modules; pick confirmations write back to SAP in real time. We never touch the database directly, never bypass SAP business logic, and never require a middleware layer. SAP stays the system of record; from its perspective, picks simply arrive faster and cleaner. Non-SAP WMS platforms (Manhattan, Blue Yonder, Körber) are on the V2 roadmap, not V1.
The glasses connect over your existing warehouse WiFi — we recommend WiFi 5 (802.11ac) coverage across pick zones, which most modern warehouses already have. No dedicated network infrastructure, edge servers, or on-prem compute is required. Architecturally: barcode scanning and offline pick-list caching run on the device, while the adaptive LLM copilot runs in APXR's AWS cloud. Only lightweight data moves between the two.
Worker activity data — picks per hour, error frequency, guidance interactions — is stored in APXR's AWS cloud, encrypted at rest and in transit. We do not store personally identifiable information beyond what's required for worker login and SAP user mapping. There is no facial recognition and no individual worker shaming; analytics are aggregate-first. Retention is configurable per customer. On compliance: SOC 2 readiness is underway, with Type I targeted post-pilot — we do not currently hold SOC 2. A Data Processing Agreement is available on request.
APXR Pick includes an offline mode: workers keep picking against the cached active pick list if connectivity is interrupted. Pick confirmations queue locally and sync to SAP automatically when connectivity is restored. SAP remains the system of record at all times. A connectivity loss doesn't create a gap in your SAP data — it creates a brief delay in confirmation sync that resolves on its own.
The supervisor dashboard is available today as a standalone web application — no software to install. Roadmap A REST API for exporting productivity metrics, error rates, and worker performance data to external BI tools (SAP Analytics Cloud, Power BI, Tableau) is on the post-pilot roadmap, not shipped today. We'll scope BI export with you as part of rollout planning.
Workers authenticate via PIN or barcode scan at device login — configurable per site. Devices are registered to your APXR tenant and cannot be used outside your environment without re-authorization. RoadmapMDM and remote device wipe are on the post-pilot roadmap, as is SSO integration with your existing identity provider (targeted Q4 2026).
