Author: Next

A food brand ran 14 restaurants plus a central kitchen that supplied them all. The menu prices were set two years ago, and nobody had recalculated the actual cost of a plate since then. When they finally did the math, they found the cost of a signature pasta dish had gone from $4.10 to $5.60 while the menu price never moved.

A Recipe Is Not Just a List of Ingredients

The chef had a recipe card, but the central kitchen was cooking by feel. Portion sizes varied by who was on the line that day. One kitchen was using 15 percent more cheese per plate than the recipe called for, and nobody had noticed because the cheese was bought in bulk.

ERPNext Consulting worked with the team to build a live cost per recipe. Each dish on the menu now has its ingredients, the exact quantity of each, and the latest purchase price attached. When the price of a vegetable goes up, the system shows the impact on every dish that uses it.

What the Numbers Did to Menu Decisions

• Two dishes were quietly losing money and were re-engineered with cheaper, similar ingredients
• One best-selling item got a small price increase that customers never noticed, because it had been underpriced for years
• Portion controls were tightened, which meant the same monthly food budget served more customers

The 12 cents per plate on the pasta dish might sound tiny. Multiply it by 1,800 plates a month across all stores, and you are looking at a meaningful annual loss for zero extra effort. Small margin leaks are the most dangerous ones because nobody feels them in a single day.

The Weekly Check That Prevents Drift

The restaurant group now reviews a simple report every Tuesday: which ten recipes changed the most in cost over the past month. That single report tells them whether a price adjustment or a recipe change is needed before the margin disappears completely.

ERPNext Consulting gave the operations manager a weekly habit, not a one-time analysis. The most expensive mistake in food service is assuming menu prices stay valid forever. Set a recurring calendar reminder to review your top 10 cost-per-recipe numbers. If any has moved more than 8 percent, act in that same week.

An export trader we worked with sold custom furniture fittings to clients in Australia, Germany, and the United Arab Emirates. He invoiced in three currencies, got paid at unpredictable times, and did all his pricing in his head. One deal looked great on paper, then the exchange rate moved, and suddenly a “winning” order was barely breaking even. He knew it was happening but couldn’t prove it.

Why every order’s profit was a mystery until it was too late

The problem wasn’t that he was bad with numbers. It was that his numbers lived in disconnected places. The freight quote sat in one email, the supplier cost sat in another spreadsheet, and the customer’s currency sat somewhere in his memory. By the time the payment landed—sometimes 90 days after shipment—nobody could clearly say which orders had actually made money.

ERPNext Consulting took a practical, vendor-agnostic approach to this mess. We didn’t overcomplicate it. The goal was to have every order capture a few key numbers at the moment of creation: the supplier cost in the original currency, the customer price in the customer’s currency, the agreed exchange rate, and the estimated freight cost. Then the system converts everything into a base currency for reporting.

How exporting became routine instead of a gamble

Here’s the structure that made the difference for this trader:

1. Every sales order asks for the customer’s currency and the agreed exchange rate at that moment, so the expected profit is calculated instantly in his home currency
2. Freight costs are attached to each order as a line item instead of hidden in a vague “shipping” bucket, so the true landed cost is visible
3. At the end of each month, a simple one-page report shows every open order, its expected profit at the original rate, and the current value of that profit if the rate has moved

Within one quarter, he could finally see which products and which markets made sense. Turns out, one of his “best” customers in Australia was actually producing the thinnest margins after currency conversion and freight. He didn’t fire them. He just changed the pricing structure and the currency clause in the contract. That one renegotiation added roughly 4% to his overall profit margin.

The part about timing that most exporters get wrong

I’ll share a specific habit that paid off. The trader used to let invoices sit unpaid for as long as the customer wanted. After the rollout, we set a rule: any invoice past 60 days gets a gentle but firm reminder, and any repeat customer with a history of late payment gets a slightly less favorable credit term. It sounds like simple business sense, but having it recorded in the system meant it actually happened. The average payment time dropped from 74 days to 51 days.

The deeper lesson is that currency risk doesn’t need to be a mystery. You don’t need a Wall Street background. You need to know, on the day you accept the order, exactly what profit you expect in your own currency. If that number moves later because of exchange rates, at least you know it and can respond.

