Shops where an order is the beginning of real work rather than the end of it — assembly, personalisation, installation, fulfilment by hand — and where that work currently lives in a spreadsheet beside the admin.
Pull Shopify into RowFold tables you own — filter them, report on them, link them to everything else in the workspace.
And it stays current: importing again updates the same tables, adding new records and updating changed ones, so links from your other tables hold. Keep in sync does that for you hourly or daily.
Automation steps that act on Shopify when something happens in RowFold:
What it doesn't do: It has no say in what a booking page offers. An import only reads: nothing is written back to Shopify, a record deleted there stays here, and a sync runs hourly at most rather than the moment something changes. Anything else you have read about Shopify and RowFold, this page is the authority: it is generated from the connector's own code.
The import gives you the orders; the value is in what you add next, because Shopify's statuses are about money and postage and your operation is about neither. Budget ten minutes for deciding your own statuses before importing anything.
You'll know it worked: Compare the order count for a recent week against the Shopify admin for the same week. If a longer range comes up short, check the order scope before assuming the import dropped anything.
The step changes an inventory level by an amount at a specific location, so it wants two ids and a delta rather than a product name and a new total. Both ids come from Shopify and neither is the product id.
You'll know it worked: Run it once with a change of one against a test product and compare the level in the Shopify admin with the one saved on the record. Then re-run the same record and confirm the level does not move again.
Shopify's order statuses describe payment and shipping, and nothing about your actual process. Cut, engraved, awaiting stock, with the framer, ready for collection: none of those exist, so the real status probably lives in a spreadsheet somebody updates twice a day.
Import orders and give them the statuses your operation really has. The spreadsheet becomes a table with the order beside it rather than a copy of it.
Nothing joins an order to the supplier purchase it depends on. When a component is late, working out which customer orders are affected means reading both lists side by side.
Link orders to purchase orders, components and suppliers. A late delivery then answers “who is waiting” as a filter rather than as an afternoon.
Stock adjustments that come from outside the shop — a stocktake, a breakage, a return to the supplier — get typed into Shopify by hand, which means they tend to happen late and sometimes not at all.
An automation adjusts the level from the record that caused it, so the count changes because the event was recorded rather than because somebody remembered.
Because Shopify limits order access to the last 60 days unless the app has been granted the wider order permission, which is a separate scope you request on the custom app. The import reports this in its warnings rather than leaving the short history looking like a fault. Grant the scope in Shopify and import again: the older orders join the same table, beside the ones already there.
No, and nothing here would let you. Shopify runs the storefront, takes the money and handles checkout, all of which it does far better than a workspace builder would. What it has no opinion about is what happens between the order landing and the parcel leaving, which for a lot of merchants is arguably where the actual business is.
Yes, on a schedule. Importing again adds new orders to the same table and updates changed ones, a fulfilment or a refund for instance, matched on the Shopify order ID, and Keep in sync runs that hourly or daily. Without the wider order permission each run sees only the last 60 days, so an older order stays as it was when it last fell inside that window. If you need to react within seconds of checkout, that is a webhook problem and a different mechanism from an import, so it is worth being clear before building a process that assumes it.
The available quantity of one inventory item at one location, by an amount you give it. It does not set a total and it is not a product-level operation, which surprises people the first time: the inventory item id is a different number from the product and variant ids, and in a multi-location shop the location id decides which warehouse moved.
Yes. Shopify connects with credentials from a custom app you create in your own admin, so nothing depends on an application we registered with them and there is nothing pending at our end. Create the app, grant the read scopes you want, paste the values, and the resource list appears.
There is no template to wait for. Type a sentence about what you run and RowFold assembles the tables, links, views and dashboard around it — then you change whatever does not fit.