Multi-User Accounts and Approvals

This is the feature area where the free account is most underrated. A surprising number of write-ups describe multi-user purchasing as a Business Prime capability. It is not — it comes with the account, and if several people ordering is your only requirement, you should not be paying anything.

The problem this actually solves

Most small organizations arrive here from one of two situations, both bad.

The shared login. One Amazon account, one password, passed around. Nobody can tell who ordered what, the password never gets rotated when someone leaves, and the person whose name is on the account is personally exposed to everything bought under it.

The reimbursement pile. Everyone buys on their own card and expenses it. No pricing consistency, no spend visibility until the receipts land, and a monthly administrative chore.

Multi-user access fixes both, and it does so at no cost. Each buyer gets their own login under the organization's account, with permissions you control, and everything appears in one purchasing history.

Setting it up

Users are invited by email from the business account, and each is assigned permissions when invited. Practically, plan three things before you start sending invitations.

Who buys, and who approves. These should be different people, or the approval step is decoration. On a small team the approver is usually whoever owns the budget.

What triggers approval. An approval rule that fires on every order teaches people to click through it without reading. One that fires on genuinely significant orders gets read. Set the threshold where it will actually cause someone to think.

What happens when the approver is away. The most common failure of approval workflows in small businesses is not fraud, it is a blocked order on a Friday afternoon because the only approver is on holiday. Decide the fallback before it happens.

Approvals versus Guided Buying

This distinction decides whether you need to spend money, so it is worth being precise about.

Approvals (free) are a review step. A buyer selects what they want, and an approver signs it off before it is placed. The control is human and it happens after selection.

Guided Buying (paid, from Essentials) shapes selection itself, steering buyers toward preferred products and categories. On the Enterprise tier, Amazon describes it as being able to block certain purchasing behavior — a genuinely different capability from steering.

So: if your requirement is "somebody should check this before it goes", approvals are free and sufficient. If it is "people should be nudged toward the right products", that is Guided Buying from Essentials. If it is "people must not be able to buy X", Amazon describes that blocking capability on Enterprise. Being clear about which sentence describes you is worth $179/year at minimum.

The seat cap trap

Here is the counterintuitive part, and it is the reason this page sits in the guides section rather than the Business Prime section.

Buying Business Prime makes your user situation more constrained, not less. The free account supports multiple users and Amazon publishes no cap on it. The paid tiers cap seats: 5 on Essentials, 20 on Small, 200 on Medium.

And those caps are cliffs. Crossing one forces the next tier entirely:

• User #6 — Essentials → Small: +$320 a year
• User #21 — Small → Medium: +$800 a year
• User #201 — Medium → Enterprise: +$8,800 a year

If you are considering Business Prime for reasons unrelated to users — shipping, most likely — count your buyers first, because the seat cap may cost more than the shipping saves. The full arithmetic is on Business Prime pricing.

Reporting across users

The free account includes pre-built and custom purchasing reports, so "what did the organization buy, and who bought it" is answerable without paying. Spend Visibility, from Essentials up, is a deeper analytics layer — the difference between having the data and being able to slice it the way a finance function wants.

For a team where the person buying is also the person reading the report, free reporting is almost certainly enough.

Making it stick

The technical setup is the easy half. Three things determine whether this survives contact with a real team:

1. Remove leavers the same week. A dormant buyer account is exactly the problem you set this up to avoid.
2. Review permissions when roles change. Permissions granted for a temporary project have a way of becoming permanent.
3. Look at a report once a month. Reporting nobody reads is not a control, and this is the free feature most often configured and then forgotten.

Related: for the org-type view of this, see offices and small teams — where the five-seat cap decides more than anything else — and for the other free operational feature, tax-exempt purchasing. The one genuinely paid operational feature is Pay by Invoice and net terms.