ERP use cases — operational patterns that cut across industries
An ERP system is rarely chosen by industry alone. The way a business actually operates — running dozens of branches, billing by project milestone, swinging through a sharp seasonal peak, or recognising revenue from monthly subscriptions — shapes the requirement profile far more than the NACE code on the commercial register. We group these cross-industry operational patterns into use cases. A use case captures how the company earns, ships and bills, independent of whether the products are textiles, software licences or industrial spare parts. The four use cases collected here cover the patterns that DACH Mid-Market companies most often ask us about: branch networks, project business, seasonal business and subscription business.
What a use case means in the ERP context
A use case is an operational pattern that shows up across several industries and forces an ERP into a particular shape. A franchise bakery chain and a fashion retailer both run a branch-network use case, even though their product catalogues have nothing in common. A management consultancy and a structural-engineering firm both run a project-business use case. Selecting an ERP only by industry vertical — without checking which use cases also apply — tends to produce expensive surprises around month six of an implementation.
Industry view vs use-case view
The industry view answers the question «which vertical features and compliance points do I need?» — for example IFS lot tracking in food, IPC-A-610 in electronics, or BMECat in wholesale. The use-case view answers «which operational mechanics do I need?» — multi-entity stock visibility for branch networks, milestone billing for project business, revenue recognition for subscription business. A complete ERP shortlist tests both lenses. If your operation matches more than one use case (e.g. a project-driven engineering firm with seasonal swings around year-end projects), the ERP must handle both without forcing parallel processes.
The four use cases at a glance
- ERP for branch networks — multi-store retail and franchise operations, central price/SKU control, store autonomy, POS-to-ERP sync, inventory rebalancing across locations.
- ERP for project business — agencies, consultancies and engineering firms, milestone billing, time tracking, profitability-per-project reporting.
- ERP for seasonal business — textile, garden and Christmas businesses, planning peaks and troughs, buffer stock, temporary staffing integration, financial smoothing.
- ERP for subscription business — SaaS and recurring-revenue models, MRR/ARR tracking, deferred revenue, churn analytics, upgrade/downgrade flows.
Using use cases during ERP selection
In an ERP selection process, we recommend tagging every requirement either with the industry it comes from or with the use case it serves. That makes it easier to see at the demo stage which vendors really cover your operational reality — rather than only ticking the obvious industry checkboxes. For most DACH Mid-Market companies, two or three use cases apply at once. The right ERP is the one that handles all of them natively, not the one that scores best on a single dimension while forcing workarounds on the others.
Related Topics
- ERP for branch networks
- ERP for project business
- ERP for seasonal business
- ERP for subscription business
Frequently Asked Questions
How is a use case different from an industry?
An industry describes what you sell and which regulation applies (e.g. medical devices, food, machinery). A use case describes how you operate — project-by-project, branch-by-branch, subscription-by-subscription. Two companies in different industries can share a use case, and one company can match several use cases at once.
Can one ERP cover several use cases?
Yes, most established mid-market and upper-mid-market ERPs (Microsoft Dynamics 365 BC and F&O, SAP S/4HANA, NetSuite, abas) cover multiple use cases natively. Specialist tools (Vertec for project business, Chargebee for subscription) are stronger in their core use case but require integration with a primary ERP.
Which use case is most often underestimated in DACH SMBs?
Project business. Many manufacturers and service companies run a sizeable share of revenue through project-style engagements (engineering, custom-build, consulting) without ever modelling project profitability properly in their ERP. That gap shows up as «projects that look profitable but aren't» in the management report.