How to run several couriers from one system: Bosta, Aramex, J&T Express, Mylerz and ShipBlu
The short answer
To manage Bosta, Aramex, J&T Express, Mylerz and ShipBlu from one system, connect each courier account to a single operations system that receives your store's orders, books each parcel with the courier you choose, and reads every tracking update back into the same order record. Booking, waybills, pickups, address matching, tracking and store updates then happen in one queue instead of in a separate portal for each courier. Ora Dash is the operations system for e-commerce brands in Egypt, and it works this way.
Why does running several couriers get hard?
Each courier gives you its own portal, its own district list, its own waybill format and its own tracking states. That is reasonable: each portal is built to run that courier's network well. The trouble starts on your side, when one team has to move orders between all of them.
The usual pattern is a spreadsheet for orders, an export uploaded to each courier portal, and tracking numbers copied back into the store by hand. Every handoff is a place where an order can be booked twice, booked with the wrong district, or forgotten after it leaves the warehouse. The fix is not a better spreadsheet. It is one system that owns the order from the moment the store sends it until it is closed.
What does one system need to do for multi-courier shipping?
Whatever tool you use, check that it covers the full shipping job, not only booking:
- Receive orders from your store automatically, with the customer, items and address.
- Book shipments in bulk with the courier you pick, through the courier's own API.
- Print waybills for many orders at once.
- Schedule pickups on dates the courier accepts.
- Match each Egyptian address to the courier's district list, including Arabic spelling variants.
- Show one timeline per parcel, with every movement, attempt and reason.
- Read parcels that were created directly in the courier's portal.
- Stop the same order from being booked twice.
- Write fulfilment and the tracking number back to the store.
How do you book shipments in bulk across couriers?
Start from a single list of orders that are ready to ship. Select all of them, one product, or a group, and choose the courier. Before anything is sent, run a check that splits the batch into orders that are ready (address matched to a district, details complete) and orders that need review, each with a reason.
Only the ready orders go to the courier's API. The tracking number comes back and is saved on the order. The orders that need review stay in front of your team with a clear reason, before anything is sent.
How do you print waybills and schedule pickups?
Once a batch is booked, print all its waybills together, in the label size and language your warehouse uses. Then request the pickup from the same screen, on a date the courier offers. If a customer changes their address or phone before the parcel moves, edit the live shipment rather than cancelling and re-creating it, so the tracking number stays the same.
How do you match Egyptian addresses to each courier's districts?
Egyptian addresses arrive in many forms: the same area written with different Arabic letter forms, Arabic-Indic digits, or extra words such as «محافظة». A courier needs one exact district from its own list, so a raw address often fails or lands in the wrong zone.
A good matcher normalises the text first (letter variants, digits, filler words), then proposes a district. Your team should confirm suggestions rather than have them applied silently, and should be able to save an alias once (for example, a neighbourhood nickname) so future orders match it automatically. The courier's own district list is always the reference.
How do you track parcels from several couriers in one dashboard?
Every courier reports progress with its own status names. To follow all of them in one place, the system has to translate each courier's statuses into one shared set of states and attach them to the order as a single timeline: picked up, in transit, out for delivery, each delivery attempt with its reason, delivered or returned.
Two details matter. Updates should arrive by webhook and also be checked on a schedule, so a missed message does not leave a parcel stuck. And a final state such as delivered should never be overwritten by a late, older update. Parcels that are late or stuck should collect in one list so someone owns them.
What about parcels created in the courier's own portal?
Teams still create some parcels outside the system: a quick shipment from the courier's portal, or a file upload during a busy day. If your system only knows about parcels it booked itself, those orders disappear from view. Choose a system that also reads the parcels on your courier account, links them to the right order, follows them, and updates them in the store.
How do you stop an order from being shipped twice?
Double booking usually happens when two people work from two copies of the same list. The protection is structural: one queue of ready orders, a single record per order, and a booking step that skips any order that already has a shipment. Flagging possible duplicate orders before they are confirmed helps too, because the same customer sometimes orders twice by mistake.
How do you connect Shopify to Bosta and the other couriers?
Shopify keeps orders and fulfilment status; the courier keeps the parcel. Shopify's own developer documentation describes fulfilment as a separate step in which a merchant or app marks items as fulfilled and attaches tracking information. The link between the two is therefore a system that reads the order from Shopify, books it with the courier, and writes the fulfilment and tracking number back.
Check that the write-back covers the whole life of the order, not only the first step: fulfilled with tracking when the courier picks up, delivered when it arrives, and returns when it comes back. Then Shopify stays accurate without anyone copying numbers by hand.
Which approach fits: courier portals, a spreadsheet, or one system?
A plain comparison of the three common set-ups, for a brand that ships with more than one courier. It compares only how each set-up handles several couriers together:
- One list for all your couriers: portals: one courier each · spreadsheet: by hand · one system: yes
- One tracking timeline per order across couriers: portals: per courier · spreadsheet: by hand · one system: yes
- Arabic address matched to each courier's districts before booking: portals: per courier · spreadsheet: by hand · one system: yes, for every courier
- One record per order across couriers: portals: per courier · spreadsheet: by hand · one system: yes
- Store updated for every courier from one place: portals: per courier, where offered · spreadsheet: by hand · one system: yes
- Ready with no set-up: portals: yes · spreadsheet: yes · one system: needs connecting first
How does Ora Dash handle multi-courier shipping?
Ora Dash, the operations system for e-commerce brands in Egypt, connects your Shopify, WooCommerce or EasyOrders store, your WhatsApp Business number and your couriers (Bosta, Aramex, J&T Express, Mylerz and ShipBlu) in one system. From the ready-to-ship list your team books in bulk, prints waybills, schedules pickups and follows every parcel's full timeline. Addresses are matched to courier districts with Arabic spelling differences handled, and suggestions are confirmed by your team. Parcels created outside Ora Dash are still read, and the store is kept updated with fulfilment, tracking, delivery and returns. Our team sets it up around the way your brand already works; you can book a demo to see it.
Frequently asked questions
Can I manage Bosta, Aramex, J&T Express, Mylerz and ShipBlu shipments from one dashboard?
Yes, if you use an operations system connected to each courier's account. It books parcels through each courier's API, translates their tracking states into one shared set, and shows every parcel on its order's timeline. Ora Dash works this way for e-commerce brands in Egypt.
How do I connect Shopify to Bosta?
You need a system that reads orders from Shopify, books them through the Bosta API, and writes fulfilment and the tracking number back to Shopify. Ora Dash connects to your Shopify store and to Bosta and keeps Shopify updated with fulfilment, delivery and returns.
Do I still need each courier's own portal?
You keep your account with each courier, because the connection runs through it, and the portal stays useful for account matters. Day-to-day booking, labels, pickups and tracking can move into the one system, and parcels you still create in a portal are read back and linked to their orders.
Why do Arabic addresses fail when booking a shipment?
Couriers expect an exact district from their own list, while customers write the same area in different spellings, digits or with extra words. Normalising the text and matching it to the courier's districts before booking, with a person confirming the suggestion, helps prevent these failures.
How do I avoid shipping the same order twice?
Work from one queue of ready-to-ship orders with one record per order, and use a booking step that skips any order that already has a shipment. Flag possible duplicate orders from the same customer for review before they are confirmed.
Can I sign up for Ora Dash on my own?
No. Ora Dash is set up for each brand by our team around the way it already works. To see it, book a demo through the site or message us on WhatsApp.
One operations system runs everything after the order.
Book a demo