Shipping is not a button on checkout. This article explains zones, weight, cash on delivery, branch pickup, tracking states, failure, returns and reconciliation, and lays out a test matrix before launch.
Checkout ends at the buy button, but the order begins there. After payment comes a longer path: address validation, shipping calculation, label creation, handover to the carrier, tracking, and proof of delivery or failure management. Every step has a state, and every state has to appear to the customer, the operations team and the finance team in the same form.
What most often ruins a shipping experience is not the shipping price. It is ambiguity: a charge that appears after payment, a city the carrier does not cover, an order that ships at an unexpected weight, or a return the system does not know how to value. Good integration makes the rules explicit before the customer sees a number, and gives every exception a written procedure.
Map the rules before the shipping screen
Before designing any screen, write the shipping rules on one page. Who delivers where, which weight is charged, whether dimensions change the rate, which services are available in each zone, what the cash-on-delivery limit is, and where pickup is possible. The code is built on these rules, not the other way around. A screen built before the rule imposes a decision nobody made.
An unwritten rule shows up as a production error. If you have not defined how a multi-piece shipment is priced, the system will behave in some way, and you will discover it on the first large order. Write test examples for every rule before you start, and show the customer the cost and the promise before payment, not after. Give one person ownership of the shipping rules, because a rule owned by everyone is owned by nobody.
| Rule | What it decides | What you test |
|---|---|---|
| Zones | Where the carrier delivers, and on which service | An in-zone address, an out-of-zone address, a border address |
| Weight and dimensions | Which rate applies and which weight is charged | Actual weight, volumetric weight, a multi-piece shipment |
| Cash on delivery | The limit, who collects, and when cash is remitted | A successful order, a refusal at the door, a cash refund |
| Branch pickup | Which branch, which hours, which identity | Branch selection, a ready-for-pickup notice, a no-show |
| Tracking states | How a carrier status maps to your order status | A duplicate event, an out-of-order event, a long pause |
| Failure | What happens after a failed delivery attempt | A first attempt, a second attempt, a wrong address |
| Returns | Who receives, who inspects, who restocks | A full return, a partial return, a damaged item |
| Address | Required fields and the Arabic format | An address without a postal code, a new building, a differently named district |
| Reconciliation | How the carrier invoice matches orders | A weight difference, a lost shipment, an open claim |
Carrier interfaces are not identical
Every carrier exposes a different interface: some calculate a rate immediately, some expect a periodic file, some return a tracking number at once and others after a delay. Some send automatic notifications when a status changes, others require polling. Do not assume two carrier interfaces behave the same way. Write one integration layer inside your system, then adapt each carrier inside it.
Treat every call as something that can fail or repeat. Create the label once with a unique key, record the request before and after the call, handle timeouts, and retry without creating a duplicate shipment. Keep the tracking number and the label file in your system, not in an employee's inbox. These details separate an integration that works from one that appears to work.
The Saudi address
A Saudi address is not one field. It needs a city, a district, a street, a building number, a postal code and additional numbers, and it may need a landmark. Do not force a Western form onto an address that does not follow it, and do not leave every field as free text without validation. Balance validation against refusing a valid address because an optional field is missing.
Test the address in Arabic and English, on mobile, and when it changes after payment. What happens if the customer changes the district after the label is created? Is the shipment cancelled and reissued, and who carries the difference? Write the answer before it happens, and show the customer a clear state instead of a generic error. The address causes more returned shipments than any other field, and receives less design attention than any other field.
Cash on delivery and branch pickup
Cash on delivery changes the cash cycle, not only the payment page. You need a maximum value, a collector, a remittance schedule, a reconciliation against orders, and a rule for a customer who refuses the parcel. Define these states in the system, make the order status reflect them, and do not let finance discover the difference at month end.
Branch pickup adds another dimension: which branch, which hours, which identity is required, and how long the order waits before it is returned. Send a ready-for-pickup notice, set a collection window, and write what happens after it. The customer needs to know the place and the time, and the branch team needs a clear list rather than an inbox search. These small details decide whether the option actually works.
Tracking, failure and returns
From reading to shipping
Want this built, not just explained?
Bring us the problem behind the article. We will tell you what it takes, what it costs, and whether we are the right team.
Carrier states do not always arrive in order. A delivery notice may arrive before a warehouse dispatch notice, or the same event may repeat twice. Do not show the raw status to the customer. Map it to a limited set of states in your system, and define the rule for a conflict. Keep the full event log for audit, because the log is what proves what happened when the parties disagree.
Failure is part of the path: a wrong address, an unavailable customer, a refused delivery attempt. Write a procedure for each case: who calls, when the retry happens, when the parcel comes back, who carries the cost, and how stock is updated. A return is not the end of an order; it is a new order with its own states and accounting. Without written procedures, every employee handles the case their own way.
Reconciliation and reverse shipping
The carrier invoice does not match orders automatically. A weight may differ, a return may be charged, a parcel may be lost, or a claim may stay open. Build a periodic reconciliation report that matches the tracking number to the order, the cost and the state, and name who reviews differences before the invoice is approved. Without that report, small errors become a permanent deduction nobody can explain.
Reverse shipping needs a return authorisation, a receiving state, an inspection, and a decision: restock, scrap or repair. Tie each decision to the invoice, the stock and customer service. When that chain is clear, returns become a process you can measure rather than a monthly surprise. Also review ecommerce development, and the earlier post on Saudi checkout conversion fixes, to see where shipping meets checkout.
The integration checklist before launch
Use this list when reviewing the scope with your team and the carrier. Every line needs an owner, a test and a recorded result, not a verbal promise.
Zone rules: write who covers what, and define the service available in each zone.
Weight and dimensions: define the charged weight and the multi-piece rule.
Cash on delivery: define the limit, collection, remittance and reconciliation.
Branch pickup: define branches, hours, identity and the collection window.
Unified states: map carrier states to your order states, and define the conflict rule.
A unique key: create the label once, and handle duplicates and retries.
Failure and returns: write the procedure, the cost, who restocks and when.
Reconciliation: build a report matching label, order and invoice before launch.
The test matrix
Good testing does not stop at the happy order. Run the full matrix: an in-zone order, an out-of-zone order, a volumetric-weight order, a multi-piece order, a cash-on-delivery order, a branch-pickup order, a failed attempt, a full return, a partial return, a duplicate tracking event, an out-of-order event, and a lost shipment. Record the result for each case, and rerun after any rule change.
Connect shipping to payment in measurement. Baymard's 50-study average puts cart abandonment at 70.19%, 22% of users have abandoned because checkout was too long or complex, and the average form has 11.3 fields. Shipping is part of that form: if its cost appears late or unclear, you have added another step to a path that needed fewer. No percentage compensates for a bad experience, but clarity reduces surprise.
Frequently asked questions
Can any carrier be integrated? Usually, but every carrier has a different interface and behaviour. What matters is one internal layer, testing each carrier separately, and not assuming that what works with one works with another.
When should the shipping cost appear? Before payment, after the address is entered. Showing it after payment turns shipping into a surprise, and surprise is a known reason for abandonment.
How do we handle an address without a postal code? Make it required where it exists, and allow a documented alternative where it does not. Do not reject a valid address because of a general rule.
Who pays for a return? That is a commercial decision and a published policy, not a technical one. Write it on the returns page, apply it in the system, and show it to the customer before purchase.
Do we need a warehouse? Not necessarily. You can connect an external warehouse or an order management system. What matters is knowing who owns the stock, who updates it, and when.
Sources
- Baymard: cart abandonment rate — the 50-study 70.19% average.
- Baymard: checkout usability — 11.3 fields on average, and 22% who abandoned because checkout was too long or complex.
- Ecommerce development — scope, payment, shipping and delivery.
- Rasad integrations — how carrier interfaces and internal systems are connected.
- Rasad's published price bands — the figures this article works from.
Cover image: MobiusDaXter, CC BY-SA 4.0, via Wikimedia Commons.

