Logistics
Carriers, forwarders, warehouses and declaration systems still exchange data in batches and files. We connect them through governed APIs and event streams on Google Cloud, so exceptions surface while there is still time to act.
Updated October 19, 2026
In logistics, the value of information falls by the hour.
Your shipments, partners and customers multiply, and every partner integrates a different way. Planners keep the network moving by phone, email and a wall of screens.
Declarations
Goods moving in, out of and through Singapore are declared through TradeNet, and controlled items need permits under the Strategic Goods (Control) Act. Data re-keyed between your systems and the declaration is where errors start.
What waiting costs: cargo held while someone corrects a field by hand.
Documents
Singapore's Electronic Transactions Act recognizes electronic transferable records such as bills of lading, and IMDA's TradeTrust framework lets parties verify them. Paper and PDFs between partners slow every handoff that depends on them.
What waiting costs: shippers move to forwarders who can exchange documents as data.
Exceptions
Rebooking, rerouting and customer notices are being automated across the region. IMDA's framework for agentic AI asks for bounded autonomy and human checkpoints, and the PDPA covers the consignee details the agent reads.
What waiting costs: an agent that acts without limits once, and is switched off for a year.
| Regulator or law | What it asks | What it means for an agent |
|---|---|---|
| Singapore Customs: TradeNet and the Networked Trade Platform | Accurate declarations and permits for goods imported, exported and in transit | An agent may draft or check a declaration; the declarant submits it, and the record shows both. |
| Strategic Goods (Control) Act, administered by Singapore Customs | Permits for controlled goods, including transshipment and transit | An item flagged as controlled leaves the automated path and goes to a compliance officer. |
| Electronic Transactions Act, as amended in 2021, and IMDA's TradeTrust | Legal recognition of electronic transferable records; verifiable trade documents | Documents move through the API layer as verifiable data, with the trail intact. |
| Cybersecurity Act 2018, as amended in 2024 | Duties for owners of critical information infrastructure, including in maritime and aviation | Integration with port or airport systems follows the owner's controls and access rules. |
| Personal Data Protection Act | Purpose, protection and accountability for shipper and consignee personal data | The agent reads only the contact details a notice needs. |
Every partner integration was built for its own contract, so status data arrives in a dozen formats on a dozen schedules. Before any agent can help a planner, the events have to arrive on time and in one shape.
How long after a shipment misses a connection does a planner who can fix it find out?
A missed connection, found while there is time to fix it
We turn one lane's status data into events first, then put an agent on its exceptions with a planner signing every fix.
One governed Apigee layer for carriers, warehouses and customers, with EDI kept where a partner needs it and a developer portal for new partners.
You hold: an owner and a policy for every partner connection.
Apigee and APIsStatus events carried as event streams on Google Cloud to the transport system, the warehouse system, customer notices and BigQuery together.
You hold: one version of each shipment's status, seen by every system at the same time.
Vertex AI, BigQuery and dataAgents on Gemini Enterprise that propose a fix within cost and service limits and hand the decision to a planner.
You hold: one exception agent in production with planner approval and a decision log.
Gemini Enterprise and agentsEasy to start
Choose one workflow, name one owner, and give us time with the people who sign it off.
We bring engineers and the gateway design, we work inside your environment under your security rules, and we write the review pack alongside the build.
A good first workflow is exception handling for one lane or one carrier. See the fixed-price ways to start.
What the work feels like
One workflow is chosen and one person owns it. The questions your reviewers will ask are written down before any build starts. Your planners see live exceptions from one lane in the first sprint demo.
Governance goes in before the first agent does: the gateway, the audit trail and the access rules. Your risk team sees them working.
A working demo you can show your own review board, not a status slide.
A decision log that can rebuild any action, and a go-live date that was agreed at the start.
Seen it before
Production readiness check
A short readiness check on a live or planned agent workflow. You get a score and the principles worth another look.
Take the readiness checkNo. We keep EDI where partners depend on it and put it behind the same governed layer as your APIs, so every message has an owner and a log. New partners can connect by API when they are ready.
Yes. We work in the integration and data layer around them, and they stay the systems of record.
Only inside limits you set for cost, carrier and service level. Anything outside them goes to a planner, and the log shows what the agent proposed and who approved it.
By publishing one standard API product with a developer portal, keys and a test environment. Carriers connect to the standard instead of a custom link for each one.
We design agents to prepare and check declarations, not to submit them. Submission stays with the declarant your Customs registration names, and the log shows what the agent drafted and what a person changed.
Tell us what you are working on. Our Customer Partnership Team will reply to arrange a conversation.
Get answers to your questions
AI assistant. It can make mistakes, so check anything important with our team.
