Using Cloud POS as your retail mobile device

Handheld functionality for retailers is a question I get a lot. Then typical in the area of counting, replenishment, receive and daily POS operations. In version 8.1 Microsoft have taken a small step forward to make it easier to use any handheld device that supports a common browser. Because Cloud POS (CPOS) runs in a browser, the application isn’t installed on the device. Instead, the browser accesses the application code from the CPOS server. CPOS can’t directly access POS hardware or work in an offline state.

What Microsoft have done is to make the CPOS change according to the screen size, to work more effectively on your device. To make it simple, I just want to show you how it looks on my iPhone.

Step 1: Direct your browser towards the URL of where the CPOS is located. In LCS you will find the URL here:

Step 2: Activate your POS on mobile device by selecting store and register, and log in

Step 3: Log into CPOS and start using it. Here are some sample screens from my iPhone, where I count an item using CPOS.

You can also “simulate” this in your PC browser, but just reducing the size of your browser window before you log into CPOS. Here I’m showing the inventory lookup in CPOS.

What I would love to see more of is:

– Barcode scanning support using camera

– The ability to create replenishment/purchase orders in CPOS

– More receive capabilities like ASN/Pallet receive etc.

– Improved browser functionality (like back-forward browsing etc)

To me it seems clear that we will see additional improvements in CPOS, making it the preferred mobile platform for Dynamics 365 for Retail. As we get a little, I hope to see more of this as Microsoft is definitely investing in this area. In our own customer projects we will be developing more and more functionality using RTS (Real Time Service calls) to add more features to be used together with CPOS.

To take this to the next level, please also check evaluate to create a hybrid app, that incorporate CPOS in a app friendly way. Sources say that this will also allow us to build extensions like camera barcode scanning

The direction is right and my prediction for the future is that: Mobile Retail device = CPOS.

Dynamics AX 2012: At your service!

Dynamics AX Service management can be used for service agreements and service subscriptions, handle service orders and customer inquiries, and to manage and analyze the delivery of services to customers. You can use service agreements to define the resources that are used in a typical service visit. You can also use service agreements to view how those resources are invoiced to the customer. A service agreement can also include a service level agreement that specifies standard response times, and offers tools to record the actual time.

What I wanted was to see how much we could simplify the registration of needed repair materials and service hours.

The Dynamics AX service orders is tightly integrated to the project module, and sometimes our customers react that they feel the registration of materials in a warehouse scenario is a bit confusing. The reason for this, is that there are two ways of registering used items on a service order.

  1. You can key in the material in the service order (As you can see in the picture above), and then post it. Then the items will be SOLD from the specified location using a project item journal. There are now way to implement proper warehouse processes in this scenario.
  2. You can create item requirements, that essential is a sales order line, and so support warehouse processes. The drawback, it that the lines posted in the item requirement isn’t visible on the service order screen.

So I decided to create a very easy to use Data Collection Studio application, that allows a more simpler en easy to use approach, and that it closed to the expected process flow.

In this service order I need some items that is not on the list, so I scan item 100, and I need 2 pcs

On the service order, the new line is added, but is marked as “posted” :

But this is “just-for-show” to create a better visibility for the service operator.

The real transaction is located on the item requirements:

The next stage is packingslip update or invoicing.

By this added functionality it means that we have a very simplified way for allowing service personnel into the warehouse, and still maintaining 100% inventory accuracy.

I end this blogpost with a picture from WMD warehouse: