feliXart

Solutions

The systems we build.

We do not sell a package. We build systems shaped around how the company works, whose source code belongs to you and which run on your own servers. Below are the system types we build and what each one covers.

System types8 / 167
01

ERP — Enterprise Resource Planning

The core system where finance, stock, purchasing, sales and production meet one data model.

36 functions
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
  • +2
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
  • +2
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
  • +2
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
  • +3
Production
  • Bill of materials and routing definitions
  • Work orders, material reservation and consumption
  • Operation tracking, scrap and rework
  • Capacity planning and work-centre loading
  • +2
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
  • +1
02

CRM — Customer Relationship Management

Customers, opportunities, quotes and service requests tracked in one place.

25 functions
Customers and contacts
  • Company and contact records, one entity with the ERP ledger
  • Contacts, titles, authority and communication preferences
  • Segment, source, representative and territory assignment
  • Credit limit and balance visibility
  • +1
Sales process
  • Opportunities, stage definitions and win probability
  • Pipeline view and stage transition rules
  • Quote preparation, versioning and approval flow
  • Quote-to-order conversion and loss reason analysis
  • +2
Activity and communication
  • Meeting, visit, call and email logging
  • Calendar, reminders and task assignment
  • Email templates and send history
  • SMS and notification integration
  • +1
Service and support
  • Request logging, category and priority
  • Assignment, routing and escalation rules
  • Resolution targets and breach alerts
  • Warranty and contract coverage checks
  • +1
Analysis
  • Funnel conversion rates and time in stage
  • Sales by representative, territory and product
  • Distribution of loss reasons
  • Customer lifetime value and repeat purchase
03

B2B Dealer and Ordering Portal

Where dealers see their own balance, their own pricing and live stock, and place orders themselves.

18 functions
Dealers and permissions
  • Dealer accounts, sub-users and permission levels
  • Dealer group, territory and representative assignment
  • Credit limits, with orders blocked on breach
  • Contract, document and authorisation tracking
Catalogue and pricing
  • Catalogue by brand, model, category and technical attributes
  • Price lists by dealer group and turnover
  • Tiered discounts, campaigns and quantity breaks
  • Live stock, allocated quantity and estimated lead time
  • +2
Orders and dispatch
  • Basket, reorder and saved order templates
  • Order approval flow and partial dispatch
  • Dispatch status and carrier tracking numbers
  • Returns and warranty claims
Accounts and documents
  • Statements, balance, overdue and upcoming payments
  • Invoice and delivery note viewing with PDF download
  • Payment notification and card collection
  • Reconciliation letters
04

WMS — Warehouse and Stock Management

Warehouse operations running on racks, locations, batches and handheld terminals.

16 functions
Warehouse structure
  • Warehouse, aisle, rack, bin and location hierarchy
  • Location types: picking, reserve, quarantine, returns
  • Capacity, volume and weight constraints
  • Addressing and barcode label generation
Operations
  • Goods-in, quality control and quarantine
  • Put-away rules and suggested locations
  • Pick lists, wave picking and route optimisation
  • Packing, dispatch preparation and load checking
  • +1
Traceability
  • Batch, lot, serial number and expiry date
  • FIFO / FEFO issue rules
  • Movement history and a full audit trail
  • Recall queries
Counting and control
  • Periodic, cycle and spot counts
  • Variance analysis and approval flow
  • Per-operator throughput
05

Production Tracking and MES

Work orders, operations, scrap and real production cost captured on the shop floor.

17 functions
Definition and planning
  • Bills of materials, semi-finished goods and alternative recipes
  • Routings, operations and work-centre definitions
  • Capacity planning and work-centre loading
  • Work order creation, prioritisation and scheduling
Shop floor
  • Machine terminal: start, pause and finish a work order
  • Production records by operator, shift and staff
  • Material reservation and consumption reporting
  • Scrap, waste and rework records
  • +1
Quality
  • In-process quality checkpoints
  • Sample, measurement and tolerance records
  • Non-conformance records and quarantine
  • Traceability: which raw material went into which product
Cost and analysis
  • Standard versus actual cost variance
  • Material, labour and overhead allocation per work order
  • OEE: availability, performance, quality
  • Downtime analysis and scrap trends
06

Field Service Management

Field teams running their jobs, location, paperwork and expenses from a mobile app.

