Author: Next

Frank ran a metal parts workshop with 40 staff and a warehouse that looked tidy but lied. Every quarter he shut down production for two days to count everything by hand, and every quarter the count told the same story: hundreds of parts were missing, some had been sitting for two years, and nobody trusted the spreadsheet. One quarter the gap hit 3,000 items out of 12,000 tracked. That is when he picked up the phone and called ERPNext Consulting.

They started on the floor, not on the screen

The ERPNext Consulting team did something that surprised Frank. Instead of opening a laptop on day one, they spent two days watching how parts actually moved — how the kitting area pulled stock, where offcuts got returned, and why one storeroom worker kept a private notebook of “real” quantities. Only then did they configure the system to match reality.

• Every bin got a shelf code, and every part got a default bin so no one had to guess where things live.
• Reorder points were set at 14 days of average usage, so purchase suggestions appeared before a part ran out, not after.
• They replaced the dreaded full warehouse count with weekly cycle counts of the 30 fastest-moving items.

What the numbers looked like after 90 days

Inventory accuracy climbed from roughly 75 percent to 98.6 percent in three months. Counting time dropped by 22 percent, and for the first time in years Frank could quote delivery dates from the system instead of from a guess.

Frank told me the best result wasn’t the accuracy. It was that his two warehouse staff stopped keeping private notebooks. They finally believed the system they were feeding, because it gave them something useful back.

The part most managers skip

Frank’s team did not adopt the system because it was beautiful. They adopted it because the ERPNext Consulting team trained the warehouse staff first and the office last, and made the data entry work take less than five minutes per transaction. If your team is still keeping shadow records, start with the bin labels and the cycle-count list. That small step is what pulls a whole company out of the counting trap.

Every year, the same ritual. The 60-person food processing company would lock its office for three weeks during audit season. Cartons of paper invoices, glue-stained spreadsheets, and a finance manager who slept at work while the auditors chased document after document. The owner once joked: “we spend more time proving what we did than actually doing it.” Nobody laughed.

What the auditors were really asking for

They wanted traceability. Which batch of raw material went into the batch of jam that shipped to which customer on which date. When asked a simple question like that, the team needed hours, sometimes days, because the answer lived across three different record-keeping habits.

ERPNext Consulting started not with the finance team but with the production manager. The traceability trail had to begin at the receiving dock: batch number, expiration date, storage location — and then link through production, packaging, and delivery to a customer order.

A trial in one product line first

We picked a single high-volume product, tested the full trail for a month, and only then rolled it out across the other 12 products. The pilot revealed three places where labels were written by hand and the handwriting decided what got logged — a headache no software could fix on its own.

1. Replace handwritten batch labels with printed labels containing a batch number and date, generated right at the receiving dock.
2. Log every quality check result against the batch number within the same day, not in a weekly summary that arrives too late.
3. Generate delivery documents straight from the batch-managed stock record, so the customer and the lot always travel together.

Audit season turned into audit week

The next annual audit started on a Tuesday and finished that Friday. The finance manager took a day off instead of a vacation at the office. Traceability questions that used to take a full day now take minutes, and the production manager finally knows exactly which raw material batch is tied to which delivery.

The most fragile link in any audit trail isn’t the system; it’s the habit of recording at the moment of movement. The ERPNext Consulting setup worked here because the team changed their routine, not just their software. If your audit season makes your staff dread Q1, start with one product line, prove the trail works, and let the results drag the rest of the company along.

An agency with 25 people and three big retainer clients was always busy. The office hummed, projects shipped, clients renewed. But by month nine of that year, the owner had to pull a credit line for the third time in four months to make payroll. On paper, revenue was up 18 percent. In the bank, profit was nowhere.

The six numbers nobody was tracking

When I looked under the hood with the ERPNext Consulting team, the problem wasn’t effort or talent. The problem was that price, cost, and actual workload weren’t connected anywhere. Overruns were being absorbed silently into “client servicing.”

• Actual hours spent per retainer contract, compared to the hours the fee was supposed to cover
• Weeks of unbilled work sitting in the delivery pipeline — this agency had 4.6 weeks and called it normal
• Cost of internal revision cycles on projects billed as fixed fee
• Share of total hours spent on non-billable internal admin, an alarming 22 percent
• Average delay in invoicing after a milestone was actually delivered, which was 11 days late on average
• Profit contribution per client, not just revenue per client

A retainer that looked profitable but wasn’t

