What flo.space prepares with Shopify
Reads orders, customers, and inventory and prepares stock updates and order responses.
- Prepare a low stock restock note
- Draft a reply to an order status question
- Update inventory after a receiving
What it reads, and what it can write
Reads · read-only to start
Only the Shopify data you connect, within the OAuth scopes you approve. flo.space reads the context it needs to prepare an action and nothing beyond it.
Writes · only on approve
Nothing writes back to Shopify until you approve it. On approval, flo.space performs the exact action you reviewed, and logs it to the audit trail.
A Shopify action, prepared and waiting
Every prepared action lands on one screen with its source, reasoning, and a risk level. You approve, edit, or decline.
Recommendation: Reads orders, customers, and inventory and prepares stock updates and order responses.
What flo.space drafts from your store
Four workflows carry most of a store's correspondence, and flo.space drafts all of them from live Shopify data: order confirmations with the real items, totals, and expected ship window, written like a person and flagged when an order is unusually large or from a new account; customer replies to status, availability, and pricing questions, answered from current inventory rather than memory; invoices drafted from orders for the wholesale buyers who pay on terms rather than at checkout, posted to QuickBooks on your approval; and availability and restock replies with quantity on hand cited at draft time.
Worth locating honestly against the tools that share this search result page: A2X, Synder, MyWorks, and Amaka are sync engines; they move Shopify transaction data into your accounting package accurately and unattended, and they are good at it. flo.space is not a sync engine. It is the drafted, human-approved communication layer on top of the same data: the confirmation, the reply, the invoice on terms. Plenty of stores run a sync tool and flo.space together; they do not overlap.
Connecting Shopify, step by step
Choose Shopify and authorize through Shopify’s standard OAuth with your store login.
Orders, customers, and inventory levels, read-only. Nothing at this step can modify your store.
Confirmations and replies referencing real orders appear in the queue within a day, each citing its order number and data.
Inventory updates and any store-side writes are prepared actions requiring both the write scope and your per-action approval.
A worked example
Order #2114 lands: a wholesale account's usual buyer, but at twice their average size. flo.space drafts the confirmation with the line items and a Wednesday ship window from your recent fulfillment pace, and flags the size anomaly instead of treating it as routine. You glance at the account history it cites, decide the jump is the spring reorder, approve the confirmation, and approve the companion action: a QuickBooks invoice on the account's net 15 terms instead of a card charge. Both records land in the audit trail linked to the order.
Limitations, honestly
flo.space does not build your storefront, edit themes, manage listings, or run marketing campaigns. It does not replace Shopify's own transactional emails; it drafts the personal correspondence those emails cannot carry, which matters most for wholesale and B2B stores. Multi-store setups connect one store per workspace today. For the accounting combination specifically, the Shopify + QuickBooks page covers the whole flow, and the order confirmation template shows the flagship workflow with a realistic drafted example.
Shopify + flo.space, answered
No, and it does not try to. Shopify’s transactional emails stay on. flo.space drafts the personal correspondence on top: the wholesale confirmation with a human voice, the availability answer, the invoice on terms, each approved by a person.
Those are sync engines: they move Shopify transactions into your accounting package unattended, and do it well. flo.space is the communication layer: it drafts what you SAY to customers and what you invoice on terms, with human approval on every send. Many stores run both.
It prepares inventory updates as approval-gated actions when receiving or corrections imply them. It never adjusts stock unattended.
It works best where orders carry relationships: wholesale, B2B, and high-touch B2C. A store doing thousands of small anonymous orders a day should lean on Shopify’s native automation and use flo.space for the exceptions that need a human-quality reply.
Shopify paired with the rest of your stack
Deep dives on what flo.space prepares between two connected tools.
Connect the rest of your stack
Put Shopify on approve
Connect Shopify read only and let flo.space prepare the first wave of actions. Nothing sends until you approve.