Category: ERPNext

A bakery with 25 employees supplies fresh loaves to three supermarket chains. One Tuesday morning, a supplier flagged that a single batch of flour might be contaminated. The supermarket buyer asked one question: “Can you tell me, within a day, exactly which of our shelves got products made with that flour?”

The bakery’s answer before the consulting work would have been a shrug. After working with ERPNext Consulting, the answer came back in 40 minutes.

What “traceability” really demands from a small food business

Traceability is not a fancy label on a bag. It means that for every finished product, you can list the batch of every raw material that went into it, where it was stored, and which customers received it. For this bakery, the ERPNext Consulting team set up batch numbers at the point of receiving flour, and those numbers followed the dough through mixing, baking, and packing.

1. Every raw material is received with a batch number, an expiry date, and the name of the supplier.
2. Production records capture which batches went into which mixing run, on which machine and shift.
3. Each finished pallet carries the batch links, so the delivery note for a supermarket shows the exact production history.

Why this was a business decision, not a compliance chore

When the audit came, the bakery produced a list of affected products in under an hour, and the supermarket’s buyer said it was the fastest response she had ever seen from a supplier that size. That moment protected the contract. Since then, the bakery has also reduced waste because expired ingredients surface on a weekly report instead of hiding at the back of a shelf. Knowing exactly what sits where saves money even when nothing goes wrong.

What you can test tomorrow

Pick one product you make, write down every ingredient and its supplier, and time yourself tracing it back. If it takes longer than half an hour, you have a gap. Small food businesses assume traceability is a big-company problem, but this case shows it is achievable with a small team when the batch number is captured at the first step. That single habit is what turned a scary Tuesday morning into a quiet 40-minute report for this bakery.

It was 9pm on a Saturday, and a customer in the shop wanted the last armchair in stock. The website had already sold it twenty minutes earlier. The shop manager called the owner, the owner called the delivery team, and the delivery team said the chair was still in the warehouse. Nobody knew the truth.

That is how a five-store furniture retailer with a web shop and two marketplaces ended up talking to ERPNext Consulting.

The real problem was not the double sale

The double sale was just the visible symptom. In a regular week this retailer was reconciling sales from four channels by hand every evening, and the numbers rarely matched. Stock-outs hit 18 percent of advertised items, and refunds for cancelled orders were eating up time and goodwill. The ERPNext Consulting team started with a simple rule: one central stock number, shared by every channel, updated at every sale.

How one count replaced four daily reconciliations

• Each channel gets the same stock level at the start of the day, and the system deducts a sale the moment it happens on any channel.
• Allocation rules reserve items for the in-store customer first when stock is below three units, because walk-in sales have no delivery cost.
• Staff receive a single consolidated pick list so the warehouse only touches each order once.

The numbers the owner now watches on Monday morning

After eight weeks, stock-out rates dropped from 18 percent to 4 percent, and the daily manual reconciliation simply disappeared. The owner told me the most valuable report is a simple one: items with fewer than three units across all channels, refreshed every morning. It tells him where to chase purchases before a problem starts.

The shift that made everything else possible was installing one shared stock record and insisting every channel connect to it. If you are an owner with two shops and a website, you can start this week: pick one spreadsheet, list your top 20 selling items, and update it from every channel every night for a fortnight. Then imagine what happens when the system does that for you automatically. That is exactly the leap ERPNext Consulting helped this five-store owner make.

A restaurant chain sent back an invoice and refused to pay it. The distributor checked and found the quoted price was 12 percent higher than the contract, because a sales rep had picked the wrong price list from an Excel dropdown. For a 30-person beverage wholesaler with 400 customers on different terms, this was not a one-off. It was a weekly event.

The managing director estimated those pricing mistakes cost around $90,000 a year in rebates, disputes, and awkward apologies.

Where the wrong prices were hiding

The ERPNext Consulting team spent a day listening to the sales team, then a day mapping every price rule the company had. There were customer-specific deals, volume discounts, promotional prices for certain products, and different tax rules by region. Each rule lived in someone’s head or in a messy spreadsheet. When a customer complained, the company just credited the difference instead of fixing the root cause.

What they put in place instead

• One price list per customer group, with a validity period, so old deals automatically expire.
• Volume discount rules that step down based on the last 90 days of purchases, not on a promised figure someone forgot.
• A simple approval step for any manual price override, so exceptions leave a trail and get reviewed monthly.

The quiet win nobody expected

Once the first version of the pricing rules went live, a second benefit appeared. Customers stopped calling to negotiate because the invoice matched the quote every time. Dispute emails dropped by more than half, and the finance team stopped spending two hours a week on credit notes. The managing director says the ERPNext Consulting setup paid for itself within the first quarter — not from new sales, but from money that used to leak out the back door.

If you are still approving manual price adjustments by email, start by listing your five biggest customer groups and writing down the exact rule that applies to each. That list is your starting point, and it is exactly how this wholesaler’s fix began. The invoices you send today are a test of how well you know your own pricing.

Marie is a partner at a 14-person structural engineering firm. She found out a project nicknamed “Green” was 18 percent over budget only when the client said no to an invoice. Her team had filled in timesheets every Friday, sometimes from memory, and the spreadsheet showed everything was fine. It was not fine.

Her first call was to ERPNext Consulting, and the conversation started with one simple question: what does each project actually cost, week by week?

The numbers that were hiding in plain sight

The ERPNext Consulting team set up project budgets with hourly rates for each engineer, then switched time logging from weekly memory to daily reality. Within six weeks, the data exposed three projects out of seven that were priced below what they actually cost to deliver. That gap added up to roughly $40,000 of profit leaking out per year — money the firm thought it was making.

• Planned hours versus booked hours, reviewed every Friday before payroll closed.
• Actual cost per hour compared to the billing rate for each project and each person.
• Remaining budget checked against the next milestone, so overruns surfaced two weeks early.

Why this hurts so many service firms

Most small consultancies treat a timesheet as an admin chore rather than a measurement tool. The result is that under-priced projects look profitable until the cash runs out. Marie’s firm now reviews project margins in a ten-minute Monday meeting, and they re-quote or re-scope any project that drops below a 35 percent margin target. The rule is simple: you cannot fix a margin problem you only discover at invoicing time.

What you can steal from this case tonight

Open your last three closed projects and compare the hours you billed with the hours your team actually worked. If any project is more than 15 percent off, you have found your error rate. That one calculation is the reason Marie called ERPNext Consulting — and the reason she now sleeps better at month-end.

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.