-
Cash Management - Warning on close shift of a discrepancy
It would be really useful if the POS warned the user of a discrepancy between cash taken and counted before closing the shift. The functionality would check each payment method where counting is required, and identify if a discrepancy is present. If yes this would then warn the user about the discrepancy and ensure they agree with the value before closing the shift. If they do not agree, they can go back, re-count their takings and amend banking or tender declaration values. We have developed this for 2 customers now, so I believe it would be beneficial to add into the standard functionality. Consideration would be required for the different shift closing / statement calc mechanisms -
Apply discount proportionately across all lines for least expensive discount type
When using the 'Least expensive' mix and match discount, retailers would like the discount to be applied proportionately across all the qualifying lines of the discount, instead of just on the least expensive item. The reason for this is so that when an item is returned to the store, the customer receives the correct value back, regardless of which of the lines are being returned. This also prevents fraudulent transactions where a customer may have purchased against a buy two get the cheapest item free offer, then simply return the most expensive item, (resulting in obtaining the other item for free). This would need to be a parameter under the discount parameters in the retail parameters form. The result would be to change the logic under the DistributeLeastExpensive code within the pricing engine for MixAndMatch discounts, so that instead of splitting the value across the number of least expensive lines qty setting, it would split across the mix and match line group 'number of products needed' value.
-
New promotion type: Threshold item promotion
There is a gap in the promotions engine which has been highlighted by several of my customers. They want to be able to create a threshold discount, which applies a discount to a specific item on the transaction. For example: Spend $100 Get Item X at 50% off. Or Spend $150 Get Item X Free Of Charge (100% off). At present you can only use mix and match promotions based on a quantity of items sold. Existing threshold discounting can only apply a $ or % value off of the entire basket, not a specific item We would need to be able to configure a threshold discount, (so triggered based on basket spend), to apply a discount to specific items in the basket, and be able to specify $ off, % off or deal price for one or more items. In order to trigger the promotion, the threshold will need to have been reached, and the item(s) being discounted must be added to the basket. Also the threshold should be met not including the item being discounted (i.e. for the Spend $150 get Item X Free of charge, if item X is $20, they will need to have spent $170, and the discount applied will be $20, to the specified item only). -
Fix gift receipt prompt displaying incorrect values
The prompt for gift receipts has bugs which have been rejected for fix as by design. Although these issues are minor, they add to customer concerns of inconsistency in the product for user experience. This particular issue is caused by 'exchange' type transactions, (sale and refund on same cash and carry style transaction), where by the returned item(s) and any voided lines are given to the operator as an option to print on a gift receipt. When either of these lines are selected, a receipt prints with no lines, (just header and footer). The gift receipt prompt correctly does not display for the return only transaction. On a normal sales transaction voided lines are correctly not given as an option to print on lines.
-
Adyen Merchant account per store
A number of retailers have a setup where they have a merchant account with their PSP per store. This helps in being able to search for transactions and separate devices etc across stores. The merchant id setting is currently stored on the hardware profile, and as a result a separate hardware profile is then required per store which is not desirable. Please enable a mechanism where a merchant id set at store level can override the value set on the hardware profile.
-
Improvements to e-receipt design capabilities
The current capabilities around email receipts are extremely basic and honestly not fit for purpose in a world where email has removed the need for paper.
EVERY customer I work with requests e-receipt capabilities as a mandatory requirement of the product, and the vast majority already have the capability in their legacy POS systems.
At present we only have the option of embedding a single placeholder, for the entire receipt message, into the email template. When the receipt body is inserted, all formatting completed in the receipt designer is ignored, all the fields bunch up together, and it is not possible to do anything about it.
As a bare minimum, the receipt should take any spacing from the designer into account. So that there is at least some possibility of making it readable.
We also need to be able to display the bar code of the receipt id, to be able to scan for returns etc. Ideally we would be able to determine which bar code format, (often QR code is requested). Again this is a mandatory requirement for every customer I am currently working with.
In an ideal world, we would be able to have a separate design between the printable version and emailed version. The emailed version would be able to use different fonts and colours, which would tie in with any corporate branding. This may then require a different designer to the existing receipt designer, so I would assume is quite a lot of work.
Unfortunately with the limitations at present, most customers are having to use a third party tool to complete which is not a good story. -
Re-send email receipt for a completed transaction
It would be great if from the journal screen, it is possible to send an email receipt again for that transaction. Obviously you can currently re-print the physical receipt - but paper receipts are becoming a thing of the past! Email receipts are the way forward.
-
New DOM rule based on stock churn
Since the release of the distributed order management functionality, we have seen a massive amount of customers interest. One ask that every single one of our customers has raised, is the ability to prioritise order assignment based on stock churn of the items on the order. The core business driver they are seeing for implementing the functionality, is to remove slow moving or end of season stock from stores, through sales (being delivered to customer), to minimise the costly exercise of consolidation back to larger stores or back to a DC, to be sold at clearance events/shows etc. In order to maximise the benefit, it would be great if a DOM rule could be created to prioritise the fulfillment location based on if the items are slow moving at the location. This ensures that stores actually selling the item in store retain the stock required for in store sales, where as stores struggling to move that line are able to reduce the on-hand stock. -
Ability to re-print receipt from customer order history screen
Currently, receipt re-prints are only available from the journal view in POS. Often, when trying to find the receipt you want to re-print it is quicker to search for the customer using the existing search capabilities, and look at their order history from the customer details view. As it is not possible to re-print from that screen, you then have to note down the receipt id, and go to your journal view to find the order again, which is not a great user experience, and time consuming.
-
Stop cash management printing
It would be great if we had the ability to disable all cash management receipts from printing. Currently every time you complete a starting amount, tender declaration, bank drop etc. a slip prints out with the information. As the information is recorded, and can be reported from (both in HQ or via a channel report), there is no need to print this information. It is a waste of paper and unnecessary.
You’re offline. This is a read only version of the page.
