Tipsy Elves uses Agentway to turn operational complexity into systems, giving a lean team the visibility and leverage of a much larger organization.

Tipsy Elves is an occasion-driven apparel brand. People buy a costume for Halloween, a shirt for a golf tournament, matching outfits for a ski trip. For Tipsy Elves, a delivery date is often part of the product.

That makes the business unusually sensitive to timing, and unusually seasonal. “We might do as much business in October in a day as we do in April,” says CEO Nick Morton. A small operational issue in the summer can become a very large one at peak, exactly when the team has the least time to investigate it.

Tipsy Elves partnered with Agentway to catch those problems before they become customer problems. What began in customer support has grown into an operating layer across orders, inventory, fulfillment, and CX: continuously checking the systems involved, tracing disagreements back to their source, and bringing the team the small number of exceptions that actually need a person’s attention.

The goal isn't another dashboard or another queue to watch. It's to let a lean team spend less time reconstructing what happened and more time deciding what to do next.

Start with the work nobody wants to do

Order reconciliation had been bothering the team for years. An order can exist in Shopify but never reach NetSuite. A warehouse can cancel a line without the change making it back upstream to Faire. Tracking says one thing, the warehouse says another. Each system can be working as designed while the handoff between them fails.

Finding those failures meant repeatedly pulling together data from different systems and figuring out which orders actually needed help. During Q4 it could eat half a day to a full day of one person's time, every day. "It's just something that no one wants to do," Nick says. "The person doing it is also miserable. It's just not fun."

Gavin Sorey, Tipsy Elves' Chief of Staff, remembers peak periods when the broader reconciliation process consumed roughly 40 labor-hours in a day.

Agentway now runs that check automatically across orders. Instead of asking a person to inspect thousands of records, the system compares the relevant state across the sales channels, NetSuite, the warehouse, and other systems, then surfaces the discrepancies.

“Making the decision is actually the easier part. It’s gathering the information into a place where they could decide what to do.”

Nick Morton, CEO, Tipsy Elves

An early run caught an order sitting in Shopify that neither NetSuite nor the warehouse had ever heard of. On the old model, the likely detection mechanism was an angry email a week later asking where the order was, potentially after the event it was bought for. Instead, the team fixed the order before it became a customer problem.

That's the basic pattern: do the exhaustive checking automatically, then give a person the few cases worth thinking about.

Establishing inventory truth at the exact SKU

Tipsy Elves deliberately sells the same physical inventory through more than one merchandising context. A jumpsuit shown as part of a matching family collection might also have its own listing for someone shopping for a Halloween bar crawl. The listings should look different to the customer, but splitting the physical inventory behind them would create unnecessary excess.

So a unisex product might live on its own product page for men and women, plus in a themed collection, and in a bundle, all pulling from one pool. Every listing looks fine on its own. The trouble hides in the relationships: two pages quietly disagreeing about how many units exist, a size that's sellable on the storefront but doesn't resolve in the ERP. Nobody notices until something oversells. "That always happens every year," Nick says. "It's an annual holiday of overselling top-selling stuff."

The standard defense is a low-stock report, which across a catalog like this flags so many items it might as well flag none. Agentway instead grouped every active listing by the exact size-level SKU it sells from, then checked whether Shopify, NetSuite, and the warehouse agree about that SKU. The first pass produced a dozen real discrepancies — few enough that a merchandiser checked them that morning and had firm warehouse counts back before lunch. The other several thousand SKUs got confirmed as boring and stable, which is what everyone wanted them to be.

Customer support is where problems show up first

The partnership began in customer support, which is still where operational problems tend to surface earliest. "Customer service is the eyes and ears for any issues that are happening," Gavin says. A wrong shirt might be a warehouse pick error, or a returns bin restocked wrong, or a vendor label problem. A delayed order might mean the delivery promise and the fulfillment handoff have drifted apart.

None of this was Agentway's idea, strictly speaking. "We've been talking about doing this kind of thing on the customer service side for a long time," Nick says. "We just haven't been able to get to it."

In one case, a customer received the wrong size of a shirt he needed for a golf tournament and was flying to another city the following day. The team got the customer taken care of first: a replacement was created, expedited to his destination, and given a guaranteed arrival before the tournament.

But the interaction didn't end there. The workflow also preserved the evidence needed to investigate why the wrong item had shipped in the first place, so the same customer problem could become useful operational information rather than disappearing when the ticket closed.

Give people visibility, not more things to watch

As the work expanded, the reporting rhythm got tuned to decision speed.

Urgent order and fulfillment exceptions surface immediately during the day. Inventory reconciliation runs across the catalog overnight. Support patterns get reviewed weekly or monthly, depending on the season. Leadership gets a regular view of where problems are appearing without reading every ticket or inspecting every order.

“We’d hear it if it got really bad”, Nick says. “It’s nice to just get a weekly check-in.”

"The point of having this visibility is to not have to read through every ticket," Gavin adds.

A smaller team with more time to think

Tipsy Elves keeps expanding beyond the Christmas business it became famous for: Halloween, ski, vacation, golf, and other occasions all create their own products, operational wrinkles, and seasonal peaks. Historically that meant another set of processes for somebody on the team to absorb. Now more of that work becomes automatic systems before it becomes headcount.

Nick believes the next generation of ecommerce companies will operate with much smaller teams. The limiting factor, in his view, will not be how many tasks a company can automate, but whether its leaders retain enough time for oversight and strategy.

That's the operating model Tipsy Elves and Agentway are building together. Automate the exhaustive checking, keep people at the consequential decision points, and catch problems while there is still time to do something about them.

And give a small team more of its time back to think about what comes next.

Company: Tipsy Elves, a clothing brand known for bold holiday and occasion wear
Channels: Amazon, Shopify, Target, Wholesale
Stack: Shopify, Amazon Seller Central, NetSuite, Stord, Zendesk, Monday.com, Google Workspace, and Slack, with Agentway as the operating layer across support, inventory, and order reconciliation

Your operations probably rhyme with these

If any of this sounded familiar, that's the point. We start with an audit of your workflows, build the first automation against your existing process, and prove it before it runs on its own.