Public Profile
  • POS sales should be posted as a physical transaction

    When POS sales are imported to Dynamics 365 through p-jobs, the transactions are creating inventory transactions with the issue status "reserved physical/on-order". It would make much more sense to have theese transactions posted as deduced. This because the current design creates a lot of issues in terms of counting in the stores. The statement postings can be delayed or stopped because of bugs, and any counting then will be wrong. So instead of having theese intermediate statuses I hope that Microsoft can find a way to physically post the retail transactions as soon as they are imported. Yes, I know that this is difficult, but the ability to have correct onhand and the ability to count is more important.

  • Allow less than 100% cut's on POS receipts/reports

    When printing a receipt, or any other receiptprinter documents, the printer cut's the paper 100%. What is most common is to cut the receipt with 95%. If cut 100%, the receipt very often falls down to the floor. When cut 95% there is a small strip of uncut paper that the casher then rips of when handing the receipt to the customer. There are no parameters that lets us control this setting. The RetailDSK dll/class that controls this process is interop.oposPOSPrinter, and the class method is OPOSPOSPrinterClass.CutPaper(Int). What we need is the following : 1. The ability to control CutPaper to 95% 2. The ability to add extensions to this class We prefer no 1. Hardware profile is set up with OPOS printer - HP A799 printer Repro steps: Log into MPOS, and print a receipt or X-report and see that the paper is cut 100%
  • Split-Bill functionallity

    Split Bill is a highly requested and common function for many restaurants customers frequently request to split bill directly from the point of sales system. This feature offers a convenience to customers who wants to know the exact amount to pay for their food orders respectively. Also separate receipts are generated when the bill is split. There are different way's of splitting a bill. Like evenly divided, where all bill contains the same lines, but the amount's are divided by the number of payers. Also the most common requirement is to be able to move the transaction lines between the bills, and then separately pay them. In a restaurant we often see that some guests go before others, and want's to pay their bill before others. In addition to Split Bill, there is also a need of "Combine Bill" to take two sales, and combine them again. The Dynamics 365 Fore Retail have an enormous potential for also covering restaurant domains, and this is a key functionality for covering this domain.

  • Retail finance reconcilliation

    In Dynamics 365 it is difficult to see if all retail transactions have been financially posted. Issues, errors and bugs sometimes results in that transactions are not included in the statements. In most companies it is common practice to perform financial period closing, and then closing the period. But to be sure that no more transactions will be posted, it would make sense to have some functionality to see transactions that have not been posted/financially updated. Also, a financial reconciliation would make sense to have, making sure that all statements have been calculated and posted. Also including steps in the financial period closing would help. Can we have more reconciliation functionality in the retail/Finance domain ?
  • Price check in store currencies

    In POS there is a possibility to perform price check on a product. But the price is only shown in current store currency. Retailers do also want the ability to perform price checks on the other currencies that is used in the store. This is very relevant for retailers that accept multiple currencies.

  • Welcome or transaction screen at login based on start amount

    In the "Screen Layout" it is possible to spesify if Default start screen is "Welcome Screen" or "Transaction Screen". Cashier's say they want to get to the Welcome screen when there are no shifts or if no start amount have been entered. Else they would prefer to get to the "Transaction screen". The idea is therefore to have an option to say "Always Welcome Screen", "Always Transaction Screen", "Start amount dependent". Please evaluate this small' easy fix :-)
  • Support for "Not Exists joins" in Advanced filter/Sort

    It would be highly appriciated to have the possiblity to allow for "not- Exists-Joins" in the Advanced filter/Sort. This would allow us to filter for products without inventory transactions. Vendors with no purchase orders or sales orders with no salesorder lines. I did a blog post about this a few years ago, that is available here https://kurthatlevik.com/2014/11/19/dynamics-ax-2012-r3-to-exist-or-not-that-is-the-question/ Feel free to incorporate this into the platform product backlog.

  • Add CPOS as a Hybrid App in Apple AppStore

    Having a standard Hybrid App for CPOS would greatly benetif customers that do not need to create customized solution. Please create the CPOS as a hybrid app, and make it available in AppStore and on the Microsoft AppSource

  • Allow custom fields to be distributed to channel database without extensions

    In D365 F&O it is now possible to add new fields directly from the UI. Like adding a new field to the customer. I see that we can add this field manually to the sub-scheduler jobs, and also add the field to the schema. It would be nice if this also was supported in the channel database, and more dynamically adding new fields to the channel database without creating extensions.
  • Add functionallity for handling tips.

    In hospitality scenario's it is common for customers to provide tips for good service. The tips is paid in cash, or by adding tips the payment terminal. It is an requirement for many customer to keep track of tips and to make sure they are paid out accordingly. Dynamics 365 do not have any known functionality for handling tips together with payment terminals. This is there for an idea to support this.