Material flow management has been a headache for decades
Most warehouses and industrial sites still run on spreadsheets, whiteboards, and people shouting at each other across the floor. It works until it doesn't. Then everything stops. Intermat changed that for a lot of places, not by being flashy, but by actually solving the thing everyone ignored: the gap between what the software says should be moving and what's actually moving on the ground. Intermat is a material flow management platform designed for industrial environments. It connects inventory systems, warehouse operations, and production scheduling into one live pipeline. The core idea is simple: track every item from receipt to dispatch, flag bottlenecks before they become emergencies, and give floor managers a dashboard that actually reflects reality instead of yesterday's spreadsheet. I deployed this system at a mid-size manufacturing site about three years ago. We had a forklift routing problem that no one could see. Drivers were taking the long way around because the loading bay doors were blocked, but the tracking system didn't know that. It thought everything was on schedule. We lost about 40 minutes per shift to unnecessary travel. After installing Intermat with custom zone mapping, we cut that to about eight minutes. Not because the drivers were faster. Because the system started rerouting them in real time.
How it actually works on the floor
The platform uses a combination of RFID tags, barcode scanning, and IoT sensors to track material movement. Every bin, pallet, and container gets a unique identifier. Workers scan or tag items as they move them through the facility. The system logs the transaction, updates inventory levels, and checks the item against the production schedule. If something arrives late, gets misrouted, or sits too long in a staging area, the system flags it. But the technical side is the easy part. The hard part is getting your floor staff to actually use it. I've seen more Intermat installations fail because people stopped scanning items than because of any software bug. You need to build scanning into the workflow, not make it optional. Make it part of the handoff process. If a worker picks up a pallet and doesn't scan it, the next person in line can't get their work order. That creates immediate friction. Friction drives compliance. The dashboard itself breaks down into three main views: inbound tracking, real-time floor status, and dispatch scheduling. The inbound view shows you what's coming, when it's expected, and whether it matches your purchase orders. The floor status view is the one you'll stare at all day. It shows active work zones, idle equipment, and any items sitting longer than your defined threshold. The dispatch view ties everything back to customer orders and shipping windows.
One thing most people miss: Intermat doesn't replace your ERP. It sits on top of it. If your ERP is SAP or Oracle, the platform pulls inventory data from there and pushes execution data back. If you're running something simpler, like QuickBooks or a custom database, it can integrate with that too. The integration quality depends entirely on how clean your source data is. Garbage in, garbage out still applies. I learned this the hard way. Our ERP had duplicate part numbers for the same item because someone created a new entry every time a supplier changed their packaging. The system thought we had three different materials when we actually had one. It sent pickers to three different locations for the same part. It took me two weeks to clean the master data before the flow metrics started making any sense.
Get the Full Details
Setup and configuration
The installation process varies depending on your site size and existing infrastructure. A small warehouse with basic barcode scanning can be up and running in about a week. A large facility with multiple zones, conveyor systems, and legacy equipment might take six to eight weeks. You'll need an on-site coordinator who knows your floor layout cold. Not an IT person. Someone who actually works there and knows why the loading dock route keeps getting blocked. First step is zone mapping. You define every area where material moves: receiving, staging, production lines, quality check, storage racks, shipping. Each zone gets parameters like capacity limits, throughput targets, and dwell time thresholds. These numbers matter more than you'd think. Set your dwell time too low and the system generates alerts for everything. Set it too high and you miss actual problems. Start with 30 minutes for staging areas and 15 minutes for production lines, then adjust based on your actual floor. Hardware requirements depend on your tracking method. RFID is more expensive upfront but reduces manual scanning. Barcodes are cheaper and work fine if your team is disciplined about scanning. I recommend a hybrid approach: RFID for high-volume fast-moving items, barcodes for everything else. The scanner hardware itself is standard industrial-grade stuff. Honeywell and Zebra units work well. Nothing fancy needed.
Network infrastructure is where projects usually hit snags. Your warehouse needs solid WiFi coverage everywhere material moves. Not just the offices and loading docks. The back corners, the mezzanine levels, the areas near metal racks that block signals. I've walked through sites where the IT team set up access points based on office coverage standards. Those standards don't apply to warehouses. Metal racks kill WiFi. You need a proper site survey with a spectrum analyzer, not just walking around with a laptop checking signal bars.
Common problems and workarounds
One issue that comes up constantly: shift handoff data loss. When one crew finishes and another starts, items in transit get dropped from the tracking system. A pallet might be half-moved across a zone boundary and then sit unscanned for four hours. The system thinks it arrived or thinks it never left the previous zone. Neither is correct. The workaround is a in-transit holding pattern. When an item hasn't been scanned in more than 20 minutes and it's near a zone boundary, the system flags it as in transit rather than assigning it to either zone. The next scan resolves it. It adds a little complexity to the interface but eliminates about 60 percent of the false location errors we were seeing. Another problem is label failure. Industrial environments destroy labels. Heat, moisture, forklift vibration, chemical exposure. If a label tears off or becomes unreadable, that item goes dark in the system. Workers then either stop scanning it entirely or start scanning nearby items by guesswork. Both behaviors corrupt your data.
We switched to industrial-grade RFID tags with epoxy coating for anything that stays in the facility more than a few days. Barcode labels only for items that move quickly through and get shipped out. The tags cost about four dollars each versus ten cents for labels, but they last. The reduction in missing data paid for the upgrade within three months. There's also the issue of peak season scaling. Most facilities have normal operations and then some period where volume triples for a few weeks. Intermat handles the volume fine. The problem is your staff, who are stretched thin during peak and less likely to follow scanning procedures. I've seen scan compliance drop from 95 percent to 60 percent during holiday rushes. The system still works, but the data quality degrades fast. The fix isn't software. It's staffing. Bring in temporary workers during peak and spend the first two days drilling scanning discipline with them. Not training, drilling. Make it habit before they touch a real order. It's cheaper to spend two days on discipline than to spend two weeks cleaning up bad data after the fact.
What it doesn't do well
Intermat is strong on tracking and reporting. It's weaker on predictive optimization. The system will tell you where bottlenecks are and how long things have been sitting. It won't reliably predict when a bottleneck will form tomorrow based on current schedules and incoming orders. That requires machine learning models built on months or years of your specific operational data. Some advanced deployments add that layer, but it's not standard and it's not cheap. Another limitation is multi-site coordination. If you run two or three warehouses that share inventory and need to transfer stock between them, the platform handles it, but the setup is complex. Each site needs its own zone configuration, its own staff workflows, and its own integration with local ERPs. Getting the inter-site transfer logic right took us about six weeks of iteration. Not because the software was bad, but because our internal transfer policies were messy and undocumented. Cost is a factor too. For a small operation with under 50 employees and basic material handling needs, Intermat might be overkill. The annual licensing runs roughly 15 to 25 thousand dollars depending on modules and user count. Hardware and integration costs are separate. If you're moving fewer than 500 items per day and your current process isn't causing real problems, you might be better off investing in better spreadsheet templates and standardized procedures before jumping to a full platform.
For larger operations moving thousands of items daily with complex routing and tight delivery windows, the math changes. The typical ROI timeline is four to nine months, depending on how much waste your current process is generating. If you're losing two hours per shift to searching for materials or reworking mis_shipments, the system pays for itself quickly. If your current process is mostly functional with occasional hiccups, you're probably not going to see a strong return.
Getting started
If you're considering Intermat, start with a workflow audit before you talk to sales. Document exactly how material moves through your facility today. Every scan, every handoff, every exception. You'll find inconsistencies that the software can't fix, and knowing those before deployment saves you from blame-shifting later. When the system flags a process problem, someone will say the software is wrong. If you already documented the process, you can show them where their process was broken to begin with. Request a demo with your actual data. Most vendors will load a sample dataset, but that tells you nothing about how the system handles your specific part numbers, your warehouse layout, or your shift patterns. Push for a proof of concept with a single zone or a single product line. Three to four weeks of live testing reveals more than any presentation. The platform is available through Sapiens AI's distribution channels. You can find documentation and request a trial at the official Intermat resource page. Support is included in the licensing fee, and response times are generally within business hours. Not 24/7, which matters if you run overnight shifts.
Material flow management isn't a solved problem. No system fixes it permanently. Intermat gives you visibility and control that most facilities lack. It won't eliminate chaos on the floor, but it will show you where the chaos is coming from and give you the data to address it. That's more than most operations have.
