FAQ

What is DeliveryOS?
A multi-tenant SaaS platform for running delivery operations: dispatch, riders, tracking, customers, COD, billing, and optional fleet, inventory, and marketplace modules.
Who can use it?
Delivery companies, merchants that need deliveries, enterprise logistics teams, and riders (smartphone or button-phone channels).
Do riders need smartphones?
Smartphone riders use the DeliveryOS PWA. Button-phone riders can operate via SMS/USSD when your workspace and carrier integrations are configured—no app login required.
Does DeliveryOS support GPS?
Yes, for smartphone riders during active delivery operations, subject to plan features and device permissions.
Can merchants request delivery companies?
Yes, via marketplace workflows when enabled for merchant and provider workspaces.
How does the 7-day trial work?
New company and merchant workspaces receive a trial period on signup. Operational limits follow your subscription rules after trial.
Does it support MTN Mobile Money?
Not yet. Mobile Money is planned as a future integration—UI may show “Coming soon” until APIs are configured and tested.
Is SMS/USSD available?
The product is designed to support operational SMS and USSD. Production use requires Supabase/auth SMS for login and operational carrier configuration—verify on staging before launch.
Can businesses use their own riders?
Yes. You create rider records, assign jobs, and onboard smartphone or button-phone riders under your company workspace.
Can DeliveryOS integrate with websites or apps?
Yes, via REST API and webhooks on eligible plans.
How is company data protected?
PostgreSQL Row Level Security, role-based access, tenant-scoped RPCs, and private storage. See the Security page for details.