If you’re selling across borders and your profit per order shifts wildly from month to month, sit down and write out how you currently calculate your expected profit. If the words “I just estimate it” appear anywhere in that process, an honest look at your last ten orders will probably surprise you. That’s your starting point. And it’s exactly the kind of starting point where ERPNext Consulting can make a real difference.

A trading company imported kitchen equipment from three countries and sold it to local retailers. The owner was proud of his margins until a customer ordered a full container. When the container landed, the owner realized the freight and customs charges had eaten an entire year of profit on that one order.

Why the Price Tag Was Wrong

The company priced products using the supplier invoice plus a fixed markup. But that markup never included ocean freight, insurance, customs duties, or the bank fees for the overseas transfer. A product that looked like a 20 percent margin was often a 9 percent margin once the container actually arrived.

ERPNext Consulting helped them restructure how cost was recorded. Every purchase now carries all the extras, freight, insurance, duty, and local transport in one place. The purchase cost shown on the screen is the real landed cost, not just the supplier’s invoice.

What the New Numbers Revealed

• One product line that seemed profitable turned out to lose money on every order due to heavy packaging weight
• Air freight orders were costing three times more than ocean freight, but the selling price was identical
• Two suppliers had consistently higher defect rates, which added hidden rework and replacement costs

The owner made two changes within a month. He stopped air-freighting the heavy items unless a customer paid a faster-delivery premium. And he renegotiated prices with the two expensive suppliers. The combined effect kept more than $40,000 in the business over the following year.

Currency, the Quiet Profit Killer

Trading across currencies means the exchange rate moves between quoting and paying. The old method was to just note the rate on a sticky note and hope. The new approach records a fixed quote rate in the system, so a currency swing becomes visible immediately instead of becoming a surprise at the bank statement.

Every importer should know the true landed cost of each product before promising a price to any customer. ERPNext Consulting did not invent any magic here. It simply forced the company to include every number that already existed.

If you trade across borders, list every cost attached to the next container that arrives, then check what your spreadsheet actually includes. You might be surprised.

I met a boutique online retailer—organic skincare products, about 3,000 orders a month—where a smart, hardworking woman named Priya was spending three full days every week copying order data from one system to another. Her bank statement didn’t match her sales platform. Fees were mysterious. Refunds vanished. She had five different spreadsheets, each with a different total, and she’d given up trying to explain why.

When order counts and bank deposits disagree

The core problem was that the shop had grown fast. Orders came in through the website, payments arrived through a payment gateway, and inventory counts lived in yet another tool. Every night, Priya would download three files and manually try to make them agree. It never quite worked, and she was spending her entire Friday trying to figure out why the numbers were off by a few hundred dollars each week.

ERPNext Consulting ran a diagnosis over two weeks. We connected all the order flows into one system: sales orders, payment capture, shipping, refunds, and returns. The aim was simple—one order should create one record, automatically, with no human needed to connect the dots.

The new rhythm for the retail operation

Let me show you what a clean order flow looks like after the change:

• An order lands on the website, a system record is created with the customer’s details, items, and shipping method—all in under a second
• Payment confirmation comes back from the gateway, the order status updates from “pending” to “paid,” and the warehouse pick list is generated
• When the courier marks the package delivered, the system books the shipping cost, and the order is ready for reconciliation at month-end

Priya went from 12 hours of weekly reconciliation work to about 40 minutes. And the matching problem disappeared: every single order now has a clear trail from click to delivery to accounting entry. The month-end bank reconciliation, which used to take a full day and a bottle of wine, now takes less than an hour.

The hidden money in refunds and chargebacks

Here’s where the real surprise was hiding. The system showed that 7% of orders were being refunded or partially canceled, but nobody had ever aggregated that number. When we added it up, refunds and failed payments were consuming about 11% of the company’s gross margin. Priya had suspected but never quantified it. Seeing that number on one screen changed the conversation—they adjusted their pricing on a few low-margin products and stopped offering free shipping on orders under a minimum threshold.

