What the orders and revenue screens on the iOS app are good for
The same dashboard numbers on a smaller screen. What you can genuinely decide from your phone, and what still needs the full view at a desk.

On a train, in about four seconds, the revenue screen tells you a number. The question nobody asks is what you are supposed to do with it. Most of the time the answer is nothing, and that is not a criticism of the screen. Orders and revenue on the store.fan iOS app are built for two different jobs, and mixing them up is why some creators check their phone forty times a day and still get caught out by a parcel they forgot to post.
Two screens, two completely different jobs
An order is a promise with a name attached. Someone paid for something, and depending on the product type you owe them a file they already have, a slot in your diary, a parcel you have to take to the post office, or access to a community. Reading that on a small screen is perfectly adequate, because you are not comparing anything. You are asking: what does this person need, and when.
Revenue is the opposite. A number with nothing beside it invites a story, and the story you tell yourself on a Tuesday afternoon is usually wrong. Two hundred pounds is a good day if it came from ninety views and a bad day if it came from nine hundred. The phone gives you the figure long before it can give you the context, and that gap is where the anxious checking habit is born.
The genuinely awkward part is that both screens feel equally urgent when they buzz. They are not. One has a clock on it and one does not.
Waiting for the desk, against having it in your pocket
The point of a phone view is not to do everything. It is to stop a small thing from turning into a late thing.
| Waiting until you are at a desk | With the app in your pocket |
|---|---|
| Find out about a booking the evening before it happens | See it the day it lands, while the diary can still be rearranged |
| Discover a physical order after the day's post has gone | Catch it in the morning and put it in today's post |
| Answer a buyer question two days later | Send a two-line answer while the question is still warm |
| Look at revenue once a week and read too much into it | Glance daily, note the odd day, investigate it properly later |
| Wonder whether an announcement did anything | See whether orders arrived in the hours after you posted |
| Carry a vague feeling that something is unhandled | Reach the end of the orders list and know that it is not |
What to actually do on each screen
Read the orders screen with a question in mind. Read the revenue screen with a threshold in mind.
- 1Orders: for each new one, name the promise. Digital download means nothing to do, since delivery is instant and the buyer has a private order page they can come back to. Booking means check the diary and the answers they gave on the order form. Physical means an address, a delivery fee you set, and a trip to the post office that only you can make.
- 2Orders: deal with the parcel first if there is one, because it is the only item on the list that is affected by what time of day it is.
- 3Orders: if a booking arrived with an empty or confusing brief, message the buyer now. This is the highest-value minute in the whole routine.
- 4Revenue: decide in advance what counts as surprising. Roughly double a normal day, or roughly nothing for three days running. Everything between those is weather.
- 5Revenue: when a day is surprising, do not analyse it on the phone. Write one line about it and look at the product-level view later, with views, buyers and traffic source beside the money.
- 6Revenue: never compare today to your best day. Compare a window to the same length of window, which is a thing the desk is for.
A worked example, on a Thursday
You look at the app at nine in the morning. Revenue for yesterday reads roughly triple a normal day, which trips your surprise threshold immediately. The temptation is to spend twenty minutes on the train working out why. Do not. Note it and open orders instead, because that is where anything that needs doing lives.
Orders shows eleven, and nine of them are the same $19 digital product, which already answers half the question: something you posted travelled. Two of the nine also bought the $49 pack, which is more interesting than the spike itself. There is one booking and one physical order, so your actual jobs are to check Thursday's diary and to post a parcel. That is the whole phone task, done in six minutes. That evening, at the desk, you open per-product analytics and see the traffic source that carried it, which tells you whether it is repeatable or whether someone with a large audience mentioned you once. Only one of those is a plan.
If you have ever found out about an order too late to do anything about it, store.fan gives you orders, messages and revenue on your phone, with payments going straight to your own Stripe account.
Open a free storeThe mistake most people make
The mistake is using the revenue screen as a mood regulator. It is available, it is one tap away, and it gives a different answer every few hours, which is exactly the shape of thing a restless mind will keep returning to. The cost is not the minutes. It is that a number checked eleven times a day stops meaning anything, and you lose the ability to be surprised by a genuinely unusual day. Give revenue one look per day, at the end of your check, and put the real reading in a weekly slot where views and buyers are sitting next to it. If you want to see how the money side is structured before you commit to anything, the payments page covers it plainly.
It is what buyers paid. store.fan charges no platform fee on Free, Starter or Pro, but Stripe's own card processing fees apply and are settled in your Stripe account, which is also where payouts are scheduled.
You can see the order and the full delivery address the buyer entered at checkout, and you can message them. The posting is yours to do: store.fan never touches the parcel and does not create carrier labels or tracking.
Yes, it is the same store. The difference is space rather than data, so the deeper comparisons, longer windows and side-by-side product views are more comfortable on a full screen.
By looking at traffic source for the product afterwards. A spike from a channel you control is something you can do again. A spike from someone else mentioning you is a gift, and planning next month around it is how people end up disappointed.
Treat orders as a list you finish and revenue as a signal you note. That single distinction turns the app from a source of low-level worry into the thing that stops parcels going out late and bookings arriving as a surprise. Everything else can wait for a proper screen and a cup of tea.
Start a store, put your first product up, and get every order on your phone from the day it sells.
Sign up freeTurn your knowledge into income
Launch your Store.Fan in minutes — sell digital products, courses, and calls straight from your bio. Free to start.



