Recruiting a marketplace software audience from recent seller tasks and verified authority

A marketplace seller software target audience is not everyone who sells online. Make it recruitable by tying eligibility to one recent seller task and a real decision. For example: people at an England merchant who approved, transmitted or corrected a product record, stock update or order exception for one named marketplace account during a stated period.

Fix the job and account boundary

Write the buyer question before the screener. The merchant may be deciding whether to retain its current manual reconciliation or investigate another operating route. Record the legal seller, account owner, catalogue, source system and marketplace. Do not infer any of these from a profile headline.

Separate the people who buy software from those who use or experience the workflow. Relevant populations may include the procurement owner, catalogue or merchandising staff, inventory and order operations, customer service, product-safety owner, finance or VAT reviewer, privacy and security staff, accessibility lead, managed provider and adult customer. A person can occupy several roles, but each interview should state which evidence they can supply.

HMRC's digital-platform seller guidance defines sellers for a particular reporting purpose. It does not prove marketplace activity, buying authority, turnover or software use. Likewise, the ONS business activity and location dataset records broader enterprise and local-unit facts. Neither source gives the audience size.

Write observable eligibility rules

Use a recent event rather than general interest. A catalogue participant could qualify after handling an approved listing change and its marketplace response. An operations participant might qualify after reconciling a cancellation, return or refund. A buyer should have documented authority to approve, reject or recommend the operating route.

The England rule also needs evidence. Choose an operating establishment and decision-location test that fits the study. A registered office, residence or marketplace delivery address alone may not do so. Record cross-border roles rather than forcing them into England.

Build a screener with these fields:

• organisation and role, verified through an authorised contact;
• named marketplace and account relationship;
• recent qualifying task and date range;
• source and destination records used;
• authority over the decision or evidence;
• conflicts, supplier relationships and incentives;
• safe participation and accessibility arrangements; and
• explicit exclusions and an unknown option.

Do not ask for customer names, full order files, payment details or sensitive product information. A synthetic scenario can confirm workflow knowledge without exposing live records.

Recruit transparently

The GOV.UK participant-recruitment guide recommends defining target groups, varying recruitment routes and considering exclusion bias. It is public-service guidance, not a marketplace rule, but the method is useful. Log contact provenance, eligible people, invitations, refusals, bookings, attendance and item completion.

Send a participant sheet before agreement. The government's informed-consent guide covers purpose, collected data, observers, recording, sharing, retention and withdrawal. Research permission stays separate from marketing, sales contact and marketplace messaging permission.

Ask about practical adjustments instead of inferring disability. Offer materials and sessions in usable formats. If a recruiter or transcription service is involved, name it and explain its data role.

Judge whether the sample can answer the question

Create a coverage table by role and qualifying event, not by invented persona. Mark missing populations and contrary cases. A few rich interviews may diagnose a process, but they do not estimate England prevalence or demand.

Stop recruitment if contact provenance is unclear, the screener collects unnecessary data or participants cannot understand the activity. Proceed only when the sample covers the decision owner and the people who perform the actual hand-offs. Report every denominator and limitation when findings are used.