How to sync supplier stock to Shopify without an API
Ask ten dropship merchants how their supplier stock gets into Shopify and most of them will say one of three things: someone updates a spreadsheet, we pay an integrator for this specific supplier, or we don't — we find out we're out when a customer complains.
The awkward truth is that most suppliers don't have an API. Not a bad one, none at all. What they do have is a person in logistics who exports a CSV from their ERP every Friday morning and emails it to their accounts. That email is the integration everyone has and nobody uses. Here is how to turn it into a Shopify sync.
The pieces you need
Four moving parts, in order:
- An inbound email address per store. Your supplier emails here; you route on the address. `shop-<slug>@your-domain.com` is plenty of entropy, gated by a sender allowlist.
- SPF, DKIM, and DMARC enforcement, because supplier emails flow through an external system and you don't want a vendor's email account compromise writing stock values on your products.
- A parser with an explicit column mapping. Suppliers name their columns inconsistently ("SKU" vs "Product Code" vs "Item No"). Pick your column names per supplier once; don't auto-detect.
- A place to put the result. Shopify product metafields, under a namespace you own.
That's it. There is no hard bit. The hard bit is the operational bit — what happens when a supplier silently renames a column, when a sender's email gets spoofed, when they forget to send a week. But the core integration is small.
Why product metafields, not Shopify inventory?
Shopify has native inventory levels tied to locations. You could, in theory, create one Location per supplier and write quantities there. Most merchants don't want that. They want their supplier's stock as advisory data — something that informs their fulfilment rules, triggers their Shopify Flow automations, feeds their out-of-stock alerts — without overwriting the inventory numbers they've carefully assembled themselves.
Product metafields are perfect for advisory data. They show up on the admin product page if you add a metafield definition. They're queryable from the Storefront API if you want to show "only 3 left from supplier" on a PDP. And they don't fight with your existing inventory model.
What breaks in practice
A few lessons from a few hundred thousand ingested rows:
- Your supplier's CSV format will drift. Not the schema — the file. Extra blank rows, merged headers, a UTF-16 BOM snuck in because someone opened it in Excel and re-saved. Detect these at parse time and fail loudly.
- Zero rows is a signal, not an empty state. If a file comes in with zero parseable rows, treat that as an alert. It usually means the supplier broke their export.
- Trust the sender's email address, not the From header. SPF and DKIM exist; use them to decide whether a given supplier email is really from that supplier.
- Don't auto-create products. Match on SKU only, report unmatched rows, don't guess. Let the merchant audit drift before it becomes a data problem.
The "no supplier integration" integration
The best integration is the one that requires zero work from your supplier. They keep sending the same CSV they've been sending for years. You handle the rest. When merchants realise they can add new suppliers without so much as a meeting, the adoption curve looks different.
Stockpost is this idea, productised: one inbound address per store, sender allowlists, column mapping per supplier, metafield writes, full audit log. $39 / store / month, 14-day trial.