Run Your Card Fair Table Booking Without First-Come Chaos

It's 9pm on Wednesday and you post next month's table map in the Telegram group. By 9:01 there are 60 replies. Two vendors both typed "T7" in the same second, one regular says he messaged you privately last week, and a new seller asks why the corners are always gone before she sees the post.

Then comes Friday. Four tables are "claimed" but unpaid, and nobody knows if they're free.

That's the first-come scramble, and almost every small card fair starts with it. It rewards whoever has notifications on, then leaves you to sort out the arguments by hand.

This post is about your card fair table booking: how to give out tables fairly, how long to hold one while a vendor pays, when to release it, and what to tell vendors before the release so nobody feels cheated. It goes deeper on one part of our guide on how to run a trading card fair. Most of this works with a Telegram group, a Google Form and PayNow.

Why Does Your Card Fair Table Booking Turn Into A Race?

It turns into a race because a chat message is treated as a booking, and a chat can't stop a second claim, check who paid or mark a table as gone. It fails in three ways.

Double Claims

Two people post "T7" within a second. Whoever you give it to, the other one thinks you picked a friend.

Unpaid Holds

A claim costs nothing, so people claim first and think later. Some never pay, and the table sits in limbo while vendors who would have paid move on.

Favoritism Complaints

Regulars message you privately, you reserve something as a favor, and the public post goes out with the best tables gone. Even with good reasons, it looks like a back room.

Our verdict: keep first-come if you like it, but give it a proof of order, a deadline and published rules.

Which Way Of Giving Out Tables Is Fairest?

The fairest method is the one that matches how much demand you have: first-come is fine when supply beats demand, and a ballot or a priority window is fairer once more vendors want tables than you have. Here's how the common methods compare.

Paid priority isn't hypothetical. The Singapore Card Show's vendor page says applicants who opt for Booth Selection, at S$100 per booth, get priority on a first in time basis, that each applicant is limited to 6 booths, that applications are only processed once full payment is received, and that allocations are confirmed by WhatsApp Singapore Card Show, Vendor Applications. Notice what that does: no money, no place in the queue, so unpaid holds can't exist.

You can mix methods.

Our pick: below 30 tables with steady demand, a returning-vendor window plus first-come with a payment deadline is enough. When a release sells out in minutes, add a ballot after the window, or use a map with holds.

How Long Should You Hold A Table While A Vendor Pays?

Hold a table for as long as paying actually takes: 20 to 30 minutes if the vendor is paying right then by PayNow, and no more than 24 hours if you're collecting by message. A hold is a promise to one vendor and a "no" to everyone else, so keep it short.

Two numbers do the work:

• The hold time is how long a picked table is reserved before it's paid. On a map with holds, minutes. In a chat, you can't enforce minutes, so you set a deadline instead.
• The payment deadline is the point where an unpaid table goes back on offer. We'd use 24 hours for a monthly fair and 48 hours for a big yearly one where vendors may need to check with a partner.

Write the deadline as a time, not a duration. "Pay by 9pm Thursday" ends arguments. "Pay within a day" starts them.

A table counts as booked when the money is in your account, not when a screenshot lands in your DMs. Checking proof against your bank is its own job, and our guide on collecting booth fees covers it.

Honestly, a 24-hour deadline you enforce beats a 6-hour one you don't.

What Should You Tell Vendors Before The Release?

Tell vendors every rule of the release before it opens, in one pinned post: when, how, how much, how many and what happens if they don't pay. Changing a rule mid-release is how favoritism complaints start.

Your pinned post should cover:

1. The date and time the release opens, with the time zone if vendors travel in.
2. The method: ballot, returning-vendor window, first-come or a booking link.
3. The map and prices for each table type, corners included. Our guide on pricing tables and booths works through the numbers.
4. The cap per vendor, for example 2 tables each.
5. The payment deadline and how to pay.
6. What happens to unpaid tables: released to the waitlist, in order.
7. The cancellation rule: whether a vendor can get money back or hand a table to someone else.
8. Where to ask questions, so they don't land in 40 private messages.

