Frequently asked questions for Dynamics 365 Commerce
Both; and considerably more.
Dynamics 365 Commerce is an omnichannel commerce platform that supports physical retail, digital commerce, and call-centre sales. It includes Store Commerce POS, e-commerce capabilities, pricing and promotions, customer and loyalty management, merchandising, inventory visibility, and order processes across channels.
Commerce and Supply Chain Management are closely connected, particularly where retail operations depend on inventory, procurement, warehousing, planning, and fulfilment.
The right architecture depends on your wider Dynamics 365 environment and operational requirements. We would scope those dependencies as part of the solution design rather than treating the storefront or POS in isolation.
Dynamics 365 Commerce includes its own digital commerce capabilities, but it also uses a headless commerce architecture. Depending on your existing website, technology stack, and requirements, there may be options to retain or integrate parts of the current digital experience rather than replacing everything.
Dynamics 365 Store Commerce supports offline operation, allowing appropriate store processes to continue when connectivity is temporarily unavailable.
Exactly what remains available depends on the configuration and the operation being performed, so offline requirements should form part of the store design and testing process.
Yes. Dynamics 365 Commerce is designed around omnichannel retail scenarios, including customer orders, pickup and fulfilment workflows, and returns across connected channels. Store Commerce supports workflows covering in-store, online, and curbside pickup scenarios.
The specific processes still need to be designed around your policies, inventory model, stores, and fulfilment network.
A single-region retail operation with straightforward POS requirements is very different from a multi-brand, multi-country environment spanning stores, e-commerce, warehouses, loyalty, integrations, and complex fulfilment.
We scope the channels, stores, products, data, integrations, operating processes, and rollout approach first, then build an implementation plan around the actual complexity.