Master Data

Master data is the set of relatively stable records that the rest of Pharus operates on. Materials, products, customers, vendors, and locations don't do anything by themselves — they are the nouns that orders and inventory reference. A purchase order buys a material from a vendor into a location; a sales order ships a product to a customer. Get the master data right and everything built on top of it stays consistent.

This is the counterpart to the Modules, which are the transactional records that move stock and progress through a lifecycle.

The records

Record	What it is
Materials	Raw inputs you purchase and consume
Products (SKUs)	Finished goods you make, buy, and sell
Bills of Materials	The recipe linking a product to its components
Customers	The organizations you sell to
Vendors	The suppliers you buy from
Brokers	Commission-taking intermediaries on sales
Contacts	People linked to customers and vendors
Locations	Warehouses and sites where stock lives
Types & Configuration	The lookup lists that classify the records above

A few conventions that hold everywhere

• Org-scoped. Every record belongs to a single organization and is invisible to any other. You never pass an organization id around — it's bound to your credentials.
• Deactivate, don't delete. Most records carry an isActive flag. Once a record has been referenced by an order or a ledger entry it can't be hard-deleted, because that would orphan history. Deactivating hides it from new work while preserving the past.
• Codes and names. Materials and products carry a human code (materialCode, skuCode) that's unique within your organization; most other records are identified by name.

Every record here is reachable through both the REST API and the MCP server.