Agencies: Running Prep for Ten Clients Without Ten Logins

By Bernardo Campelo, Forbes Business Council E-Commerce Leader, Amazon SPN Certified provider, Amazon SP-API authorized partner, and Founder of PrepVia.

An account manager at a ten-client Amazon agency described her Monday routine to me. She opens ten tabs. Each tab is a different portal, because three of her clients use one prep center, four use another, and the rest never quite settled on one. She checks a receiving count in one tab, chases a label question in another, and waits for an invoice that always seems to land on a different day of the month depending on which client it belongs to. By the time she has answered the first client of the morning, four more have already emailed her.

If that sounds like your Monday, the problem is not your clients. It is your operating model, and it sits entirely on your side of the relationship. You do not manage one Amazon account with an occasional question attached. You manage ten, or thirty, or fifty, each with its own inventory, its own invoice, and its own owner who expects an answer from you inside the hour. The prep center a single seller can tolerate, the one running on a shared inbox and a spreadsheet for receiving, becomes the exact bottleneck you cannot survive once you pass three or four clients. An aggregator managing a portfolio of brands hits the same wall, just under a different name on the org chart.

The fix is not a better spreadsheet on your end. It is a prep center built around the assumption that you touch many accounts, and every one of those accounts still has to look, from your client's side, like it is the only one in the building. We hear some version of this story from every agency that calls us for the first time.

Who Actually Holds the Contract With the Prep Center

Before you sign anything, one question decides how every later problem gets solved: whose name is on the service agreement with the prep center. It sounds like paperwork. It is closer to a liability decision, and most agencies discover which model they are in only after something has already gone wrong. Most of what defines a solid 3PL prep center for Amazon sellers still applies to you, but managing on behalf of clients adds a layer a single seller never has to think about.

Three structures show up across the industry, and a prep center rarely announces which one it runs until you ask directly.

The Agency as Titleholder

In this model, you sign the master service agreement, and every client account sits underneath it. The prep center bills you one number, and you are expected to collect from each client on your own schedule. This looks efficient from the outside. It also means you owe the full balance to the prep center regardless of whether a client pays you on time, or pays you at all. A late client becomes your cash flow problem, not the prep center's.

The Client as Titleholder

Here, each client signs its own service agreement and holds its own account with the prep center, tied to its own Amazon seller account. You are granted access to manage that account on the client's behalf, the same way you would be granted access to a client's Seller Central through an authorized user, not a shared password. The prep center bills the client directly. If a client stops paying, that balance belongs to the client, not to you.

The Mixed Model

A handful of clients sit under your own agreement, usually the smallest or newest accounts, while the larger or longer tenured clients hold their own contracts directly. This model tends to appear by accident rather than by design, as you grow past your first few clients and never go back to standardize the earlier ones. It works until you need a single, clean answer to who owes what, and find two different answers depending on which client you ask about.

The table below lays out what changes across the three, specifically on the questions that matter once a client relationship gets complicated: who owes the invoice, who is the prep center's point of contact, and what happens when a client exits.

PrepVia runs the second model for every agency client we onboard. Each of your clients gets its own account, tied to its own Amazon seller account through its own Amazon SP-API authorization, billed on its own invoice on Net-30 terms. The clauses you should get in writing before any of this starts are covered in the prep center agreement checklist. You are added as a manager on top of the account, not as the owner of it, and that single structural choice removes the debt question before it can ever reach you.

Permission Layered by Client, Not by Password

The easy way to give yourself visibility across ten accounts is to hand out one shared login and let everyone into everything. It is also the fastest way for client B to stumble across client A's inventory count, or worse, client A's invoice, while checking on its own shipment. A shared password is not a permission system. It is the absence of one.

A workable structure runs the other direction. Each client's account holds its own inventory, its own shipments, and its own receiving reports, visible only inside that account. You are layered on top, with your own login that follows every account you manage, without the client ever needing to share a password and without you ever needing to request one. When you check status on client six, you are inside client six's data specifically, not a general dashboard where six clients' numbers sit side by side waiting to be mixed up. The same logic that keeps Amazon, Walmart, and TikTok Shop inventory from mixing in a multichannel operation is what keeps your clients' accounts from mixing inside your own portfolio.

