You’re offline. This is a read only version of the page.
Announcements
Hi Community,
The new Store commerce APP officially does not support modifications in Price engine and also does not support localization. But...
Background - we are launching a project with golive in Norway in summer this year... and we need fiscalization and we need custom payment connector. Obviously we would like to start with the new technology...
Any thoughts / ideas?
Cheers
Martin
Hi Ramune,
For your information - we have done a test migration by one existing customer from RetailSDK to Commerce SDK... and our custom-built fiscalization solutions that are based on fiscal framework seem to be working fine... but it is in all cases a communication with a device, not a direct service call. For the pricing we have successfully used a workaround suggested by Microsoft.
Anyway... the urge to "migrate ASAP" to CommerceSDK is postponed to fall 22 earliest. I am not happy that we should start working on the "future deprecated" solution today... and the Norway RetailSDK solution is not even based on the fiscal framework yet... but probably it is the only supported way.
ML
Hi Martin,
"This means that if the customer want to go live this year, they need to keep development in RetailSDK and migrate later?"
Correct.
"Or can they manually import the parts of solution from Retail SDK to Commerce SDK, similar as it is possible for the pricing extensions?"
This is not possible, because there are sealed Commerce localization features for Norway that cannot be enabled with the new extensibility approach.
In addition, we had a similar discussion for Germany some time ago. This problem currently exists for all Commerce localizations provided by Microsoft.
We got an update on the Retail SDK deprecation plans from the core Commerce team. Per the most recent White Paper, deprecation of the Retail SDK will happen in Spring 2023 the earliest (latest supported version is 10.0.32) to give customers at least six months to migrate from the moment we have full parity on the new Commerce SDK.
Moreover, if localization delivery dates slip, so will the deprecation date. This of course applies to Retail deployable package and combined POS, Hardware station, and Cloud Scale unit installers too. The date in the deprecation notice will be fixed.
Hi Ramune,
Thanks for answer.
This means that if we want to go live this year, we need to keep development in RetailSDK and migrate later? Or can we manually import the parts of solution from Retail SDK to Commerce SDK, similar as it is possible for the pricing extensions? We would obviously like to start development with Commerce SDK...
Thanks
ML
Hi Martin,
we have already replicated the sample part of the Commerce localization for Norway to the new Commerce SDK.
However, it is still not possible to use it from the new Commerce SDK, as other parts of the localization still depend on the legacy extensibility approach and do not work with the new independent packaging and extension model.
Thus, you have to use the legacy Retail SDK to be able to implement the Commerce localization for Norway (and any other country).
Any “hybrid” approach is not possible either, such as using the legacy Retail SDK for localizations and the new Commerce SDK for other customizations within one instance (one CSU, one MPOS, or one HWS).
#1
André Arnaud de Cal...
293,435
Super User 2025 Season 1
#2
Martin Dráb
232,567
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (