Can I configure Waslni for Oman?
Yes. Configure OMR pricing, Arabic and English, operating areas, service types, registration fields, and supported payment integrations. Local licences and merchant approval remain the operator’s responsibility.
Configure OMR pricing, Arabic and English, operating areas, service types, and driver-registration fields. Supported payment providers are connected only after the operator obtains an approved merchant account.
Oman has different travel patterns across Muscat, Salalah, Sohar, and other areas. A focused operator should validate demand, driver supply, coverage, and support rather than assume that one city’s settings fit the whole country.
Language, payment preferences, seasonal demand, and trip distances may vary by operating area. The operator can configure these rules, but it remains responsible for local research, approvals, and commercial decisions.
Waslni can be configured with OMR pricing, supported languages, operating areas, service types, and dynamic registration. One role-aware app serves riders and drivers, authorised staff get quick administration inside it, and the full web dashboard controls the operation. App Experience selects rides, delivery and shops, or both. Payment support is confirmed after merchant approval and testing.
The operator can connect a supported local or card provider after merchant approval, then choose the methods offered at launch. Cash and the in-app wallet are optional settings.
Admins define the registration sections, fields, and supporting documents for each service type. The operator’s Omani legal advisers determine the official requirements.
Define approved areas in Muscat, Salalah, Sohar, or elsewhere with separate pricing and operating rules. Airport-specific rules require separate approval and testing.
Choose from the supported interface languages, including Arabic with RTL and English, across the unified app and both administration surfaces.
The same branded iOS and Android app opens the right rider or driver mode after sign-in. Configure it for city rides and parcel delivery, a restaurant and grocery marketplace, or both.
Permission-aware admin tools let authorised team members handle urgent approvals, live operations, and support checks without switching to another app.
Manage dispatch, users, service types, pricing, payment options, documents, roles, reports, shops, and content from the main web dashboard.
Apply the brand, set OMR, choose languages, define approved operating areas, and select App Experience.
Configure service types, fares, operating rules, and locally approved registration fields.
Connect a supported provider after merchant approval and test every enabled payment and settlement flow.
Submit the app for store review and validate dispatch, support, and finance in a limited area before expansion.
Yes. Configure OMR pricing, Arabic and English, operating areas, service types, registration fields, and supported payment integrations. Local licences and merchant approval remain the operator’s responsibility.
Choose a provider that supports your Omani entity, required methods, and settlement model. Waslni confirms technical support after merchant approval and testing.
The operator must confirm company, transport, app-store, and merchant-account requirements with qualified Omani advisers. Waslni does not issue licences or approvals.
A basic airport service area and fare can be configured. A holding queue, flight-data link, or automatic airport fee requires separate approval, scope, and testing.
The platform records trips, commissions, and wallet movements. The operator defines the settlement destination and schedule according to provider support, contracts, and local accounting requirements.
Explore OMR pricing, languages, the unified app, in-app administration, the full web dashboard, and App Experience.