01
Workflow & module mapping
Define departments, approval steps, record ownership and the modules that belong in your first delivery.
ERP & business systems
One connected operation.
A clearer working day.
ERP, invoicing and inventory workflows that connect the moving parts of your business — with agreed rules, roles and responsibilities.
ROOTED IN SRI LANKA. BUILT AROUND YOU.03 / ERP & business systems
THE RIGHT STARTING POINT
Understand the work.
Define the right solution.
A business system should reflect how work moves between people. We map purchasing, stock, sales and approvals before proposing the modules and connections your team needs.
- Shared business records
- Defined approvals & roles
- Connected stock and orders
FROM REQUIREMENTS TO HANDOVER
A scope you can review.
A path you can follow.
These are areas we can discuss. Your quotation defines which deliverables are included in your project.
02
Invoicing & inventory
Scope quotations, invoices, stock receipts, issues, adjustments and the points where records change.
03
Permissions & reports
Agree who can view, create and approve records, along with the reports needed for daily work.
04
Migration & rollout planning
Assess opening data, trial imports, testing, team guidance and cutover responsibilities.
INTERACTIVE EXAMPLE / FICTIONAL DATA
Try the ERP walkthrough
Approve a purchase, receive stock, dispatch a sale and record simulated payments in a connected sample company.
Start the guided demo01 / FOLLOW A WORKFLOW02 / SEE THE RECORDS CHANGE03 / EXPLORE THE RESULT
A working sample to explore possibilities. Production features and delivery are agreed separately.
POSSIBLE STARTING POINTS
Start with your working day.
Illustrative situations to help you describe what you need.
Purchase to stock
Follow an order from approval to receiving goods and recording a supplier balance.
Sales to delivery
Connect a customer order to stock availability, dispatch and payment tracking.
Invoice to inventory
Define when a confirmed invoice changes stock and how returns or adjustments should be handled.
A CONSIDERED DELIVERY PROCESS
Clarity at every stage.
- 01
Discover
Understand users, workflows, constraints and priorities.
- 02
Define
Agree deliverables, price, responsibilities and acceptance checks.
- 03
Develop & review
Build or configure the agreed solution and review the scoped work.
- 04
Handover & support
Agree documentation, access, team guidance and ongoing arrangements.
What shapes the quotation?
Modules, user counts, migration, accounting requirements, tax rules and integrations are confirmed during discovery. Software licences, hardware, hosting and ongoing operation are separate unless included.
Gokly is preparing its services for launch. Availability, suitability and terms are confirmed before work begins.
Prepare a relevant enquiryBEFORE WE BEGIN
A few useful answers.
Have a different question? Share a brief outline of your requirements.
Let’s discuss itDo we need every module at once?
No. We can discuss a focused first scope and later stages. Dependencies, acceptance criteria and any future requirements are recorded so the first delivery has clear boundaries.
Can stock and invoicing work together?
Yes, as an agreed workflow. We first define when stock changes, how cancellations and returns work, and who can make adjustments.
Is this an accounting package?
Accounting, tax calculations and formal financial reporting require a separate defined scope. The public demos illustrate operations and simulated balances; they are not production accounting systems.
LET’S MAKE IT HAPPEN
Your next step.
A clearer conversation.
Tell us what you want to achieve with erp & business systems. We’ll discuss suitability, scope and a practical way forward.