Pavoi is a Miami jewelry and activewear brand, and the number one jewelry seller on Amazon and TikTok. The brand also sells on its website, runs a retail store and is starting out in wholesale.
For a long time, the business ran on an order management system with light ERP features, plus spreadsheets and email. Pavoi has since moved onto the AI-native ERP built by DOSS.
I spoke with Lindsay Keys, Pavoi's VP of Operations and CX, and Sebastiaan Debrouwere, VP of Business Development at DOSS, about why Pavoi switched and what it had to fix first. Here's their story.
What’s inside
How Pavoi's supply chain is set up
First, we discussed how Pavoi's supply chain is set up, from the factory to the customer.
Sourcing. Most of Pavoi's products are made in China and Thailand, where it has manufactured for years. A small share comes from Vietnam. Over the last year and a half, Pavoi has also moved parts of its supply chain to deal with tariffs.
Transport. Pavoi moves much of its stock to the US by air. Jewelry is small and light, so one carton holds more units than anything Lindsay had worked with at past companies. "There's a luxury in being small and light," she said. Air freight puts new products in front of shoppers first, which matters for a brand that sells mainly on marketplaces. "We want to be there first. We want to capture that demand," she said.
Customers. Pavoi sells mainly in the US, with smaller Amazon businesses in Canada and the UK.
Fulfillment. Pavoi's stock sits in five places:
Amazon's fulfillment network
TikTok's fulfillment network
A third-party logistics (3PL) warehouse
Its retail store in Miami
Its studio in Los Angeles
"We have inventory quite literally [in] any marketplace that you could want it," Lindsay said.
Each sales channel comes with its own delivery promise. Amazon shoppers expect the speed and reliability of Amazon's network, where Pavoi has sold for about a decade. TikTok promises delivery in three days. Shoppers on Pavoi's own website will wait a little longer, because they come for a different product experience, Lindsay said.
Lindsay aims for value first. Speed comes from where each order is fulfilled.
Growing backwards
Pavoi started on marketplaces and added its website, wholesale and the store later. Lindsay calls this "growing backwards," the reverse of a DTC brand that starts on its own site and then expands onto marketplaces.
Growing backwards changed what Pavoi needed from its software. A marketplace business mostly needs order visibility and reconciliation. Once DTC and wholesale join, the business also needs order routing, inventory pushed to the right channel and rules that differ by channel.
👉 Five checks to run on your own operation: 5 checks to tell if you've outgrown your operations systems
When the OMS stopped keeping up
Before DOSS, Pavoi ran on "an OMS that had very, very light ERP functionality," Lindsay said. For a marketplace business that wasn't routing many orders, the OMS was enough.
As Pavoi's sales channels grew, the team lost sight of the supply chain. Lindsay listed what it couldn't see well: what was being made, where the stock was, which channel was selling it and how orders were being routed.
Speed depends on all of those pieces talking to each other. "When you're running that in so many different places, you have to make sure that you're checking that every place is talking to each other," she said.
Within a month of joining, Lindsay said, it was clear Pavoi needed "one centralized system that we can ultimately rely on" to run the business end to end.
Why not the traditional ERP route
Lindsay looked two, three and five years ahead and didn't see a traditional ERP getting Pavoi where it wanted to go. She gave me three reasons.
Pavoi likes to do things its own way. "We're not here to kind of mirror what we see is working well for others," Lindsay said. She credits that habit for much of the brand's success.
Order volume. Pavoi ships a lot of orders. From experience, Lindsay knew high volume "doesn't play well in every system," and that "ultimately you get priced out of at some point."
Customization. Growing backwards means Pavoi keeps adding channels with their own rules, so it needs software it can keep changing at a price it can afford. "I have not met somebody in a traditional ERP space that said customization came easy to me, and it came in a way that I could afford at scale to keep customizing," she said.
DOSS is built for that kind of change. Seb calls it "a box of Legos," assembled at a level below a standard ERP module. DOSS's order management is "a recipe," in his words, with data schemas, workflows and building blocks underneath that a team can change. So DOSS can rebuild a customer's own logic, like Pavoi's routing rules, inside the system.
👉 How DOSS gets a brand set up: How DOSS takes a brand from first call to go-live
Product data first
Before Pavoi could move onto DOSS, it had to clean up its product data. Lindsay said the job took far more work than the team expected. "I get triggered when anybody talks about unified master data," she said.
The product catalog is the most critical data Pavoi has. Each product is set up differently on each marketplace. The catalog also drives how Pavoi buys from its factories. After years of moving fast on marketplaces, the catalog carried a lot of legacy in how the data was structured and what connected to what.
Pavoi did its own discovery before any data went into DOSS. Two teams worked on it with Lindsay's operations team: a dedicated data team and a catalog team that handles SKU setup from procurement through to each marketplace. Together they cleaned the data, rebuilt how products get created and changed parts of Pavoi's business strategy along the way.
"Is this what we want to carry forward into the next ten years?" Lindsay said the team asked. "This is the opportunity to change this."
Lindsay said the work is ongoing, because marketplaces change and so do Pavoi's decisions about where to sell and store stock.
Seb said Pavoi's catalog taught DOSS a lesson it now explains to other prospects. New customers often ask for features like automated procurement first. DOSS starts with their master data. "We are not touching that until we figured out your master data," he said.
👉 Lindsay and Seb on the cleanup: Fix your product data before you automate anything
Routing every order as if it were the only one
Order routing was one of the first things Pavoi built on DOSS. For orders Pavoi ships itself, the routing tool picks where each one ships from. Lindsay described it as "such a beautiful product."
In legacy ERPs, Lindsay said, routing usually comes down to two options: how close the stock is to the customer, or a ranked list of warehouses. Brands that want more add another piece of software between the marketplace and the ERP.
Pavoi wanted its system to weigh four things for each order:
Speed to the customer
Cost, against the targets Pavoi sets for each location
Number of packages, so the customer gets as few deliveries as possible
Where the stock was meant to ship from
"I want to get my customers an incredible experience with the fewest amount of deliveries," Lindsay said. She wanted the system to look at "every customer as they are the only customer."
After a lot of testing, the tool still needs constant care, Lindsay said, because its inputs go stale as carriers change their rate cards and stock moves around. "You've got to kind of keep this as a living being in your business," she said.
Lindsay also used routing to set the bar for the whole project. She asked her team what they hadn't liked in past systems and what they'd change. "We don't want to recreate what we had before," she said. "We want to recreate things that we love and elevate it."
👉 How the routing rules work: How to set order routing rules that balance speed and cost
What AI-native means
I see AI on almost every software platform now, so I asked Seb what makes an ERP AI-native. He described two kinds of software.
AI bolted on. An existing system with a chatbot added. A team points the chatbot at the right data and asks it questions. Seb said these chatbots get easier to build as models improve.
AI-native. Software that "can be used both by humans and by agents or by machines in equal measure," Seb said. AI agents, software that can carry out tasks on its own, work inside the system, check their own work and can build new parts of it.
Seb's example was a short shipment. A brand orders 1,000 units from a supplier and only 900 arrive, but the supplier's paperwork still adds up to 1,000.
Part of the follow-up runs on fixed rules, like counting what arrived and checking what the contract says about shortfalls. The rest takes judgment:
What happened to the missing 100 units
What to tell the warehouse to expect
Whether to ask for a credit or a refund, or cancel the order
How to escalate it, and who follows up
A bolted-on chatbot can report the count and the contract terms. An AI-native system also helps a person make the judgment calls, Seb said.
Lindsay said Pavoi deals with this "more than people would care to admit." Missing units can sit in the system as in transit indefinitely. Demand planners keep counting them as on the way. Finance still sees the dollars at month end, even after a claim has paid out.
Pavoi is now building decision trees in DOSS for this case. Lost units move out of in transit and into a bucket the team tracks, with an audit trail for each unit.
Seb said each of those judgment calls teaches the system more about how a business runs, so "over time it gets smarter and smarter."
👉 Seb's test, step by step: How to test whether an ERP is actually AI-native
Reports that show only what went wrong
With its data in one system, Pavoi can build its own reports and tools on top of it. DOSS launched a feature for this, Dynamic Apps, the week before our conversation.
Seb said teams often have a list of reports they want and never get to, because pulling the data together takes too long. One DOSS customer, a coffee roaster, had a list of 32 reports it wanted to see in real time. Dynamic Apps lets a team build a workspace for one job, such as tracking margins or onboarding new hires.
Lindsay uses these apps as checks on the business. She only wants to see the exceptions. "I don't want a vanity metric that says 99.9% of your orders made it into the system. I really don't care," she said. "I do care about that percentage that doesn't."
When her team already knows what good looks like, Lindsay wants the system to flag whatever falls outside it. "I build this report 52 times a year, once a week. So I know what I'm looking for here," she said.
For now, DOSS builds these apps with its customers. Seb said guardrails matter when the data is the source of truth. He'd rather build with a customer than "get a phone call at three in the morning."
👉 See Dynamic Apps live in Part 2, a DOSS demo on Friday, Nov 20 at 10am PT: register here
Pavoi's supply chain team
Pavoi's supply chain team is just four people. They cover production, procurement, freight forwarding, warehouse management, marketplace management, inventory accuracy and returns. A separate team runs data.
The team has stayed that size as the business has grown. Lindsay expects the new system to keep it there. "We don't bring on these tools to not enable time back," she said. The time saved goes to the brand's next big project.
Lindsay also credits her people. "I'm very fortunate to have a team of people I would classify as builders," she said. They get into the weeds and keep asking whether software could do a task alongside them.
Seb hires for the same thing at DOSS. In his view, a strong ops team pairs people who have deep experience in hard areas, like retail chargebacks and deductions, with people who can spot one narrow problem and build for it. His example was a sales peak like Prime Day, Black Friday or Valentine's Day, which can call for one-off packaging or ad budgets matched to the stock at each marketplace.
Who this fits
Seb said Pavoi matched everything he looks for in a first call with a brand:
Growing at breakneck speed. Almost every DOSS customer is.
A small team that's stretched. A few people running a complicated business with high order volume.
A couple of things breaking first. Usually one decision that's getting harder, like what to reorder, which channel sells which stock, or how to spend cash.
Lots of handoffs. Between teams, between an OMS or two and an inventory system, and between spreadsheets and software, so nobody has a full view.
A team that wants to move fast. Seb wants customers who will "really challenge and stretch us."
Each new DOSS customer starts from a template built for its industry. Seb said the template covers about 80 to 90% of what a brand needs. DOSS builds the rest with the customer. The standard parts of Pavoi's setup go into the template. "We're obviously not taking Pavoi's secret sauce and handing that out to the rest of the industry," he said.
What Pavoi is building next
Pavoi is still building on DOSS. The catalog work continues as marketplaces change, and the team is building decision trees in DOSS to clear lost inventory out of in transit. Lindsay wants the system to surface the exceptions, so her team can spend its time on the brand's next big project.
DOSS will show Dynamic Apps live in Part 2 on Friday, Nov 20.
More from this conversation



















