Eight modules, one platform
STOS core runs the terminal. These eight modules run everything around it, on the same login, the same customer master and the same reporting layer, so the business stops being a set of disconnected systems.
Pick what the operation actually needs
Modules are licensed individually. Start with the one that hurts most and add the rest as you go.
| Module | What it runs | Who uses it |
|---|---|---|
| Logistics | Order to delivery tracking, gate movement, order timeline | Transport desk, customer service |
| Procurement | Requisition, RFQ, quotation comparison, PO, GRN, closure | Requesters, approvers, procurement, finance, warehouse |
| CRM | Visit plans, quotations ledger, monthly plan against actual, tickets | Sales, commercial, customer service |
| Warehouse | Locations, receipts and issues, stock ageing, cycle counts | Warehouse and bond staff |
| Maintenance | PM schedules, job cards, spares, downtime reporting | Workshop and engineering |
| Empty Yard | Empty in and out, survey and grading, repair estimates, depot billing | Depot operations |
| Accounts | Chart of account, tariff assigning, billing, AR and AP ageing | Finance |
| Help Desk | Ticketing, categories, assignment, escalation, SLA ageing | Support and IT |
Order to delivery, tracked end to end
Logistics turns a customer instruction into a tracked order and follows it to the door. Every order carries its own timeline, so when a customer calls you can answer from the record rather than from memory.
Inside the module
Requisition to purchase order to goods receipt
Procurement runs the full buying cycle with approvals at each gate. A requisition becomes an RFQ, quotations are compared side by side, a purchase order is approved, and goods are received against it, with a work queue showing each person only what is waiting on them.
Inside the module
Sales pipeline and customer service on terminal data
CRM sits on top of the customers you already handle containers for. Visit plans, quotations and tickets are measured against a monthly plan, so sales performance is reported from activity rather than from a spreadsheet kept on the side.
Inside the module
Bonded and general warehousing with real stock control
Warehouse gives stored cargo the same discipline the yard already has: a known location, a known quantity and a movement record for every change, so a stock figure can be defended.
Inside the module
Keep the equipment that moves the boxes available
A reach stacker out of service stalls the yard. Maintenance plans the work that prevents that, records the work that could not be prevented, and shows what downtime is actually costing.
Inside the module
A depot has different rules, so it gets its own module
Empty container depots do not work like a laden yard. Empty Yard handles movements against the shipping line, survey and grading on arrival, repair estimates, and storage billed per line.
Inside the module
Terminal billing that posts straight to the ledger
Accounts is where handling turns into money. Tariffs are assigned against the services a container actually consumed, billing runs from the same record operations worked in, and the position per party is live rather than reconstructed monthly.
Inside the module
One queue for every issue, internal or customer raised
Help Desk gives support requests the same traceability as a container movement: logged, categorised, owned, escalated if it ages, and closed with a record of what was done.
Inside the module
One login, one customer, one set of numbers
The modules are not separate products bolted together. A central identity service issues the session, an app switcher moves between modules without a second sign-in, and every module reads and writes the same customer, container and invoice records that STOS core uses.
Module questions, answered
No. They run on the same platform as STOS core, behind the same login, against the same customer and container master. An app switcher moves between them without signing in again.
Yes. Modules are licensed individually. Most operators start with the one that is hurting most, usually Procurement or Logistics, and add others as they go.
Yes. A customer, a container and an invoice mean the same thing in every module, so reporting is built over one data set rather than reconciled between systems.
A central identity service issues the session. Roles are granted per module, so a procurement officer and a terminal operator see different applications under the same sign-on.
Ready to secure and streamline your operations?
Join 30+ enterprise clients who trust Ciphertronix for fraud detection, cyber security and terminal operations. Tell us what you are trying to solve and we will show you the platform running on real data.