One company.
One engine.
Many products.
ikainepal builds fully customised ERP systems on n360, our own ERP engine — and runs the servers, networks and security underneath them.
Three things, under one contract
Most companies buy their software from one vendor and their infrastructure from another, then spend the year deciding whose problem it is. We do both.
Business systems
ERP, CRM, inventory, production, project costing, HR and payroll, retail counters, restaurant floors and online storefronts. Built from scratch on n360, or integrated with the systems you already run.
- Fully customised on the n360 engine
- Retail counters, restaurant floors, storefronts
- Integrates with what you already run
IT & infrastructure
Server management, networking, security, backup and disaster recovery, cloud migration, annual maintenance and helpdesk — for the systems we build and for the ones you already have.
- Servers, networking and security
- Backup, disaster recovery, cloud migration
- Annual maintenance contract and helpdesk
ERP consulting
Requirement study, process design, chart-of-accounts and costing design, data migration and staff training — by the team that builds the engine, not by a reseller reading a manual.
- Requirement study and process design
- Chart-of-accounts and costing design
- Data migration and staff training
Everything we ship is built on n360
n360 is our own ERP engine: one double-entry posting engine over one database. Finance, inventory, sales, purchasing, production, CRM, HR and payroll, and project costing all write through it — and so do the purpose-built front ends for a counter, a kitchen, a storefront and an employee.
Because we own the engine, a customisation is a build on proven foundations rather than a workaround bolted onto a black box. Nothing is synchronised between systems at night, because nothing was ever separate.
ERP modules, taken only if you run them
purpose-built vertical applications
database — nothing syncs at night
costing methods, per item
Six steps, every engagement
The order matters. Nothing is built before the scope is written down, and nothing goes live before it is ready.
- 01
Study your business
Your floor, your prices, your people, your documents. We map how the work actually happens before proposing anything.
- 02
Shape the solution
Agree exactly what the product will do for you — module by module, document by document — on paper, before a line is built.
- 03
Develop
Build your customisations on the proven n360 engine, in agreed increments you can see and correct.
- 04
Implement
Data migration and staff training on your calendar — opening stock and opening balances loaded as posted documents, not typed twice.
- 05
Go live
Only when it is ready. Cutover timed to a fiscal boundary where that suits your books.
- 06
Improve & support
Post-go-live support and improvement as the business runs and the requirements move.
Judged on costing, traceability and audit
Our team has delivered SAP work in manufacturing, FMCG, government and textile — the kind of environment where an ERP is measured by whether the cost of a batch is right, not by how the dashboard looks.
- Manufacturing
- FMCG
- Government organisations
- Textile
- Steel
- Construction & project firms
- Distribution & trading
- Retail chains
- Restaurants
Sarbottam Steels — centralised system
A centralised system bringing operations, stock and financial data onto one set of books, so plant-level activity and the ledger describe the same day.
Latest thinking
A restaurant that posts real books from order one
Kitchen tickets, recipe back-flush and Z reports — how a Kathmandu restaurant went live on n360.
Why one posting engine beats five apps
POS, storefront and warehouse writing to one double-entry ledger — and what that saves you at month-end.
Go-live checklists that actually protect you
Opening balances, master data, dry runs — the six things we verify before the switch flips.
Ready to talk?
Tell us how your business runs. We study it first — then shape the solution together. Write to hello@ikainepal.com.