Appearance
Vocabulary & lifecycles
Milogi uses a small set of words everywhere — in the app, in notifications and in this documentation. Here is what they mean, and the statuses each object moves through.
The words
| Term | Meaning |
|---|---|
| Corridor | A route between two countries, e.g. China ⇄ Algeria. Milogi is corridor-agnostic: any pair of countries from the catalog works. |
| Operation | One delivery job, from the customer's request to the final handover. It has a code like OP-NB2S6P, a route, a goods type, a total weight, a quote and one or more batches. |
| Request | The first state of an operation: the customer (or the provider, for a walk-in customer) describes what must be shipped. |
| Quote | The price the provider proposes for the operation, in a currency of their choice (DZD by default). |
| Walk-in operation | An operation the provider creates directly for a customer who has no Milogi account — only a name, a phone and an agreed price. |
| Batch | A portion of an operation that travels together in one traveler's baggage. Each batch has a public tracking code like MLG-VEJDZJP5, a weight and a number of pieces. |
| Piece / item | One physical unit inside a batch (a carton, a bag…). Pieces can be marked delivered, damaged or missing individually. |
| Declared contents | A flag the provider sets on a batch to certify its contents were inspected. A batch cannot be picked up before it is declared. |
| Trip | A traveler's journey: origin, destination, departure date, baggage capacity in kg and number of bags. Batches are assigned to trips. |
| Payload | The traveler's own goods on a trip. Payloads reduce the trip's free capacity like batches do. |
| Offer / assignment | When a provider assigns a batch to a trip, the traveler sees it under Batches to carry. |
| In-house traveler | A traveler managed by a provider (name + phone, no login). Their trips are private to that provider. |
| Location | A provider's physical place: a warehouse (where goods are received) or a drop point (where customers pick up). |
| Ticket | A QR voucher scanned at a location. A customer ticket (TKC-…) is the drop-off/pickup receipt of an operation; a traveler ticket (TKT-…) is the payout voucher of a batch. |
| Ledger | The list of amounts owed between the parties: customer → provider (the accepted quote) and provider → traveler (payouts). Money itself moves off-platform; the ledger records it. |
| Entitlement | A limit or feature granted by your plan or your user group: open trips, searches per day, team seats, statistics depth, landing page… |
| Plan / subscription | The paid tier attached to a provider or traveler profile, with a 14-day trial. See Plans & pricing. |
| Showcase / landing page | The dedicated public page of a premium subscriber, at milogi.dz/@handle, optionally on a custom domain. |
Operation lifecycle
REQUEST ──► QUOTED ──► ACCEPTED ──► DISPATCHING ──► PARTIALLY DELIVERED ──► COMPLETED
│ │ │ │ │
└───────────┴───────────┴─────────────┴───────────────────┴──► CANCELLED| Status | What it means | Who moves it forward |
|---|---|---|
| REQUEST (draft) | The customer sent a request, no price yet. | Provider sends a quote. |
| QUOTED | A quote is waiting for the customer. The provider can still update it. | Customer accepts. |
| ACCEPTED | The price is agreed and recorded in the ledger. | Provider creates the first batch. |
| DISPATCHING | At least one batch exists; goods are being split and carried. | Batches get delivered. |
| PARTIALLY DELIVERED | Some batches landed, others are still on the way. | Automatic. |
| COMPLETED | Every active batch is delivered. Reviews open. | Automatic. |
| CANCELLED | The operation was cancelled. | — |
A walk-in operation skips the request/quote steps: it is created ACCEPTED with the agreed price.
Batch lifecycle
CREATED ──► ASSIGNED ──► PICKED UP ──► IN TRANSIT ──► ARRIVED ──► CUSTOMS CLEARED ──► DELIVERED
│ │ │ │ │ │
│ └─(unassign)──┘ └─────────────┴──────────────┴──► RETURNED
└──► CANCELLED| Status | What it means |
|---|---|
| CREATED | The provider split off this batch; it is not on a trip yet. Can be cancelled. |
| ASSIGNED | The batch is booked on a trip. The provider can still remove it from the trip. |
| PICKED UP | The traveler has the goods. Requires declared contents. |
| IN TRANSIT | On the way. |
| ARRIVED | Landed in the destination country. |
| CUSTOMS CLEARED | Through customs. |
| DELIVERED | Handed over to the provider's location. Pending pieces become delivered, a payout line opens for the traveler, and the operation status is recomputed. |
| RETURNED | Sent back after pickup. |
| CANCELLED | Cancelled before pickup. |
Each transition is recorded as a timestamped event, shown on the public tracking page and in the customer's operation view.
Trip lifecycle
OPEN ⇄ FULL ──► DEPARTED (shown as "In transit") ──► COMPLETED
│ │
└───────┴──► CANCELLEDOnly OPEN trips with a departure in the future appear in provider searches. The traveler changes the status from the My trips page.
Ledger statuses
| Status | Meaning |
|---|---|
| PENDING | Nothing settled yet. |
| PARTIAL | Part of the amount was settled. |
| SETTLED | Fully settled — either recorded by the provider, confirmed by the traveler, or settled by a QR ticket scan. |
Ticket statuses
Issued → Scanned (someone at the location checked it) → Settled (payment collected / traveler paid).