Integrations · Shopify
Count the shop floor, and Shopify gets the corrected level.
If what you wanted was to count your store and have the numbers land back in Shopify, this is that.
What moves, and which way.
Down, before the count
Products and inventory levels come down as the counting catalogue, per location, so a phone in one shop is counting that shop’s stock.
Back, after you approve
Corrected levels go back per location, so a two-shop business ends with two correct shops rather than one merged number.
Nothing is written until you approve it. The count sits on the hub, the variances are reviewed there, and the write is one pass at the end that you start.
A custom app on your store, and nothing in between.
What you supply
A custom app on your own store, which you create in the Shopify admin and whose token you hold. The hub uses it directly.
Fractional quantitiesheld back and named
Shopify quantitiesare whole numbers
Locationsmust exist in Shopify first
What it cannot do yet, before you buy rather than after.
- Fractional quantities are held back and named, never rounded. Shopify’s quantity is a whole number, so 2.5 kg has nowhere to go — SoftBo tells you which items those are instead of quietly writing 2.
- Locations have to exist in Shopify first. SoftBo writes to the ones that are there; it does not create them.
- It writes levels, not products. A barcode that is not in Shopify is reported, not created.
- It has not been run against a live Shopify. The code is written and tested against a stub, and the write path ships behind a flag that is off. The date below is empty on purpose, and it is the honest state of it.
[VERIFIED · DATE] and [SETUP TIME]. Both close the first time SoftBo writes to a real Shopify. That one afternoon turns this page, the integrations page and CLAIMS C1–C3 green together.