[{"data":1,"prerenderedAt":608},["ShallowReactive",2],{"site-schema":3,"article-zh-tw-erp-implementation-stuck-what-to-do":106,"article-related-zh-tw-erp-implementation-stuck-what-to-do":595},{"@context":4,"@graph":5},"https:\u002F\u002Fschema.org",[6,85,97],{"@type":7,"@id":8,"name":9,"alternateName":10,"description":17,"knowsAbout":18,"legalName":27,"foundingDate":28,"numberOfEmployees":29,"taxID":30,"url":31,"logo":32,"founder":33,"contactPoint":35,"address":49,"location":55,"sameAs":75},"Organization","https:\u002F\u002Fjoinx.co\u002F#organization","JoinX哲煜科技",[11,12,13,14,15,16],"JoinX","TWJOIN","哲煜科技","哲煜科技股份有限公司","TWJOIN 哲煜科技","twjoin.com","JoinX 哲煜科技（原品牌名 TWJOIN）是 2016 年在台北成立的軟體開發公司，80+ 人自有團隊，承接客製系統、APP、AI 導入與 IoT 開發，以及軟體外包與既有系統接手維運，服務 220+ 客戶、完成 520+ 專案。",[19,20,21,22,23,24,25,26],"軟體外包","客製化系統開發","APP 開發","AI 導入","AI Agent 開發","IoT APP 開發","ERP 系統整合","既有系統接手維運","JoinX Co., Ltd.","2016-04-28",80,"43774383","https:\u002F\u002Fjoinx.co","https:\u002F\u002Fjoinx.co\u002Fimages\u002Flogo-with-name.png",{"@id":34},"https:\u002F\u002Fjoinx.co\u002F#person-jack-lee",[36],{"@type":37,"contactType":38,"url":39,"telephone":40,"email":41,"areaServed":42,"availableLanguage":45},"ContactPoint","customer service","https:\u002F\u002Fjoinx.co\u002Fcontact-us","+886-2-8771-9095","service@joinx.co",[43,44],"TW","JP",[46,47,48],"zh-Hant","en","ja",{"@type":50,"streetAddress":51,"postalCode":52,"addressLocality":53,"addressRegion":54,"addressCountry":43},"PostalAddress","民生東路二段170號8樓","104","台北市中山區","台灣",[56,63,69],{"@type":57,"name":58,"address":59},"Place","JoinX 台中辦公室",{"@type":50,"streetAddress":60,"postalCode":61,"addressLocality":62,"addressRegion":54,"addressCountry":43},"台灣大道二段360號21樓C室","40453","台中市北區",{"@type":57,"name":64,"address":65},"JoinX 高雄辦公室",{"@type":50,"streetAddress":66,"postalCode":67,"addressLocality":68,"addressRegion":54,"addressCountry":43},"民族一路80號2樓之一(B4)","807","高雄市三民區",{"@type":57,"name":70,"address":71},"JoinX 東京辦公室",{"@type":50,"streetAddress":72,"postalCode":73,"addressLocality":74,"addressCountry":44},"東五反田5-22-37 Office Circle N 五反田 9樓","141-0022","東京都品川區",[76,77,78,79,80,81,82,83,84],"https:\u002F\u002Fwww.crunchbase.com\u002Forganization\u002Ftwjoin","https:\u002F\u002Fwww.facebook.com\u002FJoinX.TW","https:\u002F\u002Ftw.linkedin.com\u002Fcompany\u002F%E5%93%B2%E7%85%9C%E7%A7%91%E6%8A%80","https:\u002F\u002Fwww.youtube.com\u002Fc\u002Fjoinstuido%E5%93%B2%E7%85%9C%E7%A7%91%E6%8A%80","https:\u002F\u002Fmedium.com\u002Ftwjoin","https:\u002F\u002Fwww.104.com.tw\u002Fcompany\u002F1a2x6bjomb","https:\u002F\u002Fclutch.co\u002Fprofile\u002Ftwjoin","https:\u002F\u002Fwww.goodfirms.co\u002Fcompany\u002Ftwjoin","https:\u002F\u002Ftwjoin.com",{"@type":86,"@id":34,"name":87,"alternateName":88,"jobTitle":89,"worksFor":90,"url":91,"sameAs":92},"Person","李秉哲","Jack Lee","創辦人暨執行長",{"@id":8},"https:\u002F\u002Fjack.joinx.co",[93,94,95,96],"https:\u002F\u002Fwww.instagram.com\u002Fjack88.podcast\u002F","https:\u002F\u002Fwww.threads.net\u002F@jack88.podcast","https:\u002F\u002Fjoinx.co\u002Fjack88\u002F","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fjacklee-taiwan\u002F",{"@type":98,"@id":99,"url":31,"name":9,"alternateName":100,"publisher":101,"inLanguage":102},"WebSite","https:\u002F\u002Fjoinx.co\u002F#website",[11,13,9],{"@id":8},[103,104,105],"zh-Hant-TW","en-US","ja-JP",{"id":107,"title":108,"body":109,"category":560,"cover":561,"dateModified":562,"description":563,"extension":564,"faq":562,"hasCoverTitle":565,"locale":566,"meta":567,"navigation":568,"need":569,"path":570,"seo":571,"seoDescription":562,"seoTitle":562,"sources":572,"stem":585,"takeaways":586,"time":592,"type":593,"__hash__":594},"content\u002Fzh-tw\u002Farticle\u002Ferp-implementation-stuck-what-to-do.md","ERP 導入卡關怎麼辦？停損、保留套裝、補客製三條路（含 Odoo／鼎新導入後要客製時怎麼選）",{"type":110,"value":111,"toc":537},"minimark",[112,116,119,122,127,130,133,137,140,222,225,229,232,308,313,316,320,323,327,336,340,343,378,382,385,456,459,463,466,472,478,481,485,488,495,498,502,505,509,516,520,523,527,530,534],[113,114,115],"p",{},"ERP 導入卡關時，先別急著加預算或換廠商，而是先判斷卡在哪：流程不合、資料轉換、使用者不用，還是串接不到。卡在資料或使用者，多半能在原系統上救回來；只有少數流程不合，可以保留套裝 ERP、再用串接或外掛模組補上；核心流程和套裝根本對不上、而且越改越難維護時，才考慮停損、改走客製。",[113,117,118],{},"常見的情況是：專案已經延了好幾個月，顧問說還要加客製天數，業務和倉庫還在用 Excel，月底一樣要人工對帳。這時候最容易做錯的決定，是在還沒搞清楚原因前，就整套換掉，或繼續往原系統裡加客製。",[120,121],"article-cta",{},[123,124,126],"h2",{"id":125},"erp-導入卡關第一步該做什麼","ERP 導入卡關，第一步該做什麼？",[113,128,129],{},"第一步是先暫停新增需求，把「現在卡住的事」逐條列出來，標出每一條屬於流程、資料、使用者還是串接。分類清楚之後，才知道該補哪一塊，而不是一次全部重來。",[113,131,132],{},"具體做法是把專案相關的人找來，各自寫下三件事：哪個作業還在系統外用 Excel 或紙本處理、哪張報表數字對不上、哪個畫面大家不願意用。不要在這個階段討論要不要換系統，先把事實收齊。產業調查（例如 Panorama Consulting 每年發布的 ERP Report）也長期指出，ERP 專案超出預期時程與預算相當常見，原因多半在組織與資料，而不只是軟體本身。",[123,134,136],{"id":135},"erp-導入卡在哪四種常見卡點怎麼分辨","ERP 導入卡在哪？四種常見卡點怎麼分辨？",[113,138,139],{},"ERP 導入卡關，大致可分成流程不合、資料轉換、使用者不用、串接不到四種。前兩種在專案中期最常出現，後兩種多半在上線後才浮現，判斷方式和解法都不一樣。",[141,142,143,162],"table",{},[144,145,146],"thead",{},[147,148,149,153,156,159],"tr",{},[150,151,152],"th",{},"卡點",[150,154,155],{},"常見症狀",[150,157,158],{},"先查什麼",[150,160,161],{},"通常的方向",[163,164,165,180,194,208],"tbody",{},[147,166,167,171,174,177],{},[168,169,170],"td",{},"流程不合",[168,172,173],{},"某些作業一直要「先在 Excel 算好再輸入」，顧問說要客製才做得到",[168,175,176],{},"是少數流程不合，還是核心流程整個對不上",[168,178,179],{},"少數不合：外掛模組補上；核心不合：評估停損",[147,181,182,185,188,191],{},[168,183,184],{},"資料轉換",[168,186,187],{},"舊資料匯不進去、庫存數字對不起來、期初開帳一再延後",[168,189,190],{},"料號、客戶、價格條件等主檔有沒有先整理",[168,192,193],{},"先整理主檔，再分批轉入",[147,195,196,199,202,205],{},[168,197,198],{},"使用者不用",[168,200,201],{},"系統上線了，但現場還是用舊方法，資料只有部分人在輸入",[168,203,204],{},"是畫面太繁瑣、權限不對，還是沒有人負責推動",[168,206,207],{},"簡化操作、指定內部負責人、縮小上線範圍",[147,209,210,213,216,219],{},[168,211,212],{},"串接不到",[168,214,215],{},"電商、POS、倉儲或會員資料要人工匯出匯入",[168,217,218],{},"ERP 這個版本開放哪些介面（API、資料庫、檔案匯出）",[168,220,221],{},"在 ERP 外面做串接，資料自動同步",[113,223,224],{},"分類時要注意「流程不合」最容易被誤判。很多時候真正的原因是主檔沒整理，或某個部門不願改變習慣，看起來卻像是系統做不到。",[123,226,228],{"id":227},"停損保留套裝補客製三條路怎麼選","停損、保留套裝、補客製，三條路怎麼選？",[113,230,231],{},"三條路的差別在於原本的 ERP 還能承擔多少：還能管好帳務與庫存，就保留套裝、只補缺口；核心流程對不上、改動已經難以維護，才走停損或客製。多數企業最後落在「保留套裝＋補客製」。",[141,233,234,250],{},[144,235,236],{},[147,237,238,241,244,247],{},[150,239,240],{},"比較項目",[150,242,243],{},"停損換方向",[150,245,246],{},"保留套裝、修正導入",[150,248,249],{},"保留套裝＋補客製",[163,251,252,266,280,294],{},[147,253,254,257,260,263],{},[168,255,256],{},"適合的情況",[168,258,259],{},"核心流程和套裝對不上，或原廠已停止更新",[168,261,262],{},"卡在資料轉換或使用者不用，系統本身合用",[168,264,265],{},"帳務庫存合用，少數流程或串接做不到",[147,267,268,271,274,277],{},[168,269,270],{},"要先確認",[168,272,273],{},"資料能否完整匯出、已完成的客製能否帶走",[168,275,276],{},"主檔是否整理完、有沒有內部負責人",[168,278,279],{},"ERP 開放的介面、補的部分由誰維護",[147,281,282,285,288,291],{},[168,283,284],{},"主要成本",[168,286,287],{},"已投入的授權與導入費用、重新導入的時間",[168,289,290],{},"內部人力與顧問延長的天數",[168,292,293],{},"串接或模組開發費、後續維運",[147,295,296,299,302,305],{},[168,297,298],{},"主要風險",[168,300,301],{},"新系統重蹈覆轍",[168,303,304],{},"問題其實是流程不合，修了也用不起來",[168,306,307],{},"改動寫進 ERP 核心，改版時要重做",[309,310,312],"h3",{"id":311},"什麼時候該停損","什麼時候該停損？",[113,314,315],{},"出現下列兩種以上的情況，就值得認真評估停損：核心流程（例如計價、工單成本、派工）必須大量改寫套裝才能運作；已改過的部分每次原廠改版都要重做；原廠或版本已停止更新；專案已經延誤很久，卻仍說不出何時能結帳。停損不代表全部重來，帳務與庫存模組有時仍可保留。",[309,317,319],{"id":318},"什麼時候保留套裝修正導入就好","什麼時候保留套裝、修正導入就好？",[113,321,322],{},"卡點集中在資料轉換或使用者不用時，系統通常沒有選錯。把上線範圍縮小到財務與庫存，先讓一個部門真正用起來，再擴充到其他流程，往往比換系統快得多。",[309,324,326],{"id":325},"什麼時候要補客製","什麼時候要補客製？",[113,328,329,330,335],{},"ERP 的帳務與庫存已經穩定，只有報價、品檢、經銷下單等少數流程，或是電商、POS 等串接做不到時，就在 ERP 旁邊補上獨立模組，資料再透過 API 回寫 ERP。這樣原本的 ERP 改版不受影響，補的部分也能單獨維護。選型時的完整比較，可參考 ",[331,332,334],"a",{"href":333},"\u002Farticle\u002Ferp-selection-packaged-vs-custom\u002F","ERP 怎麼選：套裝、雲端 ERP 與客製開發","。",[123,337,339],{"id":338},"決定停損時要先拿回哪些東西","決定停損時，要先拿回哪些東西？",[113,341,342],{},"決定停損前，要先把資料、文件與已完成的成果拿回來，否則下一個團隊只能從零開始。建議依下面的順序逐項確認，並在合約或交接紀錄上寫清楚。",[344,345,346,354,360,366,372],"ol",{},[347,348,349,353],"li",{},[350,351,352],"strong",{},"完整資料匯出","：主檔、交易紀錄與期初開帳資料，確認匯出的格式能被其他系統讀取。",[347,355,356,359],{},[350,357,358],{},"需求與流程文件","：導入期間整理的現況流程、需求清單與差異分析，這是最花時間的成果。",[347,361,362,365],{},[350,363,364],{},"已完成的客製程式","：確認程式碼與設定是否屬於公司、能否交給其他團隊維護。",[347,367,368,371],{},[350,369,370],{},"帳號與權限清單","：系統管理員帳號、雲端主機或資料庫的存取權。",[347,373,374,377],{},[350,375,376],{},"未解決問題清單","：把導入過程中卡住的事逐條記下來，讓下一套系統或下一個團隊先處理。",[123,379,381],{"id":380},"導入後要客製找原導入顧問還是找開發團隊","導入後要客製：找原導入顧問還是找開發團隊？",[113,383,384],{},"設定調整、報表與套裝內建功能的延伸，找原導入顧問通常最快；跨系統串接、整段新流程或需要寫程式的模組，找開發團隊較合適。重點不是誰比較便宜，而是改動放在哪裡、以後由誰維護。",[141,386,387,399],{},[144,388,389],{},[147,390,391,393,396],{},[150,392,240],{},[150,394,395],{},"原導入顧問（原廠或經銷）",[150,397,398],{},"開發團隊",[163,400,401,412,423,434,445],{},[147,402,403,406,409],{},[168,404,405],{},"擅長的事",[168,407,408],{},"參數設定、報表、套裝內建功能、版本升級",[168,410,411],{},"跨系統串接、獨立模組、ERP 沒有的流程",[147,413,414,417,420],{},[168,415,416],{},"了解程度",[168,418,419],{},"熟悉套裝與你們的導入設定",[168,421,422],{},"要先花時間了解 ERP 的介面與資料結構",[147,424,425,428,431],{},[168,426,427],{},"改動的位置",[168,429,430],{},"常在 ERP 內部做二次開發",[168,432,433],{},"多半在 ERP 外部，透過 API 或資料交換",[147,435,436,439,442],{},[168,437,438],{},"改版的影響",[168,440,441],{},"二次開發的部分可能要跟著改版重做",[168,443,444],{},"介面不變時，ERP 改版影響較小",[147,446,447,450,453],{},[168,448,449],{},"適合的需求",[168,451,452],{},"「套裝本來就有，只是沒設好」",[168,454,455],{},"「套裝本來就沒有，要另外補」",[113,457,458],{},"兩者也可以合作：原導入顧問負責 ERP 內的設定與介面開放，開發團隊負責外部模組與串接。分工時要把「資料以哪一邊為準」寫清楚，例如庫存以 ERP 為準、電商訂單以電商平台為準，之後出問題才知道該找誰。",[123,460,462],{"id":461},"odoo鼎新導入後要客製各要注意什麼","Odoo、鼎新導入後要客製，各要注意什麼？",[113,464,465],{},"Odoo 與鼎新的客製方式不同：Odoo 可以用 Studio 調整欄位與畫面，較深的需求要寫自訂模組；鼎新等套裝 ERP 的二次開發多由原廠或經銷處理。兩者共通的原則，是盡量把改動放在核心之外。",[113,467,468,471],{},[350,469,470],{},"Odoo","：先分清楚需求能不能用 Studio（企業版的設定工具）完成，例如新增欄位、調整表單或簡單的自動化。需要新的資料模型、複雜計算或外部串接時，就要寫自訂模組。依 Odoo 官方的升級說明，跨大版本升級時，自訂模組需要由開發者另外調整，所以模組越多、改得越深，每次升級的成本越高。",[113,473,474,477],{},[350,475,476],{},"鼎新等套裝 ERP","：先確認目前使用的產品與版本開放哪些介面，例如 API、資料庫讀取或檔案匯出。ERP 內部的流程與報表調整，通常由原廠或經銷顧問處理；要和電商、POS、倉儲或會員系統交換資料時，可以在 ERP 外面做串接，不必動到 ERP 本身。",[113,479,480],{},"不論哪一套，客製前都先問一句：「這個改動在下一次改版時會不會被覆蓋？」答案是會，就優先考慮放在外部。",[123,482,484],{"id":483},"joinx-怎麼協助卡關的-erp","JoinX 怎麼協助卡關的 ERP？",[113,486,487],{},"JoinX 接手卡關的 ERP，先盤點 ERP 開放的介面與現有資料，再判斷是補模組、做串接，還是只調整報表；能保留的 ERP 就保留，不建議沒必要的整套更換。",[113,489,490,491,335],{},"我們替比漾百貨建置官網暨電商時，就是讓電商平台串接既有的 ERP、POS 與鼎新財會系統，沒有更換原本的 ERP。開發時我們用規格驅動開發（SDD）把流程與例外情況寫清楚，再用測試驅動開發（TDD）確認每次修改都不會影響既有的帳務資料。串接方式與做過的案例，可參考 ",[331,492,494],{"href":493},"\u002Ferp-integration\u002F","ERP 系統整合服務",[123,496,497],{"id":497},"常見問題",[309,499,501],{"id":500},"erp-導入失敗錢是不是都白花了","ERP 導入失敗，錢是不是都白花了？",[113,503,504],{},"不一定。導入期間整理出的流程文件、乾淨的主檔資料與已完成的設定，換系統時大多還用得上。停損前先把資料與文件拿回來，可以保住這部分的投入。",[309,506,508],{"id":507},"erp-導入後要客製費用怎麼估","ERP 導入後要客製，費用怎麼估？",[113,510,511,512,335],{},"依範圍而定。調整報表或欄位通常是小範圍；獨立模組或跨系統串接，要看流程複雜度與介接的系統數量。JoinX 的簡單型 ERP 約 NT$45 萬起，補模組或串接則依需求報價，可先參考",[331,513,515],{"href":514},"\u002Farticle\u002F2026-custom-system-development-cost\u002F","客製化系統開發費用全解析",[309,517,519],{"id":518},"odoo-社群版可以客製嗎","Odoo 社群版可以客製嗎？",[113,521,522],{},"可以。社群版和企業版都能寫自訂模組；差別在於 Studio 等設定工具與部分功能只在企業版提供。選擇時要考慮之後升級版本的成本。",[309,524,526],{"id":525},"已經導入鼎新-erp可以不換系統就串接電商或-pos-嗎","已經導入鼎新 ERP，可以不換系統就串接電商或 POS 嗎？",[113,528,529],{},"可以，先確認目前版本開放的介面。多數情況可以在 ERP 外面做串接，讓訂單、商品、庫存與帳務資料自動同步，不必更換 ERP。",[309,531,533],{"id":532},"原導入顧問不願意做的客製可以找別人做嗎","原導入顧問不願意做的客製，可以找別人做嗎？",[113,535,536],{},"可以，但要先確認合約對程式碼與系統維護的約定，並請原顧問開放必要的介面或帳號。改動放在 ERP 外部時，通常不會影響原廠的維護責任。",{"title":538,"searchDepth":539,"depth":539,"links":540},"",2,[541,542,543,549,550,551,552,553],{"id":125,"depth":539,"text":126},{"id":135,"depth":539,"text":136},{"id":227,"depth":539,"text":228,"children":544},[545,547,548],{"id":311,"depth":546,"text":312},3,{"id":318,"depth":546,"text":319},{"id":325,"depth":546,"text":326},{"id":338,"depth":539,"text":339},{"id":380,"depth":539,"text":381},{"id":461,"depth":539,"text":462},{"id":483,"depth":539,"text":484},{"id":497,"depth":539,"text":497,"children":554},[555,556,557,558,559],{"id":500,"depth":546,"text":501},{"id":507,"depth":546,"text":508},{"id":518,"depth":546,"text":519},{"id":525,"depth":546,"text":526},{"id":532,"depth":546,"text":533},"技術分享","\u002Fimages\u002Fblog\u002Ferp-implementation-stuck-what-to-do.webp",null,"ERP 導入卡關時，先別急著加預算或換廠商，而是先判斷卡在哪：流程不合、資料轉換、使用者不用，還是串接不到。卡在資料或使用者，多半能在原系統上救回來；只有少數流程不合，可以保留套裝 ERP、再用串接或外掛模組補上；核心流程和套裝根本對不上、而且越改越難維護時，才考慮停損、改走客製。本文整理四種卡點的判斷方式、三條路的選擇條件，以及 Odoo、鼎新導入後要客製時，找原導入顧問與找開發團隊的差別。","md",false,"zh-tw",{},true,"ERP","\u002Fzh-tw\u002Farticle\u002Ferp-implementation-stuck-what-to-do",{"title":108,"description":563},[573,576,579,582],{"name":574,"issuer":575},"Enterprise Resource Planning (ERP)，Gartner Glossary","Gartner",{"name":577,"issuer":578},"The 2024 ERP Report","Panorama Consulting Group",{"name":580,"issuer":581},"Odoo Documentation：Studio 與 Upgrade 說明","Odoo S.A.",{"name":583,"issuer":584},"2024 年中小企業白皮書","經濟部中小及新創企業署","zh-tw\u002Farticle\u002Ferp-implementation-stuck-what-to-do",[587,588,589,590,591],"ERP 導入卡關，先診斷再花錢。把卡點分成流程不合、資料轉換、使用者不用、串接不到四類，每一類的解法和成本都不同。","卡在資料轉換或使用者不用，通常不是系統選錯，整理主檔、縮小上線範圍、找出內部負責人，多半就能救回來。","只有少數流程不合或串接不到時，保留套裝 ERP 管帳務與庫存，再用 API 或外掛模組補上缺口，是風險最低的做法。","核心流程和套裝對不上、改過的地方每次改版都要重做時，才值得停損。停損前要先拿回資料、規格文件與已完成的客製程式。","導入後要客製，設定與報表找原導入顧問較快；跨系統串接或整段新流程，找開發團隊通常較合適，關鍵是改動要放在 ERP 核心之外。","2026\u002F11\u002F04","blog","GG5Z7zRwlW5eGVGmnn_HRpDIAYGLWe9Mh_7Q07yo5g0",[596,600,604],{"slug":597,"title":598,"time":592,"cover":599,"need":569},"cloud-erp-not-enough-integrate-or-custom","雲端 ERP 不夠用怎麼辦？保留、串接還是客製","\u002Fimages\u002Fblog\u002Fcloud-erp-not-enough-integrate-or-custom.webp",{"slug":601,"title":602,"time":592,"cover":603,"need":569},"custom-erp-cost-total-cost-of-ownership","客製 ERP 費用怎麼算：買斷、月租、套裝訂閱的 3 年與 5 年總成本","\u002Fimages\u002Fblog\u002Fcustom-erp-cost-total-cost-of-ownership.webp",{"slug":605,"title":606,"time":592,"cover":607,"need":569},"digiwin-erp-integration-ecommerce-pos","鼎新 ERP 串接電商、POS 的 4 種方式與費用","\u002Fimages\u002Fblog\u002Fdigiwin-erp-integration-ecommerce-pos.webp",1793793305449]