Author: Next

An audio-visual installation company had 14 active projects, a full order book, and a cash balance that kept shrinking. The owner was personally covering wages and supplier bills. When he reviewed the three largest projects, each looked profitable on paper. Yet the bank account said otherwise. The explanation was embarrassingly simple: the timesheets were filled in every Friday from memory, and materials purchased for one job were regularly charged to another job to make that job’s numbers look better.

Fake project margins hide real losses

For one school auditorium job, the estimate allowed 220 hours of installation labor. The team actually spent 340, but engineers recorded the extra time on a different project because that project still had budget left. In the end, the job that looked profitable had actually soaked up six extra paid days. As the owner said: “We didn’t lose the project. We lost track of the project.”

The owner brought in ERPNext Consulting for a margin audit. The consultants compared the quote hours against actual booked time for every project finished in the last two years. The result was uncomfortable: actual labor exceeded quoted labor by an average of 21%, and one-third of all “extra” materials had been silently absorbed.

Daily time entry and the approval rule

The fix was not about sophisticated planning. It had two parts:

1. Each technician spends 15 minutes at the end of the day entering time against a specific project task. Friday catch-up sessions are forbidden.
2. No supplier invoice or expense can be coded to a project unless a purchase order exists for that project. If the project runs over its quoted hours, the system blocks further uncontrolled spending before the overrun eats the cash.

Engineers hated the daily entries for exactly two weeks. Then they noticed a benefit: their own weekly reports about “how busy we were” turned into precise numbers, and the owner stopped asking them to redo timesheets from memory.

What the numbers look like after a quarter

Within 90 days, labor overruns on active projects dropped from 21% to about 4%. More importantly, the owner could see, in real time, which projects were consuming their contingency. One installation that was quietly 30% over budget surfaced early enough that he could renegotiate the client’s change requests instead of swallowing the cost.

An unapproved extra is a gift from the installer to the client. ERPNext Consulting set the rule that any variation above 5% of a quoted project requires the client’s written confirmation before work continues. That single change recovered more margin than the license fees for years. Tracking time daily is inconvenient at first, but it is the only way to catch a bleeding project before the cash runs out.

On a Monday morning, an owner of eight clothing stores sat down with three reports: the stores’ end-of-day sales, the website’s inventory file, and the buying team’s stock sheet. The three documents disagreed on more than 600 items. One said they had 26 units of a popular jacket; the website said 14; the main store said the jacket had been discontinued in March. The buying team had already reordered 40 more.

When the stock count and the customer’s reality collide

The breaking point came during an online promotion. The website confirmed an order for a denim jacket that, according to the system, existed in Store 5. It didn’t. The store manager later discovered that the only sample jacket had been sold weeks earlier and nobody marked it. Customer service spent two days calling stores, refunding orders, and handing out apology vouchers.

This chain had 4,000 SKUs, so the problem wasn’t the size of the business. The problem was that every location treated its records as private. The stores updated their books at different times, the web warehouse reserved items that were never set aside, and display samples were still legally “available” for sale online.

The rules that fixed the mess — without adding headcount

ERPNext Consulting walked through one full day at each type of location before making a single recommendation. Then they set three operating rules:

• Online orders can only be filled from the central stock pool. Store shelves are not part of the website’s inventory, ever.
• Every display sample must be counted in a “not for sale” status. A sample on the shop floor is no longer sellable stock, full stop.
• Store teams count their 60 best-selling items every morning during the opening routine. The full count happens quarterly, not monthly.

These look like common sense, but they require a system that can separate stock pools without demanding that staff become IT experts. The ERPNext Consulting configuration created separate counting areas for the online warehouse and each physical store, so the owner could see at a glance which channel was eating the margin.

The result: a shorter count and a calmer team

Monthly reconciliation time across all eight stores dropped from three full days to roughly six hours. Failed online orders fell from 9% of orders to under 2% in two months, and the customer service team stopped dreading Monday mornings. The hardest part was not the technology — it was convincing store managers that logging a sample as “not for sale” wouldn’t be treated as a theft accusation.

If you run multiple stores plus a website, do one thing this week: check how many display units are still marked as sellable. Those free “virtual” units are the ones that quietly destroy your online reputation. ERPNext Consulting calls them the hidden out-of-stocks, and every retailer has a drawer full of them.

A wholesale distributor of bathroom fittings was preparing a large order for brass valves. The warehouse supervisor checked the system: 43 units in Branch B. He walked over to the shelf and found eight. Then a driver mentioned that a delivery from the supplier, seven weeks earlier, had been parked in a small rented building behind the main warehouse because there was no space on the day it arrived. Nobody had told the system. Inside that building, they found 700 boxes of stock the company technically owned but could not sell.

