The same records are used by search, scan and API paths · mock data from a German-configured demo instance
Scope
What this area changes in the data flow.
A label should resolve an unambiguous record; an integration should use the same documented identifiers and operations. Open Inventory connects both paths with explicit lookup, preview, validation and idempotent execution.
Result 01
Resolve records by short link, QR code, barcode, UUID, SKU or serial number
Result 02
Create reusable print layouts in the browser
Result 03
Exchange data through validated CSV and scoped REST operations
Included implementation
Individual capabilities and constraints.
These components are part of the MIT-licensed project. Optional providers are identified where they take part in a workflow.
01
QR and barcode workflows
Scan from a camera or image, resolve inventory links, UUIDs, SKUs and serial numbers, and review configurable stock operations before idempotent execution.
02
Reusable label layouts
Design layouts in the browser with a short QR link, Code 128, optional record image and presets including Brother 62 mm and 102 × 152 mm.
03
CSV import and export
Import and export UTF-8 CSV. Row-level validation identifies invalid values, and repeated imports can use idempotent processing.
04
Transactional duplicate merging
A score helps identify similar records. A merge applies related-data changes transactionally instead of leaving partially moved associations.
05
Revocable public shares
Expose selected records through a revocable read-only share without opening the complete workspace.
06
Documented REST API
The checked-in OpenAPI 3.1 specification, interactive reference and hashed tokens with expiry and scopes make integrations inspectable.
Sequence
Resolve first, mutate only after review
A scan starts as a lookup. A stock change is written only after the record and proposed operation have been resolved and reviewed.
01
Choose an identifier
Use a short inventory link, UUID, SKU or serial number as the stable entry point to the record.
02
Build a label layout
Combine a QR link, Code 128, text and an optional record image in a reusable print definition.
03
Scan and resolve
Camera, image upload or hardware scanner reads the code. The matching record is displayed before any mutation.
04
Execute the workflow
Run a reviewed stock action or call the same contract from an integration using a scoped token and idempotency key.
Worked example
Concrete records, states and decisions.
The values are mock data, but the workflow and state changes correspond to operations implemented by Open Inventory.
concrete example
Example · Tool issue
The scan opens context before the action
A QR code on a tool case resolves the unique inventory record. The UI shows state and location before asking whether to write the issue movement.
Entry point
Short QR link
Resolved record
TOOL-0042
Operation
Confirm issue
Real SwiftUI app capture · demo data
Open-source iOS implementation
Use the iPhone as an open scanner client.
The native app recognizes QR, EAN-8/13, UPC-E, Code 128, Data Matrix, PDF417 and Aztec and calls the operator's own Open Inventory instance.
Resolve an inventory link, UUID, SKU or serial number
Display the matching record before a stock mutation
Inspect scanner and server implementations in the same repository
The API contract is a checked-in project artifact.
The OpenAPI 3.1 specification is stored as YAML in the repository. Tokens are stored as hashes and can carry expiry dates and scopes. They can be revoked without changing the underlying user account.
Checked-in OpenAPI document and interactive reference
