> For the complete documentation index, see [llms.txt](https://docs.theconfigteam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theconfigteam.com/prebilt-for-public-cloud/support/frequently-asked-questions.md). # Frequently asked questions ## Product overview #### What problem does PreBilt solve that SAP Public Cloud doesn’t? PreBilt provides operationally efficient mobile workflows for warehouse and manufacturing processes that go beyond standard SAP Public Cloud UX, without requiring custom development. #### When would we need PreBilt vs using standard SAP apps? PreBilt is typically used where high-volume, scan-driven, or user-specific workflows are required that standard SAP apps cannot efficiently support. ## Application, devices and hardware #### What devices can we run PreBilt on? PreBilt supports Android, iOS, and enterprise scanning devices. A browser-based version is available for testing and support scenarios. #### How are devices set up for users? Devices are registered via a QR code and then authenticated against the customer’s SAP system. #### Can we manage devices through our existing MDM (e.g. SOTI)? Yes. PreBilt can be deployed and managed via standard MDM tools. ## Configuration & flexibility #### How much can we configure without development? Core processes, menus, and user experiences can be configured through the admin portal without transports or custom code. #### Do we need to make changes inside SAP? Yes. Initial setup such as communication arrangements, roles, and allowlists must be maintained in SAP. #### Can we customise the solution beyond configuration? PreBilt follows a clean-core approach. Customer-specific requirements are handled either through configuration or agreed enhancements. ## Product updates & clean core #### How are updates delivered? App updates are delivered via app stores or MDM. Configuration changes can be tested before being promoted to production. #### Will updates impact our existing processes? Updates are designed to be tested in advance to ensure compatibility before go-live. ## Licensing, users & access #### How is licensing structured? Licensing is user-based and managed through the admin portal. #### What happens if we exceed our licence limit? Additional users will be blocked from logging in until the licence is extended. #### Can we manage users ourselves? User access is controlled, with changes managed through agreed support processes. ## Performance, stability & connectivity #### What happens if SAP is slow or unavailable? Performance is dependent on SAP response times. PreBilt provides visibility to help identify where delays originate. #### Do we need additional middleware or infrastructure? No - PreBilt is designed to work directly with SAP Public Cloud using standard APIs. ## Co-innovation & roadmap #### How are new features decided? Features are prioritised based on common customer requirements and product strategy. #### How are customer-specific requirements handled? Unique requirements are delivered separately as part of project work. ## Support, logs & troubleshooting #### How do we raise support issues? Support requests are raised through the portal. #### What information is available for troubleshooting? Audit logs and system diagnostics are available to support issue investigation. ## Branding & UX #### Can we apply our own branding? Yes — branding such as logos and colours can be configured through the admin portal. ## Data & privacy #### Where is our operational data stored? Operational data remains within SAP Public Cloud. #### What data does PreBilt store? PreBilt stores configuration and authentication data required to operate the solution. #### What is the retention period for logs and system data? * Chat logs: 24 hours * Audit logs: 14 days * Licence usage data: retained and deleted on request * Suspended user data: retained and deleted on request #### **Is full payload data stored in logs?** By default, full payload data is not stored. When detailed logging is turned off, only metadata required for operational logging and diagnostics is retained. Full payload data is only captured when detailed logging is explicitly enabled by an administrator for a specific device, including in break-glass scenarios. Any stored detailed log data is retained for 14 days in line with the standard log retention policy. ## Core functionality & processes #### What warehouse processes are supported? PreBilt supports common warehouse processes such as picking, putaway, stock movements, and inventory operations, depending on SAP capabilities. #### Does PreBilt support batch and serial number handling? Yes, where supported by SAP Public Cloud APIs and configuration. ## Project delivery & implementation #### Can PreBilt be implemented incrementally? Yes - deployments are typically delivered in phases aligned to business priorities. #### How does rollout work for multiple sites? A common approach is to establish a template at one site and scale to others.