The ERP Glossary 60+ Terms Every SME Leader Should Know

ERP, defined in one paragraph

ERP (Enterprise Resource Planning) is software that integrates core business processes — finance and accounting, HR, manufacturing, supply chain, procurement, inventory, and sales — into one unified platform built on a shared database. The defining trait is not any single feature; it is the integrated shared data model that replaces disconnected apps, manual re-keying, and the spreadsheet glue holding them together.

The acronym matters because it tells you the scope: 'enterprise' (the whole organisation, not one department), 'resource' (people, money, materials, capacity), and 'planning' (forecasting, scheduling, allocating those resources). An ERP is one connected system and one source of truth — which is why definitional queries like 'what does ERP stand for' and 'ERP meaning' map directly onto this page.

By 2026 the conversation has layered new vocabulary on top of that core: agentic AI that acts inside the ERP, usage-based AI capacity such as Copilot Credits, composable architectures assembled from interoperable components, and product-specific integration patterns like dual-write. The classical definitions below still hold; the modern terms tell you how vendors are packaging autonomy, licensing, and integration. For the plain-English deep dive rather than a glossary entry, see our companion guide at /learn/what-is-erp.

Browse ERP terms by topic

A 15-second scan of an alphabetical list rarely sticks. Use these topic buckets to jump to the cluster you need in a vendor meeting, then open the full definition in the A–Z sections below. Every term still appears once alphabetically; this map is only a navigation layer.

**Core definition & history** — ERP, ERP II, MRP, MRP II.

**Finance & inventory valuation** — COGS, FIFO, LIFO, GAAP, IFRS, Chart of accounts, KPI, ROI, TCO.

**Supply chain & manufacturing** — BOM, SKU, MRP, MES, PLM, APS, WMS, SCM, ASN, Order-to-cash, Procure-to-pay.

**Customer & commercial** — CRM, Commerce Scale Unit (CSU).

**Integration & data** — API, EDI, ETL, Integration, Middleware, iPaaS, Dual-write, Dataverse, Master data, MDM, Golden record, Data migration.

**Deployment & architecture** — Cloud ERP, On-premise, SaaS, IaaS, PaaS, Multi-tenant, Single-tenant, Hybrid ERP, Two-tier ERP, Composable ERP.

**Implementation lifecycle** — Pilot, UAT, Cutover, Go-live, Hypercare, Rollout, Sandbox, Change management, Post-implementation review, RACI, SLA, Workflow, Approval matrix.

**AI & 2026 licensing jargon** — Agentic ERP, AI agent, Copilot Credits, Customization vs configuration. For a deeper treatment of agents inside ERP, see /learn/ai-agents-in-erp.

Key ERP acronyms at a glance

Use this table as a quick-decode reference when you hit ERP jargon in a vendor demo, RFP, licensing quote, or support ticket. Each acronym is expanded and given a one-line meaning; full definitions with cross-references follow in the alphabetical and 2026 sections below.

2026 ERP terms: agents, credits, dual-write, and composable design

Vendor demos and licensing quotes in 2025–2026 use a layer of jargon that classic MRP/ERP glossaries omit. These terms do not replace the definitions of ERP, MRP, or BOM — they describe how AI capacity is sold, how front-office and back-office apps stay in sync, and how architecture is assembled when a single monolith is no longer the default.

**Agentic ERP / AI agents** — Agentic ERP integrates autonomous AI agents into enterprise resource planning so the system can perceive live operational data, reason through multi-step decisions, and execute actions across procurement, inventory, finance, or supply chain within defined guardrails — not merely answer chat questions. Industry commentary in 2026 frames this as a shift from copilots (assist) to agents (act). Gartner-linked forecasts commonly cited in the trade press project material agentic decision share later this decade; treat percentages as directional, not a guarantee for your industry. See also: Copilot Credits, Workflow. Deep dive: /learn/ai-agents-in-erp and /learn/ai-in-erp.