This matters most on your client's side of the relationship. A client that hired you to manage its Amazon account did not agree to have its inventory counts, its SKU-level costs, or its invoice visible to nine other businesses it has never met. Permission scoped by account, not by shared password, is what keeps that promise without you having to ask for it every time a new client comes on board.

One Invoice Per Client, One Statement for the Agency

A consolidated invoice sounds like a convenience until you actually have to reconcile it. One number covering ten clients means someone, usually the same account manager juggling ten tabs, has to go back through the shipment history and work out which portion of the bill belongs to which client, every single month. That work does not disappear when the invoice is consolidated. It only moves from the prep center's accounting team to yours.

An invoice itemized per client, per shipment, removes that reconciliation entirely. Each client sees exactly what it owes for exactly what moved through the dock under its own account, on Net-30 terms it can plan a cash cycle around. You do not need to build a spreadsheet to split a combined number, because there was never a combined number to split in the first place.

You still need your own view across the portfolio, and that is a separate need from billing. What you want at month end is not one invoice, it is one place to see all ten invoices at a glance, without opening ten separate emails to find them. That is a reporting question, covered further down, and the two ideas are worth keeping apart: billing per client keeps liability clean, and portfolio visibility keeps you from having to ask each client to forward its own invoice back just so you can build a summary.

The Debt Question Nobody Asks Until a Client Stops Paying

Every agency eventually loses a client mid-relationship, and a smaller number lose one while that client owes money somewhere in the supply chain. The question that decides how bad that moment gets is rarely asked during onboarding, when everyone is optimistic and the paperwork feels like a formality. Ask it before your first client ships.

If you are the titleholder on the prep center contract, your client's unpaid balance is now your unpaid balance, and the prep center has no reason to distinguish between the two. You can chase the client for reimbursement, but the prep center is owed regardless of whether that chase succeeds. This is the risk described under the first model in the table above, and it is the reason you should ask, directly, before signing anything: if this client stops paying tomorrow, whose invoice does not get paid.

Under a client-as-titleholder structure, the answer is simpler. The client owes the prep center directly, for its own account, and your relationship with the prep center is unaffected by whatever happens between you and that specific client. PrepVia does not run term contracts for the agency or for any client we manage, which means there is no standing agreement obligating you to a balance you did not create. Work is billed as it happens, per client account, and a client that stops paying is a matter between that client and the invoice on its own account, not a liability that travels up to you.

Reporting by Brand and Reporting Across the Portfolio

Your client wants one thing from a report: what happened to its inventory, its shipments, and its money, with nothing that belongs to a different business mixed into the same page. A report scoped to the brand is not a nicety. It is the baseline expectation of any client that hired you instead of managing its own account, the same expectation a single brand has from its own 3PL for ecommerce brands.

You want the opposite problem solved. You need to see status across every client you manage without opening ten separate accounts and building a summary by hand every Monday morning, the exact routine described at the start of this piece. The two needs are not in tension. They simply live at different altitudes of the same data. Receiving counts, prep progress, carrier pickup, and Amazon receiving status write to each client's own account as they happen. Your view rolls that same data up across every account you follow, without a second version of the truth appearing anywhere in between.

The receiving count feeding both reports holds to 99.9% accuracy, so the number your client sees on its own dashboard is the same number you see rolled into your portfolio view, not two different figures that quietly drift apart over a quarter. The practical result is that you can check on client six and see exactly what client six would see logging in itself, and nobody on your team is retyping a receiving count into a slide deck the night before a client call.

When a Client Leaves the Agency, the Inventory Stays Behind

You will lose clients for reasons that have nothing to do with the prep center. A client brings account management in house. A client switches agencies. A client's business changes direction entirely. The question that should never be a surprise is what happens to that client's inventory sitting on the dock the day the relationship ends. The full mechanics of a clean handoff are covered in how to switch 3PLs without losing a quarter, but the agency-specific version of that question deserves its own answer here.

Under a client-as-titleholder structure, the answer does not depend on you at all. The inventory was always inside the client's own account, tied to the client's own Amazon seller account, independent of which agency happened to be managing it that quarter. When the client leaves you, nothing about the inventory changes. What changes is who has permission to log in and manage it on the client's behalf.

