ERP Case Study: How a Business With Eight Branches Stopped Selling Stock It Did Not Have

What Is an ERP Case Study?

An ERP case study is a documented account of how one business used enterprise resource planning software to fix a specific operational problem, showing the starting pain, the configuration chosen, anything that went wrong after launch, how it was fixed, and the measured result, so other businesses can judge whether the same approach fits them.

Would you trust a restaurant review written by the chef?

Neither would I. Yet that's how a lot of software proof gets made. Pick the happiest customer, trim the awkward months, publish the highlight reel.

A real case study works the other way around. It goes by a few names (customer story, success story, enterprise resource planning case study), but the job never changes. It shows one business, one problem, and the full road from pain to result, potholes included.

Here's what it isn't. It isn't a testimonial, which is one happy sentence and a headshot. It isn't a press release. And it isn't a page of ERP implementation success stories with every bad week edited out.

That last one matters more than you'd think. ERP Research analyzed more than 1,900 case studies published by vendors and their partners, and the ones that disclose a timeline report a median implementation of six months. Meanwhile, the failures on the public record ran for years. The gap has a simple explanation: projects that go badly rarely get written up.

So the ERP case studies worth your time earn trust by showing the part that went wrong. This one does. If you're still getting clear on what an ERP system actually does, start there and come back. We'll wait.

What a Complete Case Study Needs

A complete ERP case study answers nine questions. Miss one and you're reading marketing.

If you only read one row, read the setback log.

Anyone looks good on launch day. What you're really asking is what happens on day 21, when something breaks and the customer is furious. A case study without a setback is a brochure wearing a lab coat.

What the Enerpize Case Study Worksheet Includes

We built the worksheet after reviewing 18 published case studies and case libraries, from enterprise rollouts to academic papers. Whether you're writing a case study on ERP for a university course or documenting your own rollout for the board, it gives you the skeleton. Four things make it different.

A Setback Log, Not a Highlight Reel

There's a dedicated section for what broke, when it broke, who noticed, and how long the fix took. Leave it blank and the worksheet looks unfinished. That's deliberate.

Baseline Before Brag

Every result field sits next to a "before" field. You can't write "stock accuracy improved" without writing down where it started.

Test Cases Before Launch Day

A page of test cases sits before the results section, already filled in with the seven checks from this case. If you didn't test it, you don't get to claim it.

One Feature, One Metric

The worksheet asks for the single feature that decided the purchase and the single number that proves it paid off. Twenty features and zero numbers is how case studies turn into wallpaper.

The Case: Eight Branches, One Stock Truth

He didn't come to us for the dashboards.

He came for one setting.

This ERP system case study is about that setting, and about the week it failed.

The Problem: Selling What the Shelf Did Not Have

Picture a Friday morning at Branch 3. A builder pays for 20 boxes of decking screws. The screen says the business holds 26. Great, except all 26 are sitting at Branch 6, forty minutes away.

Now someone has to make the phone call. The builder waits, gets annoyed, and drives to another supplier down the road.

Before Enerpize, each branch ran its own point of sale, and stock synced overnight. By 9 a.m., the numbers were yesterday's truth. The owner counted about 35 oversold orders a month across the eight branches, and every one of them meant a refund, an apology, or a trade customer who didn't come back.

He wasn't unusual. When DeHoratius and Raman studied nearly 370,000 inventory records across 37 stores of one retailer, 65% were wrong, off by about five units on average, roughly 35% of what was actually on the shelf. They also found that a business's distribution structure makes records less accurate. Translation: more branches, more places for the numbers to drift.

Why One Setting Decided the ERP Choice

Plenty of systems demo well. Dashboards spin, reports glow, everyone nods politely.

The owner cared about something smaller. Could the system stop a sale on stock that wasn't there? Not warn. Stop.

His reasoning was blunt. A warning gets clicked past on a busy Saturday. A block doesn't. Every other feature was a nice extra. This one protected the promise his counter staff made to every customer: if we sell it to you, we have it.

How the Negative Inventory Block Works in Enerpize

Enerpize runs a perpetual inventory system, so every sale, purchase, and transfer moves the stock count the moment it's recorded. With "Allow Negative Inventory" switched off, Enerpize checks the quantity before an invoice saves. Ten units on hand and an invoice for 12? The system shows the invoice would take stock to minus two, refuses to save, and asks you to fix the quantity.

