Short answer: yes, and switching between the two is usually just a setting, not a technical project — but it's worth thinking through which one actually fits what you're trying to show before you pick.
What each one actually communicates
Order count tells a story about activity and momentum. Every order ticks it up by exactly one, regardless of size. It's the number that feels the most alive — it moves often, and it's easy to read at a glance, which makes it a natural fit for a shared space where you want a quick, motivating pulse of "things are happening."
Revenue tells a story about outcome. A single large order can move it more than ten small ones combined, which means it more accurately reflects the health of the business, but it also updates less predictably — there can be quiet stretches where nothing visibly changes, followed by a jump.
Neither is more "correct" — they're just answering different questions.
When order count tends to work better
If the counter lives somewhere public-facing — a storefront, a lobby, anywhere customers or visitors might see it — order count is usually the friendlier choice. It's a satisfying number to watch climb, and it doesn't reveal anything about your actual revenue, which some businesses prefer to keep private from customers or competitors.
It also tends to suit teams that want a sense of steady activity rather than a value judgment on order size.
When revenue tends to work better
If the counter is internal — an office, a team space, somewhere only staff see it — revenue often gives a more meaningful sense of how the day or month is actually going. It's also the more natural choice if you're tracking toward a specific goal, like a monthly target.
Switching between the two
If you're using an app to manage the connection, this is typically a single setting rather than anything you need to rebuild. In Flipcounter, it's a dropdown on the settings page — orders or revenue — and the counter updates to match without needing a new URL or any changes on the counter's side.
If you built your own feed, this means changing what value your endpoint calculates and returns — the counter itself doesn't need to know or care which one it's displaying, since it just reads whatever number the feed hands it.
You don't have to pick just one forever
Plenty of stores switch depending on the season or what they're currently focused on — order count during a high-volume launch period, revenue when they're tracking toward a specific target. If switching is easy on your setup, there's no real downside to changing it whenever it makes sense.
Still deciding what period it should cover alongside this — today, this week, this month? That's a separate setting worth thinking through too, and it's covered in how the connection works from the start.