The library every client is built on, and the tools that connect warecache to the rest of your workflow.
warecache is meant to be built on. The same library that powers the desktop and mobile clients is available to your own code, the server describes its own API, and a small set of integrations is taking shape around it. Status is marked honestly on each: the integrations below exist and run, but they are not yet published and may change before they are.
One Rust core that compiles to a native library and is exposed to C and C++, to Android through JNI, and to Python. The desktop client, the phone and iPad apps, the command line client, and every integration on this page go through it.
Rust core
|- C / C++ header -> desktop, iOS, iPadOS
|- JNI -> Android
|- Python package -> KiCache
'- Rust crate -> command line, odoo2wc, ts-tracker
In development. Not yet published.
Two pieces for electronics design. A library server that shows warecache parts inside KiCad's symbol chooser, so engineers design with what is actually in stock. And a board plugin that reads the finished layout and uploads its bill of materials straight into a warecache project.
A one-way importer for teams already running Odoo. It reads products from an Odoo instance, maps Odoo categories onto warecache part types, and creates the parts in warecache. It never writes back to Odoo, and it can rehearse a run without changing anything.
A read-only web page for the wall of a production floor. Each stage of production is a warecache part, and the dashboard shows how many units sit at each stage and how they flow from one to the next. It reads with a token that cannot change anything.
Every resource is available over an authenticated HTTP API, and the server publishes a live OpenAPI description of itself. Generate a client in any language from it.
API documentation →Add a supplier warecache does not know yet with a short Python script that implements three functions. The server handles scheduling, retries, and storage.
About plugins →The sensor interface is open: one connector, one power range, one identity scheme. A KiCad template for new sensor boards is published with the hardware files.
Hardware →