Multiple Shipping Addresses on Amazon Business

This is one of the highest-leverage settings on an Amazon Business account and one of the least discussed, because it looks like administrative housekeeping. It is not. It is the control that decides whether an order placed on the company account can be delivered to a private address, which is the practical enforcement mechanism behind the personal-use rules.

Shared versus individual: the actual difference

Amazon frames it at the group level, which is the part people miss — it is not an account-wide switch:

• Individual addresses. Requisitioners in that group can add a shipping address during checkout, or to their address book under Your Account. Maximum flexibility, minimum control.
• Shared addresses. Requisitioners in that group cannot add a shipping address during checkout. The administrator adds addresses from Business Settings or from the checkout pages, and once added they are available to everyone in the group.

Because it is per-group, you can run both. A facilities group on shared addresses locked to your sites; a field-sales group on individual addresses because they genuinely need to ship to varying locations. Setting up groups is covered on multi-user accounts and approvals.

Amazon's own stated rationale for shared addresses is worth repeating because it is unusually concrete: it helps to prevent delivery errors, makes the ordering process easier, and gives you better control of shipping locations.

The Amazon Hub trade-off

There is exactly one thing you give up, and it is stated plainly:

You can use Amazon Hub services (such as Amazon Locker and Amazon Counter) and set a pickup point for individual addresses only. Shared addresses do not support Amazon Hub or pickup services.

For most organizations this is irrelevant — they ship to their own premises. For two groups it is decisive: businesses with no staffed delivery point, and contractors who collect en route to site rather than having materials delivered to an unattended location. Those groups need individual addresses, and should get their control from approval workflows instead. See contractors and jobsites.

Bulk uploading addresses

If you have more than a handful of sites, do not type them. Amazon supports uploading addresses to shared address business groups using a Microsoft Excel .xlsx file, and administrators of multiple groups can upload to their groups at the same time.

The published mechanics:

1. Business Settings → Addresses, viewing a group you administer.
2. Add an address → choose Upload addresses for the current group, or Upload addresses to multiple groups.
3. Download the template and complete the mandatory fields.
4. For multi-group uploads, download the available groups file and copy the group IDs. To make one address visible to several groups, duplicate the address line and enter the other group IDs.
5. Save as .xlsx, browse to the file, and Upload. If any address fails, Amazon provides a link to a report explaining what went wrong.

Each file supports up to 1,000 addresses, though Amazon notes you may add any number of addresses to a group — so a larger estate is split across files rather than blocked.

Two practical notes from Amazon's guidance: use match destination formatting when pasting data into the template, and know that there is a bulk download route too — Actions → Download addresses for the current group, delivered by email link. That download is how you migrate a list from one group to another without retyping.

There is also a blunt instrument worth knowing exists so you do not press it: Actions → Remove all addresses clears the shared list entirely.

Locations and delivery preferences

Above addresses sits a second concept most administrators never open. Within addresses and delivery preferences settings there is an Account Locations tab listing every location — a building or campus — used across your individual and shared addresses, sorted by shipment volume.

Per location, administrators can edit delivery preferences including delivery times, drop-off information, pallet preferences and observed holidays, applied to Amazon Logistics deliveries. Amazon adds two things worth knowing:

• Updating preferences for a location updates them for all groups in your organization that ship there.
• The locations list updates regularly based on shipment volume and the addresses on the account — and your address settings do not change based on the locations list.

Sorting by shipment volume is a small gift to anyone managing a large estate: it tells you where to spend your five minutes of configuration. The top three locations by volume are where a wrong delivery window costs the most.

The observed-holidays setting deserves a special mention for schools, which close for weeks at a time — schools and education — and delivery times matter enormously for restaurants that cannot receive during service — restaurants and food service.

Shipping one order to many sites

The pattern that makes bulk buying work for a multi-site organization: place one large order and ship cart items to every address in a selected group. That is how you clear a quantity-discount tier or a Request for Quote threshold that no single site could reach alone. See bulk buying and quantity discounts and Request for Quote and large orders.

One boundary to respect: shipping to your own locations is exactly what this is for. Shipping to your customers is not — the Prime Business terms restrict shipping benefits to products shipped to the customer itself or to locations for its own use. See Business Prime shipping and delivery.

A sensible default setup

1. Create a group per site or per function, then set shared addresses on any group that only ever ships to company premises.
2. Bulk upload the estate if you have more than about ten locations.
3. Set delivery preferences on your top locations by shipment volume.
4. Leave individual addresses only where staff genuinely need Locker pickup or variable destinations, and control that group with approvals instead.