I build ERP modules and business automation systems tailored to specific industries, focusing on inventory management, pricing logic, purchasing workflows, and operational coordination.
Experience
I’ve designed ERP systems for automotive parts distribution (PartFly), parapharmacy operations (Parazone), and multi-location retail management. The consistent pattern is that generic ERP systems fail at the domain-specific logic.
For automotive parts, the challenge isn’t storing inventory—it’s cross-referencing parts across manufacturers, handling VIN-based lookups, and managing the importer-distributor-mechanic relationship. For parapharmacies, it’s expiration batch tracking, prescription validation, and regulatory reporting.
What usually matters is not the feature set, but how well the system encodes the actual business rules that determine who can do what, when.
Vertical-Specific Logic
Generic ERP systems rarely fit specialized industries well. I design systems that reflect actual business processes in sectors like parapharmacies, automotive parts, and hospitality.
The constraint: you can’t build “configurable” systems that work for everyone. Configuration becomes its own complexity layer. It’s more maintainable to build purpose-specific logic than to maintain a configuration engine that tries to be universal.
Inventory Management
Inventory systems must handle product categorization, stock levels, expiration tracking (for health and food products), and multi-location coordination. I build inventory modules that reflect real operational complexity.
In practice, the main issue is data quality. Products arrive with inconsistent naming, incomplete specifications, and supplier-specific identifiers. The system needs to handle this messiness, not assume clean data. Product matching and deduplication are harder than storage.
Pricing & Purchasing
Dynamic pricing, supplier management, purchase order workflows, and cost tracking require systems that connect purchasing decisions to inventory levels and sales data.
The trade-off: real-time pricing versus stable operational workflows. If pricing updates too frequently, it creates reconciliation problems. If it updates too slowly, margins suffer. You need versioning and audit trails, which adds complexity.
Multi-Actor Systems
Some industries involve multiple actors (importers, distributors, retailers, service providers). I design systems that coordinate these relationships while respecting each party’s operational independence.
What doesn’t work: trying to enforce centralized control in a naturally distributed system. An importer can’t dictate retailer workflows. A distributor can’t force mechanics to use specific pricing. The system needs to coordinate without controlling.
Integration Patterns
ERP systems need to integrate with POS, payment providers, accounting software, and external APIs. I design integration patterns that are maintainable and handle real-world data inconsistencies.
The main constraint is not the API itself—it’s handling schema changes, downtime, and data inconsistencies across systems that were never designed to talk to each other. Integration is ongoing reconciliation, not one-time setup.