The Allocadence customer orders nobody wants to work through
Allocadence exposes 2 operations and a companion can work all of them: create a purchase order and create a customer order. Anything that changes a record waits for your click.
Open the customer order. Check it against something else. Write the change. Move to the next one. That is the Allocadence afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a customer order until you approve it.
What it can do is exactly what Allocadence exposes to an account you authorise and nothing beyond it: 2 operations, no reads and 2 writes. In practice that means it can create a purchase order and create a customer order, and work across the customer orders and purchase orders.
The Allocadence API stops at Allocadence. 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 customer orders or ask you for them?
In the tab.
Allocadence exposes no read operation to a connected account, so a companion opens Allocadence in the session you are already signed into and reads the screens you would.
The customer orders are what most of this inventory is about, alongside the purchase orders. A companion can hold all 2 of these operations and forty open tabs in the same pass, which is how an afternoon of Allocadence admin becomes a queue you review.
What happens before it can create purchase order?
All 2 write operations wait for you.
A companion can create a purchase order and create a customer order, and each one is staged on an approval card first: you see the customer order, the field and the new value before it lands in Allocadence.
Nothing in Allocadence is sent, changed or deleted on your behalf without that click, and a rejected card leaves the customer order exactly as it was. The gate is the same one on every surface, described at security.
- Create Purchase Order
- Create Customer Order
Does the customer order sweep have to be asked for every time?
Yes.
Saved as a routine, the Allocadence customer orders 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 the operations, the Allocadence customer orders 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