Frequently Asked Questions

MoboSafe is a fleet operations platform from Movozen Private Limited in Jaipur, India. It brings GPS tracking, trips, dashcams, assets, inspections, e-way bills, fuel management, inventory, accounting, and employee management into one workspace.

Yes. The platform also supports loading sheets, driver advances, fuel indents and pump settlement, stock and material requests, purchase orders, accounting documents, attendance, and payroll. Its September 2026 operations manual documents 132 operations across eight module groups.

MoboSafe supports a hardware-agnostic control tower. Compatibility depends on the device model, protocol, and data access. Share your current device list during the demo so the team can confirm the integration and any installation requirements.

No universal module entitlement is published. Discuss tracking, trips, assets, dispatch, fuel, inventory, accounting, and HR/payroll individually. Your proposal specifies the modules, users, vehicles, storage, and integrations included.

Fuel monitoring uses supported vehicle sensors to review tank levels and consumption. Fuel management handles the operational records: fuel indents, approvals, pump redemption, meter-photo evidence, audits, bills, and driver claims. The two workflows complement each other.

Yes. Organisation scope, branch or depot assignments, vehicle groups, and role permissions control which data users can view and which actions they can perform. Custom roles can cover approvals, exports, and individual modules.

Pricing is quoted for your fleet size, selected modules, hardware, storage, integrations, and implementation requirements. Confirm inclusions, limits, support, taxes, and third-party charges in your proposal.

Identify any GPS devices, dashcams, sensors, installation, connectivity, and replacement requirements when requesting a quote. Supported existing hardware may be reusable after compatibility checks; confirm each line item in your proposal.

Discuss a phased rollout and future capacity during the demo. Additional modules, vehicles, users, integrations, and storage may change the subscription and implementation scope; the agreed terms determine billing.

Book a demo and bring sample loading sheets, fuel statements, inventory records, and accounting or payroll requirements. Confirm any pilot, contract, cancellation, refund, and support terms directly with the team.

No. GPS tracking supplies location and vehicle activity. A transport ERP also supports the operational and financial work around the trip, such as dispatch records, fuel authorization, material inventory, invoices, and workforce administration.

The quote is scoped around the workflows and fleet you need to support. Module access, vehicle limits, storage, hardware and integrations depend on subscription and configuration. Agree the initial modules, user access, rollout sequence and any third-party charges before activation.

A trip reference provides traceability. The documented accounting workflow posts accounting documents when they are finalised; fuel and advance workflows have their own approvals and settlement records. During setup, verify which handoffs use references, which require a user action and which depend on a configured integration.

Active trips support changes to dates, waypoints, remarks, and documents. Vehicle and driver fields may be restricted. Completed and cancelled trips are read-only in the documented workflow.

Yes. Add intermediate waypoints during trip creation and order them to match the planned movement. The trip timeline records waypoint arrivals and other journey events.

Electronic proof of delivery adds linked signatures, photos and delivery timestamps to the trip close-out process. Planned-versus-actual route and stop analysis uses recorded tracking data. Importing a past trip adds its record, but does not recreate GPS positions that were never captured.

Yes. The documented asset types include vehicles, trailers, equipment, and containers. Available fields and inspection templates can be organised by equipment type.

The asset-management workflow supports decommissioning with a date, reason, and disposal details. The asset leaves active lists while its historical record remains available for reporting.

Store issue and expiry dates with the uploaded asset documents, then review upcoming renewals in the asset dashboard and document-expiry reports. Assign a person to update renewed documents. If your process needs notifications, confirm their configuration and recipients during setup.

Yes. Templates support custom sections, checklist items, pass/fail criteria, ordering, and critical-item flags. You can update templates as fleet requirements change.

Yes. The inspection workflow supports photos and notes for failed items, with the results retained in the vehicle’s inspection history.

The documented inspection workflow flags failed items for maintenance attention and lets templates identify critical items. It does not establish an automatic dispatch block. Test the clearance process with your inspection and dispatch teams before relying on it.

No. It helps your team document and track a claim. The insurer determines coverage, assesses the claim, and decides the settlement under the policy.

Yes. Claims reports can be organised by asset, incident type, insurer, or period to review frequency, amounts, and settlement history.

The documented workflow lets your team add documents and update claim and survey stages as information arrives. A recorded status is an internal tracking record, not confirmation of an insurer submission. Keep the insurer’s acknowledgement and correspondence with the case.

Draft and authorised pending sheets can be edited. The documented process for major changes to a finalised sheet is cancellation and recreation, preserving the record of the dispatch decision.

No. A loading sheet is an operational dispatch record. An e-way bill is a separate document with its own statutory requirements. MoboSafe provides a dedicated e-way-bill workflow.

It generates a numbered loading sheet with print and PDF output. Invoices, purchase orders and delivery challans can be attached as supporting files. Attaching a document is different from generating it; review any additional document-generation requirement separately.

The documented workflow compares total load weight with the selected vehicle’s capacity. The dispatch team should review that comparison before finalising. An enforced dispatch block is not established by the capacity check alone.

Yes. The documented Other Expenses workflow includes a General Expense option with a department and cost centre for costs that do not belong to a specific trip.

Yes. Rejected advance sheets show the reason and can be corrected and resubmitted through the approval workflow.

No. An advance is money entrusted for the trip; an expense records an actual cost. At settlement, compare approved advances with receipt-backed approved expenses and document the difference. Agree the balance-handling and accounting steps during setup.

No. A sensor measures the vehicle’s fuel level. The indent workflow records authorization, dispensing evidence, approval, and settlement. Use the fuel-monitoring solution when you also need supported sensor data.

Drivers can submit a fuel claim with the receipt, quantity, amount, and vehicle details. Reviewers compare it with fuel history and the trip before approving or rejecting reimbursement.

The documented workflow locks dispensed indents against editing and deletion. Disputed transactions can be flagged and investigated through the audit process.

The audit compares approved and dispensed quantities, with meter-photo evidence available for review. Accounts compares the pump statement with recorded transactions and investigates discrepancies before recording settlement. Agree evidence standards and discrepancy thresholds during setup.

The dispensing location and pump-user role need to be configured. The operator checks the approved indent, records the actual quantity, meter reading and nozzle, and uploads the meter photo. Set up the pump, rates and access responsibilities before using that location.

Yes. Reviewers can approve a subset of items or reduced quantities, and the store records the quantities actually dispatched. Remaining shortfalls can be followed up in the request workflow.

Yes. Stock movements include store transfers. The receipt workflow also supports goods arriving against a transfer order so the movement can be followed between locations.

The receipt workflow records shortages, damage and quality issues, with photographs where needed. Check the received quantities against the purchase order, transfer or direct receipt before completing it, so the discrepancy remains part of the stock record.

The item master stores units and costs, and inventory reports include valuation. Bring representative items and your accounting policy to setup so the team can confirm the available valuation method and any unit-conversion requirement. The catalogue does not specify a universal method for every stock type.

Yes. The document workflow supports references to trips, purchase orders, or contracts, allowing a reviewer to connect the entry with its operational context.

The documented workflow locks finalised documents. Corrections use linked credit or debit notes; draft documents can be edited before finalisation.

No. Report generation and filing are different capabilities. Confirm the precise export format, configured integration, and filing process with the team and your accountant.

The documented accounting module provides its own chart of accounts, journals, accounting documents and financial reports. Connecting those records to another accounting system is a separate integration question. Confirm the required records, posting responsibilities and supported data exchange before rollout.

Yes. The My HR self-service portal includes monthly payslips, leave applications, attendance records, profile updates, and expense requests, subject to the organisation’s access settings.

Draft payroll entries can be edited. The documented process after finalisation uses a supplementary payroll adjustment, with the amount and reason recorded for the next cycle.

The contractor module records contractor identity, contract terms, compliance documents, assignments, and payment information. Confirm how your worker categories and pay rules should be configured during setup.

The documented workflow covers monthly payroll with configured salary structures, earnings, allowances and deductions. It does not establish every per-trip or per-kilometre formula. Bring your worker categories and calculation examples so HR can check the required rules and outputs before activation.

Yes. A fence can monitor the whole fleet, selected vehicles, or a vehicle group. Active hours can further scope when the rule is monitored.

