The twelve orders that need a person today, found by 08:30

Why is a price write different from a CRM write?

Because somebody can pay it thirty seconds later.

WordPress has revisions for posts; a product price change through the API does not queue anywhere or wait for review. If a decimal point moves, the next order is placed at the wrong price.

So the sensible arrangement is a proposal step. A companion reads the supplier list, matches SKUs, and produces a table of proposed changes with old and new values side by side. You approve the write. Automating inventory price updates covers the pattern in more detail.

What is worth reading every morning?

Orders in a state that needs a human.

On hold, failed, pending payment for longer than an hour: each is a customer who thinks they bought something and a payment that did not complete. Woo shows them if you filter, and nobody filters at 08:30.

Then stock. Products below threshold, products at zero that are still purchasable because backorders got left on, variations where one size is out and the parent still says in stock. The Available tools list on the WooCommerce entry under `strawberry://settings/integrations` names every tool the connection exposes and marks the read-only ones.

• Orders on hold, failed or pending payment: the list that needs a person today.
• Stock below threshold, and variations that disagree with their parent.
• Price and stock writes: live immediately, so propose first and approve deliberately.
• A REST API key with read permission unless a specific task needs write.

The rest of the store lives in four other tabs

A store is Woo plus a payment provider plus a shipping tool plus an email platform plus whatever the supplier uses. An order question routinely spans three of them. A companion reads the Woo order, checks the payment status where the payment lives, sees whether a label was created, and writes the reply.

The recurring version is a daily pass over exceptions rather than a dashboard. Tracking shipment and order status is the neighbouring page, and ai for ecommerce managers covers who ends up owning it.

Frequently asked questions