• 8

    Multi-select in Return transaction screen in POS

    Suggested by Eduardo Mendoza New  0 Comments

    Actually, in POS when customer makes a return order in the screen on the POS all products are shows in the transaction and is necessary select one by one quantity and reason code. If the lines in transaction are too much, users lost the trace that items selected because not are market in the screen.


    Customers want to see all items selected in the return screen to can be more efficiently the process.


  • 7

    D365 Commerce B2B Linking Online Store Users to the Global Address Book

    Suggested by Maddie Evangelisti New  0 Comments

    avoid using Person-type Customer accounts. We’re requesting your input on the feasibility of an alternate solution that leverages GAB contacts.



    We proposed an approach where each user accessing the Online Store would be associated with a Customer account (Type = Person). These Person-type accounts are linked to their respective Invoice Accounts (Type = Organization) via the Customer hierarchy. Delivery address, lead time, and auto-charge logic are driven by values defined on the Organization-type Customer account.



    We do not want to create separate Person-type Customer accounts, as they believe this would:

    • Introduce data clutter and confusion in their CRM
    • Conflict with their existing customer/contact structure

    They are proposing an alternative:

    • Use contacts from the Global Address Book (GAB) linked to Organization-type customers
    • Map these contacts to Commerce identities (based on email)
    • Let users select a delivery address during checkout, and base lead time/charge logic on that selection rather than the user’s customer record


    Idea:

    1. Commerce Identity Mapping
    2. Can GAB contacts be authenticated in D365 Commerce as B2B users without being Person-type Customer accounts?
    3. Lead Time & Pricing Logic
    4. Is it technically feasible to:
    • Use delivery address selection at checkout (regardless of user record)
    • Drive lead time and charges logic based on the selected address, not the logged-in entity
    1. Commerce Limitations
    2. What, if any, limitations would we face in using contacts instead of customer accounts for:
    • Storefront login and access
    • Order history visibility
    • Address validation and delivery charge logic

  • 7

    Add pretty price to POS transactions

    Suggested by Jon Crespo New  0 Comments

    In some scenarios it would be interest to apply pretty price to each transaction line in the POS. Or maybe to the total amount of the transaction.


    We have some customers that want to use it, and the rounding of the tender type is not enough because they want to get the amount rounded to complace with the Tax Authorities.


  • 7

    To make Unit of measure not compulsory on Periodic discount line

    Suggested by Nicholas Fook New  0 Comments

    There should be an option, not to make Unit of measure compulsory for Calculation type = 'Amount off' at Periodic discount line. Else it may impact how the Quantity limit should work, when they are different unit of measure from a product category.


    The option could be to make/refer the Unit of measure from product master.


  • 7

    POS: Separate permissions for actions on transfer orders

    Suggested by RubĂ©n Garrido New  0 Comments

    Currently, it is possible to select which POS user profile has permission to create a transfer. If the user has permission, they can create, send and receive transfers related to their store. It would be interesting to have separate permissions for each of these actions, so that a user can create transfers but not send them, for example.


  • 7

    Donate the change option

    Suggested by Simon Sholl New  0 Comments

    At a lot of retailers (especially self checkout) an option is prompted at the end asking if the customer would like to donate their change


    we can partially acheive this functionality by using an info code linked to a payment type to prompt if you would like to donate change and link it to a service item being added to the basket.


    however this could be vastly improved by calculating the round up amounts for card, or change being given for cash




  • 7

    Mix and match BOGO discounts that honor customer pricing

    Suggested by Brandon Best New  0 Comments

    D365 is currently missing the capability to use Mix and Match discounts to be leveraged for BOGO scenarios that honor customer trade agreement pricing. With the current setup, a discount trade agreement is overridden by a mix and match discount line set to 0% or $0 off, meaning the customer is forced to pay full price for their "Buy one" item. It would be great for omni-channel and B2B customer mix if we could configure a BOGO retail promotion that honors the customer's pricing for the first item and overrides the price of the second. This could be as simple as a new type of discount group on the mix and match called "unchanged" or "customer pricing" that is treated as a required line that receives no change in pricing.


  • 7

    Allow registration of different bank accounts for Retail statements in One voucher

    In General Ledger, when the parameter "Allow multiple transactions within one voucher" is disabled, and there are different bank accounts for each payment method in Retail stores, it does not allow the posting of statements, so it is necessary to turn on the aforementioned parameter in order to record the transactions.


    It is proposed that it be possible to record in different bank accounts using the One voucher functionality ("Allow multiple transactions within one voucher" disabled) for the Commerce module, considering that Microsoft suggests the use of One voucher but Retail statements have this limitation.


  • 7

    Return Policy for Cancellation of Transaction From the POS

    Suggested by Fayaz Rafeeq New  0 Comments

    The POS currently supports the return policy only for fulfilled or completed cash & carry transactions. If we are doing a return for a customer order via cancellation of the transaction, POS doesn't respect the channel return policy.


    As the cancellation of the transaction is also treated as a return from the POS and the amount due is always negative, this should also respect the channel return policy.


  • 7

    Archiving cash and carry transactions In the Headquarter from the sales order table list.

    Suggested by Huguette Giramata New  2 Comments

    The cx wants to delete sales order because they manage B2C operations with high volume capacity. However, the system produces an excessive amount of data in the related tables, such as the sales table and transactions. As a result, they would like to remove some of the old sales records to relief the tables that are fed from these tables. Therefore, they would like to use the clean-up function but they are facing an issue with Archiving sales order generated from the MPOS only, while transactions generated from HQ they are able to Archive them where they use the account receivable parameter to enable deleted transaction to be archived in the voided sales order as they don’t want to delete sales order permanently but to archive them. And they are using the cleanup function by enabling first the parameter.