# Request for Order Cancellation Webhook Setup for Carrier Integration

**URL:** <https://community.shiphero.com/t/request-for-order-cancellation-webhook-setup-for-carrier-integration/3536>\
**Category:** Getting Started\
**Created:** [August 22, 2025, 9:12pm UTC](https://community.shiphero.com/t/request-for-order-cancellation-webhook-setup-for-carrier-integration/3536 "2025-08-22T21:12:34Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![lramos](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lramos](https://community.shiphero.com/u/lramos)\
**Post date:** [August 22, 2025, 9:12pm UTC](https://community.shiphero.com/t/request-for-order-cancellation-webhook-setup-for-carrier-integration/3536/1 "2025-08-22T21:12:34Z")

</div>

As a carrier, we’re currently integrated through the **Generate Label Webhook**. While that webhook works as expected for label creation, we’ve noticed that when a client cancels or voids an order in ShipHero, we don’t receive any update. As a result, those orders remain stale in our system.

We’d like to properly receive **order cancellation (or voided order/label)** updates so our system can stay in sync with ShipHero. Could you please guide us through the correct process for enabling and registering the necessary webhook(s) for cancellations?

If there are any additional event webhooks or best practices you recommend carriers implement (beyond Generate Label) to keep our systems aligned, we’d appreciate your guidance.

---

<div class="post-metadata">

**Author:** ![lramos](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lramos](https://community.shiphero.com/u/lramos)\
**Post date:** [August 27, 2025, 3:59pm UTC](https://community.shiphero.com/t/request-for-order-cancellation-webhook-setup-for-carrier-integration/3536/2 "2025-08-27T15:59:49Z")

</div>

Appreciating any and all assistance.

---

<div class="post-metadata">

**Author:** ![sh-agent2](https://avatars.discourse-cdn.com/v4/letter/s/9f8e36/32.png) [@sh-agent2](https://community.shiphero.com/u/sh-agent2)\
**Post date:** [August 27, 2025, 4:02pm UTC](https://community.shiphero.com/t/request-for-order-cancellation-webhook-setup-for-carrier-integration/3536/3 "2025-08-27T16:02:10Z")

</div>

Hey Iramos, The order update webhook will get all order updates including cancellations. YOu can watch that and filter for status “cancelled” Which should solve your issue

---

<div class="post-metadata">

**Author:** ![lramos](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lramos](https://community.shiphero.com/u/lramos)\
**Post date:** [August 27, 2025, 6:23pm UTC](https://community.shiphero.com/t/request-for-order-cancellation-webhook-setup-for-carrier-integration/3536/4 "2025-08-27T18:23:42Z")

</div>

Hi Austin,

Thanks for clarifying. Could you clarify which field you’re referring to when you mention “status”. My assumption is “fulfillment\_status”, but we’ve seen that field contain a mix of value (e.g., “pending”, merchant names, etc.), which makes it unreliable.

Could you share the full set of possible status values and their definitions so we can handle them correctly on our side?

Thanks

---

<div class="post-metadata">

**Author:** ![lramos](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lramos](https://community.shiphero.com/u/lramos)\
**Post date:** [August 28, 2025, 6:19pm UTC](https://community.shiphero.com/t/request-for-order-cancellation-webhook-setup-for-carrier-integration/3536/5 "2025-08-28T18:19:08Z")

</div>

Appreciating further guidance on this.

---

<div class="post-metadata">

**Author:** ![lramos](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lramos](https://community.shiphero.com/u/lramos)\
**Post date:** [September 2, 2025, 5:33pm UTC](https://community.shiphero.com/t/request-for-order-cancellation-webhook-setup-for-carrier-integration/3536/6 "2025-09-02T17:33:57Z")

</div>

hi @sh-agent2, following up on my question:

Thanks for clarifying. Could you clarify which field you’re referring to when you mention “status”. My assumption is “fulfillment\_status”, but we’ve seen that field contain a mix of value (e.g., “pending”, merchant names, etc.), which makes it unreliable.

Could you share the full set of possible status values and their definitions so we can handle them correctly on our side?