C
ClickPay
Jump to product, campaign, PO, or run a command ⌘K
● ops 14m ● ppc 2h ● api ok 3 approvals
JL
AI & System
Agents AI Assistant Listing Agent Ops Hub
Scheduler
Database
Integrations
Audit log
Health
Data Freshness Ops Health
Settings
Users Notifications
Writes and gates
Feedback
Requests
Build order
Saved views
Costs over 1 h/week 4
Defects, not requests 3
Waiting on data 2
Closed without building 3
m merge   o order   r reply to whoever asked
Build order
34 requests open · the top five cost 7.9 people-hours a week · 3 are defects, not features
Export
Reply to everyone waiting
Requests 34
Build order 5
Shipped 12
Declined 6
open
costs over 1 h/week
+ filter
Save as view
Make a rule
ranked by hours a week — not by who asked, and not by who asked last
What people asked for
What it costs them
The plan
What was asked for Asked by Times Costs them Kind Size Waiting on Order State
● “Let me keep the filter I retype every morning” Mei, Isaac, Priya 12 3.5 h/wk request S nothing 1 building
● “Restock takes eight seconds to open” everyone 22 1.5 h/wk defect M nothing 2 building
● “Tell me the moment a listing goes inactive” Priya 6 0.6 h/wk request S nothing 3 next up
● “Stop making me open GoFlow to find a ready date” Mei 8 2.0 h/wk request M ready dates at PO time 4 next up
● “Let me undo a bid change” Isaac 4 0.3 h/wk request M nothing 5 next up
Twelve people asking in twelve different sentences is one request. Requests arrive as sentences rather than as tickets, so they are merged first and the count becomes a ranking input instead of the loudest voice. And the ranking number is hours a week, not enthusiasm: three people retyping the same filter every morning is three and a half hours, most of a working day every week, and it outranks a feature four people said they would like.
● “One packing list per supplier, not per container” Andres, Mei 7 1.2 h/wk request M nothing — shipped Aug 18
● “Show me Temu shipping cost per unit” Joseph 3 — request S the feed writing zeros — blocked
Two rows are waiting on data, not on anybody’s time. The Temu request cannot be built at all while the shipping feed writes 0.00, and the ready-date request is only worth building once ready dates are required at purchase-order time. Both fixes are small and upstream and neither is a screen — but unnamed here, both requests simply look ignored.
● “The tables are too cramped to read” Andres 2 — a setting S nothing — answered
● “Why doesn’t this match Sellerboard?” Dana 5 2.0 h/wk question — nothing — answered
● “Bring back the old dashboard” Andres 1 — request — nothing — declined
Three were closed without building anything, and that only works if the person who asked is told. The cramped tables became a density setting rather than a redesign; the Sellerboard question is answered by a board that already exists, so the reply is a link; the old dashboard was declined with a reason attached rather than left to rot in a list. Feedback that disappears quietly stops arriving within about a month, and a queue people can see is the whole reason the next twelve requests get filed.
34 open · 5 scheduled · 2 waiting on data rather than on time · 3 closed without building anything · every row has a state its author can see
a queue nobody can see is a queue people stop adding to
Brief
ClickPay against SellerboardBrief Command CenterBrief Daily BriefBrief Getting startedBrief Profit and lossBrief Where a number comes fromBrief
Advertising
Ad GroupsAdvertising Advertising — launchesAdvertising After you press the buttonAdvertising Ask the tableAdvertising AudiencesAdvertising Bulk selectionAdvertising CampaignsAdvertising ClickPay SuggestsAdvertising Empty statesAdvertising Filter builderAdvertising HourlyAdvertising Loading statesAdvertising PlacementsAdvertising Search TermsAdvertising ShapesAdvertising StrategiesAdvertising Targets › KeywordsAdvertising Why did this move?Advertising Window pickerAdvertising
Inventory
AI listing rewriteInventory Container planInventory Container plan — mid-dragInventory Listing editor + keyword optimiserInventory Listings — changesInventory Listings — competitorsInventory Listings — variation familiesInventory MarketplacesInventory Marketplaces — profit by productInventory Marketplaces › ListingsInventory Marketplaces › ProductsInventory Marketplaces › RestockInventory Marketplaces › Search TermsInventory Marketplaces › SQPInventory Marketplaces › Temu PricesInventory One purchase orderInventory Orders — returnsInventory Orders › FBA ShipmentsInventory Orders › PaymentsInventory Orders › ShipmentsInventory Orders › TimelineInventory Orders › Timeline, groupedInventory Payments — the next 13 weeksInventory Product › KeywordsInventory Product detailInventory Purchasing coverageInventory Receiving a containerInventory Restock — where the stock isInventory Restock at 1280Inventory Restock, a line openedInventory Search catalog performanceInventory Shell + command paletteInventory SuppliersInventory Suppliers — purchase ordersInventory
Automations
ApprovalsAutomations Automation draftsAutomations Automations › RunsAutomations Failure statesAutomations RulesAutomations Save a view, or make a ruleAutomations TagsAutomations WorkflowsAutomations
AI & System
AI AssistantAI & System AI layer › AgentsAI & System Asking for somethingAI & System Audit logAI & System Data freshnessAI & System Feedback, turned into a build orderAI & System Listing agentAI & System NotificationsAI & System Ops healthAI & System Settings v6AI & System System › Ops HubAI & System Users and what they can spendAI & System Writes and gatesAI & System
Reference
Console systemReference Every tab and sub-tabReference Packing list — as it printsReference Phone layoutsReference Width rulesReference