Executive summary
- What: Shopify adjusted three Built for Shopify criteria that apply only to fulfillment services apps, covering order completion, fulfillment request response, and cancellation response.
- Why: The previous thresholds screened out capable 3PLs whose operating rhythm did not fit the measurement window, so the badge under-represented real quality.
- Who: Merchants evaluating or already running 3PL and warehousing apps, plus the partners who build them. No other app category is affected.
What changed
Three requirements in section 5.8 moved. Requirement 5.8.2 sets the share of assigned fulfillment orders an app must complete, now 97 percent over a trailing 28 days, with orders created in the last 7 days excluded. Requirement 5.8.6 covers how quickly an app answers a fulfillment request, now 95 percent answered inside 24 hours by accepting or rejecting. Requirement 5.8.7 covers cancellation requests, now 99 percent answered inside 24 hours. Shopify extended the response windows on the latter two and adjusted the required rates. How the criteria are measured is otherwise unchanged, evaluation remains automatic, and no other Built for Shopify requirement was touched.
Why it matters
Built for Shopify is one of the few quality signals a merchant can read before running a pilot, which makes its calibration a practical concern, not a partner ecosystem detail. The older, tighter response windows penalised warehouses that work in shift cycles: an operation confirming requests every morning was marked down for latency its customers never actually experienced. A 24 hour window measures something closer to merchant outcome. The near term consequence is that the credible fulfillment app shortlist just got longer, and providers you filtered out on badge status alone deserve a second look. Read it accurately though: a relaxed threshold is a less discriminating filter, so treat the badge as a floor rather than a service guarantee and keep your own SLA in the contract. If you split inventory across providers, pair this review with how those apps handle SKU sharing across fulfillment services, which tends to matter more day to day than the badge does.
Role-specific impact
- Marketers: Delivery promise copy is only as safe as the slowest provider behind it. If procurement adds a newly qualified 3PL, confirm dispatch cutoffs before changing shipping timelines on product pages or in campaigns.
- Developers: No code change is required. If you build or maintain a fulfillment app, re-check your latency instrumentation against the 24 hour window and the 95 and 99 percent rates so internal dashboards match how Shopify scores you.
- Store admins: Update the app evaluation checklist. Badge status is now a weaker discriminator, so weight your own data on acceptance speed and cancellation handling more heavily when comparing providers.
Use-case example
Real-world scenario
A home goods brand shipping about 30,000 orders a month splits volume across two providers: an incumbent 3PL and a regional warehouse handling oversized items. The regional partner's app never carried Built for Shopify status, which kept it off the shortlist during last year's procurement review despite strong on the ground performance, because its request confirmations ran on a single morning batch and fell outside the old response window. Under the revised criteria that batch pattern clears 5.8.6 comfortably. The brand can now re-run the comparison on delivered cost per order and regional transit time rather than on a badge the partner could not previously earn, and the oversized lane usually wins on transit days rather than price.
Implementation checklist
- Pull the current Built for Shopify status of every fulfillment app in your stack and note which ones recently changed state.
- Re-open any 3PL evaluation that was closed specifically on badge status within the last 12 months.
- Compare your measured acceptance and cancellation response times against the 95 and 99 percent thresholds, since your contractual SLA may be stricter than Shopify's floor.
- Confirm dispatch cutoffs and batch confirmation schedules with each provider, because a 24 hour response window can still sit behind a same day delivery promise.
- If you build a fulfillment app, check your Partner Dashboard distribution page for the recalculated status rather than inferring it.
- Record the review date and thresholds used, so the next cycle can separate a criteria change from a real performance change.
FAQ
Q: Do we need to take any action as a merchant? A: No action is required. Status is evaluated automatically against these criteria, so any change appears on its own. The value in acting is commercial, not technical: your provider shortlist may now be out of date.
Q: Does a newly badged fulfillment app mean better service than before? A: Not necessarily. The app's performance may be unchanged while the measurement moved to better reflect how fulfillment operates. That is useful context, not a substitute for your own performance data.
Resources
Built for Shopify requirements, fulfillment services apps
Need guidance? Talk to Makro.