What if SAM doesn't have webhooks enabled for my tenant?
Some older SAM tenants haven't been migrated to V3 webhooks yet. In that case the plugin falls back to scheduled stock sync only — same correctness, just a longer worst-case lag. We can help organise the webhook activation with SAM head office.
How is the webhook secured?
HMAC-SHA256 signature on every request, verified against a shared secret you set in Settings. The secret is stored encrypted at rest (AES-256-GCM). The signature header is checked with a constant-time comparison so timing attacks can't probe for the secret.
What's the SLA on webhook delivery from SAM?
SAM aims for < 5 seconds between the change in SAM and the webhook landing at the plugin endpoint. The plugin acknowledges with HTTP 200 within ~50ms of receipt; the catalogue update is visible to shoppers immediately on the same request.
Does this work behind WP Engine or Vercel?
Yes. The webhook endpoint is a standard HTTP POST route. WP Engine's CloudFront and Vercel's edge network both pass it through unchanged. SAM's outbound CloudFront IPs are documented and can be allowlisted at the WAF layer if needed.
What happens if a webhook signature fails verification?
Returns HTTP 401. The payload is not parsed. The event is logged (without the payload contents) so admins can spot misconfigured secrets. SAM retries with exponential backoff so transient mismatches recover automatically.