Trade fairs have one definitive characteristic: the date doesn’t move. Salone del Mobile is when it is; Euroluce is when it is. There is no room for negotiation, no extensions. And this means that every year, in the weeks leading up to the opening, the exact same thing happens across dozens of companies in the industry: the pace of work shifts, priorities collapse, and teams enter emergency mode.
It is not necessarily wrong to speed up before a trade fair. The problem arises when that acceleration is not the result of a natural peak, but of poorly managed information in the preceding weeks.
The recurring emergency
In the weeks leading up to a trade fair, work that should already be finished suddenly resurfaces as urgent: new product data sheets are incomplete, photos are still in progress or not linked to the correct codes, translations for international markets are missing or rushed, and materials for sales agents do not match what is online. Marketing is chasing the technical department for definitive data. The technical department is waiting for final approval on variants. Someone patches it all together into an export that will only be used for a week.
Then the trade fair arrives, everything looks great, and the panic is forgotten. Until next year.
This cycle repeats because the root cause is never addressed. Every time a new collection is launched, product data is treated as something to be built from scratch: information is gathered, organised, and published, but that structure is never maintained continuously. When the next launch comes around, the process starts all over again.
Product data management: what changes with a structured workflow
A collection launch should not be a standalone project. It should be the final output of a process that begins much earlier, while the products are still in development.
If the information flow is structured — with a centralized tool like a PIM (Product Information Management) that gathers technical data during the development phase, progressively enriches it with marketing content, manages it by variant, and makes it available in multiple languages from a single point of entry — then the weeks before the trade fair are no longer an emergency. They are just a final check.
The catalogue is not built at the last minute before the Salone: it is ready because it has been fed at the right time, department by department, with information validated upfront. Product sheets already exist, in the right languages, with photos matched to the correct variants. What remains is quality control, not content production.
This shift in perspective is not a matter of discipline or goodwill. It is a matter of system: without a tool to support the workflow structurally, even the most organised teams tend to slip into emergency mode because the work of building data has no natural place to happen.
The collection launch as a stress-test for the digital catalogue
There is a useful way to read the difficulties that arise before every trade fair: they are a thermometer for the quality of your product data management system. If every launch generates friction, searching, corrections, and duplication of work, the problem is not the launch itself. It is the underlying structure.
The questions to ask are concrete: how many people are working in parallel on the same data, across different files? How much time passes between the final definition of a product and the availability of the complete data sheet across all channels? How many urgent corrections are made in the two weeks leading up to the trade fair?
The answers show where the bottleneck lies. And in most cases, the bottleneck is not creative production: it is the management and distribution of information.
At MON-KEY, we work with furniture and lighting companies that want to stop treating every launch as an emergency. If you are already thinking about the next trade fair with a hint of anxiety, it is a clear sign that it is worth talking about it beforehand.