Skip to content
All Retail connections

Event connection

Retail webhooks

Give the next system a useful signal.

Give the next system a useful signal.

Use event notifications to support a defined handoff. Retail's webhook settings cover endpoint configuration, event selection and delivery history so your team can review what happened.

  • Select sale-paid, sale-refunded, low-stock or day-closed events.
  • Configure the receiving HTTPS endpoint.
  • Review delivery history and test-event tools.
  • Manage the endpoint's active state and signing-secret rotation.
Explore event connections

Make every event useful to the receiving system.

Choose a defined trigger

Start with the event your workflow needs: a paid sale, refund, low-stock item or closed business day. Describe what should happen in the receiving system. Subscribe only to relevant events so your team can review a focused stream of activity.

Prepare the receiver

Confirm the HTTPS endpoint, payload and signature requirements with your developer. Use the available test-event tools and inspect delivery history before rollout. Agree who owns the endpoint and how they will learn about a failed or delayed delivery.

Expect delivery exceptions

The receiver needs a plan for duplicate, delayed and out-of-order events. Use stable event identifiers when the documented payload provides them, and reconcile against source records when needed. Review retries and secret rotation together; receiving an event should not trigger an unguarded payment or refund.

Building something for Taply stores?

Bring your idea, your expertise and the workflow you want to improve.

Become an integration partner