Designed scope
- mobile receipts and transfers
- prices and labels
- scanned stock counts
In development · request access
R&D COPILOT Warehouse
Work on the floor executes commands; authority over stock always stays somewhere else.
01 / Workflow
From intent to a verifiable trail
The operator scans a receipt, a transfer or a count, and the app confirms the outcome through the stock API — not through a separate note.
Every operation retains company identity, actor, and source linkage.
Acceptance requires tests against the actual authorized version, integration, and data.
02 / Scope
Capabilities and boundaries
On the roadmap
- Selecting the handheld terminal model and the printer model is the next step.
- Proving the five workflows on real devices comes next.
03 / API
Controlled integrations
Connections use authenticated APIs and durable events. Single sign-on does not replace data synchronization, and each service retains its declared authority.
- Inventory API
- ERP
- Label printer
04 / Docs
Public integration notes
Working contract
Commands require an idempotency key, legal company, actor, source, and timestamp. Corrections use linked reversals and never silently rewrite history.
Access and availability
Validating the application entry point — origin, path, license, and release evidence — is the next milestone before the /app route goes live.
Price and inclusions
Pricing and commercial terms are being worked out; there is no published price or checkout yet. Reach out for where things currently stand.
05 / FAQ
Factual answers
Is the product available now?
Not yet — it's in development. Reach out and we'll tell you exactly where things stand and how to get early access.
Can I purchase online?
Not yet — there's no self-serve checkout while pricing and terms are being finalized.
What does this page prove?
It describes what's designed and what's still ahead — not a claim that this is production-ready or certified today.