Noest Express is an Algerian courier with its own standalone API — it is not an EcoTrack tenant. DZBuild has a dedicated Noest integration, so linking it takes just two values.
What you need
API Token
User GUID
Both values come from your Noest merchant dashboard. The GUID identifies your store inside Noest; the token authenticates the API calls.
Linking Noest in DZBuild
Open
/dashboard/link-shippingand find the Noest tile.Click Lier / ربط.
Paste your API Token in the first field and your User GUID in the second.
Click Tester la connexion (« اختبار الاتصال »). DZBuild verifies the credentials live.
Click Lier et enregistrer (« ربط وحفظ »).
Per-wilaya prices are edited on the separate page /dashboard/shipping.
Auto-validate — read this before your first send
The credential modal has a Noest-only auto-validate switch, and it is off by default.
With it off, an order DZBuild pushes to Noest is created as an editable draft. Noest's logistics team never sees it until you open the Noest dashboard and validate it yourself.
Turn the switch on and DZBuild validates each order right after creating it (marked « تم التأكيد تلقائياً »). If that validation call fails, the order is still created and DZBuild marks it « يحتاج تأكيد يدوي من لوحة NOEST » — validate it yourself in the Noest dashboard. The trade-off: a validated order is no longer editable in Noest.
What gets synced
The list of wilayas Noest serves.
Communes per wilaya, matched against Noest's own synced commune list.
Home + desk rates per wilaya: Sync rates from provider fills the home price and the desk price for every wilaya. You can still override any wilaya by hand on
/dashboard/shipping.The desk list, with each desk's name, address, phone and map link — all surfaced by the Stop Desk picker. Each desk has a code whose number is the wilaya, e.g.
16Ais in wilaya 16.
What happens when an order ships
DZBuild submits the order to Noest with the customer's name, phone number (only one phone reaches Noest — a second customer phone is stored on the DZBuild order but not forwarded), address, destination wilaya and commune, the product summary, your order reference, and:
montant— the order total (products plus shipping), not the subtotal.poids— the weight in whole kilograms, defaulting to 1.can_open— set so the customer is allowed to open the parcel before paying.type_id— 1 for a normal delivery, 2 for an exchange, 3 for a pick-up. A pick-up forces the COD amount to 0, per Noest's spec.For desk delivery:
stop_desk: 1plus astation_code(Noest's desk code, e.g.16A) resolved from the synced desk list.commune_idis a separate field sent when known — it is not the desk reference.
If no station can be found for the wilaya the send is refused with « لا توجد نقطة استلام (Stop Desk) متاحة في ولاية … » rather than being downgraded to home delivery.
Commune resolution runs against the synced Noest commune list first, then a live API match. If neither matches, the send is refused — you get an Arabic error naming the commune plus up to five suggested nearby communes, and no tracking number is created. DZBuild refuses rather than risk delivering to the wrong commune.
Noest returns a tracking number. A bordereau download URL exists on Noest's API, but no button in the DZBuild dashboard opens it — Print label on a Noest order prints DZBuild's own HTML bordereau. Print Noest's official label from the Noest dashboard.
Noest throttles aggressively, so bulk sends are paced and retried automatically when the API returns a rate-limit response.
Common errors and fixes
Symptom | Likely cause | Fix |
"Test connection failed" | Wrong token, wrong GUID, or both | Re-copy each value from the Noest dashboard; the two are easy to swap. |
« البلدية … غير موجودة في قاعدة بيانات NOEST » | Noest doesn't know that commune spelling | Pick one of the suggested communes shown with the error, or click Actualiser on the Noest tile to re-sync the commune list, then re-send. |
« لا توجد نقطة استلام (Stop Desk) متاحة في ولاية … » | No Noest desk in the customer's wilaya | Refresh provider data, switch courier, or change the order to home delivery. |
The parcel never appears in Noest's logistics view | Auto-validate is off and the draft was never validated | Validate it in the Noest dashboard, or turn on auto-validate in the credential modal. |
Tips
Decide on auto-validate before your first bulk send — a batch of unvalidated drafts is easy to miss.
Commune matching depends on the synced Noest commune list. If you sell into a commune Noest recently added, click Actualiser on the tile instead of waiting for the automatic daily refresh.
Noest parcels carry no declared value and no insurance field — those are Yalidine-family only.