When records give you a false “yes,” customers feel it twice

In the previous year, this 28-person wholesaler shipped wrong items or couldn’t ship at all on 6.4% of order lines. Most problems came from shelf-level records that were never updated. Every few months they did a full stocktake, found big gaps, fixed them, and then let the records drift again.

An ERPNext Consulting review quickly showed the pattern: receiving staff checked quantities on the delivery note but rarely checked locations, so new stock went wherever there was space. The system said it was on a rack that didn’t even exist anymore.

The weekly top-100 count that changed everything

The consultant didn’t suggest counting all 11,000 SKUs every week. Instead, they built a routine that would survive a busy Tuesday:

• Every Monday morning, count the 100 fastest-moving items that drive 70% of shipments, by physical location, not by part number.
• Log all goods received on the same day the truck arrives, with the exact aisle and shelf code printed on the receiving slip.
• Never allow “we’ll fix the records after the rush” — the after-the-rush fix never happens.

At first the warehouse manager resisted. Two months in, he admitted the Monday count took 45 minutes and saved his pickers hours of walking to empty shelves.

The three numbers that tell you it’s working

After one season, picking accuracy went from 93.6% to 98.1%. But the owner watches three quieter numbers now: the value of stock adjustments each month, the number of locations with a negative quantity, and the count of “emergency” transfers between branches. All three trend downward when the routine is followed. Great inventory management is a weekly habit, not a quarterly project.

ERPNext Consulting also set up the receiving layout so that goods are matched to a purchase order before they are given a shelf slot. That single rule killed the “we found it later” problem at its root. If a box arrives without a destination, it will be lost no matter how good your software is.

At 7:40 on a Tuesday, the production manager of a 60-person precision machining shop opened the plan for the day and found that the first three jobs couldn’t start. The steel for job 1187 had never been ordered, because the person who estimated the requirement assumed someone else had. The fixture for job 1189 was in a workshop across town, borrowed a month earlier and never logged. And the 400 finished brackets from last Friday were sitting somewhere in the yard, but no one could point to which pallet — while a customer was waiting to collect them.

The morning that made them pick up the phone

This wasn’t a one-off. Over the previous year, 31% of their jobs had shipped late, yet the order book looked healthy. The problem wasn’t the machines or the workforce; the shop floor and the planning board simply told two different stories. When the ERPNext Consulting team spent its first two days watching instead of configuring, they found 39 unlabeled bins, three “temporary” storage spots that had lasted two years, and a rework pile nobody counted as inventory.

That last detail mattered most. Scrap and rework only become visible when you decide to count them. For a shop quoting with margins of 8–12%, hidden rework is the difference between a profitable month and a mystery loss.

Three changes that did the heavy lifting

The owner expected a grand software project. Instead, ERPNext Consulting set ground rules that sound almost boring:

1. Every shelf, pallet and tray got a location code, glued to the edge of the bin where the forklift driver could read it without stopping.
2. Stock must be moved in the system on the same shift it physically moves. The old “we’ll type it all in on Friday” habit was banned.
3. Purchase orders for materials could only come from open production jobs, not from the famous “we’d better order some just in case” reflex.

That last rule hurt at first. It forced the owner to admit that nearly one-fifth of his raw material dollars had been sitting in stock for over 200 days without touching a machine.

The numbers after 90 days

Late shipments fell from 31% to 11% in one quarter. The goods-in team stopped doing double counting work, because materials were no longer buried under tarpaulins and rediscovered weeks later. The daily flood of “emergency purchase” requests dropped from eight to one or two.

The best result has no dashboard. Schedulers now plan against actual stock instead of what they hope is there. The discipline of writing down movements on the day they happen is worth more than any fancy report. If your team can’t trust the numbers on a screen, fix the bins before you fix the screens.

When a family-owned group grows from one company into four, the paperwork multiplies faster than the profit. I worked with a holding group that had a distribution arm, an installation service firm, a small manufacturing line, and a leasing entity that owned the vehicles and machines. Altogether about 150 employees, three sets of shareholders, and two currencies. Every month, the finance team spent six days consolidating numbers in spreadsheets, and every month, the family asked more questions than the numbers could answer.

The issues were not glamorous. Loans between the companies had no clear repayment schedule, one company charged rent to another but the invoice was never booked in the right month, and the leased equipment was carrying depreciation in the wrong entity. The owner, a sharp woman in her late fifties, summed it up in a single sentence: “I know total revenue, but I don’t know what each business actually earns.” That’s the sentence that brought ERPNext Consulting into the group.

