Author: Next

Two regional packaging manufacturers merged, and for the first six months they operated as one company with two completely different pricing lists. The same corrugated box design was quoted at $18.40 by plant A and at $16.90 by plant B. Customers noticed. Salespeople lost deals arguing about which division was allowed to honor whose discount, and the finance team could not calculate combined margins without building two separate spreadsheets side by side.

A Merger in Name Only

The new owner assumed the big challenge would be integrating computer systems. In reality, the biggest mess was that plant A used a $5 markup on a particular material while plant B used a $1.20 markup plus a separate handling fee. Both plants were profitable under their own rules, but now they were sharing customers and both still used different cost definitions for freight.

ERP Consulting assembled six people from purchasing, production, sales, and finance for a single working session. The goal was not to choose one price list over the other. It was to agree on exactly what went into the cost of a box, right down to whether the glue in the recipe was a shared raw material or a factory consumable charged to the customer.

The Three Decisions That Made the Price Book Work

• One cost definition. Every plant now includes freight, tooling, and a fixed overhead rate in the same way, so comparing quotes at any of the three sites feels apples to apples.
• One discount ladder. A customer who orders $200,000 a year gets the same discount no matter which plant produces the order.
• One exception log. Any price that does not fit the standard formulas is written on a shared exception sheet that gets reviewed every Friday. Nobody simply memorizes a special deal anymore.

The project took ten weeks, and less than one-third of that time involved software configuration. The hard part was getting the production teams to agree that the cost of an hour of machine time should be calculated identically at both sites. Once the cost definition was settled, everything else became an administrative task.

What the New Owner Noticed Afterward

The biggest benefit was not having a prettier price list. It was that salespeople finally argued with competitors instead of with each other, and quote response time dropped from three days to one. Margin analysis also exposed that one of the merged plants had been quoting freight charges significantly below its actual delivery cost for years.

If you are heading into any kind of merger or acquisition this year, start by printing the last ten quotes from each site and highlighting every line where the same item costs a different amount. If you circle more than three differences, what makes a shared system work is not better software reports but the uncomfortable discussions about cost and discount definitions that your leadership team has been avoiding. ERP Consulting can offer the neutral room, but the honesty has to come from inside your own team.

A sauce and dressing manufacturer with 18 production lines scheduled every day on a giant whiteboard. The production manager used colored magnets to show which batches were running, and his morning phone started ringing before 7am because two products needed the same mixing tank. The system was in his head, and when he went on vacation for two weeks, the plant missed four customer delivery dates in a single week.

A Scheduling Tool Is Not About Making a Pretty Timeline

The whiteboard looked organized, but it only ever showed the current day. It could not show what would happen in three days, when a shortage of glass bottles, a changeover constraint, and a raw ingredient delivery would all collide. No one was stupid and no one was lazy. The planning method simply had no way to look beyond tomorrow.

ERP Consulting started with a very plain question: what actually limits daily output? It turned out to be a single filling line that handled three premium products and was booked for the next three weeks without a single gap. Every other department was scheduling as if that line had unlimited time.

How the Plant Built a Schedule It Could Trust

1. Write down the five longest-running customer orders and their promised dates on one sheet of paper as the “must-ship” list.
2. For each of those orders, work backwards and list every required step: material, packaging, filling line time, and truck booking.
3. Find the single resource that appears most often. That resource becomes the anchor for the whole week’s schedule.
4. Most importantly, protect the anchor by reviewing changes with the sales team before accepting any urgent order. Saying yes to one rush customer means saying no to someone else.

Once the leadership team understood the anchor principle, the planning process became far calmer. The production manager now runs a 30-minute meeting each afternoon to review tomorrow’s anchor line schedule, and urgent requests are handled against a visible list of commitments instead of whoever shouts the loudest.

The Reliability Dividend Nobody Expected

On-time delivery improved from roughly 84 percent to 96 percent in the first ten weeks. The more interesting change was that the sales team stopped promising “next week” so casually, because they could see exactly which lines were already full. The anchor resource acted like a compass: everyone finally knew what had to happen first for everything else to fall into place.

Even if you never open an advanced scheduling program, try this small version yourself. On Sunday afternoon, write down the one machine, vehicle, or person that every big order this week will depend on. If you cannot identify that resource in under five minutes, your schedule is still living on a whiteboard that only works when one clever person is standing in front of it, and ERP Consulting would remind you that a plan should survive a vacation.

