Revenue, and what it is doing per minute
Tonight’s takings, with dollars per minute and a projected hourly figure underneath. The projection is the useful half: it answers whether the third hour is worth staying up for.
The show is running and you are not on the mic. Open it in a browser and watch.
The live console is the whole show on one screen: revenue and pace moving as sales land, the pulse of viewers and bids, the funnel from watching to buying, the chat with a box to answer it, and a scoreboard of what each host has sold tonight. It is the seat for whoever is running the show rather than performing it.
The numbers, while you can still do something about them
Five readouts across the top of the console, each with its own trend line, each one clickable for the detail behind it. They move on the live connection as events land, not on a refresh button and not on a timer.
Sales and average order
How many items have gone, with the average sale beside them. A high count next to a low total tells you something a revenue figure on its own hides.
Bids per minute
The room’s temperature as a rate rather than a total. It turns before revenue does, which is what makes it worth a card of its own.
Viewers now, and peak
Who is watching this second, against the highest the show has reached. The gap between the two is the audience you have already lost tonight.
Hourly pace
Earnings expressed as dollars per hour, with items per hour beside it. This is the number that decides how long a show should run.
It says "collecting" instead of zero
For the first minutes of a show there is not enough data to be honest with. The cards say so rather than showing a confident $0 that reads like a failure.
The shape of the show, not just the total
A total tells you where you ended up. These tell you how you got there, and they are the reason the console is a place you look during a show rather than after one.
Show pulse
One chart carrying viewers, bids, and cumulative revenue together, with a marker at every sale. Drag a range and the rest of the console follows it, so you can ask what happened in the ten minutes the room went quiet.
Conversion funnel
Viewers, then chatters, then bidders, then buyers, as bars you can compare at a glance. A wide top and a narrow bottom is a different problem from a narrow top, and the funnel is where you tell them apart.
Lots tonight
Every lot ranked by what it brought in, with its bid count. Click one for its bid timeline and who won it.
Dead-time meter
A live count of how long it has been since anything sold, against the gap that counts as too long for your show. Dead air is the quietest way a show loses money and the easiest to miss from behind the camera.
Click any number for its detail
Every card opens into the working behind it rather than being a figure you have to trust. Progressive disclosure is the whole design: clean surface, depth on demand.
Your team, and who is actually selling
This is the half that makes the console worth opening for a shop rather than a solo seller. One show can run all day with the mic passing between people, and the console keeps score of it as it happens.
Per-host scoreboard
Each host with their sales, their attributed revenue, their share of the night, and a marker on whoever is on camera right now. It is the answer to "who had a good night" without anybody exporting anything.
It updates the moment the mic moves
Switch hosts from the extension and the console re-reads the ledger on its own. Nobody refreshes, and nobody is looking at last host’s numbers under this host’s name.
Sales that cannot be attributed are shown, not dropped
If a sale lands where the handover record cannot place it, it goes into its own bucket in plain sight. A leaderboard that quietly discards its awkward rows is worse than no leaderboard.
Time on camera, and host against host
A separate host-performance view puts each host’s airtime beside what they sold in it, so a big total earned over four hours is not confused with a big total earned in one.
The room, and talking to it
The console carries two conversations at once: the one with your audience, and the one with your team. They are deliberately not the same window.
Live viewer chat
Whatnot chat as it arrives, with host and moderator messages marked so the people running the room stand out from the room.
Post to the chat from the browser
A compose box under the log, so whoever is managing can drop a link or answer a question without taking the phone off the host. It needs your show on air and the extension open, and it says which one is missing rather than failing quietly.
Who is actually talking
Messages per minute, distinct chatters, and the night’s top chatters with badges for the ones who also bid or bought. A loud room that never bids is a different night from a quiet room that does.
Team chat, kept separate
A conversation between whoever is managing and whoever is on the mic, stacked below the audience chat. It stays after the show ends, because a team thread should outlive the broadcast.
Controls that reach the show
The console mostly watches. Where it does act, it acts through the same path the extension uses, so nothing here is a second implementation that can drift.
The automation queue, with a pause button
Tips, raids and callouts line up server-side with a ticking estimate for each. Pause the whole queue, resume it, skip whatever is running, or clear what is waiting. Automation you cannot stop mid-show is not automation you can trust.
A countdown on whatever is running
The active callout shows how long it has left, matching the countdown the host sees in the extension. Two screens, one truth.
The product drawer is a list, for now
You can see what is loaded into the show with prices, quantities, and what is running. The run, pin, and auction controls are visibly switched off and labelled as not ready, rather than being present and doing nothing when you press them.
What it needs to work
Four straight answers, so nothing here is a surprise on the night of your first show.
It is part of the Whatnot app, not a separate purchase
The console lives inside LiveStreamPro’s Whatnot app. Your plan has to include Whatnot and your Whatnot account has to be connected. Without either, the app sends you to connect one rather than showing an empty console.
The extension has to be running
The console is a window onto a show the extension is watching. The extension is what sees your Whatnot show, so with the show tab closed the console has nothing to report and posting to chat is refused with the reason.
It opens from your shows, not from a bookmark
Open Console sits on each show in your list, and Open Live on each running stream. You do not need to keep a URL anywhere.
It works after the show ends
A finished show keeps its console. The numbers stop moving, the chat becomes a replay, and the team thread stays open, so the post-show conversation happens where the evidence is.
Common questions
Do I need a second screen for this?
It helps, and plenty of sellers run it on a laptop beside the phone they broadcast from. It is not required. The console is most useful to whoever is managing the show rather than holding the mic, which is often not the same person.
Is this the same numbers as the extension panel?
Same source, more room. The extension bar rides along with the show in a narrow strip and shows what fits there. The console has a full browser window, so it can carry the charts, the funnel, the per-host scoreboard, and the chat at once.
Can I run the show from the console?
Partly, and we would rather be specific than flattering. You can post to the chat, and you can pause, skip, or clear the automation queue. The product controls in the drawer are switched off and labelled as not ready yet, so today the console is where you watch and talk, and the extension is where you push products.
How does it know which host made a sale?
Every sale is stamped with whoever held the mic at the moment it landed, and the scoreboard replays the handover timeline over the night’s orders. Switching hosts in the extension is what moves that pointer, and it does not end or restart the show.
What happens if my connection drops?
The console shows that its live connection is down rather than leaving stale numbers looking current, and it reconnects on its own. Anything the extension captured while you were offline is queued and replayed, so the record catches up even if the screen was behind for a minute.