Comments
Preferred solution would be to show the translation based on the user language, if not found - fall back to the company language or other defined language fall back rules, and only at the very end - to the global system language.
For international holdings with companies in different countries it's an absolute must. But there are also countries with several official languages, like Switzerland. User should be able to see a product name in any of those languages if translations are set up.
Example could be to get all prices currently active and used by BC pricing method in place.
Another example could be to get all prices for one price group.
Subscription on the endpoint and odata filtering would be a needed feature as well. (Update external endpoint once a price is updated in BC, or filtering on prices updated since last ddmmyyyy.hhmmss)
Luc made a good suggestion that I make add some justification for this.
I am a pre-sales consultant for Business Central and we often get potential deals where Business Central will not manage the entire business - there is another (best of breed) operational system that fits the industry specific need. Of course they still want an integrated solution.
Business Central has some great integration tools these days, including API's, PowerApps, PowerAutomate etc.. - technically we can sell the dream. And customers are used to doing this as they used to in the on-premise scenario, with concurrent-style licensing.
But the (multiplexing) licensing kills the whole deal - without more licensing options we are losing the client completely, and so is Microsoft.
Metered licensing for API's would be a good solution to this, without getting into more complex modular licensing (I know F&O has an Order Lines SKU - that might work in BC for some scenarios but maybe not others).