An online children’s clothing brand with 12 warehouse staff shipped about 900 orders a day. On a busy November week, they discovered that 3 out of every 100 parcels contained the wrong size or the wrong item. Refunds and re-shipping alone cost roughly $26,000 that month, before counting the angry emails from parents.

Why the Picking Error Was Not Really a Picking Error

The workers were actually fast. They picked by scanning a bin label and a barcode on the item, and the system still passed the mismatch through because the item code in the bin was outdated. Someone had stocked a shelf in the wrong size two weeks earlier and never fixed the location records.

The owner assumed the warehouse needed more scanners and more speed. A closer look showed that the real breakdown happened during restocking, when new cartons were opened and placed before their location codes were entered. The faster the staff worked, the more wrong items they pushed into the picking aisles.

Three Changes, No New Hardware

• Restocking is now a separate task, not a side job done between picks. One person owns it from 8am to 11am, with a count-up checklist for each shelf.
• Any carton with a torn or missing product label goes to a “quarantine bin” and is never placed until a senior staff member confirms the item. That bin is cleared twice a day, not once a week.
• Every new batch of stock requires a quick visual spot-check of three units before the shelf location is activated in the system.

The change sounds almost too simple, but the math was dramatic. Mispicks dropped to below 1 percent within six weeks, and returns due to wrong sizes fell by half. The warehouse supervisor later admitted that the old method had been making the team more productive at doing the wrong task, and speed without correct location codes just creates a larger pile of returns.

The Part Nobody Wants to Hear

ERP Consulting spent most of our first walkthrough counting how many times the same carton was touched before shipping. We found the average box was touched eight times. Every touch added a chance for a mistake, and the team had been treating each touch as normal.

When you walk your own warehouse this week, follow one carton from the delivery dock to the courier van. Count every hand that touches it, and ask each person what they do when the number on the box disagrees with the number on the screen. The first gap you find is usually where your shrinkage and returns actually begin, and fixing that gap will help you far more than adding a second barcode scanner.

The finance manager of an industrial maintenance contractor told me she spent the first week of every month chasing invoice backups from project sites. Job costs arrived on the 12th day after month-end, and the managing director made decisions on the 20th day using numbers that were already two weeks stale. Sound familiar? She was doing the work of three people, and none of it was analysis. It was just assembly.

The Month-End Bottleneck Was Never the Accounting Team

Technicians filled out paper job sheets and dropped them in a box. Someone typed those sheets into the system days later. Meanwhile, a shared spreadsheet tracked which customer ordered what, and that list did not talk to the job sheet box at all.

The breakthrough was to define the close as a business deadline, not a finance task. The field crews started sending job sheets to the office by phone photo at the end of every day. The office team started logging them the same evening, and by midnight the data entry was already complete.

What the New Month-End Rhythm Looks Like

1. Day one and two: all job sheets are logged, and any missing customer approval is flagged in a daily email to the project lead.
2. Day three: the finance manager matches job sheets against the spreadsheet, then merges any difference into one working list with visible comments.
3. Day four: a half-day review is held with the managing director to question the five largest job cost variances before any reports are printed.
4. Day five: the summary is distributed to department leads with a clear note explaining what is included and what will move next month.

ERP Consulting suggested adding one more meeting that seemed unnecessary: a 15-minute call with technicians every Friday to confirm that every job sheet from that week was in the system. Without that check, the old habits crept back within a month.

The Result That Mattered to the Owner

The close now lands on the fifth working day, but the real change is what happens after it. The managing director finally reviews profitability per client before signing new work, instead of relying on a gut feeling about which jobs felt busy. In the first quarter, he stopped discounting a repeat customer who had quietly become the firm’s least profitable account.

Start your own fix by asking a simple question: where does job cost information sit on day two of the close? If the answer involves a shoebox or a personal inbox, your bottleneck is upstream of finance, and ERP Consulting would tell you the same thing.

A 64-person metal fabrication plant accepted a rush order for 48 steel door frames. The inventory screen said every hinge and bracket was in stock, but the warehouse crew spent more than two hours hunting down 14 missing boxes. That Friday, the owner discovered the real problem was not the workers. It was a system that had been allowed to drift away from the floor for years.

Why the Shelf Stopped Matching the Screen

