Shops and service businesses that sell through Shopify, WooCommerce or Stripe and run the work behind each sale, such as making, fitting, delivering or chasing payment, somewhere their store can't see.
Import orders, products and customers, and adjust stock levels from an automation.
Import orders, products and customers from your WooCommerce store.
Import customers, subscriptions, invoices and payments — and create payment links from an automation.
Import the orders to get the backlog in, and keep them in sync if new ones should follow. The work goes on records of your own that link to them: the order stays a fact about the sale; the job carries your process.
You'll know it worked: Open an order with a job and check the job is listed on it. Then filter Jobs by status and check the count matches what the team says is on the bench.
The store import names the customer on every order instead of linking it. One conversion turns those names into links, and each customer then shows their orders.
You'll know it worked: Open a customer you know and check their orders are listed. Orders still showing a plain-text name are guest checkouts or names that differ between order and account; link those by hand or leave them.
A store's order statuses describe payment and shipping. Cut, engraved, waiting on stock, with the fitter: the steps your business actually runs have nowhere to live, so they end up in a spreadsheet beside the store.
Import the orders, then track your own steps on a Jobs table that links to them. A board of job statuses shows the real state of the week, and each order lists the work behind it.
An import arrives as separate lists: orders in one table, customers in another, with the buyer's name typed on each order and no link between them.
Convert to Relation… turns the name on each order into a real link to the customers table, matching by name and leaving anything it can't match as typed. Each customer then lists their orders, and a rollup can total them.
A store dashboard answers the store's questions. Which product causes the most remakes, or how long an order waits for a fitter, aren't among them.
Once orders and your own work records are linked, those questions are ordinary filters and reports over tables you control, not an export rebuilt every month.
Both, for different tables. The store knows orders, products and who bought what. Stripe knows subscriptions, invoices and payments, including any that never went through the store, and it names each customer by email address. Import what each one is the authority on, rather than the same customers twice.
They can, on a schedule. Importing again adds new orders to the same table and updates changed ones, matched on the store's or Stripe's own IDs, and Keep in sync runs that hourly or daily for each connection. A Shopify store without the wider order permission only ever shows an import the last 60 days. Work that has to start the moment somebody checks out needs something that listens, and an import doesn't.
Your shop's address, which must start with https, and a REST API key made in WordPress under WooCommerce, then Settings, then Advanced, then REST API. Read permission is enough, because RowFold only reads from Woo. Paste the consumer key and the consumer secret, which WordPress shows once, and press Save & verify.
Guest checkouts aren't customers in WooCommerce's sense: only people with an account on the shop appear in its customer list, and the import brings that list. Guest orders still come across in the orders table, with the buyer's name and email on each order, so nobody's order is lost.
Only through actions you put in an automation. Shopify can adjust a product's stock level, and Stripe can create a payment link or a customer. WooCommerce is read-only. Imports never write back to any of them, so importing can't change an order, a price or a customer record.
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.