Connect Salla, Zid or Shopify to Shipping in Saudi Arabia and Automate Waybills

Orders arrive in your shipping dashboard with the receiver, National Address, items and COD amount already filled. You pick a carrier, create the waybill and the tracking number returns to the store.

Three things move automatically. The order arrives with its items, receiver, phone number, address fields and payment method. You choose a carrier and create the waybill without retyping anything. Then the tracking number and status are written back to the order so your customer sees them in the store. Each step used to be manual work and a chance for a typo.

The National Address is most useful when it arrives on the waybill as its own value, not buried in a long address line. Check how your store collects it: as a dedicated field, as part of the address text or not at all.

If your store has a custom field for it, map that field to the short address in your shipping platform. If it does not, add one at checkout first, since a connection can only pass on what the store collects.

Connection takes minutes. The same approach works across Salla, Zid, Shopify and API-based stores.

Gather what you need first: admin access to your store, the list of payment methods you offer, your pickup address and the carrier rules you want as defaults. Ten minutes of preparation avoids most of the back-and-forth later.

The payment mapping tells the platform which orders are COD and how much the courier should collect. List every method on your checkout and mark it as COD or prepaid, using the exact names your store sends.

Place real test orders through your public checkout, not an admin screen, so you see what a customer's order looks like on arrival.

Saudi customers write in Arabic, English or a mix of both, and the courier's system may read one better than the other. Store the data as the customer typed it, then check how the label prints each language before you rely on it.

Standardise phone numbers too. Saudi mobile numbers begin with 05 locally, or +966 5 internationally, and a store may send either format. Normalise them to one format so the courier always has a number that can be dialled.

Automation moves orders quickly, but not every order should go straight to a courier. Decide in advance which ones pause for a human check: a missing short address, an unusually high COD amount, a first-time customer in a remote area.

Give one person the job of clearing that queue each morning and again before the pickup cut-off. It is a small habit that keeps flagged orders from being forgotten.

When tracking and status flow back, customers see progress in their order page and contact you less. Fewer 'where is my order' messages free your support team.

Decide which statuses the customer should see. Too many updates create noise and too few create anxiety. Picked up, out for delivery, delivered and a clear message when there is a delivery problem are usually enough.

Orders change after they are placed. A customer cancels, edits an address or asks to swap an item. If the store and the shipping platform disagree, a courier may arrive for an order that no longer exists, or a parcel may go to an old address.

Agree a rule for who changes what and until when. A simple one: edits are made in the store before the waybill is created, and after that through your shipping platform, with the customer informed.

Connecting should show up in your numbers. Time a sample of orders handled by hand before you connect, then time the same kind of orders afterwards, and note the number of corrections and where-is-my-order messages.