• Ability to mark a product as non-returnable

    Retailers run clearance or final sales fairly often for a variety of reasons (primary one being ability to get rid of the inventory). Most of the times, it also means that these products are non-returnable. In addition to clearance scenarios, retailers sometimes collect donations for charities and the donation amount is added to the customer order total. In such cases, retailers may not want to refund the donation amount back to customers if the entire or part of the order is refunded. All such scenarios require the ability to mark an item (product, product master or service) as non-refundable / non-returnable. My idea is to provide a flag on Released Product set up which would control whether an item can be returned or not. This would save partners from doing additional extensions to meet client's requirements.
  • Ability to restrict Loyalty Points redemption in increments of fixed points

    Some retailers have a minimum threshold of Loyalty Points that are required to redeem for a fixed reward, e.g. redeem 500 points for $10 off. Additional rewards can be redeemed in increments of 500 points, so if customer wants to redeem 1000 points, they can get $20 off or 1500 points for $30 off. This is fairly common scenario when retailers allow fixed $ amount redemption when customer has accrued/reached a points milestones. This can be a configurable flag on the loyalty points redemption line so that user can set it to fixed points redemption or the standard behavior.

  • Allow Return of multiple transactions into the same return transaction from POS

    Currently D365 Commerce allows return of multiple Customer orders at POS into the same return transaction. This functionality should be extended to Cash & Carry transactions as well. Cash and Carry transactions form a bulk of orders for a retailer. This functionality becomes even more important for retailers where customers are purchasing items across multiple transactions for a project and want to return unused material left over from those purchases. This would save time for cashiers where they have to scan multiple receipts and process returns in multiple transactions.

  • Payment using internal gift cards should not require balance check prior to tender

    POS throws error when redeeming Gift Card with lower balance than the total order amount. 

    The only workaround at this point is that cashier clicks on "Check Balance" button on the payment tender screen, and then enters the exact same amount or a lower amount into the amount field, before they can complete the transaction. This requires additional clicks and manual entries (prone to errors) which adds valuable time to entire transaction (specially in fast paced retail environment). For D365 internally managed Gift Cards, POS should be able to check the balance and apply maximum amount possible automatically to the transaction. If customer wishes to use a lower amount, then cashier should be able to change the amount.

    This would make the gift card redemption process much more seamless, reduce cashier involvement and ultimately reduce transaction time as well as unnecessary human errors.