A By Janson Wang , Founder of ASG Dropshipping · September 13, 2026 · 21 min read
Editorial cover design for this article; not a warehouse photograph or operational evidence. You typed a number into one field. Your warehouse in Guangdong runs a sequence of actions. Nobody at checkout sees the sequence — they see the number, and they hold you to it.
Enter the span your own records cover: order placed to carrier handoff. Shopify states that transit time “doesn’t account for order processing time”, so carrier speed cannot fill that field — your China warehouse lead time fills it. Before you change the number, check three things in your own admin: which two events your timestamps name, which days each system counts as working, and what time each rolls an order into tomorrow. Then confirm the actual handoff arrangement with your warehouse and your carrier.
Key Takeaways
The field holds four named actions , in Shopify’s words: reviewing the order, printing labels, packaging, handing the shipment to a carrier. Shopify says transit time excludes that span.Two parties can check the number afterwards. Under 16 CFR 435.2(a)(4), a respondent-seller who cannot produce documentary proof in an FTC enforcement action faces a rebuttable presumption that no basis existed. Google separately scores the speeds it serves for you.
The setting covers one span between two named events. Diagnostic points sit inside it; transit sits outside it. You have had this argument with a customer. They paid for two-day shipping. The parcel arrived on day six. They were not wrong about the two days. Neither were you.
Direct answer — the date your customer reads is two spans added together. The first ends when you hand the parcel over. The second starts there.
Shopify defines processing time as “the time between when a customer places an order and when you fulfill it”, then fixes the moment of fulfillment : orders that require shipping “are considered fulfilled when the business gives the shipment to a shipping carrier service”.
One naming note: the pages quoted here read processing time in August 2026; the same URLs now use fulfillment time
Order Processing Time vs Transit Time: The Two Endpoints You Are Promising
Endpoint
The event it names
Where the timestamp usually lives
If you cannot get it
Start The customer places the order
Your Shopify admin, with its timezone
You have this one. Record the timezone beside it
End “the business gives the shipment to a shipping carrier service”
A signed handover document, or a carrier event you confirmed means they took the parcel
Ask your warehouse and carrier, in writing, which record marks the handover
Look — that second row is where sheets quietly go wrong. A carrier’s first scan is not automatically the handover: it can be raised at a drop-off point, at an agent’s counter, or on first read in a sorting facility. Confirm which event type in your carrier’s data means the parcel was in their possession, then write that event type into your sheet.
The carrier’s span starts where yours stops. Shopify defines transit time as the span “from when your shipping carrier collects the shipment from you, to when the shipment arrives at your customer’s address”, then settles the argument in one sentence:
“Transit time doesn’t account for order processing time.”
Two spans, two owners, one date at checkout. When that date is wrong the customer blames the shipping label, and the error can sit upstream.
Dispatch station with staff preparing shipments. Most people read that field as a buffer. It is a container, and Shopify says what is in it.
The setting covers four named actions, not one waiting period: reviewing, labelling, packing, handing over. Whether Shopify turns it into a date your customer sees depends on where your fulfillment location sits and how your shipping rates are produced.
Verbatim from Shopify’s page on processing time:
“Reviewing an order, printing shipping labels, packaging products, and handing over shipments to a shipping carrier all contribute to an order’s processing time.”
Four actions. One input box. The same page is blunt about outsourced fulfillment:
“If you dropship, then your only control is over which suppliers you work with and how quickly you place your orders with them.”
That field is a claim about somebody else’s building.
The allowed values, from Shopify’s own overview : same business day, next business day, 2 business days, or a custom value of “3 to 40 business days, or 1 to 8 weeks”.
Here’s the thing — whether that value becomes a date at checkout is a separate question, and it is gated.
What the Shopify Processing Time Setting Covers, and Who Can Actually Use It
Feature
What Shopify requires of your setup, quoted
What it produces
Automated delivery dates “an active fulfillment location within an eligible country” plus one fulfilled domestic order. The overview page instead says “active US fulfillment location” and one fulfilled US domestic order
“a date-specific estimate based on historical fulfillment and shipment transit data, not a carrier-provided estimate”
Manual delivery dates An origin country on Shopify’s list — for flat rates with transit time: “Canada, United States, United Kingdom, France, Italy, Spain, Germany, Australia”, narrower for the other two rate types. Also: “Delivery dates don’t work with shipping rates provided by third-party apps”
A calculated delivery date range at checkout
Row one carries a disagreement between two Shopify pages, and I am not picking the convenient half: the automated dates page lists the US plus a long set of European countries, while the overview states it as a US location and a US domestic order. The range is what I can support, not one end.
Check your actual fulfillment origin and your shipping-rate type before counting on either path. Both are gated by origin country, and the manual delivery dates page adds a gate the overview does not mention: manual delivery dates do not work with shipping rates provided by third-party apps, a common setup for cross-border sellers. The overview does describe the manual path as the documented option for stores shipping from outside the US. Accurate, but not the whole restriction.
What I am not saying, and why. We read eligibility lists; we tested no live store, and nothing here reports what your admin will do today. So the honest statement is that China does not appear in the lists we read — and that these lists change. Open both pages against your own configuration first. If neither fits, Shopify may not calculate a date at all, and your levers become the fulfillment-time number plus whatever you tell the customer off-platform.
Where that number gets republished
Shopify lists where the estimate reappears: checkout, accelerated checkout such as Shop Pay, the Thank You and Order Details pages, Shop app surfaces, and the order confirmation email. One of those lands in an inbox and stays there. The consequence is assigned in writing too:
“If a customer reports a damaged, incorrect, or late product, then it’s your responsibility to resolve the issue directly with the customer.”
You own the fallout — the same trap that shows up downstream in why tracking updates turn into a fulfillment bottleneck .
Change the number, then check every surface it reaches. Fixing the policy page fixes the least-read copy of the promise.
You set two business days. An order lands at 3 pm. Your team ships it next morning and feels fine. The estimate your customer saw started counting later than you think.
Four settings decide when “today” ends for an order, and they sit in four different places. Three are display settings; one is a booking deadline. Name the layer before you change anything.
Cut-offs, Timezones and Configuration Layers
Setting
What time it stops counting today
Whose timezone
Where you change it
Shopify fulfillment time “The business day cutoff time is 12 pm in the local timezone of the shipping origin”
The origin you configured
Shipping and delivery settings
Google Merchant Center, account level Left blank, “the default time will be 8:00 a.m. PST”
Pacific, until you set it
Merchant Center shipping settings
Google product feed handling_cutoff_timezone unspecified defaults “to the timezone of the shipping destination”The customer’s, until you set it
The shipping attribute in your feed
Carrier pickup booking UPS, on its Smart Pickup service: “If you process your first package after the cutoff, your UPS Smart Pickup service will be scheduled for the next business day”
The pickup location’s
Your carrier account
The first three are display settings: they decide what the customer is told. Shopify’s is a display cut-off — noon where the shipment leaves from, not where the customer is.
The fourth is a booking deadline: miss it and the collection moves. One named US service — an example of how such a deadline is worded, not a rule about yours.
And one more thing that neither the platforms nor that example records: the moment the parcel physically leaves, and whatever closes first on your side. Confirm the actual handoff arrangement with your warehouse and your carrier , in writing, and note which deadline closes earliest on your lane.
The two Google rows are different configuration layers, not one page contradicting itself: an account-level default for a cut-off left blank, and a feed-level default for a timezone never set. A merchant can configure one and forget the other.
The working week each system assumes
Shopify’s rule is one line: “Business days are considered Monday to Friday.” It adds that “Weekends and statutory holidays are included in the estimated delivery dates calculation.”
Google’s shipping attribute page tells merchants to use two feed attributes “if your handling and transit business days respectively aren’t the default Monday to Saturday”. Google’s account-level page carries a worked example that splits the halves inside one illustration: “0 – 1 handling days (fulfilled Monday – Friday) / 3 – 5 transit days (fulfilled Monday – Saturday)”.
So one page states a default of Monday to Saturday while another’s own example illustrates handling on a Monday-to-Friday week. Those sit at different layers, and I have not tested what an unconfigured account does — treat that as unknown. Configure both explicitly, then check the listing.
Run Shopify’s own worked example on that page — an illustration, no year given — and the arithmetic lands where nobody expects: two business days entered, eight or nine calendar days shown.
Write each of those four cut-offs down once, with its timezone. The platform settings decide what the customer is told; the booking deadline decides whether a collection happens today. Test your worst case first: a Friday afternoon order in a holiday week.
Packing and material preparation at the fulfillment bench. If your inventory sits in Guangdong, you have lived through that week. Nothing moves, and nobody warned the checkout page.
China’s working calendar comes from an official annual notice. It removes weekdays and it designates weekend days as working days, on named dates. A fixed Monday-to-Friday assumption is wrong in both directions.
The 2026 arrangement comes from the General Office of the State Council, document number Guo Ban Fa Ming Dian [2025] No. 7, published November 4, 2025 and carried the same day on the State Council’s English site .
Take February 2026 — already past by the time you read this — as the worked example, because the notice states it verbatim: Spring Festival ran nine days, February 15 to 23, “with adjusted working days; February 14 (Saturday) and 28 (Saturday) are designated as working days”.
Hold that against Shopify’s Monday-to-Friday rule. The two produce arithmetic, not opinion:
On February 14 and February 28, the national arrangement schedules a working day. A Monday-to-Friday calculation treats both as closed, so the estimate reads more pessimistic than the official arrangement.
Between February 16 and February 20, a Monday-to-Friday calculation counts five working days the official arrangement had removed. The estimate reads more optimistic than the official arrangement — in the week where a miss costs most.
What this section does not say. The notice is the national arrangement. It says nothing about what any individual warehouse does. A private operator may run reduced shifts through a holiday, or close longer than the official window. We found no authoritative source on that, so we are not telling you China warehouses are closed during any particular block. Ask your own partner for their shift plan, in writing, with dates.
Do this with the current notice, not with mine. The dates above are February 2026 and have passed. Each year’s arrangement is published separately and the designated working days move. Pull the notice covering your next promise window.
Put the current year’s designated working days and holiday blocks into whatever calendar drives your promises. Then decide, per block, whether to widen the number or pause the claim.
Here is where teams stall: they accept the number should be measured, then find they have no timestamps to measure it with.
Measure the whole span first — order placed to carrier handoff — then use stage records to explain where the time went. The elapsed span is the number. The stages are the diagnosis.
Your China warehouse lead time is not the sum of the touch times. It is the elapsed span between two events, and much of what sits inside it is waiting: for a batch to clear, for a picker to reach the line, for the day’s collection. Add up the steps and you will publish something you cannot hold.
Five decisions come first. Each is a place where two people produce two different numbers.
1. Pick your row unit and write it in the header. One row per parcel, each carrying its order id — one order can ship as two parcels with two handovers. If you report at order level, say which you mean: the last parcel’s handoff, or a split shipment you announced in advance.
2. Pick your queue by order date, not ship date. Take the orders placed inside your observation window. Taking the orders that shipped inside it quietly removes the slow ones, because the slow ones have not shipped yet.
3. Keep the unfinished rows, and keep them separate. Orders still open at your cut-off date have no end event — what you have is a lower bound. Report those rows and their bounds separately from the percentiles of the completed rows; a bound folded into a percentile reads as if the order finished. If a bound already exceeds the value you planned to publish, that row is the answer.
4. Decide how batch records enter. Incoming inspection on a lot is not a per-order stage — it can happen weeks before the order exists. Record it separately as a lot id and release date. The waiting still counts: if an order sat waiting for a lot to be released, that wait is inside the order-to-handoff span, even though the inspection event is not a per-order column.
5. Convert to business days last. Measure raw elapsed time, then replay the candidate value against the cut-off and working-week rules above. Dividing hours by 24 is not a business-day figure.
How to Measure Your China Warehouse Lead Time
Column
Required or diagnostic
What goes in it
Parcel id and order id Required
One row per parcel, linked to its order
Order placed Required
Timestamp with timezone, from your admin
Carrier handoff Required
Timestamp, plus the event type you confirmed means the carrier took it
Order released for fulfillment
Diagnostic
When payment clearing or manual review let the order go
Purchase order placed with supplier
Diagnostic
For items bought after the order was taken
Picked, packed, label printed
Diagnostic
Whichever your warehouse actually stamps
Lot id and release date
Diagnostic, not a per-order stage
Batch investigation only. Waiting on it still counts inside the span above
Calendar exception
Diagnostic
The holiday block or designated working day the row crossed
Two of those columns are yours. Most of the rest are not. Order placed comes from your admin; the handoff timestamp usually comes from the carrier or a signed document. The diagnostic columns typically live in your warehouse’s system, so a blank there is a missing agreement, not a measurement failure. Start with the required columns — you can publish from those alone.
One more gap, and for a China-origin store it is the biggest: these columns assume the unit is already in your warehouse. If you source after the order arrives, procurement and production sit in front of all of them — inside the span you publish, outside anything your warehouse can timestamp. Ask your supplier which record marks the order going to the factory.
Pull the orders placed in your last full month and fill the required columns. Sort by the gap between them and read the slowest rows, not the average. Whatever you cannot fill is a conversation with your warehouse, not a measurement problem.
Dispatch floor layout with material handling equipment. Two parties can ask you to show your work.
Direct answer — the FTC requires a reasonable basis for a stated shipping time. In an enforcement action brought by the FTC, a respondent-seller who cannot produce records faces a rebuttable presumption that no basis existed. Google separately scores the shipping speeds it serves for you.
From the FTC’s own business guide to the Mail, Internet, or Telephone Order Merchandise Rule:
“The Rule requires that when you advertise merchandise, you must have a reasonable basis for stating or implying that you can ship within a certain time. If you make no shipment statement, you must have a reasonable basis for believing that you can ship within 30 days.”
The guide reproduces 16 CFR 435.2(a)(4):
“In any action brought by the Federal Trade Commission, alleging a violation of this part, the failure of a respondent-seller to have records or other documentary proof establishing its use of systems and procedures which assure the shipment of merchandise … within any applicable time set forth in this part will create a rebuttable presumption that the seller lacked a reasonable basis for any expectation of shipment within said applicable time.”
Read the mechanism, and read the clause it opens with. This bites in an action brought by the FTC — the subject is a respondent-seller , a seller already on the receiving end of one. It is not a filing duty, not a retention statute, and not something a single unhappy buyer triggers. It decides who carries the burden once the regulator does ask.
Three boundaries, because the gap between this rule and your Shopify field is real:
The rule is about shipment statements , not the delivery date a platform calculates and displays. Whether a value you enter in an admin, which the platform converts into a customer-facing date, counts as advertising a shipping time is a question I have no source on. I am not asserting that it does.This is US jurisdiction, and this article is not legal advice. Whether the Rule reaches a seller established outside the US selling to US buyers is a further question I have no source on, and I am not answering it here.The sheet above is mine, not the rule’s. The rule says “records or other documentary proof establishing its use of systems and procedures” — it names no columns, and one month of rows is not a safe harbour. A reasonable basis also takes account of expected demand, supply, and fulfillment-system capacity.
The Rule also sets out what to do when you learn you cannot ship within the applicable time: offer the buyer the choice of consenting to a new date, or cancelling for a prompt refund. Act when you learn it, not only after the date has passed.
This is not a settings problem. It is a problem of evidence.
What Google does when your stated speed misses
Google calls it a Shipping Confidence Value. Its own page describes these as representing “the accuracy of the shipping speeds and costs that Google serves to users versus the shipping speeds and costs available on your website, order tracking history, and other sources”. Google gathers that mainly by crawling checkout, product and policy pages, and for select merchants by collecting order-tracking signals — not a per-order audit.
“Low CVs might lead to shipping speed or cost data being removed from your product listings or replaced with other available data that have higher CVs.”
Low values can also affect placement by influencing ranking models — so the shipping data attached to your listings can be replaced or suppressed, which is narrower than a listing being removed. Then the line that decides how to treat it:
“At this time, you cannot check your own confidence values.”
The truth is that changes the kind of problem this is. A metric you can read is something you optimise; a metric you cannot read is something you stay well inside — and “well inside” means accurate, not wide. A padded number your own pages contradict is still a mismatch.
That page covers Google Free listings and Shopping ads. We found no equivalent published requirement from Meta this run, and not finding a page is not the same as there being none.
Two merchants, on Shopify’s own forum, with names and dates attached.
HeretoSell, June 25 2021, in a thread about adding processing time before an item ships :
“A business can add info on pages all day long, and even send messages after the fact, but the fact is that the only thing that matters is the date they are staring at during checkout, and we need to make sure that they are given the best information possible to be able to make an informed decision about the shipping method that works best for them.”
Then the post closest to this article’s reader. DaveD, January 23 2023, in a thread asking how to set different delivery durations per origin :
“Since one of the warehouse is in China (I guess no surprise for you guys), I have to set t to 25 to 30 business days.”
The typos are his. Read it for what it is: one merchant describing what he had set for one origin, on one date, in a thread asking how to configure different durations per warehouse. Not a benchmark, not a verified measurement of any China warehouse, not a report of a solved problem — and two posts is not a prevalence measurement.
Read your own checkout as a customer, on a phone, today. Whatever date it shows is the promise you are making.
Full warehouse floor with scanning and sorting stations. The only decision that matters: what do you type into the field on Monday morning?
Choose, Apply and Recheck
What your records cover
What that supports
What it does not support
Order placed and a confirmed handoff event, across a full window
A value drawn from that measured span, export saved
A value tighter than the slow tail you measured
Intake and a confirmed carrier scan only
The wider span those two endpoints support
Anything narrower than those endpoints
Records that stop before the handoff
Only the pre-handoff step you can prove, stated as that step — “labelled within N days”
Your processing-time value. You have not measured to the handoff, and the gap between labelled and collected is un-evidenced, not zero
No usable endpoints at all
Two moves: get one pair of real endpoints, or keep your current number and stop describing it as measured
Widening the number. A wider guess is still a guess
A window crossing a holiday block or designated working day
The number, plus a stated calendar exception
A single year-round value
No row holds a day count: one borrowed from an article is not a measured warehouse lead time.
The strongest case for the other side, put properly. Configure a broad estimate and a lot goes right. The allowed ceiling is generous, so you can cover your worst week rather than your median one. Each “where is my order” email gets answered by pointing at a date the customer already accepted — cheaper than an apology. And you hide nothing: a wide date at checkout is the most honest thing a store with no timestamps can show a buyer, because it is a promise that store can keep. On that reading, measuring first is a luxury for sellers whose warehouse already exports timestamps.
Here is where that case holds, and where it stops. It holds on the conversation: a number you comfortably beat is easier to defend, and I am not telling you padding fails. It stops at the word safe. Whatever you enter is a stated time; the checkout date is where it lands, as HeretoSell said, and padding does not hide there. The consent-or-refund duty above runs against whatever shipping time you stated — subject to the boundary above on whether an admin value is such a statement — so a wide statement is still a statement. And the no-endpoints row holds: a wider guess is still a guess. The real question is not whether a broad estimate is safe — it is whether it is measured. A wide China warehouse lead time you can evidence beats a tight one you cannot; padding is a decision you make after you can measure. Re-measure when anything feeding the span moves: volume, a new SKU group, a new supplier, a new lane, a holiday block.
If you pad, pad on purpose. Write down the range you measured, then the slack you added, then why.
What to ask your warehouse for
Ask for records, not a number of hours. Hours are a claim; a record goes in a sheet.
The required timestamps, exported per parcel with order ids, for one real month
Which event type their system uses for the handover, and whether it means the carrier took the parcel
Lot ids and release dates for incoming inspection, so a batch hold can be traced without being counted as a per-order stage
Their written shift plan for the next holiday block, and any designated working days inside it
The deadlines they design around, and which closes earliest on their side
If a partner cannot produce the first two, that is your real ceiling — not the lead time quoted. Put the same list to us. We run China-side fulfillment for Shopify and WooCommerce brands, and I am deliberately not quoting our own timings here: a timing with no record behind it is a quoted number, ours included. More on where the pressure shows up first: why fulfillment breaks when Shopify order volume starts growing .
Fill the required columns for one month of your own orders first. If a column will not fill, ask us what it takes to close that one — the gap is the conversation, not your data.
Quick Answers About Processing Time and Lead Time
Does the processing-time value appear anywhere besides checkout?
Yes. It reaches the Thank You and Order Details pages, Shop app surfaces, and the order confirmation email — the copy the customer keeps.
Can a store shipping from China use Shopify’s automated delivery dates?
China does not appear in the eligibility lists we read, and those lists change. Check your own fulfillment origin and shipping-rate type first.
What creates a rebuttable presumption under the FTC rule?
Missing records. In an FTC enforcement action, a respondent-seller without documentary proof faces the presumption that no reasonable basis existed.
Can a merchant see their own Google shipping confidence value?
No. Google states you cannot check your own values, and low ones can lead to shipping data being replaced or suppressed.
Should a fixed Monday-to-Friday calendar be trusted for a China origin?
No. The official annual arrangement both removes weekdays and designates weekend days as working days. Check the current notice.
What is the difference between processing time and transit time? Two spans, not two words for one. Processing time runs from the order being placed to the shipment being given to a carrier; transit time runs from collection to the customer’s address, and Shopify states that transit time “doesn’t account for order processing time”. Google’s handling time “normally starts when an order is placed by a customer and ends when a carrier picks up the package for shipment” — different vocabulary, same endpoints.
What two timestamps actually prove my processing time? When the order was placed, and when the carrier actually took it. Everything else is diagnosis. The FTC’s wording is “records or other documentary proof establishing its use of systems and procedures” — it names no columns, and one good month does not satisfy it. Export both timestamps per parcel with order ids, and keep unfinished rows visible.
Does a carrier’s first scan count as the handoff? Not automatically. A first scan can be raised at a drop-off, at an agent’s counter, or on first read in a sorting facility. Ask your carrier which event type means the parcel was in their possession, then write it into your sheet. Failing that, use the signed handover document.
Should every product carry the same processing time? Not necessarily, and merchants have raised this on Shopify’s own forum. One value has to cover your slowest SKU group, so faster items advertise a date they beat. I have not tested what per-product options exist in the admin today — check your own settings.
What should I do when a public holiday falls inside my stated window? Treat it as a stated exception, not a silent one. Pull the official arrangement covering that window, check which days it removes and which weekend days it designates as working, and ask your warehouse for its own shift plan in writing — the national arrangement does not tell you what any single operator does. Then decide per block: widen, or pause the claim.
Platform pages read August 2026; an asterisk marks those re-checked on 13 September 2026.
Shopify, Processing time and delivery dates *
Shopify, Understanding processing time *
Shopify, Understanding fulfillment time
Shopify, Setting up transit time for your flat shipping rates
Shopify, Setting up manual delivery dates *
Shopify, Setting up automated delivery dates
Shopify, Getting started with fulfillment time and delivery dates
UPS, UPS Smart Pickup through a reader service; a direct request from our machine failed to connect
General Office of the State Council, Notice on 2026 public holiday arrangements, Guo Ban Fa Ming Dian (2025) No. 7 — dated November 4, 2025
The State Council, China’s public holidays for 2026 — dated November 4, 2025, cited for the announcement date
Federal Trade Commission, Business Guide to the FTC’s Mail, Internet, or Telephone Order Merchandise Rule — dated September 9, 2011, quoting 16 CFR 435.2(a)(4); re-checked Sep 13, 2026
Google Merchant Center Help, Set up estimated delivery time *
Google Merchant Center Help, Shipping attribute *
Google Merchant Center Help, About Shipping Confidence Values
Shopify Community, post 8 by HeretoSell, “How to add 2-5 day processing time before item is shipped?” — June 25, 2021
Shopify Community, Setting up different delivery durations / lead time — post by DaveD, January 23, 2023
This article contains no ASG performance figures, and that is deliberate: its argument is that a timing with no record behind it is a quoted number, so I have not quoted ours. Platform behaviour here was read in the vendors’ own documentation on the dates given in the source list; those pages carry no publication dates, so treat every platform mechanic as current at retrieval, not permanent. The FTC material is US jurisdiction and is quoted, not interpreted. This article is not legal advice.
I am Janson, founder of ASG Dropshipping . We handle China-side fulfillment for Shopify and WooCommerce brands. Most of my week goes to one gap: what a store promises at checkout, versus what a warehouse floor in Guangdong can evidence.