Conduct rules, like authenticity and buying from minors, belong in your written card fair vendor rules, not the release post. Link them so vendors accept both.

If you keep a first-come release in Telegram, turn on Slow Mode for the release hour. It limits each member to one message per interval you choose, which stops one vendor flooding the chat with ten table numbers Telegram, Silent Messages and Slow Mode.

If a vendor can read the pinned post and know exactly what will happen to them, you've done it right.

How Do You Release Unpaid Tables And No-Shows?

Release an unpaid table the moment its deadline passes, and offer it to the next vendor on the waitlist with a shorter deadline. Don't wait for an excuse, and don't send a reminder after the deadline. Send one before it.

A simple release routine:

1. 2 hours before the deadline, post or message a reminder.
2. At the deadline, mark unpaid tables as free in your sheet and in the group.
3. Offer each one to the waitlist in order, with a 12-hour deadline.
4. Repeat until the waitlist is empty, then open the leftovers first-come.

A waitlist is the list of vendors who missed out, in the order they joined or were drawn. Post it so vendors can see where they stand.

Day-of no-shows are different, because the money is usually paid. Put a rule in the release post, like "a table not set up 30 minutes after vendor load-in closes may be given to a walk-up vendor, and the fee isn't refunded". For a monthly fair, a vendor who no-shows without a message also loses the returning-vendor window next month.

Releasing feels harsh the first time. It's also the only thing that makes your deadline real.

Walkthrough: A 24-Table Monthly Trade Fair In A Game Store's Function Room

Here's an invented example with illustrative numbers. A game store runs a trade fair on the last Saturday of each month in its 24-table function room, and books every table through a Telegram group of about 500 members.

The old way. The map goes up on a Wednesday evening and all 24 tables are claimed in four minutes. By Saturday, 5 are still unpaid, two vendors argue over a corner, and a new seller posts that "it's always the same people".

The new rules, pinned two weeks before.

• Tables are S$35, corners S$45, 2 tables per vendor at most.
• Last month's vendors who paid and turned up get a 48-hour window from 8pm on Monday.
• Everything left goes to a ballot. A Google Form is open Wednesday to Friday, and the organizer draws names on Saturday at 8pm with a random number generator, then posts the drawn order.
• Winners choose a table in drawn order and pay by PayNow by 9pm Sunday.
• Unpaid tables go to the next names on the list, with 12 hours to pay.

What happened. 17 regulars rebook in the window, taking 18 tables. 6 tables are left, and 31 vendors enter the ballot. The first 6 names pick tables; 5 pay by Sunday, and table 22 goes to name 7, who pays the next morning. The other 24 entrants keep their place on the waitlist for no-shows.

The result. Every table is paid 5 days before the fair, and the draw order is public, so nobody can say the corners went to friends.

Where it still strains. Picking in drawn order takes an evening of messages. At 24 tables that's bearable. At 50, we'd move to a map where each vendor picks and pays in one go.

That's the case for a booking tool, and BookASquare is one way to do it. A vendor taps a table on the map, and pressing Continue holds it on the server for 20 minutes while they pay; the database refuses a second sale of the same table. A password-protected vendor link can run the returning-vendor window.

To be clear about limits: BookASquare doesn't run ballots or waitlists for you. You'd still draw names yourself and send the winners the link. And if your fair is 15 tables of people who all know each other, a pinned message and a spreadsheet are honestly enough.

What To Do Next

Write your release rules before the next map goes up: the method, the cap, the payment deadline and the release routine. Pin them, and point to them whenever someone asks for a favor.

Then run one edition with those rules and watch what breaks. If it's the speed, add a ballot. If it's double claims and unpaid tables, a map with holds solves both, and BookASquare is free to register.

See how table booking works for trading card fairs