Where depot control breaks down
When gate records, surveys, estimates, approvals, locations and invoices live in different files, every exception needs manual follow-up. Delays accumulate while revenue, customer service and yard capacity become harder to control.
One operating record from arrival to invoice
The right depot system connects the container, MLO, vehicle, condition, location, approval, service and charge so teams do not rebuild the same record at every stage.
Record references, vehicle, driver, seal, condition, date and instruction while enforcing release rules.
Capture condition, damage, images and remarks on a mobile-ready workflow and pass exceptions forward.
Control stack location, reservation, estimate, MLO approval, repair activity, material use and completion.
Generate gate documents, notify stakeholders and calculate authorised storage, handling, repair and service charges.
Complete inland depot workflow
OCTO Ops brings together the operational controls that determine turnaround time, yard capacity, repair recovery, billing accuracy and customer confidence.
Capture MLO and port references, vehicles, drivers, seals, condition and supporting documents while generating gate passes.
Use mobile-ready inspections, damage codes, images and remarks to create a traceable survey record.
Use repair masters and MLO-specific rates, send estimates for approval and retain every revision and decision.
Track stack location, transfer, hold, reservation, repair, ready and release states across multiple yards.
Manage jobs, labour, repair items, workshop inventory, issues, transfers, completion and quality checks.
Calculate storage, handling, washing, repairs and other services from trusted operational records and customer rules.
Operational control by design
Flatorb maps the actual depot flow, user roles, customer rules and exception points, then configures the screens, approvals, notifications and reports around how the yard operates.
Prevent unauthorised gate activity and make the reason for every block visible to the right team.
Apply customer-specific repair rates, approval paths, EDI formats, free days, tariffs and report requirements.
Surface overdue surveys, pending estimates, repair approvals, holds, aging units and unbilled activity.
Support transfers, shared master data, role-based access and consolidated or yard-level reporting.
Record who, what, where, when and why so operational, customer and billing questions can be answered with evidence.
Designed for the gate, yard, workshop and officePractical tools for every work point
The same platform can support fast operational capture in the yard and deeper review, control and reporting in the office.
EDI, API & business-system integration
OCTO Ops can operate as the depot’s primary platform or exchange verified movements, statuses, approvals and billing data with existing systems.
From movement records to operational control
The goal is not more reports. It is a dependable operating record that helps teams act earlier and gives management confidence in every movement, status and charge.
| Operational question | What OCTO Ops controls | Business outcome |
|---|---|---|
| Can this unit move? | Instruction and release validationBooking, hold, approval, document and gate rules | Safer gate operationsFewer unauthorised or incorrectly documented movements |
| Where is it now? | Location and status historyYard, stack, slot, transfer and current state | Faster retrievalLess searching and more dependable planning |
| What work is waiting? | Survey, estimate and repair queuesPending action, owner, age, approval and priority | Shorter dwell timeTeams act on bottlenecks before they become delays |
| What is consuming capacity? | Aging and yard-position visibilityCustomer, status, dwell, reservation and stack mix | Better yard useOperational decisions based on current yard reality |
| What should be billed? | Tariff and event-based chargingStorage, handling, washing, repair and other services | Revenue protectionFewer missed charges and clearer invoice support |
| What happened? | Protected audit trailUsers, timestamps, evidence, approvals and revisions | Customer confidenceResolve operational and billing questions with evidence |
Implementation approach
A successful rollout connects software configuration with master data, customer rules, integrations, user roles and real gate-to-invoice testing.
Container yard software questions
The right scope depends on yard volumes, customers, service mix, approval rules, billing model and systems already in place.
Ask about your depot ↗The platform is designed for inland container depots and yards handling empty or laden units, multiple MLOs or customers, surveys, repair estimation, workshop activity, storage, handling and related services. The configuration can vary by depot and operating model.
Yes. Customer-specific masters, repair rates, tariffs, approval paths, documents and data formats can be managed within one controlled platform. Access and reporting can be configured by company, depot, role or customer requirement.
Yes. OCTO Ops can generate and receive suitable EDI messages or other customer-specific data formats. During discovery we confirm the required events, message structures, transmission method, validation and exception handling.
Survey findings can flow into estimates using standard repair items and MLO-specific pricing. Estimates, images and supporting information can be shared for approval, with revisions, decisions and authorised work retained in the container history.
Yes. Operational charges can be calculated from controlled events and tariff rules, then reviewed, exported or exchanged with accounting, ERP or invoicing systems through an agreed integration approach.
Yes. You can maintain a separate price sheet for each MLO while using the same standard repair codes. When an estimate is prepared, OCTO Ops identifies the container’s MLO and automatically applies the correct MLO-specific pricing.
Yes. OCTO Ops can calculate storage from recorded container movements, tariff rules and the applicable number of free days. It can also apply handling charges such as mounting, demounting, washing and other services, creating a clear operational basis for billing.
For most mid-sized container yard operations, we typically configure the system within two weeks and have the operation up and running within one month. Timing can vary with data readiness, MLO requirements, integrations and workflow complexity, so we confirm the rollout plan during discovery and test complete gate-to-invoice scenarios before go-live.
The container yard management system is offered at one fixed annual price for unlimited usage by one legal entity. The price is not based on the number of modules, users, transactions, yards, depots or locations, and the annual cost is typically less than the salary of one employee. A one-time implementation charge may apply for initial data migration, configuration and training.
Begin with the bottleneck
Show us your gate-to-invoice flow, customer requirements and current exceptions. We’ll help define the practical system, integration and rollout path.
Discuss your container yard ↗