What does Request fulfillment mean in Shopify?

You open a paid order and find Request fulfillment instead of the packing action you expected. Pressing it can feel like finishing a job. For a service-connected order, it is the start of a handover. Your next check is whether the other system has accepted the instruction, not whether the customer has received the goods. This distinction gives you a useful way to investigate an order that appears to have stopped.

What exactly are you asking the fulfilment service to do? #

Shopify’s app fulfilment instructions describe a request to start picking, packing and shipping. The service can accept or decline it. In the detailed progress section, Requested and Accepted identify different stages; the timeline carries the response. Read those details before treating In progress as evidence that someone has already packed the box.

Think of the order as a sales record and the request as a work instruction. Before sending it, check the exact items, quantities, assigned service and delivery details. If an instruction is wrong, the supplier may act on it while your shop still looks administratively tidy. A correct payment status does not establish that the correct variant is on the provider’s shelf or that the intended service has received the instruction.

Shopify’s FulfillmentOrder documentation says a fulfilment order groups work assigned to a location. Shopify creates those work records automatically through routing. A fulfilment record represents ongoing or completed work and can exist before carrier collection. Therefore a work record appearing, a request being accepted and a parcel being scanned should each have their own evidence in your operational check.

Who receives the request note and notification? #

The request’s optional Notes field sends a message to the service rather than to the customer. Use it for an instruction that the provider can act on, such as checking an approved pack specification. Keep customer updates in the channel intended for the customer. Do not assume that something written in this field will appear in the buyer’s shipping email or change the checkout promise.

For an important instruction, ask the provider how it handles request notes. A field being delivered does not guarantee that it is printed on a pick list or seen at the packing station. Agree which instructions belong in product setup and which belong on the individual order. Repeated requirements such as a supplied insert should have a stable operational home, rather than relying on someone noticing a free-text exception.

Notification settings also need to match the action being used. Shopify’s Flow request action has a Notify customer field for the request. A notification about requesting work is different from evidence of dispatch. Check the resulting customer message when you configure automation, including its wording and the point at which it is sent.

Use one identifiable order to follow the communication sequence from request to tracking. Record which action generated each email. If the operational history looks correct but the expected message is absent, investigate delivery separately using Shopify shipping confirmation checks. Sending an extra fulfilment request is not a useful substitute for finding out whether an email was requested.

What should you check when a request stays unanswered? #

Start with the instruction that already exists. Record the Shopify order number, assigned location, affected line items, request time and last service response. Then look for the corresponding order in the provider’s system. Ask whether it was received, whether it is waiting for approval and whether any physical work has begun. This makes your support message about a specific handover, rather than a general complaint that an order is stuck.

Use your provider’s documented response and dispatch arrangements to decide when to escalate. Shopify’s request button does not supply a universal picking deadline for every connected warehouse. Keep the relevant cutoff and working calendar with your agreement. If you cannot find a promised response interval, ask for one. Do not invent a fixed waiting period and communicate it to customers as if it were a platform rule.

Check whether the request applies to the whole basket or only part of it. A shop selling its own stock alongside a partner’s stock can have work allocated to different locations. A provider’s confirmation should identify which items it covers. Keep a separate unresolved list for the rest. This prevents the response to one instruction from being mistaken for acceptance of every item the customer purchased.

Can you send a request again or fulfil the order yourself? #

Resolve the ownership of the first instruction before creating another execution. The provider may have received it even when your view has not updated. Ask it to confirm whether the existing work should continue or stop. Keep that response against the order number. A retry should address a known failed handover, rather than create a second packing instruction while the first instruction’s status is unknown.

Shopify documents a status-dependent location change: if work is requested but unaccepted, cancel the request first; after acceptance, obtain the service’s cancellation response before changing location. Mark as fulfilled is unavailable on orders assigned to service locations. These mechanics protect the handover, but your operational check must still establish what the provider is doing with the physical goods.

If you will dispatch from your own stock, match that replacement to the exact items released by the provider. Check your available units, delivery service and customer message. Keep the old instruction’s reference in your notes so support can reconcile both histories. Do not send a replacement simply because a tracking number is missing: ask whether the original box is waiting for collection, has already left or has not been packed.

What does a duplicate execution cost in an AirPost comparison? #

AirPost’s fee constants, checked on 14 October 2026, give a recommended small-parcel sender fee of €2.25 and a platform fee of €0.85. One separately executed small parcel therefore has €3.10 in those components before its label. If the same intended contents are actually dispatched twice as separate small parcels, those components total €6.20, plus two labels and the goods used.

This is an execution comparison, not a charge for clicking a button twice. It also does not calculate cancellation, refunds or recovery of an unwanted parcel. Use the actual platform record to see which shipments exist and which costs have been incurred. The economic reason to verify ownership is straightforward: avoiding another physical execution avoids the extra shipment’s handling, label and stock consumption.

AirPost’s own copy describes paid-order forwarding with stock and a default service configured, followed by tracking returning when the label is bought. Assess that documented event rather than assuming every app uses Shopify’s generic request lifecycle in the same way. Start from the seller fulfilment model and verify the point where your connected app writes the fulfilment status.