The lesson here applies to any business selling online. If your order data and your bank statement need a human detective to reconcile them, that detective is probably costing you more than you think. Not just in hours, but in the mistakes that slip through.

Run this quick test. Take last month’s sales report and your bank deposits for the same period. If the difference is more than 2%, you have a data problem. Tell yourself it’s temporary if you want, but it rarely fixes itself. The kind of clean, automated order flow that ERPNext Consulting sets up pays for itself in the first quarter, just by giving you back your Friday afternoons.

Two sisters ran a seven-store clothing retail chain and still argued about stock levels every Monday morning. One sister would say, “We have 40 of those jackets in the warehouse.” The other would respond, “No, we sold 30 last weekend, so we have ten.”

Both were wrong. The truth was somewhere in the back of a store room.

The Monday Morning Truth Test

They had a point-of-sale system, but it only tracked sales, not the stock on shelves. Nobody counted what was actually in each store. Transferring stock between stores was done by group chat messages and hope.

ERPNext Consulting started with one question: what is the minimum information you need to run this chain without constantly being wrong? The answer was basic, but it changed everything. Every store needed a live count that matched what the shelves said.

Keeping Stock Honest in 7 Different Locations

1. Start with a full count at every store on the same weekend, so all seven databases begin from the same reality
2. Set a fixed schedule, one store per week does a partial count of its top 50 selling items
3. Treat any mismatch above 2 percent as a bigger investigation, not just a quick fix

The sisters were skeptical about the counting discipline. Their old habit was to count the best sellers only when things felt wrong. The change was committing to the schedule even when sales were busy. It felt like slowing down, but it actually sped everything up.

Transfers That Used to Take Days

The real payoff came from inter-store transfers. A jacket that sat unsold in the downtown store for three weeks sold out in one weekend at the airport location. The system showed the difference instantly, so the transfer became a routine decision instead of a neighborhood drama.

After four months, the chain’s stock turnover went from 3.1 turns a year to 4.4 turns, and the Monday morning arguments disappeared because both sisters looked at the same screen. The lesson I pass along from this one: a retailer’s worst enemy is not low stock, it is stock in the wrong place. ERPNext Consulting gave them one version of the truth, and that alone was worth the effort.

A food manufacturer producing sauces and marinades had a painful secret. Every month, the warehouse would send a list of expired raw materials to the owner’s desk, and every month, the owner would wince at the number. It averaged about $19,000 a month in spoiled ingredients. That’s $228,000 a year vanishing into the trash bin.

Why things went bad before anyone noticed

The company’s old way of working was: write the production date on the box with a marker, store it on a shelf, and hope someone remembered. With 400 SKUs, “hope” is not a storage strategy. Ingredients would sit behind other ingredients for months. The purchasing officer kept buying fresh stock while perfectly good but older stock aged into oblivion in the back corner.

ERPNext Consulting took a different angle. Instead of making one person responsible for watching expiry dates, we made the system do the watching. Every batch of raw material gets a tag with an expiry date and a bin location. The system knows what’s oldest, what’s closest to expiring, and what should be used first.

What the new routine looks like on the ground

Here’s the concrete workflow that replaced the marker-pen system:

1. Every incoming ingredient batch is recorded upon delivery with its production and expiry dates, tied to a specific location in the warehouse
2. The system automatically sets a “use by” date that’s 45 days before the real expiry, giving the production planner a buffer to use old stock first
3. Each Friday, a one-page report lists every batch expiring in the next 60 days, organized by location, so anyone can walk straight to the shelf and pull it

The results came faster than anyone expected. In the first two months, spoilage dropped by 60%. By the fourth month, the company’s loss rate had fallen to about 1.2% of stock value, down from 8%. The savings were enough to cover the entire consulting fee plus the software subscription for a year and a half.

The trick that most companies miss

The real win wasn’t the expiry tracking itself. It was fixing the purchasing policy. The system started flagging how much stock was being ordered versus how much was genuinely being used. The company discovered they were over-ordering some ingredients by nearly double, purely out of fear of running out. Better data meant they could order less, store less, and waste less. That’s the kind of insight no spreadsheet can give you, because the spreadsheet was built on the same faulty assumptions.