**Copilot Credits** — Microsoft's usage-based capacity unit for Copilot Studio agents and many generative AI tools in the Power Platform / Dynamics stack. As of Microsoft's public pricing pages, Copilot Credit packs are sold at 25,000 credits per pack for $200/pack/month, with pay-as-you-go also available (commonly described as about $0.01 per credit). Different agent actions consume different rates (for example classic answers, generative answers, and agent actions). Dynamics 365 Premium SKUs have also been documented as including a monthly pool of Copilot Credits per user; older seeded AI Builder credits are being retired on a published schedule (seeded AI Builder credits remain usable monthly until 1 November 2026, then are removed). Always verify current rates in Microsoft Learn and your licensing agreement before budgeting TCO. See also: SaaS, TCO, SLA.

**Dual-write** — Microsoft's out-of-the-box infrastructure for near-real-time, bidirectional integration between Dynamics 365 finance and operations apps and Dataverse (and therefore customer-engagement apps such as Sales or Customer Service). A change written in finance and operations is written to Dataverse, and a change in Dataverse is written back — enabling a shared customer, product, and vendor master without nightly batch jobs. Architects on X and community forums regularly warn that bidirectional maps need careful ownership rules and error handling; dual-write is powerful, not magic. See also: Integration, Dataverse, API, Master data.

**Dataverse** — Microsoft's cloud data platform that underpins Dynamics 365 customer-engagement apps and much of the Power Platform. In dual-write scenarios it is the common data plane that lets CRM-side and ERP-side records stay aligned. See also: Dual-write, PaaS, Integration.

**Commerce Scale Unit (CSU)** — In Dynamics 365 Commerce, the retail services / headless commerce runtime that hosts channel logic for POS, e-commerce, and third-party storefronts. CSU (including self-hosted options for unreliable store connectivity) is the piece that answers real-time pricing, cart, and inventory calls without routing every request through the full back-office stack. See also: Cloud ERP, Hybrid ERP, API.

**Composable ERP** — An adaptive architecture strategy (popularised in Gartner research) that assembles foundational administrative and operational capabilities from interoperable components, APIs, and application experiences so the business can change modules without a full rip-and-replace. Think 'built to change' rather than 'built to last as one monolith.' Composable design depends on clean master data and an integration/orchestration layer; without those, you re-create silos. See also: Two-tier ERP, iPaaS, API, Customization vs configuration. Architecture context: /learn/erp-architecture.

**Two-tier ERP** — A deliberate strategy where the corporate parent runs a tier-1 ERP for group finance and control while subsidiaries, brands, or regions run a lighter, often cloud tier-2 ERP for local operations — integrated rather than forced onto one global template on day one. Common after M&A or when local statutory and go-to-market needs outpace corporate rollout speed. See also: Hybrid ERP, Rollout, Integration. Deployment models: /learn/erp-deployment-models.

**iPaaS (Integration Platform as a Service)** — A cloud-hosted integration platform that connects ERP, CRM, ecommerce, WMS, and other SaaS or on-prem systems with managed connectors, transformations, and monitoring — without you operating classic on-premise middleware hardware. iPaaS is the modern default for multi-app landscapes; it sits beside (and often replaces) bespoke point-to-point APIs. See also: Middleware, API, ETL, Integration. Patterns: /learn/erp-integration-patterns.

ERP terms: A to C

**Agentic ERP** — An ERP posture in which autonomous AI agents can initiate and complete multi-step operational work (for example reordering, exception handling, or invoice triage) inside defined policies, rather than only suggesting next actions to a human. See the 2026 vocabulary section for licensing and governance caveats. See also: AI agent, Copilot Credits, Workflow.

**AI agent (in ERP)** — Software that pursues a goal across live ERP data with limited human input — perceiving state, deciding next steps, and executing transactions or updates. Distinct from a copilot (assists a user) and from a fixed RPA script (replays a rigid path). See also: Agentic ERP, BPM, Approval matrix.

**API (Application Programming Interface)** — A set of rules that lets two software systems exchange data programmatically. In ERP, APIs let your platform connect to ecommerce, CRM, payroll, or shipping tools without manual export-import loops, and they are the modern backbone of integration alongside pre-built connectors and iPaaS. See also: Integration, Middleware, EDI, iPaaS.

