Plugixa Inventory

Items

Assets, consumables and sellable goods, each with a SKU, a barcode, a reorder level and a cost and sale price.

Warehouses

Locations with their own stock levels and their own valuation, rather than one address the whole catalogue shares.

Categories

Group the catalogue so lists, filters and the dashboard's breakdown by type have something to work with.

Recipients

The people assets are checked out to, so a laptop that has left the building is still an item you can find.

Custom fields Pro

Your own data on records, grouped into field groups, for the things a stock system cannot guess you track.

Units of measurement Pro

Count in boxes, metres or litres rather than in bare numbers, with the unit carried through documents and reports.

Check in and check out

Assets go out to a recipient and come back. Stock is added and removed. All four are the same document with a different direction.

Finalising writes the ledger

A draft changes nothing. Finalising posts the movement, and from then on the document cannot be edited or deleted.

Inventory adjustments Pro

Write off breakage, shrinkage and a count that disagrees with the system, as a document with a reason rather than a silent edit.

Warehouse transfers Pro

Move stock between locations as one document, so it leaves one warehouse and arrives at another without passing through a void.

Append-only, by construction

No REST route, no admin screen and a veto in the data layer. A ledger somebody can edit is not an audit trail.

On-hand is derived

Quantities follow from the ledger rather than being kept beside it, so the two cannot drift apart unnoticed.

Reconcile proves it

A built-in check compares every on-hand quantity against the ledger, on demand from the admin or from WP-CLI.

Corrections are visible

A mistake is fixed with a second, opposite document. That is what every stock system does, and what the audit trail is for.

Stock per location

Ten in the west depot and none in the east is two facts, not an average. Netting them into one number loses both.

A view per warehouse

Its own stock list, its own low-stock list and its own activity feed, rather than a filter on a global list.

Valuation per warehouse

What the stock in one location is worth, which is the number a site with more than one address actually needs.

Transfers between them Pro

One document that takes stock out of one warehouse and puts it into another.

Stock dashboard

Total value, broken down by type and by warehouse, with a movement trend over time.

Top movers

What is actually turning over, which is rarely the same list as what takes up the most space.

Closest to running out

Items ranked against their own reorder level, so the list is about urgency rather than about quantity.

Reports and analytics Pro

Deeper reporting across movements, valuation and activity, beyond what the dashboards summarise.

Average costing

What the free edition costs stock at. The item's cost price, falling back to its sale price where no cost has been recorded.

Outgoing costed separately

What a movement cost is recorded on the ledger row that removed it, so it is a different question from what the remaining stock is worth.

FIFO and LIFO Pro

Layer costing, where stock is consumed oldest-first or newest-first and each layer keeps the cost it arrived at.

Opening balances seeded Pro

Layers are seeded from what you already hold, so switching costing method does not start your history again.

A column-matching step

Match your file's columns to the fields before anything is written, so an unexpected header is a question rather than a mess.

Looked up by name or code

A file can say "Power tools" rather than an id, and a line naming something that does not exist is reported by line number instead of invented for you.

Opening stock is a real document

It arrives as a finalised movement rather than a number written onto a record, so the ledger and the valuation agree with it from day one.

Batched, resumable, revertible

Large files import in batches and can be resumed, and an import can be undone: the records go to the trash and the stock is taken back out with a reversing document.

Export what you are looking at

Every list has an Export button that writes the current view to CSV, filters and all.

One shortcode

[plugixa_inventory_app] with width, height and mode attributes. Your header and footer stay where they are, and there is a full-screen button in the toolbar.

The same API, the same rules

It is the application the admin screen loads, talking to the same API, so there is no second set of permissions to keep in step.

Install it as an app Pro

A progressive web app, so the inventory can live on a phone or a tablet home screen on the warehouse floor.

Dark mode Pro

For the people who are in it all day, and for a screen mounted somewhere the lights are low.

App manager

Switching an app off hides it everywhere, stops its endpoints answering and stops its background work, and keeps every record it holds.

Settings

Formatting, currency, appearance and each app's own options, in one place.

Notifications and alerts

Low stock and the things that need somebody, raised where whoever is working will see them.

Desktop notifications Pro

The same alerts as browser notifications, for a screen nobody is watching continuously.

Roles and permissions Pro

Who may see and change what, separately from their WordPress role.

Concurrent finalises cannot oversell

The sufficiency check is the WHERE clause of the write, so there is no window between deciding and writing. The second person is told the stock changed and nothing is written.

A daily check that reports

It compares every on-hand quantity against the ledger and reports anything that disagrees. It reports; it never silently corrects.

Reconcile from the command line

wp plugixa-inventory stock reconcile does the same thing, for sites too large for a browser request.

Its own tables, not posts

Stock levels, ledger rows and document lines are relational data. As posts and post meta, every list and report gets slower as history grows.