feliXart

Solution

ERP — Enterprise Resource Planning

The core system where every resource in the company is managed on a single data model.

36 functions6 module groups7 integrations

An ERP is a data-model decision, not a list of modules. Unless you define upfront how an order draws down stock, at what cost it hits the ledger and when it becomes revenue, every module added later reopens the same question. In our setup definitions, transactions and accounting entries live in one schema and the modules open on top of it. The system runs on your servers, the source code is yours, and you do not pay per user.

Scope and modules36
01

Master data

  • Account cards: customer, supplier, employee, bank
  • Stock items, variants, unit sets and barcodes
  • Chart of accounts, cost centres and project codes
  • Price lists, discount and payment-term rules
  • Users, roles, permission matrix and approval hierarchy
  • Multi-company and multi-branch structure with intercompany movement
02

Sales and purchasing

  • Quotation, revision and approval flow
  • Orders, dispatch planning and partial delivery
  • Delivery notes, invoicing and batch invoicing
  • Purchase requests, quote collection and comparison
  • Supplier order tracking and lead-time alerts
  • Returns, discounts and price adjustments
03

Stock and warehouse

  • Multiple warehouses, racks and locations
  • Receipt, issue, transfer and stocktake documents
  • Batch, lot and serial number tracking
  • Minimum levels, critical thresholds and automatic requests
  • Costing method: average, FIFO, moving average
  • Consignment and third-party stock
04

Finance and accounting

  • Ledgers, statements, ageing and reconciliation
  • Cash, bank, cheque and note portfolio
  • Collection and payment plans with due-date tracking
  • Automatic journal entries against the chart of accounts
  • Expense management, advances and staff spending
  • Budget, variance against actuals and cash flow
  • Multi-currency, FX differences and revaluation
05

Production

  • Bill of materials and routing definitions
  • Work orders, material reservation and consumption
  • Operation tracking, scrap and rework
  • Capacity planning and work-centre loading
  • Production costing and standard-versus-actual variance
  • Quality checkpoints and quarantine stock
06

Reporting and management

  • Role-based dashboards and indicators
  • Profitability by product, customer, project and branch
  • Parametric report designer with spreadsheet export
  • Audit trail: who changed which record, and when
  • Scheduled reports and email notifications
What it connects to07
  • Licensed provider for statutory e-invoicing and e-ledger filing
  • Bank statement import and payment file generation
  • Payment gateways and virtual POS
  • Courier and carrier services
  • Your existing ERP or accounting package (two-way bridge during transition)
  • Barcode scanners, scales, label printers and handheld terminals
  • Single sign-on via Active Directory / LDAP
Signs you need this system06
  • 01The same data is keyed into two systems
  • 02Month-end close is finished in a spreadsheet
  • 03Per-user licensing penalises you for growing
  • 04Getting the report you want means calling an outside developer
  • 05You follow a process the package forces on you, not one that suits your work
  • 06You have no direct database access, or the contract forbids it
Decisions to make upfront04
01Does accounting stay inside the system or outside?
Either works. Producing statutory accounting inside gives independence but enlarges scope; posting entries to your existing package starts faster but keeps the dependency. We decide with you, after seeing how your accountant actually works.
02How many companies, branches and currencies?
Multi-company changes the data model from the start, and retrofitting it is one of the most expensive changes there is. If a split is plausible later, we build the model multi-company while the interface behaves as one.
03What migrates from the existing data?
Account and stock cards almost always migrate. Historical transactions are a separate line item; for most companies the right answer is a read-only archive of the past plus opening balances in the new system.
04Who uses which screen?
Warehouse and production want handhelds or tablets, finance wants a desktop screen open all day, management wants reports on a phone. That distribution decides which layers get built, and most of the cost.
Frequently asked05
Why custom instead of an off-the-shelf ERP?
If your processes fit a standard package, off-the-shelf is cheaper and we will say so. The maths changes when you are constantly paying for customisation, finishing the job in spreadsheets, and losing negotiating power at renewal. The technical assessment puts the multi-year cost of both routes side by side.
How long does it take?
It depends on scope. Taking one module live is measured in weeks, transferring every process in months. Because the system goes live in waves, the first benefit arrives in the early months rather than at the end.
Will operations stop while we leave our current ERP?
No. In each wave old and new run in parallel, outputs are compared, and the switch is decided together once the gap closes. We do not do irreversible cutovers.
Who owns the code and the data?
The source code transfers to you once payment obligations are met, and is delivered at every phase acceptance. The system runs on your servers with full database access.
Do we pay more as user numbers grow?
No. Development is priced against scope, and there is no per-user licence. Growth only shows up in your own server capacity.

Let’s scope it together.

We do not quote a fixed price for undefined scope. We review your existing system and processes on site, then deliver the roadmap and a fixed-price proposal.