A temporary service point: what a pop-up cannot test for a permanent location
A temporary service point helps you meet customers, but it cannot test a whole permanent location. Separate event traffic, repair scope and follow-up.
Article language: English

In this article
On Saturday, a queue forms in front of a repair table. On Monday, someone suggests renting premises. Between those events, several questions remain unanswered: where did people come from, why now, and what would bring them back in an ordinary week? The length of the queue is an observation. Signing a lease requires a decision about a different operation.
Imagine a bag repair workshop setting up a weekend service point at a local event. Selected small repairs can be done on site; more difficult cases are inspected and sent for further discussion. The team wants to understand local interest. A temporary point, often called a pop-up, lets it meet customers at a particular place and time. The conditions of that meeting must remain part of the conclusions.
An event has an offer of its own
The announcement for Worn Wear at LOFTMAN 50th Fes in Kyoto concerned 17 October 2026, a date already past when this article was prepared. Patagonia described free sewing-machine repairs and self-service patching, same-day return and a reservation limit of one sewing repair per person. It also noted that a garment's condition might prevent repair. That is a clearly defined event offer.
The workshop in our example should likewise know what it is actually putting to the test. A demonstration of skill may attract different people from a paid repair that requires leaving a bag. Learning to patch together meets another need again. If all these forms appear on one day, record them separately. A total visitor count will not show which activity people chose.
There is no need to pretend the event is an ordinary permanent location. Its purpose might be promotion, education or learning about particular types of damage. Choose that purpose before opening. Otherwise, the team may call whatever it collected most a success: conversations, photos, forms or items left on the table. Each may be useful, but for a different decision.
The invitation should therefore describe the on-site scope, how an item is accepted and how service ends. "We will repair your bag on Saturday" is a broad promise. "We will inspect the small damage you identify and carry out repairs within the point's scope" still needs a specialist to explain the actual cases covered. Information before the visit should match what the team can really do.
Where did the queue come from?
The original abstract of Zhang and colleagues' 2019 study describes an experiment with Alibaba involving around 800,000 customers. Customers were randomly assigned to receive or not receive a message about a week-long Tmall event; the authors analysed visits and subsequent online purchases. The results concerned connections between a temporary store and the platform. They did not test the lasting profitability of a repair point in a Polish neighbourhood.
For the workshop, this raises a question about how people arrived, not a ready-made forecast. Some guests may have come for the main event. Others heard about the workshop through its own list. Someone travelled across the city specifically for a free service. Recording the route to the visit helps identify which part of the traffic can even be considered in relation to a permanent place.
A brief conversation at intake is enough, without collecting data the team does not need. Ask how a participant learned about the point and what prompted them to come today. Separate the channel from the reason for the decision. Someone may have seen a social media post but brought a bag because they were already going to the event next door. A single form choice may not capture both.
Record changes in conditions throughout the day too. Rain may have reduced street traffic, while an announcement from the stage may suddenly have brought a group of guests. The aim is not to produce a statistical explanation for every minute. It is to stop a final claim that "many customers come on Saturdays" being drawn from one Saturday that an ordinary location could not reproduce.
At closing, the team has recorded eighteen conversations. Six people came for repairs prepared in advance. Four asked about later paid work but have not ordered it yet. The remaining eight attended the demonstration or asked for work outside the point's capacity. These numbers belong only to the hypothetical example. The report should retain eighteen distinct contacts, not turn them into eighteen repairs or eighteen future customers of a permanent location.
For those four people, establish what happens next through the ordinary process. Did they receive a description of the paid work? Were the time and place of handover suitable? Did they ultimately choose the service? Do not retrospectively revise the number who expressed interest after receiving the answers. Keep the sequence of stages. Then it will be possible to see whether the next uncertainty concerned price, travel, timing or whether the repair was possible at all.
Someone had to bring the whole workshop
At the event, the owner, the best specialist and a person helping explain the scope are working. Materials prepared beforehand are close at hand. This may be good organisation for the point, but it is not yet evidence that the same team will be available every week. Record who performed the repairs and who accepted items and spoke to waiting people. Otherwise, the specialist's working time disappears into the general picture of a smoothly running stand.
Separate service from preparation and closing. Materials had to be selected, equipment transported and a work area arranged. Afterwards, someone sorted items referred for further assessment. Opening hours alone do not show the whole effort. A permanent location may need a different organisation, but also recurring work that the customer standing at the table cannot see.

