電子發票
品項、稅別、金額要正確，還要留下可查的處理結果。
09 · 要解決的問題
資料都在 ERP 裡，
卻沒有一扇門。
這套 26 年前的 32-bit Delphi ERP 沒有現代 API，也沒有 CLI。人看得到、點得到；但外部系統無法安全、穩定地呼叫。
Windows-only
No API
No CLI
商業規則不能丟
AI 與組織效率提升之間，最大的隔閡——是沒有 API、只能靠人操作的 Legacy ERP。
10 · 商業代價
沒有接口，六個成長需求一起被卡住。
第三方支付
付款、Webhook 與 ERP 單據之間，需要可靠對帳。
第三方貨運
標籤、追蹤、代收，只能取得完成任務所需的資料。
業務異地打單
手機、Mac、Discord 能下單，不等於遠端控制公司電腦。
銷售預測
歷史交易應該變成補貨、回購與交叉推薦訊號。
Lead 追蹤與預測
誰該先跟進、下一步做什麼、結果如何，都要能回到閉環。
不是沒有資料；是資料出不來，外部結果也回不去。
11 · 解題策略
不重寫 ERP。先選對入口。
先用反編譯、DFM 與型別研究看懂邊界；再依模組成熟度，選擇其中一條路。
路線 A
Accessibility + SQL
雙重驗證
還沒找到穩定 Kernel 時，用 UI 物件名稱與唯讀資料查詢，核對同一張單。
- Live Inspect 讀 UIA 物件
- 唯讀 SQL 查持久化資料
- 兩邊一致才納入流程
OR
路線 B
直接接 ERP Kernel
保留商業規則
已找到穩定商業物件時，跳過座標、滑鼠與鍵盤，直接走既有規則。
- 固定輸入欄位
- 既有商業物件執行
- 完成後獨立核對
兩條路最後都收斂成
Headless CLI + 可驗證 JSON
12 · 路線 A
畫面一把尺、SQL 一把尺。
量的是同一張單。
UI 看到的值=SQL 查到的值→欄位關係成立
13 · 路線 B
找到 Kernel，
就拿掉滑鼠和鍵盤。
正式流程不再靠視窗位置、焦點或人工節奏。查詢與建立都經固定命令邊界，結果再獨立核對。
UI 未觸碰
ERP 鍵盤事件 0
SQL 只讀核對
JSON 命令→ERP 商業物件→結果核對
14 · AI 工作流
當 ERP 有了 CLI，
業務可以在任何地方打單。
- 1自然語言業務說出要開什麼單
- 2固定欄位AI 只負責理解，不直接碰資料庫
- 3ERP 建單Kernel 執行原有商業規則
- 4SQL 驗證單號與內容核對後才回覆
15 · 企業整合
同一個接口，
接上外面的世界。
電子發票
整理品項、金額與處理結果
第三方貨運
建立託運、標籤、追蹤與代收
UDI／郵局版位
掃碼、紀錄與批次列印
第三方支付／應收
收款狀態、Webhook 與單據對帳
ERP 帳密與原廠元件仍留在受控 Windows 主機；外部服務只拿到完成任務所需的最少資料。後續擴充的是新供應商 Adapter，不必重做 ERP 整合。
16 · 從資料到決策
資料一旦能安全出來，
就能預測下一步。
橋接層負責「可信地拿資料」；分析層負責「下一個最佳行動」。兩邊分開，AI 才不會越權操作 ERP。
這不是把 Chatbot 放在舊流程旁邊。
是先看懂流程、補上接口，再讓 AI 可靠工作。
01 · THE PROBLEM 中文版從第 9 頁開始 →
All the data is in the ERP,
but there is no door.
This 26-year-old 32-bit Delphi ERP has no modern API and no CLI. People can see and click it, but external systems cannot call it safely or reliably.
Windows-only
No API
No CLI
Business rules must remain
The largest gap between AI and higher organizational productivity is often a legacy ERP with no API that can only be operated by people.
02 · BUSINESS COST
Without an interface,
six growth needs are blocked together.
E-invoicing
Correct products, tax types, and amounts, with an auditable processing result.
Third-party payments
Payments, webhooks, and ERP documents require reliable reconciliation.
Third-party logistics
Labels, tracking, and cash on delivery receive only the minimum required data.
Remote order entry
Creating orders from phones, Macs, or Discord is not remote-controlling an office PC.
Sales forecasting
Transaction history should become replenishment, repurchase, and cross-sell signals.
Lead tracking and prediction
Who to contact, what to do next, and the outcome must return to a closed loop.
The data exists. It simply cannot leave safely, and external results cannot return reliably.
03 · SOLUTION STRATEGY
Do not rewrite the ERP.
Choose the right entry point first.
Use reverse engineering, DFM, and type analysis to understand the boundary, then choose one route according to each module's maturity.
ROUTE A
Accessibility + SQL
dual verification
Before a stable kernel is known, compare UI object names with read-only persisted data for the same document.
- Read UIA objects with Live Inspect
- Query persisted data with read-only SQL
- Accept a field relationship only when both agree
OR
ROUTE B
Direct ERP kernel access
preserves business rules
Once a stable business object is known, remove coordinate, mouse, and keyboard automation and execute existing rules directly.
- Fixed input schema
- Existing business object executes
- Independent post-operation reconciliation
Both routes converge into
Headless CLI + verifiable JSON
04 · ROUTE A
The UI is one ruler. SQL is another.
Both measure the same document.
Value shown in UI=Value returned by SQL→Field relationship verified
05 · ROUTE B
Once the kernel is found,
remove the mouse and keyboard.
Production workflows no longer depend on window coordinates, focus, or human timing. Queries and creation use fixed command boundaries, followed by independent reconciliation.
UI untouched
0 ERP keyboard events
SQL read-only reconciliation
JSON command→ERP business object→Result reconciliation
06 · AI WORKFLOW
Once the ERP has a CLI,
sales staff can create orders from anywhere.
- 1Natural languageSales staff describe the required order
- 2Fixed fieldsAI interprets intent; it never writes directly to the database
- 3ERP creates documentThe kernel applies existing business rules
- 4SQL verificationReply only after document number and contents are reconciled
07 · ENTERPRISE INTEGRATION
One controlled interface
connects to the outside world.
E-invoicing
Products, amounts, and processing results
Third-party logistics
Shipments, labels, tracking, and cash on delivery
UDI / postal layouts
Scanning, records, and batch printing
Payments / receivables
Payment status, webhooks, and document reconciliation
ERP credentials and vendor components remain on a controlled Windows host. External services receive only the minimum data needed for each task. New providers require a new adapter—not another ERP integration project.
08 · FROM DATA TO DECISIONS
Once data can leave safely,
the next action becomes predictable.
The bridge retrieves trustworthy data. The intelligence layer recommends the next best action. Keeping them separate prevents AI from exceeding its ERP authority.
This is not a chatbot placed beside an old workflow.
Understand the process, add a safe interface, then let AI work reliably.