Three related settings decide how tight the lock really is:

• Bundles: a separate option controls whether the components inside a composite product can go negative.
• Tracked items: products tracked by serial number, lot, or expiry date have their own negative setting.
• Requisitions: when they're enabled, stock moves only after a requisition is approved, and you can view available, pending, and total quantities separately.

Each branch can also have its own default warehouse, and so can each employee, so a sale draws from the right shelf without anyone choosing it by hand.

The Setback: "I Came to You for This Feature"

Week three. Branch 1 saved a transfer of 60 bags of cement to Branch 5 on a Tuesday. The truck was due Thursday.

On Wednesday, Branch 5 sold 40 of them.

The block should have stopped that sale, because the bags were on a truck, not on a shelf. It didn't. The check was treating a saved transfer as stock already received at the other end.

The owner called our Customer Success team, and he didn't soften it. "I came to you specifically for this feature," he said. "So how does it not work?"

He was right to be angry. It was the one job he'd hired us for.

Here's what happened next. The same day, we agreed on a workaround: branches saved transfers only when the truck actually arrived, which kept the block honest while engineering worked on it. Six working days later, the fix shipped. The check now counts only stock that has physically been received.

We could have left this part out. But a case study that hides its worst week isn't worth your time, and this was the week that taught us the most.

The Results

Here's what makes this a successful ERP implementation case study, measured the boring way: before and after.

• Oversold orders fell from about 35 a month to none recorded in the six months after the fix.
• At the quarterly stocktake, the share of products with count mismatches dropped from 9% to 2%.
• Branch managers stopped phoning each other to confirm stock, saving the business about 45 staff hours a month.
• All eight branches still run on Enerpize today.

Is this an ERP success case study? We'd say yes, with an asterisk. The win came after the stumble, not instead of it.

For a benchmark outside our own walls, a peer reviewed study followed a food distributor in Alagoas, Brazil, after it brought stock, sales, and logistics into one ERP. SKU accuracy averaged 99.97%, and between 2018 and the first half of 2022, its logistics costs fell 31% while revenue grew 55%. The authors are careful not to credit the software alone. So are we.

Why Negative Stock Happens When You Run Several Branches

Negative stock rarely comes from one big mistake. It comes from small timing gaps that pile up across branches.

And those gaps are expensive. IHL Group's 2026 study puts the global cost of stockouts and overstocks at $1.7 trillion, equal to 6.2% of global retail sales. Its definition of a stockout even covers stock the system says exists but nobody can find.

When Should an ERP Allow Negative Inventory?

Short answer: almost never by default.

Enerpize's own documentation recommends leaving negative inventory off unless your type of business genuinely needs it. There are honest reasons to switch it on:

• Made to order goods, where you invoice before production posts the finished item.
• Drop shipped products, where the supplier ships straight to your customer.
• Paperwork lag, where goods physically arrive before the purchase invoice does.

If one of those is you, allow it on purpose, not by accident. Give negative balances a named owner and review them every day.

Negative stock is like a credit card. Handy in a pinch. Dangerous as a lifestyle.

How to Test an ERP Feature Before You Go Live

Here's the uncomfortable truth our customer taught us. A successful ERP implementation depends less on the feature list and more on whether someone tried to break the one feature that matters.

So break it. On purpose. Before launch.

Step 1: Switch the Block On and Write Down Every Setting Around It

Turn off negative inventory, then note the bundle, tracked item, and requisition settings next to it. Record starting quantities for every branch in a warehouse inventory template. When a test fails, you need to know whether the setting was wrong or the software was.

Step 2: Try to Sell 12 When You Have 10

The basic test. If it passes, you haven't proven much yet. If it fails, stop the rollout.

Step 3: Sell at the Empty Branch While Another Branch Is Full

Put stock in Branch A, none in Branch B, and sell from B. This proves the check looks at the right shelf and not at the company total.

Step 4: Sell Stock That Is Still on the Truck

Save a transfer, don't receive it, then sell at the receiving branch. This is the exact test that would have caught our customer's problem three weeks earlier.

Step 5: Test a Bundle and a Tracked Item

Sell a kit whose components are short, then sell a serial numbered item that isn't there. Special products follow special rules, so they need their own test.

Step 6: Let Two People Chase the Last Unit