**Approval matrix** — A rules table defining who can approve transactions (purchase orders, expenses, journal entries) up to defined limits, by amount, type, and department. ERPs enforce the approval matrix automatically via workflow, replacing emailed sign-offs. Agent-driven approvals still sit on top of this matrix; autonomy without authority rules is a control risk. See also: Workflow, RACI.

**APS (Advanced Planning and Scheduling)** — Planning software that optimises production schedules against finite capacity, material availability, and constraints more deeply than basic MRP time-phasing. Often integrated with ERP manufacturing modules or run as a specialised planner. See also: MRP, MES, BOM.

**ASN (Advance Ship Notice)** — An electronic document (often via EDI) that tells a buyer what is about to arrive, in which quantities, and on which shipment — before the truck shows up. ASNs feed receiving, WMS putaway, and three-way match. See also: EDI, WMS, SCM.

**BI (Business Intelligence)** — The tools and processes that turn ERP transaction data into dashboards, reports, and analytics for decision-making. A BI layer typically sits on top of the ERP's shared database and surfaces KPIs in real time rather than at month-end. See also: KPI, ERP dashboard.

**BOM (Bill of Materials)** — The structured list of raw materials, sub-assemblies, and quantities needed to manufacture a product. Manufacturing ERPs use the BOM to calculate material requirements, cost, and what to purchase. See also: MRP, MRP II, SKU.

**BPM (Business Process Management)** — A discipline and toolset for modelling, automating, and optimising end-to-end business processes. Many ERPs embed BPM via workflow engines for approvals, ordering, and exception handling. See also: Workflow, Approval matrix.

**Change management** — The structured approach to preparing, supporting, and reinforcing people through an ERP transition so adoption sticks. It covers communication, training, and reinforcement — not just the cutover event — and is one of the biggest predictors of whether an ERP delivers its business case. See also: Hypercare, Go-live, ERP training. Guide: /learn/erp-change-management.

**Chart of accounts (CoA)** — The structured list of general-ledger accounts used to classify every financial transaction. In ERP implementations the CoA design is master data: get it wrong and every P&L, balance sheet, and management report inherits the mistake. See also: Master data, GAAP, IFRS.

**Cloud ERP** — ERP software hosted by the vendor or a partner and accessed over the internet, usually on a subscription basis. It removes on-premise server management and shifts cost from capital expenditure to operating expenditure. See also: SaaS, On-premise, Multi-tenant. Guide: /learn/cloud-erp-guide.

**COGS (Cost of Goods Sold)** — The direct costs of producing the goods a company sells — typically materials and direct labour. ERP finance modules calculate COGS from inventory and BOM data and post it to the profit-and-loss statement. See also: FIFO, LIFO, BOM, GAAP.

**Composable ERP** — An adaptive strategy for assembling ERP capabilities from modular, interoperable components and APIs so the organisation can change faster than a single monolithic release cycle allows. See the 2026 vocabulary section. See also: Two-tier ERP, iPaaS, API.

**Copilot Credits** — Usage-based capacity units for Microsoft Copilot Studio agents and related generative AI tools; packaged as prepaid packs (public list: 25,000 credits / $200 / month) or pay-as-you-go, with action-specific consumption rates. See the 2026 vocabulary section for Premium-licence seeding and AI Builder credit retirement dates. See also: TCO, SaaS.

**CRM (Customer Relationship Management)** — The processes and software for managing customer acquisition, sales, and service. CRM is frequently a module inside an ERP rather than a standalone system, so contacts, pipeline, and service history share the same database as finance and inventory. See also: ERP, ERP vs CRM. Guide: /learn/erp-vs-crm.

**CSU (Commerce Scale Unit)** — The Dynamics 365 Commerce runtime layer that serves real-time retail and headless channel operations (POS, e-commerce APIs), including self-hosted options for stores with unstable connectivity. See the 2026 vocabulary section. See also: Cloud ERP, API.

**Customization vs configuration** — Configuration meets a requirement using the ERP's built-in settings, parameters, and low-code designers (reversible and upgrade-safe); customization changes code or logic (more powerful but riskier and can break on upgrades). Drawing this line correctly per requirement is a major driver of long-term TCO. See also: TCO, On-premise. Guide: /learn/erp-customization-vs-configuration.

