
Session type
Theme
Day 1 programme
8:50
9:00
9:00
09:30
A replacement may solve a real limitation. Migration, support and existing know-how can still change whether the move is worthwhile.
9:30
10:00
AI may speed up an authorised campaign action, but teams still have to decide what needs approval and how mistakes can be contained.
10:00
10:15
A worked 12-month example compares licence, implementation and support costs, with staff hours and campaign continuity shown separately.
10:15
10:30
Faster drafting can shift work rather than save it. Four routes compare the total effort needed for the same accepted campaign output.
10:30
11:00
Frequent use can still leave work unfinished, while a tool used only occasionally may already be doing its job.
11:00
11:20
11:20
11:50
A first campaign may not need every system connected. It still needs dependable inputs, someone responsible for handovers and a workable fallback.
11:50
12:05
A worked task log shows how user observations and support requests can reveal different causes and guide a fair retest.
12:05
12:35
Changing a background can change what customers believe about a product, even when the pack itself stays accurate.
12:35
13:05
Automating production can save time for one team while creating extra review, correction and support work elsewhere.
13:05
14:00
14:00
14:30
Shared capabilities can reduce duplicate work, but teams must agree who controls local changes and pays for upkeep.
14:30
15:00
Successful use by one team does not settle what the next will need in access, preparation or continuing support.
15:00
16:00
RETAIL SUMMIT 2027 · PROGRAMME
Discover the full Retail Summit 2027 programme and explore the specialist stages across both days.
View All Stages









































































































































































































