Choose the storefront technology
Call the services from ASP.NET, PHP, Java or a mobile client. The commerce engine does not dictate the presentation tier.
A services layer, a standard .NET stack and extension points that do not require a permanent fork.
The same capability can be a feature, a risk or a time saver depending on who is using it.
Call the services from ASP.NET, PHP, Java or a mobile client. The commerce engine does not dictate the presentation tier.
Services, administration and the scheduler can be distributed across servers as load grows.
Override the behaviour that differs, keep the rest of the core intact and make upgrades a realistic plan.
The .NET client, the ASP.NET MVC sample store and the console reduce the distance from install to a working storefront.
Campaigns, assortments, markets and margins all move at once. The platform should make the connections visible, not hide them in spreadsheets.
Open the role pageOne console for catalogs, orders, prices and content, with the routine tasks brought into the open.
Open the role pageStandards, documentation and tools that are relevant to this topic. They open on the publisher's site.
Each role should name the two tasks that cost the most time today. Those tasks are the real evaluation criteria.