Skip to main content

Using the yayloh Rejection Event in Third-Party Integrations

Using the Yayloh Rejection Event for Automations (e.g., Return Notifications)

Vineeta Pendse avatar
Written by Vineeta Pendse
Updated this week

Starting 2025-11-19, yayloh sends a Rejection Event whenever a merchant rejects an item directly in a return request. This event can be consumed by any third-party integration connected to yayloh events including Klaviyo, Rule.io, Voyado, ERPs, BI tools, or custom automation systems.

This enables brands to automate notifications, workflows, analysis, or downstream logic when a request has been denied.


What is the Rejection Event ?

The Rejection Event is triggered when an item inside a return request is manually rejected by a merchant. It communicates that the request (or an item within it) has been denied and closed, without triggering refunds or native notifications.

Any system subscribing to yayloh events can use it to:

  • Send emails/SMS

  • Trigger workflows

  • Update customer profiles

  • Sync rejection data to ERPs

  • Feed BI dashboards or analytics pipelines


When is the event triggered?

The event is pushed to your integrations only when the following workflow is completed in yayloh:

  1. Open the return request

  2. In the action dropdown for the item, select "Reject"

  3. Click "Confirm"

  4. Finalize the action by clicking "Apply"

After clicking Apply:

  • The request is closed

  • No refund or notification is sent from yayloh or Shopify

  • A Rejection Event is emitted to all downstream integrations connected to yayloh events

For detailed technical documentation, read here.


Example Use Cases

Here are common scenarios in which merchants can use the Rejection Event in returns, exchanges, or claims workflows.

  1. Automate customer notifications (e.g., return rejection, claim denied, exchange not eligible)

  2. Feed BI/analytics tools with rejection data (e.g., reasons, product trends, customer segments)

  3. Trigger internal automation (e.g., tickets, CS alerts, manual review flags)


When the Event Does Not Trigger?

The Rejection Event does NOT trigger when a merchant rejects the placement of a new order in:

  • Exchange flows

  • Claim flows with replacement orders

This is not the same as item-level rejection and does not emit an event.

Summary of behavior:

Merchant Action

Generates Rejection Event?

Rejecting an item inside the return request (via dropdown)

✅ Yes

Rejecting a new order creation (for exchange/claim)

❌ No

Did this answer your question?