Why consolidation fails when you run a multi-company group

Spreadsheets are fine for one company. The disaster begins the moment you need to eliminate balances between companies, revalue one currency inside another, and prepare a combined report where the numbers add up. The finance team tried to build reconciliation tables, but every month some invoice went missing or a sale between companies was recorded only on one side. The solution wasn’t to hire more people to feed the spreadsheet; it was to change the setup so that every entity logged its transactions into the same chart of accounts, with the same rules, against the same calendar.

• Set one fixed closing calendar: all four companies close their books on the same day every month, no exceptions, so the consolidation starts on a clean date.
• Create a single chart of accounts that everyone uses, and resist the urge to let each director customize their own account names, or the consolidation becomes a translation exercise instead of an arithmetic one.
• Book every transaction between companies immediately, with a document reference, so the balance between two companies can be verified in minutes instead of days.

The finance team’s consolidation time dropped from six days to half a day. More importantly, the quarterly family meeting changed its character: instead of debating whose numbers were right, they started debating which business deserved more capital, which is a much better problem to have. ERPNext Consulting‘s role was not to build an elaborate reporting palace, but to make the foundation clean enough that the family could finally see its own reality.

The one practice that made all the difference

Every invoice between companies, every loan repayment, every rental charge between entities, was given a document number and posted within 48 hours. That single rule eliminated more than half of the reconciliation problems in the first two months. The finance team was skeptical at first, because they were used to catching up at month end, and the thought of continuous posting required a discipline shift. But the shift paid off in a ratio they could immediately appreciate: one day of finance work per month, instead of nearly a week.

If your business has more than one legal entity, and you feel queasy when someone asks “what did each part of the group actually earn?”, then your first step is to run a single balance sheet between all entities involved. List every loan, rental, and service charge, and note which ones have a matching entry on the other side. The missing matches are your top two fixes for the next month. Once those are clean, your consolidation will start to feel like math instead of detective work, and that’s exactly the feeling a growing family business deserves.

A plant manager at a plastic injection molding facility once told me: “Every breakdown costs money twice.” The first cost is the obvious one — the repair bill and the downtime hours. The second cost is the one nobody writes down: the overtime shift needed to catch up on the missed production, the rush freight for the orders that fell behind, and the damaged trust of a customer who received a late shipment. On their floor, a single hour of unplanned downtime on the main line was worth 1,200 dollars in lost output, and that was before adding the repair cost.

In six months, that factory counted 27 unplanned breakdowns. The maintenance team was talented, but they spent their days fighting fires, and they never had time to plan proper maintenance work. This is a classic case where ERPNext Consulting doesn’t come in to teach complicated reliability theory, but to install a simple rhythm: see the machine history, generate the maintenance task before the failure, and make sure spare parts are already in the storeroom.

The rhythm of maintenance that actually works

• Every machine gets a run-time reading taken at the same time each day, and the system calculates when it crosses the service threshold. For example, a pump that needs service every 500 hours gets its maintenance task generated automatically at 490 hours.
• Spare parts are given a reorder point at 45 days of average consumption, so the storeroom doesn’t run out of the exact part you need during a Saturday night outage.
• Each completed maintenance ticket records the actual time and the parts used, building a history that shows which machines are costing you the most, so you can make better decisions about replacing them.

The rhythm took a little while to become natural. In the first month, the maintenance team still reacted to breakdowns because they didn’t trust the new schedule. But by the third month, the numbers started to shift. Over the next six months, breakdowns dropped from 27 to 11, and the plant manager estimated the company saved something in the neighborhood of 90 thousand dollars, mostly in avoided rush freight and overtime catch-up costs.

What to measure if you don’t know where to start

If you walk into your plant and your maintenance team knows exactly what’s going to break this week, you’re probably already ahead. If they don’t, pick the three machines that caused the most downtime last quarter and write down the top three part failures for each. That’s your starting list. Build a simple calendar task for each of those failure points, set a spare part minimum, and keep going from there.

The lesson from the injection molding plant is that ERPNext Consulting brings the structure, but the real change came from the maintenance planner who started trusting the calendar over the daily noise. When you stop paying for breakdowns twice, you’ll feel it in the budget, and you’ll also feel it in a quieter Monday morning, the mornings where you don’t start the week with a crisis.

A home goods retailer with three warehouses was bleeding 18% inventory accuracy. Every month, the stock counts in the system disagreed with what was physically on the shelves, and the team was spending 30 hours a week hunting for things that weren’t where they said they’d be. The owner’s favorite line was “the system is wrong” and, honestly, he was half right: the system repeated errors that the picking and receiving teams made every single day.