**Cutover** — The planned sequence of final data loads, system switches, and go/no-go checks that moves the business from legacy systems onto the new ERP. Cutover is an event inside the broader go-live programme, not a synonym for success. See also: Go-live, Data migration, Hypercare. Related: /learn/erp-cutover-plan.

ERP terms: D to F

**Data migration** — The structured process of moving financial, operational, and master data from legacy systems into the new ERP. It is one of the most failure-prone phases of an implementation and demands data cleansing, mapping, and validation before and after load. See also: Master data, Golden record, ETL. Guide: /learn/erp-data-migration.

**Dataverse** — Microsoft's low-code data platform that stores tables used by Dynamics 365 customer-engagement apps and Power Platform solutions; dual-write keeps selected finance-and-operations entities in sync with Dataverse tables. See also: Dual-write, PaaS, Integration.

**Dual-write** — Near-real-time bidirectional data synchronisation between Dynamics 365 finance and operations apps and Dataverse, so CRM and ERP share masters (customers, products, vendors) without batch lag. See the 2026 vocabulary section and Microsoft Learn dual-write overview. See also: Integration, Master data, API.

**EDI (Electronic Data Interchange)** — A standardised format for exchanging business documents — purchase orders, invoices, and advance ship notices — directly between trading partners' systems. EDI is common in retail, manufacturing, and logistics supply chains and is often handled inside or alongside the ERP. See also: API, SCM, Integration, ASN.

**ERP (Enterprise Resource Planning)** — Software that integrates core business processes — finance, HR, manufacturing, supply chain, procurement, inventory, and sales — into one unified platform on a shared database. The defining trait is the integrated data model, not any single feature. See also: CRM, MRP II, ERP II.

**ERP II** — A term introduced around 2000 for the next generation of ERP that extends beyond internal optimisation to connect external partners, customers, and the broader value chain over the internet. Most modern cloud ERPs already embody ERP II principles through integrated portals, APIs, and partner networks. See also: ERP, Cloud ERP.

**ETL (Extract, Transform, Load)** — A data integration pattern that pulls data from source systems, cleans and converts it, and writes it into a target such as the ERP or a data warehouse. ETL underpins both one-off data migration and ongoing BI feeds. See also: Data migration, BI, Middleware, iPaaS.

**FIFO (First In, First Out)** — An inventory valuation method that assumes the oldest stock is sold or used first. In inflationary periods FIFO tends to produce lower COGS and higher reported profit, and it is permitted under both GAAP and IFRS. See also: LIFO, COGS, GAAP.

ERP terms: G to I

**GAAP (Generally Accepted Accounting Principles)** — The standard accounting rules used in the United States for financial reporting. ERP finance modules are configured to comply with GAAP (and with other frameworks such as IFRS) for postings, valuations, and reports. See also: COGS, FIFO, LIFO, IFRS.

**Golden record** — A single, authoritative, de-duplicated version of a master-data entity — for example one 'true' customer or supplier record that every system agrees on. Achieving a golden record is the goal of master-data governance and is what makes cross-module reporting trustworthy. See also: Master data, MDM, Data migration.

**Go-live** — The moment an ERP system moves from implementation into live production use. Go-live is a milestone, not the finish line: the real adoption, stabilisation, and value-realisation work happens afterwards. See also: Hypercare, UAT, Pilot, Cutover, Post-implementation review.

**Hypercare** — A period of intensive, elevated support immediately after go-live — typically one to four weeks — to rapidly resolve issues as users hit the new system in real production conditions. Hypercare bridges the gap between cutover and steady-state support. See also: Go-live, Change management. Guide: /learn/erp-hypercare.

**Hybrid ERP** — A deployment that mixes cloud and on-premise components — for example a cloud ERP with an on-premise manufacturing module, or a two-tier setup with cloud subsidiaries feeding an on-premise corporate system. Hybrid lets firms move at different speeds by workload. See also: Cloud ERP, On-premise, Two-tier ERP.

