Stop polling. Salesupply pushes status updates to your endpoint the moment something happens — stock changes, tracking numbers, shipment confirmations, returns processed.
When an event occurs in the Salesupply platform, our system sends an HTTP POST request to the URL you registered for that event. Your endpoint responds with a 2xx status code to confirm receipt. No polling, no rate-limit budgeting, no missed events.
Triggered when the available stock of a product changes in our OMS — when a shipment is booked, a return is received, or a purchase order is received.
Use caseKeep your sales channels in sync with real warehouse stock.
Triggered when a shipment transitions to "shipped" status with a valid tracking number.
Use casePush tracking numbers back to your sales channel and trigger customer notification emails.
Some warehouse systems push shipment data to Salesupply via webhook instead of polling. Inbound webhooks are secured with a shared secret.
Use caseLower latency for warehouse partners that support push-based shipment confirmations.
Triggered when a return arrives at the warehouse and is processed, with condition mapping (sellable / unsellable) and return reason.
Use caseTrigger customer refunds, exchanges, or grading workflows automatically.
Triggered when the warehouse books an inbound delivery against an open purchase order, with received quantities synced back to the OMS.
Use caseReplenishment workflows, supplier reconciliation, automated PO closure.
Status transitions through the fulfillment lifecycle — confirmed, allocated, picked, packed, shipped, delivered. Pushed to your endpoint as they happen.
Use caseReal-time order status pages, customer notifications, internal dashboards.
If your endpoint doesn't respond with a 2xx, we retry. No silent failures, no missed events.
Stock update webhooks use unique queue items — if the same event fires multiple times before processing, only the latest state is delivered.
Inbound webhooks from warehouse partners are secured with a shared secret. Validate every incoming payload before processing.
Configure your webhooks directly through our developer portal. Choose which events you need and where to deliver them. Self-service, no support ticket required.