PrepVia does not run term contracts, for the agency or for any client, which means a client is never locked into staying past the point it wants to leave, and you are never put in the position of holding inventory hostage on a client's behalf just to make an exit difficult. A client that departs takes its inventory to the address it names, and the release timeline is confirmed in writing before the first pallet moves, not negotiated after the fact when both sides are already frustrated with each other.

Moving the Amazon Account Without Moving a Single Pallet

The scenario you probably fear most is not losing a client. It is losing a client mid-shipment, with inventory somewhere between receiving and a carrier pickup, and no clean way to hand off management without physically moving product out of one warehouse and into another. That fear is reasonable when the underlying account structure ties inventory to you instead of to the client.

When the account belongs to the client from the start, a change in who manages it is a permissions change, not a logistics event. The client's Amazon seller account, its SP-API authorization, and its inventory at the prep center never move. What changes is which agency, or which internal team, is granted access to see and act on that account going forward. A shipment already in progress the day the switch happens continues exactly as planned, because nothing about where the inventory physically sits, or which Amazon seller account it belongs to, was ever a function of the agency relationship in the first place.

This is the structural reason a prep center built around per-client accounts handles agency turnover better than one built around agency-level pooling. The pallets never have to move for the login to change, and if you inherit an existing client from another agency, you inherit the account, not a moving truck. We built the account structure this way on purpose, so a login change never turns into a warehouse job.

Frequently Asked Questions

Can each client in an agency's portfolio have its own Amazon seller account with a prep center?

Yes. Each client is set up under its own account, tied to its own Amazon seller account through its own SP-API authorization. You are granted access to manage that account, but the account itself belongs to the client, not to you.

Who is responsible for the invoice if a client under an agency stops paying?

That depends on who signed the service agreement. If the client is the titleholder on its own account, billed directly, the unpaid balance belongs to the client. If you signed as the titleholder for every client underneath you, you owe the full balance regardless of whether that specific client ever pays you. Ask which structure a prep center runs before signing anything.

Does an agency need a separate login for every client, or one login across all of them?

A well built system gives you one login that follows every account you manage, without a separate password per client and without needing the client to share access. Each client, in turn, keeps a login scoped to its own account only, so nothing about another client's data is ever visible from inside it.

What happens to a client's inventory if it leaves the agency managing its account?

Nothing changes about the inventory itself if the client was always the titleholder on its own account. The client keeps its inventory, its invoice history, and its Amazon seller account exactly as they were. What changes is which agency or team has permission to manage the account going forward.

Can an agency see a consolidated view across all its clients without one combined invoice?

Yes, and the two should be kept separate. Billing per client keeps each client responsible for its own balance. A portfolio level view for you is a reporting layer built on top of that same data, not a change to how the invoice itself is structured.

Does PrepVia require a term contract for an agency or for the clients it manages?

No. PrepVia does not run term contracts for agencies or for any client account it manages. Work is billed as it happens, per client account, on Net-30 terms, which means neither you nor your client is locked into staying past the point either side wants to leave.

How fast can a new client under an agency be onboarded with a prep center?

A properly structured account can be created and connected to the client's own Amazon seller account the same day, with the first inbound shipment created immediately after. Starting with a smaller test shipment before moving full volume lets you confirm receiving accuracy and labeling before committing the rest of a client's inventory.

Final Take

If you run an agency, you are not asking a prep center the same questions a single seller asks. A seller wants to know the prep window and the price per unit. You need to know what happens on the tenth login, the tenth invoice, and the tenth client that eventually leaves, because none of those three events are edge cases for you. They are Tuesday.

The structural questions matter more than the sales pitch: who is the titleholder on the contract, whether permission is scoped per client or shared through one password, whether the invoice arrives itemized or consolidated, and what happens to inventory the day a client walks. Answer those four questions before you sign, and most of the operational pain you have heard other agencies describe from prep centers disappears before it ever starts.

We run every agency client on its own account, tied to its own Amazon seller account, billed on its own Net-30 invoice, inside a 24-36 hour prep window, out of a single Miami facility. You are layered on top with visibility across every client you manage, not ownership of the debt, the contract, or the inventory underneath it.

Ten clients should not mean ten different relationships for you to maintain by hand. They should mean one workflow, run ten times, with the same answer every time to the question of who owns what.