Skip to content
STOS Add-on Modules

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.

WarehouseMaintenanceLogisticsProcurementAccountsEmpty YardCRMHelp Desk
At a Glance

Pick what the operation actually needs

Modules are licensed individually. Start with the one that hurts most and add the rest as you go.

STOS add-on modules at a glance
ModuleWhat it runsWho uses it
LogisticsOrder to delivery tracking, gate movement, order timelineTransport desk, customer service
ProcurementRequisition, RFQ, quotation comparison, PO, GRN, closureRequesters, approvers, procurement, finance, warehouse
CRMVisit plans, quotations ledger, monthly plan against actual, ticketsSales, commercial, customer service
WarehouseLocations, receipts and issues, stock ageing, cycle countsWarehouse and bond staff
MaintenancePM schedules, job cards, spares, downtime reportingWorkshop and engineering
Empty YardEmpty in and out, survey and grading, repair estimates, depot billingDepot operations
AccountsChart of account, tariff assigning, billing, AR and AP ageingFinance
Help DeskTicketing, categories, assignment, escalation, SLA ageingSupport and IT
Logistics

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.

DraftActiveIn-TransitOverdueDeliveredPickup PendingDestination Pending

Inside the module

Orders raised against a reference type and reference number, tied back to the terminal record
A status board counting draft, active, in-transit, overdue and delivered orders at a glance
Pickup pending and destination pending queues, so nothing waits unnoticed at either end
Gate movement recorded against the order, not in a separate log
Per-order history and timeline for every status change
Logistics Insights for trend and exception reporting
Procurement

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.

RequisitionRFQQuotationComparisonPOService POGRNClosure

Inside the module

Requisition raising, action and departmental approval
RFQ creation and RFQ status tracking across vendors
Quotation capture and side-by-side quotation comparison
Purchase order creation and approval, including service purchase orders
GRN creation and status, closing the loop against the order
Work queue and closure, with roles for requester, department approver, procurement officer, finance and warehouse
CRM

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.

DashboardMy workCustomersCommercialReportsSetup

Inside the module

Management dashboard filtered by month, employee and customer
Customers contacted and approached, meetings held and visits completed
Quotations generated with commercial value tracked against vendor value
Plans against actual: visits against plan, contact rate, activities done and pending
Customer service tickets by category, with ageing on each open ticket
Customers onboarded, reported alongside the quotations that won them
Warehouse

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.

LocationsReceiptsIssuesStock ageingCycle counts

Inside the module

Location and bin mapping across bonded and general areas
Goods receipt and issue posted against the owning party
Stock ageing, so long-dwell cargo is visible before it becomes a dispute
Cycle counts and adjustments with a reason recorded against each
Bonded carrier movements tracked in and out
Storage charges feeding the same billing run as the terminal
Maintenance

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.

PM schedulesJob cardsSparesDowntime

Inside the module

Preventive maintenance schedules per equipment, by hours or by date
Breakdown job cards raised from the yard and tracked to completion
Spare-part consumption booked against the job and the machine
Equipment downtime reporting, by unit and by cause
Service history retained for the life of each asset
Cost per machine, so replace-or-repair is an informed decision
Empty Yard

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.

Empty in / outSurveyGradingRepair estimateStock by line

Inside the module

Empty in and out recorded against the owning shipping line
Survey and grading on receipt, with condition captured
Repair estimates raised and approved before work starts
Stock reported by line, size and type
Depot storage billing per line and per agreement
Release against line instruction, checked at the gate
Accounts

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.

Chart of accountTariff assigningTerminal billingAR / AP ageingParty balance

Inside the module

Chart of account maintained in the system, not alongside it
Tariff assigning per party, service and container type
Terminal billing generated from the movements already recorded
AR and AP ageing reported without a separate extract
Party balance visible to operations as well as finance
Settlements and adjustments recorded against the party and the container
Help Desk

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.

TicketsCategoriesAssignmentEscalationSLA ageing

Inside the module

Ticket logging from internal teams and from customers
Categories that match how the operation is actually organised
Assignment and ownership, so nothing sits unallocated
Escalation rules when a ticket ages past its threshold
SLA and ageing visibility across the open queue
Resolution history retained per customer and per category
How they fit together

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.

Single sign-on across every module
One customer master, no duplicate accounts
Roles granted per module, per person
Reporting built over one data set
FAQ

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.