Intellore LogoIntellore
Back to All Success Stories
Case StudyERP & Digital OperationsOct-26

The Missing Middle

How a leading consumer brand company gave its third-party plants a shop floor it could finally see, without putting the brand's corporate ERP on every one of them.

Every Batch, Traceable
The Missing Middle - Industry-Specific case study hero image

Client

$2B Consumer Products Brand

The batch nobody could vouch for

It is the start of the morning shift at a contract plant. A truck of packing material has just backed into the dock. The purchase order behind it lives in the brand's corporate ERP. Everything that happens next lives on paper.

The store clerk writes the receipt in a register. The quality inspector tests a sample and notes the result on a sheet. Production pulls the material, runs the line and records output in a spreadsheet. By the time the finished goods leave for the brand's distribution center, the batch has passed through four sets of hands and three formats, and not one system.

Now multiply that by every contract manufacturer the brand relies on, across their consumer product line. Then ask a simple question: if a batch goes wrong, how fast can you find every pallet it touched?

Now try answering:

•What are we producing right now?
•How much are we producing?
•Where is our inventory?
•Which batches are available?
•How much can each manufacturing location produce?

Those questions are where this story starts.

The challenge: a brand that could see the purchase, but not the plant

The brand had done the hard part already. Through the brand's corporate ERP, provisioned and managed centrally, they could see raw material movement shipping out and finished goods shipping into their distribution centers.

In between, the trail went dark. Between the delivery note receipt and the finished pallet sat production planning, quality inspection and batch control. At the plants, those ran on registers, spreadsheets, phone calls and WhatsApp.

The gap showed up in three places:

•Traceability. Linking a finished batch back to the material lots that went into it meant reading paper, plant by plant.
•Quality release. An inspection result did not stop a batch from moving. Holds depended on people remembering.
•Visibility. Category heads and regional teams saw what had been bought and shipped. They could not see what was being made, held or rejected today.

The obvious fix was to extend the corporate ERP's production and quality modules to every plant. The brand wanted the capability without the cost and weight of that footprint at each third-party site. It needed something lighter that would still behave like part of the corporate ERP.

Act one: prove it in one plant

Intellore did not start with a network-wide plan. It started with a single plant.

The pilot ran ERPNext's manufacturing and quality modules against real orders. Goods receipts carried batch numbers from the dock. Work orders drew on those batches. Quality inspections sat at three points: incoming material, in-process on the line, and finished goods before dispatch. A failed inspection stopped the batch, in the system, not on a sticky note.

Pick any finished batch and walk it back to the receipt and the supplier lot from one screen.

The pilot answered the question nobody could answer before. It also taught the team what to change before scaling:

•Configuration beats customisation. Most of what the plant needed was standard ERPNext, set up well. Custom code was kept for the corporate ERP touchpoints and the brand's approval rules.
•Masters are the real project. Item codes, BOMs and naming series that did not match the corporate ERP caused more friction than any screen.
•The plant needs one reason to log in. When the work order arrived in the system ready to run, operators used it. When it had to be keyed in, they did not.

Act two: the architecture turn

The first scaling design gave every plant its own ERPNext site and its own database. It looked clean. It also meant dozens of copies of the same item master, dozens of copies of the same BOMs and dozens of places for them to drift apart.

So the design changed. All plants now share one ERPNext portal, and common BOMs and items are maintained once. Each plant sees only its own orders, stock and inspections through role-based permissions.

Three rules kept the portal honest about ownership:

•No money in the portal. It records quantities, batches and quality status. It posts no valuation and no accounting entries. Costing, valuation and reconciliation stay in the corporate ERP.
•Local material is tracked, not valued. Material a plant buys itself is recorded by quantity and batch, so traceability holds without pretending it is the brand's stock.
•Separate naming series per plant. Every document number says whose it is, so traceability never depends on a filter.

The trade-off was stated plainly to the client. One shared database is cheaper to run and keeps masters consistent. In exchange, separation between plants lives in the application's permissions, not in separate databases, and a restore applies to the whole portal. The brand chose that trade with its eyes open.

Built for the 3 a.m. question

In an early architecture review, the client's IT team asked the question every enterprise asks: what happens if the server goes down?

It was a fair challenge. The first infrastructure design had been sized for performance, not availability. Intellore did not defend it. The team rebuilt the answer around recovery targets the business could understand. The brand chose with the cost of downtime in front of it, not after the first outage.

The security posture was tightened at the same time. The database server has no public IP and accepts connections only from the application tier. Traffic between tiers is encrypted, storage and backups are encrypted at rest, and data residency follows the brand's own policy.

What changed

Go back to the truck at the dock. Today the receipt carries a batch number the moment it lands. That batch can be followed through the work order, the line inspection and the delivery note to the brand's depot, and back again.

•Traceability you can act on. Any finished batch traces back to its material lots and forward to its dispatches, across plants, from one system.
•Quality that holds the line. A failed inspection blocks the batch in the system. It cannot be issued or dispatched until someone with authority releases it.
•One chain with the corporate ERP. Orders start there and results return to it. The brand's finance and costing never moved, and plants kept their own books.
•No corporate ERP footprint at the plants. Production and quality run on ERPNext, with no corporate ERP production or quality licences extended to third-party sites.
•A repeatable onboarding. The pilot became a playbook. Each new co-packer is a new Company on a proven portal, not a new project.

Running production through partners you don't own? If your contract manufacturers are a black box between the purchase order and the depot, we have built the bridge before. Talk to us at hello@intellore.com.

Technology

ERPNext

Industry

$2B Consumer Products Brand

Ready for Your Success Story?

Let us work together to create transformative solutions for your business.

Get in Touch