Logistics Document Recognition
PilotCommercial invoice, packing list, bill of lading and customs declaration parsing
Input: scanned or photographed documents. Output: structured fields with confidence scores.
API / Private deployment
AI Logistics Cloud is our industry AI platform, built on the scenarios we handle every day: forwarding, customs documentation, yard and warehouse operations, and electronics distribution. Customers access domain-specific models, GPU cloud compute, fine-tuning and training services, hosted AI agents, token governance and multimodal token metering through one platform.
Our AI work started inside our own operation, where the problems are concrete: incomplete enquiries, re-keyed documents, disputed cargo condition, and safety supervision that depends on who happens to be walking the yard. Solving those problems produced models, agents and governance rules that other companies in the same industry face as well.
The platform makes that capability available to industry customers. It is built for logistics, forwarding, trading and warehousing scenarios, with domain terminology, document formats and operating rules already reflected in the models, and with the ability to adapt further to a specific customer's data.
Five-Layer Architecture
Open API, customer console, token metering and billing, private or hybrid deployment options for customers with data residency requirements.
Agent orchestration, visual recognition, document parsing, forecasting and scheduling, exposed as reusable building blocks.
Training, fine-tuning and inference capacity scheduled by job priority, with elastic scaling for online services and private compute options where data cannot leave customer premises.
General foundation models combined with industry-specific models trained and fine-tuned on logistics, customs and warehouse scenarios.
Industry corpora, document samples, handling imagery and operational records, governed with access control and retention rules.
Each model is delivered through API or private deployment, with maturity stated honestly. Evaluation results are reported per scenario against an agreed evaluation set.
Commercial invoice, packing list, bill of lading and customs declaration parsing
Input: scanned or photographed documents. Output: structured fields with confidence scores.
API / Private deployment
Classification review and declaration element checking before submission
Input: product description and specifications. Output: candidate HS codes with reasoning and required elements.
API
Lane-level rate trend and equipment availability outlook for booking decisions
Input: lane, period, cargo profile. Output: indicative range and confidence level.
API / Console
Container and pallet condition, seal verification, stacking and lashing anomalies
Input: yard or handling point imagery. Output: condition labels, anomaly flags and time-stamped records.
Private deployment
Enquiry handling and status replies in English, Bahasa Melayu and Chinese
Input: customer message and shipment context. Output: drafted reply for officer review.
API / Agent Cloud
PPE compliance, forklift and pedestrian conflicts, restricted zone intrusion
Input: fixed camera streams. Output: event records with imagery for officer confirmation.
Private deployment
Three services that turn industry models into something a customer can actually run: models adapted to their data, agents that execute defined tasks, and a metering layer that keeps usage and cost under control. GPU cloud compute and multimodal token metering are documented on their own pages.
For customers whose terminology, document formats or operating rules differ from generic models, we provide an end-to-end fine-tuning service: from data assessment to evaluation, deployment and ongoing iteration.
Standard Delivery Flow
Review sample volume, quality and coverage, then define what additional data is worth collecting before any training starts.
Written labelling rules for documents, cargo conditions or safety events, so results stay consistent across annotators and batches.
Supervised fine-tuning and parameter-efficient adaptation on industry corpora, with version control for every training run.
A held-out evaluation set agreed with the customer, with metrics reported per scenario rather than a single averaged score.
Customer SOPs, tariff rules and service scopes connected as a retrieval knowledge base so answers stay grounded in approved material.
Production feedback and corrected cases flow back into the next training cycle, with rollback available at version level.
A hosted environment where industry customers compose, run and govern task-oriented agents. Agents call your systems through defined interfaces, and every action is logged with a human takeover path.
Captures cargo details, checks completeness, retrieves tariffs and prepares a structured quotation draft for the desk.
Parses incoming documents, maps fields into your workflow and flags inconsistencies before submission.
Consolidates milestone events and answers status questions in the customer language, escalating exceptions to an officer.
Handles first-line enquiries across channels with knowledge base grounding and defined escalation rules.
Reviews visual detection events, groups repeated findings and prepares a corrective action record for review.
Turns operational data into periodic reviews of transit performance, cost structure and exception patterns.
A single gateway and metering layer across models, so industry customers can control spend, attribute usage to the right project and keep an auditable record of every call.
One API surface across multiple models, with routing rules per scenario and fallback when a provider is unavailable.
Token budgets assigned by project, department or end customer, with hard limits and soft warnings.
Usage and cost dashboards with threshold alerts, so overruns are noticed during the month rather than at billing.
Repeated prompts and stable reference material served from cache, and lighter models routed to simpler tasks to reduce cost.
Call-level records with request context, model version and outcome, retained for a defined period and exportable for reconciliation.
Throttling and priority queues to protect production workloads during peak usage.
Two platform services are documented on their own pages, with capacity tiers, counting rules and governance controls described in enough detail to plan a workflow against them.
Elastic inference nodes, fine-tuning queues, multi-accelerator training capacity and batch throughput pools, with priority scheduling, checkpointing, utilisation reporting and private compute deployment.
View GPU Cloud ServiceText, image, video and voice usage measured on their own terms, converted into one comparable unit, with cross-modal task tracing, per-modality quotas and modality-level audit logs.
View Multimodal Token ServiceEach scenario below pairs a common operational difficulty with the model and agent combination we would propose, and the direction of benefit we would measure during a pilot.
Typical Difficulty
Enquiry volume spread across email, phone and messaging, with quotation turnaround limiting how many lanes can be served.
Proposed Combination
Document Recognition + Quotation Agent + Token Cloud
Direction of Benefit
Faster first response and consistent quotation structure across branches.
Typical Difficulty
Safety supervision depends on patrol coverage, and condition disputes are hard to evidence after the fact.
Proposed Combination
Cargo Visual Condition + Safety Behaviour Recognition + Safety Inspection Agent
Direction of Benefit
Documented condition records and earlier detection of unsafe practice.
Typical Difficulty
High SKU counts with frequent catalogue and compliance changes across destination markets.
Proposed Combination
HS Code Assistant + Multilingual Service Model + Tracking Agent
Direction of Benefit
Fewer classification corrections and clearer customer status answers.
Typical Difficulty
Oversized and staged deliveries involve many parties, so handover responsibility is often unclear.
Proposed Combination
Document Recognition + Tracking Agent + Supply Chain Analysis Agent
Direction of Benefit
One custody record per leg and periodic review of exception patterns.
Typical Difficulty
Inbound and outbound checks are manual, and stock accuracy depends on cycle counting discipline.
Proposed Combination
Cargo Visual Condition + Safety Behaviour Recognition + Token Cloud
Direction of Benefit
Visual stocktaking support and monitored handling practice.
Send us a sample of your documents, a description of the workflow or a site layout. We will review it and propose a bounded pilot with success criteria agreed in advance.
Discuss a pilotCustomer data is separated per tenant, and access is granted only to the roles that need it for a defined task.
Imagery, documents and call logs are kept for an agreed period, with access limited to authorised staff and signage displayed at monitored areas.
Handling of personal data follows Malaysian personal data protection requirements, and cross-border transfer arrangements are confirmed before deployment.
Model results support decisions rather than replace them. Declarations, quotations and safety findings are confirmed by a responsible officer.
Evaluation results are reported per scenario with the evaluation set disclosed. We do not claim absolute accuracy for any model.
Where data cannot leave customer premises, models and agents can run in a private or hybrid arrangement.
Near Term
Mid Term
Longer Term
Sandbox access to selected models so your team can test against real samples.
One bounded workflow, with success criteria agreed before the pilot starts.
Your data and terminology incorporated, with evaluation results reported per scenario.
Ongoing access to models, agents and token governance under an agreed service level.
Tell us the workflow you want to improve and the data you can provide. We will propose a bounded pilot, the models and agents involved, and the evaluation criteria we would report against.
Contact Our Team