Classic WM and EWM
RFC, BAPI and OData
Read only shadow mode start
SAP stays the system of record
No middleware

APXR for SAP

Running SAP?We go deeper there.

The people who build APXR have spent two decades inside SAP warehouses, on classic WM and on EWM. This page is for the operations and IT teams on SAP: how APXR is built to connect, where the connector stands today, and how a pilot starts.

Where it
stands

The native SAP connector is not yet running in production at any customer site. An SAP pilot starts the way every APXR pilot starts: from an export of your pick lists, running alongside your current process. The native connection is scoped with your SAP team during the pilot and switched on once it clears your security review.

Classic WM and EWM

Built to stay through the migration.

SAP ECC mainstream maintenance ends at the end of 2027, so most classic WM sites are deciding when and how to move to EWM. APXR is designed to run on the system you have today and to stay in place while the system underneath changes: the copilot talks to one connector abstraction, with an adapter for classic WM and an adapter for EWM beneath it. Your workers keep the same guidance through the move.

Connectivity

How APXR reaches your SAP system.

APXR runs in its own AWS environment and connects to your SAP warehouse system across a tunnel your network team controls. Task data flows out, confirmations flow back, and the connection is scoped to the SAP function modules the copilot uses.

Designed pattern

Site to site VPN

An IPsec tunnel between your network and APXR's AWS environment. The SAP connection runs inside that tunnel rather than across the public internet, and your team holds both ends of it.

During the pilot

Read only to start

The same tunnel carries read only traffic until your security review clears write back. Nothing about the connection changes when it does; the permissions on the SAP side do.

Anything else

Other patterns

If your security team requires a different connectivity model, we will scope it with you. Ask us before you assume the answer is no.

Data flow

YOUR NETWORK SAP EWM classic WM (LE-WM) APXR AWS Adaptive copilot and connector YOUR FLOOR Smart glasses on warehouse WiFi SITE TO SITE VPN TLS Task data and guidance Pick confirmations, written back to SAP
  • SAP stays the system of record on your side of the tunnel.
  • Barcode verification runs on the device, not in the cloud.

Integration approach

How the connector is built.

  • Built for SAP EWM and classic WM (LE-WM), configured per environment.
  • Uses RFC, BAPI, and OData, the standard SAP interfaces that certified SAP partner applications use.
  • Bidirectional by design: warehouse orders come in, pick confirmations go back, with queue, stockout, and priority handling.
  • No middleware and no custom server side development in your SAP system.
  • Never writes to the database directly and never bypasses SAP business logic.
  • SAP remains the system of record at all times.
  • Starts in read only shadow mode. Write back is enabled after your security review.
  • Supported releases are confirmed per environment. Tell us the SAP release you run and we will tell you where it stands.

Shadow
mode

Live SAP write access triggers a security review that no VP of Operations can waive, typically 4 to 10 weeks at an enterprise. We design around it: the pilot runs from your export first, the connection starts in read only shadow mode, and an IT prerequisites pack ships with the LOI, so your review starts on signature day instead of after kickoff.

The SAP experience behind it

Two founders who have run SAP projects for a living.

Felipe R. Cordeiro, CEO

20 years of SAP warehouse implementation across classic WM and EWM, 20+ enterprise distribution centers, 3,000+ picking rules. Led greenfield SAP EWM at Brazil's third largest air cargo terminal.

Ricardo Rabay, COO

Two decades as an SAP solution architect across more than 30 enterprise implementations in logistics and order to cash: transportation, shipping, receiving, inventory, and 3PL integration.

The whole team is on the About page. For data handling, the LLM boundary, and control status, see the Trust Center.

Founding Pilot

Ninety days. Your data decides.

We bring the glasses, start from your current spreadsheet or system export, and measure your baseline against APXR with success criteria agreed before signature. The fee is fully creditable to your first rollout contract. If the numbers do not convince your team, you keep the report and walk away.

Founding pilot slots are limited.

Book a Call

Prefer email? felipe@apxr.com

  • Glasses loaned at no charge. A phone works too.
  • Set up from your spreadsheet or system export
  • Runs alongside your current process first, so nothing breaks
  • Founder level support throughout
  • Measured performance report, yours either way