One last thing. Don’t hire a consultant during your busiest season and expect it to go smoothly. Wait for a reasonably calm month, get the system live, and let the routine settle before the rush hits. The team needs about two weeks of repetition before the new behavior sticks.

If your stock has an expiry date and you’re still relying on anyone’s memory, start tracking the money you lose monthly. Write it down. I promise the number will be big enough to justify a call to ERPNext Consulting.

An agency with 25 employees ran a review of their 40 active projects. They assumed the biggest client was the most profitable because it generated the most revenue. Turns out that client was losing them money every month, and the smallest retainer project was quietly funding the whole office.

Revenue Is Not Profit, and Everyone Had It Backwards

The agency tracked billable hours but never compared them to what each project actually cost to deliver. The account manager for the big client kept asking for extra design reviews, all uncharged, because “the client is worth keeping happy.”

ERPNext Consulting helped them set up a simple structure: every project carried its own costs, its own hours, and its own budget on one screen. Project managers finally saw a running number instead of discovering a surprise at the end of the quarter.

What Made the Numbers Look Different

• Time entries were tagged against a specific project and phase, not just the client
• Fixed-fee projects showed a live profit number that updated as hours went in
• Retainer projects were reviewed on a fixed date every month, comparing hours spent to the fee received

The result was uncomfortable but useful. They renegotiated one contract, dropped one unprofitable service line, and put the big client on a new pricing model that charged for the extra review cycles. Within three months, the agency’s average project margin went up from 24 percent to 39 percent.

Do This Before You Buy Anything

For two weeks, list every project and write down the hours your team actually spent, not what you planned to spend. Add in the small extras, the calls, the last-minute tweaks. That two-week snapshot will tell you more about your business than any software demo ever will.

The agency’s mistake was celebrating revenue while ignoring the cost of delivery. ERPNext Consulting did not save them money with fancy features. It just showed them the truth in a format they had to look at daily. If your agency cannot tell which projects make money right now, start fixing that next Monday, not next quarter.

A digital marketing agency with 22 employees came to us with a strange complaint. They were busy all the time. Profits were thin. The founders had that tired look of people working harder than their paycheck. We dug into the numbers and found that the agency was billing clients for about 30% fewer hours than employees were actually working. Some of that was honest, generous scope creep. Most of it was just disorganized tracking.

How time and money were drifting apart

The agency used a mishmash of email, WhatsApp, and a free timesheet tool that nobody liked. Project managers would estimate a job, then hand it to freelancers and juniors who logged hours whenever they remembered—usually three days late, in half-hour chunks, rounded down. When invoicing day came, whoever was responsible would just look at what “felt right” and send a number.

ERPNext Consulting pointed out the real cost: every 1% of unbilled time at that agency equaled roughly $45,000 a year. When you see the dollar figure attached to “just ten minutes here and there,” suddenly people stop treating timesheets as an administrative chore.

What we changed, and what it produced

We set up a simple project-billing structure that connected time entries directly to client projects. No more separate tools. Here’s the practical shape of the solution:

• Every team member logs time at the end of each day, tied to a specific client and task—ten entries max per day, so it’s quick
• Project managers get a weekly alert showing hours used versus hours budgeted, so scope creep gets flagged before the client gets the bill
• Invoicing becomes a one-click review: the system drafts the invoice from approved time entries, and the PM just removes anything questionable

Within two billing cycles, the agency caught hours they’d been giving away for free. Fixing their pricing and their time-capture habits recovered roughly $90,000 in billable work over a year. Their profit margin went from 11% to 19%. Same team, same clients, same effort—just properly counted and properly billed.

The part nobody wants to talk about

Here’s the uncomfortable truth. The agency’s most senior person was the worst at logging time. He thought it was beneath him. The founder had to sit him down and show that his under-logging was literally funding a client’s project at a loss. Once the senior people started logging properly, the juniors followed within a week. Culture follows behavior, not policy.

If you’re a services business, here’s your homework. Pick any ten projects from the last quarter. Compare the hours logged to the hours actually worked, as best you can estimate. If the gap is more than 10%, you’re leaving money on the table. Do that calculation tonight, and if you don’t like the number, that’s exactly the conversation ERPNext Consulting is built for.

