Customers, orders and dispatches, worked for you
Your Orderspace, worked while you do something else: 3 reads to go through it, 4 writes to change it, and a card in front of every one of those changes.
Open the customer. Check it against something else. Write the change. Move to the next one. That is the Orderspace afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a customer until you approve it.
What it can do is exactly what Orderspace exposes to an account you authorise and nothing beyond it: 7 operations, 3 reads and 4 writes. In practice that means it can update an inventory level, create an order and create a dispatch, and work across the customers, orders and dispatches.
The Orderspace API stops at Orderspace. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Does it read the customers or ask you for them?
3 of the 7 operations are reads.
Your account, not a guess at it: a companion can list products, list orders and list customers, and the full list below is the whole list, with nothing inferred from Orderspace's documentation.
The customers are what most of this inventory is about, alongside the orders. A companion can hold all 7 of these operations and forty open tabs in the same pass, which is how an afternoon of Orderspace admin becomes a queue you review.
- List Products
- List Orders
- List Customers
Which customers wait for your approval?
All 4 write operations wait for you.
A companion can update an inventory level, create an order and create a dispatch, and each one is staged on an approval card first: you see the customer, the field and the new value before it lands in Orderspace.
Nothing in Orderspace is sent, changed or deleted on your behalf without that click, and a rejected card leaves the customer exactly as it was. The gate is the same one on every surface, described at security.
- Update Inventory Level
- Create Order
- Create Dispatch
- Create Customer
Does the customer sweep have to be asked for every time?
Yes.
Saved as a routine, the Orderspace customers pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The operations playbook catalogues the other recurring shapes of store admin, the Orderspace customers sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents