adamshupe.com · index

PacSun · eCommerce

Building PacSun’s Drop-Ship Business

How vendor-direct fulfillment turned inventory ownership from a prerequisite into a choice—and became a continuing cross-functional growth capability

Owned
Created the Drop Ship program and owned it end-to-end: strategy and program direction, vendor-acquisition and assortment coordination, platform and vendor selection, integration direction, analytics and reporting, ongoing operating accountability, and cross-functional problem solving.
Boundary
Buying decisions were shared with PacSun Buying and vendor partners.

Approximately 2015–2016 through 2023 · documented 2020 operating state

ARCHIVE · 2015—2026

Find another growth lever

Around 2015–2016, as I remember it, PacSun needed another way to grow. Growing assortment the conventional way meant buying first: decide what would sell, own the inventory, carry the risk. I began building Drop Ship as another lever. Vendors could ship their own products directly to our customers, which meant we could put far more of what they already carried in front of shoppers without buying it in advance.

Start with two brands

I began the proof of concept with exactly two brands: Volcom and O’Neill. Two established vendors were enough to prove the model could actually work before the emphasis shifted toward bringing as many approved vendors into the program as we could.

Inventory ownership becomes selective

Drop Ship did not replace conventional buying. It made inventory ownership selective. PacSun could still buy the products it wanted to own while exposing more of a vendor’s long-tail assortment through vendor-direct fulfillment.

That changed what we could consider selling. The model opened room to consider skateboard and surfboard hardgoods, video games, and electronics—categories PacSun would have been unlikely to buy outright. Looking back, I also came to see Drop Ship as a proving ground for emerging brands we could not or would not buy conventionally: a brand could show us what it did with real customers first, though there was no formal rule or guaranteed path from there to a buy.

Scale the vendors, not just the integration

After the proof of concept, the work was not to repeat an integration. It was to bring more approved vendors in, and to keep acquisition, assortment, systems, and reporting moving together as we did. I owned that program end-to-end and stayed accountable for where it went.

The preserved 2020 Drop Ship worksheets show that work in motion: vendor discovery calls, a Q1 target to onboard 16 brands, seasonal assortment work, scorecarding and reporting, and vendors sitting under Launching, On-Going, and Upcoming. They record what we were aiming at and what was in flight—not what we hit.

Operate the business every day

Drop Ship was never a finished integration; it was a business that had to be run. Vendors had to be found and onboarded, assortment agreed, reporting maintained, money reconciled—and underneath all of it ran the exceptions, the returns and cancellations and customer problems that fell into the gaps between systems and teams. The 2020 worksheets still carry customer service, invoicing, returns, and cancellations as On-Going work, which is what they were: open, not resolved.

End-to-end ownership did not mean I wrote the integrations, chose every item, or handled each payment, shipment, return, or customer case myself. Buying, Technology and Logistics, Finance, Customer Service, our vendors, and the platform providers each did their own work. What I owned was the capability—holding it together, and answering for it when it did not hold.

Learn to own what I could not control

This was my first substantial experience owning a business capability like this. I had to learn unfamiliar technical and operating concepts quickly, including EDI processes I had not previously known existed. I wanted to scale faster than the resources allowed. Work was deprioritized, goals were missed, and integration and operating complexity slowed things down. None of it was dramatic. It was the steady friction of a program that ran on other teams’ roadmaps as much as my own.

The deeper lesson was that accountability and direct control are different. I remained responsible for the capability’s direction and operation even when the systems, specialist teams, and vendor actions it depended on sat outside my authority. Progress came from coordination and follow-through, not from doing the work myself.

What the capability became

Drop Ship began well before PacSun’s later replatform, continued through it, and remained afterward through my 2023 departure. The replatform did not introduce the program; Drop Ship was a separate commerce capability that had to keep operating across that change.

What started with two brands became a standing part of how the company could grow. Inventory ownership was no longer a prerequisite for everything PacSun wanted customers to see, which left room for long-tail assortment, nontraditional categories, and brands too new to buy. What I took from building it is smaller and more durable than the program itself: a capability is not a launch. It is the thing you keep operating after it works.

Limits

The program’s origin, the two-brand proof of concept, and the categories it opened rest on my memory, and exact dates and vendor counts are not established. No sales, growth, margin, or order figure is claimed or implied.

With

PacSun Buying
— Supported vendor acquisition and made assortment decisions.
PacSun Technology, Logistics, Finance, and Customer Service
— Supported integrations and day-to-day technical and logistics requirements, reconciliation and payment, shipping-cost and invoicing work, and customer-facing operating functions within their respective specialties.
Vendors, vendor eCommerce operations, and platform providers
— Supported integrations, operating coordination, assortment execution, and enabling platform functions.

Kept by Adam Shupe · adamshupe.com