City Tyres operates in the tyre and automotive products sector in Lubumbashi, DRC, serving retail and wholesale customers. As the group expanded across branches, its accounting environment also had to support multiple locations, high data volumes and teams with very different responsibilities. The project focused on one core goal: centralize Tally access without giving every user the same level of visibility or control.
1. Business Problem
City Tyres had a multi-branch operating structure with users working from different locations. Sales, operations, warehouse, accounting and audit teams all needed access to Tally-related information, but they did not all need access to the same data. At the same time, the volume of accounting data was high, making performance, concurrency and day-to-day management important parts of the solution design.
- Multiple branches needed to work around a centralized accounting environment.
- Multiple users across locations needed simultaneous access without making the process difficult to manage.
- Sales, warehouse, accounts, audit and operations teams required different levels of access.
- High transaction and data volumes had to be considered when sizing the environment.
- Management needed a clearer way to see the necessary information from one administrative view.
2. Old Setup
With multiple branches, users and departments to manage, City Tyres was handling a large volume of accounting data. This made it increasingly difficult to manage operations efficiently and provide seamless access to Tally across the business.
- Accounting activity was spread across a multi-location operating structure.
- Different teams depended on the same business data but needed different access boundaries.
- The amount of data and transaction activity made performance planning important.
- The client wanted to centralize work instead of continuing with a difficult-to-manage distributed process.
3. Our Assessment & Recommended Solution
Before recommending an architecture, Tally Experts assessed how City Tyres was operating across its branches, teams and users. The review considered business footfall and operational activity, transaction and data-entry volume, the amount of data being handled, the teams requiring access, expected multi-user concurrency, branch-wise and user-wise security needs, and the admin’s requirement for centralized visibility.
Based on these requirements, we evaluated Tally Server and Tally on Cloud rather than selecting a solution by default. For City Tyres’ distributed, multi-user environment, we recommended Tally on Cloud on a dedicated cloud server with multi-user access and controlled permissions. This approach aligned with the client’s need for centralized working, concurrency, speed, data security and easier access management across branches and departments.
4. Why Cloud?
A key design decision was whether City Tyres should use TallyPrime Server Edition setup or move to Tally on Cloud services. Rather than treating either option as universally better, we evaluated the choice against City Tyres’ actual operating model.
Because the business had multiple branches, distributed users, high data volume and a strong need for centralized access, a dedicated cloud environment was selected as the more practical fit for this requirement. It allowed the Tally environment to be centralized while authorized users could connect from different locations and work concurrently.
What we assessed before selecting the architecture
- Business footfall and operational activity.
- Transaction volume and the amount of data users needed to feed into Tally.
- The number and type of teams requiring access.
- Concurrency and performance expectations for multiple users.
- Branch-wise, user-wise and department-wise security requirements.
- Administrative reporting and visibility requirements.
This requirement-first assessment helped avoid choosing infrastructure based only on product labels. The solution was sized around how City Tyres actually worked.
5. Implementation
Dedicated Tally on Cloud environment
We implemented Tally on Cloud on a dedicated cloud server for City Tyres. The dedicated environment was intended to support the client’s high data volume, multiple users and need for a responsive multi-user experience. Tally multi-user access was configured so authorized users could work in the centralized environment with concurrency across the business.
Multi-user access across branches
The solution was designed around distributed usage rather than a single-office workflow. Users from different branches and teams could access the centralized Tally environment according to their assigned permissions, helping City Tyres move toward its objective of centralizing work.
Branch-wise and user-wise security
We implemented TallyPrime customization and security controls so access could be limited by branch, user and business role. Instead of allowing every user to see everything, permissions were aligned with the information each team needed for its work.
| Team / Role | Access approach implemented |
|---|---|
| Sales | Access limited to sales-relevant information. |
| Warehouse | Access aligned with warehouse responsibilities. |
| Accounts | Accounting access based on assigned responsibilities. |
| Audit | Controlled access for review and audit requirements. |
| Operations | Access limited to relevant operational information. |
Single-screen administrative visibility
For administration and oversight, the required information and data were brought together into a single screen for the admin. This reduced the need for management to depend on multiple disconnected views when checking the information relevant to overall control.
6. Access, Backup & Security
Access
The centralized cloud setup gave authorized users a common Tally environment that could be accessed from their respective locations. Multi-user concurrency was a core part of the implementation, allowing different departments to work without the solution being tied to a single user or a single branch workflow.
Security
Security was implemented around the principle that users should only access the data they are supposed to see. Branch-wise, user-wise and role-based restrictions were used to separate access for sales, warehousing, accounts, audit and operations. This gave City Tyres more controlled data visibility while still supporting cross-branch collaboration in the same centralized environment.
Backup and business continuity
Moving the working environment to a dedicated cloud server centralized the Tally data location and reduced dependence on a single branch computer for day-to-day access. That makes backup administration and recovery planning easier to manage from one environment. However, the project information supplied for this case study does not specify the actual backup schedule, retention policy, secondary copy, redundancy design or restore-testing process, so no specific backup claim has been added.
7. Measurable Outcome
| Area | Challenge | Outcome after implementation |
|---|---|---|
| Centralization | Multiple branches and teams needed a common accounting environment. | Tally access was centralized on a dedicated cloud server so distributed users could work in one controlled environment. |
| Multi-user working | Several users and departments needed access across locations. | Tally multi-user access and concurrency provided a simpler shared-access model for authorized users. |
| Access control | Not every team should see the same information. | Branch-wise, user-wise and role-based permissions limited visibility according to responsibilities. |
| Performance planning | The client had high data volume and substantial transaction activity. | The solution was designed on a dedicated cloud environment after reviewing workload, data feeding and usage requirements, with speed as a key objective. |
| Management visibility | Administration needed necessary information in a clearer consolidated view. | Relevant information was made available to the admin through a single-screen view. |
Overall, City Tyres moved toward the centralized working model it wanted: a dedicated Tally on Cloud environment with multi-user access, controlled departmental visibility and an easier way for management to oversee the accounting setup across branches.
8. Talk to Tally Experts
If your business has multiple branches, distributed teams, high Tally data volumes or users who should not all have the same access, the first step is to assess the operating requirement before choosing between Tally Server and Tally on Cloud. Tally Experts can review your user count, locations, transaction volume, data size, concurrency, security and backup expectations and recommend a practical setup.
Need help centralizing Tally for multiple branches? Discuss your TallyPrime requirement with Tally Experts.
9. Frequently Asked Questions
What problem did City Tyres solve with Tally on Cloud?
City Tyres needed to centralize accounting across multiple branches and users while handling high data volume and giving departments different levels of access. The solution combined a dedicated cloud server, Tally multi-user access, concurrency and role-based security.
Why was Tally on Cloud chosen instead of Tally Server for City Tyres?
Tally Experts evaluated both approaches against the client’s operating model. Because City Tyres had distributed branches, multiple teams, high data volume and a strong need for centralized remote access, a dedicated Tally on Cloud environment was selected for this requirement.
