A Customer Portal: What the Account Holder Can See
31 Oct 2026
A tracking portal shows a customer their orders, the status, and documents that belong to them. It does not open another customer account or your internal cost. Submitting an order on a website is not that portal. The difference belongs in the scope so the name is not larger than the function.
A customer calls to ask where the order is, what number it has, and whether the invoice they received is the latest one. Staff search a file or a chat. A portal moves that question to a screen the account holder opens, and they see only what is theirs. It is not an open shop for every visitor, and it is not the accounting program. It is a narrow window onto a record you already keep.
Before design, name what tracking means for you. Some companies want the customer to see orders they sent and a status: being prepared, dispatched, delivered. Others also want a copy of the invoice, or its number, if one was issued. Do not put the whole wish in the first sentence. Every extra document the customer can open is a privacy decision and an accounting decision, not only a button.
What appears inside the account
- A list of orders for this account only, with a number, a date, and a status whose meanings you agreed.
- Line detail they are allowed to see: the item, the quantity, and the agreed price if a price belongs on the order at all.
- An invoice file or its number if you decided to show it, tied to the order, not a company-wide folder.
- A status that does not reveal an internal note: no salesperson comment about margin, and no internal argument.
- A way to ask about one order that carries the order number, not a message box with no context.
The acceptance test that matters more than the logo: a trial account must not see another account orders, and must not see a price that is not theirs if prices differ. Ask for that test by name in the delivery. If it fails, the portal is not merely unfinished in appearance. It is not fit to use.
What to leave out of the first version
- Editing an issued invoice from the customer screen.
- A full statement of every journal line, if the accounting program is the master and you have not agreed what may be shown.
- Any comparison with other customers.
- Downloading every internal attachment on the job.
- Self-service signup with no approval from you, if your work is on known accounts under an agreement.
Who opens the account: you do, after an agreement, or the customer requests one and waits. The choice changes support. Self-service signup brings incomplete names. An account you open is slower and cleaner. You can combine them: a request is possible, and activation waits until invoice details are checked. Do not leave that queue without an owner inside your company, or activation requests sit in an inbox nobody opens.
The invoice on the screen
Showing an invoice means showing a document you accept as belonging to that customer. Whether that document is the electronic invoice required in Egypt is for your accountant to decide, not for ENS. The portal may show a copy of a document that was already issued in the accounting program, or it may show a status and no tax file. Do not build an invoice generator inside the portal on the assumption that every customer must download an electronic invoice. Ask the accountant what the customer is allowed to see, then show that and nothing else.
Submitting an order is not a tracking portal
Laborex is a pharmaceutical and medical supplies company. What was built is a website and an online order-submission system. A visitor or a customer sends an order from the site. That is submission. The published description does not say the customer later signs in to browse past orders and invoices in a portal. Reading the case as a full tracking portal reads more than was written. If that view is what you need, write it as its own function: an account, a list of their orders, and documents that are theirs. A project can start with submission and add tracking once the order number and the status are stable. Promising both before statuses exist shows the customer an empty screen, or a status with no meaning.
Submission without tracking fixes the mess of retyping an order. Tracking fixes the call about where the order is. Both are useful, and they are not the same delivery. One sentence in the scope is enough to separate them: this version receives the order, or this version shows orders after sign-in.
What to send
- Whether accounts are known to you in advance, or the customer opens them.
- The statuses you want shown, in your words, not in generic ones.
- Whether an invoice is a file, or a number only, and what your accountant said about that.
- A real order with anything you do not want to share removed.
- Who inside the company answers a question that arrives from the portal with an order number.
Two questions that change the size
Is the portal also where the order is created?
It can be. Creating the order brings back questions of price, minimum quantity and credit, which is a wider scope than viewing. If the pain today is the call about status, start with viewing orders that you create. Add creation when the statuses are understood. The reverse is right if the pain is that the order arrives as a photo on WhatsApp: then submission comes first, in the pattern of an order sent from a site, and tracking comes later.
Does staff use the same screen?
Staff need more: every account, internal notes, and statuses before they are published to the customer. Do not hand the customer a link to the operations panel and hide buttons by hope. Two entrances, or two clear permissions. What the customer sees is the short list of what you agreed to publish.
The order-submission pattern, not a history portal, is described in the Laborex website and order system. Building the portal sits in custom software development.
Describe what the customer should see a week after the order, via start your project. A voice explanation fits the WhatsApp button at the bottom of this page. The chat arrives with the article as its source, and no phone number is printed here.
