Disconnected records
Fulfilment and consignment data sit in different systems, each with its own identifiers and event vocabulary.
I designed and developed both the custom Cloudflare Worker delivery app and the Shopify–CartonCloud API integration. Together, they coordinate Shopify fulfilment information, logistics consignments, tracking events and estimated delivery-date updates.
Technical write-upShopify records the order and communicates with customers; CartonCloud manages the physical consignment lifecycle. Without a dependable bridge, shipment movement, tracking state and estimated delivery dates can become fragmented. Manual checking introduces delays and makes a consistent customer-facing delivery experience harder to maintain.
Fulfilment and consignment data sit in different systems, each with its own identifiers and event vocabulary.
Delivery estimates and tracking milestones need structured, recoverable updates at the order level.
Webhook retries, API authorisation and partially processed updates require explicit diagnostics and controls.
Two distinct development contributions working as one system. The app orchestrates the operations; the custom integration handles communication and data mapping between Shopify and CartonCloud.
Order and fulfilment information
API authentication · Orchestration · Delivery-date handling · Diagnostics
API requests · Webhook processing · Consignment and tracking synchronisation
Consignments · Tracking milestones · Delivery events
The same app and integration provide the return path for tracking information, fulfilment events and estimated delivery dates stored in order metafields.
The Cloudflare Worker application coordinates authenticated requests, webhook handling, delivery-date logic, error investigation and Shopify order updates.
The Shopify–CartonCloud integration maps fulfilment information to consignments, exchanges tracking events and synchronises delivery data between platforms.
Conceptual visual only. No internal architecture diagram, payload, real order reference or secret is reproduced.
Connect commerce fulfilments to a warehouse system using authenticated REST calls and a serverless integration layer.
Translate provider-specific tracking and delivery states into a consistent set of Shopify-facing fields and events.
Investigate access scopes, webhook sequencing, retries and replay safety. These are engineering concerns, not all independently verified production guarantees.
Keep estimated delivery information associated with the order so support and notification workflows can reference the same intended record.
The supplied app log screenshot shows four successful GET requests for fulfilment-order resources. This confirms those requests were accepted, not that a full delivery update succeeded.
Previous tests exercised tracking and fulfilment paths, and a manual retry wrote a delivery-date metafield on a test order. This is not proof of complete automatic coverage.
A fresh audit of CartonCloud events, Shopify writes, error logs, failed retries and a representative order sample is needed before asserting every order is correctly synchronised.
The original app-log screenshot was deliberately not published because it contains production store and order identifiers. Successful API reads do not establish successful consignment creation, delivery writes or zero-error operation.
Both a custom serverless delivery app and the Shopify–CartonCloud integration it operates, including order/fulfilment lookups, tracking-state handling and delivery-date update paths. This reduced the need to treat the two platforms as isolated sources when investigating orders. No quantified time saving is claimed.
Permission validation, durable idempotency, bounded retries, observable write failures and sampling across dispatch, transit and delivered orders. The project is described as implemented and tested in part; current full-production synchronisation has not been freshly verified.
Portfolio documentation only. This page does not provide credentials, production Worker code, tracking URLs, raw customer records or employer-owned configuration.