You have found a private agent. The sample looks good, the quote makes sense, and someone finally answers your shipping questions. Great. Now comes the less exciting part: deciding what happens to the orders already moving through AliExpress.
Treat the switch like a restaurant changing kitchens. The new kitchen can take the next tickets. But changing the screen does not stop the old kitchen from cooking an order it already accepted.
A controlled migration follows the same logic. Give every open item an owner, verify the replacement product, test the new route, and release a defined group of orders. Keep the old workflow available for unfinished work. That is how you reduce disruption while your store keeps selling.
Decide What You Are Switching
Change the supplier, the connector, or both?
AliExpress is the marketplace. Its sellers supply your products. A connector such as DSers helps move product and order information between systems. Your private agent may handle sourcing, inspection, storage, packing, and shipping under an agreed scope.
Those are separate jobs. Changing the supplier does not always require changing the connector. Ask whether the agent supports your existing setup before installing anything. If several tools will change, review the broader app-to-agent migration process alongside this AliExpress-specific handover.
Confirm the agent is ready for your actual orders
Before granting access, verify the private dropshipping agent. Confirm who receives payment, where goods are handled, and who resolves exceptions.
Get a quote for your product, packed dimensions, destination countries, and expected quantities. Ask about purchasing, inspection, packaging, storage, shipping adjustments, and returns. Comparing agent fees, markups, and extra charges helps you spot a low product price paired with expensive extras.
Budget for the overlap too: samples, two subscriptions, prepaid agent funds, and stock awaiting inspection. A lower future unit cost will not fund today’s deposit. Agree on replenishment and payment timing before sending live orders.
Sort Every Open AliExpress Order Before Changing Supplier Mapping
Start with the backlog. This is where an apparently simple switch can produce two parcels for one customer—or none.
Build a line-item ownership ledger
Export your open store orders and reconcile them against the connector and AliExpress purchase history. Include manual purchases and anything another team member placed outside the normal workflow.
Use one record per order line, splitting quantities where necessary. Save the store order ID, line-item ID, SKU, quantity, AliExpress purchase ID, payment status, cancellation status, agent job ID, tracking numbers, and responsible person.
Why this much detail? One customer can buy two products from different suppliers. Even two units of the same product can be in different parcels. An order-level label saying “agent” cannot explain which unit has already shipped.
Separate unplaced, submitted, and shipped work
Use the table below as a review sheet. These are operational categories, not identical labels across every app.
| Observed state | Check before acting | Recommended handling |
|---|---|---|
| Never submitted to AliExpress | No purchase record, queued purchase, or other fulfillment commitment | Assign eligible quantities to one route |
| Submitted but unpaid | Purchase ID, payment automation, and cancellation or expiry status | Resolve the existing purchase before reassignment |
| Paid, awaiting dispatch | Supplier response and actual physical status | Keep the existing owner unless release is confirmed |
| Cancellation requested | Whether cancellation was accepted and work stopped | Hold reassignment while unclear |
| Label created or parcel shipped | Parcel location, carrier scans, and supplier evidence | Keep legacy monitoring; investigate missing movement |
| Partially shipped or replacement needed | Exact outstanding quantity and original parcel reference | Create a separate, traceable instruction |
Here is the software boundary that matters: DSers’ rules for supplier mapping on awaiting orders distinguish eligible unplaced orders from purchases already submitted to AliExpress. Changing the default mapping does not move purchases in Awaiting Payment or Awaiting Shipment to another supplier.
A product-level mapping change can also affect multiple eligible pending orders. Check its scope before using it for a small pilot. Where supported, a single-order change may better match your test.
Do not rely on “unfulfilled” in Shopify alone. Compare the purchasing record with the warehouse or supplier’s actual progress.
For an illustrative example, imagine 40 open lines, each containing one unit. Twelve were never submitted, six have unpaid purchases, nine are paid and waiting for dispatch, and 13 have shipped. If only eight of the twelve unplaced units have approved mappings, those eight are candidates for the pilot. The other 32 still need their assigned handling or review.
That is a very different decision from importing all 40 into the agent’s dispatch queue.
Add a review timestamp to every uncertain record. If someone checks a purchase at 9 a.m. and another person releases it at 4 p.m., check for changes between those events. Supplier activity does not pause while you update a spreadsheet.
Match the Product, Not Just the AliExpress Photo
The agent sends a familiar product image. It looks identical. That is a useful starting point, but you still need to establish what will arrive in the customer’s hands.
Compare materials, variants, bundles, and packaging
For apparel, compare measurements and fabric composition. For home accessories, check dimensions, finish, fittings, and protective packaging. Electronics accessories need the correct connector, included parts, and any relevant battery information.
Beauty products need particular care around product identity, ingredients, labeling, and storage. A matching bottle is not evidence of a matching formula. Confirm the requirements for the product and destination separately.
Write down what must remain unchanged. A two-piece set cannot quietly become one item because the supplier uses “set” differently. A thinner material is a product revision, even if the photograph looks fine.
Approve a sample and map every sellable variant
Compare the proposed sample against the product you currently sell and its listing promises. Keep dated photos, measurements, packaging details, and approval notes. Build product inspection and quality-control checks around those written requirements.
A simple mapping sheet makes the handover easier:
| Store variant | AliExpress reference | Agent SKU | Release condition |
|---|---|---|---|
| Blue / medium / one unit | Existing supplier variant ID | Agent’s exact item code | Measurements and sample approved |
| Blue / large / one unit | Separate supplier variant ID | Separate agent item code | Large size checked independently |
| Black / two-piece bundle | Supplier bundle reference | Kit code plus component quantities | Both components and packing rule approved |
Record the store’s actual variant IDs as well as readable names. Names can change; “blue” can mean several different products.
Include slower-selling variants before full rollout. Otherwise, the first unusual order becomes an emergency mapping exercise. If a variant remains unapproved, exclude it from the new route and record how it will be handled.
Also check available inventory after inspection and existing reservations. “The factory can make it” is not the same as stock ready for tomorrow’s orders. Count packaging materials where they are necessary to complete the shipment.
Connect the New Fulfillment Route Without Rebuilding Your Store
Keep product identity and control permissions
Ask the agent to explain how its system connects to your existing products. Preserve product and variant identity wherever the supported integration allows it. Avoid deleting listings merely to make a new import look tidy.
Save product exports, supplier mappings, inventory settings, and current automation rules before changes. Record which app holds reviews, bundles, or custom fields. A basic CSV export is useful, but it is not a complete backup of every app relationship.
Give the agent a named account or the supported app permissions needed for fulfillment. Check the access requested against the work agreed. Your main store password should not be the onboarding method.
Document how inventory data and fulfillment SOPs will move between the store and warehouse, including who corrects a mismatch.
Stop historical orders from being released twice
Before enabling the connection, ask: “What happens to orders that already exist?” Some imports may expose historical work to the new system. Visibility is fine; automatic release needs explicit controls.
Check the rules for payment status, holds, dates, products, destinations, and previously fulfilled quantities. Confirm who writes inventory and tracking updates. Two systems overwriting the same stock figure can create confusion even when their shipping queues are separate.
For duplicate prevention, use a stable reference tied to the store order, line item, and assigned quantity. Ask the agent to demonstrate what happens when the same instruction arrives twice. A retry should not create another purchase or parcel.
Review notification ownership too. Decide which system sends each customer update and test the result. Two shipping emails with different tracking numbers can create an avoidable support ticket.
Keep purchasing controls separate from legacy tracking where the software permits. You may need to stop new purchases through the old route while continuing to receive updates for old parcels. If the integration cannot separate these functions, arrange a documented manual process before switching it off.
Run a Small Pilot on Real Products and Destinations
A successful connection screen proves very little about the parcel. Test the entire journey with a limited, clearly identified group of orders.
Test the ordinary order—and the awkward ones
Begin with an approved product and a destination you regularly serve. Then cover the variations that could break the process. Use controlled test orders for exceptions instead of deliberately exposing customers to a known problem.
| Pilot case | Evidence to inspect | Failure that stops expansion |
|---|---|---|
| Standard order | Correct SKU, quantity, address, and accepted job | Wrong item or missing acceptance |
| Bundle or variant | Correct components, size, and packing instruction | Substitution or incomplete kit |
| Mixed shopping basket | Separate responsibility for each item | One route claims another route’s quantities |
| Address change or cancellation | Acknowledgment and confirmed handling | Change disappears between systems |
| Stock shortage | Hold, escalation, and customer decision path | Unapproved replacement product |
| Dispatch and tracking | Parcel evidence, valid tracking, and store update | Tracking linked to the wrong order |
Follow at least one shipment through receipt so you can inspect the customer experience: packaging, item condition, and delivery information. A label generated in the warehouse does not demonstrate successful delivery.
Review shipping options for the actual product and destination before choosing the pilot route. Packed weight, dimensions, product restrictions, and destination coverage all belong in the discussion.
A successful lightweight accessory shipment should not automatically approve a battery product or a fragile item for the same service. Expand the tested scope deliberately.
Agree on pass/fail evidence before expanding
Set written expectations for order acceptance, stock confirmation, dispatch, tracking updates, and exception response. These are your agreed service conditions, not universal industry timings.
Record when each event happens. Separate warehouse processing, carrier acceptance, and transit. Otherwise, a delay gets passed between teams because everyone is measuring a different clock.
Compare the pilot with recent AliExpress orders for similar products and destinations. A small batch can uncover errors; it cannot establish a reliable loss rate or guarantee seasonal delivery performance.
Reconcile the pilot invoice as well. Match quoted product, packing, shipping, and handling charges to what was billed. Investigate unexplained adjustments before sending more volume.
Finally, test the human handoff. Send an exception during the support hours you expect to use. Who answers? Who can authorize a hold? Who tells you the outcome? A named backup matters when the usual contact is unavailable.
You are ready to expand when both the parcel and the information follow the agreed path. If either is still unclear, keep the next batch small enough to review individually.
Set a Cutover Boundary and a Rollback Rule
Assign new orders by a recorded cutoff and cohort
Choose a quiet operating period when your store team and agent are available. Record the cutoff time and timezone, eligible products, approved destinations, and person authorizing release.
For example, your instruction might cover approved variants paid after a specified time, with every earlier order excluded unless individually reassigned. This is an example of a rule, not a recommended universal cutoff method.
Time alone is not enough. A late payment, edited order, or delayed sync can cross the boundary unexpectedly. Keep an explicit list of assigned orders and check the queues again after the change.
Take a snapshot immediately before the cutover. Review new arrivals, payment changes, cancellations, and agent acknowledgments afterward. Assign someone to investigate records that appear in both queues or neither.
Avoid a major advertising increase during this step. First establish that the new route can process the current workload. Then increase volume with the agent’s confirmed capacity and stock position in view.
Pause safely when the pilot fails
Define stop conditions before you need them. Duplicate jobs, wrong SKU assignments, unexplained stock changes, or missing order acknowledgments justify pausing the affected scope.
Pause new releases first. Preserve evidence, then find out which jobs have already been accepted, purchased, packed, or dispatched. Do not send the whole batch back to AliExpress simply because a dashboard looks wrong.
Keep a backup option ready for eligible, uncommitted orders. That may be the original supplier, but reconfirm price, stock, and service before relying on it. An old listing is not a reserved inventory pool.
A cancellation request is not a confirmed stop
Shopify’s fulfillment cancellation workflow distinguishes a request awaiting acceptance from fulfillment already accepted by a service. Accepted work requires a cancellation response. Reverting an item to unfulfilled does not itself stop physical fulfillment.
That Shopify process is separate from canceling an AliExpress purchase. Check the system where the work was actually committed.
As an operating rule, obtain confirmation that the affected quantity has been released before assigning it elsewhere. If a parcel has already left, handle that shipment through the existing support process. A replacement, when justified, needs its own instruction linked to the original.
Write down who may authorize a restart. The same person should confirm the fault is understood, the correction was tested, and ambiguous orders have been resolved. Otherwise, one team can resume while another is still investigating.
Keep Legacy Tracking and Customer Support Alive
Keep one support owner for each old order
A store can finish its supplier switch before its last AliExpress parcel arrives. Keep a separate legacy queue with purchase records, tracking, promised dates, customer messages, and the next action owner.
Track refunds and disputes alongside deliveries. Check the applicable deadlines in each order’s account records rather than using one assumed claim window for everything.
Use accurate customer language. If dispatch is delayed, say what you know and when you will update them. Do not send a shipping confirmation just because a label exists or a new agent imported the order.
For split shipments, explain what each parcel contains. A customer receiving half an order should be able to see where the rest is being handled without chasing two suppliers. Your store remains their point of contact.
Retire the old connection after a documented handover
Be careful when changing accounts. DSers’ guidance on changing an AliExpress account states that data synchronization with the replaced account stops after the change. Confirm the implications for your setup before proceeding.
Treat technical readiness to disconnect and operational closure as separate checks. An order with a tracking number may still need delivery monitoring, a refund, or further customer support.
Before retiring the old connection, confirm that remaining cases are closed or explicitly transferred to a working manual process. Keep accessible records and test how the responsible person will retrieve an old purchase and tracking history afterward.
Check unused balances, open invoices, subscriptions, and permissions. Remove access that is no longer needed after the handover is complete. Retain customer and order records only as required for legitimate operations and applicable obligations.
Your exit checklist should end with a person’s sign-off, not merely an uninstall button. That person should be able to explain what remains open and how it will be handled tomorrow.
Conclusion
Switching from AliExpress to a private dropshipping agent works best when each decision has a clear owner. Reconcile the old purchases, approve the actual products, connect carefully, and prove the new route with a manageable pilot.
Let existing commitments reach a documented outcome. Give new work to the agent only when the product, order data, stock, and shipping process are ready. If something fails, pause the affected orders and confirm their physical status before changing direction.
Preparing a handover for Friend Dropshipping? Start with your product references, variant list, main destinations, and open-order breakdown. Those details make it possible to discuss a realistic scope and test plan. A small, well-understood transition gives you a stronger foundation for growth than a rushed full-store switch.
FAQs
1. When should I switch from AliExpress to a private agent?
Consider switching when recurring sourcing, product consistency, communication, or fulfillment problems justify the extra setup. Check whether the proposed agent can solve those specific problems. A successful sample and pilot matter more than reaching an arbitrary sales milestone.
2. Is there a minimum daily order volume for using a private agent?
Requirements differ. Ask about minimum purchases, service charges, prepayment, and stock commitments. An agent may accept low order volume while requiring a product batch purchase. Make sure the cash requirement fits your business before agreeing to start.
3. Can I keep DSers when I work with a private agent?
Possibly. Confirm that the specific agent and your account support the intended agency connection. Test order release and tracking before relying on it. Other agents may require their own integration or an agreed manual workflow.
4. Do I need to recreate Shopify products or lose my reviews?
Changing suppliers does not inherently require new product listings. Ask the integration provider how existing products and variants will connect. Check your review app’s associations, preserve identifiers where supported, and test before deleting or reimporting anything.
5. Does changing supplier mapping move existing AliExpress purchases?
No. In DSers, a mapping change does not transfer purchases already submitted to AliExpress. Review those purchases individually. Eligible unplaced work can follow the new mapping, so check the full affected queue before saving a default change.
6. What should I do with AliExpress orders awaiting payment?
Check whether you intend to complete or cancel each purchase. Stop conflicting payment automation and confirm its outcome before reassignment. Keep the purchase ID in your ledger so another operator does not pay it later by mistake.
7. Can an agent take over an order I already paid for?
Customer payment alone does not determine the answer. Check whether a supplier purchase or fulfillment commitment already exists. If it does, resolve that commitment first. A second purchase through an agent is not an automatic transfer of the first.
8. Who handles tracking, refunds, and disputes for old orders?
Assign a named member of your store team to the legacy queue. They should coordinate with the original seller and keep customer communication moving. Do not assume the new agent has access, responsibility, or authority over earlier purchases.
9. Can AliExpress and a private agent run at the same time?
Yes, with explicit boundaries. Different products, destinations, or assigned order groups can follow different routes. Record which quantities belong to each. Both routes should never receive an active instruction to fulfill the same units accidentally.
10. How do I prevent duplicate shipments in mixed orders?
Track responsibility at line-item and quantity level. Link each parcel to the items it contains. Check partial shipments before resending instructions, and test that repeating an import or order message does not create a second fulfillment job.
11. What information should I send to the new agent?
Provide product references, specifications, variant mapping, quantities, approved packaging, destinations, and release rules. Include the relevant customer delivery details only for assigned orders. Agree on a secure transfer method and how corrections will be acknowledged.
12. What if the agent’s sample uses different materials?
Hold approval and compare it against your specification and customer-facing claims. Request a compliant replacement sample or treat the change as a deliberate product revision. Do not send a cheaper substitute under the old description without resolving the difference.
13. Will a private agent always ship faster or cost less?
No. Compare actual processing, transit, and total charges for equivalent products and destinations. Include deposits, storage, packaging, adjustments, and support costs. A pilot helps reveal operational differences, but a small sample cannot guarantee future performance.
14. When can I disconnect AliExpress or uninstall the old app?
After checking the tool’s technical requirements and arranging continued handling for every unfinished case. Verify access to old purchase records, tracking, refunds, and disputes. Keep a documented alternative wherever removing the connection would interrupt those tasks.
15. What should I do if the new fulfillment route fails?
Pause affected releases, identify the cause, and verify what has already been committed or shipped. Reassign only eligible quantities. Test the correction before restarting, and tell customers about any material delay with a clear next update time.
Table of Content
I’m Cassiel. I’ll help you scale your Shopify business with reliable fulfillment.
Join to newsletter.
Follow us and get more knowledge.
