Client Onboarding Checklist for Dropshipping Agencies

Onboarding is where you set the account you can keep

A client hands you their store because the fulfilment they had was slow, opaque, or wrong. The first two weeks decide whether you become the operator they forget about or the vendor they replace. A structured onboarding is how you avoid the second outcome: it front-loads every decision that, left unmade, turns into an angry message after a customer has already paid. This is the checklist to run, in order, before a single live order ships, written as the actions you take on the client's behalf rather than questions you forward and hope they answer.

Everything below assumes you are running the backend through a China sourcing-and-fulfilment desk rather than warehousing yourself. RyanFulfil's Agency Desk has operated since 2018, ships around 4,000 orders a day from Guangzhou to more than 150 countries, and the workflow is the same whether you refer the client or contract them yourself. What changes is who signs, invoices and prices. Decide that first.

Step 1: Register the client before you quote anything

Your first action is administrative, not operational: put the client on the record so the account is protected and the commercial path is fixed. Do this before you show a price, because the price depends on the path.

On the referral path RyanFulfil contracts, invoices, supports and prices the seller, and the quote it issues discloses that your commission is included. On co-manage and white label you contract, invoice and price the client, and RyanFulfil invoices you. Either way you name the commission folded into the quote. Guidance is around 2%, the level that keeps a client's landed cost competitive against buying direct. There is no joining fee, no monthly programme fee and no published minimum, so the decision is purely about who owns the relationship. Register the account and confirm the path on the client-protection section before you quote.

Protection is account-level, not territorial. Registering a client does not make their product yours, because a publicly listed item can be sourced independently by any other seller, so do not promise a client exclusivity you cannot hold. What you can promise is that the account, their pricing and their supplier work stay confidential to your desk.

Step 2: Capture the catalogue, the markets and the real volume

Now build the operational picture. Vague onboarding produces vague quotes and preventable delivery failures. Capture, on the client's behalf, the specifics that actually change cost and feasibility.

• Every SKU and every variant that maps to a physical difference: size, colour, material, bundle composition. A variant the store treats as cosmetic but the warehouse must pick differently is a real variant.
• The destination markets, ranked by share. Where a client ships decides more than where they sell.
• Realistic volume: current orders a day, the expected launch spike, and any seasonal pattern. A store doing twenty a day and one about to run a campaign to two thousand need different handling from day one.
• Product eligibility. Screen for anything a fulfilment desk cannot ship, such as certain battery types, liquids, or branded and lookalike goods, before the client lists it rather than after a customer pays.

The destination list is not trivia. Several markets require the end customer's own customs identifier before a parcel clears, and if your client's checkout does not collect it the order stalls. Turkey needs a TC Kimlik No, Chile a RUT, Brazil a CPF or CNPJ, South Korea a PCCC and Argentina a CUIL. Bill in a no-surcharge currency where you can, since USD, EUR, GBP, CAD, AUD, NZD and SGD carry none, and price in the small FX surcharge on TRY and HUF. Capturing this now means the delivery promise you write in the next step is one you can actually keep.

Step 3: Agree the exact words the store will use about delivery

The most common way an agency loses a fulfilment account is a delivery promise the operation never agreed to. Before anything goes live, write the words the client's store pages, order emails and support macros will use, and make sure they are estimates tied to a route rather than guarantees.

Most routes ship DDP, so the advertised price is the delivered price and the customer is not ambushed by a customs bill; inside the EU, orders under 150 euros clear under IOSS. Delivery windows are route-specific estimates that move with carrier and destination. RyanFulfil runs 4PX, YunTu and Wanbang, and the realistic ranges by lane are on the shipping-times page. Put the estimate in the store as a range, never as a dated guarantee, and never let a client advertise a delivery date you have not confirmed for that lane.

This is also where you set what the client may claim about the operation itself. Saying fulfilment is operated through your China supply-chain team or network is accurate and sells just as well. Claiming that the client, or you, own a warehouse you do not is a claim that fails at the worst possible moment, in front of a customer or a payment processor. Keep the promise language and the capability claims honest from the first line of store copy.

Step 4: Connect the store and prove the sync both ways

With the catalogue and promises agreed, connect the storefront. On Shopify and WooCommerce the integration is two-way and automatic: orders flow in, tracking flows back to the customer without anyone rekeying. On TikTok Shop, eBay and Etsy the tracking number is sent to you to apply on the client's side, so build that step into your routine rather than assuming it happens by itself.

Match each store variant to the SKU it will actually pick, confirm the address fields carry through cleanly, and check that the tracking write-back reaches the customer-facing order. The connection options and what each platform does and does not automate are set out on platform integrations, and the step-by-step version your client's developer may want is in the seller-side walkthrough on connecting a Shopify store. Do not treat an installed app as a connected store: a connected app with an unmapped SKU still ships the wrong thing.

Step 5: Push one real order through before you open the taps

Never let a client's first live order be their first test. Place a single genuine order through the connected store and follow it end to end: order received on the fulfilment side, correct SKU picked, address and any customs identifier intact, dispatch, and tracking written back to the customer. One controlled order surfaces the mismatch that would otherwise repeat across the whole launch spike.

Run this on the client's real checkout, not a spreadsheet. The full preflight, meaning what to check on the platform before the first live order, is on the seller-side preflight checklist. Only after that order lands cleanly do you turn on volume.

Step 6: Write the exception rules before you need them

Exceptions are not edge cases; at volume they are a daily category. The accounts that survive are the ones where the rules were written before the first problem, not argued after it. Agree, on the client's behalf and in writing:

• The order-change and cancellation cut-off: the point after which an order is locked because it is in production or already packed.
• The claims process for lost, damaged and wrong-item orders: what evidence is needed, who files, and who absorbs the cost in each case.
• The escalation path, so your client knows exactly who to contact when something is genuinely urgent.

The claims rules and the evidence each type needs are set out in the claims section, and they apply whether you refer or own the client. Set the client's expectation on response honestly: RyanFulfil's median first reply in working hours is 23 minutes, and about one in five in-hours messages still take more than half a day. The full picture is on the response-time FAQ. Telling a client the honest range is cheaper than defending a number you invented.

The one-page onboarding checklist

• Register the client and fix the commercial path, whether refer, co-manage or white label, before you quote.
• Capture every SKU, variant, ranked market and realistic volume; screen product eligibility up front.
• Collect the customs identifier each market needs, and confirm the billing currency and any FX surcharge.
• Write delivery estimates as route-specific ranges, and keep every capability claim honest.
• Connect the store, map every variant to a SKU, and prove tracking writes back to the customer.
• Push one real order end to end before opening volume.
• Agree the change cut-off, the claims process and the escalation path in writing.

What a finished onboarding looks like

A client is onboarded when you could hand the account to a colleague and they would know what ships, to where, under what promise, and what happens when something goes wrong. For a fuller definition from the operations side, the seller-facing note on what counts as a successfully onboarded fulfilment client is worth reading alongside this. Run the six steps in order and the account starts quiet, which is the only state in which a fulfilment client stays yours.

When you are ready to onboard your first client this way, apply for founding partner access. The application asks what your clients sell, how many you manage and which path fits, the same information you will already have gathered running step one.