A spreadsheet can hold a stock count. It cannot stand at a packing station and tell an operator which cartons belong on which pallet. That gap is why a manufacturing and logistics company asked TNH Technology for custom warehouse software. The client name stays private. The system finished in October 2024, after eight months, with nine people on the team.
This is a case study of that build, not a product brochure. The work was custom software development for one operation: pallet assignment, carton assignment, and the stock those assignments depend on. If your floor still runs the same job from a shared file, the shape of the problem will be familiar even if the screen you need is different.
Why the spreadsheet stops working
Warehouse work is a sequence of small decisions. A carton arrives, or it is ready to leave. Someone decides which pallet it joins. Someone else needs the count to be right before the truck goes. When those decisions live in a spreadsheet, three things drift apart: the file, the floor, and the person who last edited the file.
The file is usually right at the moment someone saves it. It is wrong as soon as a carton moves and the sheet does not. Two shifts can each keep a version. An assignment written in the morning is a guess by the afternoon. The operator then spends time checking, not packing.
Custom warehouse management software exists to close that gap. The screen at the station and the stock record are the same system. The assignment is calculated, then shown, then stored. A person still confirms the work. They are no longer the only place the count lives.
Client challenge
The client needed a warehouse system that could assign pallets and cartons and keep the stock behind that assignment current. The public record of the job is the warehouse case study. The operation was manufacturing and logistics. The process in place was manual.
Manual assignment does not scale with the number of cartons. Each new size, each rush order, and each partial pallet adds a decision that used to sit in someone's head or in a sheet. When the sheet and the floor disagree, the error shows up as a recount, a rework, or a load that does not match the plan.
Visibility was the other half of the problem. A count that is updated at the end of a shift is a report about the past. The station needs the count now, for the pallet in front of the operator. Without that, assignment becomes a debate about which file is current.
The limitation is not that people on the floor are careless. The limitation is that a spreadsheet has no place in the workflow. It does not know the nesting rule. It does not update because a carton was placed. It cannot be the screen someone opens fifty times a day.
Business requirements
The system had to do a short list of jobs well.
- Show pallets and cartons as live stock, not as a sheet saved earlier.
- Assign cartons onto pallets with a nesting calculation, and keep that assignment with the stock it depends on.
- Give the operator one screen at the station, in the order of the work they already do.
- Keep the record accurate enough that the next person trusts it without opening a second file.
Reporting, in this project, is that screen. The operator watches stock and the assignment. We have not published a separate analytics product for this client. The requirement was the floor's view of the work, current at the moment they look.
Solution architecture
The stack is .NET, C#, WCF, WPF, and SQL. WPF is the desktop application on the floor. WCF is the seam between that screen and the services behind it. SQL holds the pallets, the cartons, and the assignments. Linear programming is the nesting method the case study records for the assignment calculation.
Operator screen (WPF desktop)
|
WCF
|
Application services (.NET, C#)
|
SQL database
pallets, cartons, assignments
That is a plain layout of what shipped. It is not a diagram of every class in the solution. Nine people worked across the screen, the services, and the database for eight months. The finished system is the one described in the case study.
Key features delivered
Pallet assignment
The application assigns cartons onto pallets. The nesting calculation proposes how the load sits. The point on the floor is a decision the operator can follow, stored with the pallet, instead of a layout redrawn from memory at the start of each shift.
Carton assignment
Cartons are the unit being placed. The stock record tracks them so the assignment is about real cartons, not a typed quantity that might already have moved. Assignment and stock stay in one system.
Live inventory
The case study describes real-time inventory tracking for pallets and cartons. Live stock is what makes the assignment usable. A perfect layout against yesterday's count is still the wrong layout.
Operator screen
The interface is a WPF desktop application. It is the screen at the station. It shows the work: stock and the assignment. It is not a phone app and it is not a report portal. The person using it is standing or sitting at that station, opening the same program through the shift.
What the floor watches
There is no separate reporting suite in the published account of this project. What the floor watches is the same screen: which stock is there, and which assignment goes with it. That is the monitoring that matters at the station. A management report can be a later piece of enterprise software if the operation asks for it. It was not a claimed deliverable of this build.
Nesting logic
The assignment rule is a nesting calculation, recorded in the case study as linear programming. It is the business rule for how cartons go onto pallets. It is not a general rules-engine product that an administrator retunes from a menu. The rule lives in the application, next to the stock it uses. A person still confirms the result on the screen.
That nesting step is also the honest link to AI and automation on our site. The automation we can show here is a repeated assignment rule inside software the floor already opens. It is not a model sold apart from the operation.
Why the floor got a desktop application
The operator is at a station. The work is a full screen of stock and assignment, used all shift, on a machine that stays put. WPF fits that. A browser page would have been a second choice for a person who is not walking the aisle with a phone.
Mobile app development is the right conversation when the person is away from the desk: a check in the yard, a collection, a confirmation off the station. This floor job stayed on the desktop because that is where the operator already stood. Moving it to a phone would have copied the screen into a worse place.
How the eight months were spent
The engagement ran eight months. The team was nine people. We do not publish a sprint diary for this client. What we can say is how a build of this kind is divided, and what this one contained.
Discovery
The first job is the operation itself. Who stands at the station. What a pallet and a carton mean in that building. Which assignment has to be right before a load leaves. A project with TNH starts with that note, a reply within one business day, a call, and a written plan.
Design
The screen, the WCF seam, and the SQL record are designed together. A handsome layout that does not match the stock model becomes a second spreadsheet. The operator's path is the assignment they repeat, not every report someone might want later.
Development
The build is C# on .NET: the WPF application, the services behind WCF, and the database.
Testing
The test that matters is whether the assignment on the screen matches the cartons and pallets in the database. We have not published a defect count for this project. The standard is the operator's: they can follow the assignment without opening another file to check it.
Deployment
The finished application is a desktop program on the floor. It was done in October 2024. The client name remains withheld. The case study is the public account.
Support
After a system is in use, we reply within one business day. Urgent production issues on a system we already support are handled first. That is the support line. It is not a promise of a measured uptime figure. We have not published one for this client.
What changed for the floor
We are not going to invent a percentage. There is no published figure for hours saved, error rate, or cost removed. What the system changed is the shape of the work.
- Stock is visible in the application, at the station, rather than in a sheet that lags the floor.
- Assignment is a calculation the operator can follow, rather than a manual layout redone from memory.
- The person at the station has one screen for that job.
- The assignment and the stock it uses are stored together, so the next shift is not reconstructing the last shift's file.
Those are the outcomes we can stand behind. If a later conversation needs a measured baseline, that baseline has to come from the operation's own counts, not from a case study sentence.
Why a company commissions custom warehouse software
A packaged warehouse system is a fit when the floor already works the way the package assumes. This client needed assignment logic and a screen for their own pallets and cartons. That is the usual reason to commission warehouse software development instead of configuring a suite and hoping the exceptions stay small.
Custom means the workflow can match the station. It also means the service seam is yours. WCF was that seam here, between the desktop application and the services. A later system can sit on the same idea: keep the screen the operator trusts, and connect the services you already run. We have a separate example of that kind of connection. In November 2025 a UPS integration added labels, rates, address checks, and tracking to an existing .NET stack. Five months, four people. It is a carrier integration, described in the UPS case study, not a feature of this warehouse screen. Logistics software on our site is the pair of those two jobs: the floor, then the carrier.
The long-term reason to own the system is practical. The nesting rule, the stock model, and the screen can change with the operation, with the team that built them. That is the return. We are not going to print a number for it.
PalletIQ is not this system
PalletIQ is a standalone pallet calculation tool. The warehouse system in this case study is the operational software: assignment, live stock, and the desktop screen. PalletIQ is free, it runs in the browser at palletiq.in, and it does not ask for an account. You enter a carton and a pallet. It returns cartons per layer, layers, and how many pallets the load needs.
Use the calculator when the question is the load. Read the PalletIQ page for what it returns. Hire us when the floor needs the system around that question. The calculator does not assign stock on a station, and it does not replace the October 2024 application.
Need custom warehouse, manufacturing, logistics, or enterprise software? Book a project call with TNH Technology. Tell us the role, the timeline, and the budget. We reply within one business day.