For the complete documentation index, see llms.txt. This page is also available as Markdown.

Architecture

PreBilt’s mobile solution is designed to run on a wide range of devices: industrial scanners, Android phones, iPhones, tablets, and even Windows-based devices. It provides a fast, intuitive experience following SAP Fiori design principles.

The architecture separates three key layers:

  • The PreBilt Mobile Solution – used by warehouse staff to carry out day‑to‑day operational tasks

  • The PreBilt Admin Portal – used by administrators to manage configuration, users, devices, and environments

  • The Cloud Backend – a secure configuration and authentication layer

At the centre of the design is a simple principle:

Warehouse processes should keep working - even if config systems go offline. That’s why the mobile solution communicates directly with SAP Public Cloud for all operational transactions. This removes the need for middleware and reduces operational dependency on intermediary systems.

PreBilt Mobile Solution

Key characteristics

  • Built using SAP UI5 for a consistent, enterprise-grade user experience

  • Packaged as a mobile app, allowing App Store / Play Store distribution

  • Direct API communication with SAP S/4HANA Public Cloud

  • Single codebase for Android, iOS, and desktop/tablet support

  • Can function even if the PreBilt backend is temporarily unavailable

Why this matters

  • Your warehouse teams get an ultra‑stable solution

  • You avoid costly custom development

  • Updates can be delivered quickly without lengthy impacts on operations

PreBilt Admin Portal

The Admin Portal gives administrators full control of how PreBilt behaves - without technical skills.

Customer benefits

  • Configure transactions, menus, branding, warehouses, and behaviour in minutes

  • Make changes without needing IT or development teams

  • Immediately deploy updates to devices through the cloud

  • Secure, controlled access with role‑based permissions

Backend & data layer – powered by Supabase

PreBilt uses Supabase, a secure, scalable Backend‑as‑a‑Service, as the foundation for configuration storage and device authentication.

What the backend does

  • Authenticates devices and config users

  • Stores configuration for transactions, menus, warehouses, and environments

  • Holds logs for audit trails and customer support (if enabled)

What it doesn’t do

It never sits between the Mobile Solution and SAP Public Cloud. This ensures:

  • Maximum security

  • Higher performance

  • No dependency on PreBilt’s backend for mission‑critical processes

Why this matters

  • Zero downtime risk from intermediary servers

  • Faster SAP communication

  • Lower operational cost

  • Secure and auditable authentication infrastructure

How data flows through the architecture

The PreBilt architecture is intentionally simple:

  1. The PreBilt Admin Portal stores configuration in the backend.

  2. The Mobile Solution retrieves configuration directly from the backend based on the environment and warehouse.

  3. All transactions (picking, put away, bin-to-bin etc.) communicate directly with SAP S/4HANA Public Cloud.

  4. If the backend is offline, the mobile solution continues working using already-downloaded configuration.

This approach ensures maximum stability for warehouse operations and protects you from backend downtime.

Last updated

Was this helpful?