19 functions
Work orders and planning
  • Request logging, category and priority
  • Technician assignment matched on skill and territory
  • Route and appointment planning, daily schedules
  • Resolution targets and breach alerts
  • +1
Mobile app
  • Task list, detail and customer history
  • Digital service forms and checklists
  • Photos, signatures and barcode scanning
  • Location-verified check-in and check-out
  • +2
Parts and cost
  • Van stock and spare part consumption
  • Warranty coverage checks and chargeability
  • Expenses, advances and fuel records
  • Post-service invoicing
Tracking and reporting
  • Live team and job status board
  • Technician performance and first-time fix rate
  • Fault history by equipment
  • Customer satisfaction capture
07

Integration and Middleware

A structure where separate systems talk through one connection layer.

18 functions
Connection layer
  • Single entry point, service contracts and versioning
  • Retry, timeout and circuit-breaker behaviour
  • Queueing and deferred processing
  • Full request/response logging and error tracking
  • +1
Enterprise systems
  • Logo, Netsis, Mikro, SAP and bespoke ERP connections
  • Journal entry export to accounting packages
  • Single sign-on via Active Directory / LDAP
  • Database-level reads from legacy systems
Statutory and financial
  • E-invoice, e-archive, e-waybill and e-ledger providers
  • Bank statement import and bulk payment files
  • Payment gateways, providers and instalment rules
  • Exchange rate services
Operational services
  • Courier and carrier services
  • SMS, email and push notification providers
  • Mapping, address and routing services
  • Marketplaces and e-commerce platforms
  • +1
08

Document Processing and Automation

The layer where invoices, forms and paperwork become structured records.

18 functions
Document reading
  • Invoices, delivery notes, order forms and contracts
  • Field extraction from identity and official documents
  • Image pre-processing: perspective correction, deskew, denoise
  • Validation rules and checksum verification
  • +1
Flow and approval
  • Document queue, assignment and priority
  • Multi-level approval hierarchy
  • Three-way match: order, delivery note and invoice
  • Discrepancy alerts and exception handling
Archive and access
  • Full-text search and field-level filtering
  • Version history and change log
  • Permission-based access and share links
  • Statutory retention periods and automatic disposal
AI layer
  • Natural-language queries over your documents
  • Draft records generated from free-text email
  • Document classification and automatic routing
  • Summarisation and missing-document detection
  • +1
One system, many faces01

These are not separate products. In most programmes two or three of them meet on one data model: the ERP account is the CRM customer, warehouse movement costs feed production costing, the dealer portal reads the same stock. That is why we build them in one schema rather than integrating separately bought systems.

Technical foundation02

The part that does not change, whichever system we build. A company buying custom software is also buying what it will inherit, so we set the ground out upfront.

Architecture

One data model, one connection layer, row-level permissions and an audit trail on every record.

  • One data model; modules open on top of the schema
  • Every outward link gathered into a single connection layer
  • Role and permission matrix with row-level access control
  • Audit trail on every record: who changed what, and when
  • Shared business logic in one place; desktop, web and mobile read the same source
Technology

TypeScript and Next.js, Flutter and Swift, PostgreSQL and Python; Docker on your own servers.

  • Web and server: TypeScript, Next.js / React, Node.js
  • Mobile: Flutter (iOS, Android) and native Swift
  • Desktop: Windows and macOS from one codebase
  • Data: PostgreSQL, Firebase / Firestore
  • Vision and data services: Python, FastAPI, OpenCV
  • Deployment: Docker, on your own servers or in the cloud
Security and data

The system can run on your own servers; data never leaves the building.

  • The system can run on your own servers; data never leaves the building
  • Row-level security and unit-level data separation
  • Server-side sessions; secrets never reach the client
  • Separation of personal data and retention-period rules
  • Backups, restore rehearsals and a disaster scenario
  • Encrypted transfer and encrypted backups
Delivery and ownership

Source code is yours at every phase acceptance, with no per-user licensing.

  • Source code is delivered at every phase acceptance and belongs to you
  • No per-user licensing
  • User and technical documentation are part of delivery
  • Acceptance criteria are written into the contract
  • Defect warranty from acceptance
  • The team taking over is trained while development runs
How we build03

We do not quote a fixed price for undefined scope. On larger programmes we start with a paid technical assessment and fix scope and budget after it.


Which system carries your business?

Tell us where you are — and we will say so plainly if you do not need one.