First answer this: who is it for, you or the buyer?
An account area solves one of two problems. Either it takes routine off your plate - fewer "where's my order" calls, fewer "can you resend that invoice" threads. Or it gives the buyer something: history, a discount, access to content they paid for.
If it does neither, the account will sit empty. Easy way to check: look at your last 30 enquiries across chat, messengers and phone, and write down what people actually ask. If half of them are "did my payment go through" and "when is delivery", an account area will pay for itself. If they're questions about stock and picking the right product, what you need is a decent catalogue and search, not an account.
Also look at purchase frequency. Accounts live where people come back: consumables, pet food, cosmetics, spare parts, subscriptions. If someone buys once every three years - a window, a sofa, a ceiling - there'll be nobody to log in.
The required minimum: four screens
This is what an account area is pointless without. Everything else is an add-on.
Notice that none of these needs "functionality". It's just data you already have in your order database, laid out clearly.
- Order list with status and date. Statuses in plain language: "Packing", "Handed to courier", "Ready for pickup" - not "status_3".
- Order detail: what's in it, what was paid, tracking number, link to the receipt or invoice.
- A "Reorder" button - which is also the main reason a customer would come back to the account at all.
- Delivery details: addresses and recipients that get filled into checkout automatically.
What gets added often and almost always wasted
Internal messaging and chat with a manager. Customers will write to whichever messenger suits them anyway. You end up with a second channel to monitor and complaints along the lines of "I messaged you in my account three days ago".
News feeds, blogs, "personal recommendations". Recommendations without behavioural data are just random products. Until you have thousands of orders, the algorithm has nothing to learn from.
A loyalty programme at launch. Points, tiers, expiry - that's not a screen, it's separate logic for earning, spending, refunds and disputes. If you haven't decided yet what earns points and what happens to them when a product is returned, it's too early to build this.
Avatar uploads, colour themes, notification settings with ten checkboxes. Nobody decorates their account at a spare parts store.
A separate mobile app instead of an account area. An app makes sense when someone opens it several times a week. Once a month, and they won't tolerate the icon on their home screen - they'll delete it.
Registration: the main place you lose orders
An account area introduces a mandatory step - registration. Every extra field in it costs you orders, so you build it to the bare minimum, not "just in case".
The approach that works: checkout without registration, and the account gets created automatically from the order using the phone number or email. The customer gets a link and lands inside, where their order is already waiting. That way you're not asking anyone to invent a password before they trust you.
Test the future account on three things: sign-in by code from SMS or email with no password, account recovery in a single action, and usability on a phone held vertically in one hand. Over 80% of visits will come from phones - open the prototype on yours and try to find a tracking number.
How to discuss it with a developer without overpaying
The account area is the easiest place to inflate a quote, because "customer account" sounds like one line item while there are ten screens inside it. Your job is to make them break it down screen by screen.
And ask directly: what can we skip in phase one? A developer who says "you need all of it" either hasn't looked into your situation or is selling hours. A sensible answer sounds like "let's postpone points and recommendations, they won't work at your current order volume".
Ask for the quote as a list of screens and actions, not a single line reading "customer account - total". One line isn't a quote, it's a number.
- Ask for the quote as a list of screens and actions, not one line item. A single line isn't a quote, it's a number.
- Clarify where order statuses come from. If they come from your accounting system or CRM, that's a separate integration, and it usually costs more than the account area itself.
- Ask what the customer sees if the integration goes down. A blank screen with no explanation is worse than having no account area at all.
- Agree on phase two upfront: which sections get added once you have real numbers.
The check-in a month after launch
An account area isn't a one-off purchase, it's a hypothesis. A month in, look at two numbers in your analytics: how many customers logged in at all, and how many pressed "Reorder". If there are almost no visits, the problem isn't the content - it's that you're not giving out the link. Add it to the order email, the SMS and your team's signatures.
The second metric is enquiries. If "where's my order" questions have dropped, the account is working. If they haven't, statuses are updating late or are worded confusingly. That gets fixed with copy, not new sections.
At EFIMOV DEV we build stores and web services on React and Node.js, and we usually start with a minimal account area so you can see real numbers before paying for a loyalty programme. Starting-price ranges for online stores and web services are published on our site; an exact quote comes after the brief, once it's clear where order statuses are coming from.
A good customer account area starts with four screens: orders, order detail, reorder and saved addresses. Add anything else only after your analytics show that people are actually logging in.
Frequently asked
Can we manage without a customer account area entirely?
Yes, if purchases are rare and one-off. Order history and receipts can go out by email and messenger, and status updates as a short message at each stage change. For furniture, renovation or windows that's enough.
Will an account area push the store's price up a lot?
Noticeably, but most of the money usually goes not into the screens themselves but into the link with your accounting system - without it, statuses have to be maintained by hand. Ask for the quote split into the account area and the integration separately so you can see what you're paying for.
Do we need points and purchase-based discounts?
Not at launch. First you need clarity on what earns points, whether they expire, what happens to them on a return, and how accounting sees it. Until those rules exist, the section will just generate disputes with customers.
Is it worth adding sign-in via Google or social accounts?
Sign-in by code to a phone or email is enough - it works for everyone and there's nothing to remember. External logins add a setup step and the risk that someone forgets which account they registered with.