Naming a Product for Submission to Both the MSFS2020 and MSFS2024 Marketplaces

Hello,

An MSFS2020-native aircraft that is also compatible with MSFS2024 will be submitted to the Marketplace.
There are two projects that build two packages: “company-aircraft-model-2020” and “company-aircraft-model-2024”, one for MSFS2020 and the other for MSFS2024. This is due to the MSFS2024 G3XTouch V2 and other changes required for MSFS2024 compatibility.

If the company-aircraft-model-2020.zip file is submitted to the MSFS2020 Marketplace, and the company-aircraft-model-2024.zip file is submitted to the MSFS2024 Marketplace, will these be recognized as the same product so that a customer who purchases it on either Marketplace (2020 or 2024) will own the aircraft for both simulators?

How do the MSFS2020 and MSFS2024 Marketplace determine that a submission is the same product? Is it based on an ID, a checkbox, the ZIP filename, or the product root package name?
Maybe package named company-aircraft-model.zip should be submitted to both Marketplaces for it to be considered the same MSFS2020-native product?

I understand this is a Marketplace question, but since I do not have a Partner ID to contact a Marketplace representative, I would appreciate if any developers could provide some guidance.

Thanks in advance!

Yiannis

afaik if its compiled with the 2020 sdk it will be listed as such
these use a ‘legacy mode’ of some kind for compatibility

to be native 2024 it needs to be built in that game and with that folder structure i believe

The package name has to be the same to accomplish what you want. Each package has to be build with the corresponding MSFS SDK, also known as native packages.

The 2024 MCP only accepts packages built with the 2024 SDK.

The 2020 package has to be uploaded to the 2020 MCP. There it can be marked as compatible (not native) with 2024.

2020 products appear in the 2024 MCP list, and under that product, a native 2024 built package with the same name can be uploaded. A free or paid upgrade price can be set in the metadata.

@EzRyder @vpilotfs Thanks for your comments guys!