Changing Service Loads with a seat map enabled

In GO7 PSS, the change of Service Load (SL) may be enabled or disabled in the flight series. If it is disabled (normally a default setting), then service load can only be updated via seat control flight by flight, and the option to change SL is not available for mass update in the Flight series.

If it is enabled, then service load can be updated both flight by flight in Seat control or in Flight series via mass update. 
The setting above can only be updated by the GO7 Support team upon the airline's request (not directly by the airline). Once enabled, it takes immediate effect (meaning literally from the next second) for all flight series and routes in the system, with no possibility to enable it only for some routes or flight series. It can also be changed to the opposite direction at any time later (again with immediate effect).
Below we provide the description of the consequences, associated with both choices.
1.Verification of seats enabled on Service Load change (SL change in Flight series not possible):

When you change a service load in Seat control, the system verifies seats assigned to each passenger to check if such seats exist and are available on a new SL seat map. If all seats are available on the new seat map, the change is successful (and seats are accordingly assigned and reflected on the seat map of the new SL). If, however, at least one seat cannot be accommodated, the SL update will fail, and the logs with errors will be provided.
When an error on service load change is received, the airline should manually:

  • Print the manifest with seats indicated.
  • Cancel a seat service in each PNR as indicated in the log.
  • Update the service load.
  • Open all affected PNRs and reassign a new seat on a new seat map as close to the original choice as possible.
  • Change the seat fee to match the original canceled seat service amount and re-issue tickets.

Verification of seats disabled on Service Load change (SL change in Flight series possible):
There will be no verification enabled, so the SL will be changed, ignoring potential seating issues. Seats will remain assigned in the PNRs but will not be assigned/reflected on a new seat map (and so will not block the same seats from being booked again). Hence the airline should:

  • Open the seat simulator in the seat control and one by one block all seats in the new flight seat map in accordance with all seats booked by the passengers on the previous seat map.
  • If some of the seats assigned to passengers do not exist on a new seat map, the airline should open a PNR, cancel a seat, book a new seat, and remove the price difference manually.

In case the airline prefers to switch to the alternative 2, it should be acknowledged that the following consequences are understood:

  1. Seats assigned to passengers in the old seat map may exist (or may not) on a new seat map.
  2. If a seat does not exist, then such a seat assigned to a passenger may be assigned to another passenger on the same flight as well, as the seat is not relinked to a new seat map and, hence, does not prevent it from being selected again.
  3. Both passengers' seats, as above, would be sent to DCS in PNL.



Have more questions? Submit a request


Powered by Zendesk