Client A brought in $45,000 a month — a headline number. But the contract allowed unlimited revisions, and the delivery team routinely burned 1,300 hours a month to serve it. The true margin on Client A was negative 6 percent. Meanwhile, the smaller project client paying $9,500 was returning a 31 percent margin because the work scope was crystal clear.

The ERPNext Consulting approach convinced the owner to set a hard floor: every client must clear a 20 percent margin before overhead. The agency renegotiated Client A’s scope, cut the internal admin ratio from 22 to 14 percent by consolidating weekly reports, and made a rule that invoices go out within two days of any milestone.

What the calm looks like now

Three months later the credit line was paid off. The agency’s actual net margin went from negative territory to 9 percent, on the same revenue. The owner’s biggest insight: revenue growth without project-level profitability isn’t a badge — it’s a delay.

If you run a service business, compute the margin per client before you celebrate the revenue. Your most famous client may be your most expensive problem, and ERPNext Consulting gives you a step-by-step procedure for exposing it.

The owner of a regional trading business used to open five bank apps every morning, add the balances in his head, and still not know whether he could pay Friday’s payroll. Three branch offices generated revenue on different days, and money moved between them whenever someone needed cash. When payroll day came, he was always one transfer away from panic. Twenty-two days of cash were tied up in limbo.

One dashboard changed his Saturday scroll

ERPNext Consulting built a cash-position view that pulled sales, supplier bills, and bank balances across all branches into a single daily summary. The owner stopped relying on the branch managers’ WhatsApp messages entirely.

Almost immediately he saw that his busiest branch was holding $40,000 in receivables while a quieter branch was carrying the full payroll load. Without a shared system, money moved fast and information moved slowly.

Visibility beats adrenaline every time

A consultant on the ERPNext Consulting team told me something I now say to every client: cash flow problems are usually information problems. The cure is not more discipline — it’s a cleaner view of what will hit the account this week.

• Set a rule: no branch transfers after Tuesday, so cash settles and the dashboard reflects a real balance before the weekend.
• Schedule one 15-minute weekly cash meeting, not a monthly marathon, to approve the next five days of outflows.
• Give each branch its own internal budget code, so an outflow is matched to its branch the same day — not four days later in a reconciliation shock.

From panic to a boringly calm Friday

After six weeks the business had a buffer that covered payroll before the week started. Days of cash tied up fell from 22 to 9. The owner now checks one screen at 7am, calls no one, and simply knows.

The reframe that matters: cash isn’t something you control with heroics; it’s something you see in time to act. That’s what the ERPNext Consulting assessment delivered here — not more spreadsheets, but one calmly reliable number.

The sales meeting started calm and ended with a phone flying across the room. A 15-person trading firm had two salespeople who both handled one large account. The order was booked through “the relationship” — but the credit was split 50/50. Then the client doubled the order, changed the shipping terms, and both reps claimed the full commission.

An honest disagreement turns into a costly habit

The owner’s fix was to give everyone half. That made both reps angry, and worse, it taught the whole team that commission was negotiable. Within one quarter, disputes consumed the equivalent of 17 days of management time — days not spent on customers, pricing, or new leads.

I sat in on the next sales review with the ERPNext Consulting team. We didn’t need to see more emails. We needed to see the stages of a deal, and which rep added value at each stage.

A clear split of stages instead of opinions

We set one rule: a deal’s commission is assigned the moment the deal is recorded as won, with a fixed split based on what actually happened at each stage.

1. First touch — whoever made the customer request a quote gets 15 percent of the commission.
2. Negotiation — the rep who managed the price negotiation gets 55 percent.
3. Handover and delivery — the rep who ran the order to final payment gets 30 percent.

The key principle is commission follows the paper trail, not storytelling. When a salesperson’s role changes, they add their name to the stage record at that time — not after the money arrives.

What changed when the team felt the new rules were fair

Over the next quarter, commission disputes fell from eleven to one. Salespeople went from hoarding leads to collaborating on big accounts. The ERPNext Consulting implementation gave the owner a live view where every open deal showed its expected commission — no more spreadsheet surprises at month end.

That one meeting? The phone-thrower has now closed 20 percent more deals by working together instead of in two separate silos. Fair rules beat good intentions. Write them down, make them visible, and let the system arbitrate.

Let me show you a quote from a furniture maker’s invoice: a dining table listed at $480, and a material cost of $210. The owner thought he was making a comfortable 56 percent margin. He was actually losing money on every single table, and had been for 14 months.

