Skip to content

Websites & Apps

Webhook

A message one system sends another automatically the moment an event happens, like a new order or payment.

In Arabic ويب هوك

What is Webhook?

A webhook is how one system tells another that something happened, at the moment it happens. You give the store a URL, and on every paid order the store sends the order data to that URL, so the courier creates a waybill or the accounting system adds the invoice right away.

The alternative is polling: your system asks every ten minutes "anything new?", which delays work and uses up requests. But a webhook sends once, so if the receiver is down at that moment the message can be lost. Good senders retry, and a good receiver handles a duplicate message without creating two orders.

Why does Webhook matter in marketing?

It makes the next step after payment happen immediately, instead of waiting for a periodic sync or manual entry.

  • 01

    Speed up fulfillment

    Creating the shipment or sending the customer a WhatsApp message at payment time cuts preparation time and order-status questions.

  • 02

    Pick the events that matter

    You do not need every event. Choose those that trigger real work: paid order, cancellation, refund, out of stock.

  • 03

    Plan for failure

    Decide in advance who gets alerted when webhook messages fail, and how missed orders get handled.

Worked example

  1. 1Situation

    A perfume store in Buraidah collects paid orders and sends them to the shipping company once an hour.

  2. 2Data

    The average wait between payment and shipment creation is 30 minutes, and an order can wait up to 60 minutes.

  3. 3Calculation

    With a webhook the shipment is created within a minute, saving about 29 minutes per order on average.

  4. 4Decision

    The store adopts the webhook and reviews failed orders at the end of each day so no order is lost.

Common mistakes

  • Not verifying the sender

    Anyone who knows the URL can send fake data. Check the signature or secret the provider sends with each message.

  • Processing duplicates twice

    Providers may resend the same event. Use the event ID to ignore repeats, or you will create two shipments for one order.

  • Long processing before replying

    If your system replies slowly, the provider may treat the message as failed and resend it. Acknowledge quickly, then process.

Frequently asked questions

What is the difference between a webhook and an API?

With an API you ask whenever you want and get an answer. A webhook comes to you without asking when the event happens. Example: you ask the API for an order's status, and the webhook tells you the moment the status changes.

Do Salla and Zid support webhooks?

Yes, both platforms offer events you can subscribe to, such as order created and order status updated, through developer settings or apps. Check each platform's documentation for the available events and how to verify messages.

Takteek services that help here

When connecting stores to shipping and accounting systems we use webhooks for urgent events and add a log of failed messages for the client's team to review.

Talk to Takteek

Want to put this to work for your business?

Tell us about your business in four steps and we will come back with a clear plan that starts from your current numbers. The consultation is free.

  • A plan built on your numbers
  • One team for ads, content and store
  • Free consultation, no commitment
Message us on WhatsApp
Tell us about your business
What do you want to achieve?

Approximate monthly ad budget

Pick at least one option, then your approximate budget.

How can we reach you?
+966
You are
Review your request

The consultation is free, with no commitment.

Free consultation×