**IaaS (Infrastructure as a Service)** — A cloud model where the provider supplies virtualised computing, storage, and networking, and you run your own platform and ERP software on top. ERP on IaaS offers control without owning physical hardware. See also: PaaS, SaaS, Cloud ERP.

**IFRS (International Financial Reporting Standards)** — The global accounting framework used in many jurisdictions outside the United States. Notable ERP impact: LIFO inventory valuation is prohibited under IFRS while allowed under US GAAP, so multinationals must configure valuation methods carefully. See also: GAAP, FIFO, LIFO.

**Integration** — The connection of an ERP with other systems (ecommerce, CRM, payroll, shipping, EDI) so data flows automatically rather than being re-keyed. Integration is typically delivered through APIs, iPaaS, middleware, or vendor pre-built connectors (including dual-write in the Dynamics stack), and it is what turns an ERP from a system of record into a system of action. See also: API, Middleware, EDI, iPaaS. Guide: /learn/erp-integration-patterns.

**iPaaS (Integration Platform as a Service)** — Cloud-delivered integration tooling that connects SaaS and on-prem applications with managed connectors, mapping, and monitoring — reducing the need to host classic middleware yourself. See the 2026 vocabulary section. See also: Middleware, API, ETL.

ERP terms: K to M

**KPI (Key Performance Indicator)** — A measurable value that shows how well a business is achieving a specific objective. ERPs and their BI layers surface KPIs — such as inventory turnover, order-to-cash cycle time, or gross margin — on dashboards for real-time management. See also: BI, ERP dashboard. Guide: /learn/erp-key-performance-indicators.

**LIFO (Last In, First Out)** — An inventory valuation method that assumes the newest stock is sold or used first. LIFO can reduce reported profit (and therefore tax) in inflationary periods; it is permitted under US GAAP but prohibited under IFRS, so multinational SMEs must choose carefully. See also: FIFO, COGS, GAAP, IFRS.

**Master data** — The core reference data that describes the business's key entities — customers, suppliers, products, the chart of accounts, and employees — shared consistently across modules. Clean master data is the foundation of reliable ERP reporting and clean financials. See also: Golden record, MDM, Data migration, SKU. Guide: /learn/erp-master-data-model.

**MDM (Master Data Management)** — The discipline, governance, and tooling used to create and maintain golden records for customers, products, suppliers, and other entities across systems. MDM is how multi-ERP and composable landscapes stay coherent. See also: Master data, Golden record, Data migration.

**MES (Manufacturing Execution System)** — Shop-floor software that executes, monitors, and records production in real time — work orders, machine status, labour, quality — bridging the gap between ERP planning and physical manufacturing. ERP plans; MES executes; PLM defines what is built. See also: MRP, APS, PLM, BOM.

**Middleware** — Software that sits between the ERP and other applications to translate, route, and orchestrate data, often providing pre-built connectors and error handling. Classic middleware is often on-premise; iPaaS is the cloud-hosted evolution of the same idea. See also: Integration, API, ETL, iPaaS.

**MRP (Material Requirements Planning)** — A planning technique developed in the 1960s that calculates what materials are needed, and when, based on demand and the bill of materials. MRP was the direct ancestor of modern ERP and remains the logic inside manufacturing modules. See also: BOM, MRP II, ERP, APS.

**MRP II (Manufacturing Resource Planning)** — A 1980s expansion of MRP that added capacity planning, shop-floor control, finance, and other business functions into one closed-loop system. MRP II broadened the scope from materials alone to the whole manufacturing operation, and it evolved into ERP in the 1990s. See also: MRP, ERP, BOM.

**Multi-tenant** — A cloud architecture where many customers share the same application instance and underlying infrastructure, kept logically separate. Multi-tenant SaaS lowers per-customer cost and enables seamless, vendor-managed upgrades, but it limits how deeply any one customer can customize the core. See also: Single-tenant, SaaS, Cloud ERP.

ERP terms: N to P

**On-premise (on-prem)** — ERP software installed and run on servers the customer owns and maintains inside its own data centre. On-premise offers maximum control and customization but shifts infrastructure, security patching, and upgrades entirely onto the customer's team. See also: Cloud ERP, Hybrid ERP, TCO.

