Info codes are a great way of capturing additional information for reporting but they are also a great feature for taking both the customer and worker through a journey to ensure transactions and orders are created in a certain way by the business and hold all of the relevant information that the business needs to provide a great customer experience both during and after the sale has happened.

Using the info code input type - 'Customer' or 'Product' it would be great if instead of using this to capture a customer account number or a product number against the info code which is simply held against the sales line, that the system in fact either:

- Adds the Customer Account to the transaction

- Adds the product selected to the transaction basket

A customer requirement that I have come across is the requirement to hold a Customer Account on a transaction when a specific product is added to the basket. Setting up the info codes with an input type of customer the system takes you to the customer search screen whereby you can search/select the relevant customer. But the required output of this was the Customer Account being added to the transaction not as part of the order line within an info code.

Additionally, the product input type would work better if this could direct the customer/worker not just to the product search screen to search/select a product to be added to a response to an info code but to help drive the upsell/cross sell by taking them to a specific category of products that relate to the purchase of the original product selected AND add it to the basket for purchase.