Check which cases fit within the available capacity. If most visits concerned damage the point did not handle, interest in repair is a real signal to understand. It does not, however, confirm demand for the work the company could perform there at that time. Separate accepted cases, those deferred for assessment and those outside the offer, along with the reason.
Your own rules for booking and releasing a service slot help organise a limited number of appointments. The article on booking and releasing a slot (in Polish) discusses how to set them. In the report, also retain the people for whom no slot was left. Their number is not the number of future paid orders. It may show that the day's schedule limited the observation and that the next inquiry should distribute intake differently.
Also plan an ordinary week at the prospective point in terms of tasks. Who accepts an item on Wednesday when the specialist is working at the main workshop? Where are bags awaiting an answer kept? Who returns a completed repair to someone arriving after work? An additional location may serve only for intake and collection. In that case, the specialist's weekend work on site does not yet show how an intake point alone would operate.
Only after mapping those activities should you compare the options. For one team taking events to several places, preparing a trip may be the main work. An intake point adds regular handovers to the workshop. A full location requires the availability of the necessary expertise during the hours promised on the website to be confirmed. Those differences are needed for a discussion of the choice, even before the exact cost of every option is known.
After Saturday, the bag still has an owner
On a separate page about its regular repair intake in Japan, Patagonia describes different service routes and says price and timing depend on the product's condition and damage. For an online request, it provides for shipping or handover through a store. This is a different scope of information from an announcement for a one-day event with same-day repairs.
In the workshop, therefore, define the route for a case that will not be completed on site. The customer should know who will contact them after inspection, where they will hand over the item and what happens if they decide against further work. At the weekend, do not promise a return date the ordinary workshop has not confirmed. The point may close on Sunday, but cases left with it do not close with the tent.
Recording what happens to an order afterwards also reveals something the event alone cannot. A participant may want a free small fix on site and decline after receiving information about a larger paid repair. They may instead use the workshop later at another location. These outcomes lead to different decisions about place. A free trial and a free plan (in Polish) require a similar distinction: you need to know what behaviour each form actually lets you observe.
The event page should change alongside the service. After the date, show that the point has ended and provide the current route for cases already accepted. Keep the necessary information about the past scope. A new visitor should not read a registration button a month later as an invitation for the next Saturday. On your own map of service points, give a temporary presence a date as clear as its address. The article on maps of service points (in Polish) discusses how to design one.
If you need to organise the invitation, on-site scope and message after closing, Aeneia Design can bring those details together on a clear page. The company must first confirm its ability to provide the service and what happens to accepted cases afterwards. The digital design should show those decisions to someone seeing the invitation for the first time.
Which next test will bring the decision about a location closer?
After the weekend, choose one uncertainty about the permanent operation. It might be willingness to pay for repair, traffic without a large event or the ability of the regular staff to provide the service. Do not try to settle them all in one summary. Record your own comparison before the next stage. The article on a business experiment card (in Polish) explains how to prepare one.
When comparing later days, keep a record of the scope and conditions. If the first Saturday included free sewing and the second only intake for a quote, the visit counts describe different offers. Likewise, the presence of a popular specialist may be part of the event that you do not plan for a permanent point. You do not need to force everything to be equal. You do need to know which differences limit the answer to the question about the location.
Further inquiry might include an ordinary day without an accompanying event, or a clearly priced scope and a different booking method. Make changes in conditions explicit. If the next event attracts fewer people, that does not necessarily mean the offer has worsened. You may be testing, for the first time, the very service and situation that would exist after a location opens.
When discussing a permanent place, also check whether opening hours fit the customer's task. Someone present on Saturday may need to drop off a bag in the morning before work and collect it on the evening of another day. Availability at one of those times does not confirm the whole journey. This is a concrete condition to investigate when choosing an intake point.
Keep several decisions possible. The workshop might remain mobile, work with an existing intake point or continue investigating a permanent location. Strategic scenarios without pretending to forecast (in Polish) help examine the conditions for these directions without immediately choosing the prettiest shopfront visualisation. A successful weekend can be a good reason for a next step. It need not be a reason to order a sign.







