Strategic & API partnerships
Not one agency with one client? We build the arrangement around you.
Refer, Co-Manage and White Label answer four questions — who owns the client, who invoices, who supports, who sets the price — with fixed answers. A platform, a marketplace, a community at scale, a regional 3PL or a freight forwarder rarely fits any of those answers cleanly. The strategic path settles all four in writing, per partnership, and adds the parts a single-client onboarding never needs: custom integration, data exchange and dedicated capacity.
- Fulfilling from Guangzhou since 2018
- 500+ active client accounts
- 4,000+ orders fulfilled daily
- Ships to 150+ countries
500+ active client accounts and 4,000+ orders fulfilled daily are RyanFulfil operating declarations dated 15 August 2026 across the whole business, not figures for this programme, which is new. They are separate from the measured order window (orders paid 1 May – 3 October 2026). The 150+ figure reflects the maintained 147-destination route table; eligibility for a given product and route is confirmed in the quote. Delivery windows are route-specific estimates, not guarantees.
Who the strategic path is for
The strategic path is not a bigger version of the agency paths. It exists because some partners bring many downstream sellers, or operate one leg of the flow themselves, or move volume that a per-order commission and a WhatsApp thread stop serving well. Below is who actually ends up here, and what each type needs that the standard paths do not give them.
Platforms and marketplaces
You already have merchants or sellers of your own, and you want China sourcing and dispatch-to-door running behind your product rather than sending each seller off to a separate agent.
What the standard paths cannot give you: many sellers served through one relationship, and order intake at platform scale rather than one store connected by hand. That is an integration to design, which is exactly what this path is for.
Communities and course operators at scale
You support hundreds or thousands of members who ship physical products, and you want a single desk they reach on terms you have agreed, with reporting and attribution you can see.
What the standard paths cannot give you: a repeatable, member-level arrangement. Registering each member as an individual referral works for a handful; past that, the structure is a strategic one.
Regional 3PLs and freight forwarders
You already move freight or run last-mile in your region, and you want China sourcing, inspection and pick-and-pack as an upstream capability feeding what you already operate.
What the standard paths cannot give you: a clean split of which side operates which leg, and how orders and tracking hand off between two operations. That handoff is the whole conversation, and it is settled in writing.
High-volume sellers and brands
You are past the point where a per-order commission and a manual thread scale. You want reserved handling, forecast-driven pre-stock and data moving into your own systems.
What the standard paths cannot give you: capacity planned against committed volume, and a data exchange shaped to your operation. Both are bespoke, because both depend on your numbers and your systems.
If that is not you
For a standard client-store relationship, start with the established partner paths. One agency taking on a client wants Co-Manage or White Label. Someone introducing sellers without running their fulfilment wants the referral path. The four standard paths are set out on the Agency Desk, and how the programmes fit together is on the programmes overview.
What “custom” actually means
On the four standard paths, the answers are already set: whoever holds the client contract owns the relationship, and who invoices, who supports and who sets the price follow from that one fact. The comparison table on the Agency Desk lays all four out column by column. Strategic is the path where none of those answers is assumed. They are decided per partnership, and the commercial model is built around the integration rather than picked from that list.
The four questions, answered per deal
Who contracts, who invoices, who supports and who sets the price are settled deal by deal. A marketplace serving its own sellers, a forwarder operating one leg, and a brand buying capacity give different answers to all four, and each answer is written down before anything runs.
Commercial terms around the integration
The standard paths run on a partner-named commission: you name the number, guidance is around 2%, and it is added into the quote. A strategic arrangement is more likely to run on volume commitments, per-integration terms or reserved-capacity terms — because a partner serving many sellers is not priced like one client’s orders.
Settled in writing, then run
A strategic enquiry goes to the partnership owner, not the standard onboarding queue. Nothing runs on a handshake or an assumption about who does what. The scope, the ownership split and the commercial terms are agreed in writing first, and a small proof run comes before scale.
What “custom” does not mean
It does not move the operating boundary. RyanFulfil is the operations layer on every path, strategic included: we source, check, pack, ship and investigate fulfilment problems. We do not build your platform, run your advertising, or become your sellers’ end-customer service department. And custom terms never turn an estimate into a promise — delivery windows stay route-specific estimates, capacity is only what a forecast and a staffed operation can actually support, and the same approved-claims rules apply to anything a strategic partner says about RyanFulfil-operated fulfilment.
The integration reality today
This is the section that decides whether a strategic partnership is a short conversation or a build. Two lists: what runs today, and what is a custom conversation rather than a product you plug into. A partner API requires separate scoping and development; no off-the-shelf partner API is available.
Working today
Built for the 4,000+ orders a day RyanFulfil declared on 15 August 2026.
- Two-way store connections on Shopify and WooCommerce.Orders pull in, tracking uploads back, and that triggers the store’s own shipping notification.
- Marketplace tracking on TikTok Shop, eBay and Etsy.Tracking numbers are sent to the seller to apply on their side; the connection is not two-way.
- Several stores under one account.Each store is its own record, with client-level and store-level invoicing allocation.
- Reporting prepared for you.A document or statement, produced by hand during the pilot — not a live feed.
- Route choice across 4PX, YunTu and Wanbang.Selected per destination from the maintained route table.
A custom build, not a product you plug into
Each of these is a conversation about what to build and who builds it.
- A partner API.No off-the-shelf partner API is available. Scope and development must be agreed separately.
- Programmatic bulk order intake at platform scale.Beyond connecting one store at a time.
- Live data feeds or webhooks into your systems.Real-time status pushed to you, rather than a prepared statement.
- A self-serve portal or dashboard.No self-service partner login or dashboard is currently available.
- Automated attribution across many downstream sellers.Manual registration works for a few; platform scale needs a build.
Why we draw the line this way
If your partnership depends on an API, agree its scope, development responsibilities and acceptance criteria before committing. The current seller-side connection detail is on platform integrations, and it is the same material a strategic partner starts from.
What data moves, and which way
A strategic partnership is largely a question of what information passes between two operations, in which direction and in what form. Here is what flows, what comes back, and how it moves during the pilot — each of which is part of the scope, not a fixed product.
What flows in
Order data: a product reference, the variants that matter, the destination markets and a realistic volume. At platform scale this is where bulk intake gets designed, because sending it one store at a time stops working.
What flows back
Tracking — two-way to Shopify and WooCommerce, sent to the seller to apply on the marketplaces — plus fulfilment-issue evidence for lost, late, damaged or wrong-item cases, and periodic reconciliation of what shipped against what was invoiced.
How it moves today
Through the live store connections and prepared documents. There is no live data feed yet; agree the required format, cadence and direction in the strategic scope.
Confidentiality is not renegotiated for scale
The confidentiality position that applies on every path applies here too: a partner’s sellers, their pricing, their volumes and their product research stay theirs, and private research is not reused to build somebody else an offer. The protection and its limit — a public product stays publicly sourceable — are set out under client protection.
What dedicated capacity means, and what it does not
Capacity is the third thing a strategic partner usually needs and the standard paths do not size for. It is planned against your forecast and committed volume — not promised on signup, and never larger than a staffed operation can actually deliver.
- Reserved handling against committed volumePlanned from your forecast, confirmed in writing, not assumed.
- Forecast-driven pre-stockBuy ahead of proven demand once a product line is working.
- Surge and peak planningChinese New Year closures and carrier congestion move the whole timeline; planned for, not absorbed in February.
- Route capacity across carriersService choice per destination across 4PX, YunTu and Wanbang.
Operating limits
Delivery windows stay route-specific estimates, never guarantees, whatever the volume. Capacity is confirmed only after the staffing requirement and forecast are clear. The four service-level targets are already published; any credit schedule and severity-update cadence require agreement. See the targets and historical first-reply measurement on service levels, and route transit ranges are on the shipping times table.
How to start a strategic partnership
Because it is bespoke and qualified, there is no button that switches it on. The sequence below is the qualification, and it is deliberately different from the standard onboarding: a strategic enquiry goes to the partnership owner, and integration and volume are discussed before terms are set.
- Tell us the shape of the partnership Through the application, with the strategic path selected: partner type, expected volume, which systems have to talk to each other, and which side operates which leg of the flow. You
- A scoping conversation with the partnership owner Not the standard onboarding assessment. A platform or a forwarder is not the same conversation as an agency onboarding one client, so this goes to the person who owns partnerships. RyanFulfil
- Settle the four ownership questions in writing Who contracts, who invoices, who supports and who sets the price. All four are agreed and written down before anything runs, so nothing depends on an assumption made in a good week. Together
- Map the integration against what exists today What is live now — store connections and prepared reporting — against what needs building, such as bulk intake or an API, and who builds it. Agree the scope and responsibilities before development. Together
- Agree commercial and capacity terms around the integration Volume commitments, per-integration or reserved-capacity terms, or a mix — built around the integration rather than taken from the standard commission model. Together
- Run a small proof before scale A limited live run to prove the flow, the data exchange and the handoff work as agreed, before volume goes through it. Confirm the results of the limited run before increasing volume. Together
Strategic partnerships
Bring your integration requirements.
Tell us the shape of the partnership — platform, marketplace, community, 3PL, forwarder or high-volume brand — your expected volume, and which systems have to talk to each other. It goes to the partnership owner, not the standard assessment queue.
Prefer to just ask? WhatsApp +86 178 4666 9989, or use the short link wa.link/dropship. A person reads it — we are on China hours.
Strategic arrangements are bespoke and qualified. There is no guaranteed capacity, no off-the-shelf API and no guaranteed-income programme here; terms, integration and delivery estimates are settled in writing around what a route, a forecast and a build can actually support.