Skip to content

Shopify · Orders, inventory & shipping

Keep stock and shipping information accurate.

Deliveries, tracking, stock counts and customer messages kept in step, so an order stops turning into a support ticket on its way out of the door.

Is this for me?

Four problems this work is for.

None of these show up in a design review. They happen in the gaps between systems, which is why they survive a redesign.

The order that shipped twice

One system was told the order went out and the other was not, so a second parcel goes out and the profit goes with it.

Tracking nobody sent

It shipped, but the message quietly failed. The customer finds out by emailing to ask.

Stock that disagrees with itself

The store says two left, the shelf says none, and you find out at packing rather than at checkout.

Four tabs to answer one question

"Where is my order" taking a person through the admin, the courier, the helpdesk and a spreadsheet.

What we do

What the work actually is.

01

Shipping kept in step

Orders, deliveries and returns kept in step between Shopify and whoever ships — your own warehouse, or a 3PL, the company that stores and ships your products for you.

02

Messages that try again

The messages a customer gets after buying, with a retry if the first attempt fails and a record of what was sent — rather than a message nobody notices going missing.

03

One stock count

The store reading from a single count, with an alert when it drifts away from what was actually counted.

04

Everything about an order in one place

The order, its history and its messages in one view, so answering a customer takes a moment rather than four tabs.

Interactive example

One order, two locations.

Stock split across two locations, a message that fails to send, a shelf that disagrees with the count. Make the merchant's decisions and watch the stock, the messages and the record keep up.

Three throws, and no single location holds all three. You decide whether the customer waits.

ReadyOrder #1043Day 1 · 14:02

Each step the order takes lands here, with the system it happened in.

Next

The order starts moving when the demo is in view.

Stock

available to sell
ItemWarehouseShop
Wool throw2 1 
Enamel mug40 6 

Customer

Maya’s phone

Nothing yet. Texts and emails land here as they are sent.

Ledger

Order #1043
  • Order3 items
  • Refundnone
  • Feespending
  • Payoutpending
  • Checkruns when the payout lands

A worked example. The store, the order and the timings are scripted for the demo.

How it runs

We look before we price.

01

Map

Every system an order passes through, and every handover between them. Most of the problems are visible at this stage.

02

Scope

A written list of what is being connected, and a price, before work starts.

03

Build

Set up and tested against real orders, including the awkward ones — part-shipped, returned, exchanged.

04

Watch

Failures show up as an alert to you rather than as an email from a customer.

Pricing

Small jobs $250–$750

Larger work is quoted after a short call, because the price depends on which systems are involved. You get a written scope and a firm price before anything starts.

Questions

Shopify inventory sync: common questions

Usually not. Most of it is joining up systems you already run. Where an app already does the job well, we will tell you to use the app.

You get an alert rather than silence. It is built expecting things to fail: it tries again, and anything that could not be delivered can be sent again rather than being lost.

Tell us which part keeps going wrong.

We look before we quote, and you keep what comes out of it either way.