Webhooks and feature gating
React to events with webhooks, and understand how plan-based feature gates control what's available.
Two platform concepts matter when you build on Vendor: webhooks (how you hear about events) and feature gates (what your plan unlocks).
Webhooks
Webhooks let external systems react to what happens in your store — an order placed, a payment captured — without polling. Payment gateways also use signed webhooks as the authoritative signal that money moved, which is why a payment is only marked complete on a verified webhook.
Feature gating
Capabilities across the platform are controlled by feature gates tied to your plan — for example, bulk stock import, saved cards, or specific reports. If an endpoint or screen is unavailable, the relevant feature may not be included in your plan.
Was this article helpful?