Online store order tracking is the system that shows a customer where their order is, and shows your team what to do next. In Egypt, it has to handle cash on delivery, several couriers, partial deliveries and returns, all while keeping the customer informed. A tracking link added at the end of checkout does not cover that. This article lists the workflows and data you should plan before you build or buy.
What order tracking must do for an Egyptian online store
A useful order tracking system answers three questions at any moment: what state is this order in, who is responsible for the next step, and how much money is still expected from it. Those questions apply whether you sell music gear, groceries, clothing or spare parts.
Most stores start with a simple status list and add complexity later. That works until a courier returns half a delivery or a customer changes the address after the parcel has left the warehouse. Designing the workflow around those cases from the start is cheaper than patching them later.
The order status flow to design first
Define every status an order can hold, who can set it, and what the customer sees. Keep the list short. Ten clear statuses are easier to run than thirty overlapping ones.
| Status | Set by | Customer sees |
|---|---|---|
| Received | Checkout (automatic) | Order confirmation |
| Payment confirmed | Payment gateway or cash order approval | Confirmation of payment or COD accepted |
| Picking and packing | Warehouse staff | Order being prepared |
| Handed to courier | Dispatch scan or waybill | Courier name and tracking number |
| Out for delivery | Courier update | Expected delivery window |
| Delivered | Courier confirmation | Delivery confirmation |
| Delivery failed | Courier update with reason | Reschedule option |
| Returned | Warehouse receipt | Refund or exchange status |
| Cash collected | Courier settlement | Internal only |
| Closed | System, after settlement and returns window | Final receipt |
Each status should have an owner and a rule. For example, an order cannot move to "Handed to courier" unless it has a waybill number. That single rule prevents many of the "where is my order?" calls.
Courier integration: API, file import or manual
Your options for courier data usually fall into three groups:
- API integration: the courier pushes status changes to your system. This gives the most accurate tracking but depends on the courier's technical capability.
- File import: the courier sends a daily sheet of delivered, failed and returned parcels, which you import. This is common and workable for mid-volume stores.
- Manual entry with scanning: staff update statuses from a handheld or phone. This is the fallback, and it needs clear rules so the data stays reliable.
Whichever you choose, store the courier's own reference and the timestamp of every update. When a dispute happens, you need the history, not only the latest status.
Cash on delivery reconciliation
Cash on delivery is still a major payment method in Egypt, so reconciliation deserves its own workflow. The courier collects cash, then settles with you at a set interval. Your system has to match each settlement against orders, and flag the differences.
Build these checks into the design:
- Each order has an expected COD amount, including delivery fees and any discount.
- Each courier settlement lists the waybills and amounts collected.
- Mismatches go to a review queue with the order, the courier and the difference.
- Partial collections and refusals are recorded with a reason, not left as open balances.
For more on payment methods and how they fit into checkout, read our article on payment gateways for Egyptian businesses, which covers cards, mobile wallets and COD side by side.
Customer notifications that reduce support load
Customers contact support when they do not know what is happening. Send updates at the moments that matter: payment confirmed, handed to courier, out for delivery, delivery failed. Include the tracking link in each message.
Choose channels based on your customers. Many Egyptian shoppers respond to SMS and WhatsApp more than email. Keep messages short, state the next step, and avoid sending the same update twice. A good test is whether a customer can answer "what happens now?" from the message alone.
Returns, exchanges and failed deliveries
Returns are where order tracking often breaks. A returned parcel must be received, inspected, restocked or written off, and the refund must be linked to the original order and payment. Plan for:
- A return reason code chosen by the customer or agent
- A warehouse receipt step that updates stock
- A refund path that matches the original payment method, including COD refunds to a wallet or bank account
- A limit on how many delivery attempts happen before the order is returned
Connecting tracking to inventory and your POS
If you also sell in a shop or run several branches, order tracking has to share stock with the rest of the business. An online order should reduce the same inventory that the POS uses, and a returned item should return to the right branch. This is where a unified system pays off. Our ERP system service covers that linking, and our POS subscription option handles in-store sales that feed the same stock records.
Our work on retail projects includes a music gear store with full checkout, shipping and order tracking for customers. The lessons from that build, especially around status clarity and customer updates, apply to most stores selling physical goods.
How to scope the project
Before you ask for a quote, write down:
- Your average and peak daily orders
- Your couriers and how each one shares status data
- Your payment methods, with COD share if known
- Whether you have one warehouse or several branches
- Your return rules and refund methods
A clear list lets a vendor price the work accurately. If you want help turning these notes into a scope, contact our team and we will walk through the workflow with you.
Frequently asked questions
Do I need custom software for order tracking, or is a plugin enough?
A plugin can cover basic tracking for a small store with one courier and few returns. Once you have several couriers, COD reconciliation or multiple branches, the rules become specific to your business. At that point a custom or ERP-based workflow usually fits better.
How do I track cash on delivery payments properly?
Record the expected amount on each order, then match each courier settlement against those expected amounts. Put every difference into a review queue with the reason. Do not leave partial payments as open balances.
Which order statuses should customers see?
Show a short set: confirmed, being prepared, with courier, out for delivery, delivered, or delivery failed with next steps. Keep internal states such as cash settlement and reconciliation out of the customer view.
Can order tracking share stock with my physical shop?
Yes, if the online orders and the POS draw from the same inventory records. Returns should also update the correct branch's stock. This needs planning at the start, because retrofitting shared stock is harder than building it in.
