Connecting a courier

Ordexs connects to Algerian couriers directly through their APIs, so an order can be sent for pickup without leaving the dashboard and its status comes back automatically.

To connect one, open Delivery, pick the courier, and enter the credentials it issued you — usually an API token or an id/key pair from the courier's own dashboard. Ordexs validates them on save, so a wrong key is reported immediately rather than failing later on a real parcel. For ZR Express that is the Secret key (in ZR: API Rest → Token API → create a token; ZR shows it only once) and the Tenant ID. Nothing else is needed: Ordexs sets up live status updates with the same keys (see "Live updates").

Once connected you can send an order to that courier from the order card or in bulk from the orders list. Ordexs creates the parcel on their side, stores the waybill code on the order, and moves the order to Shipped.

What the courier receives. The order number (ORD-00042) as the parcel's reference, unless the agent the order is assigned to has "Agent name as the courier reference" on in their Team profile. Each product line is "product name + variant", for example "Sneakers Size: S · Color: Red", or the name you set for the courier slip on the product page.

Order types. Couriers distinguish a normal delivery from an exchange, a pickup and a cash-collection (recouvrement). Which types are available depends on the courier; the order form adapts to what the selected one supports.

How many couriers you can connect at once depends on your plan: 1 on Try, 3 on Starter, 5 on Growth, unlimited on Scale.

The same courier credentials can only be connected once per store. Adding a connection whose credentials are exactly the same as an existing one (every field the courier asks for — both of them where there are two, like ZR Express's Secret key and Tenant ID) is refused with a message naming the existing connection ("already connected to this store as …"); open that one instead. A connection that differs in any field — for example a second token for the same courier account — is allowed, and the same credentials can be connected to two different stores. Spaces, tabs or line breaks pasted around a key are removed when you save, so they never cause a failed connection or a duplicate.

If a dispatch fails, the courier's own response is kept against the order so the reason is readable rather than a generic failure.

What couriers charge you is read from the couriers. For ZR Express, Yalidine (and Guepex), Ecotrack-based couriers (DHD and others), Noest and Ecom-DZ, Ordexs knows what each parcel costs to deliver and to return. The courier's price list (per wilaya, home and stop desk) is saved when you connect the courier and kept under a week old; when you send a parcel, its price for that wilaya and delivery mode is saved on the order (Ecom-DZ gives its own price for the parcel when it is created). ZR and Yalidine then confirm each parcel's own price in their status updates, and a courier payout statement has the final word. Analytics and the Cash section use those real prices. eLogistia gives its delivery prices but not its return price.

Return fee field. Only couriers that don't give their return price (eLogistia, Zimou, Maystro, Procolis) show a Return fee field in their settings window: what that courier charges for a parcel that comes back. Leave it empty to use the default return fee in Analytics → Costs, where those couriers' fees can also be edited in one list.

More in Delivery & couriers

Still need help?

Ask the assistant from the search box in your dashboard. It answers from these same guides, in English, French or Arabic, and can make changes for you. Or write to us and a person will reply.