An Australian retailer sold through several marketplaces while sharing one fulfillment operation. Mark Philippe Mirasol built the order, tracking and stock connections, then retained that integration layer when the storefront changed.
Catch, Kogan and MyDeal supplied orders in different formats. The warehouse needed them in ShipStation, while each marketplace needed shipping and tracking information returned after dispatch.
Available stock was another shared dependency. Updating channels independently could leave them disagreeing with the inventory system, so the workflow needed a clear source for stock availability.
Custom PHP connectors exported marketplace orders in the XML format used by ShipStation custom stores. Ship-notify callbacks returned tracking and carrier information to the originating channel.
SkuVault supplied stock updates to Catch and Kogan. During a later move to MedusaJS, Mark retained the connectors and deployed the replacement storefront with Docker and Caddy on DigitalOcean, promoting the same build through environments.
Project materials showing the workflows and interfaces described in this case.
Orders, shipments and stock had explicit paths between the retailer’s systems. The later storefront change reused those connections, preserving the operating workflow while replacing a different part of the stack.
A replatform should start by separating the customer interface from the processes it depends on. Mapping stock authority, order identifiers and shipment callbacks makes it possible to replace one component without rebuilding every connection. Those interfaces are valuable business assets in their own right.
Project contribution: Mark Philippe Mirasol. The scope described above identifies the work behind this case.
Editorial review: Ego Eimi · Updated September 6, 2026 · About the team
Your technology
Start with the business
Tell us which system matters, what has changed and who controls it. We will define a reviewable next step. Read Foundation and the commitments and evidence.