The turning point happened when a rush order for a wedding in two days couldn’t be fulfilled, because the system said a certain lamp shade was in stock, but the shelf location was empty. The customer left, the manager apologized, and the owner finally agreed that the problem was not the tools but the process. ERPNext Consulting started by counting the fastest-moving 100 items across the three sites, and just that exercise exposed a shocking rule: the most popular items also had the most inconsistent storage locations.

The three fixes that took the accuracy from 82% to 97%

1. First, every shelf gets a permanent address. The team stopped moving products to “temporary” spots after receiving, and any item found outside its shelf is treated as a mini-incident that gets logged with a reason.
2. Second, daily counts of the top 50 sellers per warehouse, done by the same person, at the same time, using a consistent counting method. Ten minutes a day, not a huge count at year end.
3. Third, transfer orders between warehouses must be posted the same day, not at the end of the month. This single rule eliminated most of the phantom inventory across all three sites.

By day 90, the accuracy had risen to 97%, and the emergency exception count dropped from dozens a week to three in the whole month. The picking team stopped losing time, the customer service team stopped promising items that did not exist, and the owner stopped confusing “the system is wrong” with “the workflow is wrong”. ERPNext Consulting came in as a guide, but the real ownership of the change landed with the warehouse supervisors who adopted the shelf addresses as their own idea.

What most warehouse managers still get wrong

They buy nicer equipment, more labels, more screens, and assume the accuracy improves automatically. It doesn’t. The accuracy improves when every move has a consequence: a shelf gets a location, a transfer gets posted the same day, a miscount gets explained. That’s a discipline problem, not a technology problem. Once the discipline is in place, the technology actually starts to work, because it’s fed with accurate information at every step.

For a business with multiple warehouses, don’t start with a full inventory count. Start by counting the 100 fastest-moving items, because those are the ones doing the most damage when they’re wrong. Track how long it takes you to reconcile those 100 items and why the errors occur. Fix the top three causes, then expand the routine. That’s how you get from “the system is wrong” to a number you can actually trust.

It started with a single jar. A customer in a northern suburb wrote in to say a batch of chili sauce smelled funny when she opened it, and her family felt queasy after dinner. That one message triggered a nightmare for a 60-product sauce manufacturer whose production records lived in a binder of handwritten forms and a single spreadsheet that nobody could sort reliably.

It took the quality manager two full days to identify which batches were affected. Two days of guessing, while a whole aisle of jars sat waiting for an answer.

Luckily, the test results came back clean, and the company avoided a formal recall. But the scare itself was enough to convince the owner that “lucky” is not a strategy. That’s when ERPNext Consulting came into the picture, not to install a big package of unnecessary features, but to build a simple traceability loop that a small production team could actually follow.

The traceability trail that fits in a single afternoon

The design principle was brutal simplicity. Every production batch gets a number printed on the label. The system records three facts for each batch: which raw material lots went in, which line and shift produced it, and which customer orders it shipped to. That’s it. No barcode scanners with exotic equipment, no industrial engineering degrees required. Just a rule that no batch gets released until those three facts are entered.

• Raw material lots are tagged at the receiving dock with the supplier’s own lot number and the delivery date, so a problem can be traced all the way back to the farm or the processor.
• Every production run starts a new batch record, and the line supervisor confirms it the same day, while the details are still fresh.
• Customer returns go into a dedicated screen, so any pattern like “three returns from one region” is visible within days instead of months.

Six months later, a supplier’s tomato paste shipment was found to have a sulfur smell. The manufacturer pulled the batch numbers that used that paste, identified the four customer orders that contained it, and had the retail stores informed within 15 minutes. The cost of that rapid response was a few phone calls and one email, versus the potential 80 thousand dollars in recalls, disposal fees, and damaged distributor trust that a slow response would have meant.

What traceability is really worth

Managers often think of traceability as a compliance burden, something to build for auditors. But the real value is defensive speed. A food business cannot control every ingredient that arrives at the dock, but it can control how fast the organization reacts when something goes wrong. That speed is precisely what ERPNext Consulting focuses on when it reviews a food manufacturer’s production records: if the answer to “where did this batch go?” takes more than a coffee break, the process needs to change.

If you run any business that buys ingredients or components and ships them onward, run this test this week: pick the most recent batch you produced, and find the answer to two questions in writing — which materials went in, and which orders went out. If you need more than one hour to answer, you have a process gap that will eventually cost you money. Close that gap now, before a bad batch finds you first.

