Protect familiar working patterns
Staff were used to specific paper layouts and operational routines. The new system needed to feel recognisable enough for daily adoption from the start.
Workflow Automation System
Custom workflow software for a seafood trading company.
Scellus helped a fast-growing seafood business replace scattered manual processes with a central system for tracking orders, containers, documents, invoices, contacts, and daily tasks.
Malaysian seafood trading company · Malaysia · Ongoing
2xSales processing speedNearly doubled within 3 months of implementation.
100+Products managedFresh and frozen seafood products handled across daily operations.
3 moImpact windowThe operational improvement was visible within the first 3 months.
6People involvedScellus team members across workflow mapping, design, and development.
Project Snapshot
A custom workflow system for a seafood trading operation.
A Malaysian seafood trading company managing more than 100 fresh and frozen seafood products needed a better way to run daily operations. Scellus designed and built a custom workflow automation and tracking system around the client's existing operating process, centralising orders, container updates, documents, invoices, contact records, task follow-ups, and inventory-related workflows. Client name and selected interface details are withheld under NDA.
The Challenge
The company had grown beyond what paper workflows and manual coordination could support.
The team was managing a large seafood product portfolio across daily orders, customer and supplier records, container updates, documents, invoices, and internal task follow-ups.
Much of that work still depended on paper workflows, repeated data entry, manual checking, and informal updates between staff.
As volume increased, staff had to re-enter the same information across different stages. Updates became difficult to track once work moved between people, and management lacked a clear view of what was pending, completed, delayed, or at risk.
The client did not need a generic off-the-shelf system. They needed a workflow tool that matched how their business already worked, while removing the parts that slowed the team down.
- Orders, invoices, documents, and contacts were handled across separate manual processes.
- Container updates and operational follow-ups depended on scattered staff coordination.
- Repeated data entry created admin overhead and inconsistent records.
- Management needed clearer visibility into pending, completed, delayed, and at-risk work.
Operational Friction
The work was not just digitising forms. It was giving the operation more control.
Centralise operational context
Orders, contacts, documents, invoices, containers, and tasks all carried related information. The system needed to keep that context connected instead of splitting it across records.
Reduce repeated admin
Information entered once needed to be reusable across relevant workflows so the team could spend less time copying, checking, and reconciling data.
Improve management visibility
The business needed a clearer view of status, pending work, delayed items, handovers, and operational exceptions across daily activity.
What Scellus Built
A central workflow application built around the client's real operating process.
Scellus designed and developed a custom internal application for tracking orders, containers, contacts, invoices, documents, and operational tasks from one central system. The system supported familiar layouts, reusable data, responsive access, and workflow visibility across multiple operational stages.
Key Capabilities
The system connected the daily workflows that had been spread across paper, spreadsheets, and follow-up messages.
- 01
Order and workflow tracking
Order information was centralised so staff could track progress, status, and related details from one place instead of jumping between paper records, spreadsheets, message threads, and separate documents.
- 02
Container tracking
The team could monitor container-related updates and tasks through a structured workflow, reducing scattered manual follow-ups and making shipment progress, pending actions, and exceptions easier to see.
- 03
Contact and document management
Customer, supplier, and operational contact details were organised alongside related documents and communication records, making it easier to move from intake to invoice without losing context.
- 04
Digital invoicing and document sharing
The application generated unique URLs for selected documents, allowing external parties to view specific files without accessing the internal system.
- 05
Reusable workflow data
Information entered once could be reused across relevant parts of the system, reducing duplicate entry and the risk of inconsistent records across orders, invoices, documents, and task flows.
- 06
Localised interface support
The system supported multiple languages, number formats, currency display, and visual localisation based on user preference.
- 07
Responsive access
The platform was designed for desktop and tablet use, giving staff access from the office, warehouse, or other operational locations.
- 08
Custom operational layouts
Custom data layouts mirrored parts of the client's existing paper workflow while adding faster search, clearer status tracking, automated running numbers, and better visibility across records.
Our Approach
Map the real workflow first, then digitise the parts that slowed people down.
Scellus started by studying how the team handled orders, container tracking, document preparation, invoicing, contact records, and operational follow-ups.
Instead of forcing the business into a completely new workflow, we digitised the process around familiar working patterns.
A key design decision was to mirror parts of the client's existing paper layouts. This reduced the learning curve for staff and made the system feel recognisable from day one.
- 01
Workflow mapping
We traced how work moved through the company, where information was repeated, where handovers slowed down, and where visibility was missing.
- 02
Familiar interface structure
We preserved recognisable operational layouts so the system felt like a controlled upgrade to the team's existing process.
- 03
Reusable data model
We structured orders, contacts, documents, invoices, containers, and tasks so shared information could move through the workflow without constant re-entry.
- 04
Operational visibility
We added clearer status tracking, task visibility, document access, and management-level context across the daily workflow.
03 — System
Implementation
The application was implemented as a custom internal workflow system with a React frontend, Express and Node.js backend, PostgreSQL database, and Docker-based infrastructure.
Order, document, and invoice workflow
Container, task, and data visibility
The build focused on centralising the operational records staff used every day: orders, documents, invoices, contacts, containers, and task follow-ups.
Because the system was designed around existing business logic, selected interface details and sensitive workflow rules are not publicly shown under NDA.
Technologies
- React
- JavaScript
- Express.js
- Node.js
- PostgreSQL
- Docker
Results
Within 3 months, the client nearly doubled sales processing speed.
The system helped the team process more work without adding more operational complexity. The biggest result was not just speed. It was control.
- 01
Reduced repeated manual data entry
Reusable information lowered the amount of copying and re-checking required across orders, invoices, documents, and task flows.
- 02
Improved workflow visibility
Staff and management gained a clearer view across orders, documents, containers, invoices, contacts, and operational tasks.
- 03
Clearer status tracking
The team could see what was pending, completed, delayed, or at risk across daily operations.
- 04
Less dependency on paper
Familiar paper-based workflows were moved into a controlled digital system without forcing the team into a generic process.
- 05
More work without more complexity
The company could handle a higher volume of sales and operational activity with fewer manual handovers.
- 06
Better management control
Leaders gained a more reliable view of daily operations, accountability, and follow-up work.
Why This Worked
The system followed the client's actual operating rhythm.
Scellus did not start with a generic dashboard and force the business to adapt. We studied how work moved through the company, where information was repeated, where handovers slowed down, and where visibility was missing.
Then we built the application around those patterns.
The system kept what was familiar, removed what was repetitive, and added structure where the operation previously depended on manual checking.
A workflow system only succeeds when people actually use it. That balance mattered.
- Orders
- Containers
- Documents
- Invoices
- Contacts
- Tasks
- Reusable data
- Localisation
- Responsive access
The client could handle a higher volume of work with less guesswork, fewer manual handovers, and clearer accountability across the operation.
In their words
Scellus was very responsive to our needs and changing requirements. This was our first experience building a custom application, and the team helped us understand what was possible while keeping the system practical for our daily operations. With their support, ideas, and dedication, we were able to move from a manual process into a system that gave our team much better control.
Have an operation that is outgrowing spreadsheets, paper forms, and manual follow-ups?
Scellus designs, builds, and runs workflow systems that fit the way your business actually works.