-
Receipt date format
On the receipt format you're able to select time format 12H or 24H, but for date, there's only one option, which is decided by the store language. This is not good, as you can't just change the store language to change date format, as all product translations will disappear. There should be the options to select date format DDMMYY or MMDDYY on the receipt format. -
Different POS permissions per store
Workers may require different POS permissions in the different stores, but I don't see that D365 supports this. If I'm correct, this classifies as an idea, which some might think is quite good. This is useful in cases were a worker is hired to several positions/jobs with different pos permission groups. -
Info box instead of pop-up info code.
Several customers dislike the info codes because of the pop-ups which the cashier has to close every time. What about adding a box to the screen layout, where the info is just shown when an item is scanned? A parameter, if no input is required, on the info code can define if this info code should pop up or just show in this new box, which could be added to the screen layout. -
Info code - Signature
To make use of the signature pad in more scenarios than when selecting a certain payment method, I'd like to suggest a new info code input type: Signature. That would make it possible to trigger a customer signature request in many scenarios without customization.
-
Item name/description on forms
When printing a sales confirmation/packing slip/invoice, the item description in printed. For instance if you're selling item 81100 in Contoso, this will be printed: A modern notch-lapel jacket and flat-front trousers give this trim-fit suit a modern feel. Both the jacket and trousers are made with dark-grey virgin wool. The jacket is fully lined, and the trousers are not lined. Instead of the item name 'Trim Fit Suit'. There's a parameter which makes it possible to include item name as well as description, but I'd like to see a parameter to exclude item description, which in our case could include several hundred characters. A long description is nice to have in POS, but not on the forms.
-
Product attributes in POS
When using attributes of type ProvisionedChannelAttributeReference, such as 'product category' or 'product name', and you set these to 'show attribute in channel' in the channel metadata, they are not shown on an item in POS before you've opened the product's attribute form in D365 and then ran the 1040 job. The reason is that the value isn't populated in the EcoResProductAttributeValue before you open the product's attributes form. That means you basically have to open the attributes on every single item to get these kind of attributes to show in POS. I'd like to see a job that populates these values after adding such an attribute to a relevant attribute group, as it's not an option to click on attributes manually on thousands of products.
-
Store Configuration Status
As I've experienced many customers forget to create number sequences for statement and voucher when setting up new stores, I think it would be very useful to include these as dependencies in the store configuration status. -
Print behavior receipt formats
I'd like the opportunity to set print behavior for a receipt format based on payment method. Scenario: In Norway it's mandatory to print the sales receipt when the customer are paying with cash. But when a credit/debet card is used, sales receipts are only printed if the customers ask for it. A new option in receipt format print behavior, such as 'payment method', and a print behavior parameter on store's payment methods, is one way that could solve this.
You’re offline. This is a read only version of the page.
