Mobisec
Product · Manufacturing & export ERP

The ERP built inside a coir factory, not a boardroom.

23 modules covering the whole operation: supplier intake, gate and weighbridge, production and QC, warehouse, HR and export. Running in production at a global coco peat exporter since 2022, and now available to other manufacturers who need the same thing.

Why it fits

Generic ERPs make you describe your factory in their vocabulary.

Most packaged systems were built for discrete manufacturing or distribution, then bent to fit. You end up describing husk intake as a “raw material receipt”, grading as a “quality inspection lot”, and a lorry on the weighbridge as nothing at all.

This one was written against a real coir operation, with the people doing the work. The gate, the weighbridge, the shift, the QC rejection, the supplier advance. They are first-class parts of the system because they were first-class problems in the factory it was built in.

What's in it

23 modules, one system.

Not a suite of products stitched together, but a single platform on one data model, so a weighbridge ticket, a QC rejection and a stock position are the same record seen from different angles.

Sales & customers

From first enquiry through quotation and confirmed order, with the product catalogue and buyer records behind it.

  • Customers
  • Products
  • Quotes
  • Marketing

Procurement & suppliers

Supplier records and purchase orders, so raw material commitments are visible before the lorry arrives rather than after.

  • Suppliers
  • Purchase Orders

Gate, weighbridge & vehicles

Every movement in and out of the yard captured at the point it happens: check-in, weight, fuel and vehicle location.

  • Gate
  • Weighbridge
  • Factory Vehicles
  • Vehicle Tracking
  • Fuel

Production & quality

Job specifications, shift-level output, machine records, and QC with an approval and rejection workflow.

  • Job Specs
  • Daily Production
  • Machines
  • Quality Control

Warehouse & inventory

Stock positions across raw material, work in progress and finished goods, with a controlled item catalogue.

  • Warehouse
  • Inventory Catalog

People

Workforce records and attendance pulled directly off the biometric devices on your wall.

  • HR
  • Attendance

Administration & control

Who can open which screen, who can take which action, and a full record of what everyone did.

  • Users
  • Roles
  • Screen access
  • Activity log
The system

What it actually looks like.

Gate operations screen listing vehicles and visitors currently on site
Gate: who is on site right now, with the load recorded against the delivery it belongs to.
Weighbridge screen showing first weight, second weight and net weight per ticket
Weighbridge: first and second weights, net load, and the operator who recorded each ticket.
Daily production screen grouping job specifications by production status
Daily production: every job specification grouped by whether it is running, queued or complete.
Product catalogue listing coco peat and coir products
Products: your catalogue in your own vocabulary: blocks, bricks, grow bags, husk chips and fibre.
Employee register listing staff with designation and department
Workforce: the staff register behind attendance, shifts and payroll inputs.
Module access screen for granting screens to job roles
Screen access: decide what each job role can open, before deciding what they can do.
Talks to your hardware

The part most ERP projects underestimate.

Data has to be captured where it is created: on the scale, at the gate, on the device on the wall. Every integration below is running in production today, not on a roadmap.

Biometric attendance devices

Attendance is pulled directly from ZKTeco terminals over your network. No exports, no manual entry, no month-end reconciliation against paper.

GPS vehicle tracking

Live vehicle positions and trip history through a Protrack365 integration, tied back to the same factory vehicle records used for fuel and gate movements.

Weighbridge capture

Gross, tare and net weights recorded against the gate movement and the supplier delivery they belong to, so a load is traceable from the scale onward.

Document storage

Photos and supporting documents captured in the field are stored against the record they belong to, in object storage inside your own cloud account.

Access control

Your costing is not visible to the yard.

Two independent layers, because “can they open it” and “can they do it” are different questions.

Screens
Screen access decides what a role can even see. A weighbridge operator opens the weighbridge; they never see costing or buyer pricing.
Actions
Permissions decide what they can do once there. Viewing a QC report, creating one, and approving one are three separate rights.
Accountability
Every denied attempt and privileged action is written to an activity log you can read yourself.
What you own

Buying software should not mean depending on us forever.

The fair question every buyer asks about a smaller vendor is: what happens to us if you disappear? Here is our answer, in writing, before you ask.

It runs in your cloud account

Your environment is provisioned under your own AWS or Azure account. You own the infrastructure, the billing relationship and the data residency. We operate it for you, and we don't hold it hostage.

Your licence is perpetual

Your right to use the system is perpetual and irrevocable. Support and maintenance is a separate, renewable subscription. If you ever stop paying for support, your factory keeps running. You simply stop receiving updates and our help.

Your data is yours, and exportable

All of it, in common documented formats, at any time, and not a proprietary blob you'd need us to read. If you ever leave, you leave with everything.

You are never one person deep

Every client is assigned a named primary contact and a named backup, both familiar with your system. If your primary is unavailable, your backup takes over. You don't chase anyone and you don't re-explain.

2 hoursProduction-down response
07:00–22:00, 7 daysProduction-down cover
99.5% monthlyUptime commitment
Daily, retained 30 daysBackups
Implementation

Seven to eight weeks, in four stages.

Around seven to eight weeks from start to go-live for a standard implementation. Customisations specific to your operation are scoped and quoted separately, and add to that timeline.

2–3 weeks

Deployment & configuration

Your environment is provisioned in your own cloud account, the system is configured to your operation, and your users and roles are set up.

2 weeks

Data preparation

Suppliers, products, customers, machines and opening stock positions are loaded and reconciled against your existing records.

1 week

Training

Role-by-role training for the people who will actually use it: gate, weighbridge, production, QC, stores and office. Not a single classroom session.

2 weeks

Parallel run & go-live

You run the new system alongside your existing process until the numbers agree, then cut over. Nothing is switched off before you are confident.

Priced on the modules you actually take.

Most exporters do not need all 23 modules on day one. We scope to the parts of your operation you want running first, and price from there, so the entry cost reflects your operation rather than a fixed package.

Implementation
From LKR 1.5M

One-off. Covers deployment into your cloud account, configuration, data preparation, training and the parallel run through to go-live.

Support & maintenance
From LKR 100,000 / month

Ongoing. Covers the response times and uptime commitment above, your named contact and backup, updates and fixes. Renewable, and your licence to use the system is perpetual regardless.

Customisations specific to your operation are scoped and quoted separately. We talk through your requirements before quoting. The figures above are starting points, not a price list.

Confidentiality

We work with more than one exporter. Here's how we keep that safe.

Coco peat and coir is a small industry. Any software partner with real depth in it will have worked with someone you compete with. We would rather say that plainly than have you find out later.

Confidentiality by default

We sign an NDA before discovery, not after. Everyone at Mobisec who touches a client system is bound by confidentiality terms in their own agreement with us.

Separate systems, not shared ones

Each client runs in their own hosting environment, provisioned under their own cloud account. Your data never sits in a shared instance alongside another client's, and it stays under your ownership and billing, not ours.

Nothing is published without your approval

We would like to write about the work. But no case study, metric, screenshot or client name goes public until you have read it and approved it in writing.

Your processes are yours

Your costing model, supplier terms, grading parameters and buyer relationships are your competitive advantage, not reusable material. We build to your process; we don't carry it to the next client.

Next step

See it running against real factory data.

The most useful first conversation is a walkthrough of the modules that matter to your operation, so we can scope what you actually need before talking numbers.

Arrange a demonstration