Wholesale customers
- Log in through the dedicated wholesale entry.
- Browse the authorised product catalogue and prices.
- Submit an order without staff entering it for them.
- Return to check order progress.
Let customers complete the next step themselves
tPanel develops custom client and customer portals for Australian businesses. A portal gives external users a login and a defined set of tasks, while your staff control what they can access and what needs approval.
The starting point is a customer workflow: a buyer placing an order, a client checking progress or a customer submitting information. We agree the users, access rules and connection to your internal process before designing screens.
Check whether your existing software already provides a suitable customer area. Custom development makes sense when its access rules, approvals or system connections leave important gaps.
Everau: a dedicated portal for wholesale buyers
tPanel developed a wholesale feature for Everau with a dedicated customer login. Buyers see the product list and prices made available by an administrator, place orders themselves and view order progress.
Explore the Everau project →Background: AI-generated wholesale environment, not Everau’s premises.
Everau administrators
- Control which products and prices customers can access.
- Review submitted orders.
- Approve or reject an order.
This is a delivered workflow described by the tPanel project team. The portal functionality is distinct from the order hub’s channel and warehouse connections, documented in the Everau case study.
Log in
The wholesale buyer enters the dedicated customer area.
Choose products
The buyer sees the catalogue and prices available to them.
Submit for review
The buyer places an order; an administrator can approve or reject it.
Check progress
The buyer can return to the portal to view the order’s progress.
Define the customer task and the staff handover
The Everau build demonstrates wholesale ordering. Other portal workflows need their own scope; the examples below describe what to discuss, rather than additional claims about that project.
- Requests and progress
- Decide what a customer can submit, what status they can see and which staff member owns the next step. Link it to the actual work record.
- Documents and approvals
- If files or approvals are needed, agree who can upload, view, replace and approve each item. Set the access and retention rules before building.
- Orders and account information
- Agree product visibility, prices, order submission and admin review. Payments, invoices and changes after submission each need a separate scope decision.
A clear next step
An accountable decision
A self-service order
Access rules belong in the first release
Write down what a customer, a customer’s colleague and your own staff can see and change. Agree whether access follows an individual account, a company, a product entitlement or an assigned request.
The implementation and tests must enforce those rules on the server as well as in the interface. A hidden button alone does not establish a permission boundary. The storage model and customer isolation approach are agreed for your system.
- Account lifecycle: agree invitation, sign-in, password recovery and access removal.
- Record visibility: verify access with different customer and staff accounts.
- Admin decisions: define who may approve, reject or change a record.
- Exceptions: check what happens when a submission is incomplete, repeated or no longer permitted.
These are requirements to agree and verify for a new portal. They do not imply a specific authentication method, hosting architecture or certification for the Everau implementation.
Connect the portal to the team’s existing work
A useful portal connects a customer action to the system staff use to respond. Agree where customer details, product information, orders and progress are maintained, and what happens if an update cannot be delivered.
For sales records and follow-up, see custom CRM development. For the employee side of requests and approvals, see internal business systems.
System integration covers API access, mapping and recovery. If the workflow continues into warehouses and delivery tracking, e-commerce integration covers that part of the project.
Customer-facingYour portal
Requests · Orders · Progress
Agreed rulesSystem integration
Access · Mapping · Recovery
Team-facingYour business systems
CRM · Operations · Orders
Scope one complete self-service journey
Start with a customer task that reaches a useful outcome and includes the staff response. A login screen on its own is not a complete first release.
- Agree the scope
- List the user groups, visible records, customer actions, admin decisions and connected systems. Identify what stays in existing software.
- Test the journey
- Use representative customer and staff accounts. Check a successful submission, a rejected request, progress visibility and access boundaries on desktop and mobile.
- Plan the handover
- Agree account administration, data imports, training, hosting, monitoring and who handles customer support after launch.
Budget and delivery dates follow the scope
We quote the portal after reviewing the workflow and integrations. There is no single package price or standard delivery date for every portal. Identify GST, hosting, third-party services, migration and ongoing maintenance separately in the budget.
You own the agreed source code and IP. You can arrange your own hosting and maintenance, or discuss tPanel’s optional managed software plan. Mobile apps, payment collection and additional workflows are included only when agreed in the scope.
Client portal questions
Start with who will log in and the task they need to complete.
What is the difference between a client portal and an internal system?
A client portal gives external customers access to defined actions and information. An internal system supports your staff. The two can share a workflow, with different permissions and screens for each group.
Can a portal support wholesale ordering?
Yes. In the Everau wholesale build, customers log in, view admin-authorised products and prices, place orders and check progress. Administrators can approve or reject submitted orders.
Can different customers see different information?
Access rules are part of the scope. We agree what each customer or company can see and test those boundaries with representative accounts. Product access, shared company records and administrator permissions need explicit rules.
Do we need to replace our CRM or website?
Not necessarily. A portal can connect to existing software where suitable interfaces are available. We review the data, permissions and integration limits before recommending the implementation.
Does every portal include payments and file uploads?
No. These are separate scope choices. Include only the actions needed for your customer journey, with the relevant payment, file access and data handling requirements agreed before development.
What should we provide for a quote?
Describe the customer type, what they should see and do, what staff approve, and the systems involved. Include a target date and any access restrictions. Sample workflows are more useful than a long list of unrelated features.
Tell us what your customers need to do
Describe who will log in, what they should see, the task they need to complete and what your staff must approve. We will review the first release and quote with you.
Related services and project evidence
Last updated 19 September 2026 · tPanel Solution