Author: Next

“How long for a quote on twelve oak desks?” The customer asked on a Tuesday. “About a week,” the sales rep said. “Don’t bother,” the customer replied, and hung up.

A sales manager at a 25-person custom furniture maker overheard that call from the next desk. It wasn’t unusual. It was Thursday morning and that same thing had happened twice already that week.

Where the week actually went

Quoting wasn’t hard. It was just slow, and the slowness came from six people touching every single quote. The sales rep wrote the requirements. A drafter checked dimensions. The workshop manager estimated hours. Purchasing priced the timber. Someone checked finish options against the supplier list. Then the owner signed off.

Each step took a day or less. Six steps, plus waiting, added up to six or seven days. And in custom furniture, a week is an eternity — the customer has usually already called two competitors by Wednesday.

Guess what the fix wasn’t

It wasn’t a faster spreadsheet, and it wasn’t hiring another estimator. The problem was that every quote was treated as brand new, even though 80% of them reused the same 40 or so components.

So the team built a priced options list: standard timber types, standard finishes, standard leg profiles, standard edge treatments. Each option had a cost and a lead time attached, kept current by purchasing. Anything outside the list still went to the drafter, which turned out to be about two quotes a week instead of twelve.

• Eight finish options priced and dated, updated every Monday morning
• Twelve standard desk and table sizes with fixed workshop hours
• Three delivery zones with real freight costs, not guesses
• A rule that any quote needing a custom component gets flagged at the start, not discovered on day five

Ninety days later

Quote turnaround went from six days to same-day for anything using standard options. Win rate moved from 34% to 51%, partly because speed itself wins work, and partly because the team stopped losing track of quotes in someone’s inbox.

An ERPNext Consulting review six months in found something the owners hadn’t expected: the average order value went up 11%, because salespeople could now show priced options and customers picked more of them.

Speed didn’t just win deals. It changed what customers were willing to buy.

Try this before you spend anything. Count how many people touch a single quote before it reaches the customer. If the answer is more than two, you’ve found your bottleneck, and it’s almost never solved by working harder.

Twelve days. That’s how long a 60-person manufacturer took to close its books every month. The finance team wasn’t slow — they spent most of those twelve days waiting on other people.

I asked the finance manager to log what she was actually waiting for. The results embarrassed everyone, including her.

The 12 days, broken down honestly

Days one to three: chasing shipping to confirm what actually left the dock, because the dispatch notes and the system disagreed on 8 to 12 lines every month. Days four to six: three sales reps who filed expense claims “when they got a minute”.

Days seven to nine: matching purchase invoices to receipts, with roughly 200 invoices a month and no reliable way to tell which ones had a matching delivery. Days ten to twelve: fixing the mess that the first nine days created.

Not one of those twelve days involved analysis. The company had a finance team doing detective work instead of looking at margins.

Three rules that did most of the work

The ERPNext Consulting engagement started with a simple question: who is allowed to change a number, and when? That question produced most of the fixes.

1. Nothing leaves the dock without being confirmed in the system the same day. Dispatch owns this, not finance.
2. Expense claims get submitted by Friday or they roll to next month. Two reminders, then it rolls. No exceptions, including the sales director.
3. Goods received are recorded at the door, so a purchase invoice either matches automatically or lands in a short exception queue.

The exception queue turned out to be the most valuable part. Instead of reviewing 200 invoices, the team reviewed 14. The other 186 cleared themselves, and anything odd stood out immediately.

What four extra days bought them

Close dropped to four days. But the unexpected win was what showed up in the gap: £71,000 a year in duplicate payments and missed supplier credits that had been hiding inside the pile.

The finance manager now spends the second week of every month on margin by product line, not on reconciliation. That’s a different job, and she says it’s the first time in nine years she’s enjoyed it.

Here’s your next step. For one month, keep a log. Every day, write down exactly what you’re waiting for and who owes it to you. The pattern will point at one or two bottlenecks, and those are the only things worth fixing first.

It’s 7:10 on a Monday morning. A 30-person industrial parts distributor has three orders that must leave by noon, and two of them need the same pump seal. The shelf holds four. The system says eleven.

That gap, repeated across 4,000 SKUs, is what got the owners to pick up the phone. Not because they wanted new software — because they were burning about £18,000 a month on split shipments, rush freight, and credits handed out to keep angry customers quiet.

