More than a place.
A world to discover.

Visitors could search by shop name or describe what they need: “I want a chocolate cake” or “Where can I find a clothing shop?” An AI assistant would suggest relevant places based on information supplied and maintained by the centre and its retailers.

The directory could also include toilets, lifts, stairs, food courts and other registered services. Response quality would depend on the accuracy and coverage of the available information.

After choosing a destination, visitors would enter or confirm their starting point. An interactive map would show a route through the centre’s corridors, based on approved floor plans and validated connections.

Camera-based directions are also part of the vision, with separate development and on-site positioning tests required.

The centre could register found items with descriptions and, where appropriate, photos. Visitors could browse the list and follow the centre’s process to confirm ownership and collect an item.

Retailers could promote products, offers and promotions within the guide. Clearly labelled advertising could create a commercial opportunity, with pricing and any revenue share for the centre agreed through negotiation.

A future extension could help visitors identify shops offering a particular product. Reliable availability would require retailer system integrations or another agreed process for keeping product information current.

A QR code on a sign or kiosk would open the guide in the customer’s browser. The proposed options are identification through the retailer’s loyalty programme, using a CPF in Brazil and the authentication process defined by the retailer, or a guest purchase session with a temporary code.

Benefits such as cashback would depend on an integration with an existing retailer programme. Identification, session handling and use of customer data would be agreed with the retailer.

Customers could search a connected catalogue, consult prices and offers, and find a route to the aisle and location assigned to a product. Camera-based guidance is a further development goal.

Catalogue data, prices, stock and shelf locations would need to be supplied, integrated and kept up to date by the store.

Customers would scan existing product barcodes as they pick up items. The virtual basket would list registered products and show the purchase total before checkout. Alternative labelling could also be studied with the retailer.

Customers could continue to a conventional checkout under the store’s agreed process, or complete payment in the site using supported integrations, such as Pix, cards and digital wallets, including Apple Pay where available.

Unlike a shared self-service kiosk, each customer would use their own phone. The aim is to avoid the conventional checkout queue when paying online, while following the store’s verification process.

The proposed exit flow would compare the paid purchase with tagged items detected by sensors. A discrepancy could alert staff to carry out a check.

This capability still needs feasibility studies and real-world validation. Tag and sensor technology, reliability, costs and discrepancy procedures would be assessed with the retailer. Scanning a barcode into a basket does not, by itself, enable automatic remote detection of every item at the exit.

Passengers would scan a QR code and search the terminal map for check-in desks, boarding gates, baggage reclaim, toilets, shops, restaurants and other services.

Routes would need to reflect real floors, access restrictions, checkpoints and the areas each passenger may enter. Camera-based guidance would require additional development and validation.

Passengers could select or enter a flight to see its scheduled time, status and boarding gate, using an authorised, integrated data source. They could then select the gate as a destination.

Gate and time changes would be shown according to the source’s coverage and update capabilities; live flight information is not connected in the current demonstration.

Passengers could explore participating restaurants, choose a meal and order through Teseu, then follow the collection instructions and pick it up at the restaurant counter.

This would require agreements with each restaurant operator and integration with available ordering and payment services. No restaurant partnerships or API access are assumed.

A further possibility is flight search and ticket purchases through authorised airlines or travel partners. Flight selection, payment, ticket issuance and support would need to be scoped with those partners.

Counter collection refers to food orders. Ticket issuance and presentation would follow the airline’s or travel partner’s process.