- Home
- Customer Stories
- Nezone Group
How Nezone Group connects multi-plant steel manufacturing and distribution with exactllyERP
For more than 10 years, Nezone Group has used exactllyERP across a multi-location, multi-plant and multi-warehouse operating environment, connecting production, inventory, costing, dispatch and distribution.
Customer Proof
When one steel business operates through several plants and warehouses
General context for this kind of operation, not a description of any one company’s system.
A single-site manufacturer can hold a good deal of its operating truth informally. The people who made the material are near the people who store it, and the people who store it are near the people who dispatch it. When something does not agree, someone walks across the floor and looks.
A steel business operating through several plants in different states cannot work that way. The material is made in one place, may be stored in another, may be moved to a third before it is sold, and is sold through a channel that is nowhere near any of them. Nobody can walk across the floor. The only thing holding the operation together is the record.
That record has to carry more than quantity. In steel processing, what makes a given piece of stock usable for a given order is a combination of properties — the grade of the material, its size, its thickness and the specification it was made to. Two consignments that weigh the same are not interchangeable if those properties differ. So the record has to keep the properties attached to the stock, in every plant and every warehouse, through every movement, all the way to the invoice.
Add the commercial side and the difficulty compounds. Manufacturing has to agree with inventory; inventory has to agree with what has been promised to a dealer; the promise has to agree with that customer’s credit position; the dispatch has to agree with the weight actually shipped; and the costing has to agree with what the plant actually consumed rather than what it was supposed to consume. Each of those is manageable on its own. Keeping all of them in agreement, across a geographically distributed business, is the real problem an ERP has to solve here.
Nezone Group at a glance
Nezone Group is an Indian steel and engineering manufacturer founded in 1981, with origins in ERW pipe manufacturing in Guwahati. Its own account of its history describes a manufacturing footprint that expanded over the following decades, and it today describes facilities in Assam, Meghalaya, West Bengal, Odisha and Tamil Nadu.
The product range described publicly covers MS and GI pipes, ERW and precision tubes, RHS and SHS sections, CRCA strips, poles, towers, scaffolding, metal crash barriers, pre-engineered buildings and related steel and engineering products. Nezone describes its market reach as a pan-India network of distributors, dealers and retailers.
That is the company. What follows is the Exactlly relationship: Nezone Group has used exactllyERP for more than 10 years, across its manufacturing and distribution operations.
- Customer
- Nezone Group
- Industry
- Iron and steel — tubes, pipes and engineering products
- Founded
- 1981
- Location
- India
- Operating model
- Manufacturing and distribution
- Relationship
- More than 10 years with Exactlly
- Product
- exactllyERP
- Manufacturing
- Multiple plants
- Inventory
- Multiple locations and warehouses
One connected operating record
Built only from the workflows the customer has confirmed run in exactllyERP.
Plan
- Production planning
Make
- Production transactions
- Batch identity
- Yield and scrap
Hold
- Grade, size, thickness and specification-wise inventory
- Multi-warehouse stock
- Inter-plant and inter-warehouse transfers
Sell
- Distributor and dealer orders
- Customer credit-limit controls
Close
- Weighbridge / weight-based transactions and dispatch
- Collections
Running across the whole chain: production costing, with standard versus actual comparison. Costing is not a phase at the end of the sequence — it reads from what the plant, the warehouse and the dispatch actually recorded.
Production across more than one plant
Planning and production transactions in the same environment that holds the stock they create.
From plan to production entry
Nezone runs production planning in exactllyERP, and the production activity itself is recorded there as transactions rather than reported into it afterwards. Production entry happens in the same environment that holds the inventory it consumes and the inventory it creates, across more than one manufacturing plant.
That distinction matters more than it sounds. When production is entered somewhere else and summarised into the ERP later, the ERP holds a description of manufacturing. When production is entered as it happens, the ERP holds manufacturing itself, and every downstream question — what is available, what did it cost, what can be promised — is answered from the same record rather than from a reconciliation between two.
Each production output carries a batch identity. That identity is what allows a specific quantity of finished material to remain distinguishable from other material of the same description as it moves into stock, between locations and out to a customer.
What the run actually consumed
Production costing runs in the same environment, and it is held as a comparison rather than a single figure: standard cost against actual cost. A standard tells the business what a run was expected to consume. An actual tells it what the run consumed. The difference is the operational information — and in steel processing it is often the most useful number the plant produces.
Two specific quantities feed that comparison and are tracked in their own right. Yield records how much saleable output a run produced from the material it took in. Scrap records what did not become saleable output. In a business that buys material by weight and sells product by weight, the relationship between those two numbers is a direct measure of how well the plant is running.
Because yield, scrap and production costing all read from the production transactions rather than from a separate exercise, the costing view and the plant view describe the same events.
A tonne is not enough information
Stock that keeps the properties which decide whether it can fill a given order.
In Nezone’s environment, inventory is not held simply as a quantity. Batch identity is maintained alongside grade-, size-, thickness- and specification-wise inventory.
Those dimensions are the ones that determine whether a given piece of stock is commercially usable. An order for a particular grade at a particular thickness cannot be filled from material of a different specification, however similar the tonnage looks in a summary. Holding the dimensions against the stock is what lets the business answer “can we serve this order from what we already have” without someone physically going to look.
Batch identity does the same job through time. It keeps a specific quantity of finished material distinguishable from other material of the same description, so a consignment remains identifiable as it moves into stock, between locations and out to a customer.
Stock that moves between plants and warehouses
Multiple locations and multiple warehouses, with the movements between them recorded as transactions.
More than one place to hold stock
Nezone operates multiple locations and multiple warehouses in the exactllyERP environment. Stock is held against the place it actually sits rather than as one pooled figure, which is what makes a location-wise view of inventory possible at all.
For a distributed steel business this is the difference between knowing that a quantity exists and knowing whether it is anywhere useful. A tonnage sitting in the wrong state is not available for an order that has to ship this week, and a pooled stock figure conceals exactly that.
The movements between them
Movement between locations is handled in the same environment: inter-plant transfers between manufacturing plants, and inter-warehouse transfers between storage locations. Because a transfer is recorded as a transaction rather than an adjustment at each end, the material remains the same identified stock throughout — its grade, size, thickness, specification and batch travel with it.
That is the mechanism behind the whole distributed picture. A transfer that preserves identity means the record at the receiving location describes the same material the sending location dispatched, without anyone re-describing it.
When the physical movement is measured by weight
Weighbridge and weight-based transactions handled in the same operating environment.
Steel is bought, moved and sold by weight, and weight is where the commercial and the physical meet. The quantity on an invoice has to correspond to the quantity that actually left the premises, and in this industry that correspondence is established by weighment rather than by counting units.
Weighbridge and weight-based transactions form part of the Exactlly operating environment, supporting the weight-driven movement of material and finished goods. Keeping weighment in the same environment as the stock record and the dispatch document is what allows the weight that was measured, the stock that was relieved and the quantity that was billed to be the same set of facts rather than three separate ones that have to be matched afterwards.
From finished stock to the money coming back
Dealer and distributor orders, credit control, dispatch and collections in the same record as the manufacturing that supplies them.
The order and the credit position behind it
Nezone’s distribution operations run in exactllyERP: orders from distributors and dealers are taken in the same environment that holds the finished stock they draw on. Customer credit-limit controls sit with those orders, so a commercial commitment is made against a known credit position rather than against an assumption about one.
Putting the order, the available stock and the credit limit in one environment is what makes the promise reliable. The question a dealer order really asks is whether this material can be committed to this customer — and that has an inventory half and a commercial half. Separating them means answering only one of them.
Dispatch and collections
Dispatch is handled in the same environment, with the weight-based transactions described above, and collections follow in it as well. The chain therefore closes: material that was planned, produced, identified, stored, moved and committed is dispatched and collected against the same record it was created in.
Nezone describes its market reach as a pan-India network of distributors, dealers and retailers. The part of that reach which runs in exactllyERP is the operating part: the distributor and dealer orders, the credit position behind them, the dispatch that follows and the collections that close them.
Business outcomes
What the operating environment carries, across manufacturing, inventory, movement, dispatch and distribution.
Manufacturing
- Production planning and production transactions in one environment across multiple plants
- Batch identity carried on production output
- Yield and scrap tracked against the runs that produced them
- Production costing held as standard against actual rather than a single figure
Inventory and movement
- Stock maintained grade-wise, size-wise, thickness-wise and specification-wise
- Location-wise and warehouse-wise stock rather than a single pooled quantity
- Inter-plant and inter-warehouse transfers recorded as transactions
Commercial and dispatch
- Distributor and dealer orders taken against known finished-stock availability
- Customer credit-limit controls applied with the order
- Weighbridge and weight-based transactions handled with dispatch
- Collections in the same environment as the orders they settle
Across the business
- One ERP environment across manufacturing and distribution
- A connected operation across multiple plants, locations and warehouses
- Production, inventory, movements, costing and dispatch managed in the same operating environment
- Sustained use for more than a decade
Proof at a glance
Manufacturing
- Production planning
- Production transactions
- Multiple plants
- Batch identity
Costing
- Production costing
- Standard versus actual
- Yield tracking
- Scrap tracking
Inventory
- Grade-wise
- Size-wise
- Thickness-wise
- Specification-wise
Locations
- Multi-location
- Multi-warehouse
- Inter-plant transfers
- Inter-warehouse transfers
Dispatch
- Weighbridge / weight-based transactions
- Dispatch
Distribution
- Distributor and dealer orders
- Customer credit-limit controls
- Collections
More than ten years, across a distributed operation
More than 10 years of continued use across a distributed manufacturing and distribution environment reflects sustained operational adoption of exactllyERP within Nezone Group.
Software that does not fit an operation tends not to last that long. Plants get added, product ranges change and channels grow, and a system that makes the daily work harder gets replaced. Continuity through that kind of change is what a decade of use describes.
Related Exactlly capabilities
The product and the sector behind this story.
In the customer's words
We have been using exactllyERP for more than 10 years across our manufacturing and distribution operations. It supports our multi-plant, multi-location and multi-warehouse environment, helping us manage production, inventory, inter-location movements, costing, dispatch and our distribution operations in an integrated manner. Over the years, Exactlly has become an important part of how we manage and coordinate our business.
Running steel manufacturing across more than one plant?
If your business has to keep production, grade and specification-wise stock, several warehouses, inter-location movement, weighment, dispatch and a dealer channel all agreeing with each other, talk to Exactlly about running them on one record.