每一项能力都为「一个人管好几个仓」的真实场景打磨:不做大而全的 ERP,只把记录、核对与交接做扎实。 Every feature is shaped for the real situation of "one person running several depots" — not a bloated ERP, just record-keeping, verification and handover done right.
一个 App 同时管理彼此独立的多套账:家庭、工作室、客户代管各记各的,互不串数据。Keep several fully separate ledgers in one app — home, studio, or goods you hold for others never mix.
没有「手工维护的库存数字」这回事:库存由全部流转记录按时间折叠累计而来,账实天然一致。There is no hand-maintained "current stock" number: stock is folded from the full record timeline, so ledger and stock can never drift apart.
跨城搬迁最怕「搬一半、账乱了」。先立预案再执行:预案不动真实库存,每车一个在途仓,装车卸车逐行放行。Relocations fail on "half-moved, ledger-messed-up". Draft a plan first — it never touches real stock. Each vehicle becomes an in-transit depot; every line is released row by row at loading and unloading.
录单最慢的是打字。引路模式让你先拍再说:连拍实物,识别链自动预填,决策卡一下确认。Typing is the slowest part of logging. Guided mode flips it: shoot first — a recognition chain pre-fills the form, and one decision card confirms it.
想留存运输证据,又不想把车牌公开?给每辆车建档,照片里的车牌在本机自动模糊。Keep transport evidence without exposing plates: profile each vehicle and its photos get license plates auto-blurred on your device.
手机记账,电脑对账,现场贴标。XLSX 由自研引擎生成(零第三方依赖),打印无需电脑二次排版。Log on the phone, reconcile on the desktop, label on site. XLSX files come from a self-built engine (zero third-party code); printing needs no re-layout on a computer.
「在哪个架子第几层」和「这台设备由哪些散件组成」,都能记。Answers both "which shelf, which level" and "what parts is this device built from".
小工具也有细功夫:扫码直达物品,帮助就在 App 里,删什么都要再问一遍。The small touches matter: scan to open an item, help lives inside the app, and nothing deletes without asking twice.
仅使用 Apple 系统框架,连 Excel 引擎都是自研的——没有 SDK,就没有暗管。Apple frameworks only — even the spreadsheet engine is hand-built. No SDKs means no hidden channels.
核心逻辑是 200+ 条自动化测试锁定的纯函数,负库存拦截、对账口径等规则可回归验证。Core logic is pure functions locked by 200+ automated tests — negative-stock rules and reconciliation semantics are regression-checked.
全项目通过 Swift 6 严格数据竞争检查编译,长期维护的稳定性从第一天开始。The whole project compiles under Swift 6 strict concurrency checking — long-term stability from day one.