A dwell alert is triggered when a vehicle stays inside a boundary longer than the configured duration. It can help teams review loading, unloading, or other extended stops.

Timing depends on the location source, device reporting interval, configured rule and available notification channel. Test a known movement with your devices and recipients. The documented email, SMS and push options need configuration; confirm channel availability and any third-party charges in your quote.

The documented assignment workflow links a driver to one vehicle at a time. Assigning a different vehicle ends the prior assignment and retains the history.

The manual describes a weighted score for safety, efficiency, timeliness, and compliance, with configurable weights. Review the scoring window and event data before interpreting a result.

No. The document-review workflow lets your team approve, reject or request more information on a submission. Automated identity or document checks depend on a configured verification service. Agree which review is required before a driver is assigned.

Yes. Supported report workflows include recurring schedules and configured email recipients. Frequency and formats vary by report module.

A historical trip import adds record entries. It does not create GPS positions that were never captured, so route-level analytics depend on the actual tracking data available.

No. Filters, PDF, Excel or CSV output, and scheduling depend on the report workflow. Choose the reports your teams need and check their available date, vehicle, store, department or account scopes during evaluation. Access and source-module configuration also affect what can be reported.

Yes. Custom roles can select module-level and action-level permissions, such as viewing fuel records and approving indents without granting unrelated administrative access.

Yes. Team-member deactivation removes active access while preserving the account’s data and history. The documented workflow also supports reactivation.

Organisation scope, branch or depot assignments, vehicle groups and role permissions control data visibility and actions. Custom roles cover individual modules, approvals and exports. Configure the intended finance and HR access, then test both permitted records and restricted cross-branch records during onboarding.

Contact the MoboSafe team with your intended integration. Request the available endpoint documentation, authentication method, rate limits, plan requirements, and test process for your deployment.

No. Resolution, frame rate, streaming, event capture, and upload capabilities depend on the camera and its integration. Confirm the supported settings for the actual hardware.

Compatibility must be checked for the actual device model or external system. Share its documentation and the records you need to exchange. The team should confirm supported endpoints, read or write direction, authentication, update method and commercial access before the connection is included in your rollout.

There is no single reporting interval for every deployment. Location refresh depends on the tracker, configured interval, network coverage, and data connection. Confirm those settings on a representative vehicle; route replay uses positions actually recorded.

AIS-140 compliance is specific to the device, installation, applicable vehicle category, and state backend registration. Ask for the type-approval and state eligibility of the proposed model; using tracking software alone does not establish compliance.

An AI dashcam analyses video to flag supported road or driver events rather than only recording footage. ADAS and DMS capabilities depend on the camera, placement, calibration, and model. Alerts support driver awareness and review; they do not guarantee accident prevention.

Night performance varies by camera, lighting, installation, and lens. Ask to review footage from the proposed road and cabin cameras on representative night routes before deployment.

Create a driver profile, submit readable licence and identity documents, and have an authorised reviewer approve, reject, or request more information. Automated checks depend on the configured verification service; turnaround depends on the documents, reviewer, and service availability.

Record the issue and expiry dates when uploading vehicle documents, then review upcoming renewals and configured notifications. Your team must complete the renewal and update the record; reminders do not renew documents or guarantee compliance.

Confirm offline capture and retry behaviour for the mobile workflow in your deployment. Test signature, photo, timestamp, and location capture without connectivity and verify the record after reconnection before relying on it at remote delivery sites.

No. The official Part-B update API concerns transport details, including the vehicle number, place, state, and reason. GPS visibility can help operations review the journey, but Part-B is not a live-coordinate stream.

The official API documentation checked on 19 September 2026 permits eligible extension requests within eight hours after expiry as well as eight hours before it. Conditions, permissions, reasons, and outer limits apply. The request must be accepted by the portal; do not treat the window as permission to continue moving goods.

No. Software can help organise records and surface work requiring attention. Compliance depends on the actual goods, movement, documents, user actions, and applicable rules. No zero-penalty guarantee is made.

Yes. The documented trip-association workflow supports multiple active e-way bills for multi-consignment loads. Review the bill, vehicle, and route details before dispatch.