Systems and integrations developer
Alex Henrique da Silva
I do systems integration and process automation inside manufacturing ERP.
I have been at Adapcon since 2021, in southern Brazil, developing on Consistem ERP (InterSystems IRIS / ObjectScript). The work almost always starts the same way: there is a process that only happens because someone remembers to do it, and it needs to start happening on its own, with a deadline it has to meet and a record of who did what. To get there I connect the ERP to whatever the company runs around it: B2B marketplaces, e-commerce, store tills, WhatsApp, tax robots, cloud services. The case studies below are anonymised. I talk about industry, scale and architecture, with no client names and no source code.
By the numbers
511
signed routines and classes
39
repositories
28
clients and products served
5
years of experience
Recent highlights
- A multi-step workflow engine built from scratch and shipped to production in 2026.
- Retroactive IBS/CBS tax recalculation on already-issued invoices, ready within the deadline of the Brazilian tax reform.
- One of my features shipped in the core ERP product and now runs on every new implementation.
Selected case studies
Eight areas of work, all running in production.
B2B e-procurement engine for pharmaceutical distribution
A multi-marketplace quoting engine integrated with Bionexo and Sintese, plus catalogue and order synchronisation to the field sales platform over REST and WebSocket.
REST integration with a retail POS and Brazilian tax reform rollout
A two-way bridge between the ERP and the Varejo Online POS platform, with a custom rate limiter, log-driven incremental sync and retroactive IBS/CBS tax recalculation.
Hybrid tax and finance RPA with Microsoft Power Automate
Automation of tax obligations and banking routines combining business rules inside the ERP with orchestration in Power Automate and Azure Logic Apps, with end-to-end observability.
WhatsApp-based sales CRM with RFV segmentation
Backend for a sales CRM app with a 360º account view, RFV segmentation, visit logging through a WhatsApp bot with audio transcription and automated NPS surveys.
Multi-step workflow engine built from scratch
A generic workflow engine inside the ERP: step definition, rule-driven progression, side effects on completion and an SLA job that flags overdue work.
Onboarding console shipped in the core ERP product
A core-product ERP feature for bulk-importing master data during client onboarding, with a tax authority lookup later extracted into a reusable component.
E-commerce, marketplaces and live commerce
Digital sales integrations on top of the ERP: Tray, Bling, a marketplace hub, drop-shipping with an external franchise, live commerce and a two-way textile PLM bridge.
WMS with regulated batch traceability
Warehouse management for pharmaceutical distribution: batch traceability, picking labels, pending-stock reconciliation and cascading release of commercial and credit holds.
Experience
Adapcon
May 2021 – presentJaraguá do Sul, BrazilMid-level software developer
Feb 2022 – present- Sole author of a generic workflow engine inside the ERP, running in production since 2026.
- Retroactive IBS/CBS tax recalculation on already-issued invoices, delivered within the deadline of the Brazilian tax reform.
- One of my features shipped in the core ERP product and now runs on every new implementation.
- ERP integrations with B2B marketplaces, e-commerce, store POS, WhatsApp and tax RPA across 28 clients and products.
Junior programmer
Jul 2021 – Feb 2022Trainee programmer
Jun 2021 – Jul 2021Intern
May 2021 – Jun 2021
Technologies and integrations
Platform
Cloud and automation
Messaging and support
Digital commerce
B2B and healthcare
Tax and compliance
Productivity and HR
How I work
Business rules stay in the ERP
Robots and integration scripts execute. The ERP decides. The moment a rule leaks into external automation it stops being auditable and starts breaking every time the vendor touches a screen.
I treat silent failure as a bug
Every integration I ship comes with logging, alerting and a panel where you can see which step the process stalled at. The worst version of a problem is the one the client finds before I do.
When the request is a symptom
If a ticket is the third variation of the same problem, I stop and build the generic mechanism instead. That is what happened with the workflow engine and with the marketplace adapter layer: rather than one more bespoke screen, a mechanism that handles the next cases through configuration.
Reuse the validation that already exists
Bulk imports and integrations write through the same routines the official screens use. Writing straight to the database saves you an afternoon and charges you later, when the rule changes in only one of the two places.
Contact
I am currently employed, but I am always up for a no-strings conversation about systems integration and process automation. WhatsApp gets the fastest reply.