Two cashiers, two branches, one unit, same minute. Whoever hits save second should be stopped. A busy Saturday runs this test for free, so run it yourself on a quiet Tuesday first.

Step 7: Return It, Resell It, Then Count It

Process a return, resell the item, then run a stocktake. The system count and the physical count should match. If they don't, your returns are posting to the wrong place.

Sign off each test in writing before launch day. Boring? Yes. Cheaper than refunding 35 orders a month? Also yes.

What This Case Adds to the Famous ERP Failures

The ERP case studies everyone quotes come from giants.

They're still worth your time. Line up the best known ERP case study examples, and a pattern jumps out: the damage almost always shows up in stock.

Read those ERP implementation examples side by side and one thing is obvious. The software brand changes. The shelf never does. Every famous ERP failure case study is a stock story in disguise, and so is every ERP implementation case study that ends well.

Every famous ERP failure is, underneath, a stock record that stopped matching the shelf. The companies that use ERP successfully aren't the ones that never slip. They're the ones that catch it in week three instead of quarter three.

How Enerpize Connects Branch Stock to Every Sale

What does a cashier at Branch 5 actually know about Branch 1?

With a separate till at every branch, the honest answer is whatever last night's sync told them. With one system, it's whatever is true right now. Here's how that works in Enerpize.

Inventory and Warehouses

Enerpize inventory management tracks quantities per warehouse or per employee in real time, with serial, lot, or expiry tracking where you need it. Low stock alerts fire at a level you set, so the reorder starts long before the block ever has to step in.

Requisitions and Transfers

Stock moves when a requisition is approved, and you can see available, pending, and total quantities side by side. Transfers between branches keep each warehouse's stock level visible after the move, so nobody sells cement that's still on the road.

Stocktaking

Enter the physical count, and Enerpize compares it with the system count and calculates shortages and overages for you. If sales happen mid count, "Update System Count" refreshes the numbers before you adjust. You can also count every warehouse on a single sheet.

Clean branch stock makes the tax side calmer, too. Enerpize doesn't file returns for you, but it's built to support the stock and sales records that tax authorities in each of these markets expect you to keep.

Branch Stock Rules in Australia, the United States, the UAE, and the UK

Tax authorities don't care how many branches you run. They care whether your stock numbers can survive a question.

Australia

Here's a rule that sounds generous until you run eight branches.

Under the ATO's simplified trading stock rules, a small business may not need a formal stocktake if the value of its trading stock changed by $5,000 or less during the year. The catch is that your estimate has to be reasonable, and the ATO lists where your stock is kept, in one location or several, as a factor.

What to set up for Australian branches:

• A separate warehouse for every branch, so the estimate adds up branch by branch
• A stocktake plan before 30 June, even if you expect to stay under $5,000
• Negative inventory switched off, since minus balances make any estimate hard to defend

Practical note for Australian businesses: With eight sets of shelves, "roughly the same as last year" gets hard to prove. Branch level records are what turn a guess into a reasonable estimate.

United States

The IRS gives small businesses a shortcut on inventory. It doesn't give them a shortcut on records.

Businesses under the gross receipts test can use simplified inventory methods instead of the general rules, and for tax years beginning in 2026, Revenue Procedure 2025-32 sets that test at $32 million in average annual gross receipts over the prior three years. But as IRS Publication 538 explains, the simplified method still has to follow your financial statements or your books and records.

What to set up for US branches:

• One inventory method, applied the same way at every branch
• Stock records you can reconcile to your books at year end
• Sales tax settings for each branch location, since rates change by state and often by city

Practical note for US businesses: If eight branches each keep stock their own way, your books and records tell eight different stories. Pick one method and let the system enforce it.

United Arab Emirates

In the UAE, the clock on your records runs longer than most owners expect.

VAT records must be kept for at least five years, and corporate tax records for seven years from the end of the tax period under Article 56 of the Corporate Tax Law. The Federal Tax Authority has reminded businesses that this includes their record of transactions and their record of assets.

What to set up for UAE branches:

• Stock movements linked to the tax invoices and credit notes behind them
• A warehouse for every branch, so each tax invoice traces back to real stock
• A seven year retention habit, not five, for anything corporate tax might touch

Practical note for UAE businesses: An oversold item becomes a cancelled sale and a credit note. That's one more document to keep for years. Blocking the sale in the first place keeps the file shorter.

United Kingdom

