Skunivo is
- A versioned inventory API
- A transaction-safe movement ledger
- A multi-organization, multi-location core
- SDKs, webhooks and an optional workspace
Headless inventory infrastructure
Inventory truth, delivered reliably.
Add multi-location stock, reservations, transfers and an immutable movement ledger to your product without owning the inventory engine.
API-firstIdempotent writesExplainable balances
POST /v1/inventory/reservations200 OK
await skunivo.reservations.create({
sku: 'HOODIE-BLACK-M',
locationId: 'loc_main',
quantity: 12,
expiresIn: '30m'
}, {
idempotencyKey: 'order_8421'
})available96 → 84
reserved8 → 20
movementmv_7f3a9c
PostgreSQLSource of truth
ImmutableMovement ledger
Safe retriesIdempotent operations
OptionalCustomer workspace
A focused inventory core
Infrastructure for the hard parts of inventory.
Skunivo is the operational layer between your application and the physical truth of stock. It coordinates quantities, states and movements so every write is safe and every balance can be explained.
Skunivo is not
- A full ERP or accounting suite
- A storefront or ecommerce platform
- A connector-specific inventory mirror
- A direct stock-editing CRUD database
One operation, one durable result
Retry the request. Never duplicate the movement.
Inventory-changing requests use idempotency keys and transactional rules. If a network timeout makes the result uncertain, the same intent can be retried safely.
POST /v1/inventory/reservations
Idempotency-Key: order_8421
{
"sku": "HOODIE-BLACK-M",
"quantity": 12,
"locationId": "loc_main"
}{
"reservationId": "res_43fa12",
"status": "pending",
"movementId": "mv_7f3a9c",
"replayed": false
}Reliability is the product
The problems teams should not have to rebuild.
Concurrency control
Competing operations cannot promise the same available units.
Explainable balances
Trace on-hand, available, reserved and committed quantities back to movements.
Reservation lifecycle
Hold stock temporarily, then commit, release or expire it with a clear history.
Multi-location transfers
Ship and receive between locations without losing the state in between.
Observable webhooks
Deliver signed events with retries and delivery visibility.
Organization boundaries
Keep human roles, organization access and API key scopes separate.
From request to inventory truth
A short path with strong guarantees.
Your app calls a business operation
Reserve, receive, transfer or reconcile through a versioned API or the official SDK.
Skunivo validates and commits atomically
Authorization, inventory state, capacity and idempotency are resolved inside the operation.
Every surface reads the same truth
Your application, webhooks and the optional workspace observe the persisted result.
A different category
Use infrastructure where other tools make you compromise.
| Approach | Best at | Trade-off |
|---|---|---|
| Skunivo | Embedding reliable inventory into software products | Focused inventory scope instead of an all-in-one suite |
| Build it yourself | Maximum product-specific control | Long-term ownership of concurrency, ledger and reconciliation |
| Traditional ERP / WMS | Broad back-office and warehouse workflows | Heavier implementation and weaker embedding model |
| Simple inventory CRUD | Fast catalog and quantity prototypes | No durable movement history or concurrency guarantees |
One core, multiple surfaces
Integrate in code. Operate when you need to.
Business operations, not table mutations
Versioned endpoints represent receive, reserve, commit, release and transfer actions.
A safer path through the contract
Typed client methods are generated from the filtered public OpenAPI specification.
Signed events for downstream systems
Observe inventory changes without making external systems the source of truth.
An optional operational interface
Teams can inspect products, balances, movements and critical operations without an integration.
Build on inventory you can explain.
Start with the API documentation or open the workspace to see the operational model.