Develop Rental Management Web Software - Qr code power bank rental

Project Brief: Web Software Development for Pow3rOn

Overview

We need a freelancer or development team to build the web software version of Pow3rOn, a power-bank rental management platform for hospitality venues such as restaurants, bars, cafés, beach venues, clubs, hotels, and similar locations.

The business model is based on placing charging devices/power-bank units on tables or in specific venue locations. End users can access the service, receive an unlock code, use the battery for a selected rental period, and the platform must track usage, merchants, devices, payments, rental sessions, and revenue distribution.

This is not a simple website.
We need a real web-based operational platform with admin logic, merchant logic, device assignment, unlock code flow, reporting, and scalable structure for future integrations.

The product must be built as a working SaaS-style web platform, with clean architecture and clear separation between super admin, merchant admin, venue management, and end-user rental flow.


---

Main Goal

Build a web platform that allows us to:

manage merchants and venues

manage battery devices manually by MAC address and battery number

assign devices to specific venues / objects / tables

define merchant revenue percentage when applicable

generate and manage unlock codes

have a backup code mechanism if the main unlock flow fails

handle end-user authentication and OTP confirmation

manage rental sessions and battery status

simulate or connect payment logic

track operational activity, telemetry, and audit logs

provide reporting and revenue visibility

be ready for staging and later real production launch



---

Product Structure

The software should include the following major areas:

1. Super Admin Panel

This is the main control layer for the platform owner.

Functions required:

create and manage merchants

create and manage venues / objects / locations

create and manage tables inside venues

create and register devices manually

each device must support:

MAC address

battery number / internal serial number

status

assigned venue

assigned table


set pricing plans

set rental durations

set merchant-specific commission or revenue percentage

monitor active rentals

view unlock code history

issue or regenerate backup codes

review logs and system activity

access reports and revenue summaries

manage users and roles


2. Merchant Admin Panel

Each merchant should have restricted access only to their own business data.

Functions required:

view only their venues, devices, rentals, and reports

manage operational data inside their allowed scope

view battery/device assignment by venue and by table

monitor current rental activity

see revenue split / commission data if enabled

access support-related operational data

not have access to global platform configuration


Important: merchant scope must be based on merchant ID, not user ID only.

3. Venue / Table / Device Management

The platform must support operational mapping.

Required logic:

one merchant can have multiple venues

one venue can have multiple tables

one device can be assigned to a specific venue and optionally to a specific table

devices must be manually added through the admin panel

every device must support manual identification by:

MAC address

battery number


devices should be movable between venues or tables

system must keep assignment history or at least current assignment state


4. End User Access Flow

The platform must support the user-facing rental logic.

Expected flow:

user enters phone number manually

user receives OTP for confirmation

after successful recognition, user is treated as an existing platform user in future sessions

user proceeds to rental screen

user selects rental option

payment is processed or simulated

unlock code is generated

if the standard unlock flow fails, a backup code must be available

rental session begins

session status is tracked

session ends or is manually closed depending on business logic


5. Unlock Code and Backup Logic

This is a critical business requirement.

Required logic:

each rental/session must generate an active unlock code

if the battery does not unlock correctly through the main backend process, the system must allow visibility of the active code or replacement with a new valid code

backup code flow must be controlled by admin logic

all issued codes must be logged

status of code usage should be trackable

system should prevent uncontrolled code duplication or abuse


6. Pricing and Rental Logic

The software must allow pricing configuration.

Current expected base pricing:

30 minutes = custom

60 minutes = custom


The architecture should allow future expansion for:

custom duration plans

merchant-specific pricing

promotional pricing

special venue pricing


7. Payments

The first version may start with a mock or staging payment layer, but the architecture must be ready for real integration.

Required:

clear payment status model

pending / paid / failed / refunded states

payment linked to rental session

webhook-ready structure

future support for real online payment provider integration


8. Telemetry and Device Status

The system should be ready to receive or simulate device signals.

Required:

online / offline status

lock / unlock related state

heartbeat or last seen timestamp

basic device health visibility

architecture ready for real hardware bridge integration later


9. Reporting and Revenue Logic

The software must provide reporting tools.

Required:

total rentals

active rentals

completed rentals

failed unlock attempts

revenue summary

revenue by merchant

revenue by venue

merchant percentage / commission calculation

date filtering

export-ready structure if possible


10. Audit and Logging

Important admin actions must be traceable.

Required logging for:

device creation and reassignment

merchant percentage updates

unlock code generation or replacement

payment status changes

OTP events

role-sensitive admin actions

rental lifecycle events



---

User Roles

The platform must support at least these roles:

Super Admin

Merchant Admin

Staff / Operator (optional but recommended)

End User / Customer


Role permissions must be properly separated.


---

Recommended Tech Expectations

We are open to your best implementation choice, but the system should be built with a modern, scalable stack.

Preferred direction:

Frontend: React / Next.js

Backend: Node.js + TypeScript

Database: PostgreSQL

ORM: Prisma or equivalent

Caching / sessions / queue if needed: Redis

API: REST or clean API-first architecture

Deployment-ready structure: Docker / Docker Compose preferred


The codebase should be clean, documented, modular, and easy to continue with another developer later.


---

What Must Be Delivered

We need a working web software build, not only design or mockups.

Minimum expected deliverables:

full source code

frontend web panel

backend API

database schema and migrations

role-based auth structure

admin panel and merchant panel

core rental logic

device management logic

unlock code and backup code logic

reporting module

environment setup instructions

staging-ready deployment instructions

documentation for how the system works

basic seed/demo data for testing



---

Important Functional Requirements

Please make sure the platform supports the following exact business needs:

1. Devices must be entered manually by MAC address and battery number


2. Devices must be assignable to specific venues/objects and optionally to tables


3. Merchant-specific percentage must be supported as a direct configurable percentage


4. End users log in with phone number + OTP


5. Existing users should be recognized after registration and go directly into the user flow


6. There must be a primary code flow and a backup code flow


7. Active rental and code status must be visible in admin logic


8. Platform owner must have visibility across all merchants


9. Merchant admin must only see their own scope


10. The system must be structured for future real hardware and payment integration




---

UX and Interface Expectations

We do not need only a technical backend.
The web version must have a clean and practical interface.

We expect:

admin-friendly dashboard

easy forms for adding merchants, venues, tables, and devices

simple active rentals view

device status view

reporting pages

logical navigation

responsive layout for desktop and tablet use

clear status labels and operational visibility



---

Quality Expectations

The software should be developed as a real commercial product foundation.

We expect:

clean architecture

secure role handling

proper validation

production-minded structure

readable code

scalable database design

no hardcoded business logic where configuration is required

easy future extension



---

Project Outcome

At the end of this project, we want a working web platform MVP that can be used for:

internal operations

merchant onboarding

venue and table mapping

device assignment

rental session control

unlock code handling

revenue monitoring

pilot testing in real venues

preparation for public launch



---

What to Include in Your Proposal

Please include:

your recommended stack

examples of similar admin/SaaS/web platforms you have built

timeline estimate

milestone breakdown

what is included in MVP

what you would leave for phase 2

total fixed price

post-delivery support availability



---

Final Note

This project is intended to become a real operational product, not just a prototype.
We are looking for a freelancer who can build a solid web-based MVP with correct business logic, clean architecture, and realistic production direction.

Please structure the system so it can later connect to:

real payment providers

real SMS/OTP providers

real device/hardware integration

production infrastructure Show More