“This is gonna unlock seven figures of purely incremental revenue for us.”
The most common message in Ridge's support inbox is also one of the least interesting to read. A customer has placed an order, noticed shortly afterwards that the shipping address is an old apartment or a former office, and written in to ask for it to be changed before the parcel leaves the warehouse. Shop Pay and other saved-checkout tools make this easy to do by accident; a customer who has moved recently and checks out quickly may not look at the address field at all.
Will Moran, who works on the ecommerce team at Ridge, has been on the receiving end of it himself. Ridge sells premium everyday carry, best known for the Ridge wallet but extending to power banks, travel gear, luggage and rings, and the order values are high enough that a misdirected parcel is more than a minor inconvenience.
"The cart is five hundred, six hundred dollars, you send it to the wrong address. It's panic. It's high, high anxiety inducing."
Multiplied across a large direct-to-consumer brand in a peak quarter, that individual moment becomes an operational problem. Thousands of customers a month were writing in with address changes, cancellations and order updates, and each of them was waiting, sometimes for the better part of a day, for someone at Ridge to act. The question the ecommerce team took into Q4 planning was what to do about the gap between the customer noticing the mistake and Ridge being able to fix it.
The antagonist: a queue that only a few people could touch
Like most large direct-to-consumer brands, Ridge's support load is heavily seasonal, and the real pressure arrives in November rather than July.
"Leading up to peak Q4, being a larger DTC brand that handles a ton of inbound volume in those peak periods, we might see thousands of CX tickets a month for things like order updates, cancellations, address edits, things like that."
On paper, an address change is a trivial ticket. In practice, it was one of the most expensive tickets Ridge handled, for two reasons that compounded each other.
The first was time. Every edit meant an agent jumping between the helpdesk and Shopify, adjusting the order, and then confirming that the fulfilment centre had received the right information before the box left the building.
"These tickets are also very high-touch, high-leverage tickets, and so that eats up a lot of time for our CX team."
The second was permission. Not every agent at Ridge was set up to make those edits at all. As Will's colleague Megan had pointed out, "not all of our CX agents have permissions in our setup to actually do those edits. So it's not only volume on the team, but it's a select few people that would otherwise have to do it." The bottleneck was not the team as a whole but a handful of people inside it, and every peak season funnelled thousands of customer requests through them.
Behind that sat a related, quieter problem. Orders with questionable addresses were dropping into a hold queue, and someone was working through that queue "manually, having to resolve one by one." Return-to-sender shipments were a cost that nobody enjoyed measuring.
"When you're in that panic mode as a customer, we've all been there. Twelve hours, twenty-four hours is otherwise a great response time. But it's just really nice to be able to get that resolution right away."
Will is careful about how he frames the origin story. He does not describe it as a crisis. He describes it as a piece of preparation. "The Order Editing origin started with helping out our CX team," he says.
"Really just wanted to set them up for success. And that led us to looking for solutions to kind of redirect some of those high-volume, high-touch tickets."
Redirect is the operative word, and it turned out to be a more precise one than most brands use.
The paradigm shift: redirect, don't reduce
The conventional way to attack a support queue is to answer it faster, with better macros, more agents and tighter SLAs. Ridge already had a good response time. What the team recognised was that speed was not the variable that mattered most to a customer who had just noticed a wrong address; the ability to act on it themselves was.
Order Editing inverted the model. Instead of the customer describing the problem to Ridge and waiting for a permitted agent to fix it, the customer fixes it themselves, on the order status page, as soon as they notice the mistake. The address change, the size swap, the cancellation, all of it happens without a ticket ever being created and without a human ever needing to be involved.
"What's great with Order Editing is that customer can just jump right in, fix the issue, and skip all the drama."
The distinction that separates this from a chatbot or a self-help article is that the edit is not a request queued for someone else to action; it writes back to Shopify directly and flows through to fulfilment. The select few people who used to hold the keys are no longer the bottleneck, because the keys have been handed, safely and within limits Ridge controls, to the customer.
Ridge added a second layer at the front of the funnel: address validation at checkout. Rather than catching a bad address after the order was placed and parking it in a manual hold queue, the address is checked before the customer ever hits "place order." Will describes it as solving two problems at once.
"It helps us keep our operational cost down associated with things like return to sender, and it also gives customers the confidence they need at checkout, knowing that their items are going to the right place."
The crucible: numbers that were bigger than anyone expected
The implementation itself was uneventful. Will's own note about the post-purchase upsell feature was blunt: "incredibly easy to set up." It sat cleanly alongside the tools Ridge already ran, including Klaviyo and an existing on-site upsell stack.
What did surprise the team was the dashboard. Ridge had a working assumption about how many customers wanted to change their orders, and that assumption was built from the tickets that reached the inbox. Once customers had a frictionless way to make an edit, the volume that surfaced was startling. "Since having it and seeing the dashboard, it's like the problem is almost bigger than we thought it was," Will says.
"You see people making edits that maybe they wouldn't have reached out otherwise. It never would have gotten attributed as a ticket, but now because they have that easy option, there's all these problems that we didn't even know existed."
Some of those customers would previously have emailed. Many would simply have lived with a wrong address or an unwanted item and, presumably, thought a little less of the brand, without Ridge ever finding out.
"Something that surprised us at Ridge is just the sheer volume of edits being made. Going into that dashboard and seeing 5,000 order edits being made per month is pretty crazy. Each one of those would otherwise be a ticket that has the potential to land in the CX inbox."
The honest version of the story, which Will and the Order Editing team talked through on camera, is that inbound to the inbox has not vanished. Some customers still miss the self-service window and write in. What has changed is where the bulk of the demand goes. In a month like May, Ridge saw more than 5,000 self-serve edits; in June, just shy of it. Peak season is expected to double that. Against a comparable pool of order-related contacts, the team estimates around 80% now never become a ticket at all.
The aftermath: a support tool that became a revenue channel
This is where the Ridge story diverges from a typical customer-service case study.
Ridge already ran a robust upsell programme. Customers were passing through a substantial sequence of offers before they ever reached the order confirmation. The reasonable expectation was that a post-purchase upsell on the order status page would find the well already dry. The opposite happened.
"One of the biggest unlocks on the CRO side this year. Purely incremental revenue that we would have been passing up otherwise."
The mechanics were straightforward once the team saw them. Customers return to the order status page repeatedly in the days after a purchase, and Ridge's Klaviyo post-purchase email now deliberately sends them there, with the upsell offer featured in the email itself. The conversion rate is modest, in the region of one percent, but at Ridge's scale that is thousands of orders a month that would otherwise not have existed.
The result is a channel that is now generating over a million dollars a year in purely incremental revenue, from an email flow and an order status page that most brands treat as an afterthought.
"This is gonna unlock seven figures of purely incremental revenue for us. We love the post-purchase order status page upsells because we're able to use our email flows to then drive eyeballs back to the order status page, creating more upsell revenue."
That figure is worth restating plainly. Ridge already had a mature upsell stack, and the widespread assumption is that a brand in that position has little left to capture after checkout. The post-purchase email upsell added seven figures on top of it.
"Incredibly easy to set up."
Taken together, the outcome looks like this: roughly 80% of order-related tickets are now redirected away from a team that used to route them through a handful of permissioned agents; around 5,000 self-serve edits a month are being made, on course to double in Q4; the manual address hold queue has shrunk because problems are caught at checkout, with return-to-sender costs down as a result; and a post-purchase email upsell that took little effort to switch on is now producing over a million dollars a year in incremental revenue.
There is also the part Will keeps returning to, which never appears in a dashboard. "The other piece that doesn't show up in our analytics is going to be that customer, right in that panic moment, now able to self-service and solve that issue."
The partnership
Ridge evaluates software vendors with a specific lens, and Will was candid that the product is only half of it. "There's the technical, the app piece, and then there's also the partnership." He and his colleague Lexi weigh the second nearly as heavily as the first. "If you have an app that's even critical, and you can't get even just mediocre service out of it, it's just the worst."
Order Editing passed that test in a way that clearly mattered to him.
"Since partnering with Order Editing, we not only love the app, but we also love their team. They're always willing to answer the Slack message, go the extra mile, solve any of the issues we may have."
Then, near the end of the session, an aside that says more than any scripted testimonial could:
"One of our favourite things about Order Editing is working with their team. We genuinely enjoy it. And to prove that, I'm here on my day off."
The takeaway
The Ridge story is usually filed under customer support, and it deserves that label. But the more interesting lesson is about what a support ticket actually is. For years, ecommerce brands have treated the inbox as a measure of demand for help. Ridge's dashboard suggests it was only ever a measure of who was willing to ask.
When customers are given the ability to fix their own orders, two things happen at once: the worried ones get their resolution without waiting, and the ones who would never have written in finally become visible. When they are also given a reason to return to the order status page, a third thing follows, which is that the period immediately after purchase turns out to be one of the more valuable pieces of real estate a brand owns.
Will's summary is the tidiest version.
"Order Editing has been a huge win for Ridge because we're creating incremental revenue, solving CX issues, and have a partner that's truly invested in Ridge's success."
Three outcomes, from a decision that was originally made just to help the CX team get through Q4.
