Home/ Home/ Features/ Custom ERP builds

Custom ERP builds, shaped by your requirements

When the packaged product covers most of what you need and the last stretch matters, we build the missing pieces on the same offline-first foundation. Your data stays on your PC, your licence is yours, and every core function keeps working without internet.

Positioning

Your requirements shape the ERP, not the other way around

Most UAE SMEs are well served by the packaged Zeyto product. Some are not - because their trade, their compliance quirks or their operations sit outside what any off-the-shelf ERP models cleanly. A Zeyto custom build takes the same production-hardened engine and layers your specific screens, documents, reports and integrations on top of it.

You do not rebuild sales, purchase, inventory, accounting, POS, VAT and printing from scratch - those are already there, tested against thousands of transactions a day. What we design and build is the part that is uniquely yours: the workshop job card that maps to how your technicians actually work, the weight-tolerance stock movement your steel yard needs, the ticket cycle your laundry group runs on, the report your owner wants the way your owner wants it. Everything you add inherits the offline-first behaviour of the base - it works on your PC, respects your licence, backs up with the rest of your data, and syncs across your branches through the same layer as the standard modules.

Decision guide

When a custom build is the right call

Consider a Zeyto custom build when one or more of these describe your situation. If none apply, the packaged product is almost certainly the faster, cheaper answer - we will tell you that plainly.

  • Your industry has a workflow no off-the-shelf ERP models cleanly - jewellery weight and purity, workshop job cards, laundry ticket cycles, weighbridge-based dispatch, project cost centres
  • You already run a legacy system with years of data and refuse to re-key it into a new product
  • Compliance or reporting formats specific to your business are not in any packaged product on the market
  • You have five or more custom document types that need their own numbering, printing and approval flow
  • Owner reports must combine data from operations software the packaged product does not touch - a weighing scale, a marketplace feed, a payment terminal
  • You need a screen designed around one specific counter operator or a specific back-office role, not a generic form
  • You want the base ERP plus one or two industry modules delivered as a single installable, licensed under one .zlic file
Scope of a custom project

What a Zeyto custom build includes

Every custom project is built on the same engine as the packaged product. You get the whole base and layer your specifics on top - not a stripped-down version.

package

Full base ERP

Sales, Purchase, Inventory, Accounting, POS, UAE VAT, Barcode and Document designers, mobile companion, backup, sync - the entire production product, not a subset

layout

Custom screens and modules

New forms, new documents, new workflows written to your written specification with your field labels, your validations and your approval chain

bar-chart

Custom reports

The reports your accountant, operations manager and owner actually ask for - not the generic ones every ERP ships with

printer

Custom prints

Invoices, quotations, job cards, delivery notes, gate passes and vouchers in your exact layout, bilingual English and Arabic where you need it

plug

Hardware and API integration

Bridges to your existing weighing scales, barcode printers, payment terminals, kitchen displays, RFID readers, marketplace feeds, courier APIs and bank statement imports

database

Data migration

Structured import from Tally, Zoho Books, QuickBooks, Vyapar, Sage, SQL Server, MySQL, Oracle or clean CSV / Excel - masters, opening balances, and optional history

Foundation

Same offline-first foundation as the packaged product

A custom project does not mean a fragile one-off. The base is production-hardened and offline-first, and everything you add inherits that behaviour by default.

One binary, one signed .zlic licence, one PostgreSQL database on your own PC or LAN. Every operational function - invoicing, POS, stock, VAT return, printing, backup - works with zero internet indefinitely. Zeyto Cloud stays optional and only holds licences, opt-in telemetry and encrypted backups. When we add a custom screen or a bespoke module, it lives inside that same binary. It reads and writes the same PostgreSQL. It is subject to the same licence checks. It is included in the same nightly encrypted backup. It replicates to other branches through the same sync layer used by sales invoices and stock transfers. There is no separate 'custom side' running on a different stack that can fail in a different way.

