Skip to content

Reference

Meal plans

A meal plan is an attribute of a rate plan, never a switch on top of one. One rate plan per board basis, with the meal inside its rate, matched to the OTA rate that carries the same meal. This page is the whole model and the three places it touches the API.

The model

Every channel manager and every OTA works the same way: the meal belongs to the rate. Booking.com keeps a meal plan on each room-rate, Agoda ticks breakfast, lunch or dinner on the rate plan, MakeMyTrip and Goibibo name their rates EP, CP, MAP and AP, Hostelworld sells a separate bed-and-breakfast rate. A hotel that sells room-only and breakfast has two rates on the OTA and two rate plans here, and the channel mapping pairs each OTA rate with the plan of the same meal.

One plan per meal
“Deluxe · Breakfast” and “Deluxe · Room only” are two rate plans. Add a plan per guest count or per refundability only where the hotel prices those apart; a 2-meal × 3-occupancy grid is normal, MakeMyTrip sells it that way.
The meal is in the rate
The breakfast plan’s nightly rate already includes breakfast. There is no meal field on a rate write and no per-person supplement in the API; your PMS prices each plan and sends the number.
The OTA holds its own copy
The channel manager carries the meal as a label on its plan and sends it to no OTA. The hotel sets the meal on the OTA’s rate in that OTA’s extranet; nothing you send here changes it.
One meal per plan, everywhere
A plan sells with the same meal on every channel. To sell breakfast on one OTA and room-only on another, make two plans and map each.

The four codes

  • EPRoom onlychannel manager none
    European plan · OpenTravel 14 Room only
  • CPBreakfastchannel manager breakfast
    Continental plan · OpenTravel 3 Bed & breakfast
  • MAPHalf boardchannel manager half_board
    Modified American plan · OpenTravel 12 Half board
  • APFull boardchannel manager full_board
    American plan · OpenTravel 10 Full board

Where it touches the API

  1. 1

    Create the plans, one per meal

    PUT /catalog/rate-plans (scope catalog:write) takes mealPlan on every plan, with your own ref as the upsert key. Put the meal in the name as well: the owner and the OTA mapping screen read names.
    PUT /catalog/rate-plans
    {
      "ratePlans": [
        {
          "ref": "dlx-ro",
          "roomTypeRef": "deluxe",
          "name": "Deluxe · Room only",
          "mealPlan": "EP",
          "occupancy": 2,
          "refundable": true,
          "defaultRate": "4000.00"
        },
        {
          "ref": "dlx-bb",
          "roomTypeRef": "deluxe",
          "name": "Deluxe · Breakfast",
          "mealPlan": "CP",
          "occupancy": 2,
          "refundable": true,
          "defaultRate": "4600.00"
        },
        {
          "ref": "dlx-hb",
          "roomTypeRef": "deluxe",
          "name": "Deluxe · Half board",
          "mealPlan": "MAP",
          "occupancy": 2,
          "refundable": true,
          "defaultRate": "5400.00"
        }
      ]
    }
  2. 2

    Price each plan on each date

    PUT /rates writes one price per plan per date; the plan fixes the meal. A breakfast plan priced as the room-only plan plus a fixed amount is your PMS's arithmetic, sent as its result. The same holds for restrictions.
    PUT /rates
    {
      "rates": [
        {
          "ratePlanId": 901,
          "from": "2026-12-20",
          "to": "2026-12-31",
          "rate": "4000.00"
        },
        {
          "ratePlanId": 902,
          "from": "2026-12-20",
          "to": "2026-12-31",
          "rate": "4600.00"
        },
        {
          "ratePlanId": 903,
          "from": "2026-12-20",
          "to": "2026-12-31",
          "rate": "5400.00"
        }
      ]
    }
  3. 3

    Match the OTA rate that carries the same meal

    In each OTA's extranet the hotel creates one rate per meal with the meal set there. On the Channels app's mapping board, each OTA rate is paired with the plan of the same meal (the board suggests pairs by room, meal, guests and refundability). An OTA rate for a meal the hotel has no plan for stays unmatched until the plan exists.
  4. 4

    Read the meal on every booking

    Every booking webhook and GET /channel-bookings room carries ratePlanId (null when the OTA rate is not mapped) and mealPlan, which is what the OTA says the guest bought: Booking.com's meal text on the room, Agoda's rate benefits (breakfast, lunch, dinner), MakeMyTrip's and Goibibo's rate name, Hostelworld's breakfast flag. Expedia and Airbnb send no meal with a booking (Expedia keeps it on the rate plan in its extranet; Airbnb has no meal plans), so for them it is the mapped plan's own meal plan, then EP. A hotel that maps its room-only and its breakfast OTA rates onto one plan therefore still gets the right meal on each booking; ratePlanId tells you the plan it was priced through. A booking you create with POST /bookings takes its meal from the ratePlanId you name (none: room only), and its nightly rate is read as including that meal, so no meal extra is ever added to it at the desk.

What not to do

  • Do not model a meal as a flag you flip per date on one plan; make the second plan.
  • Do not send a meal with a rate or a booking; neither accepts one, and the plan already says it.
  • Do not expect the channel manager to set the meal on the OTA; set it in the extranet, then map.
  • Do not add a breakfast line to a booking that came on a breakfast plan; its rate includes it.