Emma: Imagine trying to keep track of 450,000 tons of physical material every single year.
Ryan: I mean, that is just a staggering amount of stuff to even picture.
Emma: Right, Picture the sheer scale of that for a second. You are standing in the middle of this massive industrial facility and there is just a relentless, never ending river of pallets, crates and shipping containers flowing right past you.
Ryan: Just absolute constant motion.
Emma: Exactly. Now imagine trying to manage all of that when your master computer system, like the central brain of your entire operation, is completely blind to what is actually sitting on your warehouse floor at any given moment.
Ryan: Oh man, that is a terrifying thought for any logistics manager.
Emma: Right. You have spreadsheets and databases telling you one thing and then the physical reality of the concrete floor telling you something completely different.
Ryan: And um, and it is an incredibly common and incredibly expensive nightmare for businesses. Like the digital map looks perfectly organized up in the office, but the physical territory out in the yard is just total chaos.
Emma: Yeah, massive gap between the software and the reality.
Ryan: Exactly. And when you have that gap, you end up spending enormous amounts of time, money and human effort just, you know, trying to manually build a bridge between the two.
Emma: Which brings us to the exact focus of our deep dive today. We’re looking at how a company facing that precise nightmare managed to completely rebuild their digital infrastructure.
Ryan: It is quite a story.
Emma: It really is. Our source material today is this really comprehensive business case study titled VIPA Hellas Case Study. And our mission here to unpack exactly how unifying disconnected software can cure some of the worst operational headaches imaginable.
Ryan: Yeah, we are going to look at the underlying nuts and bolts of how this works.
Emma: Exactly. Using this case study as the ultimate blueprint for making your digital tools actually reflect the real world. Okay, let’s unpack this.
Ryan: We really need to start by looking at the raw numbers here because, well, the scale of the problem totally dictates the complexity of the solution.
Emma: Right, Right. So the subject of this case study is a company called VIPA Hellas. They were established in Athens in 2013 and they are a major player in the recycling and recovered materials industry.
Ryan: And when the case study says major player, they are not exaggerating at all,
Emma: not even a little bit. I mean, they are moving 450,000 tons of recovered non hazardous recyclable materials, paper board products and pulp annually.
Ryan: Yeah, it’s massive. But you know, the volume isn’t even the trickiest Part, is it?
Emma: No, it’s really the specific way they
Ryan: have to move it that is the core of the issue right there. VIPA Hellas operates in what the industry calls a strictly container driven environment.
Emma: Okay, let’s pause and define that for a second because it sounds simple, but it fundamentally changes the math on how a business operates.
Ryan: Oh, it changes absolutely everything. So think about it like this. Most standard warehouse software is built around individual items.
Emma: Right. Like standard retail stuff.
Ryan: Exactly. You have a widget, you put the widget on a shelf and eventually you sell the widget. But VIPA doesn’t deal in single widgets at all. Everything moves, is tracked and is sold by the container.
Emma: And a container is not just a simple box, far from it.
Ryan: A container is a massive, complex entity. It might hold multiple different lots of recycled pulp and each of those lots has different weights, different origins, different quality grades. Wow. Yeah. So the container itself is actually the unit of business.
Emma: So standard off the shelf software just, you know, it doesn’t know how to think in terms of these massive multivariable containers.
Ryan: Precisely. It’s totally foreign to a standard system. And, and that leads us to the fundamental flaw in VIPA’s old setup. They had this massive glaring divide in their digital infrastructure.
Emma: The brain and the muscle were totally separated.
Ryan: Exactly. So they were running a warehouse management system, or a wms, which is the muscle. Right. The WMS is essentially the operational muscle of a business. It tells the forklift drivers where things are physically located on the warehouse racks. But their main enterprise software, their erp,
Emma: the Enterprise Resource Planning System.
Ryan: Yeah, basically the financial and administrative brain of the company, it was a completely separate entity. And in this case, their ERP was Microsoft Dynamics 365, Business Central.
Emma: So the brain and the muscle were entirely disconnected.
Ryan: No integration whatsoever. None. So just think about the mechanics of that for a second. You have a relentless physical flow of hundreds of thousands of tons of material moving constantly, moving constantly. And every single time a container is moved, packed or shipped by the muscle out on the floor, a human being has to sit at a desk and manually type that, that movement into the financial brain just to reconcile the data,
Emma: which is just a recipe for absolute operational misery.
Ryan: It’s a nightmare.
Emma: And the real world fallout of this manual reconciliation, according to the case study, was just brutal. Let’s look at their inventory accounts as an example.
Ryan: Oh, this part is wild.
Emma: Right. When they had to actually go out to the warehouse floor and verify what they physically had, it required multiple staff members and took two to three excruciating
Ryan: days to complete just massive amounts of downtime.
Emma: Two to three days of just counting and double checking everything by hand.
Ryan: Because you can never trust either system completely when they don’t talk to each other.
Emma: You’re just guessing.
Ryan: Yeah. You are constantly trying to figure out is the WMS lagging behind the ERP or maybe the ERP has a typo that the WMS doesn’t.
Emma: And it went way beyond just counting stuff. I mean, even the generation of barcodes, which is the very foundation of how you track physical items in any modern facility that was happening entirely outside of
Ryan: their core system, which introduces a massive risk of duplication.
Emma: It’s like playing a high stakes game of blindfolded Tetris.
Ryan: That’s a good way to put it.
Emma: Imagine you are managing this enormous shipping yard. You have a beautiful pristine master map up in the main office, but it doesn’t talk to the walkie talkies that the actual workers are using out in the rain on the ground.
Ryan: Right, right, right.
Emma: So a forklift driver moves a massive shipping container. They scribble the new location down on a clipboard and then, you know, hours later someone in the office has to squint at that clipboard and manually type the new location into the master that. Yeah, you are making moves in the dark just hoping that by the time you drop your Tetris piece, the rest of the board is actually where you think it is.
Ryan: That is a phenomenal way to visualize it. Yeah. I mean, you are introducing all this latency into a physical environment that demands real time precision.
Emma: It’s just inherently broken when you have
Ryan: a gap like that. Your business is no longer running on accurate data. It is running on the sheer manual effort of people desperately trying to keep the data from falling completely out of sync.
Emma: So if you are the management team at VIP Helis, how do you even begin to fix a disconnect this catastrophic?
Ryan: It’s a huge undertaking because you have
Emma: this massive operation that is already running at full speed. You cannot exactly just, you know, hit the pause button on 450,000 tons of material while you spend a year figuring out a new software architecture.
Ryan: No, you definitely can’t. You need a surgical intervention. And this is where the strategic concept of build versus buy comes into focus.
Emma: Okay. Build versus Buy.
Ryan: Right. V. Pahelas recognized early on that they couldn’t do this internally. They brought in two key partners to architect this fix. The first was by’s SA who acted as the primary Microsoft partner leading the entire implementation. The second partner was Insight Works, which is an independent software vendor or an ISV that specializes specifically in building warehouse applications for the Business Central platform.
Emma: Now hold on. This is where I actually want to push back a little bit.
Ryan: Okay, go ahead.
Emma: If you are VIPA Hellas, right, a massive company with a highly bespoke container driven operational model, why on earth would you piece together a solution using third party apps?
Ryan: I see where you’re going with this.
Emma: If I have a highly unique business, shouldn’t I just hire a team of developers and build a proprietary system completely from scratch? Like, if you buy off the shelf software for your warehouse foundation, aren’t you forced to change your unique business processes to fit the software’s generic defaults? Doesn’t that kind of defeat the purpose of having a specialized container business in the first place?
Ryan: It’s a totally fair question, but what’s fascinating here is how they circumvented that exact trap. The brilliance of this hybrid approach lies in understanding exactly what needs to be custom and what doesn’t.
Emma: Okay, explain that.
Ryan: Well, Microsoft Business Central is designed with a highly modular architecture, so it allows independent vendors like Insight Works to build really robust plugins that handle universal warehouse functions.
Emma: Standard stuff, right?
Ryan: The case study actually includes a really crucial quote from Antonis Kakavas. He’s the ERP technical lead at Byza.
Emma: What did he say?
Ryan: He stated, and I’m paraphrasing a bit here, but he said they identified that Insight Works apps would address most of VIPA’s standard operational requirements with minimal custom development. And this enabled his team to focus all their custom development strictly on the container specific business processes, while relying on the proven Insight Works solutions for the basic warehouse management.
Emma: Okay, I see where this is going now. It’s all about the strategic allocation of your developer brainpower.
Ryan: Exactly the point. Think about the underlying mechanics of any warehouse. Scanning a barcode, sending that data over WI fi, integrating mobile devices.
Emma: Stuff everyone has to do.
Ryan: Yeah, those are incredibly complex things to program from scratch, but they are universal. Literally every modern warehouse does them right. If the developers at by’s SA spent all their time coding the basic physics of how a scanner talks to a server, they would burn through their whole budget before they ever got to VIPA’s
Emma: actual unique problem, which is the complex logic of the containers themselves. It’s like. It’s like trying to run a highly specialized custom bakery, but you decide you need to spend 80% of your time mining your own salt and milling your own flour. Yes, you just buy the flour off the shelf so you can focus all your Energy on perfecting the actual recipe.
Ryan: That is the perfect analogy. You leverage proven out of the box solutions for the foundational tasks so you can hyper focus your custom engineering strictly where it creates real competitive business value.
Emma: Okay, the build versus buy strategy makes total sense when you break it down like that. Buy the foundational warehouse physics, build the custom container logic on top of it.
Ryan: Exactly.
Emma: So let’s look at the actual tools that executed this vision. Because a strategy on a whiteboard is great, but how did they actually shrink those agonizing multi day inventory counts down to just a few hours?
Ryan: Right, let’s get into the mechanics. It begins by fundamentally changing where the data enters the system.
Emma: Okay.
Ryan: Instead of data entering at a desk, you know, hours after an event happened out in the yard, you put the system directly into the hands of the workers on the floor.
Emma: Ah, I see.
Ryan: VIPA deployed several targeted apps from Insight Works that run natively inside their Business Central ERP. And the flagship application they used for this is called Warehouse Insight.
Emma: And just to clarify for everyone listening, we are not talking about a desktop application here. This is built specifically for mobility.
Ryan: Yes, absolutely. The warehouse teams were equipped with rugged mobile devices running this app. So it allows them to execute all their queue core tasks. Receipts, putaways, picks, movements, shipping, all in real time right there on the floor.
Emma: Let’s actually define some of those terms for anyone listening who might be outside the logistics world. When the case study talks about optimizing putaways and picks, what are we actually describing happening on the floor?
Ryan: Sure. So a putaway is the process of receiving new material and finding the optimal place to store it.
Emma: It’s not just dropping a pallet wherever there’s an empty spot.
Ryan: No, definitely not. Yeah, the system logic dictates exactly where it should go based on things like turnover rates or weight, so it doesn’t accidentally block tomorrow’s shipments.
Emma: Okay, and a pick.
Ryan: A pick is just the reverse. It’s grabbing the exact right materials from the warehouse to fulfill a specific customer order.
Emma: Got it. And with this Warehouse Insight app, the moment a forklift driver completes a putaway into a specific container, they scan it and the master ERP system knows about it instantly, instantaneously. The brain and the muscle are finally synchronized.
Ryan: Instant synchronization at the item, lot and container level. Which actually leads us directly to the second major application they used, which is called Advanced Inventory Count.
Emma: Okay, what does that do?
Ryan: This is the tool that cured the multi day counting headache. It replaced all their chaotic paper based audits with what the case study calls Structured physical and cycle counts.
Emma: And a cycle count, just to be clear for you listening, is when you count small, specific sections of your inventory on a regular rotating basis throughout the year, rather than, you know, shutting down the entire facility once a year to count every single thing at once precisely,
Ryan: it’s way more efficient. The app allows for multi user entry, flexible count sheets, and it automates the reconciliation of all those really complex lot and serial numbers.
Emma: Here’s where it gets really interesting to me. Yeah, the case study notes, they went from taking two or three days to complete an inventory count to just a matter of hours, and they achieved that with fewer staff members.
Ryan: It’s a huge leap.
Emma: I want to drill down into the mechanics of that. How exactly does simply handing a worker a mobile scanning device literally shave days off a physical counting process? What is the actual mechanism driving that massive time reduction?
Ryan: It is a really great question because it’s not just about typing numbers into a screen instead of writing them on a piece of paper. It is about fundamentally eliminating the secondary and tertiary tasks that paper inherently creates.
Emma: Okay, walk me through that.
Ryan: Let’s trace the life cycle of a manual account. First, a worker walks the floor, finds a container, and writes down a lot number. That takes time. Second, they have to physically transport that clipboard all the way to the back office. More time. Third, an administrator has to try and read their handwriting and manually type those numbers into the ERP system.
Emma: Which introduces a massive opportunity for human error. Like typing a 5 instead of an 8 or just missing a decimal point completely.
Ryan: Exactly. And that error is where the real time drain happens. Because once that typo goes into the system, the ERP realizes there is a discrepancy between what was just typed in and what the system thought was supposed to be in that container.
Emma: Right. So what has to happen next?
Ryan: Someone has to put their boots on, walk all the way back out to the warehouse floor, and physically double check that specific container.
Emma: Ugh. Yes. You become trapped in this endless, miserable loop of paper shuffling, manual data entry, error generation, and physical double checking.
Ryan: It’s awful. But what advanced inventory count does by utilizing mobile devices and barcode driven workflows is collapse all those separate steps into a single real time action. A worker scans the barcode on the container. The mobile device instantly pings the central database over WI fi. The database runs a validation check in milliseconds.
Emma: Okay.
Ryan: And if there is a discrepancy, say the scanner reads lot A, but the system expects lot B. The device alerts the worker immediately. Right there on the floor.
Emma: Aware. So they investigate and reconcile the anomaly in the moment while they are already standing right in front of the container.
Ryan: Exactly. The mechanism. You aren’t just moving faster. You are entirely removing the layers of administrative friction and error correction that bog down traditional audits. You are solving the problem at the absolute point of origin, rather than waiting
Emma: to uncover the problem three days later buried in a spreadsheet.
Ryan: Precisely.
Emma: That makes perfect sense. So you have given the workers these mobile scanners and the data is finally flowing in real time. But that data flow is only as good as the underlying infrastructure, right?
Ryan: Very true.
Emma: Like, if your background processes are still messy, those fast scanners are just going to feed bad data into your system faster. Which brings us to the next phase of this transformation.
Ryan: Good background infrastructure. Yeah, yeah. The case study highlights three specific tools that are really fascinating because they function as the unsung heroes of this whole operation.
Emma: What are they called?
Ryan: Insight Works calls them power tools. And it’s important to note here that they provide these specific applications as completely free additions to the business central environment.
Emma: Oh, wow. Free is always good. Let’s look at what these power tools actually do, starting with the barcode generator, because remember, Vika used to generate their barcodes in a totally separate program, which is terrifying for data integrity.
Ryan: It’s a huge risk.
Emma: This power tool embeds 1D and 2D barcodes directly into the core business central reports. Now I see 1D and 2D thrown around a lot. Why does upgrading to a 2D barcode actually matter? For a company dealing with massive containers,
Ryan: it really just comes down to data density. A standard 1D barcode, like the UPC code on a box of cereal at the grocery store, that is basically just a license plate. It’s a simple string of numbers that says, I am item 1, 2, 3. But a 2D barcode, like a QR code or a data matrix that can hold vast amounts of embedded information. It can say, I am item 1, 23 from lot 456, I contain 500kg of recycled pulp, and I was processed on this specific date.
Emma: Oh, wow. That makes a huge difference.
Ryan: Yeah. For VIPA, being able to generate that dense data natively inside the system is absolutely crucial for tracking those complex containers.
Emma: That makes sense. The second tool they used is the import export power tool, which the case study notes replaced all their manual, you know, duct tape spreadsheet workarounds with structured, validated bulk data operations directly inside the erp.
Ryan: Super important for keeping the data clean.
Emma: But it is the third tool I really want to highlight Here, because it perfectly illustrates this concept of operational micro frictions. It’s called the Print Node Connector power tool.
Ryan: Ah, yes. This is a seemingly small feature that actually solves a massive architectural headache.
Emma: Right. The underlying issue was that business Central is a cloud based system. The servers are sitting in a data center somewhere far away. But the physical label printers are sitting on local IP addresses right there on the warehouse floor.
Ryan: And standard web browsers really struggle to bridge that gap.
Emma: Exactly. So to print a simple shipping label, workers were having to generate a file, convert it to a PDF, download that PDF to a local machine, open it, and then finally hit print.
Ryan: Which, you know, sounds like a very minor inconvenience.
Emma: It sounds like nothing. Like if you do that once a week in your home office, it takes 10 seconds. It is a tiny paper cut of an annoyance.
Ryan: Right.
Emma: But when you’re moving 450,000 tons of material, multiply that 10 second PDF conversion by 3 thousands of labels a day across dozens of workers, it adds up fast. Suddenly, that tiny paper cut becomes a massive arterial hemorrhage of time and focus. The Print Node connector establishes a secure network bridge. It allows direct cloud printing. No more PDFs. A worker hits print on their scanner and the label instantly comes out of the printer on the floor.
Ryan: If we connect these power tools to the bigger picture, you know, this is fundamentally a story about system integrity. These aren’t just minor quality of life upgrades, they are structural necessities. Yeah, when you have disconnected background processes, you are just inviting chaos into your database. By standardizing these micro frictions, VIPA ensured that the data feeding their massive logistics machine was absolutely pristine.
Emma: Okay, so we have the heavy lifting apps out on the floor capturing the data, and we have these crucial power tools cleaning up the background infrastructure. How does this all actually culminate?
Ryan: This is the best part, because having
Emma: a bunch of great data flowing in is cool. But if the people in the office can’t easily parse that data, you just have a different kind of mess.
Ryan: Totally. And this brings us to the climax of the whole transformation. How did BYC use this new pristine data? Well, they broke down the data silos and they built a custom user interface, creating a consolidated allocation view.
Emma: The case study refers to this as the OneView transformation. How did they structurally unite this data?
Ryan: It is all about relational database mechanics. So in the past, the sales module and the warehouse module were totally siloed. Okay, If a customer called a sales rep wanting say 50 tons of a specific recycled board product, the rep would have to go on this Digital scavenger hunt.
Emma: Sounds fun.
Ryan: Not at all. They would check one screen to see if they technically owned the product, another screen to see where it might physically be, and then they’d likely have to make a phone call to the warehouse manager just to verify that a forklift driver hadn’t already moved it for someone else’s order.
Emma: Because the inventory in the system was essentially just theoretical. Until a human manually confirmed it.
Ryan: Exactly. But by unifying the environment, the custom UI allows the sales module and the warehouse module to query the exact same datadress tables simultaneously with zero latency.
Emma: Wow.
Ryan: A sales rep can pull up a single consolidated view directly inside Business Central. They can see the available containers, the exact lot contents, and critically, the real time reservation data.
Emma: So they aren’t guessing anymore?
Ryan: No guessing. They are querying the exact barcode that a forklift driver scanned five seconds ago. They can make informed allocation decisions instantly, knowing with absolute certainty that the container is actually there and available.
Emma: So what does this all mean for the actual people working at VIPA Hellas? The case study notes the system was fully deployed in Q2 of 2025. Picking accuracy, skyrocketed. Operations were fully digitized, and as we discussed, counts shrank from days to hours.
Ryan: Huge wins all around.
Emma: But here’s the detail that stood out to me the most.
Ryan: What’s that?
Emma: Usually, when corporate management drops a massive new digital system onto a warehouse floor, morale plummets. Change management is notoriously difficult. Workers often feel like the new software is just an administrative burden getting in the way of their actual jobs.
Ryan: Very true.
Emma: Yet the case study explicitly states that user adoption went, quote, better than expected, and the client gave the deployment a perfect 5 out of 5 rating. Why? Why didn’t the warehouse staff rebel against this new system?
Ryan: It’s a great question. And it’s because the new environment provided something workers deeply appreciate when it’s done right. It provided clear, logical structure that actually matched their reality. Okay, this wasn’t a case of management forcing a generic, rigid piece of software onto a complex business and demanding the workers change their habits to appease the computer. The brilliance of what BY’s and Insight Works achieved was building the software architecture around the actual physical shape of the business.
Emma: They built it around the container.
Ryan: Yes, the system was designed from the ground up to think in terms of containers, just like the warehouse workers do every single day.
Emma: That makes so much sense.
Ryan: When your digital tools natively understand the physical reality of your workday, it doesn’t feel like an imposition. It feels like a relief. The workers weren’t fighting the system’s logic anymore. The system was finally supporting their actual workflow.
Emma: It is the stark difference between software acting as a chore and software acting as a true tool. You can really hear the impact of that relief in the concluding quote from Charlampos Chattadamianos, the CFO of VIPA Hellas. He stated, before implementing the solution, we struggled with limited visibility and control over our container based warehouse operations. With Warehouse Insight and the supporting apps, we now have real time structured processes and full traceability across all operations.
Ryan: I mean from an operational standpoint, that is a journey from darkness into light. Going from limited delayed visibility to full real time traceability is a monumental shift for a company manager managing 450,000 tons of physical inventory.
Emma: It really is an incredible blueprint. So to quickly recap this journey for you listening VIPA Hellas started with a chaotic, disconnected, multi day inventory nightmare. Their digital brain and their physical muscle were completely divorced. But by utilizing targeted Microsoft and Insight Works integrations, basically buying the proven Warehouse foundation so they could focus their engineering on building the custom container logic, they turned that chaos into a seamless real time digital machine. They brought the digital map and the physical territory back into perfect alignment.
Ryan: Which naturally leads to a much broader and frankly provocative question about the future of enterprise software.
Emma: Oh, what’s that?
Ryan: Well, if a complex recycling plant dealing with hundreds of thousands of tons of physical scrap material can achieve perfect real time digital traceability, what happens next? Right as artificial intelligence becomes more deeply integrated into these ERP Systems, these unified OneView dashboards are really just step one.
Emma: Oh, I see what you mean. Once the map perfectly matches the territory in real time, the AI can actually take the wheel.
Ryan: Exactly. The next step isn’t just human sales reps making better allocation decisions, it is the software itself predicting bottlenecks, analyzing historical flow, and autonomously routing containers before the forklift driver even turns the key in the ignition.
Emma: That is a fascinating thought to leave on. Once you cure the data disconnect, you open the door for true predictive automation. It really makes you look at your own workflows and wonder where the digital map is failing the physical territory, and what you might be able to achieve if you finally connected the two.
Ryan: Absolutely.
Emma: Well, we hope this deep dive gave you some valuable new frameworks to think about your own processes and maybe inspired you to stop playing blindfolded Tetris with your own inventory. Thank you so much for joining us as we unpack this case study and keep looking for those hidden connections in your own work until next time.
