Catalog - where item settings drive everything else
The Catalog holds everything you sell or buy - products, services, subscriptions, fees - organized across Items, Categories, Units, Price Lists, and Attributes tabs. An item’s Inventory profile is where the decisions that matter live: whether it’s tracked at all, its costing method (weighted average by default, or FIFO, or standard), and whether it needs batch or serial tracking. The item’s own detail page is read-only - editing happens back on the list, in the same drawer, which also auto-saves your draft locally so a half-finished new item survives an accidental tab close.
On the list vs. the detail screen
Items list
- Every item: name, code, type, category, price, and status - inline price/category edit, bulk tax classification
- The working surface - almost everything you’d do to an item happens right here, in the drawer
One item, opened
- A read-only profile summary, plus stock-by-warehouse if inventory tracking is on
- "Edit" deep-links back to the list’s own drawer - there’s no separate detail-page editor
Inventory Command Center
One page for stock on hand, its valuation, and the full movement history behind it, across four tabs: Balances (on hand, committed, available, average cost, and value per item and warehouse), Movements (the full ledger of what moved and why), Reservations (stock held by draft invoices, flagged if it’s gone stale), and Backorders (an invoice issued for more than you had on hand, tracked explicitly rather than silently allowed to go negative).
What posts to the ledger, and what doesn’t
Receiving stock, billing it, selling it, and recording damage or loss all post automatically - each has its own real journal entry. Opening balances and warehouse-to-warehouse transfers deliberately don’t, because no value actually changed hands in either case.
Transfer History
Every transfer between your own warehouses always creates two linked movements (one out, one in) atomically - this screen joins that pair back into a single readable row: what moved, from where, to where, at what cost. It never touches the ledger, since a transfer only relocates stock you already own.
Inventory Aging
For every item and warehouse currently holding stock, buckets the quantity by how long it’s been sitting there (0-30, 31-60, 61-90, 91-180, 180+ days), by replaying the full movement history oldest-first. This replay always assumes first-in-first-out for the purpose of judging age, even for an item whose actual costing method is weighted average or standard - age and valuation are genuinely different questions, and this report only answers the first one.
Cycle Counts
A physical stocktake workflow: start a count for a warehouse (which freezes the system’s expected quantities into count lines), walk the floor entering what you actually find - by hand or by barcode scan - saving as you go, then post. Posting creates an ordinary adjustment movement, with the normal ledger effect, only for lines that actually came out different from expected; anything you didn’t count is left untouched rather than assumed to be zero. Cancel keeps the count on record for reference but posts nothing.
Pick List
Everything currently reserved by draft invoices at a chosen warehouse, grouped by item so a picker collects one total quantity per item instead of walking the floor once per order - the per-order breakdown is still shown underneath each item. Built for printing (the page hides all navigation chrome automatically when you print it), not for generating a PDF.
Locations
Branch and warehouse structure in one place - branches can nest under a parent so financial activity rolls up automatically once posted, and each warehouse has its own capabilities (can it receive, ship, or transfer stock in/out) plus an optional operating vendor, which is what makes it a third-party (3PL) warehouse. A capacity ceiling can be set per warehouse, but nothing currently enforces it or shows usage against it - it’s stored for future use, not yet an active limit.
Does transferring stock between my own warehouses affect the General Ledger?
No - warehouse-to-warehouse transfers deliberately never post to the ledger, since no value changed hands between parties. Receiving, billing, selling, and damage/loss adjustments all post automatically; internal transfers stay purely operational.
What happens to inventory lines I don’t count during a cycle count?
They’re left untouched, never assumed to be zero. Posting a cycle count only creates adjustment movements for lines that actually came out different from what the system expected - uncounted lines simply keep their existing recorded quantity.
If I set a capacity limit on a warehouse, does the system stop me from exceeding it?
Not currently - a capacity ceiling can be stored per warehouse, but nothing today enforces it or shows usage against it. It’s stored for future use rather than being an active limit right now.
Resources
Was this guide helpful?