Skip to content

Mobile · Workforce

Access. Act. Done.

An ERPNext-native employee self-service mobile experience for HR, payroll, leave, tasks, and approvals across deskless and field teams.

Foundation
ERPNext-native
One source of truth
Primary audience
Deskless-ready
Built for mobile workforces
Production context
Tanaqol + Luxury Cart
Reference deployments

Audience and fit

Built for teams with a clear job to do.

Start with the operating context, not a feature checklist.

Construction field teams

Give employees access to leave, payroll, and tasks across job sites.

  • Mobile self-service
  • Distributed teams

Plant and shift workers

Bring HR information, alerts, and approvals to the production floor.

  • Shift context
  • Fast approvals

Multi-location retail

Serve store employees who rarely work from an ERP terminal.

  • Branch workforce
  • LavaSell companion

How it works

One connected workflow.

A short path from the operational trigger to a governed result.

  1. 01 · 01

    Access

    Read live HR, payroll, leave, attendance, and task information from ERPNext.

    • Employee view
    • Real-time balances
  2. 02 · 02

    Act

    Submit requests, complete tasks, and respond to approvals from mobile.

    • Self-service requests
    • Manager actions
  3. 03 · 03

    Close the loop

    Route updates through ERPNext workflows and keep the system of record current.

    • Workflow status
    • Central audit trail

Core capabilities

What the product does.

Focused capabilities cover the work that makes this product distinct.

HR and payroll self-service

Expose payslips, leave, attendance, and employee details on mobile.

  • Fewer back-office tickets
  • Live ERP data

Tasks and approvals

Assign, complete, review, and approve work away from a desk.

  • ERPNext workflows
  • Mobile actions

Field-ready experience

Design workflows around drivers, store staff, plants, and job sites.

  • Multi-site teams
  • Focused mobile UI

Operating boundary

Know what connects, where it runs, and what requires scoping.

Deployment, integrations, ownership, and limitations stay visible before rollout.

Platform dependency

ERPNext is required

LavaDo is a companion to the ERPNext data and workflow model, not a standalone HR system.

  • Shared records
  • Existing permissions
Limitation

Offline is roadmap scope

Do not assume every workflow works without connectivity; offline requirements must be confirmed explicitly.

  • Connectivity review
  • Workflow-by-workflow scope

Rollout is scoped

Employee count, modules, authentication, devices, languages, and support determine the engagement.

  • Adoption planning
  • Security setup

Proof and commercial path

Used in Tanaqol and Luxury Cart contexts.

The reference names these deployments but does not provide approved product-specific outcome metrics.

Used in Tanaqol and Luxury Cart contexts.

The reference names these deployments but does not provide approved product-specific outcome metrics.

  • 2 — Production examples
Talk to Us

A scoped ERPNext add-on.

Users, workflows, modules, authentication, deployment, training, support, and any offline requirement shape the quote.

  • No public numeric price
  • ERPNext dependency is explicit

Scope the right next step

Ready to put this product in your operating flow?

Share the systems, users, volumes, locations, and constraints involved. LavaLoon will map them to an accountable next step.

LavaLoon × Balubaid Group

Delivery in the Kingdom of Saudi Arabia through our strategic partnership with Balubaid Group, Jeddah — local presence, regional reach.

Our partnership