Parts arrived at the loading dock and sat there until the next morning, when someone finally logged them in. Machinists pulled their own brackets and bolts, and the paperwork often caught up three days later. Every time a part was moved to a different rack to make space, the location records stayed frozen in the past.

The plant manager brought in ERP Consulting to guide a fix, and we did not start by changing any computer screens. We started by watching how material actually moved for a week. The team listed every single reason a part could legally leave the stockroom without a record, and there were eleven of them.

The Three Rules That Stopped the Drift

• No receiving without a timestamp. The dock clerk logs every delivery before the truck leaves the yard, even if the details are corrected later.
• No one helps themselves. Machinists request parts from a stock keeper, and the request entry takes under 60 seconds. This was the hardest rule to enforce.
• Every missed part gets a five-minute review. The team answers one question: did the plan change, or did the record lie? Either way, somebody fixes it that same day.

Within six weeks, the plant raised its record accuracy from about 83 percent to 97.4 percent on the 350 items that move most often. The owner then understood what ERP Consulting had told him on day one: the floor will always beat the office if the office never verifies. A system is only as honest as the last movement that got recorded.

What You Can Steal From This Next Week

Pick one small rack that holds your most expensive parts. Count it every morning at the same time, and write the number on a paper log before anyone takes anything. If the count is wrong three mornings in a row, you have a movement problem that no software vendor can solve for you.

When the count comes back correct for ten straight days, expand to the next zone. That simple discipline, not the size of the software budget, was what turned this plant around, and ERP Consulting only supplied the method.

I’ve lost count of the projects that look like wins in month two and like expensive mistakes in month five. Everyone clicks the buttons when the consultant is standing next to them. Then habits kick in, and people go back to email and sticky notes. The tell is in the data: usage drops by roughly 40% between the eighth and sixteenth week after a new system goes live.

That cliff isn’t a software failure. It’s a management failure dressed up as a technical one.

Routine Is the Enemy of the New Way

People don’t resist change, they resist being the only one who looks stupid. In a 50-person tooling company, the warehouse staff quietly switched back to a paper pick list three weeks after go-live. The system was fine; the habit was stronger. The ERP Consulting team couldn’t fix that from behind a screen.

Three Ways to Push People Off the Cliff and Onto the New System

1. Name a “system champion” in each department, not managers — someone others already call with questions.
2. Schedule a 15-minute process review every Monday; show the numbers screen by screen, and fix annoyances publicly.
3. Track real adoption by actions, not logins — count completed orders entered in the system, not how many times people opened it.

Make the Old Way Disappear

This sounds harsh, but it works. When the old paper form disappears from the printer room, people switch fast. We put past-due orders on a shared screen in the break room, so nobody wants to be the name with a red flag.

The point is simple: adoption is a management activity, not a support ticket. If you’re planning an ERP Consulting project, plan the adoption calendar first: who reviews adoption weekly, which two behaviors you’ll celebrate, and the week when the old shortcut stops working.

Every company has that one spreadsheet. The master one. The one only Carol knows how to update. When Carol goes on vacation, the whole management team argues about whether revenue was $1.1 million or $1.35 million.

In a 35-person plumbing supplies wholesaler, the spreadsheet war got loud enough for me to hear it from across the building. Sales had their own file. Finance had theirs. The warehouse had a third. The difference between the three versions was $260,000 — and nobody trusted any of them. Their ERP Consulting engagement started with a simple, uncomfortable exercise.

The “What Did We Decide” Test

I asked them to pull up last month’s meeting minutes and the number they used to decide on a purchase. Then I asked them to find that same number in today’s spreadsheet. It took three people eight minutes. In a meeting, eight minutes is an eternity.

Run the Number You Actually Use

• If that figure lives in more than one spreadsheet, merge them into one file in a single afternoon; if they won’t match up, the problem is process, not math
• Put a single date stamp and responsible owner at the top of any shared file you live by
• Define one number per topic: one for inventory value, one for gross margin, one for promise dates

Light Rules Beat Heavy Software

The best part? The fix didn’t require heroic information technology. The ERP Consulting effort produced one shared report, updated daily at 6 p.m., that everyone agreed to treat as the single source for meetings. Six weeks later, Carol could take a holiday and nobody screamed.

Your move this week: pick the most controversial number in your company and ask two people to find it in their own records. If the answers differ, you’ve just found your starting point.

