Skip to main content
The catalog is the closed list of supplies your dental clinic works with. Every order line, stock box and consumption record points to a supply in this list, so a supply has to exist here before anyone can order, receive or use it. The console calls each catalog item a supply; the API and the code call it an item.

​
Who can do it

Permissions are assigned per member on the Team screen. See Roles and permissions.

​
Where

Open Catalog in the main navigation. The module has three item screens:

​
The catalog list

The Catalog screen (Organize the supplies used by your dental clinic.) shows:
  • New supply, in the page header, if you hold catalog.manage.
  • A search box, Search by SKU or name. It matches any part of the SKU or the name, ignoring letter case and accents, so anestesico finds “Anestésico local”.
  • Links to Categories, and, if you hold catalog.manage, Import CSV and Export CSV. See Categories and Import and export.
  • Two filters: Category (default All categories) and Status (default All statuses, then Draft, Active, Inactive). Clear filters resets the search and both filters.
The table has the columns SKU, Supply name, Category, Unit and Status, plus Cost when you hold catalog.cost.read. Click the supply name to open it. Supplies are listed in the order they were created, oldest first, 50 per page, with Previous and Next below the table and a counter of the rows shown out of the total.

​
Create a supply

1

Have a category ready

Every supply belongs to a category. If none exists, the form says Create a category before adding supplies. You can create one from Categories or with New category inside the form, which selects the new category for you.
2

Open the form

In Catalog, click New supply. The page New supply opens with Define how this supply is identified and tracked.
3

Fill in the supply information

Under Supply information, enter SKU, Supply name, Category, Unit, Packaging, Criticality and Description. The rules for each field are in the table below.
4

Choose the tracking requirements

Under Tracking requirements (These choices define the information required when registering stock.), tick Track lots, Track serial numbers, Track expiration dates and High-value supply as needed. All four start unticked.
5

Save

Click Create supply. The console opens the new supply’s detail page. The supply starts as Draft: activate it when it is ready to be ordered.
The creation form has no cost field. Record the cost on the supply’s detail page after creating it, or include it in a CSV import. See Costs.

​
Fields and validation

The Unit is the base unit the supply is counted in everywhere: stock, orders, consumption and presentations. The allowed values are:
The free-text Packaging field is not a presentation. To say that a box contains 100 units, so that receiving 3 boxes adds 300 units, add a presentation on the supply. See Presentations and codes.

​
What the tracking choices do

A change to these choices applies to receptions recorded after the change; boxes already received keep what was recorded. See Receive stock, Order approval policy and Stock corrections. Criticality is stored, shown on the supply and included in exports. On the current release it does not change alerts, replenishment or approvals.

​
Statuses

There is no way back to draft, and supplies cannot be deleted. Deactivate a supply you no longer use.

​
Why only active supplies can be ordered

When someone adds a supply to an order, muveya copies the supply’s SKU, name, unit, category, high-value flag and current cost onto the order line. That copy only means something if the unit is final, so the order screen offers active supplies only, and the server refuses any other with orders.catalog_item_unavailable: This supply is not active in the catalog. Order lines that were already added keep their copy even if the supply is later deactivated or edited. See Create and track orders.

​
The supply detail page

Open a supply from the list. The page title is the supply name, with Back to catalog above it.
  • If you hold catalog.manage, you see the same form as on creation, with the current values. SKU is locked and says The SKU identifies this supply and cannot be changed. Click Save changes; Supply saved confirms it.
  • Otherwise, you see a read-only list: SKU, Category, Unit, Packaging, Description, Criticality, the four tracking choices as Yes or No, and Cost if you hold catalog.cost.read.
Below the details, every reader sees:
  1. Status, for example Status: Draft, with Only active supplies can be added to new orders.
  2. Presentations: how the supply is bought and received. See Presentations and codes.
  3. Supply cost, only for members who hold both catalog.manage and catalog.cost.read. See Costs.

​
Activate or deactivate

1

Open the supply

Go to Catalog and click the supply name.
2

Check the unit

For a supply that is not active, the status section says Activation makes this supply orderable and fixes its unit: followed by the unit. If you changed the unit and have not saved yet, it says Save or discard the unit change before activating.
3

Click the button

The button reads Activate and fix unit when activation will also fix the unit, Activate supply when the unit is already fixed, and Deactivate supply when the supply is active.

​
The unit becomes fixed

Stock, orders and presentations are all counted in the supply’s base unit, so changing it after use would change the meaning of recorded quantities. muveya protects the unit:
  • The unit becomes fixed the first time the supply is activated, or the first time stock of the supply is received, even while it is still a draft.
  • Once fixed, it stays fixed, also after deactivation. The form shows the unit as text with This unit is protected and cannot be changed. You can edit the other details.
  • Everything else except the SKU stays editable: name, description, category, packaging, criticality and the tracking choices.
While the unit is not fixed, you can change it and save it together with the other fields. Before you save, the form shows Selected change: with the new unit and a Discard unit change button. Changing the unit has consequences:
  • A cost recorded for the old unit moves to review_required and must be confirmed again. See Costs.
  • A presentation published under the old unit cannot be used for receiving until you correct it, which republishes it under the current unit.
If the unit cannot be checked or has changed meanwhile, the form tells you:

​
Identifiers

The console always shows names, never raw ids, except on the CSV import screen where you need to copy category ids.

​
Reading the catalog outside the console

The public API reads the catalog with GET /v1/catalog/items and GET /v1/catalog/items/{itemId} (scope catalog:read), and the MCP tool catalog.search finds supplies by name or SKU (active ones by default). Both are read-only: supplies are created and edited only in the console or through a CSV import. See the API reference and MCP tools.

​
What the system records

  • The supply, with status draft, when it is created.
  • When the unit is fixed: who fixed it and when.
  • Field edits and status changes update the supply. On the current release they are not written as separate audit entries; CSV imports, exports and package code retirements are.

​
What can go wrong

Categories

Create the groups every supply belongs to.

Presentations and codes

Describe how a supply is bought and the codes printed on it.

Costs

Record costs and understand who can see them.

Import and export

Create many supplies at once from a CSV file.

Receive stock

Put stock of a supply into a warehouse.

Create and track orders

Order active supplies for a location.