Built for Kuwait delivery operations

Delivery software for merchants who already own the customer relationship.

SawagIn coordinates delivery requests between merchants and independent drivers. Merchants buy tokens, create requests, track every step, and settle delivery money outside the platform.

1 token
per delivery request
3 apps
merchant, driver, desktop
Kuwait
area-first dispatch
SawagIn dashboard showing delivery operations
Merchant balance
Tokens ready
Dispatch
Drivers online
Settlement
Outside app

Not a delivery company. Not a public marketplace.

SawagIn is the coordination layer for merchants, stores, restaurants, and service teams that need repeatable delivery workflows without turning the software into the party handling driver payouts.

Merchant-side billing

Merchants fund their account with tokens. Creating a delivery request consumes a token, so software usage is separate from delivery settlement.

Independent drivers

Drivers receive offers, accept work, and complete the operational steps. Their commercial arrangement stays between them and the merchant.

Private merchant network

The site no longer promotes a public menu or customer marketplace. SawagIn is built for merchants managing their own delivery flow.

A delivery request moves through clear operational states.

1

Create request

A merchant enters pickup, dropoff, area, fee, and notes from mobile or desktop.

2

Consume token

The account balance is checked and one token is reserved for the delivery request.

3

Offer drivers

Available drivers receive the offer and the accepted driver follows pickup and delivery steps.

4

Track and close

The merchant sees status changes live and the order remains available in history.

Usage is simple enough for merchants to understand before they dispatch.

Instead of taking a percentage from drivers or touching the delivery fee, SawagIn tracks software usage as merchant delivery tokens.

Before dispatch

Balance check

A merchant needs available tokens before sending a delivery request to drivers.

Per request

One token used

The billing unit follows the action merchants care about: creating delivery work.

Commercial boundary

Delivery money is not the platform ledger

Driver payment, customer collection, and delivery fee settlement remain operational agreements outside SawagIn billing.

Built around the people doing the work.

SawagIn keeps each surface focused: merchants create and monitor delivery work, drivers respond and complete it, and desktop supports busy operators.

SawagIn merchant app

Merchant mobile

Create delivery requests, watch active status, review history, and manage account access from Android.

Open merchant app page
SawagIn driver app

Driver mobile

Go online, receive delivery offers, accept work, and follow pickup-to-delivery steps from Android.

Open driver app page
SawagIn desktop operations screen

Merchant desktop

A Windows surface for shops with a counter, dispatcher, or back-office user handling live orders.

Download Windows app

Designed for controlled access, not anonymous signups.

Merchant and driver onboarding is structured around contracts, phone verification, and admin-managed rollout so the operational network stays controlled.

Contract acceptance

Signup is connected to role-specific contracts before accounts enter normal operations.

Phone OTP path

The product model expects phone verification for merchants and drivers, with provider wiring handled as an integration step.

Admin oversight

Admins can manage merchants, drivers, areas, pricing, rollout, billing settings, and operational visibility.

Bring SawagIn into your merchant delivery workflow.

Use the contact channel for onboarding, token package setup, merchant app access, driver rollout, or desktop installation help.