The managing partner of a 40-person engineering consultancy looked at the spreadsheet for the fifth time, then said something I hear at nearly every services firm I visit. “We billed 70% of what we worked last month. I don’t know if that’s because we’re inefficient or because we just aren’t writing everything down.” That gap, the difference between hours worked and hours billed, is where consulting firms lose their profits without ever noticing.

The weird part is that the firm’s quality of work was excellent. Their clients loved them. But the people who designed the systems never designed one for capturing their own time properly, so a big chunk of effort just vanished.

ERPNext Consulting started this engagement by asking a very simple question: for any project, can you tell me the budgeted hours, the worked hours, and the remaining hours in under five minutes? The answer was no.

Where the hours were really going

We put time records in front of the engineers for three weeks, and the results were uncomfortable in the best way. Roughly a third of the “project work” time was actually spent on redoing calculations from earlier stages, because comments and review notes were living in emails nobody could search. Another chunk went to client requests that were never registered as contract changes, so the work was done but never billed.

1. Step one is to capture every hour, even the shameful ones, for three weeks before changing any process. You need a baseline, not a guess.
2. Step two is to name the project phase for every hour entered. A task called “general work” is a red flag that the naming doesn’t match the actual way the team operates.
3. Step three is to hold a weekly 30-minute review, not of each person’s efficiency, but of the top five unbilled activities that week, and decide who talks to the client about them.

Once the team could see the data, the fixes became obvious. Email-based review comments moved into the project log. Client change requests got logged the same day, with the billing consequence highlighted. The first month of the new routine lifted utilization from about 58% to 64%, and by the fourth month the firm was consistently billing above 75% of worked hours.

Why your spreadsheet is lying to you

Most services firms keep a separate spreadsheet for project revenue, and at the end of every quarter they stitch it together with payroll numbers. That’s painful, but the deeper issue is that a spreadsheet has no memory. It won’t tell you that a certain client type generates twice as many unbilled change requests, or that a certain project phase always swallows more hours than the estimate allowed. ERPNext Consulting pushed for a single project record, where budget hours, time capture, and billing status live together, and that’s what made the pattern visible.

If your firm operates on the 70% billing pattern, do one thing this week: print a list of the last ten projects and mark the ones that had scope changes during the work. Then check how many of those changes were actually billed. Most firms discover that the biggest names on their client list are also the most profitable to serve, not because they pay more, but because their change requests are formally tracked. That’s the shift worth making.

Seven years. That’s how long a box of oversized rubber gaskets had been sitting on the top shelf of a safety-equipment distributor I once worked with. The company was doing around 12 million in annual revenue, but its warehouse held an estimated 340 thousand dollars in inventory that had not moved in eighteen months.

The owner knew the stock was there. He’d walk past it every day on the way to his office. But nobody had ever taken the time to sort the slow movers from the dead inventory, and every season the purchasing team reordered the same fast-moving items while the warehouse filled up with the same slow-moving ones.

When the team partnered with ERPNext Consulting, the first task wasn’t installing anything. It was getting a customer sales history report that ranked every single product by the last time it was sold.

Why “just sell it cheaper” is the wrong first move

Most managers look at dead stock and immediately think of discounting. That’s backwards. Discounting the slowest items first just burns margin on products that nobody wants even at a lower price. The right order is to classify first, then decide.

• Items with no sales in 24 months: write them off, donate what you can, and list the salvageable material for scrap. The tax deduction comes from dealing with them, not from storing them.
• Items with a few sales but clear quarterly demand: move them to a smaller “slow lane” area, cut their order quantity by half, and reorder only after an actual order comes in.
• Items that sell steadily but always run short: set a simple reorder point equal to 45 days of average demand, so you stop running out of the products that actually pay the rent.

It sounds simple, but the discipline of actually applying it matters more than the classification itself. In one quarter, the distributor cut its dead inventory from 340 thousand to 95 thousand, and freed up enough warehouse space to rent out one bay to a neighboring company. ERPNext Consulting was the catalyst, but the owner’s willingness to accept that some purchases were a mistake, and to stop repeating them, was the real engine.

The habit that keeps the shelves honest

The real lesson was in the routine that came after the cleanup. A monthly report that lists every item with no movement in the past six months, reviewed for ten minutes by the owner and the purchasing manager, became the standard meeting. They agreed on a hard rule: no reorder on any item that has no recorded sale in the prior 90 days, no matter how cheap or how “obviously useful” the supplier claims it is.

If you have shelves full of quiet stock, set yourself a two-hour task: run a sales-by-item report covering the last 18 months, and ask every item that sold fewer than three times why it’s still there. You will find that most of those items are haunting the warehouse because somebody once ordered them “just in case”. Cut that habit first, and the space you’ll recover will pay for the whole exercise.