**Order-to-cash (O2C)** — The end-to-end process from customer order capture through fulfilment, invoicing, and cash application. ERP modules for sales, inventory, shipping, and AR stitch O2C into one flow so cycle time and cash visibility improve together. See also: Procure-to-pay, CRM, WMS.

**PaaS (Platform as a Service)** — A cloud model that provides a managed platform — runtime, database, and development tooling — for building and running applications. ERP vendors use PaaS (such as Microsoft Azure and the Power Platform / Dataverse) to host extensions and custom apps safely alongside the core ERP. See also: IaaS, SaaS, Customization vs configuration.

**Pilot** — A limited first deployment of the ERP to a single site, business unit, or process before full rollout. A pilot validates the design, tests integrations, and surfaces change-management lessons at small scale before the wider organization commits. See also: Rollout, Go-live, UAT. Related: /learn/erp-pilot-vs-big-bang.

**PLM (Product Lifecycle Management)** — Systems and processes that manage product definition data — CAD, BOMs, revisions, compliance — from concept through design, manufacture, service, and retirement. PLM often owns the engineering BOM that ERP manufacturing consumes as a production BOM. See also: BOM, MES, MRP.

**Post-implementation review** — A structured assessment after go-live — often at 3, 6, and 12 months — that measures whether the ERP met its business case and identifies optimisation opportunities. It is where promised ROI is reconciled against actual results. See also: Go-live, ROI, KPI. Related: /learn/erp-post-implementation-review.

**Procure-to-pay (P2P)** — The end-to-end process from purchase requisition and supplier selection through receiving, invoice matching, and payment. ERP procurement, inventory, and AP modules automate P2P to cut maverick spend and cycle time. See also: Order-to-cash, Approval matrix, EDI.

ERP terms: R to Z

**RACI** — A responsibility-assignment matrix that maps each task to who is Responsible (does the work), Accountable (owns the outcome), Consulted, and Informed. RACI charts are widely used in ERP project governance, approval design, and change management — and increasingly to decide which agent actions may fire without a human in the loop. See also: Approval matrix, Workflow, Change management.

**ROI (Return on Investment)** — A measure of the financial benefit an ERP delivers relative to its cost. ERP ROI is typically realised through efficiency gains, better and faster decisions, and growth capacity, and it should be tracked explicitly in the post-implementation review rather than assumed at go-live. See also: TCO, KPI, Post-implementation review.

**Rollout** — The phased deployment of the ERP across sites, business units, regions, or modules after a successful pilot or initial go-live. A phased rollout reduces risk and lets each wave's lessons improve the next, versus a single high-stakes big-bang cutover. See also: Pilot, Go-live, Change management, Two-tier ERP.

**SaaS (Software as a Service)** — A cloud delivery model where the vendor hosts the software and you access it via subscription, with no infrastructure to manage and upgrades handled by the provider. Most modern cloud ERPs are delivered as SaaS. See also: Cloud ERP, IaaS, PaaS, Multi-tenant.

**Sandbox** — A non-production ERP environment used for configuration, development, training, and UAT so experiments never touch live financials. Healthy projects keep at least one sandbox (often more: dev, test, UAT) separate from production. See also: UAT, Pilot, Go-live.

**SCM (Supply Chain Management)** — The planning and coordination of the end-to-end flow of goods, from suppliers through production and warehousing to the end customer. SCM is frequently delivered as a module or integrated suite within an ERP. See also: WMS, EDI, MRP, ASN.

**Single-tenant** — A cloud architecture where each customer has its own dedicated application instance and infrastructure. Single-tenant offers stronger isolation and more customization freedom but typically costs more and makes vendor upgrades slower and harder. See also: Multi-tenant, SaaS, Cloud ERP.

**SKU (Stock Keeping Unit)** — A unique identifier for each distinct product or item a company stocks, enabling inventory tracking, valuation, and replenishment. SKUs are core master data created and maintained inside the ERP's inventory module. See also: Master data, BOM, WMS.

**SLA (Service Level Agreement)** — A formal contract defining the level of service a vendor or support team will provide — typically uptime guarantees plus response and resolution times. SLAs govern both SaaS ERP hosting and post-go-live support tiers; AI agent availability and credit exhaustion should be covered explicitly when copilots are in production paths. See also: Hypercare, SaaS, Copilot Credits.