The real problem wasn’t the software

When an ERPNext Consulting team walked the floor, they found stock living in four different truths: the system, a paper pick list, a spreadsheet the warehouse lead kept “just in case”, and whatever the sales team remembered promising a customer.

Four truths means four numbers. And once people can’t tell which number is right, they quietly stop trusting all of them and start working around the system instead.

• The receiving desk logged deliveries the next morning, so anything arriving after 3pm stayed invisible for a day
• Sales promised stock without checking, then split orders into two shipments and ate the extra freight
• Cycle counts happened once a year, in the week half the team was on holiday

Six weeks, three changes

No big bang. No six-month freeze on new orders. Here’s what actually moved the needle, in the order it happened.

1. Scan goods in at the door the moment the truck arrives. One handheld, one person, about 20 minutes per delivery.
2. Give sales a live availability screen — the same number the warehouse sees, refreshed every few minutes.
3. Count the top 200 moving items every Friday. Two people, 90 minutes, finished before lunch.

By week four the paper pick list was gone. Nobody issued a rule banning it. It just became slower than the screen, so people stopped picking it up.

What came back

Stockouts on the top 200 items fell from roughly 60 a month to 6. Emergency freight dropped by about £9,000 a month. Two people who used to spend their mornings hunting for misplaced pallets went back to serving customers.

The clearest sign things had changed: the warehouse lead stopped maintaining his private spreadsheet. Eleven years of workarounds disappeared in five weeks, and that told the owners more than any dashboard.

Total spend on the ERPNext Consulting work came in below the cost of three months of expedited shipping. If your stock numbers are a mess, do this on Friday: pull your 20 highest-revenue items, count them by hand, and compare against your system. Whatever the gap is, that’s your real accuracy rate — a far better starting point than any feature list.

An apparel importer with 25 staff and 12,000 SKUs ran its entire operation on spreadsheets. There was a spreadsheet for inventory, one for purchase orders, one for the bank, and a legendary file called “Final Final Stock 2023 v4” that everyone knew was wrong but nobody dared delete. When two different versions of a popular shirt showed different quantities, the owner assumed one was a typo. It wasn’t. It was two different suppliers’ versions of the same shirt, with the same name in two different styles, entered years apart.

The old system wasn’t the problem. The old data was.

The first attempt to move to a proper system had failed for a simple reason: the team tried to import all Excel files as they were. Every SKU code, supplier name, and unit of measure came from a different era. One item was measured in cartons on purchase orders and in pieces in the sales file. Nobody had defined which one was the base unit, so the system showed some orders needing 600,000 pieces when the warehouse held 600.

ERPNext Consulting took a different approach: clean the data outside the system first, and make the clean version visible to the people who know the products every day — not to an IT specialist.

Five rules that made the migration boring

• Do not merge products that look similar “to save time.” Create them as separate records and mark the old one inactive later. Merging without proper research creates a permanent mess.
• Agree on one base unit per product for all purchases and sales, and enter that as a fixed rule. Pieces and cartons can live as packaging details, but they never drive the stock count.
• Let the purchasing manager review the final product list in small batches — no one stares at 12,000 records in a day. Batches of 500 worked well here.
• Import inventory balances only after a physical count of that exact storage location. Never carry over a spreadsheet balance that hasn’t been verified on a shelf.
• Hold a full dress rehearsal one weekend before the real go-live, and make the whole warehouse team practice receiving and picking from the new system with a small batch of items.

The dress rehearsal that saved the launch

During the rehearsal, the team discovered that mobile barcode scanning into the new system returned the wrong bin for about 40 SKUs because the old location codes had been typed into Excel with inconsistent spaces. Fixing that before the real cutover took two hours. Since the go-live, the warehouse finds 99.6% of all items within two minutes. In the old world, the owner would have thought that target was a joke.

A good migration is more about convincing people to look at one clean list than about the technology. ERPNext Consulting’s consultants spent most of their time sitting with the purchasing manager, asking “is this the same product as this?” until the team themselves realized how much energy the old spreadsheets were consuming. The system will only ever be as clean as the master data you feed it on day one. Spend the extra week cleaning now, and you will never spend a month reconciling the mess later.

