# Commercial Context, the AI-native foundation > Commercial Context is the layer that tells Revomo what your price, cost and customer data means, so every product above it answers in your language instead of your column names. Source: https://revomo.ai/commercial-context/ --- Revomo platform architecture ## Your data does not mean anything. Until it does. Every pricing tool can read your columns. None of them know what `NET_PR_2` is. Commercial Context is the layer that tells the system what your price, cost and customer data means, so every product above it answers in your language instead of your column names. **The model, in five planes.** Drag to turn it. Click a group to zoom in and read its instances. Counts are a specimen scale for a mid-market distributor, not measured figures. Context on ← All groups **PRICE***184* **QUOTE***268* **CONTRACT***96* **INCENTIVES***74* **APIS***38* **AGENTS***26* **RULESETS***46* **PUBLISHING***31* Decision intelligence **ANALYTICS***412* **PLANNING***148* **OPTIMIZATION***86* **PREDICTIVE MODELS***74* Datasets and views **MARGIN***148* **CUSTOMER***310* **PRODUCT***274* **DEAL***190* **AGREEMENT***87* **DATASETS***94* **COST***132* Commercial Context **INDUSTRY PROFILE***42* **BUSINESS PROFILE***68* **BUSINESS GLOSSARY***233* **SEMANTIC MODEL***128* **SEMANTIC MAPPINGS***412* **POLICY***57* Raw data and objects **ERP***1,840* **CRM***960* **CPQ***640* **FILES***1,260* ### The same model, as text - **PRICE** on the execute plane, 184 objects. - **QUOTE** on the execute plane, 268 objects. - **CONTRACT** on the execute plane, 96 objects. - **INCENTIVES** on the execute plane, 74 objects. - **APIS** on the execute plane, 38 objects. - **AGENTS** on the execute plane, 26 objects. - **RULESETS** on the execute plane, 46 objects. - **PUBLISHING** on the execute plane, 31 objects. - **ANALYTICS** on the decide plane, 412 objects. - **PLANNING** on the decide plane, 148 objects. - **OPTIMIZATION** on the decide plane, 86 objects. - **PREDICTIVE MODELS** on the decide plane, 74 objects. - **MARGIN** on the view plane, 148 objects. - **CUSTOMER** on the view plane, 310 objects. - **PRODUCT** on the view plane, 274 objects. - **DEAL** on the view plane, 190 objects. - **AGREEMENT** on the view plane, 87 objects. - **INDUSTRY PROFILE** on the context plane, 42 objects. - **BUSINESS PROFILE** on the context plane, 68 objects. - **DATASETS** on the view plane, 94 objects. - **COST** on the view plane, 132 objects. - **BUSINESS GLOSSARY** on the context plane, 233 objects. - **SEMANTIC MODEL** on the context plane, 128 objects. - **SEMANTIC MAPPINGS** on the wedge plane, 412 objects. - **POLICY** on the context plane, 57 objects. - **ERP** on the source plane, 1,840 objects. - **CRM** on the source plane, 960 objects. - **CPQ** on the source plane, 640 objects. - **FILES** on the source plane, 1,260 objects. - **Industry Profile** (starter ontology). How your industry prices before you change a thing. Distribution sells from a matrix, manufacturing sells from a cost roll-up, and the context arrives knowing the difference. - **Business Profile** (no standard term). What you sell, who you sell it to, on what terms, in what units. Your branches, your product hierarchy, your customer tiers. - **Business Glossary** (business glossary). What you call things. If your team says landed cost and means something specific by it, the system says it too. - **Semantic Model** (semantic model). What price, cost, discount and rebate mean. How they aggregate, what rolls up to what, which one wins when two disagree. - **Semantic Mappings** (semantic mapping). Which column is which. This is the part everyone else makes you hand-author, and the reason semantic layer projects take months. RV·2026·CC-01 · How it builds ### The context builds itself. A semantic layer is only useful once someone has told it which column is which. Everywhere else that job is months of consulting, and it is why so few of these projects reach production. Auto-Mapping does the first pass on load, from the files you already have, and shows you what it could not resolve rather than guessing. Five source shapes, one resolved layer. Nothing above the line reads a source system directly. The dashed leg is the policy document: prose rather than columns, so it is extracted and cited instead of mapped. What lands Auto-Mapping What it means `NET_PR_2` Net price `CUST_SHIP_TO` Ship-to customer `MTL_STD_CST` Standard material cost `REB_ACCR_YTD` Rebate accrual, year to date `BRNCH_CD` Branch `UOM_ALT` Alternate unit of measure Specimen Column names and the 340 of 412 resolution figure shown here are illustrative of a typical distributor load, not a published benchmark. RV·2026·CC-02 · How it learns ### It changes when your business changes. A context that is authored once and never revisited is a liability. Every change to this layer arrives as a proposal with a source, and moves through the same approval states as a price change. CTX·PROP·0417 Awaiting review Proposed · Semantic Model Define **Landed Cost** as standard material cost plus inbound freight, excluding duty. Because “Landed cost for margin reporting is material plus inbound freight. Duty is carried separately.” Pricing Policy 2026, section 4.2, line 118 Lineage **3 metrics · 2 guardrails · 1 rebate program** Draft Submitted Review Approved 01 #### Lineage dependency graph Every definition knows what depends on it. Before a change is approved the layer can say which metrics, guardrails and programs move with it, which is the difference between reviewing a change and guessing at it. 02 #### Drift Detection semantic drift A new product line, a new system, a table that stopped being written to. The context raises it instead of quietly modeling a business that no longer exists. 03 #### Policy Statements extracted definitions with provenance Definitions pulled out of your pricing policy document, each shown with the line it came from, so a rule can be traced back to the sentence that authorised it. 04 #### Context Pack portable semantic model The whole setup as one portable file. Move it between environments, diff two versions, or start from an industry pack, which is just one you did not have to write yourself. Specimen An illustrative proposal. The states shown are the ones Revomo uses for governed changes; the definition and citation are made up for the example. RV·2026·CC-03 · What is inside ### Five things, one layer. Four of these have an industry name. The fifth is the one that is normally left to you. 01 #### Industry Profile starter ontology How your industry prices before you change a thing. Distribution sells from a matrix, manufacturing sells from a cost roll-up, and the context arrives knowing the difference. Structures Metrics Defaults 02 #### Business Profile no standard term What you sell, who you sell it to, on what terms, in what units. Your branches, your product hierarchy, your customer tiers. Hierarchies Segments Units 03 #### Business Glossary business glossary What you call things. If your team says landed cost and means something specific by it, the system says it too. Terms Synonyms Owners 04 #### Semantic Model semantic model What price, cost, discount and rebate mean. How they aggregate, what rolls up to what, which one wins when two disagree. Entities Hierarchies Metrics 05 #### Semantic Mappings semantic mapping Which column is which. This is the part everyone else makes you hand-author, and the reason semantic layer projects take months. Columns Keys Confidence **Bold** is the Revomo term. The line under it is what the industry calls the same thing, where the industry has a word for it at all. RV·2026·CC-04 · What runs on top ### Everything above it lives in it. These are not eight products integrated with a semantic layer. They are eight products that have no other definition of price, cost or customer to read. Change a definition once and every one of them changes with it. The one that writes #### Commercial Data & Context The Studio is where the context is authored, reviewed and versioned. Every other module reads what is agreed here and cannot overrule it, which is the whole point of putting the meaning in one place. The seven that read ##### Analytics & Insights reads **Semantic Model** Margin means one thing, so two dashboards cannot disagree about it. ##### Planning & Forecasting reads **Business Profile** Plans roll up through your hierarchy, in your units, on your calendar. ##### Decision Optimization reads **Semantic Model** Constraints are written against defined metrics, not against column names. ##### Price Management reads **Semantic Mappings** A guardrail on cost holds even when the cost column is renamed upstream. ##### Quote Management reads **Business Glossary** The quote uses your deal vocabulary, so sellers do not translate. ##### Contract Management reads **Business Profile** Terms attach to the entities you actually contract with. ##### Incentives Management reads **Semantic Model** An accrual is calculated from the same definition that reports it. Module availability differs. See [the platform](https://revomo.ai/platform/) for what is shipping today and what is in beta. Plate C1 · Series 2026 · Commercial Context · RV·2026·CC ### See it read your columns Bring a price file and a policy document. We will map them live and show you what the context resolves, and what it flags. [Book a walkthrough](https://revomo.ai/contact/?plan=Commercial%20Context%20walkthrough)[See the platform](https://revomo.ai/platform/)