Client account management
Manage client records, contacts, relationship stage, account health, priority, active projects, active routes, and buyer portal access from the seller workspace.
Codefy ERP Module
Client accounts, projects, and buyer visibility in one workspace
Give every client a controlled buyer portal while your team manages accounts, transportation, product, and service projects, approvals, invoices, and service proof from the same data.
Client accountsProjectsBuyer portalApprovals
Operating Chain
One client flow from account setup to buyer-side review
Client work becomes difficult when account records, project scope, participants, delivery proof, incidents, invoices, and approvals are split across disconnected tools. Codefy ERP keeps the seller workspace and buyer portal aligned.
Step 1
Create client
Step 2
Open project
Step 3
Define scope
Step 4
Add participants
Step 5
Deliver service
Step 6
Review proof
Step 7
Approve billing
Client Workflows
Built for client-facing work across transportation, products, and services
The module supports transportation operations without limiting every client relationship to transport. Product and service projects can sit beside routes, trips, riders, invoices, incidents, and buyer-side review.
Multi-type projects
Run transportation, product, and service projects with the right scope, status, participants, billing context, delivery details, and operational history.
Buyer portal visibility
Give clients a controlled branded portal for dashboard summaries, projects, routes, schedules, employees or participants, trips, fleet tracking, incidents, notifications, and invoices.
Review, approval, and billing
Support client-side service review with trip review, invoice approval, overdue visibility, controlled price visibility, payment review, incidents, and notifications.
Smart Logic
Client visibility should follow the project scope, not expose the whole ERP
Codefy ERP separates internal workspace control from buyer-facing access. Client portal users see only the projects, prices, invoices, operations, incidents, and notifications they are allowed to see, while internal teams keep full account and project control.
Client Relationship and Account Control
Keep client account records useful for sales, operations, finance, and support instead of treating the client as only an invoice name.
Client records with contacts, stage, priority, health, and status
Active projects, route counts, and portal user counts
Account-level follow-up context for commercial and operational teams
Bulk client management and safe delete workflows
Multi-Type Project Workspace
Manage transport, product, and service projects from one project workspace while allowing each project type to carry its own operating context.
Transportation, commerce, product, and service project scope
Project details, status, start and end dates, billing context, and participants
Project routes, items, sales/order context, and service scope where relevant
Bulk edit, sharing, publishing, and project-level review paths
Transportation Project Operations
For transport projects, connect the client account to routes, schedules, employees or riders, seat assignments, on-demand bookings, trips, live tracking, fleet tracking, attendance, and incidents.
Routes and schedules visible in the seller workspace and client portal
Client employees, rider records, and seat assignment control
On-demand eligibility, bookings, and trip review context
Live attendance, trip tracking, fleet tracking, and service proof
Product and Service Project Context
Support client work that is not transportation-only, including product items, service scope, delivery context, review states, pricing visibility, and invoice flow.
Product and service project records beside transportation work
Project items, product/service context, and delivery or fulfillment notes
Client-side review and approval surfaces for delivered work
Invoice and balance context tied back to client and project records
Buyer Portal Dashboard
Give clients a controlled dashboard that summarizes operational attention, live work, upcoming activity, invoices, balances, notifications, and project footprint.
Active projects, routes, schedules, employees, and assignments
Pending invoice approvals, overdue invoices, and visible balances
Unread notifications, open incidents, and attention signals
Upcoming activity and operational match indicators
Client Employees, Participants, and Contacts
Handle the people connected to the client relationship without mixing buyer-side participants with internal tenant staff.
Client employees and rider records for transportation projects
Participants and contacts for broader product and service work
Seat assignments and project participation context
Clear boundary between client portal users and internal system users
Trips, Delivery, Service Review, and Operational Proof
Let buyers inspect the proof that matters for their project type, from transport trips and attendance to delivery or service review context.
Trips, tracking, live attendance, and analysis for transport projects
Calendar and day-detail review for planned activity
Service review and operational proof tied to the project
Client-side review paths without exposing internal operations screens
Incidents, Notifications, and Approvals
Keep client-facing exceptions visible and actionable, with incidents, notifications, penalty requests where allowed, and approval states connected to the portal.
Client portal incidents and seller-side notifications
Penalty request context for incident follow-up where enabled
Unread notification and attention counts
Approval-ready review for service and billing workflows
Invoices, Balances, Pricing Visibility, and Payment Review
Connect the buyer portal to invoices, approvals, overdue balances, payment review, and price visibility while keeping sensitive commercial access controlled.
Invoice list, invoice details, and client-side approval
Pending approval and overdue invoice visibility
Controlled price visibility by portal permission
Balances and payment review context where enabled
Portal Users and Access Boundaries
Protect the ERP by keeping buyer portal users separate from tenant staff and system-user permission management.
Client portal invitations and account controls
Buyer portal users kept separate from internal staff access
Project-scoped access validation for portal routes and data
Minimal client-facing DTOs for portal screens
Screens
Show both sides of the client relationship
The module needs one internal workspace for account and project control, plus one buyer portal surface for controlled client-side review across transportation, products, services, invoices, incidents, and approvals.
Client workspace
Client and project command center
A seller-side workspace for client accounts, relationship health, active projects, transport scope, product/service context, portal access, incidents, and invoices.
Buyer portal
Controlled buyer-side visibility
Clients can review projects, routes, schedules, employees or participants, trips, fleet tracking, incidents, notifications, invoices, balances, and approvals from a controlled portal.
Commercial Value
A module that connects client control with client-facing proof
Client accounts and projects stay connected to delivery.
The same client records support account management, transportation operations, product and service projects, participants, incidents, invoices, approvals, and portal access.
1
Commercial teams manage client relationships, health, follow-up, active projects, and portal access from one account foundation.
2
Operations teams can run transportation projects without losing routes, riders, seat assignments, trips, attendance, live tracking, fleet tracking, incidents, and service proof.
3
Delivery teams can keep product and service projects visible beside transport work, with scope, participants, review, pricing, invoice, and approval context.
4
Clients get a controlled buyer portal that exposes the right projects, operations, incidents, notifications, invoices, balances, and approvals without exposing internal ERP data.
Start with the client workflow that needs cleaner visibility first
We can review your client accounts, project types, buyer portal needs, participant records, operational proof, incident workflow, invoice approval, and access boundaries, then map the right Codefy ERP starting point.