Why the textbook margin formula fails on the workshop floor

The owner only counted the wood, glue, and lacquer. He forgot that the workshop’s rent, the electric bill, machine depreciation, and a fair share of the 14 workers’ wages all had to sit somewhere on that table.

Here’s the math that changed his mind. When the ERPNext Consulting team ran a product-level cost check, they found the true total cost per table was $469. That left 11 dollars of gross profit before freight — and freight cost 18. So every table shipped was a small donation to the customer.

Two product lines were subsidizing six unprofitable ones. The owner had assumed a busy workshop meant a healthy workshop. Not true.

The shift that saved the business

ERPNext Consulting turned his production job cards into live costing records: which order consumed which materials, how many labor hours the table actually took, and how much overhead each job should absorb. The numbers that emerged changed what he sold and what he stopped selling.

• He dropped the entry-level table line entirely and raised the mid-range price by 14 percent, losing volume but gaining nine points of margin per unit.
• We set a simple rule: any new product must show a projected 25 percent margin in the costing sheet before it goes to a customer, or it never leaves the workshop.

A question of habit, not software

Within 90 days the shop cut its monthly operating loss from $6,400 to a profit of about $2,100, on the same number of tables shipped. Same workers, same machines, same customers. Different pricing, one honest costing view, and someone who asked: what does this product actually cost?

If you’re a manufacturer, your profit sits in product-level data. Find the product that loses with love — a price increase of 8 percent on your worst product can do more for your cash than a 20 percent volume push on your best one.

In 2023, the owner of a 12-person export team sat down with a spreadsheet and nearly cried. His largest customer paid in US dollars, three suppliers demanded payment in Chinese yuan, and the freight forwarder billed in euros. Over a year, his currency conversion losses reached $14,000 — more than the profit on two full container orders.

The problem was not the bank’s fees

It was that nobody on the team knew what the company’s real exposure was on any given day. The accountant tracked income in local currency, the sales manager tracked orders in USD, and the owner checked profits the way he checked the weather: weekly, and with hope.

Here’s what the ERPNext Consulting review uncovered:

• The team was invoicing in USD but setting prices using exchange rates that were 60 days old, so every losing-rate period silently ate their margin.
• They converted funds twice instead of using direct multi-currency accounts, paying two sets of conversion spreads on the same money.

A simple rule replaced the guessing game

We didn’t build a hedge fund. We set three rules. First, freeze a reference rate every Monday and base all price quotes on it for the week. Second, keep every invoice in its original currency until the payment is confirmed, so no one converts numbers on paper before cash actually moves. Third, hold all supplier contracts in one base currency to cut double-conversion losses.

The results showed up within 45 days. Currency-related losses dropped to about $300 per month, and the team regained nearly 11 hours of staff time per week that used to go into fixing spreadsheets.

ERPNext Consulting pointed out something I hadn’t fully appreciated: when a company grows quickly across currencies, the risk is not the numbers that wobble — it’s the numbers you can’t see at all.

At 11pm on a Tuesday, the warehouse manager called the owner of a wholesale distribution business. The van had returned from deliveries and the driver swore he loaded 400 boxes of canned goods. The system said he took 310. The warehouse counted 620 on the shelf. The owner put down the phone and thought: who do I trust?

The count kept getting worse — and it wasn’t one person’s fault

This owner ran a mid-size grocery wholesaler with three delivery routes and daily sales of about $18,000. Every month, his team spent two full days doing a physical count. The results got worse each cycle. The gap reached 30 percent on high-turnover items like rice and cooking oil.

The blame game started. The warehouse blamed the drivers, the drivers blamed the sales reps, the sales reps blamed whoever input the orders. The fact was, nobody owned the numbers.

• Stop doing full inventory counts every month; switch to rotating cycle counts — verify a different product family each week, so every single item gets checked within 90 days.
• Match every delivery to a confirmed order number before the van leaves the dock, not after the driver comes back tired and sketchy.

What ERPNext Consulting actually changed in the warehouse

The ERPNext Consulting team didn’t start with software. They started by watching how goods actually moved. They found three handling steps where paperwork went missing every single day, and fixed those first. Then they mapped each step to a tracking record: received, picked, loaded, delivered.

The lesson is that a 30 percent gap isn’t a scanning problem — it’s a workflow problem. Fix the workflow, and the numbers follow. Within two months, the discrepancy on high-turnover items dropped to 2.1 percent, and the monthly all-night count turned into a 40-minute weekly check.

