Profit by Salesman, Branch and Project: What Custom Fields and Dimensions Actually Do

A car showroom owner can tell you, to the unit, how many cars he moved this month. Thirty. He knows the total sale value and roughly what he made on it. But ask him a slightly different question, which of his five salesmen actually made him money and which one is just standing on the floor drinking chai, and the confidence disappears. The sale is recorded. The car, the price, the customer, all of it is in the books. The one thing that is not recorded is who closed it. And so the most useful management question in the whole business, which of my people is worth what I pay him, cannot be answered by the system at all.

This is the gap that custom fields and dimensions fill, and it is one of the most under-appreciated features in any ERP. It does not sound exciting next to inventory or tax. But it is the difference between software that tells you what happened and software that tells you where the money is actually coming from and going. For most Pakistani businesses, that second question is the one that matters.

Your books go deep. Your decisions need them wide.

A normal ledger grows in one direction: downward. Every day you add more transactions, more rows, a longer and longer list of what came in and what went out. That depth is fine for accounting. It is useless for decisions, because a decision is almost never about a single transaction, it is about a slice of them. All the sales from the DHA branch. Everything Imran sold this quarter. The full cost of one construction project. The margin on this season’s lawn collection.

To answer those, the books have to grow sideways as well as down. Each transaction needs to carry a little extra context, a tag that says which branch, which salesman, which project, which line. That sideways context is what a dimension is. As one of our clients put it, you keep needing to add dimensions horizontally, because every new way you want to slice the business is one more column of information you wish every entry was already carrying. Add those columns once, and suddenly the same pile of transactions can be cut a dozen different ways without re-entering anything.

What people do instead, and why it quietly fails

Businesses that need this and do not have it always reach for the same two workarounds. The first is paper, a separate register per branch or per salesman. The second is Excel, a separate file for each slice, updated by hand. Both feel like they work, and both carry the same two flaws.

The first flaw is fragility. A spreadsheet can be deleted, overwritten, or quietly edited, and there is no record that it happened. A register can be lost or “adjusted” before it reaches you. The numbers your decisions rest on are sitting in the most deletable, least controlled place in the business.

The second flaw is that they are never live, and never truly comparable. By the time the per-branch Excel files are collected, consolidated and cleaned, the month is over and you are looking at history. And because each file was maintained slightly differently, putting them side by side to compare branch against branch is its own small project every time. You wanted a live, like-for-like comparison; what you got was a stale, hand-stitched one. We see the same pattern with stock and gate movements, where keeping the record outside the system is exactly where things go missing, something we wrote about in why every gate pass should be linked to your inventory.

The same questions, two very different systems

The point of dimensions is not new data entry. It is being able to ask the questions you already care about and actually get an answer.

Where this hits hardest in Pakistan: multiple units

There is one local reality that makes all of this urgent rather than nice-to-have. Most established businessmen in Pakistan do not run one thing. They run several, two or three showrooms, a few retail outlets, a trading arm and a small factory, often under one ownership and one mind. What they want is brutally simple to say and surprisingly hard to find: all of it in one system, with the ability to see each unit on its own and everything together.

Without dimensions, they are pushed into bad choices. Either run a separate accounting file or company for each branch, and lose any single live view of the whole, or pour everything into one set of books and lose the ability to tell the branches apart. Dimensions remove the trade-off. One company, one set of books, every transaction tagged to its unit, and reports that pivot between “just this branch” and “the whole group” on demand. For businesses that genuinely need self-balancing units with their own P&L, that pairs naturally with a proper multi-unit setup, but for many the answer is simply a Branch dimension, switched on in an afternoon.

Standard software, made to feel like yours

Here is the part that changes how a business feels about its software. Off-the-shelf systems force every business into the same fixed shape: the same fields, the same handful of reports, and a memo box where you are supposed to cram everything that does not fit. Custom fields turn that around. You decide what extra information each form should capture, because you know your business and the software does not. A showroom adds Salesman and Model. A contractor adds Project and Site. A clothing brand adds Season and Article. A distributor adds Territory and Route.

Because you defined those fields around how your business actually thinks, the system stops feeling generic. It feels customised, as though it were built for you specifically, even though it is the same standard platform underneath. That is the quiet difference between software a team tolerates and software a team owns. We touched on this as one of the seven things worth judging an ERP on, in our buyer’s guide to choosing ERP in Pakistan: if shaping the software to your workflow needs a developer and a quotation every time, you bought a consultancy, not a product.

How it works in NavoBook

In NavoBook, Custom Fields and Dimensions are exactly that, a setting, not a project. You can add your own fields to the forms you use and define dimensions, such as branch, salesman, project, cost centre, season or anything your business needs, then tag transactions with them as you go. Your reports and profit breakdowns can then be filtered and grouped by any of those dimensions, so you see profit by salesman, cost by project, or margin by branch without re-entering a thing.

It is an optional capability, off by default, that you switch on when you actually need it, so businesses that want plain, simple books are never burdened with fields they did not ask for. And because it is part of the same connected platform, the slices stay live and reconciled, the salesman report and the branch report and the company P&L all draw from the same transactions and tie to the same totals. It is included in the one plan at PKR 30,000 a month with all 18 modules, not sold as a separate add-on. You can see the full list on our pricing page.

If you run a showroom, a multi-branch retail business, a contracting firm or a group of companies under one roof and you want to see profit the way you actually think about it, talk to us. Tell us the one slice of your business you most wish you could see clearly, and we will show you how a dimension makes it visible.