Originally Posted by
orbitmic
Fair point but just to note there are two very different things here: setting up systems to recognise status and merely allowing people to enter FFP number. The two are separate, some airlines website enable any ffp to be entered as do many otas (Expedia etc). So you could fly MH enter a *A number - of course it ri but g to give you anything (no likes, no benefits etc) but you can still enter it anyway… that might have been a good first step.
But they aren't very different at all. They are two sides of the same coin.
One the one hand, until this alliance switch, SAS had no reason to set up a system that would allow you to enter in any FFP for any reason. Retaining data isn't free. It would also be a GDPR violation as they don't have a business need for any data not used to provide a frequent flyer program benefit (whether that is elevated status perks or simple milage accrual).
On the other hand, simply having the ability to ebter in information doesn't mean anything if you can do nothing with it. I don't know the inner workings of ST and *A code, but I guess API access to data is involved. That integration has to be coded. And as I said, it is not a like for like match. For example, in ST, it seems like you can do seat selection across multiple airlines as a status holder. You can't do that in *A. Interoperability has to be planned. There may be contractual or other non-technical things at play. I am sure in SAS' minds it makes no sense for them to provide now for which there is no contractual obligation to deliver, especially on other airlines not part of alliance as of today.
If being able to enter in the number is the only concern, then I wouldn't stress. I am sure you'll be able to enter in the number at check-in or even at the gate on day of departure.