How to choose an ecommerce fulfillment provider

What should you send a fulfillment provider before requesting a quote?

Give every candidate the same product and order profile, including ordinary orders, peaks and exceptions.

Build a short brief from your actual operation: active products, dimensions, weights, storage requirements, units per order, destinations and return handling. Separate recorded figures from forecasts. Where you are launching a new shop, label the assumptions and ask how a lower-volume scenario changes the proposal.

Include a few representative order baskets rather than only a monthly total. A single-item parcel, a multi-item order and a bundle can create different work. Explain inserts, gift packaging, fragile products and any checks required before dispatch. Ask the supplier to identify unsupported requirements before preparing a detailed quote.

Use the brief to create an initial shortlist. A provider’s name in a directory is a starting point for research; it does not prove that a specific warehouse handles your products, destinations or required processes. Request confirmation for the operation you intend to buy.

How do you check warehouse location and delivery coverage?

Confirm where your stock would be held and which destinations and services are included in that specific proposal.

Ask for the proposed storage location, receiving arrangements and actual dispatch routes. Distinguish a provider’s wider network from the warehouses available to your account. Do not infer local stockholding from a website listing a country or offering delivery there.

Compare delivery promises using the complete timeline: order acceptance, payment or risk release, picking, carrier collection and delivery service. Ask how weekends, holidays and orders after the agreed cutoff are handled. A dispatch commitment and an arrival estimate describe different stages.

For international selling, assign responsibility for the information and arrangements required on each route. Keep this as a route-specific question for the provider and your advisers rather than assuming that a domestic workflow extends unchanged across borders. Confirm where undeliverable parcels and customer returns would go.

How can fulfillment quotes be compared fairly?

Price the same order baskets and inventory assumptions, then add receiving, storage, returns, minimums and exit costs.

Send each shortlisted provider an identical scenario covering ordinary activity and a plausible peak. Ask whether picking is charged by order, line or unit, which packaging is included and which activities create a separate charge. Keep quoted figures distinct from assumptions awaiting confirmation.

Calculate scenario cost per dispatched order by dividing the total cost included in that scenario by the dispatched orders in it. State the period and included cost blocks. The figure is a comparison tool for your own proposals, not a market price or a guarantee of next month’s invoice.

Keep onboarding, stock transfer and eventual stock removal visible beside ongoing fees. Ask how minimum charges interact with a quiet month and whether storage or support continues during an exit. A low standard pick charge should not hide a commitment that your expected volumes cannot support.

What should a fulfillment integration demonstrate?

Test one complete order and its exceptions across the shop, warehouse and inventory records.

Ask which connection is proposed, who maintains it and whether your required shop and warehouse configuration is supported. A platform logo establishes neither the field mappings nor the behaviour of cancellations, bundles or split shipments. Record what is standard and what requires additional work.

Run a paid order, a stock shortage, a cancellation before dispatch and a partial shipment. Record the expected order, shipment and stock states in each system. Then interrupt a notification or repeat one already processed. The outcome should remain understandable without a second shipment or duplicate inventory movement.

Agree who monitors missing updates and performs reconciliation. Shopify’s webhook documentation explicitly recommends reconciliation because notifications can be missed. Use that as a question for your implementation partner; the exact mechanism depends on the connected systems.

Reference: Shopify: webhooks and reconciliation

Which service levels belong in the agreement?

Define the measurement, starting point, exclusions and escalation owner for each operational promise.

Ask what starts the dispatch clock: receipt of any order, a validated order or a released order with available stock. Set out how invalid addresses, missing information and stock shortages are surfaced. Without a shared starting point, the same order can look late to the shop and on time to the warehouse.

For stock accuracy and picking errors, request an agreed method for identifying affected units and investigating differences. Ask how evidence is shared and who can approve a correction. Avoid comparing headline percentages whose definitions, periods and exclusions differ.

Use an exception log alongside any dashboard. Each unresolved order should have a reason, an owner and a next action. Agree normal support hours, peak-period arrangements and an escalation route for a blocked dispatch. Request these as proposed commitments, rather than assuming a universal industry service level.

How should returns and a future provider change be planned?

Agree return identification, inspection and resale decisions, and keep stock removal and data export terms visible before signing.

Specify how the warehouse identifies a return and records what physically arrived. Keep refund approval separate from inspection and resale eligibility. Decide who handles an unexpected item or a package that cannot be matched to an order, and how support sees the case.

Before sending stock, clarify the process for a future exit: notice, counted stock, removal booking, usable exports and treatment of returns arriving after the move. These questions also expose gaps in onboarding responsibilities. A provider relationship should leave the merchant able to understand its own inventory and open orders.

Choose only after mandatory requirements are confirmed or explicitly recorded as unresolved. If you are replacing an existing provider, use a separate transition plan for stock, open orders and later returns. Selection and changeover are connected tasks with different acceptance criteria.

How do you turn a shortlist into a defensible decision?

Separate mandatory requirements from preferences and preserve the evidence behind each answer.

Begin with a small set of exclusion criteria drawn from your own operation: product handling, proposed stock location, required destinations and essential workflows. Ask the candidate to confirm each criterion against the actual proposal. Mark an unanswered question as unresolved rather than treating silence as support. A supplier can remain a candidate while a gap is investigated, but the condition should stay visible to the person approving the choice.

Only compare preferences after the mandatory checks. Record why a service, integration or support arrangement matters and what demonstrates that it is included. A numerical score can help organise discussion, but it cannot repair a missing requirement or make incompatible price scenarios comparable. Retain the final brief, quote assumptions, test evidence and remaining conditions together. Use the warehouse and service-level guides for the operating details, then the provider-switching guide when an existing stockholding arrangement needs to be moved.