Skip to content

Concepts

An organization is the customer workspace boundary. Products, locations, balances, movements, reservations, transfers, inbounds, outbounds, API keys and webhooks belong to an organization.

Each organization can work in test or live. Inventory records are scoped by environment so training and integration tests do not affect live operations.

A product describes an item that can be stocked. The SKU is the operational identifier used in tables, filters, integrations and inventory workflows.

A location identifies where stock exists or moves through. Locations can represent warehouses, stores or virtual places depending on how the organization models operations.

A balance is the current stock state for a product, location and optional inventory segment. It summarizes quantities such as on hand, available, reserved, committed, incoming, damaged, quality control and safety stock.

A movement is the audit ledger entry behind an inventory change. Skunivo does not treat balances as manually editable totals. Inventory-changing actions create movements so stock can be explained later.

A reservation holds available stock for a customer order or another demand source. Reserved stock is no longer available until the reservation is committed, released, cancelled or expires.

A transfer moves stock between locations. Shipping and receiving can happen separately, and the transfer record tracks quantity across the movement.

An inbound tracks expected stock before it is received. An outbound tracks demand leaving inventory, including allocation, pick, pack and ship workflows when used.

API keys let server-side integrations call the public API for one organization and environment. Webhooks notify downstream systems about inventory events.