Marketplace agency access looks like admin work until the wrong permission blocks a commercial decision. Then it becomes expensive very quickly.
A client invites the agency to Amazon Ads as a viewer, but expects campaigns rebuilt before Monday. Seller Central access includes orders and reports, but not listing edits, so a suppressed ASIN waits three days for someone client-side to fix a missing attribute. Walmart Connect reporting arrives, but the agency cannot see inventory or item health, so budget keeps flowing to a SKU with nine days of stock left. Everyone is “connected”. Nobody is actually able to protect profit.
The named mistake I see is treating access as an onboarding checkbox instead of a live operating risk. Agencies ask for logins at the start, screenshot that access was granted, and move on. Six weeks later a new account manager joins, an old freelancer still has editor rights, an SP-API authorization expires, a client adds Germany to the scope, and the reporting dashboard quietly loses the data needed to explain why margin changed.
My stance: marketplace agencies need an access ledger. Not a password sheet. A profit-aware record of who can see, change, approve and export which marketplace data, for which client, channel, SKU group and decision type. If your agency software stack cannot answer that in under two minutes, the team is running on trust, memory and luck. Lovely people. Weak control system.
This guide is for marketplace agencies in Germany, the US and other mature ecommerce markets managing clients with five or more employees. If your team works across Amazon, Walmart, bol.com, Kaufland, Target, Mirakl retailers, TikTok Shop, retail media, Shopify or ERP data, access control is part of client profitability.
What current marketplace agency software advice gets right
The best existing content is useful. MerchantSpring talks about portfolio oversight, separate client worlds, restricted external access, scheduled reporting and one source of truth across sales, advertising, profit and operations. Pacvue makes a strong case for unified retail media execution: standardized workflows, cross-retailer reporting, automation, benchmarks and client-facing transparency. Productsup focuses on multi-client feed management, proactive error monitoring, channel coverage and product data for AI discovery. ChannelEngine explains the operational breadth: product content, inventory, pricing, promotions, order handling, Buy Box work and ERP or WMS integration.
Amazon’s own documentation adds the technical reality. Seller Central permissions, Amazon Ads roles, Login with Amazon authorization, SP-API application permissions, restricted data tokens and the newer Solution Provider Portal all shape what an agency can actually do. Access is not one button. It is a stack of roles, authorizations and responsibilities.
What most advice misses is the operating link between permissions and commercial exposure. Competitor pages often say “grant role-based permissions”, “manage multiple clients” or “keep client data separate”. Good. But the harder agency question is this: which missing or excessive permission is putting margin, stock, ad spend, reporting trust or agency scope at risk this week?
The access ledger: one table that connects permissions to decisions
An access ledger is simple, but it has a serious job. For every client and marketplace, it should show the platform, access method, role, owner, decision rights, commercial dependency and review date. Platform means Amazon Seller Central, Amazon Ads, Vendor Central, Walmart Seller Center, Walmart Connect, bol.com, Kaufland, Mirakl, TikTok Shop, Shopify, ERP, WMS or finance. Access method means named user, manager account, API authorization, feed connection, SFTP, scheduled export or client dashboard. Commercial dependency means ad spend, listing health, Buy Box, inventory, pricing, returns, settlement, margin or client reporting.
The goal is not bureaucracy. The goal is faster commercial action with fewer surprises. When a strategist spots wasted spend, the ledger should show whether they can pause it, who approves the change if they cannot, and whether the client’s scope allows the agency to act. When a report looks wrong, the ledger should show whether the dashboard lost access to fees, returns or settlement data. When a team member leaves, the ledger should show every client system where access must be removed.
FiveX fits naturally here because marketplace agencies do not need another static access spreadsheet. They need connected context. FiveX can bring advertising, product profitability, inventory signals and marketplace performance into one operating view, so permissions are not judged in isolation. The question becomes: “Do we have the access required to protect this client’s profit today?”
Scenario 1: viewer access creates five days of invisible margin leakage
Imagine a German marketplace agency onboarding a sports accessories brand called RheinFit. The client sells 140 SKUs across Amazon.de, Kaufland and Shopify. The first sprint is meant to clean up Amazon Sponsored Products and fix low-margin hero ASINs. Monthly marketplace ad spend is €18,000.
On day one, the client grants Amazon Ads viewer access and Seller Central reporting access. Dashboards populate, so it feels good enough. But the agency cannot edit campaigns, add negative keywords, change budgets or fix a listing suppression. The team spots the issue quickly: a generic campaign is spending on a resistance band set with a €34 selling price and only €7.10 contribution margin before ads. It generated 320 orders in the last 30 days and spent €1,850.
On paper, that SKU still has €422 of contribution left after ads. But the campaign is drifting toward the edge. Two broad terms consume 38% of spend with weak conversion. The agency recommends pausing those terms and lowering the daily budget from €95 to €55 until margin recovers. Because access is view-only, the recommendation waits. The client’s ecommerce manager is travelling. Finance wants to check the SKU costs. Five days pass.
The bigger leak is not only the extra spend. During the same week, one variant gets suppressed because a required attribute is missing after a category update. Average daily sales were 58 units, contribution margin was €6.40 per unit, and the listing is effectively down for five days. That is €1,856 of contribution margin at risk before lost rank, retail media waste and account-manager time.
The operator lesson: access should match the first 30-day action plan. If the agency is responsible for campaign cleanup, it needs ads editor rights before the sprint starts. If it is responsible for listing recovery, it needs the exact Seller Central catalog permissions required to edit the affected fields. If the client will not grant edit rights, the SOW should define a maximum approval window and a named client operator who executes agency-approved changes.
Scenario 2: excessive access turns a staffing change into spend risk
Now take a US agency managing twelve Amazon and Walmart clients in the home category. The team has grown from six to fourteen people in a year. Access was granted client by client, often under deadline pressure. One senior strategist left. Two freelancers helped during Prime Day. A junior account manager inherited three accounts. Nobody did anything malicious. That is usually how permission drift happens.
During a promotion week, the junior account manager has admin-level access in three Amazon Ads accounts because a client originally clicked the fastest approval option. She raises daily budgets to keep campaigns from capping out. The intention is good. The problem is that two accounts had margin guardrails requiring approval before increasing spend on products below 22% contribution margin. Across the portfolio, only €260 of extra spend per client is needed to create €3,120 of unplanned media exposure in one week.
The agency then has an awkward client conversation. The client is not angry because the team touched the account. The client is angry because the agency cannot prove whether the change respected the agreed commercial rules. A permission problem has become a trust problem.
An access ledger solves this by separating ability from authority. Someone may technically be able to edit budgets, but the ledger should show whether they are commercially authorised to do so. FiveX’s automation and recommendation layer can support this model by tying budget actions to SKU margin, stock cover, campaign role and approval thresholds. The software should not only ask, “Can this person click the button?” It should ask, “Does this change have profit permission?”
The five access zones every marketplace agency should map
1. Advertising access
Advertising access covers Amazon Ads, Walmart Connect, bol Sponsored Products, Mirakl retail media, TikTok Shop Ads, Google Shopping and Meta where social demand affects marketplace sales. Viewer access is enough for audit work. Editor access is needed for bid, budget, negative keyword and campaign-structure changes. Admin or billing access should be rare and named. The ledger should connect each permission to campaign roles, because brand defence, discovery, clearance and launch campaigns do not deserve the same approval rules.
2. Catalog and content access
Catalog access controls titles, bullets, images, A+ content, attributes, variation structure and marketplace-specific fields. This is where agencies often under-scope the work. The advertising team is blamed for poor conversion, while the agency cannot fix the content problem that caused it. If the agency can recommend but not edit, the ledger should record the SLA. “Client to update when possible” is not a control. It is a future excuse with a polite hat on.
3. Inventory and fulfilment access
Inventory access changes how aggressively the agency should advertise, price and promote. If a team can see ad performance but not stock cover, it can accidentally accelerate a SKU into a stockout. FiveX’s inventory insights help by placing stock context next to marketplace and advertising performance, so agencies can route exceptions before ads scale into seven days of cover.
4. Finance, settlement and profitability access
Revenue, ad spend and orders are not enough. Agencies need enough access to understand referral fees, fulfilment fees, returns, discounts, marketplace commissions, settlement timing and contribution margin. FiveX’s profitability dashboards and margin analysis give agencies a safer way to work with commercial truth without spreading sensitive finance files across every client pod.
5. API, integration and AI-agent access
API access is where “we connected the account” can hide the most risk. SP-API authorizations, restricted report access, feed integrations, OAuth connections, scheduled exports and AI-agent permissions can break quietly. For every integration, record the application, data scopes, client authorizer, refresh date, last successful sync, failure owner and offboarding rule.
A monthly permission review that takes 45 minutes, not a whole day
The access ledger only works if it stays alive. I like a monthly review with three passes. First, remove stale access: leavers, freelancers, old client stakeholders, unused API apps and duplicated admin roles. If someone does not need access for this month’s decisions, remove it or downgrade it. Least privilege sounds boring until it saves a client relationship.
Second, find blocked decisions. Ask each account lead which recommendations waited last month because the team lacked permission, data or a named approver. If the same gap appears twice, it is not an inconvenience. It is a process defect.
Third, connect permissions to profit rules. Review the decisions that carry money risk: budget increases, bid automation, repricing, promotions, stock allocation, listing changes on hero SKUs and reporting sign-off. Make sure the person who can act is also allowed to act under the client’s margin, stock and scope rules.
For an 18-client agency with seven core access zones per client, even a six-minute check per zone is 12.6 hours if done manually from scratch. That is why the ledger should live inside or beside the agency’s marketplace software, not as a heroic spreadsheet ritual. The more FiveX can centralise client performance, margin, stock and recommendation context, the less time the team spends asking where the missing permission sits.
The access clauses your SOW should include
Your statement of work should make the ledger enforceable. Include the platforms, marketplaces and countries in scope; the exact access level required for each service line; the client owner responsible for granting and renewing access; the maximum turnaround time for client-executed changes; the actions the agency may take without additional approval; the profit, stock or spend thresholds that require approval; the offboarding process for users, apps, exports and dashboards; and data ownership rules for reports, keyword research, campaign history, product content and performance commentary.
This protects both sides. The client knows the agency cannot wander through sensitive systems without purpose. The agency knows it will not be held responsible for outcomes it was not allowed to influence. Commercially, that is the grown-up version of “please send access”.
How to implement it this week
Start with your five highest-value clients. For each one, list every platform where the agency reads or changes marketplace data. Mark each permission green, yellow or red. Green means access matches scope and decision rights. Yellow means access works today but has unclear ownership, excessive rights or missing review dates. Red means access blocks an agreed service, exposes client data unnecessarily or allows actions outside commercial authority.
Then attach one commercial consequence to every red item. “Cannot edit Amazon Ads” is an admin issue. “Cannot reduce €95/day spend on a low-margin campaign without waiting for the client” is a profit issue. That wording changes behaviour.
Finally, connect the ledger to your weekly rhythm. In the Monday portfolio review, ask which clients have blocked decisions. In the Friday wrap, remove access that is no longer needed. In QBRs, show clients how clean access control helped protect margin, speed and accountability. That is much more valuable than bragging about another dashboard.
Final thought: permissions are part of performance
Marketplace agencies like to talk about strategy, retail media expertise, automation and reporting quality. Good. But none of that works reliably if the agency cannot see the right data, change the right settings, or prove that the right person had authority to act.
An access ledger is not glamorous. It will not win a pitch on its own. But it quietly makes everything else more professional: faster onboarding, cleaner reporting, safer automation, better scope control, stronger offboarding and fewer “who still has access?” moments at exactly the wrong time.
FiveX helps agencies move this from admin memory to operating system. By connecting marketplace analytics, profitability dashboards, advertising automation, inventory insights and AI recommendations, FiveX gives the team the context to decide which permissions matter commercially. Not access for access’ sake. Access that protects client profit.