2 results found

1. hotel folio webhook

   It looks like Bills are not supported in your General Webhooks events. It would be useful to have a BillPaid event to hook into after which customer and folio details could be requested!

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Webhooks  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   idea to upvote  ·  AdminSasha Collecutt (Admin, MEWS) responded

2. POS API: Webhook events for order creation and item updates (KDS integration)

   Use Case:
   We're developing a Kitchen Display System (KDS) integration with the MEWS POS API. A KDS needs real-time notifications when:
   - A new order is created
   - Items are added/modified on an existing order
   - Orders are merged

   Current Limitation:
   The available webhook events don't cover order creation or item additions:
   - order.state.updated - Only fires on state changes (e.g., open→paid), not on initial creation
   - order.status.updated - Fires on fulfillment status changes, but not triggered when order is created
   - order.total.updated - Only fires on tip/correction changes
   - order.payments.added - Fires when payment is added (too late for kitchen workflow)

   Testing Results:
   - Created new order → No webhook fired
   - Added items to open order → No webhook fired
   - Merged orders → No webhook fired
   - Paid order → order.state.updated fired (works, but too late for KDS)

   Requested Events:
   - order.created - Fires when a new order is created
   - order.items.added - Fires when items are added to an order
   - order.updated - Fires on any order modification (alternative to granular events)

   Current Workaround:
   Polling GET /v1/orders?filter[createdAtGt]=... every few seconds, which increases API load, adds latency, and counts against rate limits (200 requests per 15 minutes).

   Use Case:
   We're developing a Kitchen Display System (KDS) integration with the MEWS POS API. A KDS needs real-time notifications when:
   - A new order is created
   - Items are added/modified on an existing order
   - Orders are merged

   Current Limitation:
   The available webhook events don't cover order creation or item additions:
   - order.state.updated - Only fires on state changes (e.g., open→paid), not on initial creation
   - order.status.updated - Fires on fulfillment status changes, but not triggered when order is created
   - order.total.updated - Only fires on tip/correction changes
   - order.payments.added - Fires when payment is added (too late for… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   idea to upvote  ·  0 comments  ·  Webhooks  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating