web
You’re offline. This is a read only version of the page.
close
  • Wildcard product search in POS

    To my experience it is not possible to add wildcards in the product search in MPOS/ CPOS (*, %, etc.) This limits the results to the beginning of a criteria. Ex. a search for "ball" will give a result for "ballpark" but not "baseball". In Norway, for instance, we do not divide compounded words. For instance "swimming trunks" is "badebukse" not "bade bukse". If you try to search for "bukse" there will be no result.
  • Block price calculation on sales order and sales qutation

    The nature of D365 Commerce is to recalculate price and discounts whenever you update the sales order or sales quotation, with or without Call center. This has been improved by the possibility to set different sources that activates a dialogue in the Trade agreement evaluation. However, there are still scenarios where this is not sufficient. 1. A sales order is created during a promotion and the promotional discount is applied. The product, however, is not in stock and have to be purchased. The product arrives at the store the week after, and the promotion period is over. The sales order is updated with additional information, and perhaps a new charge or a new line for freight cost. This will cause the sales order to recalculate prices and discounts and the promotional discount is replaced with the standard price. 2. A sales quotation is created and a price simulation is conducted. The net amount is updated on the quotation line. Additional lines are added and the calculated line is updated with the original price. Suggestion: Add more sources to the Trade agreement evaluation like promotional discounts and price simulations.
  • POS prepayment should not be considered as a free limit

    If a prepayment is registered at the POS for a sales order created at the HQ, the prepayment is open to be used as a free limit. The open balance means that it is possible to use this as a credit limit until the original sales order is invoiced and settled. A prepayment should be dedicated to the sales order in question, and not be treated as a free limit.
  • Sales quotation pick-up mode of delivery

    If the user is associated with a callcenter and the pick-up mode of delivery i set up in the Commerce parameters, the delivery address changes to the store address if the pick-up mode of delivery is selected in a sales order. This is not the case if you create a sales quotation. There should be no difference between a sales order and a sales quotation in this regard. The expectation is that the behaviour is the same.
  • The abillity to pick-up and edit project sales orders in POS

    The POS supports payment of project invoices. The next natural step is to allow the POS to pick-up and to edit project sales orders created in the HQ. Instead of invoicing the project sales order directly, it can do a post packing slip update and be invoiced by the standard project invoicing routines.
  • Create project sales orders in POS

    For a more complete OMNI experience the POS and the HQ should be quite similar in user- and customer experience. Ref. https://experience.dynamics.com/ideas/idea/?ideaid=54d71e95-6298-eb11-89ee-0003ff45d48e. At least in our business there is an extensive use of projects where our customers relate their external projects to our sales orders. This is fine in HQ but not in POS. Therefore, it should be possible to relate a POS transaction to a project and a project sales order is created by the transactional statement or by the create sales order/ create quotation, operation.
  • The ability to register a contact on a POS transaction

    If you have a sale in POS on a registered customer, B2C or B2B, it's sometimes important to be able to register the person (contact) that's present. This is due to tracing, reporting, invoice marking and/ or to control who is eligible to use the customer account in question. The selected contact should then be registered as contact on the sales order in HQ by the transactional statement or the sales order/ quotation operation.
  • POS fails to alert user if a barcode is not found during scanning

    This applies to POS with wedge scanners, not OPOS. The dialogue that appears when a barcode is not found during scanning is not visible enough. "The product associated with the bar code was not found. Please search for the product from the product search page." This occupies only a small fragment of the screen, like all other dialogues. This is a problem because, if you don’t keep our eyes on the screen at all time you can scan a lot of items before you are aware of the situation, that one or more barcodes was not recognized. If the dialogue filled the screen, and even better, in a bright colour, it would be easier to detect. Even better if an error sound could be played.
  • POS on-screen signature

    It's a great feature to be able to sign directly on the screen, especially on hand-held devices. The problem however is that the dialogue is too small. The dialogue is the same size as all other dialogues. It should also be possible to set the signature to be mandatory and not be able to conclude the transaction with a payment method that triggers a signature, and skip it.
  • POS signature capture on returns

    It should be possible to trigger a signature capture on returns. It would be a lot easier to administrate returns if there is no need to print extra receipts on returns for the customer to sign. This should be stored electronically.