The Retail statement functionality in D365F&O is the process that puts everything together and makes sure transactions from POS flows into D365F&O HQ.   If you are using shift-based statements, a statement will be calculated when the shift is closed. Using shift-based closing can be tricky, but I highly recommend doing this! After the statement is calculated and there are no issues, the statement will be posted, and an invoiced sales order is created. 1. Manually create a new “blank” batch job 2. Click on “View Tasks”. 3. Add the following 4 classes: Class Name Task Description RetailCDXScheduleRunner Upload channel transaction(P-job) RetailTransactionSalesTransMark_Multi  Post inventory RetailEodStatementCalculateBatchScheduler Calculate statement RetailEodStatementPostBatchScheduler Post statement Here I choose to include upload of transactions, post inventory, calculate statement and post statement into a single batch-job. Click on each task, Under the general tab. Set ignore task failure to YES.  Do this process for all task in the job. And click on the “parameters” to set the parameters on each task, like what organization notes that should be included. Add this parameter to Post inventory, Calculate Statement, Post statement. On each batch task I also add conditions, so that the previous step needs to be completed before the batch-job starts on the next. Provide condition to Post inventory, Calculate Statement, Post statement according to there sequence. Click on recurrence and set the recurrence that when the statement done. The benefit of this is that when you are opening the statements workspace you mostly see statements where there are cash differences, or where the issues on master data. Now you will able to post statement automatically as per set time in recurrence. Hope this helps!

Many customers use Azure Active Directory (Azure AD) to manage user credentials for those services. In those cases, the customers might want to use the same Azure AD account across applications. Before a store worker can use an Azure AD account to sign in to the POS application, the Azure AD account must be associated with that worker. At times you will get an error while sign in POS for employees. Even when you add Associate Existing identity for the worker in HQ. Follow the below steps: Go to Azure portal, Click on Azure active directory. Go to user and select the user Copy the External Sub Identifier. Inside AX HQ, go to Commerce shared parameter Inside Identity Provider, Add azure AD link. Inside relying parties Add user External sub identifier for the same. Inside https://commerce.dynamics.com/auth provide below relying parties. Inside https://commerce.dynamics.com/authcc provide below relying parties. Run 9999 job from Channel database. After full Sync Activate POS again. you will able to sign in successfully. hope this helps!

Using the POS screen layout designer is a tedious work and very likely you would not want to do this in every environment over and over again. For this particular task of moving POS screen layouts, here are the steps to follow: In Data Management, Click on Export. Add following entity list  for POS design and receipt format. POS layout images POS button grid POS button grid buttons POS screen layouts POS screen layout zones POS screen layout button grid zones POS screen layout image zones POS screen layout report zones POS visual profiles Layout sizes RetailTillLayoutConfigurationEntity Receipt format Receipt profile Receipt profile line Export that entity Download package Import POS design and receipt format In Data Management, Click on Import. Click on Add file. Click on Upload and add Select the package file which is export (select in Zip format). Entities will be added. Click on import.  Run 1070, 1090 job and refresh the browser link. Hope this helps!

If you’re using a Tier-2 sandbox or production environment that has application version 8.1.2.x or later, you must initialize Commerce Scale Unit before you can use retail channel functionality for point of sale (POS) operations that use Retail Server in the cloud. Initialization will deploy a Commerce Scale Unit (cloud). Prerequisites: Deploy a Tier-2 sandbox or production environment that has application version 8.1.2.x or later. Initialize Commerce Scale Unit as part of a new environment deployment Make sure the headquarters environment is available and not in Maintenance mode. Steps: In LCS, on the environment details page, Click on Manage. Click on initialize Select your region And initialize. Inside HQ, go to channel Database new channel DB created. Add channels inside that new Channel DB. Go to channel, click on channel profile and select that new channel DB. Run 9999 jobs from channel Database. I hope this helps!

At times you will get an error while creating positions for employees such as this: The assignment end date must not be earlier than the assignment start date Here even if you put an Assignment end date you wont be able to create a position because the actual error is on the below form. Once you make changes to it and add date to available for assignment field, you will be able to create a position successfully Hope this helps !

There are two types of POS, or point of sale, applications in Microsoft Dynamics 365 Retail. MPOS and CPOS. Modern POS is basically an App that you can install on your computer and Cloud POS is a browser based version of POS. Those familiar with such POS must have faced issues while activating POS. Considering you have done the configuration and setup properly POS should activate. However you may get to see error such as “the azure active directory user token cannot be found“ To fix this issue you need to make sure IIS is activated on your system. If not please go to control panel and activate it. Once it is active, please make sure Anonymous Authentication is enabled in IIS as you can see in the below screen shot. Hope this helps!

