Mecalux/mcp-wms-wiki
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

lint(standard): corrections completes mode standard

Browse Source 
- Em dashes: 1712 remplaces par tirets simples (86 fichiers + _index.md,
  en-tete section Limagrain conserve)
- Checklists: 24 '- [ ]' -> '- ☐' (3 pages operations, plus de todos Obsidian)
- Ancres: 33 reparees (slugs GitHub + ancres HTML <a id> reconnues),
  1 reciblee (manuel de reten)
- related: tenseflow -> tense-flow, pie -> mechanical-elements,
  group.md retire (doublon shipping)
- Registre: compteur global 122 -> 131 pages
- Rapport racine _lint_report.md mis a jour (scan v2 + re-scan final: 0 anomalie)
- Aucun fichier limagrain/ modifie (cloisonnement)
This commit is contained in:
Arthur
2026-07-20 13:01:21 +02:00
parent 7496aafe64
commit 9ce6ae37be
88 changed files with 1769 additions and 1871 deletions
Download Patch File Download Diff File Expand all files Collapse all files
wiki/concepts/account-owner.md
+10 -10
View File
@@ -24,9 +24,9 @@ last_compiled: "2026-04-10"
EasyWMS uses two related but distinct entities for commercial master data: **Owner** and **Account**.
- An **Owner** is the entity that owns the stock in the warehouse (a sales company, the organization itself, or — in 3PL contexts — an external client). Every stock record has an owner. Owners can mix stock with each other only when mixing is explicitly enabled.
- An **Owner** is the entity that owns the stock in the warehouse (a sales company, the organization itself, or - in 3PL contexts - an external client). Every stock record has an owner. Owners can mix stock with each other only when mixing is explicitly enabled.
- An **Account** is a delivery point / customer of the warehouse — the entity to which a shipping order's stock is destined. Accounts represent end-customers or delivery addresses; they are referenced on outbound orders to control carrier preferences, label formats, and FEFO rules.
- An **Account** is a delivery point / customer of the warehouse - the entity to which a shipping order's stock is destined. Accounts represent end-customers or delivery addresses; they are referenced on outbound orders to control carrier preferences, label formats, and FEFO rules.
The two are distinct: an owner holds inventory rights; an account receives shipments. A single owner can have many accounts (multiple delivery points). In 3PL deployments with Owner Extensions enabled, every receipt order, shipping order, and master data entity must be assigned to an owner.
@@ -45,7 +45,7 @@ The two are distinct: an owner holds inventory rights; an account receives shipm
### Owner mixing rules
By default, new owners are created with mixing **disabled**. Mixing can be enabled per owner. Additionally, specific owner exclusions can be added (preventing mixing with specific other owners). Mixing checks apply to: items, item types, item families, logistic attributes, and owners simultaneously.
In **automatic warehouses**, mixing restrictions are hard-enforced — the system will not allow a container to be stored if mixing rules are violated. In **manual warehouses**, operators can override mixing warnings.
In **automatic warehouses**, mixing restrictions are hard-enforced - the system will not allow a container to be stored if mixing rules are violated. In **manual warehouses**, operators can override mixing warnings.
---
@@ -84,10 +84,10 @@ In **automatic warehouses**, mixing restrictions are hard-enforced — the syste
## Related
- [[stock]] — every stock record has an owner; owner mixing rules determine co-location eligibility
- [[order-outbound]] — shipping orders reference accounts (delivery destination) and can reference owner
- [[order-inbound]] — receipt orders reference owners when Owner Extensions is active
- [[owner-extensions]] — prerequisite module for mandatory owner assignment; enables per-owner data isolation
- [[billing-3pl]] — 3PL billing contracts are created per owner
- [[3pl-portal]] — 3PL portal access is filtered per owner; user group assignment controls visibility
- [[erp-interface]] — OWN and ACC messages manage owner/account master data from ERP
- [[stock]] - every stock record has an owner; owner mixing rules determine co-location eligibility
- [[order-outbound]] - shipping orders reference accounts (delivery destination) and can reference owner
- [[order-inbound]] - receipt orders reference owners when Owner Extensions is active
- [[owner-extensions]] - prerequisite module for mandatory owner assignment; enables per-owner data isolation
- [[billing-3pl]] - 3PL billing contracts are created per owner
- [[3pl-portal]] - 3PL portal access is filtered per owner; user group assignment controls visibility
- [[erp-interface]] - OWN and ACC messages manage owner/account master data from ERP