Magaya integrates PortConnect into New Zealand workflows

Magaya integrates PortConnect into New Zealand workflows

Magaya is integrating PortConnect data into New Zealand freight workflows. Container status, vessel schedules, clearance information, and arrival and departure estimates will feed directly into Magaya Supply Chain, reducing separate system checks for forwarders.


IN Brief:

  • Magaya is integrating New Zealand PortConnect data directly into its freight management platform.
  • Container movements, import availability, border clearance status, vessel schedules, and ETA/ETD data will update shipment records.
  • The connection extends Magaya’s recent New Zealand customs rollout into port and container visibility.

Magaya is integrating New Zealand port community system PortConnect into its freight management platform, bringing container movements, vessel schedules, border status, and import availability into the same workflows used to manage shipments and logistics operations.

The connection will feed PortConnect information directly into Magaya Supply Chain rather than requiring forwarding teams to check separate port systems and manually transfer status information into shipment records.

Data available through the integration will include container locations and movements, import availability, Customs, Ministry for Primary Industries and shipping line clearance status, vessel schedules, and estimated arrival and departure times.

Magaya is building the connection through Magaya Connect, its integration platform. PortConnect remains the independent provider of the underlying port and container information, while Magaya will display relevant data against shipment records and operational workflows.

The distinction avoids duplicating the port community system inside the forwarding platform. PortConnect continues to collect and standardise information around New Zealand’s port network, while Magaya uses that information alongside the booking, warehouse, customs, accounting, tracking, and customer service processes already attached to a shipment.

Forwarding operations routinely depend on several statuses being true at the same time. A container can have arrived physically while remaining unavailable for collection because a border, carrier, or terminal release is still outstanding. A vessel schedule can also change after transport and warehouse resources have already been booked around the original arrival.

Bringing those events into a common operational record should reduce the need for staff to establish shipment status by moving between several systems. The useful outcome is not simply an additional stream of information, but earlier identification of the events that require transport bookings, customer commitments, or warehouse plans to change.

Automatic updates can be particularly useful when a shipment moves normally. If location, availability, and clearance information can update without human intervention, operations teams can focus attention on exceptions rather than repeatedly checking consignments that remain on schedule.

When something does change, the quality of the integration becomes more important. A delayed arrival might require a truck booking to move, while a clearance hold could affect warehouse labour or a promised customer delivery. The value comes from attaching the new information to the shipment early enough for those decisions to be adjusted.

The PortConnect development follows Magaya’s New Zealand customs integration launched earlier in August. That application connected Trade Single Window submissions with forwarding processes, allowing shipment information to support customs filing without rebuilding the same record separately.

PortConnect extends the same approach beyond the declaration itself. Customs filing confirms one part of a cargo movement, but forwarders still need to know whether the container has reached the port, whether the line and border agencies have released it, and when the physical collection or onward movement can take place.

Combining those processes gives Magaya a broader operating footprint in the New Zealand market. A shipment can be created and managed within the freight platform, customs information submitted through the compliance application, and port events returned into the same environment as the cargo reaches the gateway.

That reduces one of the more persistent inefficiencies in digital logistics: different systems can each hold accurate information while operations staff still spend time copying, checking, and reconciling it between applications.

The technical challenge is therefore less about making data available than making sure it maps cleanly between systems. Container identifiers, shipment references, vessel information, clearance status, and timing fields need to match the correct operational record without creating duplicates or stale information.

Update frequency is equally important. A port status that reaches a forwarder after a truck has already been dispatched has limited value, while an early change to ETA or import availability can allow resources to be rescheduled before unnecessary cost is incurred.

Exception handling will determine how effectively customers use the integration. Displaying every event can overwhelm an operations team if routine updates receive the same attention as a customs hold or missed connection. Systems become more useful when the workflow distinguishes between information that merely confirms progress and an event requiring intervention.

Magaya says the integration will provide earlier awareness of delays, holds, and other shipment exceptions while reducing duplicate data entry and manual tracking. Those objectives are measurable once the connection enters normal use through the volume of manual checks removed, the speed at which exceptions reach operators, and the amount of shipment information that can update without re-keying.

The PortConnect connection also reflects a wider shift in freight software towards integration rather than trying to recreate every specialist function inside one product. Ports, customs agencies, carriers, warehouse systems, trucking platforms, and forwarders generate different operational data, and replacing each of those systems is rarely practical.

A connected architecture leaves the specialist application responsible for its own information while passing relevant events into the system where an operator manages the broader shipment. That places greater emphasis on interfaces, data standards, and record matching than on expanding the number of standalone screens available to users.

For New Zealand forwarders, the immediate change is comparatively straightforward: PortConnect information that previously had to be checked separately will become available inside Magaya Supply Chain. The harder test comes after implementation, when customers can measure whether connected port, customs, and freight data actually removes manual work and enables faster intervention when a shipment stops following the plan.


Stories for you


  • Panama Canal loosens Neopanamax booking rules

    Panama Canal loosens Neopanamax booking rules

    Panama Canal has revised Neopanamax booking rules for September transits. Customers gain greater flexibility over multiple and consecutive reservations while water constraints continue to shape vessel planning.


  • Ports America signs ten-year Trailer Bridge deal

    Ports America signs ten-year Trailer Bridge deal

    Ports America will support Trailer Bridge under ten-year Jacksonville agreement. The partnership combines stevedoring with a terminal operating platform intended to improve shipment visibility on the carrier’s Puerto Rico service.