Saudi sellers: let your agent handle fulfillment and courier handoff on every Salla and Zid order

The Riyadh ops bottleneck

You sell on Salla or Zid. Orders land all day. Someone on your team opens the store dashboard, reads each new order, decides which courier gets it, opens the courier portal, retypes the address and the COD amount, creates the shipment, then goes back to the store and marks it fulfilled with the tracking number. Per order that's three to six minutes. At 80 orders a day that's a full-time job whose entire output is copying numbers between two screens.

It's also where errors live. The COD amount mistyped as 240 SAR when the order was 420. The address pasted from the wrong order. The order that never got fulfilled because the dashboard was refreshed before someone got to it.

What the agent does on every order

Connect your Salla or Zid store and your courier to the Wassel MCP endpoint, then give the agent one standing instruction:

On every paid Salla or Zid order: create the fulfillment, create the courier shipment with the delivery address, customer phone, and COD amount, write the tracking number back to the order, and message the customer their tracking link on WhatsApp.

What runs, in order, untouched:

• Salla or Zid signals the paid order. The agent reads the full order — items, address, phone, COD amount, city.
• The courier gets a clean shipment request with the COD amount pulled straight from the order total. No retyping.
• Salla or Zid gets the shipment number and tracking URL written back, so support can find any order in one place.
• WhatsApp Cloud sends the customer their tracking link before they think to ask.

Addresses that don't parse cleanly go to an exception list the agent flags, so your team reviews the handful of unclear ones instead of every order.

Why it matters

1. The copying job disappears. No one moves numbers between the store and the courier portal. That's a full headcount of work returned, or a team that now handles three times the volume.
2. COD amounts are exact. The shipment COD is the order total, every time. Mistyped COD is one of the most expensive ops errors in KSA — the courier collects the wrong amount and you chase the difference for weeks, if you ever get it.
3. Nothing falls through. The agent doesn't forget order 61 because it's busy. Every paid order becomes a shipment within minutes.
4. One agent, both platforms. If you run Salla and Zid side by side, it's the same instruction and the same endpoint. You don't build two integrations.

Point your agent at the endpoint

Open the Wassel dashboard, copy the MCP endpoint into your Claude, ChatGPT, or Cursor config, and connect your Salla or Zid store plus your courier key. Run it on one real order and watch the shipment and tracking message appear, then let it run on the live queue.

One check before go-live: make sure phone number is required at checkout. KSA couriers need a valid Saudi mobile number for COD, and an order missing it lands in the exception queue instead of becoming a shipment.

If your courier isn't connected yet, tell us which one. We add integrations off what sellers actually run.