Shopify

Shopify runs the store; your transport team runs the freight that follows. Often the two meet in a CSV export someone downloads at four o'clock. Connected to Cargofy, every order arrives in Load Hub as a shipment within minutes of being placed, with ship-to address, line items and the store order number, and a digital worker builds loads from it. The transport planner usually asks for it; the store admin issues the credentials.

What teams use it for

Plan loads from the order feed

Each order arrives in Load Hub as a shipment carrying ship-to, line items and weights, so the planner no longer cleans the afternoon export and keys shipments into the TMS. In the afternoon the planner asks the digital worker to build loads. It groups shipments by destination, date and equipment into loads for Planner, and the planner reviews the plan.

Consolidate a region into one truck

By the afternoon cut-off, fifty orders to Texas are in Load Hub as shipments. The planner asks the digital worker to plan the region. It groups the Texas shipments by destination and date into multi-stop LTL consolidations out of your DC and leaves the rest for parcel. The planner sees the consolidation in Planner with the stops in order, adjusts it if needed and books it. The orders on that truck come off the parcel bill.

Stop a cancelled order from riding on the truck

A customer cancels an order after it was picked. The Shopify trigger passes the cancellation to Cargofy, and a digital worker marks the shipment cancelled in Load Hub and flags it. If no carrier is booked yet, the flag keeps the shipment off the next load. If the load is built, the planner sees the flag in Planner and pulls the stop before the carrier arrives.

Answer an order question from one screen

Customer service gets an email about order #58213. The store order number is on the shipment, so the rep searches Tracking by that number and sees the load, the carrier and the ETA. Documents on the load carry the same number, so the POD is one click away when the customer asks for proof of delivery.

Catch an address change before pickup

A customer edits the ship-to in their account the evening before pickup. The trigger reads the update from Shopify, the shipment in Load Hub takes the new ship-to, and the planner sees the change on the load before the carrier arrives.

How it fits your stack

Shopify stays the order system of record and Cargofy the shipment system of record. The integration is read-only: orders, updates, cancellations, ship-to addresses, line items and weights are read into Load Hub. Setup is per installation: your store admin issues API credentials with read access to orders, and the order-to-shipment rules are mapped at scoping. It runs through Cargofy's n8n layer. Fulfillment status and tracking numbers are not written back to Shopify in this scope, so the customer's order page does not update from Cargofy.

Who it is for

Direct-to-consumer and B2B brands on Shopify that ship more than parcel: pallets, LTL, multi-stop consolidations out of their own DC. Transport planners build loads from the order feed, customer service answers from Tracking, and the IT admin owns the store credentials.