Jakarta to Singapore: Cross-Border Connectivity and Warehouse Systems
AP Intermodal Pte Ltd needed its Indonesian and Singaporean operations to run as one business. We built the server connectivity across the corridor, then the warehouse and inventory management systems that run on top of it.
- Stack
- Network InfrastructureCross-BorderWarehouse ManagementInventoryIndonesiaSingapore
- Published
- March 2026

Project overview
AP Intermodal Pte Ltd runs freight and warehousing across the Indonesia–Singapore corridor, with operations on both sides of the strait and a Singapore holding entity. On paper it was one company. In practice it was two: Jakarta ran on one set of systems, Singapore on another, and the two only met in spreadsheets emailed between offices.
Zantosy was brought in to close that gap on both layers at once — the network that carries the data, and the warehouse systems that produce it.
The challenge
Cross-border operations fail quietly. Stock counted in a Jakarta warehouse would reach the Singapore office hours later, already stale. A customs query needed someone in the other country to look something up and reply. Nobody could answer "what do we actually have, right now, in both countries" without a phone call.
The underlying problem was not the warehouse software. It was that the two sites had no reliable, low-latency path between them, so every system built on top inherited the delay.
Cross-border server connectivity
We built the link layer first, because nothing above it works without it.
Private connectivity between the Jakarta and Singapore sites, sized for continuous replication rather than occasional file transfer.
A documented failover path, so a single carrier or circuit problem degrades performance instead of stopping operations.
Monitoring and alerting on the link itself, so the operations team learns about a problem from a notification rather than from a stalled shipment.
Server placement on both sides of the corridor, so each site reads and writes locally and the corridor carries replication traffic rather than every user request.
Warehouse and inventory management
With the corridor in place, both warehouses could run against shared state rather than their own copies.
Inventory management across both countries, with one stock record per item rather than one per site.
Goods-in, putaway, picking and dispatch flows shaped around how the warehouse teams already worked, rather than a generic template they would route around.
Stock transfers between Indonesia and Singapore tracked as a single movement, visible to both sides while in transit.
Role-based access, so warehouse floor staff, branch managers and the Singapore office each see the view appropriate to them.
Reporting that reads from live data, so month-end consolidation stops being a manual exercise.
What we delivered
Cross-border network links between the Indonesian and Singaporean sites, with failover and monitoring.
Server infrastructure on both sides of the corridor.
A warehouse management system covering goods-in through dispatch at both locations.
Cross-border inventory with a single stock record per item and tracked inter-site transfers.
Live operational dashboards and exportable reporting.
Handover documentation and on-site training for the warehouse and office teams.
The result
AP Intermodal's two sides now read from the same system rather than reconciling two versions of the truth. Stock levels are current on both sides of the strait, inter-site transfers are visible while they are moving, and the Singapore office can answer an inventory question without calling Jakarta.
The connectivity work is what makes the warehouse layer credible: the systems are only as live as the link underneath them.