Merchant cant request fulfillment even after creating a Fulfillment Service under our app

Topic summary

Issue: After programmatically creating a Fulfillment Service on app install (POST /admin/api/2024-07/fulfillment_services.json), the merchant couldn’t see the “Request fulfillment” button on orders.

Investigation: A responder asked whether the order’s products were assigned to the service’s location, noting items can be fulfillable from multiple locations. They requested screenshots to verify configuration.

Actions taken: The app owner updated product variants to use the custom fulfillment service via PUT /admin/api/2024-07/variants/{id}.json with fulfillment_service set (e.g., “agrihopper-fulfillmet-service”). They also confirmed the fulfillment order location assignment on the product variant page.

Outcome: After assigning variants and ensuring the correct fulfillment location, the “Request fulfillment” option appears and the flow works for new orders. Existing orders created before the configuration change weren’t explicitly confirmed to be affected, but the resolution applies to new orders.

Status: Resolved for new orders. No additional configuration beyond variant assignment to the fulfillment service and validating the fulfillment order location was required. Screenshots were referenced to illustrate UI states.

Summarized with AI on December 20. AI used: gpt-5.

Hi,there

Have your assign your products of your order to your service location?

could you give a screenshot for better understanding?

1 Like