De-automotive diversification and ERP boundaries
Source：宁德时代开始“去车化”（百度热搜）
A Baidu trending headline today reads: CATL has begun “de-automotive” diversification (“去车化”). The title does not spell out concrete steps, but for operations and IT leaders in manufacturing, that kind of signal usually means customer mix and product lines are shifting—not just marketing language. The first systems to strain are rarely report cosmetics; they are master data, order fulfillment, and who owns which inventory.
What “de-automotive” looks like in software
When revenue is less tied to a single downstream industry, part numbers, BOM revisions, and customer cross-references multiply quickly. Teams that still rely on spreadsheets or modules built for one segment often see the same pattern: sales quotes customer nomenclature, the warehouse ships on legacy internal codes, and finance cannot reconcile batches at month-end. Fixing that is not “buy one more module.” It starts in ERP by defining org, warehouse, and costing dimensions: shared stock vs. customer- or project-isolated stock, and which semi-finished goods may transfer across lines.
A practical gate: list three object types you expect in the next twelve months—new customer industries, new product families, new subcontractors. If any type lacks an auditable order type + issue policy + cost path in the current system, put master-data and process design ahead of feature coding.
Orders and approvals outlive the old customer profile
Mixed industries break pricing, credit, delivery promises, and change control when rules silently stay “auto-tier.” Non-auto programs often differ on acceptance, billing milestones, and reconciliation cadence. Approval flows designed for one program either block shipments or drive decisions offline. Map the order lifecycle in swimlanes—create, reprice, freeze, ship, invoice—then check whether the ERP can configure it before custom UI work.
For reconciliation, agree early how revenue ties to shipment: ex-warehouse, customer receipt, or milestones. Divergent lines force consolidated reporting into spreadsheets and raise control cost.
Inventory visibility when capacity is shared
Diversification often reshapes capacity and replenishment: one line serving multiple order families cannot run one safety-stock parameter. You need available-to-promise views by warehouse + order family + project, with explicit reservations. MRP driven only by historical auto demand will keep producing “on paper but not movable” stock for new lines.
Write interface ownership into an integration brief: which system is system-of-record for status changes when custom software and integrations connect WMS, MES, or customer portals—so you do not get bidirectional silent edits.
Pace the investment
Strategic diversification does not require betting everything on a big-bang replacement. Run one or two pilot product lines through a closed loop—master data, orders, inventory, costing—then clone templates. Full ERP and commerce-scale programs often sit in a multi-month band; if pain is concentrated in approvals, reconciliation, or stock sync, shorter automation phases may come first.
If customer-structure change is forcing you to redraw inventory and order rules, start with a structured requirements pass via contact. Fixed-scope work can be quoted after written discovery; evolving programs can run milestone-based. Source code, data, and design stay with you; engagements stay confidential by default.
Related headline: CATL begins “de-automotive” diversification (Baidu hot search). This note discusses generic manufacturing systems implications from a public title only; it is not investment or operating advice about any company.