The order came in on Monday. You clicked Request fulfillment, your warehouse accepted it inside the hour, and Shopify changed the status to In progress.
It is Friday. The status still says In progress. No tracking, no shipment, no message from anyone, and a customer who paid five days ago.
There is no Mark as fulfilled button on that order any more. There is no counter telling you it has been five days. Shopify is reporting, accurately, that something is being processed.
The short answer
In progress is not a stage of work. It is a statement about who is holding the order, and it stays true for as long as they hold it. Shopify sets it when you send the request and leaves it there, so the badge reads the same on day one and on day ninety.
Accepting the request also takes your tools away. You cannot mark the order fulfilled, cannot mark it in progress yourself, cannot edit it or refund items, and the cancel action you can reach does not stop a fulfillment that is already in progress. Getting the order back means asking the service and waiting for it to agree.
And nothing is counting the days. Shopify stores no acceptance time, sets no deadline and raises no alert, so the only way to know an order has been still for a week is to have written down what the queue looked like every day before. That is the whole job: read every open fulfillment order daily, keep your own clock, compare.
In progress means somebody else has it
The mechanism is documented and easy to misread as a progress bar. Shopify's page on fulfilling orders with a fulfillment service says that when you request a fulfillment the status changes to In progress and you need to wait for a response from your fulfillment service. The service then either accepts or declines, and the outcome is noted in the order timeline.
A decline has a clean ending: the order status returns to Unfulfilled, and the service can leave a note explaining why. An acceptance has no ending at all. The status moves to In progress and stays there until a shipment appears, which may be tomorrow, or may be never, and the two look identical from where you are sitting.
So one badge covers two completely different situations. Nobody at the warehouse has answered your request yet, which is normal for an hour and a problem after a day. Or somebody answered yes and then did nothing, which is a problem immediately. The admin does tell them apart: for an order that is In progress, the detailed status says whether the fulfillment is Requested or Accepted. That is the single most useful field in this whole story, and it sits one click inside each order, on a page you have to open to read.
What the admin takes away when the request is accepted
Both help pages say this plainly, and together they explain why the obvious fix never works. The Mark as fulfilled button is not available on orders assigned to fulfillment service locations. And if an order is assigned to a third-party fulfillment service you cannot manually mark it as fulfilled or in progress, because the service controls the status and marks the order in progress automatically when it accepts your request.
Two more restrictions arrive with the request. Once it is sent you can no longer edit the order or refund items. And cancelling a fulfillment in your Shopify admin does not stop a fulfillment that is in progress, which means the cancel action you can reach is not the one you want.
What is left is a social process rather than a setting. Before the service accepts, the admin offers Cancel request and the order goes back to Unfulfilled. After it accepts, you use Request cancellation and wait for somebody else to agree; if they reject it, the fulfillment carries on. There is a Revert to unfulfilled action for the case where the service cancelled but could not update Shopify, and the help page is blunt about what it does not do: reverting an order to unfulfilled does not stop your fulfillment service from fulfilling the order. Use it without confirming the cancellation first and the likely result is a shipment you get billed for and a customer who receives the goods twice.
Nothing in Shopify is counting the days
This is the part that turns an annoyance into a leak. Go looking for the field that says how long an order has been accepted and unshipped, and it is not there.
The
FulfillmentOrderStatus
enum gives IN_PROGRESS one line: the fulfillment order is
being processed. The
request
status is where the real detail lives, with SUBMITTED
for a request the merchant has sent, ACCEPTED for one the
service took, REJECTED for one it refused, and
CLOSED, which means the fulfillment service closed the
fulfillment order without completing it. Those are states, not
timestamps.
The fulfillment order itself carries createdAt, the date and
time it was created, updatedAt, the date and time it was
last updated, and fulfillBy, the latest date and time by
which all items need to be fulfilled. There is no accepted at. Nothing
promises that updatedAt moves on every state change, and
even if it did, it moves for a dozen other reasons too.
The
fulfillmentOrders
query can filter on status, updated_at,
assigned_location_id and id, and excludes closed fulfillment
orders unless you ask for them. So Shopify can answer which of your
orders are in progress. It cannot answer which of them have been in
progress since Tuesday. That answer only exists if somebody wrote
Tuesday down.
The closest thing to a clock on your side is
merchantRequests, the list of requests sent by the merchant
or an order management app to the fulfillment service for that
fulfillment order. Useful, and still your record of what you asked for
rather than a record of what they did with it.
The threads say the same thing three years apart
October 2023. A merchant posts that they updated orders as fulfilled and the status is still showing in progress. The orders were paid and delivered. The diagnosis, from another community member, is exactly right: the fulfillment order is with a third-party service, so rather than fulfilling the item the admin is requesting fulfillment, which puts it in progress. The fix offered is to cancel, move the fulfillment order to a location the merchant manages, then mark it fulfilled.
January 2024. An order has been paid and fulfilled in full but the fulfillment status still says in progress. The third-party fulfiller shows the item as fulfilled. The merchant tried cancelling the request, tried marking the item fulfilled, and re-synced with the supplier multiple times with no resolution. Same answer, same location workaround.
April 2024. A merchant writes that the orders keep saying Still In Progress, that they are paid in full, that fulfillment was requested, and that they have no information for customers. They ask whether this is their own mistake or the dropshipping supplier's, which is the question the admin should answer and does not. The reply is the correct one and also the end of the road: if it says In progress, the fulfillment service assigned to that order has not yet fulfilled it, or has not updated Shopify. The merchant said they would take those steps. There is no follow up.
Three threads, three years, one volunteer answering all of them, no Shopify staff reply on any of the pages, and not one confirmed resolution. The recommended fix in every case is to take the order back by hand, one order at a time, by reassigning its location. That is a workaround for a store with one stuck order. It is not a process.
And you cannot filter it out of your queue
In October 2026 a merchant filed the request that names the operational half of this problem. They wanted a view of orders whose fulfillment work has not started, and reported that filtering for Unfulfilled still includes orders displayed as In progress, while the Fulfillment status is not filter offers Fulfilled, Partially fulfilled, Scheduled, On hold and Declined, and does not offer In progress. The request is open, with no Shopify answer on the page.
Read that as a packing queue rather than as a filter bug. Your Unfulfilled view holds two kinds of work that need opposite actions: orders somebody at your end can pick right now, and orders you are waiting on a third party for. You cannot separate them, and you cannot subtract the second kind. So every morning the queue overstates the work you can actually do, and the orders you are waiting on hide in the middle of it looking like everything else.
The workaround in that thread is to tag an order when its fulfillment order moves to in progress and then filter on the tag. It works. It also means a state Shopify already knows has to be copied into a field you maintain before anybody can use it, which is a fair description of most of the automation on most Shopify stores.
The order level status can disagree with the admin
One more trap, and it is the reason the obvious alert does not fire. In December 2025 a developer reported that on a staging store the admin showed the physical products in the process of being delivered and the timeline showed fulfillment had been initiated, while the API returned UNFULFILLED and the fulfillments object was empty.
They answered it themselves the next day. The in progress status at the order level is set when all line items have the in progress status, and to see a single item's state you look at its fulfillment group rather than at the order. Shopify's reply thanked them for posting the answer.
The operational lesson is worth more than the API detail. Any alert built on the order level fulfillment status will miss every order where only part of the request was accepted, which is the normal shape of an order split across two locations. Read the fulfillment orders, one per location, and the order level summary stops mattering.
What it costs while it sits there
The customer side is the one you hear about. The order is paid, silent and five days old, and the person who paid writes in to ask where it is. You open the order and you are as uninformed as they are, because the only record of what happened is a timeline on that one order and the only next step is an email to the warehouse. The reply you can send is that you are checking, which is the reply nobody wants.
The money side is quieter. You cannot refund items on a requested fulfillment, so a cancellation you owe somebody waits on a third party answering their email. If the goods actually shipped and nobody reported it, the order sits open in your store until somebody decides to reship it. And if you reach for Revert to unfulfilled without confirming the cancellation, you can pay for two shipments of the same order and give one of them away.
None of this is expensive on one order. All of it is expensive on half a percent of orders for a quarter, which is what it becomes when nothing is watching, because the orders that stall are invisible by construction: they look like work in progress, and work in progress is the one state nobody investigates.
What the automation actually has to do
As a Dugong playbook, in plain prose:
# trigger
Daily pass over every open
fulfillment order
# steps
1. Read fulfillment orders, not
orders
2. Age each one from your own
record
3. Split the waiting from the
accepted
4. Check whether any shipment
exists
5. Chase the service with the
order in hand
6. Take the order back the only
way Shopify allows
7. Tell the customer before they
ask
Step one is the unit of work. An order can hold several fulfillment orders, one per assigned location, and each has its own status and its own request status. Reading the order level summary is what produced the December 2025 confusion, and it hides exactly the case you care about, the order where one location shipped and the other said yes and stopped.
Step two is the part only you can do. Store today's set of open fulfillment orders with their statuses, every day, and the age of a stall becomes a subtraction instead of a guess. This is unglamorous and it is the whole reason the defect goes unnoticed: Shopify can tell you the state and cannot tell you the duration, so duration has to be kept somewhere.
Step three is the triage that makes the list actionable. A request still sitting at submitted is a conversation about responsiveness with your warehouse. One sitting at accepted with nothing shipped is a conversation about a specific order, and it is more urgent, because somebody has already promised. Those two lists go to different places and should never arrive as one alert.
Step four is the check that catches the dishonest case. An order can be fully packed, shipped and delivered while Shopify still says In progress, which is what two of those three threads were actually about. Ask whether any fulfillment exists for that fulfillment order, and whether tracking was ever attached, before you tell anybody it has not shipped. Adding or updating tracking is allowed at any time regardless of who created the fulfillment, so this is also often the cheapest repair.
Step five is the chase, and it should arrive as evidence rather than as a question. The warehouse gets the order name, the fulfillment order, the date the request went out, how long it has been accepted and whether any shipment exists, in one message. A 3PL can act on that in a minute. A message asking whether they have seen order 10412 starts a thread.
Step six is the recovery, and it is the step that should always involve a person. Cancel request before acceptance is safe. Request cancellation after it is a negotiation. Revert to unfulfilled without written confirmation is how you ship twice. Automate the preparation of all three and let somebody press the button.
Step seven is the part that pays for the rest. The customer should hear about a five day stall from you, with what you know and what you are doing, before they write in. The same detection that feeds the warehouse chase feeds that email, and the email costs nothing once the detection exists.
Do this before you close the laptop
Three things, about twenty minutes, no tooling required.
Open your orders, filter to Unfulfilled, and read the status chips rather than the count. Every row that says In progress is an order you are waiting on somebody for. Open the oldest three and look at the detailed status on each: Requested means nobody has answered, Accepted means somebody said yes. Write the order numbers down, because today's list is the first entry in the record Shopify does not keep.
Then take the oldest one that says Accepted and check the timeline for the date the request went out. That number, in days, is the honest measure of how long this has been invisible in your store. In most stores that have a 3PL it is longer than anybody would have guessed, and the order is usually either shipped and unreported or genuinely lost.
Last, send your warehouse one message listing every In progress order older than three days, with the request dates. Their answer tells you which of the two failures you have: a service that is slow to accept, or a service that accepts and forgets. Those need different conversations, and most stores have never separated them.
If you run a store with a version of this story, the order that sat at In
progress for three weeks, the 3PL that accepts everything and ships most
of it, the shipment that arrived before Shopify ever admitted it existed,
the inbox is open: field-notes@dugong.live. We are
collecting case studies for the next issue.