Runs offlineโœ“
On your hardwareโœ“
One licenceโœ“
Backed up togetherโœ“
Syncs across branchesโœ“
Arabic and RTLโœ“
Engagement model

How a custom build actually runs

Fixed-scope engagement with clear stages and named deliverables. No open-ended consulting hours and no surprise invoices.

1

Discovery workshop

A working session with you and the people who will actually use the software. We map the current workflow, the pain points and the gaps - not just what management thinks happens

2

Written scope

A specification listing every custom screen, report, print, integration and data migration task, each with acceptance criteria in plain English you and your team can sign off

3

Fixed quote and timeline

A single fixed price for the agreed scope, with a delivery timeline in weeks and a payment schedule tied to milestones, not calendar dates

4

Build in stages

Each module is delivered in reviewable stages. You see progress fortnightly against the spec, not a demo at the end when it is too late to change direction

5

User acceptance

You run the software against real data in a test copy of your database. We fix and iterate until it matches the spec, before it touches your live books

6

Go-live and handover

We install on your PC or LAN, migrate your data at the cut-off, train your team on-site and hand over written documentation for every custom module

7

Support and evolution

Ongoing support under a service agreement. New requirements go through the same scope-then-quote loop, so change requests are budgeted, not billed by the hour

Integration and migration

Migration and integration, planned into the scope

The move from your current system is the highest-risk part of any ERP change. We treat it as a first-class deliverable, not something to figure out after go-live.

download

Legacy database extract

Direct read from Tally XML, Zoho Books API, QuickBooks IIF and QBB, Vyapar exports, SQL Server, MySQL, Oracle, or clean CSV and Excel workbooks

columns

Master data mapping

Customers, suppliers, items, ledgers, warehouses, tax codes and units mapped column by column with your accountant, reviewed before any load runs

book

Opening balances at cut-off

Trial balance, party balances, item stock and batch or serial details brought forward on the agreed go-live date, reconciled against the legacy system

clock

Historical transactions

Optional import of prior years of invoices, receipts and stock movements when audit, VAT re-filing or owner reports require the full trail

cpu

Hardware integration

Barcode scanners, thermal 58 and 80 mm printers, kitchen display units, weighing scales, cash drawers, RFID and biometric readers wired into the workflow

cloud

External services

Payment gateway callbacks, marketplace order feeds, courier and shipping APIs, bank statement imports and FTA-portal-ready exports when your workflow needs them

Illustrative scenarios

Where a custom build has made sense

Hypothetical UAE examples showing when the packaged product would need to bend too far and a custom module is the cleaner answer. Yours may look different - the pattern is what matters.

Jewellery retailer

Per-piece weight and purity tracking, live gold-rate revaluation, exchange-with-old-gold billing and a hallmark register alongside standard tax invoicing

  • Retail

Auto workshop chain

Job card lifecycle from estimate to gate pass, parts issued against jobs, technician time capture and warranty tracking across multiple branches

  • Service

Steel and building materials trader

Weight-per-piece stock with tolerance bands, lorry-load planning, weighbridge integration and delivery-order printing at the yard gate

  • Trading

Laundry group

Ticket-per-garment tracking, batch cycles by wash type, ready-for-collection SMS and branch-to-plant transfers on the same offline core

  • Services

Contracting firm

Project-wise cost centres, material issues against jobs, subcontractor RA bills and retention accounting on top of the standard ledger

  • Contracting

Food and grocery distributor

Van-sales rounds with batch and expiry, printed cash-collection sheets, and route-wise stock reconciliation at end of day, all offline in the van

  • Distribution
Choose the right path

Packaged product versus custom build

Both sit on the same engine. The difference is where your budget goes and how far the software bends to your workflow.