**TCO (Total Cost of Ownership)** — The complete lifetime cost of an ERP: licence or subscription, implementation, customisation, integration, infrastructure, training, ongoing support and upgrades — and, in 2026, AI capacity such as Copilot Credits. TCO is the correct lens for comparing deployment models and vendors — never compare on list price alone. See also: ROI, Customization vs configuration, Cloud ERP. Guide: /learn/erp-total-cost-ownership.

**Two-tier ERP** — Running a corporate tier-1 ERP for group control alongside lighter tier-2 ERPs at subsidiaries or brands, integrated rather than forced into one template immediately. See the 2026 vocabulary section. See also: Hybrid ERP, Rollout, Integration.

**UAT (User Acceptance Testing)** — The phase where real end-users test the configured ERP against realistic business scenarios to confirm it meets requirements before go-live. UAT is the last functional gate before cutover and a key input to the go/no-go decision. See also: Go-live, Pilot, Sandbox, Change management.

**WMS (Warehouse Management System)** — Software that manages warehouse operations — receiving, putaway, picking, packing, shipping, and inventory accuracy, often with barcode or RF scanning. A WMS may be a module inside the ERP or a specialised system integrated with it. See also: SCM, SKU, ASN.

**Workflow** — A predefined sequence of steps and rules that automates a business process, such as an approval chain for a purchase order or an exception-routing rule. ERPs use workflow engines to enforce consistency, capture approvals, and cut manual handoffs; agentic features often invoke the same workflow and approval matrix rather than bypassing them. See also: Approval matrix, BPM, RACI, Agentic ERP.

On-premise, single-tenant, multi-tenant, hybrid, and two-tier compared

Many of the terms above collapse into one decision buyers face early: how the ERP is deployed and how many ERPs the group will run. The models sit on a spectrum from maximum customer control (on-premise) to maximum vendor-managed efficiency (multi-tenant SaaS), with hybrid blends and intentional two-tier designs in between. The right choice depends on your data-residency, customization, M&A pace, and upgrade preferences — not on which model is objectively 'best.'

Composable, dual-write, iPaaS, and monolith: which pattern is which?

Buyers often hear four architecture buzzwords in the same meeting. They are not synonyms. Use this comparison when a vendor slide says 'we are composable' or 'we do real-time sync' and you need a precise question ready.

How these ERP terms fit together

A glossary is most useful when you can see how the terms connect. Four axes organise almost everything above. The data axis runs from master data, MDM, and the golden record, through data migration and ETL, into the shared database that every module reads from. The deployment axis runs from on-premise through single- and multi-tenant cloud to hybrid and two-tier — it determines control, cost, and upgrade behaviour. The lifecycle axis runs from sandbox, pilot, and UAT through cutover, go-live, and hypercare into the post-implementation review where ROI is finally measured. The 2026 AI axis adds agentic execution and metered capacity (Copilot Credits) on top of the same workflows and approval matrices you already govern.

The functional terms sit on top of the shared database: manufacturing (MRP, MRP II, BOM, MES, PLM, APS), operations (WMS, SCM, SKU, ASN), commercial flows (O2C, P2P, CRM, CSU), finance (COGS, FIFO, LIFO, GAAP, IFRS, chart of accounts), and decision-making (BI, KPI). Integration terms — API, EDI, middleware, ETL, iPaaS, dual-write, Dataverse — stitch the ERP to the outside world or to sibling apps. Governance terms — workflow, approval matrix, RACI, SLA — keep the system controlled as people and agents scale. Configuration vs customization decides how much of this you build safely versus risk on upgrades.

If you remember one thing: ERP is defined by the integrated shared data model, and every other term in this glossary is a way of either populating that model (master data, migration), extending it (modules, integration, agents), deploying it (cloud, on-prem, two-tier, composable), running it (workflow, approvals), or measuring it (BI, KPI, ROI, TCO including AI credits). For the actionable deep dives behind any of these terms, follow the related guides linked below.

Frequently asked questions