I’ve seen this pattern more times than I can count. If your stock numbers are a story people argue about, that’s not a workforce problem. It’s a process problem wearing a people mask — and ERPNext Consulting has a practical way to unwind it.

The finance manager at a 60-person engineering parts supplier spent the first week of every month closing the books. Nine days of reconciling bank statements, chasing purchase orders, and emailing people about odd numbers. That is nine days a month where nobody looked at the current month’s actual performance.

Why the Spreadsheet Was Not the Real Enemy

The spreadsheets were fine. The problem was that they lived in isolation. Sales had a file, purchasing had a different file, and the bank statements sat in a third place. Reconciling them meant manual matching and endless questions, and every question slowed down the close.

ERPNext Consulting did not start with a big transformation. We started with the purchase order process, because that was where most of the mismatches lived. Every purchase now links automatically to a supplier bill, and every bill links to a payment. That single chain removed the guesswork from accounts payable.

The Three Changes That Mattered Most

1. Bank transactions imported automatically and matched against invoices by reference number, not by human judgment
2. Sales orders, invoices, and payment receipts were tied together, so a payment landed on the exact invoice it belonged to
3. Monthly reports pulled from the same live data instead of requiring someone to copy numbers between spreadsheets

The first few weeks were messy because old habits were strong. People kept asking for files instead of looking at the shared screen. But after two full monthly cycles, the close shrank from nine days to four. By the fourth month, they closed in three days including full review.

What Three Saved Days Are Actually Worth

The team did not just sit around after closing faster. The finance manager started reviewing gross margin by product line every month instead of twice a year. That review caught a pricing error on a high-volume part that had been underpriced for six months.

An extra week of visibility every single month beats any single feature in any system. The close became a routine checkup, not a rescue mission. That is the outcome every ERPNext Consulting implementation should aim for. If your own close takes more than five days, pick the one process that creates the most reconciliation work and fix just that piece first.

Every company has that one machine, or truck, or HVAC unit that breaks at the worst possible moment. For a regional construction equipment rental company, it was the excavators. When one sat idle waiting for a part, the rental revenue stopped, the mechanic’s hours piled up, and customers started calling the competitor. The owner estimated downtime cost them about $6,000 per incident. But he had no way to track how often it happened.

Maintenance was “when it breaks,” and that was the whole problem

The rental company’s maintenance records were a folder of paper work orders and mechanics’ memories. Nobody knew which machines had recurring issues. The same pump failed on the same model of excavator three times in four months, and nobody noticed the pattern. Drivers didn’t report small issues because they didn’t think it mattered. By the time a machine went down, the repair was bigger and slower than it needed to be.

ERPNext Consulting helped them build a simple asset maintenance log. Every piece of equipment gets its own record with its full history: hours of use, maintenance performed, parts replaced, and downtime events. It sounds basic, but it changed the conversation from “why did this break?” to “what does the pattern tell us?”

The routines that kept machines running longer

Here’s what the new process looked like after the change:

• Every equipment operator completes a two-minute daily check on the machine they used: oil level, warning lights, unusual noises, anything odd
• A minor issue gets logged as a work request, not a complaint—it’s a habit, not an interruption, so people actually do it
• Maintenance staff schedule repairs based on the log’s recommended intervals, not based on the sound of something rattling

The numbers shifted in two quarters. Unexpected breakdowns dropped by about 55%, and the time to repair a machine fell from an average of four days to a day and a half because the log said exactly which part was likely failing. The company’s utilization rate—how many rental days per machine per month—went up by 18%. That came straight to the bottom line.

Why preventive work always pays more than you’d guess

The owner was initially worried that scheduled maintenance would take machines out of service too often. In practice, the opposite happened. Scheduled downtime replaces emergency downtime, and it costs a fraction of it. A machine pulled out on a Monday for a scheduled service is a plan. A machine dead in the yard on a Wednesday with an angry customer is a crisis. Once you move from crisis to planning, every number in your business improves.

If you own equipment that generates revenue, try this tonight. List your five most expensive assets. For each one, write down its average monthly breakdown cost from the last year: lost revenue, repair bills, overtime, plus the cost of whatever workaround you used. Total it up. I’d bet it’s bigger than you’re comfortable admitting.

That number is your starting negotiation point with ERPNext Consulting. You don’t need a full overhaul. You just need the pattern to become visible. Once it’s visible, it’s fixable. And once it’s fixable, the savings are mechanical, predictable, and surprisingly fast.