进销存语言怎么写？常用编程语言有哪些选择？

语义DSL与JSON示例

为了让业务规则被程序消费，同时保留可读性，我通常采用两层表达：第一层是面向业务的DSL（领域专用语言），第二层是面向系统的JSON。DSL更易于沟通与审阅，JSON便于落地与集成。下面给出一个典型的采购入库到出库、计价、合规的写法示例。

flow "采购到出库" {
  actors: buyer, receiver, inspector, picker, shipper
  entities: sku, batch, location, order, voucher
  states: PENDING_PO -> RECEIVED -> QA_PASSED -> PUTAWAY -> PICKED -> SHIPPED
  rules {
    pricing: FIFO warehouse_scope
    tax: VAT 13%
    lot: expire_in_days <= sku.shelf_life
    qa: sampling_rate by sku.class
    approval: multi_level by amount ranges
  }
  events {
    on RECEIVE {
      assert order.status == PENDING_PO
      create batch for received items
      log "receive_note"
    }
    on QA_PASS {
      assert batch.qc_score >= sku.qc_threshold
    }
    on PUTAWAY {
      move batch to location by strategy "nearest-empty"
    }
    on PICK {
      strategy FIFO by location
    }
    on SHIP {
      create voucher mapping to GL
      notify customer
    }
  }
}

与之配套的JSON，直接供系统执行与审计：

{
  "flow": "procure_to_ship",
  "states": ["PENDING_PO","RECEIVED","QA_PASSED","PUTAWAY","PICKED","SHIPPED"],
  "pricing": {"method":"FIFO","scope":"warehouse"},
  "tax": {"type":"VAT","rate":0.13},
  "qa": {"sampling":"by_class","threshold_map":{"A":0.98,"B":0.95,"C":0.90}},
  "lot": {"expire_days_max":"sku.shelf_life"},
  "approval": [{"level":1,"range":[0,50000]}, {"level":2,"range":[50000,200000]}],
  "events": {
    "RECEIVE": {"precondition":"order.status==PENDING_PO","actions":["create_batch","log_receive_note"]},
    "QA_PASS": {"precondition":"batch.qc_score>=sku.qc_threshold"},
    "PUTAWAY": {"strategy":"nearest_empty"},
    "PICK": {"strategy":"FIFO_by_location"},
    "SHIP": {"gl_voucher":true,"notify_customer":true}
  },
  "audit": {"version":"1.4.2","changed_by":"ops_admin","changed_at":"2025-05-18T09:31:00Z"}
}

在【简道云进销存】中，这类规则可以通过表单、流程、计算字段与脚本节点快速配置，并通过数据字典与审批流可视化呈现，既省去大量自研工作，又可保留灵活扩展能力。