1. Plan
Choose the store or stores, product category and main questions your team wants to explore. Agree the information needed and what a useful evaluation should show.
RETAIL PILOT PROGRAMME
A focused pilot gives your team the opportunity to explore iNteract with selected products, test the shopper experience and review what the available Retail Intelligence can tell you before considering a wider rollout.

Every store is different. A pilot helps a retailer understand how QR-based product assistance fits its customers, product range and day-to-day operations.
It is a practical way to explore the platform before making a bigger deployment decision.
A pilot should begin with the retailer's own stores, selected products and the questions the team wants to explore. Suitable product information needs to be available so the shopper experience has a useful foundation.
Agree the QR placement, retailer branding, connectivity, store-team preparation and who will maintain the information or respond to issues. The privacy arrangements, available reporting and responsibilities also need to be clear before the evaluation begins.
A retailer with an existing app can discuss whether a separate connection would be useful, but the initial browser route does not depend on it. Starting with a manageable scope gives the team a way to learn about the practical work as well as the software.
Choose the store or stores, product category and main questions your team wants to explore. Agree the information needed and what a useful evaluation should show.
Prepare product information and introduce QR codes on selected products or shelf displays. Confirm the retailer-branded experience, store placement and the support needed for the trial.
Shoppers use their phones to open ARI and ask product questions. Review the interaction information and other measures that the platform and agreed pilot setup can support.
Discuss what shoppers found useful, which questions came up and what could be improved. Decide whether to refine the experience, try another category or consider a broader rollout.
A shopper uses a smartphone to scan a QR code on a prepared product or shelf display. The browser-based experience opens ARI, where the shopper can ask about the available product information and follow up for clarity.
The retailer can then review supported interaction information in the available reporting tools. The aim is to understand whether the help is useful and which questions are emerging. Product comparisons or other additional functions should be included only where their scenario has been validated for the trial.
The scope and measurements would be agreed for the pilot. Questions and engagement are not automatically evidence of a completed purchase or increased sales.
Review which prepared products attract supported interactions and what shoppers ask about them. Interest can be worth exploring whether or not a purchase is recorded.
Look for repeated questions, gaps in product descriptions or information store employees need to assist customers. Discuss the experience with store teams alongside the available reporting.
Where the agreed setup supports them, consider product comparison interactions and the sequence of engagement. The exact events and measures need confirmation; an engagement path alone does not prove purchase intent.
If supported in the pilot, explore questions and engagement relating to offers or brand information. Do not treat that activity as proof of promotional effectiveness or a completed sale.
Assess whether the information helps the team investigate merchandising, product information and customer-experience questions. Business value is something to evaluate, not a promised outcome.
The initial experience uses cloud-based software and QR codes, so you can explore iNteract without building a new shopper app or connecting it to your checkout system.
A pilot still needs suitable product information, store preparation and agreed responsibilities. It should be manageable, useful and clearly focused on what your team wants to understand.
Explore selected stores or categories before considering a wider deployment. An evaluation can help teams consider how the shopper experience fits established operations and digital investments.
Explore digital product assistance without first building a dedicated shopper app. A smaller initial scope can help establish which information and store preparation are needed.
Discuss contextual product information and possible collaboration with retailers. Future media or campaign ideas may form part of the conversation, but are not presented as established commercial services or proven results.
The evaluation should bring together supported reporting, the questions raised by shoppers and the experience of the retailer's team. Consider what worked, what information was missing and whether the original objectives were useful.
The next step could be to improve the product information, refine the QR placement, evaluate another category, extend to more stores or decide that further work is needed before expanding. A broader rollout should follow a considered decision about preparation, support, privacy and the reporting that can be relied on.
There is no fixed store count, duration or guaranteed result implied by this process. Demonstration and pilot discussions are opportunities to establish a suitable scope, not evidence that commercial pilots have already been completed.