UK company law is unusually specific about stock.

If your company deals in goods, section 386 of the Companies Act 2006 says its accounting records must contain statements of stock held at the end of each financial year, plus all the stocktaking statements behind them. HMRC generally expects company records to be kept for six years from the end of the last financial year they relate to.

What to set up for UK branches:

• Year end stocktake sheets saved for each branch, not just a final total
• Adjustments with a reason attached, so every shortage has a story
• Negative inventory switched off, so the year end statement isn't built on minus balances

Practical note for UK businesses: The law doesn't only want your closing stock number. It wants the counts that produced it. A system that keeps every stocktake sheet does that job without anyone thinking about it.

Where the Same Control Matters Most

ERP use cases for stock blocking go well beyond hardware. Anywhere a customer pays before they collect, a wrong stock number turns into a broken promise.

Retail Chains

Click and collect orders taken on stock that isn't at the chosen store are the modern version of our Friday screw story.

Pharmacies

Lot and expiry tracking matter here, because the item you sell has to be the one you actually have, and still in date.

Auto Parts Stores

Thousands of lookalike part numbers and customers who need the car back today. Selling a part that's really two branches away costs them a day and costs you the customer.

Wholesale Distributors

Big orders, thin margins. Promising 500 units when you hold 420 means a partial shipment and an awkward call.

Food and Beverage

Bundles and recipes hide their components. When one ingredient runs out, the combo shouldn't keep selling.

Key Takeaways

1. A trustworthy case study shows the setback, the fix, and how long the fix took, not just the win.
2. Blocking sales on missing stock protects the one promise every counter makes: if we sell it, we have it.
3. In a business with several branches, the company total means very little. The check has to look at the branch making the sale.
4. Stock in transit, bundles, tracked items, and pending requisitions are where stock blocks tend to leak.
5. Test the one feature you're buying the system for, in every transaction type, before launch day.
6. Clean branch stock records make tax questions in Australia, the US, the UAE, and the UK far easier to answer.

Frequently Asked Questions

What is an ERP case study?

It's a documented story of one business using enterprise resource planning software to solve a specific problem, covering the baseline, the setup, what went wrong, the fix, and the measured result. The useful ones read like a lab report. The weak ones read like an ad.

What are some real ERP success stories?

The strongest ones include a setback. In this one, an eight branch retailer cut oversold orders from about 35 a month to none recorded, but only after a transfer bug surfaced in week three and was fixed six working days later.

How do I write an ERP case study with solution steps?

Use five parts: the problem with a baseline number, the solution and its configuration, the tests you ran, the setbacks and fixes, and the result against the baseline. The Enerpize Case Study Worksheet follows exactly that order.

Why do ERP implementations fail?

Usually not because of the software. The famous failures trace back to rushed launch dates, thin testing, bad product data, and processes that clash with how the system works. Hershey went live just before its busiest season. Nike trusted forecasts it hadn't properly tested.

What are the 7 steps for successful ERP implementation?

Define the problem and the baseline, pick the deciding feature, clean your data, configure the settings, test every transaction type, launch outside peak season, and measure against the baseline. Most teams rush step five. Don't.

What is negative inventory, and should an ERP allow it?

Negative inventory means the system shows less than zero of an item, usually because a sale was recorded before the stock arrived. Keep it blocked by default. Allow it only for a clear reason, like made to order goods, and review negative balances daily.

Will AI replace ERP?

No. AI is getting good at forecasting and spotting odd patterns, but it needs a system of record to read from. If your stock records are wrong, AI simply gets you to the wrong answer faster.

How does an ERP help a business with several branches?

It gives every branch one live stock number, moves stock between branches through tracked transfers, and stops a branch from selling what it doesn't hold. Head office sees all of it without picking up the phone.

One setting brought him to us. One bad week tested it. Six working days fixed it. Today, eight branches sell only what they actually have.

About the Author
Omar El Bahr is a Senior Digital Growth Specialist at Enerpize, where he leads SEO, content strategy, and organic growth across international markets. He is a Forbes Communications Council contributor and has written for Entrepreneur on business communication and digital strategy.

Disclaimer: The customer's name is withheld at their request. Results reflect this customer's setup and may differ for your business. Tax and legal references are general information, not advice, so confirm your obligations with the ATO, the IRS, the Federal Tax Authority, HMRC, or a licensed adviser.