The frame
There is no clever insight in this post. There is a list. Five things every day. Six things every week. Four things every month - and the cadence of each one flexes with team size, account size, the season you are in, and whether the account is running active promos or lightning deals. The list is what keeps an account from drifting. It is what separates accounts that compound from accounts that quietly leak.
After eight years across the US, Canada, UK, UAE and KSA, the pattern is the same. The accounts that work have an operating system. The accounts that struggle have heroes. Heroes burn out. Operating systems compound - quietly, on the cadence the account actually needs, not on a generic Monday morning.
What follows is the actual OS I run. Steal it. Adapt it to your catalogue. The point is to have one written down, in one place, that anyone competent on the team can pick up on a Tuesday morning when you are sick.
Daily: five things, twenty to thirty minutes
The daily list is short on purpose. If your daily list takes more than thirty minutes, you have built a daily list that includes things that should be weekly. The point of daily is to catch the small number of things that move in 24 hours.
One: stockout and inventory health. Pull the FBA inventory dashboard and look at any SKU showing less than 30 to 45 days of forward cover (the floor depends on supplier lead time and FBA inbound speed; faster categories sit at 30, slower ones at 45). For cash-constrained brands, the floor compresses to 14 to 21 days - the tradeoff is working capital vs stockout risk, and at smaller scale the cash side often wins. Stockout risk is one of the biggest revenue leaks on an Amazon account because the punishment is not just the lost sales. It is the lost organic rank, which takes weeks to rebuild. Catching a stockout at 14 days forward cover gives you time to expedite. Catching it at 5 days forward cover is too late.
Two: campaign and portfolio budget pacing. Any campaign - or any portfolio - that hit its daily budget cap before 6pm yesterday gets flagged. Campaigns hitting cap are leaving impressions on the table. Either the budget needs to go up or the bid strategy needs to change. The campaigns to leave alone are the ones spending against budget consistently throughout the day. The ones to fix are the ones flat-lining at noon.
Three: Buy Box health on the top 20 SKUs. A list of the 20 highest-revenue SKUs and a one-glance check on Buy Box ownership percentage. Anything below 95% on a brand-owned SKU is a hijack signal, a pricing rule mistake, or a competitor undercutting. Most days nothing has changed. Some days you catch a hijacker in the first hour of the workday.
Four: ad-attributed orders pace. A 7-day rolling pace number for ad-attributed orders, compared to the prior 7 days. Not the dollar number. The orders number, which is less noisy. If orders pace is down 10% week over week, something has changed. Maybe seasonal. Maybe a competitor's launch. Maybe a price change in your own catalogue that you forgot was scheduled. The signal triggers a deeper look in the weekly review.
Five: returns rate spike check on hero SKUs. A 7-day returns rate on the top 20 SKUs against the prior 30-day baseline. A returns rate jump of 2 points or more on a hero SKU is a leading indicator of a product-side problem (manufacturing batch issue, new packaging error) or a listing-side problem (image creating wrong expectations, recently changed copy). Returns spikes that go uncaught for two weeks become permanent listing rating drops, which are far harder to undo than the underlying issue itself.
That is the whole daily list. Twenty to thirty minutes if you have the dashboards built. Forty to fifty minutes if you are still building them. The point is to do it every working day, not to do it perfectly.
Weekly: six things, two hours
The weekly review is where the actual operating work happens. The daily list catches fires. The weekly list does the architecture.
One: TACoS by SKU bucket. Pull TACoS by SKU bucket against your CM1-derived ceilings. Any bucket that drifted more than 2 points from the prior week goes on a watch list with a one-line note explaining why. If the why is unclear, the bucket carries forward to next week. Two weeks on the watch list means an intervention is overdue. The rule is simple: drift triggers diagnosis, not bid changes.
Two: search term report review on top spending campaigns. Pull the search terms report from the previous seven days, filtered to the top ten campaigns by spend. The negation threshold is anchored to the product CVR, not a fixed dollar amount. The math: if product CVR is ~10%, expect ~10 clicks per sale; halve that to 5% as a benefit-of-the-doubt floor, which implies ~20 clicks per expected order.
Negation threshold, CVR-anchored: Clicks-to-negate ≈ 2 ÷ product CVR · pass that with 0 sales -> negate
Any non-converting search term that passes the threshold becomes a negative. Any search term that converted at 2x the campaign average gets promoted from auto or broad into a tighter exact-match campaign. For products with very low CVR (under 3%), the formula generates a 70+ click threshold that some operators will not have the patience or budget to wait for - in those cases the threshold compresses to a clicks-per-spend cutoff (e.g., negate after $20-30 of spend with zero sales).
Three: bid review on under-performing keywords. Filter to keywords with at least 1,000 impressions and ACoS more than 1.5x the SKU bucket target. Drop bids by 5-20%, sized to how far over target the ACoS sits, judged on a 7 to 14 day window. Then filter to keywords with high impression share, strong conversion rate, and ACoS at or below the bucket target. Increase bids by 5-10%, sized to how far under target the ACoS sits, judged on a 30 to 60 day window.
Exception worth flagging: low impression share with high ACoS is sometimes a "raise bid to test higher placement" candidate, not an automatic bid-down. Position improvements compound differently from bid efficiency wins. Use judgment.
Four: organic rank check on hero SKUs. Use Helium 10 or Jungle Scout to pull organic rank for the top search terms tied to each hero SKU. Page 1 is healthy. Anything sliding to Page 2 or beyond gets investigated - usually a listing issue, a recent stockout, or a Buy Box loss.
Five: review listings flagged for content changes. Pull the listings where the prior week showed conversion rate drops, search visibility drops, or buyer-side review issues. Schedule the listing copy and image updates for the SEO team. This is the bridge between the ads function and the listings function, and the brands that do not run it weekly end up with stale listings dragging down ad efficiency.
Six: promotions and coupon calendar look-ahead. Look at the next 14 days. What coupons are running? What deals are scheduled? What seasonal moments are coming? Every promotional event has implications for ad spend, stock, and pricing. The brands that get caught flat-footed on Prime Day or Black Friday are the brands that did not run this look-ahead every week for the prior two months.
Monthly: four things, half a day
The monthly review is where you do the work that does not fit in a week. The pattern is similar across the four checks: zoom out, audit, plan, document.
One: full TACoS and CM1 reconciliation. Pull the actual month's revenue, ad spend and CM1 with finance. Compare to plan. Compare to the prior three months. Identify any SKU buckets where CM1 has drifted from the assumed number, because CM1 changes when COGS changes, when fee structures change, when freight contracts change, and when return rates shift. If CM1 has moved more than 2 points on a SKU bucket, the TACoS ceiling for that bucket needs to be updated. Do this every month or your operating ceiling is stale by 6-8 points by the end of the year.
Two: campaign structure audit. Once a month, walk through the campaign structure for at least two SKU buckets and ask whether the architecture is still right. Are there campaigns that overlap? Are there negative keyword exclusions that need to be added at the campaign or ad group level to stop campaigns from competing with each other? Are there auto campaigns that should have graduated to broad, or broad campaigns that should have graduated to exact? Most accounts I inherit have campaigns that were right at launch and have not been touched since. Architecture rots.
Three: listing quality audit on 20% of the catalogue. Cycle through the catalogue so that every SKU's listing is audited at least once every five months. Check title, bullets, A+ Content, images, backend search terms, and the keyword density in the listing copy against the actual search terms that are converting. Listings that were great twelve months ago are probably no longer current with how buyers are searching. This is where the SEO and ads functions overlap, and the brands that get this right keep their conversion rates up and their ad spend down.
Four: competitive landscape scan. Pick the top three competitor brands in each of your SKU buckets and look at what has changed. New SKUs launched. Price changes. Listing changes. Promotional patterns. Sponsored Brands video creative changes. The point is not to copy. The point is to know what the surface of your category looks like, so when something on your own account shifts, you have context for why.
Each of these monthly items takes ninety minutes to two hours done properly. Half a day total. Once a month. Most accounts I diagnose have skipped at least two of these for six months running, which is why their TACoS has drifted and their conversion rates have softened.
How the OS flexes
The standard cadence above works for a steady-state, single-market, mid-sized account run by a single operator. Real accounts vary, and the OS has to flex.
By stage
- Early-stage / pre-PMF brands. Hero mode is the right OS temporarily. Trying to install a full ritual structure before you know which SKU is winning wastes time on tracking the wrong things. Run a stripped daily list (stockout + budget pacing only), skip the weekly architecture work until you have stable SKUs, and revisit installing the full OS at roughly $500K annual revenue.
- Growth-stage ($500K to $5M annual). The standard OS as written. Single operator, daily 25-30 min, weekly 2 hours, monthly half-day. This is the regime where ritual discipline pays off the most because architecture mistakes compound quickly.
- Mature ($5M to $25M annual). Daily and weekly cadence the same, but the operator increasingly delegates report-pulling to a junior analyst or an MIS function. The senior operator becomes the diagnostic layer, not the data-pulling layer. Monthly review expands to include a strategic layer beyond the four items above.
- $25M+ annual. Multiple operators, the OS becomes a team protocol with explicit role assignments. Daily list often splits across category specialists. Monthly review becomes a leadership review.
By marketplace count
Single-market accounts run the standard OS as written. Multi-marketplace accounts (brands in 3+ markets) need a different shape:
- Daily list runs per market by the operator owning that market, but with a consolidated cross-market dashboard the lead reviews twice a week instead of daily
- Weekly review keeps the per-market depth but adds a cross-market consolidation step (which market is driving group performance, which is dragging)
- Monthly review runs at the group level with per-market call-outs
Trying to run a 5-market account with a single operator on the standard cadence ends in dropped balls. Either staff for it or accept that some rituals will be quarterly rather than monthly.
By season
Peak weeks (Prime Day, Black Friday / Cyber Monday, Eid, Diwali, category-specific peaks) compress the cadence:
- Daily list expands to twice daily during the peak event itself - one morning check on stock + budget + buy box, one afternoon check on pace
- Weekly cadence suspends in favour of daily fire-fighting during the peak event week. Resume the full weekly cadence the week after.
- Promotional calendar look-ahead extends from 14 days to 60-90 days starting two months before the peak
Off-peak weeks run the standard cadence. The point is the OS is a baseline, not a rigid rule - it bends around the actual operating reality.
How to actually install this
Most teams who read a playbook like this nod, agree, and never install it. The reason is that the installation work is unglamorous. Three steps.
Step one: build the dashboards. The daily list needs five dashboards: FBA inventory health, campaign budget pacing, Buy Box ownership on top 20 SKUs, ad-attributed orders pace, and returns rate on hero SKUs. The weekly list needs five more: TACoS by SKU bucket, search terms report with spend and conversion filters, bid optimisation queue, organic rank tracker, and a listings health watchlist. The monthly list is mostly manual pulls plus a finance reconciliation. Spend a week setting up the dashboards. After that, the OS runs on near-zero overhead.
Step two: get the cadence on the calendar. Daily check is twenty to thirty minutes blocked out at the same time every working day. Weekly check is a two-hour block on Monday morning. Monthly check is a half-day block in the first week of every calendar month. If it is not on the calendar, it does not happen. Trust the cadence over willpower.
Step three: write down the diagnosis rules. When TACoS drifts, what is the decision tree? When organic rank slips, what is the response? When a hijacker shows up on the Buy Box, what is the playbook? Documenting the response saves you the cognitive cost of re-figuring it out every time. It also means the next person who runs this account does not have to learn it the hard way.
Diagnosis rule starter template
A working decision tree looks like this. Adapt to your account.
TRIGGER: TACoS on a SKU bucket drifted +2 points in one week
CHECK:
1. Did ad spend rise or did sales fall? (look at numerator + denominator)
2. Did organic share change? (TACoS = ads spend / total revenue)
3. Did a price change or coupon get applied this week?
4. Did any campaign budget cap recently lift?
RESPONSE:
- If spend rose: review bid changes from prior week, roll back any that look too aggressive
- If sales fell: check listing health, Buy Box, stock, returns spike
- If organic share dropped: trigger listing audit
- If price/promo change: confirm intended, log impact, no fix needed
ESCALATE:
- Two weeks on watch list -> deeper diagnostic outside the weekly cadence
That structure works for any trigger. Write one of these for each of the top five triggers your account actually sees. Five trees, written down, in a shared doc. That is the install.
I have installed versions of this on accounts across four of the five markets I have worked. The beauty brand expansion on Noon and Amazon UAE leaned heavily on this kind of operational rhythm to go from 1,500 to 25,000 AED per month while holding TACoS in a 20-25% band.
What this OS prevents
Three categories of problem.
Drift. Accounts get worse a quarter of a point at a time. Nobody notices a quarter point. By the time someone notices a four-point drift, the cause is months old and the fix is expensive. The weekly TACoS check catches drift at one to two points, which is fixable in a week.
Surprises. Stockouts, hijackers, competitor launches, fee changes. None of these are preventable. All of them are catchable within 24 to 48 hours if the daily list is running. Most accounts find out about them three weeks late, when the damage is permanent.
Hero dependence. If the account runs on one person's intuition, the day that person leaves or burns out is the day the account starts losing money. An operating system is the thing that survives turnover. I want the work to be reproducible by anyone competent who reads the playbook. That is the test.
When this is the wrong move
Be honest about where the OS does not pay off:
- Brands in pre-PMF phase - installing the full ritual structure before you know which product is winning is process for the sake of process. Run hero mode until you have stable winners.
- Single-SKU launches - the standard OS is overkill for a one-SKU brand in launch phase. Strip it to stockout + budget + buy box and revisit at $100K monthly.
- Accounts with zero discretionary spend - if the brand has no ad budget to manage, the weekly bid review and search term work has no leverage. The OS becomes inventory and listing only.
- Active fire-fighting - if the account is in genuine crisis (suspension, brand attack, supply chain failure), the rituals suspend until the fire is out. Trying to maintain ritual cadence while fire-fighting just spreads the team thinner.
The OS is a discipline for steady-state operating, not for the moments when the account needs all hands on one problem.
Bottom line - the unglamorous habit that compounds
Daily list: five checks, twenty to thirty minutes. Weekly list: six items, two hours. Monthly list: four reviews, half a day. Write the list down. Put it in a shared doc. Run it every week without exceptions outside peak weeks and active fire-fighting. The account that runs this discipline beats the account that does not, every time, in every market.
If you want a written read on whether your account is running this kind of operating cadence, the Amazon Account Audit reviews it directly. If you want a senior pair of eyes on what your in-house team or agency ships each week, the Strategic Advisor Retainer covers that cadence. Or ping me on WhatsApp for a quick second opinion.
Frequently asked questions
What is an Amazon account operating system?
An Amazon account operating system is the written set of daily, weekly and monthly rituals that govern how the account is managed - what gets checked, when, by whom, and what triggers an intervention. It replaces ad-hoc heroics with a repeatable cadence that any operator on the team can run.
How much time per week should an Amazon ads operator spend on routine work?
Twenty to thirty minutes a day on the routine checks above, plus a two-hour weekly review and a half-day monthly review. The cadence flexes with team size, account size, season and promo state. On most brands at meaningful scale, an MIS analyst or junior operator runs the data-pulling part and the senior operator becomes the diagnostic layer rather than the data layer.
What goes wrong when an Amazon account has no operating cadence?
When there is no operating cadence, problems get caught late and fixed expensively. Inventory drifts. Negative keyword work falls behind. ACoS spikes go unnoticed for two weeks. Returns spikes go untreated until they damage the listing rating permanently. Quarterly resets become emergency rebuilds. The cadence catches the small drifts before they become structural problems.
Should the OS look the same on a brand new launch as on a mature account?
No. Pre-PMF brands and single-SKU launches should run a stripped daily list (stockout, budget, buy box) and skip the weekly architecture work until they have stable winners. The full OS pays off most clearly in the $500K to $25M annual revenue range. Above that, the OS becomes a team protocol rather than a single-operator ritual.