What to Do When a Custom Shopify Order Stalls Waiting on Customer Approval

The orders nobody wants to deal with

Every store with a custom proofing workflow has a small pile of them. Orders that sat at "design ready" or "pending" four days ago, then six, then nine, and are now bumping up against the point where the customer is going to be annoyed no matter what you do.

You cannot ship them, because you do not have an approval. You cannot refund them, because the customer has not asked you to. You cannot ignore them, because each one is a potential support ticket, a potential chargeback, and a real cost in designer time already spent.

This post is a triage playbook for that pile.

Why orders stall

There are only a few real reasons a custom order sits in approval limbo, and the right response depends on which one applies.

• The customer never saw the email. It went to spam, or to an inbox they do not check, or to a mistyped address. They genuinely do not know they have a proof to look at.
• The customer saw it and forgot. They opened the email on a phone, meant to come back to it later, and never did. This is by far the most common case.
• The customer is undecided. They have looked at the proof multiple times and cannot decide whether to approve or ask for changes. The order is stalled because the customer is.
• The customer's plans changed. The event got moved, the recipient backed out, the project shifted. They are not sure what they want anymore, and avoidance is easier than telling you.
• The customer changed their mind about the purchase. They are not going to say so. They are hoping the order quietly goes away.

The reminder ladder

The first 5 to 7 days of a stall are not really a triage problem. They are a reminder problem. A working ladder looks like this:

• Day 0: initial proof email. Specific subject line including the order number and the customer's name.
• Day 2: first reminder. Friendly, short, link to the approval page. No mention of any policy.
• Day 4: second reminder. Mention the auto-approval date if you have one, or just mention that the order is held until you hear back.
• Day 6: third reminder. Keep it short.
• Day 8: fourth reminder. This is your last automated touch. After this, the order moves into the manual triage queue.

If the customer has not responded after four reminders, more email is not going to help. That is the point at which the order moves out of the automated queue and into manual triage.

When to call

The single highest-leverage action on a stalled order is a phone call, and almost no merchant does it. By day 7 or 8, an automated email has had its chance and not landed. A real human voice cuts through.

Make the call short and warm. Confirm you have their order, confirm you sent a proof, ask if they had any feedback. Most stalled customers respond with relief: "Oh, I meant to look at that, sorry." A handful tell you they have changed their mind, which is also useful information you would not otherwise get.

Worth calling: orders over a certain dollar threshold (set it where the call is cheaper than the lost revenue), wedding and event orders where the deadline is fixed, and any order from a repeat customer.

Not worth calling: orders below your threshold, marketplace customers where you do not have a number, anything where the customer's profile suggests they would prefer email.

When to auto-approve, when to refund, when to ship anyway

By day 10 to 14 you have to make a call. Three options, with the conditions that fit each one.

• Auto-approve and ship the original design. Use this when the product is low-stakes, the policy was disclosed up front, and the order has nothing time-sensitive about it. The customer will most likely receive what they asked for and never raise it. State the policy in your reminder emails so the auto-approval is not a surprise.
• Refund and close. Use this when the moment has passed (event date gone), when the customer's history suggests they are likely to dispute, or when the product is high-stakes (engraved jewelry, memorial pieces, custom signage). Send a polite cancellation email: "We have not been able to confirm your design with you, so we have refunded your order. If you would like to reorder, here is a link." Do not require a response.
• Hold and keep trying. Use this only when the order is high-value enough to justify your time, the product is high-stakes, and you have a real reason to think the customer will eventually return. Have a stop date for this, otherwise it becomes the pile.

The wrong move is leaving the order in limbo. Limbo costs you money every day it sits there, in dashboard noise, in returning to the same order in your head, and in the eventual support ticket.

Instrument your store so stalls are visible

Most stores find out about stalls by accident, usually when a customer finally writes in or a designer asks "what do you want to do with #1043?" That is too late. A few small instrument changes make stalls visible early.

• Status counts on your dashboard. If you can see at a glance how many orders are in each state, you can spot a stall pile growing before it becomes a fire.
• An overdue threshold. Any order in "design ready" or "rejected" beyond a defined number of hours flips into an overdue state. You scan for the overdue badges, not for individual orders.
• A weekly review. Once a week, walk through every order older than your threshold and assign each one a next action: reminder, call, refund, ship. Five minutes for ten orders. It is the cheapest meeting you will run.
• An internal comment on the order. Anything that is not strictly a status (a customer's offhand comment, a designer's hunch about the file) goes in an internal comment. Future you, or the teammate who picks the order up, will be glad of it.

The point of all of this is to stop discovering stalled orders. Once you can see them, you can triage them.

How ApprovePro helps with stalled orders

ApprovePro is built to take most of this work off your plate. The customer reminder cadence is a setting on the account, configurable from 1 to 14 days, and on Premium and above you can turn on recurring reminders that re-send on the same cadence, capped at four total sends and never past 28 days. That is the automated portion of the ladder above, running without any inbox work from you.

The dashboard shows status counts at the top of the orders list, so the size of your stall pile is the first thing you see when you open the app. You can also configure an overdue threshold (off, or 12 hours through 7 days) which flags any order that has sat in awaiting design, design ready, or partially approved beyond your chosen window. The flag is visual, and the orders list has a Due filter with an "In Past" option so you can pull up just the overdue pile in one click during your weekly review.

ApprovePro also tells you whether the customer has actually seen the proof. The order detail shows when the customer last viewed the revision, so you can tell the difference between "they have not opened it" (send another reminder, or check the email address) and "they have looked at it three times and still not decided" (time to call). On top of that, ApprovePro notifies you if any of the proof emails to the customer bounce, so a mistyped or dead address shows up immediately instead of looking like a silent stall.

For the cases where a customer approves and then has second thoughts, the approval page includes a configurable revert window (10 minutes, 30 minutes, 1 hour, 2 hours, 6 hours, 12 hours, or 24 hours) so they can change their decision inside that period without you reopening the order by hand. That covers the "I was about to ask for one more change" case that often becomes a support ticket otherwise.

For the orders that genuinely will not respond, you can set an auto-approval interval (1 to 14 days, or off) so low-stakes products do not sit in your dashboard forever. Auto-approval moves the order to the same approved state as a customer-clicked approval, with the same automatic order tagging, and the order's history records it as "Auto approved" so you can tell which approvals came from the timer. For high-stakes products where auto-approval is not appropriate, leave it off and rely on reminders plus manual triage.

The combination, recurring reminders, status counts, an overdue flag, a revert window, and a configurable auto-approval, is enough to keep most stalls from ever becoming a triage problem in the first place.

Final takeaway

Stalled approvals are not a customer problem and they are not a designer problem. They are an operations problem, and like every operations problem they get cheaper when you have a clear playbook for them. Run a sensible reminder ladder, escalate the high-value orders to a phone call, read the line item properties to figure out what is really going on, and decide between auto-approve, refund, and hold based on the stakes of the product and the signals in the order.

The stall pile never goes to zero. The point is to keep it small, fresh, and moving, instead of letting it become the part of your store you avoid looking at.

If you want to handle stalled approvals with reminders, an overdue flag, and an auto-approval safety net working together, see how ApprovePro keeps custom orders moving on your Shopify store.