Skip to main content

Glossary

IDM uses these words with one meaning each, in the apps, the API and this manual.

People and organisations​

Tenant: A business that connects to IDM, such as a marketplace, a restaurant platform or a retailer. Its data, credentials and settings are fully separate from every other tenant's. The tenant owns the order; IDM owns the movement.

Delivery partner (delivery company): An independent delivery company that carries out deliveries with its own riders and vehicles, through the Partner Portal and the Dispatch app.

Rider: A person who carries deliveries for a delivery company, using the Dispatch app. Riders are added by their company; there is no public rider sign-up.

Sender: The person sending an item, through a delivery company's request link or a tenant's own app.

Recipient: The person receiving the item. They confirm their own drop-off location and their receipt through a secure link.

Operator / administrator: Intellisol staff working in IDM Admin.

Foundation identity: A protected super-administrator account that ordinary admin actions cannot delete, demote, suspend or strip of privileges.

Places​

Gateway: The top level of IDM's geography: a city region or operational hub, such as Accra.

Zone: A pricing and dispatch band within one gateway.

Suburb (area): The named locality people recognise. Every active suburb belongs to exactly one zone and gateway.

Boundary version: A complete, dated set of suburb boundaries. Exactly one is in force at a time, and every quote records the one that placed it.

Pin: The point a sender or recipient drops on the map, with the phone's reported accuracy. IDM resolves it to a suburb; a typed suburb name is never accepted on its own.

Prices​

Verified route distance: The road distance returned by an approved routing provider. It is the only distance that can price a delivery.

Included distance: Distance already covered by the base price.

Chargeable distance: Verified route distance minus included distance, never below zero.

Classification: Whether a trip stays in one zone (intra-zone), crosses zones of one gateway (inter-zone) or crosses gateways (inter-gateway). It selects the one distance rate that applies.

Distance multiplier: A versioned, approved factor per classification, applied to the subtotal. It is never assumed.

Pricing version: A dated, unchangeable set of rate rules. Exactly one is active per scope at a time.

Quote: A server price for a specific delivery, with an expiry time (QT-…).

Pricing snapshot: The frozen record of every input and output of a confirmed price. Disputes are settled by reading it, never by recalculating.

Fallback price: A pre-approved server price used when routing or pricing fails. It is marked and reviewed.

Deliveries​

Delivery job: The one record of a delivery for its whole life, whatever companies or riders touch it.

Delivery reference: The public, non-sequential identifier of a delivery, such as DX-9K4M7X2Q. IDM never shows its internal database IDs.

Service type: Express, Priority, Standard or Next day. It sets the time promise.

Offer: A time-limited invitation to one rider to take one delivery. The only way a rider is assigned.

Assignment: The active link between one rider and one delivery. A delivery has at most one at a time.

Handover: The sender's confirmation that the item has passed to the rider. It is what makes a delivery Picked up.

Receipt: The recipient's confirmation that they have the item.

Relay: Passing a delivery that is under way from one rider to another of the same company, verified with a one-time handoff code. It is not a new delivery and the customer's status does not change.

Exception: A stop in a delivery that an operator or the system must resolve, with a reason code.

Recovery: Finding another way to finish a delivery without changing its original facts.

Bulk delivery: One sender, one pickup and two to five recipients. A Bulk parent (BK-…) groups the child deliveries, each an ordinary delivery with its own price, rider and tracking.

Engines​

Dispatch: The engine that chooses eligible delivery companies and riders and sends offers.

HDZE (High Demand Zone Engine): The optimisation that batches compatible standard and next-day deliveries onto one rider's route, within time and detour limits.

Batch: Deliveries carried by one rider on one route, each still financially independent. Customers see a shared delivery queue and their position.

iHe (Intellisol Hexagonal Engine): The layer that maps a pickup to a hexagonal grid cell and returns a pool of nearby riders for Dispatch to consider. It never assigns.

Cell / grid disk: A hexagon of the H3 grid. A grid disk is a cell plus its rings: 1, 7 or 19 cells.

Candidate pool: The riders iHe returns. It holds no reservation and is always checked again.

Money​

Payment status: Whether a delivery has been paid. It is separate from delivery status.

Accounting period: A delivery company's calendar month of earnings. Closing it freezes the figures and issues the platform fee.

Platform fee: The versioned percentage of a delivery company's monthly earnings payable to Intellisol.

Blocking: The automatic result of an unpaid platform fee: no new work, while deliveries under way continue. Different from suspension, which an operator decides.

Trial: A period after a delivery company's account is activated during which it can take work while its verification completes.

KYC: The verification of a delivery company's documents.

Systems​

Idempotency key: A value sent with a request so that sending it again returns the first result instead of acting twice.

Outbox: Where events are written in the same step as the change they describe, to be published only after it is saved.

Webhook: An HTTPS message IDM sends to a tenant's system when something happens.

Request session: The secure, temporary context created when a sender opens a delivery company's request link.

Emergency control: An administrator's switch that stops one kind of work at once, with a reason and an expiry.