Here’s a scene I’ve seen more times than I can count. A growing business with three warehouses: the owner asks for this month’s inventory value. The controller says $2.4 million. The warehouse manager says $2.8 million.

The sales director says “why does it matter?” Nobody agrees, and every week the argument restarts. A 60-person electrical parts distributor came to me with exactly this mess. They didn’t have a data problem, they had three separate data problems, each looking perfectly fine on its own.

Why Each Warehouse Believed It Was Right

Warehouse A used a proper receiving process; every part got scanned in. Warehouse B received through a back door and recorded everything in a notebook. Warehouse C was accurate on fast-moving items but had not counted anything in 11 months.

1. For each location, list where every physical count starts and ends.
2. Label locations as “trusted,” “guessy,” and “unknown” — be honest.
3. Run a full physical count on the “guessy” location first; fix processes before fixing numbers.

The Cost of Inventory That Sits in the Wrong Place

The real surprise wasn’t the total value — it was the mismatch. One warehouse held nine months of a slow-moving breaker, while another had to backorder the same part for an urgent customer project. The ERP Consulting review exposed that the company was simultaneously overstocked and out of stock on more than 200 part numbers.

The One-Truth Rule

We made each warehouse adopt a single discipline: every movement must have a paper or scan trail within 24 hours. Within eight weeks, the two warehouses’ numbers converged to within 2% of each other — from a gap of nearly 17%. The ERP Consulting map is only as good as the people who walk the floor.

If your numbers disagree by more than a rounding error, stop arguing and go count. Pick one location, count 100 random items this week, and compare your count to your records. The gap you see is the size of your real problem.

I’ll never forget a distributor owner who told me, “We lose a customer every quarter, and I have no idea why.” His sales team blamed pricing. His top rep blamed a competitor’s fancy new catalogue. When we pulled the account history during our ERP Consulting review, the story looked very different.

Six Out of Eight Left Because of Delivery

We looked at the last eight accounts that canceled. Discounted accounts? Only two. And in six of the eight, the final order was delivered late or incomplete. Nobody had ever asked the customers about that — because nobody reported on it.

The 30-Minute Exit Conversation

We introduced one rule: whoever manages the account calls the customer within 10 business days of a cancellation. Not to argue. Just to ask two questions.

• What was the last order that went wrong?
• What would it take to win you back?

Three of the six lost accounts came back within nine months. The questions are worth real money.

What to Watch So They Never Leave

Forget customer satisfaction surveys. Watch the data that predicts who will leave: orders shrinking, newer customers ordering more, delivery windows widening. The ERP Consulting system made it possible to see those patterns, but the decision to act was management’s.

Here’s the bottom line: before a customer walks out the door, they usually tell you with their order size. Check this week how many of your active customers have quietly ordered less than they did three months ago.

When a 120-person furniture maker told me they were losing a customer a month to delivery delays, my first instinct wasn’t to look at their software. We went to the machines: were the saws breaking, was the finishing line slow? Turns out the machines were fine. They were waiting for parts that sat three feet away from the assemblers for two days, because nobody knew they were overdue.

Promise a Date You Can Actually Hit

Their salespeople promised anything to win the order. The production manager found out about the date when the customer called to ask where it was. That’s not scheduling, that’s guessing. We mapped the actual flow during an ERP Consulting exercise — average 14 days in “in-process” inventory, but only 2.5 days of real work happened on each order.

The Whiteboard That Started the Fight

A simple whiteboard listing every open order, its promised date, and the current status exposed something uncomfortable. The sales team’s “urgent” orders were shoved ahead of planned work, which made the planned work late, which created more “urgent” orders. A hopeless spiral.

• Make every order wait a full 24 hours before it’s rushed into production
• Create one freeze zone: the schedule is locked unless the owner approves a change in writing
• Track how often a promise date actually gets kept

Weekends Without Panic Calls

Within two months, their on-time delivery jumped from 52% to 84%, and nobody’s phone rang on Saturday anymore. The first exercise in our ERP Consulting review was a simple schedule freeze — the same shared list for sales, production, and the owner.

Here’s the part people ignore: the schedule isn’t a production problem. It’s a business promise problem.

If you run any shop that makes or processes physical things, do one thing this week: write down your last five orders, the promised dates, and the real dates. The pattern will tell you everything.