[{"data":1,"prerenderedAt":319},["ShallowReactive",2],{"blog-auto-dealer-erp-or-crm":3},{"id":4,"title":5,"body":6,"description":306,"extension":307,"meta":308,"navigation":309,"path":310,"publishedAt":311,"seo":312,"stem":313,"tags":314,"__hash__":318},"blog\u002Fzh\u002Fblog\u002Fauto-dealer-erp-or-crm.md","汽贸该上 ERP 还是 CRM？一张表看懂两者边界与衔接",{"type":7,"value":8,"toc":298},"minimark",[9,13,17,22,111,119,123,126,139,146,150,157,168,171,192,196,203,255,262,266,269,295],[10,11,5],"h1",{"id":12},"汽贸该上-erp-还是-crm一张表看懂两者边界与衔接",[14,15,16],"p",{},"汽贸选系统时常陷入「先上 ERP 还是先上 CRM」的争论。其实两者解决的是完全不同的问题，搞清边界就知道该怎么选。",[18,19,21],"h2",{"id":20},"一两者的职责边界","一、两者的职责边界",[23,24,25,41],"table",{},[26,27,28],"thead",{},[29,30,31,35,38],"tr",{},[32,33,34],"th",{},"维度",[32,36,37],{},"ERP（业务+资源）",[32,39,40],{},"CRM（客户+关系）",[42,43,44,56,67,78,89,100],"tbody",{},[29,45,46,50,53],{},[47,48,49],"td",{},"核心对象",[47,51,52],{},"车辆、单据、库存、资金",[47,54,55],{},"线索、客户、跟进记录",[29,57,58,61,64],{},[47,59,60],{},"关注问题",[47,62,63],{},"车在哪、钱多少、赚没赚",[47,65,66],{},"客户在哪、会不会买、何时再买",[29,68,69,72,75],{},[47,70,71],{},"数据特征",[47,73,74],{},"强结构化、必须精确",[47,76,77],{},"半结构化、允许模糊",[29,79,80,83,86],{},[47,81,82],{},"使用角色",[47,84,85],{},"销售内勤、仓管、财务",[47,87,88],{},"销售顾问、市场、客服",[29,90,91,94,97],{},[47,92,93],{},"更新频率",[47,95,96],{},"每笔业务发生必更新",[47,98,99],{},"每次接触后更新",[29,101,102,105,108],{},[47,103,104],{},"失败后果",[47,106,107],{},"账实不符、成本失真",[47,109,110],{},"客户流失、复购下降",[14,112,113,114,118],{},"一句话概括：",[115,116,117],"strong",{},"ERP 管「事和钱」，CRM 管「人和关系」","。",[18,120,122],{"id":121},"二车商最容易踩的坑用-crm-管库存","二、车商最容易踩的坑：用 CRM 管库存",[14,124,125],{},"有些销售型系统以线索管理为核心，顺手做了个「库存列表」。这个看似方便，实际很危险：",[127,128,129,133,136],"ul",{},[130,131,132],"li",{},"库存没有状态机，卖了的车不会自动消失；",[130,134,135],{},"没有单据约束，任何人可以随手改；",[130,137,138],{},"没有成本挂载，毛利算不出来。",[14,140,141,142,145],{},"结果是销售和财务各说各话。同理，",[115,143,144],{},"用 ERP 管线索体验很差","：销售顾问需要的是快速记录与跟进提醒，不是层层必填的单据。",[18,147,149],{"id":148},"三正确的衔接方式","三、正确的衔接方式",[14,151,152,153,156],{},"两个系统应该通过",[115,154,155],{},"客户与车辆","两个主键衔接：",[158,159,164],"pre",{"className":160,"code":162,"language":163},[161],"language-text","线索（CRM） → 客户档案 → 销售订单（ERP） → 车辆出库 → 保有客户（CRM）\n","text",[165,166,162],"code",{"__ignoreMap":167},"",[14,169,170],{},"具体要打通三件事：",[172,173,174,180,186],"ol",{},[130,175,176,179],{},[115,177,178],{},"线索转客户","：成交后客户主数据同步，避免重复建档；",[130,181,182,185],{},[115,183,184],{},"订单反哺","：订单状态回到 CRM，销售看得到跟进结果；",[130,187,188,191],{},[115,189,190],{},"保有客户","：交车后自动进入保有客户池，触发保养提醒与换购跟进。",[18,193,195],{"id":194},"四现阶段该先上哪一个","四、现阶段该先上哪一个？",[14,197,198,199,202],{},"看",[115,200,201],{},"企业当前最大的损失在哪里","：",[23,204,205,215],{},[26,206,207],{},[29,208,209,212],{},[32,210,211],{},"症状",[32,213,214],{},"优先",[42,216,217,225,232,240,247],{},[29,218,219,222],{},[47,220,221],{},"库存经常对不上、卖了车忘了出库",[47,223,224],{},"ERP 优先",[29,226,227,230],{},[47,228,229],{},"毛利算不清、不知道哪台车真赚钱",[47,231,224],{},[29,233,234,237],{},[47,235,236],{},"线索大量流失、没人知道销售在干什么",[47,238,239],{},"CRM 优先",[29,241,242,245],{},[47,243,244],{},"老客户从来没人跟进、几乎没有复购",[47,246,239],{},[29,248,249,252],{},[47,250,251],{},"两者都严重",[47,253,254],{},"先 ERP（数据基础），半年后接 CRM",[14,256,257,258,261],{},"大多数中小车商属于「库存和钱没管好」这一类，",[115,259,260],{},"先上 ERP 更划算","：数据一旦准确，后续接任何 CRM 都有价值；反过来 CRM 积累的线索数据，在库存错误的前提下很难转化。",[18,263,265],{"id":264},"五如果要选一个一体化系统","五、如果要选一个「一体化」系统",[14,267,268],{},"如果对 ERP 与 CRM 都有需求但预算有限，选一体化系统时要注意验证：",[127,270,271,277,283,289],{},[130,272,273,276],{},[115,274,275],{},"库存是否真的受约束","（能否随便改状态、能否手工建单）；",[130,278,279,282],{},[115,280,281],{},"是否支持多组织数据隔离","（多家店共用时的红线）；",[130,284,285,288],{},[115,286,287],{},"权限与审计是否完整","（谁能看成本价、谁改过价格）；",[130,290,291,294],{},[115,292,293],{},"能否导出自己的数据","（防止被锁死）。",[14,296,297],{},"这四条比功能清单重要得多。功能可以后补，底层逻辑不对，用得越久改造成本越高。",{"title":167,"searchDepth":299,"depth":299,"links":300},2,[301,302,303,304,305],{"id":20,"depth":299,"text":21},{"id":121,"depth":299,"text":122},{"id":148,"depth":299,"text":149},{"id":194,"depth":299,"text":195},{"id":264,"depth":299,"text":265},"汽贸 ERP 与 CRM 各自的职责边界、重叠区与常见误区，以及如何判断现阶段该先上哪一个。","md",{},true,"\u002Fzh\u002Fblog\u002Fauto-dealer-erp-or-crm","2026-10-07",{"title":5,"description":306},"zh\u002Fblog\u002Fauto-dealer-erp-or-crm",[315,316,317],"选型指南","ERP","CRM","q1hpq6kK2mJiC71ec1HWhAhsLNyX2EZWZjKW6BNepNM",1792859777594]