Inventory Management

Inventory is the foundation of Knowledge ERP, and it is modelled at two levels: a Product is the catalogue entry; a Unit is one tracked item of it. The Product says what a thing is; each Unit has its own status, location, and history.

In this section #

Detailed guides for everything covered here:

• Products — The catalogue definition of a thing — name, price, cost, unit of measure, usage type, barcode, components, vendors, and reorder points — shared by every physical unit of that kind.
• Units — One tracked physical unit of a Product — with its own location, bin, status, lot, price, and complete movement history. Units are what you check out, sell, transfer, count, and consume.
• Locations & Bins — Locations are the warehouses, stores, or vehicles where your stock lives; bins are the hierarchical shelves, racks, and drawers inside them that tell you exactly where each unit sits.
• Categories — The hierarchical grouping tree for Products — defines which custom fields, lot/expiration tracking, and reorder defaults apply to every Product and unit within it.
• Kits — A named bundle of component Products and/or nested kits that can be sold or tracked as a single unit, with an automatically maintained count of how many complete kits can be assembled from on-hand inventory.
• Transfers — Move stock between locations with a structured request, approve, ship, and receive workflow — every unit tracked individually from source bin to destination bin.
• Cycle Counts — A targeted physical audit of a location or bin that snapshots expected quantities, collects your physical counts, and posts the differences as inventory adjustments.
• Units of Measure — The catalog of measurement units — abbreviations like "lb", "gal", "ea", or "box" — that Products and Units use to express amounts and weights across the system.
• Vendor SKUs — A Vendor SKU links one of your catalog Products to a specific supplier, recording the vendor's part number, catalog price, lead time, and pack size so purchasing and reorder suggestions always know where to buy and how much to order.

Products and Units #

• A Product holds the shared definition: name, price, cost, unit of measure, barcode, and its usage type — Consumable (drawn down or sold) or Returnable (reusable equipment that goes out and comes back).
• A Unit is one tracked item of it. Units move through statuses (in stock, checked out, on hold, in transit, out of stock, discontinued) and carry a full movement history.

Locations, bins, and lots #

Stock lives in locations (warehouses, rooms, vehicles) subdivided into bins. Units can carry lot numbers for traceability, and you can move stock between locations with transfers that follow a draft → request → approve → ship → deliver → receive workflow.

Kits #

A kit bundles component Products or nested kits so you can manage and check out a set as one thing. The system automatically tracks how many complete kits can be assembled from on-hand inventory.

Barcodes and custom fields #

Every Product can carry a barcode for scan-based lookups and actions. Custom fields add your own attributes and inherit down a chain (category → Product → unit), so you define a field once and override it where it matters.

Counting and accuracy #

Cycle counts let you reconcile recorded stock against what's physically on the shelf, posting adjustments and keeping the movement history honest.

Doing it from the API #

# List inventory units
curl "https://your-domain.com/api/v1/inventory/units" \
  -H "Authorization: Bearer $TOKEN"