Welcome back! In this second part of our journey into the latest updates for Dynamics 365 Commerce, we’ll dive into more new features that enhance flexibility, efficiency, and user experience.
Android Hardware Extensions
Let’s start by exploring the recent extension support for Android hardware stations. With the release of Dynamics 365 Commerce version 10.0.41, the Store Commerce app for Android now supports hardware station extensibility.
This new capability enables customers and partners to develop extensions tailored to their specific hardware requirements, similar to what’s available in the Store Commerce app for other hardware stations. This feature also allows organizations to use Android mobile devices as fiscal registers, adding versatility to their in-store operations.
To implement this feature, customers need to download the latest Store Commerce for Android package from Lifecycle Services (LCS). Once the solution is built and packaged, the APK file can be sideloaded onto devices or distributed through Presto.
Multi Selection of HWS (Printer/Cashdrawer)
Next, let’s take a look at the new multi-selection feature for hardware stations. This functionality allows store associates to select from shared hardware stations, such as printers, when printing receipts. Previously, Microsoft Dynamics POS only allowed up to two printers to be configured in the hardware profile. With this update, the Store Commerce app can now be set up to allow associates to select any network printer available on the list.
Once this feature is configured, store associates are prompted with a hardware station selection screen whenever they attempt to print a receipt. They can then choose the closest hardware station to their current location, making receipt printing more flexible and convenient.
This feature is particularly useful for associates using mobile POS devices. For instance, if an associate is on the first floor of a store and needs to print a receipt, they can select a nearby printer. If they move to a different location within the store, they can simply choose the closest printer from the new location, streamlining operations and improving efficiency.
Tap to Pay
With the latest updates, Tap to Pay on iPhone can now be enabled in the Store Commerce app on iPhones, as long as the payment connector is configured. This feature allows store associates to accept in-person payments directly on their iPhones, eliminating the need for dedicated hardware payment terminals.
By enabling this functionality, businesses can reduce costs and maintenance associated with traditional payment terminals, making it a highly efficient solution for retailers.
Adyen Tap to Pay on iPhone
With Adyen’s Tap to Pay on iPhone feature, store associates can accept NFC-enabled card payments directly on an iPhone, eliminating the need for a separate terminal. This feature also allows for a fallback setup if a dedicated terminal is still needed for specific payment methods.
The functionality is versatile—customers can simply tap their digital wallets or NFC-enabled credit cards to the store associate’s iPhone to complete the payment. This streamlined process enhances customer convenience and speeds up in-store transactions.
Key Limitations
While Tap to Pay on iPhone offers numerous benefits, there are some limitations to be aware of:
- Customer Orders: When handling customer orders, Tap to Pay cannot authorize a partial payment for the remaining balance. In these scenarios, there are a few options:
- Take a full authorization amount at the time of purchase.
- Select the option to pay the remaining balance later.
- Alternatively, connect the iPhone to another hardware session with a dedicated payment terminal to authorize the remaining balance if the above options are not feasible.
Inventory Visibility for Commerce
In its current setup, Dynamics 365 Commerce provides channel-side inventory calculation, accurately tracking inventory at each channel level. However, when multiple data sources are involved in updating inventory, it traditionally relies on scheduled batch jobs to synchronize data between the back office and the channel side.
This approach can present challenges, particularly if real-time inventory snapshots are required. The delay from batch updates can be problematic in scenarios involving multiple CSV files or diverse data sources that need immediate inventory updates.
To address this, Dynamics 365 Commerce now uses the Inventory Visibility Service from Dynamics 365 Supply Chain Management as a foundation for real-time inventory updates. This service ensures that accurate inventory snapshots are available across all channel-side activities, providing more timely and reliable data for decision-making.
Key Use Cases for Inventory Visibility Service
This service is especially beneficial in scenarios such as:
- Dual Use of Dynamics 365 Commerce and Supply Chain Management: When both systems are in use, the Inventory Visibility Service ensures seamless and synchronized inventory updates across platforms.
- Multi-Channel Retail Operations: Ideal for POS or e-commerce businesses operating across multiple channels, ensuring accurate inventory views across locations and platforms.
- Integration with Third-Party Systems: For businesses that integrate with third-party systems that also update inventory, the Inventory Visibility Service helps maintain accurate, real-time inventory records across all systems.
Enable POS Self-Checkout
The Self-Checkout feature in Dynamics 365 Commerce allows shoppers to independently scan products, apply discounts or loyalty rewards, and make card payments—no cashier assistance required. This feature delivers a streamlined shopping experience, eliminating the need for a traditional cashier interaction.
Currently, the self-checkout feature is in preview as of version 10.0.40 and is expected to be fully released by the end of 2024.
Configuration and Setup
To enable self-checkout, you’ll need to configure a specific point of sale (POS) terminal to operate in self-checkout mode. During setup, mark the POS register as self-checkout in the configuration settings. Additionally, make sure to synchronize the required jobs, just as you would for a standard POS activation, ensuring a smooth and consistent activation process.
Out-of-the-Box Features
The POS self-checkout mode includes several built-in features designed for ease of use and operational efficiency:
- Simplified Login and Self-Checkout Layout: A streamlined interface tailored for self-service.
- Intuitive User Interface: Designed for easy navigation, enhancing the shopper’s experience.
- Call for Assistance: Allows customers to request help if needed.
- Product Browse Operation: Provides easy product browsing for users.
- Product Restrictions: Ability to restrict certain products from self-checkout.
- Offline Support: Operates even when offline, ensuring uninterrupted service.
- Peripheral Support: Compatible with scanners, payment terminals, and printers.
- Adyen Payment Integration: Adyen is supported out-of-the-box for secure and seamless payments.
With this self-checkout feature, retailers can offer an efficient, customer-driven shopping experience, providing flexibility and reducing wait times at checkout.
Archive Commerce Transactions
Before diving into the details of the archival process, it’s important to recap the significance of data archival and long-term retention (LTR) for Dynamics 365 Commerce.
Importance of Data Archival and LTR
Many partners may already be familiar with the archival capabilities introduced in Finance and Operations earlier this year. Despite regular data cleanup efforts in Finance and Operations, certain types of data, such as historical transactions or critical business records, may remain in the system. These records may not be suitable for deletion but still contribute to database size and require proper management.
Data archival addresses these needs in several ways:
- Database Size Management: Archiving helps manage database size, a crucial factor for controlling costs and ensuring smooth database transfers between environments.
- Audit and Compliance: By defining a retention policy in the AX database, businesses can determine how long data should remain in active storage before transitioning to long-term retention.
System Optimization: Combining regular cleanup with data archival optimizes database storage and health, improving indexing, data transfers, and overall system performance.
Archive Framework – Data Flow
Now, let’s take a high-level look at the data flow architecture within the archive framework.
- Left Side: Finance and Operations (F&O) Database
- Right Side: Dataverse Managed Data Lake
The archiving process begins with defining a retention policy. For example, if you have five years of sales data but only need two years in your live F&O database, the remaining three years can be archived.
Here’s how the archival process flows:
- Define Retention Policy: Determine the duration for which data should remain in the active F&O database (e.g., retain two years and archive the remaining three).
- Initial Sync: When implementing the archival solution, all five years of data are initially synced from the F&O AX Database to the Microsoft-managed data lake.
- Archiving Data: During the sync, the three years of data designated for archival are moved from the live F&O table to the F&O history table within the same database. The live and history tables both reside within the F&O database.
- End Result:
- Active Data: Two years of active data remain in the F&O live table.
- Archived Data: Three years of archived data are stored in the F&O history table.
- Dataverse Managed Data Lake: All five years of data are stored here, with three years marked as archived.
This structured approach ensures that active data remains readily accessible while archived data is securely stored and managed, contributing to an efficient and scalable data management strategy.