EZOM Mateship Logistics Pty Ltd · Production logistics platform

Mateship Logistics Platform

Logistics workflows across Node.js, GraphQL, PostgreSQL, and React, including carrier and commerce integrations.

What it shows
Third-party integrations
My role
Fullstack Developer (remote)
When
1/2024 – now
Company
EZOM Mateship Logistics Pty Ltd
React NativeNode.jsGraphQLPostgreSQLTypeScriptCypressKeycloakBullMQDockerMonorepoRedisEzOM Landing EzOM Docs

01 · The problem

Orders, warehouses, and carriers all have to talk to each other. Every carrier or commerce platform has its own API and quirks, so integrations never stop coming, and each one touches live customer orders.

02 · What I did

  1. 01Built and maintained features across Node.js/GraphQL/PostgreSQL services and the React Native/React apps.
  2. 02Integrated Xero, Shopify, JDL, BlueStar, BorderExpress, 4PX, Allied Express, AML, Bonds, and XFM.
  3. 03Led the frontend migration from React Native to React.js.
  4. 04Fixed production issues and supported customers directly in English.

03 · Decisions & trade-offs

Moving from React Native to React.js

Led the move to React.js to make the frontend easier to maintain and to improve the user experience.

04 · Before / after

Drag the divider to compare

Demo image (replace): screen rebuilt in React.js
Demo image (replace): previous frontend
BeforeAfter
Frontend migrationBefore: the previous frontend. After: the same screen rebuilt in React.js.

05 · Screens

EZOM landing page
EZOM landing page
EZOM product login
EZOM product login

06 · What I achieved

What changed

  • 10 third-party integrations shipped.
  • Frontend migrated to React.js.

Next case study · EZOM

Organisation Subscription · Stripe

Mateship Logistics Platform · case study | Bui Thuy Ngoc