Upselling – Info codes configuration recap

Upselling is one of the common requirements in Retail POS. In this post I would like to recap how this can be achieved using configuration and no code in Dynamics 365 for Operations using info codes.

Info codes is quite an old feature and I thought it would be good to recap how we can use it to achieve “Upselling”.

Lets say we want the cashier to remember to try to upsell a product B on purchase of a certain product A (association rules)- example to prompt cashier to ask customer if he or she would like to buy batteries with purchase of camera.

The first step would be to create an infocode that will show a prompt to the cashier in the Retail POS. Infocodes can be created in Dynamics 365 in the following path- Retail and Commerce-> Channel setup -> Info codes

The input type of the info code can be setup as subcode buttons.

The subcodes need to be setup as follows. Note the use of Trigger function and Trigger code in the setup.

The above setup means that on selecting Yes, the customer agrees to buy the product we are trying to upsell (batteries) and the product will be added to the transaction.

The next part of the setup involves linking this info code to the product the cashier sells in the first place to the customer (Camera). This can be done in the released products master under Commerce tab-> Set up-> Info codes.

With the above setup in backoffice and pushed to the POS (by running the 1030 job and 1040 job), the cashier will get a prompt as shown below

On clicking Yes, the upsell will be done by adding the Batteries product to the transaction.

Regards

Hitesh Manglani

The service is not provisioned for the same tenant

If you have downloaded an Dynamics 365 for Operations / AX7 VM for Development especially for Retail do have a look at this article

https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/dev-tools/access-instances

Unless you do the steps mentioned in the Retail Configuration section in this link you will get errors like :

In MPOS trying to activate would give an error – The service is not provisioned for the same tenant. User is hitting a retail server that does not belong to the same tenant as the Activation account.

Also if you try to Associate User Identity with a worker in AX it will result in an error like the service is not reachable.

Note – You need to install KB3170424 if you are facing this issue in a LCS hosted VM.

 

-Hitesh Manglani