13 / Custom ERP Software Development

Custom ERP Software Development | Artenis Alija

Operations software for businesses that have outgrown spreadsheets but not into SAP.

Wireframe of a custom record system: filtered list on the left, full record with history on the right. Layouts are illustrative — every build is shaped around your own data.

There is a gap between a spreadsheet and an enterprise ERP where a lot of real businesses operate. I build operations platforms for that gap: orders, inventory, reservations, warehouse work, purchasing and accounting orchestration as one system, integrated with the tools you already run rather than replacing all of them at once.

Use Cases

Order to invoice orchestration

One recorded, retryable pipeline from checkout through availability, reservation, warehouse task and invoice.

Availability that is computed

Physical, reserved and sellable stock tracked separately and derived from movements, ending the overselling that estimates produce.

On-premises accounting integration

An outbound-only connector that reaches the finance system without exposing it, keeping that boundary intact.

Replacing the spreadsheet layer

The reconciliation spreadsheets that sit between systems become recorded, monitored integrations.

Common Questions

Is a custom ERP realistic for a mid-sized business?

It is realistic when scoped as modules rather than as a programme. Start with the one process that is genuinely costing money — usually order-to-invoice or availability — get it working, then extend. A full ERP replacement attempted in one step is how these projects fail.

Do we have to replace our accounting system?

No, and you generally should not. The accounting system stays and the operations platform integrates with it through a dedicated connector, which keeps the finance boundary intact.

What happens when an integration fails overnight?

It retries, and if it still fails it lands in a queue with the error attached and an alert raised. Silent failure is the most expensive property of hand-rolled integrations, so these are built to fail loudly and recover.

What you get

→Operations process mapping and module scoping
→Order, inventory and reservation modules
→Warehouse task queues and movement audit trail
→Accounting system integration through an isolated connector
→Webshop and sales channel synchronisation
→Durable background job orchestration with retries
→Integration monitoring and operations dashboard

Start a project

Related services

systems-integration Data Pipelines Dashboard Development

How a project runs

The same sequence every time. It is deliberately front-loaded: most of the risk in an automation project sits in understanding the process, not in building it.

Map the process before writing anything

The first session is spent on how the work actually happens, which is almost never how the documented process says it happens. Who touches what, in which order, and where the time really goes. Most failed automation projects failed here rather than in the build, because they automated the described process instead of the real one.

Measure the cost of doing nothing

Hours per week, error rate, and what those hours would otherwise be worth. This is what decides whether a process is worth automating at all — and it is also the number you compare against afterwards, which is why it gets recorded before anything is built rather than estimated after.

Build the smallest useful version

One process, working end to end, in production, before anything else starts. A narrow system that people actually use beats a broad one that waits on a second phase, and the edge cases that matter only surface once real work runs through it.

Run it against reality

The first two weeks of live use produce more design corrections than any amount of planning. Failures get surfaced loudly, retried and logged, because silent failure is the most expensive property a workflow can have and the one noticed last.

Hand it over properly

Documentation, credentials, and a walkthrough with whoever will maintain it. A system only one person understands is a liability regardless of how well it runs, so handover is part of the work rather than an optional extra at the end.

Ways to work together

Three arrangements cover almost every engagement. Most start with the first or the second; the third only makes sense once something is live.

Fixed-scope project

One defined process, a fixed price and an agreed definition of done. The right fit when the problem is clear and bounded — an order flow to connect, a CRM to build, a reporting pack to automate. Most first engagements are this, because it lets both sides find out how the other works without a long commitment.

Assessment first

One to two weeks mapping processes and measuring where the hours actually go, ending in a ranked list with effort and payback estimates. Useful when there is a backlog of automation ideas and no agreement on which matters. The document stands on its own and is yours whether or not you build anything with me.

Ongoing retainer

A recurring block of time for maintenance, extension and new automations once systems are live. Integrations break when the systems either side of them change, and a retainer means that gets fixed before it becomes an outage rather than after.

How the working relationship is set up

Remote, with real overlap

Work is delivered remotely. Across Europe and the Nordics the working day is effectively identical; in the Gulf it starts three hours ahead, which still leaves your full morning covered. There is no local office in any market, and none is claimed anywhere on this site.

You own what gets built

Source code, infrastructure and data stay yours. Systems are deployed on infrastructure you control — your server, a European provider, or a VPS in your own account. There is no per-seat licence and no dependency on me continuing to be involved.

Self-hosting is a first-class option

Self-hosted n8n, self-hosted databases and locally run models are all supported and, in several of these markets, preferred. Where no data may reach a third-party API, that constraint shapes the architecture from the start rather than being retrofitted.

Direct contact, one person

You deal with the person building the system. There is no account manager relaying requirements, which is the main practical advantage an independent consultant has over an agency at this size — and the main reason scope stays honest.

Questions worth asking before you commit

What if we are not sure automation is the right answer?

Then the assessment is the right starting point, and it is designed to be able to conclude that you should not automate something. A process that is broken should be fixed before it is automated, and one that runs twice a month rarely earns the build. Receiving that answer in week one is far cheaper than discovering it after a project.

We have been burned by a failed automation project before.

That is common, and the cause is usually scoping or adoption rather than technology — a system built for the documented process rather than the real one, or one nobody was trained to maintain. Both are addressed by mapping the real process first and treating handover as part of the work.

How do we avoid depending on one person?

By owning everything: source code, infrastructure, credentials and documentation, with a walkthrough for whoever maintains it. The test is whether another developer could pick the system up from the repository and the documentation alone, and that is the standard handover is written to.

Is our data safe?

It stays where you need it to. Systems can run entirely inside your own infrastructure, including self-hosted models where no data may reach a third-party API. Where GDPR applies, data stays in the EU by default, with named access control and audit logging as standard rather than as an upgrade.

How quickly can something be running?

A first working version of a single process is typically weeks rather than months. Larger platforms are sequenced as modules so something is in production early and the rest builds on a foundation that already survives real use.

Sectors this is built for

AI Automation for Retail and E-commerce AI Automation for Logistics and Warehousing

Get in touch

Tell me what needs automating

Describe the process that is costing you time and roughly how much. I reply to every enquiry personally, usually within one working day.

Email: inquiries@artenisalija.com
Response: Usually within one working day, Mon–Fri CET
Delivery: Remote across Europe, the Nordics and the Gulf