Software Applications
The interface layer that makes the platform usable at scale.
Bobnet OS and Chain Management System provide the foundation: electronics control and business orchestration. Software Applications are where that power becomes day-to-day execution — configuration, workflows, monitoring, and real-time interaction with devices.
Role-specific interfaces
Bulk control over fleets
Coherent operational visibility
Software Applications
The interface layer that makes the platform usable at scale.
Bobnet OS and Chain Management System provide the foundation: electronics control and business orchestration. Software Applications are where that power becomes day-to-day execution — configuration, workflows, monitoring, and real-time interaction with devices.
Install paths:Plug & Play • Minimal • Modular
Coverage:Romania • EU • International
Handover: Docs • Onboarding • Training
What this layer solves
Software is the surface people touch
This layer includes the web and mobile applications used by administrators, operators, and end-users to configure device fleets, run workflows, monitor performance, and interact with devices in real time — built to keep operations fast, consistent, and mistake-resistant as networks grow.
Position in the stack
Apps sit above orchestration — and make it usable
The platform stays coherent because Software Applications don’t reinvent logic. They expose it. Business configuration, rules, workflows, and device behavior remain governed beneath — while the interface layer makes that power executable by humans.
- Clarity per role Each stakeholder sees what they need — nothing else.
- Fleet reality Bulk actions and consistent workflows replace manual repetition.
- Single source of truth Apps reflect one connected system — not scattered tools.
The Software Applications
These are the key product surfaces that sit on top of the Chain Management System. They map to distinct personas and operational responsibilities — while staying connected through one backend.
WEB APP
Backoffice
Web App
Admin surface for configuration and governance. Define product catalogs, pricing models, policies, user permissions, device groupings, and operational constraints.
- Catalog + assortment configuration
- Pricing logic, promotions, and eligibility
- Rules & policy management
- Device groups, locations, and rollout controls
Governance
Auditability
Fleet configuration
MOBILE APP
Ops
Mobile App
Field-facing execution app designed for speed. Guided tasks prevent mistakes and keep operations consistent across large distributed fleets.
- Guided replenishment workflows
- Barcode/QR scanning with traceability
- Stock movement and exception handling
- On-site device servicing & checklists
Guided flows
Traceability
Field speed
MOBILE APP
End-User
Mobile App
Customer journey surface. Handles identity, entitlement, reservations, purchases, and access — while remaining consistent across multiple device types.
- Pair with devices and authenticate access
- Reservations and purchase flows
- Receipts, history, notifications
- Edge-case friendly recovery flows
Frictionless UX
Identity
Access
MOBILE APP
On-Device
Kiosk UI
When mobile isn’t available (or shouldn’t be required), the kiosk UI provides a complete self-service flow on the device itself — consistent, accessible, and fast.
- Purchases and reservations on device
- Validation and identity checks
- Admin mode for local servicing
- Designed for multiple form factors
Self-service
Accessibility
Fast UX
Monitoring
Technical Console
Monitoring surface for the full device fleet. Tracks device health, connectivity, sensor states, transaction anomalies, and operational drift — and routes issues into actionable workflows.
- Fleet-wide health dashboards and alerts
- Device-level diagnostics & logs
- Anomaly detection (inventory, access, payment)
- Bulk updates and configuration rollout
Device health
Alerts
Bulk controls
Diagnostics
How the apps connect through one backend
When mobile isn’t available (or shouldn’t be required), the kiosk UI provides a complete self-service flow on the device itself — consistent, accessible, and fast.
When mobile isn’t available (or shouldn’t be required), the kiosk UI provides a complete self-service flow on the device itself — consistent, accessible, and fast.
FAQ
Quick answers about what belongs in Software Applications — and what stays below in the orchestration layer.
Why not put business logic inside each app?
Because you’ll eventually ship inconsistencies. Apps should expose and execute the same governed logic from a shared backend. That’s what keeps pricing, validation, and workflows coherent across roles and device types.
What does “guided workflows” actually mean?
It means the app doesn’t just list tasks — it enforces the correct order, collects required proof (scans, checks), prevents skipping critical steps, and records outcomes so the system stays auditable.
How do you handle fleets at scale?
Bulk controls (grouping, targeting, staged rollouts), consistent workflows, and monitoring loops. The apps are built to support fleet operations without forcing humans to micromanage individual devices.
Where do monitoring and reporting live?
Monitoring is an application surface (console) backed by device telemetry, orchestration events, and diagnostics. Reporting/analytics can be separate surfaces, but they should be fed by the same system of record.
Tell us what you want to automate
Contact us and we’ll recommend the best software solutions.