Σημείωση
Η πρόσβαση σε αυτή τη σελίδα απαιτεί εξουσιοδότηση. Μπορείτε να δοκιμάσετε να συνδεθείτε ή να αλλάξετε καταλόγους.
Η πρόσβαση σε αυτή τη σελίδα απαιτεί εξουσιοδότηση. Μπορείτε να δοκιμάσετε να αλλάξετε καταλόγους.
Note
The Retail Interest Group by Dynamics 365 Commerce has moved from Yammer to Viva Engage. If you don't have access to the new Viva Engage community, fill out this form (https://aka.ms/JoinD365commerceVivaEngageCommunity) to be added and stay engaged in the latest discussions.
This article provides an overview of the architecture of the headless commerce (also known as Commerce Scale Unit). The headless commerce is an API-driven framework that enables extensible, personalized, friction-free commerce experiences, and integrated, optimized back-office operations.
Omnichannel solution provided by the headless commerce
Microsoft Dynamics 365 Commerce (headquarters, in-store, call center, and e-commerce) consumes the commerce APIs of the headless commerce and provides a complete omnichannel solution. Partner applications and Microsoft Power Platform connectors can also consume the APIs.
Components
The headless commerce contains these components:
- Consumer APIs
- Commerce runtime (CRT)
- Channel database
Consumer APIs
The headless commerce exposes Open Data Protocol (OData) APIs for Dynamics 365 Commerce and partner applications to consume. The API layer is built by using ASP.NET Core. It provides different authentication options so that the clients can consume the APIs. The APIs are a wrapper that exposes the business logic. For more information, see the following articles:
Commerce runtime
CRT is a collection of portable .NET libraries that contain the core commerce business logic. The consumer APIs expose the business logic for clients to consume. To add or modify business logic, customize CRT. For more information, see the following articles:
Channel database
The channel database holds transactional data and master data from one or more commerce channels, such as an online store or a brick-and-mortar store. Commerce Data Exchange (CDX) pushes master data from Commerce headquarters to the channel database. CDX pulls transactional data that is stored in the channel database back to Commerce headquarters. For more information, see Channel database extensions.
Headless Commerce Integration
Microsoft provides a set of sample implementations that are tailored to headless and composable commerce scenarios. These samples can help you kick-start and accelerate the development of custom storefronts by using Dynamics 365 Commerce headless engine (commonly referred to as headless commerce). The Headless Commerce Samples GitHub repository includes both technical guidance and hands-on code samples to help you quickly get started.
The samples serve as quick-start templates and reference implementations for partners, software development companies (formerly referred to as independent software vendors or ISVs), and customers. The samples cover core scenarios such as authentication, customer data, product data, pricing, cart, checkout, and order ingestion.
To learn more about each commerce API endpoint, and to read guidance for packaging, deploying, and operating headless commerce solutions, use the resources that are linked in the Components section of this article.