AspectPackaged ZeytoCustom Zeyto build
Time to go-liveDaysWeeks to a few months
Cost modelPer-seat subscriptionFixed project fee plus ongoing support
Screens and workflowsStandard, well testedStandard base plus your specific modules
Reports and printsField-designer tweaksAny report or layout you specify
Data migrationSelf-serve importersManaged migration from any source
Hardware and APIsCommon devices includedAny device or service you need
Ongoing changesProduct updatesChange requests via scoped mini-projects
Offline-first foundationYesYes, inherited from the base
Data on your PCYesYes
UAE VAT and FTA returnIncludedIncluded, plus any custom compliance layer
Path to the other sideUpgrade to custom laterStandard modules already inside
What we do not do

A few things we hold to

No lock-in cloud
Your data lives on your PostgreSQL, on your hardware. You can back it up, dump it, migrate it away
No open-ended hours
Every deliverable is scoped and priced. Change requests are re-scoped, not billed as consulting time
No throwaway one-off
Custom modules ship as part of your Zeyto binary and are maintained under the same update stream
No pretending
If the packaged product already covers you, we recommend it and skip the custom project
FAQ

Straight answers

When should I choose a custom build over the packaged Zeyto product?
The packaged product fits most UAE SMEs on standard invoicing, POS, stock, accounting and VAT. Choose a custom build when your industry has workflows the standard forms cannot model cleanly, when you need modules that do not exist off the shelf (workshop job cards, weight-based stock, per-piece jewellery tracking, laundry ticket cycles), when compliance or reporting formats specific to your business need to print exactly as a regulator or auditor expects, or when you must integrate with hardware or services the packaged product does not currently support. If none of these apply, packaged is faster, cheaper and lower risk - and we will tell you so.
Do custom screens and modules still work offline?
Yes. Every custom module we build inherits the offline-first behaviour of the packaged base. It runs against the same local PostgreSQL database on your PC or LAN, respects the same signed .zlic licence, backs up with the same backup engine, and mirrors across sites through the same sync layer. If your team can use the standard sales and POS screens without internet, they can use your custom screens without internet too - a custom project does not put you back on a cloud dependency.
Can you migrate our data from Tally, Zoho, QuickBooks, Vyapar or Excel?
Yes. Data migration is scoped into the project from day one, not treated as an afterthought. We extract from Tally XML exports, Zoho Books API dumps, QuickBooks IIF or QBB files, Vyapar backups, SQL Server or MySQL databases, or clean CSV and Excel workbooks. We map masters column by column with your accountant, bring forward opening balances at the agreed cut-off date, reconcile the trial balance against the legacy system, and optionally import prior years of transactions when audit or reporting requires the full trail.
How is a custom project priced?
Fixed price against a written scope, not open-ended hourly consulting. After the discovery workshop we produce a specification listing every custom screen, report, print, integration and migration task, each with acceptance criteria in plain English. You get a single fixed quote and delivery timeline in weeks, with a payment schedule tied to milestones. Later change requests go through the same scope-then-quote loop - so there are no surprise invoices for 'while we were in there' work.
Who owns the custom code and the data?
Your data belongs to you and lives on your PC in your PostgreSQL database. Custom modules built for your project are licensed to your business under the same .zlic key as the base product, unlocked for your seats. Source ownership terms are agreed in writing before build starts; typical arrangements grant you full rights to use, host and back up the custom code for your business in perpetuity, while Zeyto retains the right to reuse generic patterns learnt on the project for other customers.
Can a packaged Zeyto customer move to a custom build later?
Yes, and this is the point of building both on the same engine. Custom modules sit inside the same binary and use the same database schema as the packaged product, so moving from packaged to custom is not a migration - it is an extension. Your existing data, users, licence, backups and sync configuration continue to work. We add the custom modules alongside the standard ones and re-issue the .zlic to unlock them. You never re-buy or re-implement what you already had.

Tell us what your current software cannot do

Send a short description of your business and the workflows the packaged product would need to bend for. If a scoping call makes sense, we set one up. If the packaged product already covers you, we say so plainly and point you at it.