The Industry Selection Trap#
If you're leading an ERP selection project, you've probably heard vendors say "we serve your industry." It sounds reassuring—until you dig deeper.
The uncomfortable truth: "We serve manufacturing" can mean anything from "we have three manufacturing customers" to "we've spent 20 years building manufacturing-specific functionality." The difference matters enormously for your implementation timeline, cost, and risk.
A generic ERP forced into an industry vertical is a recipe for customisation hell. But an industry-specific ERP that's actually just a generic system with a few templates? That's worse—you'll pay a premium for functionality that doesn't exist.
What's at stake: Industry-specific requirements aren't nice-to-haves—they're the difference between an ERP that accelerates your business and one that becomes a permanent obstacle. Food manufacturers without allergen tracking face regulatory risk. Construction companies without retention management face cash flow crises. Retailers without omnichannel capability lose customers.
This article gives you a framework to cut through vendor claims and evaluate industry fit honestly—so you can distinguish real industry expertise from marketing positioning.
---
Industry Specificity Matters#
The Industry Requirements Framework#
1. Operational Model#
How does the organisation create value?
Manufacturing: Transform materials into products.
Distribution: Move products from suppliers to customers.
Services: Deliver expertise and labour.
Retail: Sell products to consumers.
Project-based: Deliver defined scopes of work.
2. Revenue Model#
How does the organisation generate revenue?
Product sales: One-time revenue from products.
Subscription: Recurring revenue for ongoing access.
Service delivery: Time-based or milestone-based revenue.
Usage-based: Revenue tied to consumption.
3. Cost Structure#
What drives costs in the organisation?
Materials: Raw materials and components.
Labour: People costs.
Capital: Equipment and facilities.
Distribution: Logistics and transportation.
4. Regulatory Environment#
What regulations affect operations?
Industry-specific: Industry regulations (food safety, pharmaceutical).
Financial: Financial reporting and controls.
Privacy: Data protection requirements.
Environmental: Environmental compliance.
Industry Profiles#
Manufacturing#
Core requirements: - Bill of materials management - Production planning (MRP) - Shop floor control - Quality management - Supply chain visibility
Differentiators: - Discrete vs process manufacturing - Make-to-stock vs make-to-order - Serial/lot tracking requirements - Engineering change management
Distribution/Wholesale#
Core requirements: - Inventory management - Warehouse management - Order management - Purchasing - Transportation management
Differentiators: - Multi-location inventory - Value-added services - Returns management - Vendor managed inventory
Professional Services#
Core requirements: - Project management - Time and expense tracking - Resource management - Billing (time and materials, fixed fee) - Project accounting
Differentiators: - Utilisation tracking - Skills management - Project profitability - Contract management
Retail#
Core requirements: - Point of sale integration - Inventory visibility - E-commerce integration - Customer management - Merchandise planning
Differentiators: - Omnichannel operations - Seasonal variability - Promotional pricing - Customer loyalty
Construction#
Core requirements: - Project accounting - Job costing - Progress billing - Retention management - Certified payroll
Differentiators: - Union requirements - Prevailing wage - Equipment management - Subcontractor management
Healthcare#
Core requirements: - Patient management - Billing (complex payer rules) - Compliance (HIPAA, etc.) - Supply chain - Human resources
Differentiators: - Electronic health record integration - Payer contract management - Regulatory reporting - Quality metrics
Evaluating Industry-Specific Claims#
Vendor Claims to Scrutinise#
"We serve your industry": How many implementations in your specific industry?
"Industry templates available": What do templates actually include?
"Industry best practices built-in": Whose best practices?
Due Diligence Questions#
- How many customers do you have in our industry?
- Can you provide references from similar organisations?
- What industry-specific functionality is included vs additional cost?
- How do you stay current with industry regulatory changes?
- What industry expertise does your implementation team have?
NZ/AU Industry Considerations#
Market Size#
The NZ/AU market is smaller than US/EU: - Fewer reference customers - Less vendor investment in local requirements - Smaller implementation partner pool
Local Requirements#
Regulatory: NZ/AU specific regulations.
Business practices: Local business conventions.
Integration: Local banking, government, and marketplace integrations.
Monday Morning Action Plan#
This week:
- Build Your Industry Requirements Matrix: List your top 10 industry-specific requirements. Score each vendor 1-5 on each requirement. "Industry expertise" claims disappear when you see the scores.
- Demand Industry References: Request 3 references from your exact industry. Ask: "What industry functionality did you expect that wasn't there?"
- Audit Your Current Industry Gaps: List every spreadsheet, workaround, and shadow system you use because your current system lacks industry functionality. These are your real requirements.
- Check Vendor R&D Investment: Ask vendors what % of R&D goes to your industry vs. their top industries. If you're <5%, you're a secondary priority.
- Verify Implementation Team Experience: The vendor may have industry expertise—but does your implementation team? Ask for team members' industry project history.
---
Conclusion: Industry Knowledge Is Essential#
Generic ERP knowledge is insufficient. Effective ERP selection requires deep understanding of industry-specific requirements and careful evaluation of vendor claims.