Amazon operations
Catalog, ads, and the weekly Amazon cadence. You keep the vendor relationship and the ad account.
01 - The situation
Seller, Vendor, Ads, or marketplace ops need doing. Catalog drifts. Pricing lives in a spreadsheet. Ads and listing health do not share a week. A new market re-asks the same questions from scratch. A media-agency pitch is not this job.
02 - How it runs
Name Seller, Vendor, Ads, or marketplace ops — and what is stuck.
I run catalog, pricing, advertising, and the weekly cadence.
You keep the vendor relationship and the ad account.
If a number is used, it is already public and attributed to the role that produced it.
03 - Already running
Catalog QA that diffs live listings against a golden record and queues fixes for approval.
Daily repricing with margin floors computed from fees, fulfillment, and FX.
A health score per listing so suppressions are caught on the way down, not after sales dip.
The cross-border launch motion for a US-native catalog into UK and SA marketplaces.
04 - Related work
Autonomous Catalog Agent
Agentic system that monitors marketplace listings, detects content drift, and pushes corrected copy and imagery back through Amazon SP-API. Compresses catalog QA from days to minutes.
Repricing Engine
Daily competitive repricer across thousands of SKUs with rule-based guardrails. Tracks margin floor, buy-box position, and competitor velocity to keep pricing honest without eroding profit.
05 - What you leave with
Catalog, pricing, advertising, and the weekly cadence running. You keep the vendor relationship and the ad account.
06 - What this is not
An unnamed client story.
A media-agency pitch.
The studio’s lead identity.
A case sold as an offer.
If this is the wrong door, I will say so.
If it still fits after the work, start a conversation. Say what you sell, which channels you are on, and what is stuck.