Warranty feature in Dynamics 365 Retail can be used to either provide standard product warranty at zero price and also to sell extended warranty at a specific price. Warranties can be sold in the retail channel during the initial purchase or for a limited time afterward. For a retailer, providing an warranty can help build customer loyalty. With the extended warranty purchase, customers know where to go for service and support in case of issues and they can gain the confidence that their issues will be handled well. You can find the Extended warranty configuration and setup in the official Microsoft document on this link https://docs.microsoft.com/en-us/dynamics365/commerce/extended-warranty However if you want to offer standard product to customers at no additional cost, you need to do below setup: 1. In Released product for warranty product, Scroll down to Commerce fast tab and set the radio button Zero price valid to yes 2. Next, go to Functionality profile and set the radio button Must key in price if zero to no Run the relevant jobs and you should be able to sell the warranty or any product at zero price on POS. Warranty transactions related data is stored in database table called WARRANTYPOLICY. The data will reflect in the table only after statement posting and running the process warranty transaction job Hope this helps!

This topic describes a configuration option that is available for the point of sale (POS) application. This configuration option changes the behaviour     for the selection of a mode of delivery when shipment orders are created in POS. When users create customer shipment orders in POS, they can select a mode of delivery for the shipment. This functionality is available regardless of whether the whole order is being shipped or only selected lines. By default, the dialog box where a mode of delivery is selected shows all the valid modes of delivery for the combination of a channel, an item, and a delivery address. These modes of delivery are defined on the Modes of delivery page in Headquarters (Sales and marketing > Setup > Distribution > Modes of delivery). “Non-carrier” modes of delivery, such as Carryout or Pickup, might also appear for selection in the dialog box. However, a feature has been added that lets you hide non-carrier modes of delivery in the dialog box. To turn on this feature, on the Commerce parameters > Customer orders tab, set the Show only carrier mode options for ship orders option to Yes. After you turn on this feature and run the appropriate distribution jobs to sync the information to the channel database, non-carrier modes of delivery won’t appear for selection during the process of creating shipment orders in POS. Hope This helps. Thankyou!

Many retailers, especially high-end specialty retailers, want their sales associates to form long-term relationships with their key customers. The associates are expected to know about these customers’ likes and dislikes, purchase history, product preferences, and important dates, such as anniversaries and birthdays. Associates need a place where they can capture this information and easily find it when it’s required. If this information is available in a single view, the associates can easily target customers who meet specific criteria. For example, they can find all customers who prefer to shop for handbags, or customers who have an important event approaching, such as a birthday or anniversary. Or if a customer had bought a gift for her husband then the cashier/associate can ask the customer if her husband liked the gift. In a nutshell, this will allow the stores to create a relationship with customers on a personal level. This is bound to make customers happy as they will begin to think that they matter and they are being looked after. Such practice will directly impact the sales Here is how you can set up Clienteling in d365 Retail  In the Feature management turn on the clienteling functionality in your environment Turn on the Clienteling feature by selecting Enable now. On the Commerce Parameters page, on the Number sequence tab, select the Client book identifier row. Then, in the Number sequence code field, select a number sequence. The system will use this number sequence to assign an ID to client books. Create a new attribute group that contains the attributes that you want to capture for customers who are managed in client books. Define the required attributes as Can be refined. Sales associates can then use these attributes to filter their client book. On the Commerce parameters page, on the Clienteling tab, in the Client book attribute group field, select the attribute group that you just created. To capture activities that occur at the POS, define the activity types on the Activity types page (Retail and Commerce > Customers > Activity types). Add two buttons to the appropriate POS screen layout, so that sales associates can view their own client book and the store client book. (Store client books include clients from all client books of all associates who share an address book with the store.) The corresponding operations are named View customers in client book and View customers from store client books, respectively. Three additional operations that are related to client books are available. These operations determine which associates can add, remove, and reassign customers from the client book. They are named Add customer to client book, Remove customers from client book, and Reassign customers to a client book, respectively. Run the following distribution schedule jobs: 1040, 1150, 1110, and 1090. After you’ve completed this procedure, sales associates can open the customer details page at the POS, and add customers to their client book, view and capture activities and notes for customers, and target customers by using customer and client book attributes to filter the client book. Hope this helps!

Some Retailers may want to encourage customers to pay via cash in their Retail stores. This can be made possible by offering discounts to customers if they pay by a Cash mode of payment. In this way, they can help reduce the expense of credit card processing fees. Therefore, retailers might provide discounts to customers who use these alternative tender types. In Dynamics 365 Commerce (Retail) a new type of discount has been introduced which is called as tender based discount. In tender based discounts, as a Retailer you are able to give different discounts based on the payment medium the customer has chosen to pay. Even though tender-based discounts reduce the subtotal of the transaction, automatic charges that are applied to the transaction aren’t affected. For example, if the delivery charges are calculated as $5 because the subtotal was more than $100, and the tender-based discount reduces the amount so that it’s less than $100, the delivery charges are still $5 for the order. In the system you can go to Retail>Pricing and discounts >Tender discount. Here you can set up the parameter as required, add price groups and then run necessary jobs to apply it in Retail POS. In the below example the payment type selected is Cash. You can select any type of method as per your need.