SellerbridgeSB-01 / NIGHT SHIFT
Decision Audit
[ back to dispatches ]
04 Sept 2026The Bridge desk6 min read

What a night shift actually looks like

The interesting thing about an unattended shift is not that software ran overnight. Cron has done that for forty years. It is that at 08:00 there is a short list of decisions with money attached, instead of a dashboard you still have to interpret.

Here is a real shape of one, from a 412-ASIN home and kitchen account. Ten entries between 22:00 and 08:00, spread across the seven agents on the roster. Zero alerts sent. One escalation.

The first four hours are inventory and waste

22:14
Supply
Order by Friday or you stock out Nov 3 — and the rank you lose takes six weeks to rebuild.

Velocity was up 18% week over week. That alone is not a decision — it could be a returns spike inflating sell-through. Supply checked returns first, found them flat at 3.1%, then read inbound shipments and lead time from the last three POs before putting a date on it. The date is the decision. The velocity is just the reason.

23:02
Spend
18% of last month's spend went to ad groups with zero attributed sales. Move it here.

The obvious objection to this one is attribution lag, and it is the right objection. Spend ruled it out because the window closed fourteen days earlier. An ads tool that reports the number without ruling out the lag is handing you homework, not a decision.

The middle of the night is where the money is

03:42
Margin
Stop advertising B0FK9RT2L — after the Aug fee tier it loses money on every unit you sell.

Contribution per unit went negative after a size-tier change. Not a fee correction that would reverse — a permanent tier move. The campaign pause was staged and costed, then left for a human, because this account runs in Recommend. What each permission mode does overnight is worth settling before you switch anything on.

This is the entry that pays for the shift. Advertising a product that loses $0.87 a unit is the kind of mistake that survives for weeks precisely because every individual dashboard looks fine: spend is on plan, ACOS is acceptable, the listing is healthy. Only contribution after fees tells you it is wrong, and nobody checks contribution after fees at 03:42. The same failure, followed through a whole agency for five weeks, is written up in the fee tier that turned six SKUs negative.

One event, not three alerts

06:20
The Bridge
One decision assembled from four agents: hold the bid, defend the price, listing is clean, floor recomputed.

At 02:40 a competitor cut price 12%. Margin recomputed the break-even ACOS at the new competitive price. Spend proposed holding the bid rather than matching, because matching would spend $1,900 to defend $340. Health confirmed the listing was clean, so the share loss was price and not suppression.

Four findings. One event. The work is deciding they describe the same thing, and then sending one decision rather than four notifications that each look urgent on their own. The hand-off that assembles them is drawn step by step on its own page, and three accounts it has run on are in the case files.

Account data in this piece is illustrative and anonymised.

Read one of these on your accountStart a Decision Audit
What this piece is about

Read next

The other two dispatches, picked for subject rather than for date.

Connect one account, read-only. See seven days of what the agents would have caught.

That is the Decision Audit. No configuration, no write access, no call required to start.

Manifest — what lands in your inbox
01Every decision the seven agents would have surfaced, timestamped.
02The money attached to the ones you missed.
03The reasoning chain for each, so you can check our work.
04A read-only audit log of everything we touched.