A family group ran an import trading company, a local distribution arm, and a small service company, all sharing one office, one warehouse, and a bookkeeper who had been there for 16 years. Every month, the external accountant spent nine working days producing three profit-and-loss statements and then a fourth “combined” version that never quite matched because money moved between the companies informally. The owner could not tell you, on the 10th of any month, whether the group was actually making money.

The float that hid the real damage

One of the companies had been paying for the warehouse renovation, but the cost had been booked as an expense rather than a loan to the shared entity. Another company’s employees routinely worked on the service company’s projects, but their hours were never transferred, so the service business looked far less profitable than it was. The family members had been making decisions using numbers that were off by enough to delay a new hire for months.

ERPNext Consulting started by mapping how money and work actually moved between the three legal entities. Every intercompany transfer, from a shared forklift to an employee’s week of work, needed a price and a paper trail. Business managers hate this at first because it feels like charging your own family for a favor.

One shared master list instead of three separate worlds

The core fix had two parts. First, all three companies use the same chart structure for master data, so a supplier record lives once and is shared, with a label for which legal entity buys from it. Second, intercompany charges are created automatically each month from actual usage rather than from the bookkeeper’s memory.

The monthly routine looks like this:

1. By the second working day, each warehouse manager confirms cycle counts and posts any missing stock adjustments.
2. By the fourth working day, the bookkeeper runs a reconciliation of the intercompany accounts. Any difference above $500 gets investigated before the close.
3. On the fifth working day, the accountant produces consolidated group numbers, with intercompany loans and sales eliminated automatically.

Three days, not nine — and one surprise

Within two months, the close went from nine days to three. The actual surprise was bigger: during cleanup, they discovered a $240,000 intercompany cash advance that was sitting on the books of the wrong entity, making one company look desperate and another look idle. When multiple entities share staff and money, the loan ledger is where clarity goes to die.

If you run more than one company, stop reviewing each company’s profit in isolation. Review the intercompany balances first, because they are usually the biggest distortion in the whole group. ERPNext Consulting built a simple monthly report that lists every uncleared transaction between the entities, and the rule is simple: nothing closes until that list is either settled or explained.

A midsize sauce and preserves maker ran a mock recall drill because a major retailer required it. The scenario: a batch of hot sauce had to be traced from raw ingredients to the store shelves. The quality manager started looking through paper production logs from three months earlier. She found the batch number, then had to walk the warehouse to identify pallets because the records showed only “production run rough date.” Four hours and twenty minutes later, they could tell the auditor which stores received the batch. The retailer’s requirement: 20 minutes.

The problem was hidden in the pallet labels

In this plant, two workers filled and labeled jars on a fast line, writing batch references on a paper sheet at the start of each shift. When jars were packed onto pallets, the pallet stickers only showed the product name and the date. If two batches were packed on the same day, which many were, the information simply melted together. The quality manager confesses they had already shipped a batch with the wrong best-before label without noticing, and only a customer complaint about a sour jar revealed it.

ERPNext Consulting started with one question: what does the retailer need you to prove about one jar in your finished goods? The answer was a simple chain of evidence from raw material lots, through production, to the dispatch note.

The batch routine that produces usable records

The solution wasn’t exotic. It was discipline applied to three moments that already existed in the day:

• When production starts, a printed batch ticket is generated, and it accompanies the line until the run ends. The operator writes nothing by hand.
• When materials are issued from the store, the system keeps track of which raw material lot went into which production batch. Leftover ingredients are returned and recorded on the same day, not dumped back into the next shift’s pot.
• Every finished pallet gets a label with batch number, best-before date and location code. A pallet without a label is quarantined, not shipped.

That last rule hurt most. In the first week, three pallets were delayed because stickers had not been printed. The warehouse manager called it “stupid paperwork.” Two months later, during a surprise audit mock recall, the same drill took 90 seconds.

Why this matters beyond the audit checklist

Trackable batches also cut their write-offs. Previously, when one lot was suspected of a problem, the entire day’s production was blocked because they couldn’t tell which pallets were safe. With proper lot records, only the affected batch was quarantined. In one recall-like situation, that meant blocking 240 jars instead of 2,400. The value of traceability shows itself in the panic moment, not in the calm one.

If you sell food, cosmetics or any regulated product, test your own recall procedure this month. Run the drill exactly as the auditors would: pick a random batch and time how long it takes to find every receiving point. ERPNext Consulting often finds that the weak link isn’t the system — it’s pallets sitting somewhere missing a label to scan.

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.