ERP Integration & Custom Solutions

An ERP does not fail because of the software. It fails earlier, at scoping.

ERP integration and custom software for Algerian companies

An ERP project rarely fails because of the software. It fails because the scope was vague, the provider was chosen on price and users were presented with a done deal. We scope before we integrate, and we say when the standard product is enough.

Try the demoDiscuss your project
  • A reasoned choice of tool, with no vendor bias
  • A written scope before the first line of configuration
  • Users involved from the start

Interactive demo

Follow an order, without an ERP and then with one

A customer order crosses five desks: sales, stock, preparation, invoicing, accounting. Send it through a company with separate tools, then through the same company running an ERP, and compare.

The company works

Five tools that do not talk to each other. At every hand-over, someone copies the order into their own.

Order C-2041Fictional example24 PX-200 pumps for Example Workshop

Path of the order

5 separate tools
  1. 01Order takenOrder form in WordTyped once
  2. 02Stock checkedWarehouse Excel fileWaiting
  3. 03Goods preparedPaper picking slipWaiting
  4. 04Invoice issuedInvoicing softwareWaiting
  5. 05Accounting entryAccounting softwareWaiting

One order, five desks

The salesperson has just typed the order. Send it and watch what happens at each hand-over.

In the tools, at the same moment

  • Stock of PX-200 pumpsBefore the order120
  • InvoiceNot issued yetWaiting
  • Accounting entryNot posted yetWaiting

Result for a single order

Without an ERPWith an ERPnot run yet
Manual entries1
Documents retyped0
Places where the figures can diverge0
Mismatches that appeared0

Simplified example: the order, the customer, the product and the figures are fictional. Your choices stay in your browser. In a real project, we describe your processes with your teams before any configuration.

What we see

Why ERP projects go off track

  1. A scope decided too fast

    Modules are bought before the processes have been described. The gaps appear along the way, and every gap becomes a contract amendment.

  2. An ERP that does not fit the business

    Teams work around the tool with Excel files. The ERP is paid for, but the real management happens elsewhere.

  3. Too much custom development

    Every request is coded. The ERP becomes impossible to update and depends on a single developer.

  4. Data migrated without checks

    Duplicate customers, wrong stock levels, accounts mapped incorrectly. The new tool starts with the old one's errors.

Our method

Our integration method

The choice between standard and custom is made on criteria, not on a preference.

  1. 1Process descriptionPurchasing, sales, inventory, production, accounting, HR: with your teams, we describe what is really done, and what should be done.
  2. 2A reasoned choice of solutionA standard ERP when it covers your business, targeted customisations when little is missing, custom development when your way of working is your advantage.
  3. 3Configuration, data migration and testingWe configure in batches, clean the data before migrating it and have each batch approved by the users concerned.
  4. 4Training, go-live and follow-upUsers are trained on their own cases. We stay on hand at go-live, then hand over the documentation and control.

Deliverables

What you receive

  • A written description of your target processes
  • A selection note: solutions compared, criteria, recommendation
  • A configured ERP, connected to your other tools
  • Data migrated and checked
  • Trained users and up-to-date documentation

Who it is for

This service is for you if

  • You still run most things on Excel and on software that does not talk to each other
  • You have an ERP that teams only half use
  • You are hesitating between several vendors and receive bids that are impossible to compare
  • Your business has specific features that no off-the-shelf software seems to cover
Discuss your project

Take stock

Standard ERP or custom solution?

Five questions for a first indication. Your answers stay in your browser.

Question 1 of 5

Do your processes resemble those of other companies in your sector?

Why Gnosis

What you get by working with us

Advice independent of vendors

We are not tied to any software vendor or hardware manufacturer. The recommendation starts from your need, not from a catalogue.

A written scope before any commitment

Scope, priorities, budget and schedule are set down in writing before the first day of implementation.

Local delivery, by a team in Algiers

A team based in Algiers that knows the country's regulatory, human and infrastructure constraints.

Straight talk on what is feasible

If a project does not have the means to succeed, we say so before it starts.

Frequently asked questions

What we are asked before we start

Which ERPs do you integrate?

Odoo, SAP and Dolibarr are the most common in our engagements, and we build custom software when none of them fits. We are not tied to any vendor: the recommendation depends on your business and your means.

How do you keep an ERP project from going over budget?

By writing the scope before signing. Most overruns come from needs discovered along the way. Serious scoping costs little compared with what it prevents.

Can you take over an ERP project that went badly?

Yes, it is a common request. We start with a diagnosis: what works, what is being worked around, what has to be redone. Sometimes the tool is sound and only the configuration needs revisiting.

Where is the ERP data hosted?

That choice is made at the scoping stage. For modules that hold personal data, such as payroll, human resources or the customer file, we favour hosting in Algeria.

Further reading

Our articles on the subject

Our other services

All services

An ERP your teams really use

Describe your business and what is holding you back today. We will tell you whether a standard tool is enough, before we talk about integration.

Discuss your project