By Bernardo Campelo, Forbes Business Council E-Commerce Leader, Amazon SPN Certified provider, Amazon SP-API authorized partner, and Founder of PrepVia.
A director of operations at an aggregator called me in August with forty brand names in a spreadsheet and one deadline. Every one of those brands had grown up on a different 3PL, a different supplier list, and in some cases a different idea of what a SKU even meant. He wanted all forty inside one prep center before the fourth quarter, and he wanted to know if that was realistic.
It is realistic, but only if you refuse the instinct that wrecks most portfolio migrations. That instinct is to move the biggest brand first, because the biggest brand carries the biggest dollar figure and looks like the win worth reporting upward. Move the biggest brand first and you have built your entire test case around the one acquisition with the most to lose if the test goes wrong.
An aggregator is not one seller switching providers. It is ten, twenty, or forty sellers switching at once, each with its own catalog, its own cost history, and its own buyer relationships, all folding into a single warehouse address. The mechanics of a single-account migration, the kind covered in how to switch 3PLs without losing a quarter, do not scale to a portfolio by simple repetition. A portfolio migration needs its own sequence, and the sequence starts with choosing the brand that can afford to be wrong.
The right first wave is the smallest, cleanest brand in the portfolio, never the largest one, and everything else in this piece follows from that single decision.
The 60-second version
Move a brand portfolio into one prep center in waves, starting with the lowest-risk brand, never the largest. Map every SKU against the old systems before the first carton ships, because two brands sharing one UPC will corrupt receiving the moment both land in the same warehouse. Keep a separate cost ledger per brand even after operations centralize, and decide up front whether the portfolio pays one consolidated invoice or a statement per brand. Sized correctly, a forty-brand rollout runs ten to twelve weeks, and each week's volume should stay well inside what a 5,500 square foot facility with three loading docks can actually receive in a week.
Why a Portfolio Migration Cannot Run as a Single Event
A single seller switching 3PLs manages one purchase order calendar, one catalog, and one relationship with the old provider. An aggregator managing the same switch across forty brands is coordinating forty of each, on forty different timelines, often with brand managers who joined the portfolio only months ago and still think of the old 3PL as their own vendor.
Treat that as one event and you get gridlock. Every brand wants its inventory prioritized, every brand manager wants a call with the new prep center before shipping anything, and the receiving dock at the new facility absorbs a spike of unfamiliar SKUs on day one with no history to work from. A dock with three doors can only process so many unfamiliar pallets in a week before pace slips for every brand in the queue, not just the one that caused the backlog.
Waves solve this by turning one large, unknown event into a series of small, measured ones. Each wave teaches the prep center something about the next, and each wave gives the brands still waiting a real answer instead of a promise, because by the time their turn comes there is already a working relationship to point to.
Choosing Wave One: The Lowest-Risk Brand, Not the Largest
The brand you choose for wave one sets the tone for the entire onboarding. Choose wrong and a single messy launch becomes the story every other brand manager repeats to justify resistance later.
A good wave-one brand is boring on purpose. It has a small, stable SKU count. Its units already carry a compliant FNSKU or a clean manufacturer barcode, not a mix of generic UPCs pulled from three different sourcing runs. Its revenue exposure is modest enough that a slow first week costs the portfolio very little, and its brand manager is genuinely willing to be first rather than being volunteered.
- Fewer than fifty active SKUs, so the SKU map can be verified by hand before anything ships.
- No multi-pack, kitting, or bundling requirements that add extra assembly steps to the first run.
- Barcodes already compliant, so labeling is not part of the test.
- A brand manager who has used the old 3PL's portal enough to know what good data looks like.
- Revenue that will not sink the quarter if the first week runs slower than planned.
The largest brand in the portfolio belongs in a later wave, once the process has already been proven on something smaller. By the time it moves, the SKU mapping method, the billing split, and the reporting format have all been tested on brands that could afford a mistake.
Mapping SKUs Across Old Systems Before Anything Ships
Every acquired brand arrives with its own SKU logic, sometimes inherited from a founder who built it alone, sometimes inherited from a 3PL that assigned internal codes nobody outside that warehouse ever saw. Centralizing forty brands means translating forty different logics into one system the new prep center can actually work from, and that translation has to happen before the first pallet leaves the old address, not after.
Build one mapping file per brand before the migration starts: internal SKU, FNSKU, UPC or manufacturer barcode, ASIN, and unit weight and dimension. Verify each line against the brand's actual Seller Central listings rather than trusting whatever spreadsheet came over during due diligence, since acquisition spreadsheets are notoriously stale by the time onboarding begins.
The UPC Collision That Breaks Receiving
The failure mode that catches aggregators off guard almost every time is the UPC collision. Two brands in the same portfolio, sourced from the same overseas manufacturer or the same private-label supplier, can end up assigned the identical UPC on completely different products. Under separate roofs with separate 3PLs, nobody ever notices. Inside one shared warehouse, a scanner that reads that UPC has no way to know which brand's inventory it just counted.
The result is not a small error. A receiving system that resolves identity by UPC alone will misattribute units, misallocate them to the wrong brand's cost ledger, and hand you a count that looks accurate at the shipment level while being wrong at the brand level, the same category of gap covered in declared versus received discrepancies. You will not catch it by checking the total. You catch it by checking the total against each brand separately, and by then the units are already commingled.
The Fix: Brand-Level Identifiers Above the UPC
The fix is to stop relying on the UPC as the sole identity field the moment a portfolio crosses one brand. Every receiving record needs a brand identifier attached at the purchase-order level, confirmed at intake before a unit ever gets scanned into general stock, so that an identical UPC on two different brands still resolves correctly. This is exactly the distinction covered in FNSKU versus UPC versus manufacturer barcode, and it matters more for a portfolio than for any single seller, because a single seller never has two SKUs racing for the same barcode.
Cost History That Has to Survive the Merger, Brand by Brand
Centralizing prep operations does not mean centralizing the way each brand understands its own profitability. Finance still needs a true profit figure per ASIN, per brand, the way it did before the merger, and that figure depends on a clean per-unit cost history that traces back through the old 3PL, not a blended average across the whole portfolio.
Before the first brand moves, pull twelve months of per-unit prep cost, storage cost, and labeling cost from its old provider, by SKU. That history becomes the baseline every future invoice gets checked against, and it is the only way to answer the question a brand manager will eventually ask: did centralizing actually save this specific brand money, or did it just get absorbed into a portfolio average that hides a brand doing worse than before. The same discipline that protects a single seller's margins, described in true profit per ASIN, still applies once that seller is one of forty inside a portfolio.
Losing that history is the quiet cost of a rushed migration. Nobody notices it in week one. Finance notices it at quarter end, when a brand that used to be profitable on paper suddenly is not, and there is no clean record explaining why.
Per-Brand Billing Against Consolidated Billing
The aggregator has to decide, before any brand ships, whether the prep center bills the portfolio as one account or bills each brand separately. Both models work. What does not work is deciding this after the first invoice arrives and the numbers do not match what any single brand manager expected.
A single consolidated invoice under Net-30 terms is simpler to reconcile against one accounts-payable process and gives the portfolio a clean total each month. Its weakness is allocation. Shared costs, an inbound container split across three brands, a kitting run that combines SKUs from two brands into one bundle, have to be divided by a rule everyone agrees on in advance, or the consolidated number stops meaning anything at the brand level.
A per-brand statement behind one consolidated summary solves the allocation problem directly, at the cost of more line items to track. Every brand sees its own per-unit prep fee, its own storage charge, and its own share of any shared cost, referenced against the same published rate structure the whole portfolio operates under. Whichever model you choose, write it into the onboarding agreement before wave one ships, alongside the other terms that belong in every prep center agreement, so nobody discovers the allocation rule by reading an invoice.
24 to 36h prep. 35-hour end-to-end guarantee or the prep is free. Net-30 terms. From 50 units to full truckloads.
One Point of Contact Per Brand, One Owner for the Whole Portfolio
A brand manager who spent two years learning the quirks of the old 3PL, which SKUs mis-scan, which packaging needs an extra layer, which supplier ships early, carries knowledge that does not transfer through a spreadsheet. Losing that person's attention during onboarding is how a clean SKU map still produces a messy first shipment.
Assign each brand its own contact at the new prep center, someone who learns that brand's exceptions directly from the person who already knows them, and pair that with one portfolio-level owner on the aggregator side who tracks every wave against the plan. The brand-level contact answers the daily questions. The portfolio owner answers the question the leadership team actually asks: are we on schedule across all forty, not just the three that shipped this month.
This structure matters most in the first two waves, while the new prep center is still learning the portfolio's habits. By wave four or five, patterns repeat enough that the portfolio owner can run reviews weekly instead of daily, and the brand-level contacts spend more time preventing exceptions than explaining them.
The Wave Plan, and the Reporting the Aggregator Actually Needs
A forty-brand rollout works best staged across ten to twelve weeks, sized so weekly volume never approaches what the receiving dock can safely absorb in a week. A facility running three loading docks in a 5,500 square foot footprint has handled a peak week of 18,080 units across 15 shipments before, and a wave plan should stay comfortably under that ceiling until the process has proven itself on the smaller waves first.
| Weeks | Brands in wave | Approximate units | Decision point before the next wave |
|---|---|---|---|
| 1 to 2 | 3 lowest-risk brands | 3,500 to 4,500 | SKU map and UPC audit clean, receiving accuracy at or above the 99.9% benchmark |
| 3 to 4 | 5 brands, including one with multi-pack SKUs | 7,000 to 9,000 | Per-brand invoice reconciles against the quoted rate, no allocation disputes |
| 5 to 6 | 8 brands | 11,000 to 13,000 | Per-brand and consolidated reports both match the source systems brand by brand |
| 7 to 9 | 12 brands | 14,000 to 16,000 | Dock scheduling across all three bays holds with no wave slipping into the next |
| 10 to 12 | Remaining 12 brands, including the largest | Variable by brand size | Old provider accounts closed in writing, records exported, portfolio fully live |
Each decision point exists so a wave that fails does not automatically drag the next wave forward on schedule anyway. A wave that misses its decision point pauses while the specific problem gets fixed, and only then does the next group of brands begin shipping.
Reporting has to answer two different questions at once, and most portfolio reporting fails because it only answers one. A brand manager needs to see their own brand: units received, cost per unit, count accuracy, and any SKU exception traced back to their catalog specifically. The aggregator's leadership needs the consolidated view: total units across the portfolio, blended cost trend, and which brands, if any, are still running above the accuracy or timeline baseline set in wave one.
| Report | Who reads it | What it must show |
|---|---|---|
| Per-brand receiving report | Brand manager | Units received against declared, by SKU, with any exception flagged to that brand only |
| Per-brand invoice | Brand manager and finance | Prep, storage, and labeling cost isolated from every other brand in the portfolio |
| Consolidated portfolio dashboard | Operations director | Total units, blended accuracy, and wave status against the original schedule |
| Inbound tracking, all brands | Operations director | Every shipment's status from receiving through Amazon check-in, filterable by brand |
Neither view replaces the other. A prep center that can only produce the consolidated number is asking every brand manager to trust an average, and a prep center that can only produce per-brand numbers is asking the operations director to add forty reports together by hand every week.
Frequently Asked Questions
How many brands should move in the first wave of an aggregator onboarding?
Two to three brands is enough for a first wave, chosen for low SKU count, clean barcodes, and modest revenue exposure rather than size. The goal of wave one is to prove the SKU mapping, the billing split, and the reporting format on brands that can absorb a slow week without damaging the portfolio, before the largest and most complex brands ever ship.
What happens when two brands in the same portfolio share a UPC?
A receiving system that identifies units by UPC alone will misattribute inventory between the two brands the moment both are stored in the same facility, even though the error was invisible while each brand used a separate 3PL. The fix is a brand identifier attached at the purchase-order level and confirmed at intake, so an identical UPC on two different products still resolves to the correct brand every time.
How do we keep cost history separate for each brand after centralizing prep?
Pull each brand's per-unit prep, storage, and labeling cost history from its old provider before it moves, and keep that baseline as a brand-level ledger rather than folding it into one portfolio average. Finance still needs a true profit figure per ASIN for every brand individually, and a blended average across forty brands can hide a specific brand losing money even while the portfolio total looks healthy.
Should an aggregator use one consolidated invoice or a separate invoice per brand?
Either works, but the decision has to be made before wave one ships and written into the onboarding agreement. A consolidated invoice is simpler to reconcile but requires a clear rule for allocating shared costs like a combined inbound container. A per-brand statement solves allocation directly and gives every brand manager a number they can verify against their own catalog.
Who should be the point of contact for each brand during onboarding?
Each brand should keep a dedicated contact at the new prep center who learns that brand's specific exceptions directly, paired with one portfolio-level owner on the aggregator side who tracks every wave against the overall schedule. The brand-level contact handles daily questions. The portfolio owner answers whether the whole rollout is on schedule, not just the brands that shipped this month.
What reports does an aggregator need during a multi-brand migration?
Two views, run in parallel. Each brand manager needs a per-brand receiving report and invoice that isolates their own units, cost, and any SKU exception from every other brand. The operations director needs a consolidated dashboard showing total units, blended accuracy, and wave status against the original schedule, plus inbound tracking that can be filtered brand by brand.
How long does it take to move forty brands into one prep center?
Plan for ten to twelve weeks staged across five or six waves, sized so no single week's volume approaches the receiving capacity of the facility. The timeline is rarely limited by how fast units can physically move. It is limited by how fast each wave clears its decision point, since a wave that fails a check should pause rather than pull the next group of brands forward on the same schedule.
Final Take
Forty brands moving into one prep center is not one migration repeated forty times. It is a sequencing problem first and a logistics problem second, and the sequencing gets solved by choosing the least risky brand for wave one, not the brand with the most attention on it.
The details that actually break a portfolio onboarding are rarely dramatic. A UPC that two brands happen to share. A cost history that gets blended into an average instead of staying visible brand by brand. An invoice nobody agreed how to split before it arrived. None of these show up in a sales conversation. All of them show up in week three if nobody planned for them in week one.
The aggregators that onboard well treat each wave as evidence for the next one, not as a race to get everything under one roof by a deadline. A wave that clears its decision point earns the next wave. A wave that does not gets fixed before another brand ships.
Forty brands, one warehouse, and a decision point built into every wave along the way. That is the difference between a migration and a mess.
See how PrepVia handles multi-brand onboarding →
PrepVia is Amazon SPN Certified, prep window 24-36 hours, Net-30 available.
- How to Switch 3PLs Without Losing a Quarter: the single-account version of this playbook
- FNSKU vs UPC vs Manufacturer Barcode: the identity layer that has to hold when two brands collide
- Prep Center Agreement Checklist: the billing and exit terms to settle before the first wave ships
