From my conversation with Lindsay Keys of Pavoi and Seb Debrouwere of DOSS. Read the full case study →
When a brand keeps stock in more than one place, every order raises a question: where should it ship from? The answer decides how fast the customer gets the order, how many boxes arrive, and what the shipment costs.
Pavoi, the number one jewelry seller on Amazon and TikTok, keeps stock in five places, including Amazon's and TikTok's own networks, which ship the orders placed on those marketplaces. For the orders Pavoi ships itself, it built its own routing rules on DOSS. Lindsay Keys, Pavoi's VP of Operations and CX, says, "I do love that product." Seb Debrouwere of DOSS says logic like Pavoi's is "really, really hard to do in an ERP system."
Here's how Pavoi approached routing, and the questions to answer before you write your own rules.
The two options a legacy ERP gives you
Lindsay says routing in legacy ERPs is "very limited." You usually get two options:
Proximity. Ship from the location closest to the customer.
Priority rankings. Ship from location A, then B, then C.
Anything beyond that means adding another piece of software between your sales channels and your ERP, or working around the system.
Route each order as if it were the only one

Pavoi wanted routing that weighs more than distance. Lindsay's goal: "I want to get my customers an incredible experience with the fewest amount of deliveries."
The rules look at every customer "as they are the only customer" and decide where to ship from separately for each order. Each decision balances two things:
The customer. Fast delivery, in as few packages as possible.
Pavoi's targets. Ship from the place Pavoi meant that stock to ship from, at the cost it planned for.
Lindsay calls blending the two "the art and science" of routing. Seb adds that Pavoi's rules also weigh inventory availability and the rules of each sales channel.
Start with what your team hasn't liked
Routing was one of the first things Pavoi built on DOSS, and the idea came from a question Lindsay put to her team. They had used many systems before, so she asked them what they didn't like, what they would change, and what enhancement they would ask for if they could.
"We don't want to recreate what we had before. We want to recreate things that we love and elevate it," Lindsay says.
Questions to answer before you write rules
What does a good delivery look like on each channel? At Pavoi, Amazon customers expect Amazon speed, TikTok promises three days, and website customers will wait a little longer.
What does a split shipment cost you? Count the extra carrier fees, and what the customer thinks when two boxes arrive.
Where did you plan for each unit to ship from, and at what cost? Your rules should protect that plan.
Which channel rules limit where an order can ship from? Seb names these as one of the inputs to Pavoi's logic.
Who keeps the inputs up to date? Rate cards and stock positions need an owner.
Treat routing as something you maintain
Lindsay's warning is that good routing is hard to build and has to be maintained. The inputs go out of date quickly:
carrier rate cards change, and
stock gets spread across locations differently.
"You've got to kind of keep this as a living being in your business," she says. Pavoi spent a lot of time testing its rules before relying on them.
More from this conversation



















