Webhook
Checking another system every few minutes to ask whether anything has changed wastes effort and always arrives late. The alternative is to let that system tell you: when something happens, such as an order being paid, it sends a small message straight to an address you gave it, and your system reacts at once. That automatic message to your address is called a webhook.
Technically a webhook is an HTTP request, usually a POST with the details in JSON, that the sending system makes to a web address of yours when an event occurs. The method it replaces is polling, where you ask again and again. Your side must answer quickly with a success code and do the heavy work afterwards, otherwise the sender assumes failure and sends the message again.
Because messages can be repeated, arrive out of order or be forged, a careful receiver treats each one as possibly a duplicate, checks the signature the sender attaches and keeps a record of the event numbers it has already handled.
In practice
A webshop sends a message to the warehouse system the moment an order is paid. Within seconds the order is on the pick list, instead of waiting for a check every fifteen minutes. If the warehouse system is down, the webshop tries again later, and the order number lets the warehouse recognise a repeat and ignore it.
Further reading
Ready to see BizBloqs on your own process?
Book a demo and we will walk your warehouse and order flow end to end — inbound, storage, picking, shipping, returns — and tell you honestly what BizBloqs would change.
Two questions about your own operation
How many of your articles sit in a pick location they empty less than once a month?
Part one: Laying out a warehouse does not start with the racking
After your last integration, how many systems hold a stock quantity for the same item? Name them.