Business hierarchy
Miridia has two levels of account: the organisation and the business. This page explains the difference, and how a group of businesses can share data.
Organisation and business
An organisation is the tenant. It is the account that you register. All the data of an organisation is kept apart from all other organisations. Your users, your API keys, and your subscription belong to the organisation.
A business is a trading entity inside the organisation. It has its own name, address, registration number, locations, products, orders, and stock. An organisation has one business when you register. You can add more.
Read Concepts for the full model.
Register an organisation
You register an organisation once, on the sign-up page of the portal. The registration creates the organisation, the first business, and the first user. That user is the owner.
To register through the API, send POST /api/organizations to the Global API. Read Organization.
Add a business
To add a business to an organisation that exists, send POST /api/business to the Core API. This needs a signed-in user with the correct permission. It does not create a new organisation.
Select the business
A user can have access to more than one business. The portal has a business switcher.
An API client selects the business with the X-Business-Id request header. Miridia checks that the user has access to that business. Read Authentication.
Master and sub-businesses
A franchise or a multi-branch operation can use one master business and many sub-businesses. A sub-business has the master as its parent. To list the sub-businesses of a business, call GET /api/business/{businessId}/children.
Planned: what the sub-business inherits
The master business will define this data, and each sub-business will read it without a copy:
- the product catalogue
- the bills of material
- the suppliers
- the price lists
A sub-business will not be able to change inherited data.
Planned: what stays local
Each sub-business will keep its own:
- inventory at its own locations
- sales orders, purchase orders, and transfer orders
The master business will have read access to all sub-businesses for consolidated reports.
Planned: configurable rules
| Rule | Options |
|---|---|
| Product ownership | Master only, or shared (a sub-business can add local products) |
| Customer sharing | Shared, isolated for each sub-business, or optional for each customer |
| Pricing model | Uniform, regional (a price list for each zone), or transfer pricing |
A product visibility setting will control which sub-businesses can see and sell each product. The location capability flags will control which locations can buy, request, and fulfil. Read Locations.