When manufacturers diversify, ERP breaks first at the boundaries
Source:宁德时代开始“去车化”(百度热搜)
A Baidu trending headline says CATL has begun “de-automotive” diversification. The title does not list concrete steps. For manufacturing IT and ops, that kind of signal usually means customer mix and product lines are changing. Report cosmetics rarely fail first; master data, fulfillment and inventory ownership do.
Same parts, more ways to use them
As revenue spreads beyond one downstream industry, part numbers, BOM revisions and customer cross-references grow quickly. Spreadsheets or modules built for a single segment tend to fail the same way: sales quotes in customer language, warehouses ship on legacy codes, finance cannot close batches. That is not fixed by buying one more module. In ERP you first define org, warehouse and costing dimensions: shared vs isolated stock, and which WIP may move across lines.
A simple gate: write down three object types you expect in the next year — new industries, product families, subcontractors. If any lack an auditable order type + issue policy + cost path, put master data and process work ahead of feature coding.
Orders still follow the old customer profile
Mixed industries break pricing, credit, lead times and change control when rules stay “auto-tier” by default. Non-auto work often differs on acceptance and billing. Approvals designed for one program either block ships or push decisions offline. Map create → reprice → freeze → ship → invoice, then check whether the ERP can configure it before custom screens.
Agree early how revenue ties to shipment: ex-warehouse, receipt or milestones. Divergent lines push consolidation into spreadsheets.
Shared capacity needs visible stock
One line serving several order families cannot run one safety-stock parameter. You need ATP by warehouse + order family + project, with clear reservations. MRP fed only by historical auto demand leaves new lines with stock that exists on paper but cannot move.
When integrations touch WMS, MES or portals, write down which system owns each status so two apps do not overwrite each other.
Pilot before a big-bang replace
Diversification does not require betting on a full suite swap. Run one or two product lines through master data, orders, inventory and costing, then copy the pattern. Full ERP work often takes months; if pain sits in approvals or stock sync, shorter automation can come first.
If you are redrawing inventory and order boundaries, contact us for a requirements pass, or skim custom ERP for scope. Fixed-price quotes follow clear scope; milestones fit work that will still change.
Related headline: CATL “de-automotive” diversification (Baidu hot search). This note discusses generic systems issues from a public title only; it is not advice about any company.
ERP Pain Point Discovery & Scope Mapping
If your team is facing similar in-transit inventory loss or cross-system reconciliation issues, book a 30–45 min discovery to map pain points and MVP scope before a written quote.