Skip to main content
Solved

Mews Lunch Product

  • April 27, 2026
  • 1 reply
  • 67 views
W

Hello,

I have a simple issue with meal management in Mews.

Context:

  • Contract of rooms of 50 rooms per days
  • need lunch charge for every night but not on check-in or check-out
  • Supper are working fine with “before end of day” since they are always taken at check-in

Problem with lunch:

Guests check out before lunch time, so lunch should not be charged.

However, with product type:

  • If I set it to “before end of day”, lunch gets charged on arrival
  • If I set it to “after end of day”, lunch gets charged at check-out

In both cases, the meal is charged even though it should not be at check-out or check-in.

I am looking for a simple way to avoid automatically charging lunch for check-in or check-out while keeping as much automation as possible.

How are you handling this in Mews?

Thank you.

Best answer by josue.orellana

Hello ​@Warh1,

I’m Josue - one of the Community Ambassadors - and I’m happy to help clarify your question regarding the Lunch product. 

From what you described, this looks like a limitation of the current product timing options: before end of day catches the arrival day, while after end of day catches the departure day.

If the goal is to charge lunch only for the nights in between, there usually isn’t a fully automatic setup for that exact logic. The most practical workaround is to use the option that creates the fewest exceptions for your operation, and then manually remove or adjust the lunch charge on the check-in / check-out edge cases.

If you want to keep as much automation as possible, I’d suggest:

  • choosing the timing that best fits when lunch is usually consumed,
  • testing it on a few sample stays with different lengths,
  • and handling the first/last day exceptions manually where needed.

So in short: what you’re seeing is expected based on the timing setup, but excluding both check-in and check-out at the same time will likely require some manual handling.

Hopefully others in the community can also share how they’ve chosen to manage this operationally.

If you have any questions, please don’t hesitate to let me know! 😎

~ Best regards, 

    1 Reply

    josue.orellana
    Community Ambassador
    Forum|alt.badge.img+1
    • josue.orellanaCommunity Ambassador
    • Community Ambassador
    • Answer
    • May 7, 2026

    Hello ​@Warh1,

    I’m Josue - one of the Community Ambassadors - and I’m happy to help clarify your question regarding the Lunch product. 

    From what you described, this looks like a limitation of the current product timing options: before end of day catches the arrival day, while after end of day catches the departure day.

    If the goal is to charge lunch only for the nights in between, there usually isn’t a fully automatic setup for that exact logic. The most practical workaround is to use the option that creates the fewest exceptions for your operation, and then manually remove or adjust the lunch charge on the check-in / check-out edge cases.

    If you want to keep as much automation as possible, I’d suggest:

    • choosing the timing that best fits when lunch is usually consumed,
    • testing it on a few sample stays with different lengths,
    • and handling the first/last day exceptions manually where needed.

    So in short: what you’re seeing is expected based on the timing setup, but excluding both check-in and check-out at the same time will likely require some manual handling.

    Hopefully others in the community can also share how they’ve chosen to manage this operationally.

    If you have any questions, please don’t hesitate to let me know! 😎

    ~ Best regards, 

    josue.orellana
      Terms and ConditionsAccessibility statement