One in every eleven orders shipped out wrong. That was the statistic a 60-person plumbing and heating wholesaler discovered when they finally measured it. With 300 orders a week, that is about 27 angry customers and a pile of return shipping costs every single week.

Stop Blaming the Warehouse Staff

The warehouse team was not careless. They were working with orders that got printed twice, prices that changed without notice, and customer addresses that lived in five different places. The forklift driver was making decisions a system should have made for him.

ERPNext Consulting looked at one specific flow first: how an order moved from a sales call to the loading dock. We found the sales team was rewriting orders by hand into a second system because the first one was too slow. Every rewrite was another chance for a mistake.

Fix the Order Flow Before Changing Anything Else

Here is what we did in order, and the order matters. First we removed the duplicate entry step completely, so the order entered once and flowed through automatically. Then we added a pick list that grouped items by warehouse aisle, not by how the salesperson typed them in.

• Orders were locked 30 minutes before dispatch so last-minute edits made it to the truck instead of the shelf
• Packing staff had to scan the order number before printing the label, which stopped the “two orders swapped” problem
• Every wrong shipment was logged with a one-line reason, so patterns showed up fast instead of staying as rumors

Within eight weeks, the error rate dropped from 9 percent to under 4 percent. The owner calculated that every percent of error was costing roughly $6,000 a year. If you do the math, that improvement paid for the entire ERPNext Consulting engagement in about five months.

The deeper lesson is that errors are rarely a people problem, they are a process problem wearing a people costume. The moment they stopped blaming the staff and started fixing the handoffs, the numbers moved. Track your error rate for two weeks before you change anything. You will not fix what you have not measured.

Here’s a confession from a distribution company owner I worked with: “I always knew my stock counts were wrong. I just didn’t know how wrong.” His company sold plumbing supplies across three states, and every quarter, the physical count would reveal losses worth around $45,000. Not theft. Just bad record-keeping.

Why the stock always seemed to be “in the warehouse somewhere”

The root cause was boring but brutal. Receiving staff would tick boxes on paper, and the office would type those numbers into a spreadsheet two days later. In those two days, salespeople were already selling items that hadn’t been recorded as received. So the system said “out of stock” when the shelf was full, and “in stock” when the shelf was empty. Classic handoff failure.

ERPNext Consulting started by showing the owner a simple diagram of where information got stuck. Receiving, picking, returns, and purchasing were four separate islands. The fix was to make one action automatically update everything else. When a driver signs for a delivery on a handheld device, the purchase order closes, the stock count rises, and the purchasing manager can see it immediately.

The changes that actually moved the numbers

Here’s what we implemented, step by step:

1. Switched receiving to a barcode scan at the loading dock, closing purchase orders the same day they arrive
2. Set up a simple cycle-count routine: count one category of items every Friday, instead of doing a painful full count twice a year
3. Created a “negative stock” alert so that any item showing zero or below gets investigated within an hour

Six months later, the quarterly variance was down from $45,000 to under $4,000. And here’s the part the owner wasn’t expecting: the time his warehouse manager spent on inventory paperwork dropped from 15 hours a week to about 4. That manager started using the freed-up time to reorganize the entire storage layout by picking frequency. The warehouse became faster, not just more accurate.

A lesson worth stealing

The most important change wasn’t technological. It was that the receiving supervisor and the purchasing manager started having a quick five-minute meeting every morning, looking at the same screen together. Before, they’d poke at each other with passive-aggressive emails. Now the system surfaces the problem before it becomes a conflict. That’s worth more than any feature.

The single biggest predictor of inventory accuracy is not the software you choose—it’s the discipline of recording every tiny movement of stock as it happens. If you can’t get your team to scan a barcode on day one, no system will help you.

If your bin labels, your spreadsheet, and your physical shelves all tell different stories, stop guessing and get ERPNext Consulting to run a quick data audit. In two weeks, you’ll know exactly how much money is hiding in those mismatches. Then you can decide if it’s worth fixing. I think you know what the answer will be.