DEV Community

jinguo ren
jinguo ren

Posted on

I Built an AliExpress Dropshipping Tool. The Hardest Part Wasn't the Code.

If you run a dropshipping store, you know the real work isn't picking products.
It's the spreadsheet hours: copying order details to AliExpress, checking which
items are actually in stock, chasing tracking numbers, fixing listings whose
price changed overnight.

GetDropFlow is the tool I built to kill that manual work — a subscription
extension that automates the AliExpress dropshipping workflow: product sourcing,
listing management, and order fulfillment. This post is not a feature tour. It's
the part nobody writes about: what it actually takes to get a tool like this
allowed to exist on the big platforms.

Lesson 1: API access is a relationship, not a form

AliExpress has an official dropshipping (DS) API. On paper the process is
simple: register your app, get an AppKey, build. In practice:

  • The application asks questions that assume you already know the answers.
  • Documentation covers the happy path; the edge cases you hit in week one are nowhere in it.
  • Support runs on tickets. I filed a detailed ticket on October 14 with four specific technical questions, followed up twice (October 18 and 22), and I'm still waiting for an answer.

None of this is a reason not to build. But if your product roadmap assumes API
access in "about a week," rewrite the roadmap. Build the parts of your product
that don't depend on anyone's permission first.

Lesson 2: Marketplace review is a black box with a stamp

Getting listed in a major commerce marketplace meant a formal review case. It
sat for weeks. Then it was closed — category: "User Education," with an empty
explanation field. No list of issues. No line numbers. Nothing to fix.

What do you do with a rejection that contains zero information? You go back to
first principles: re-read every published requirement, audit your listing
against each one, and assume the strictest interpretation everywhere. It's slow
and unglamorous, and it's the only move available.

If you're building on top of other people's platforms — and in e-commerce, you
always are — treat review outcomes as weather, not as justice. Plan inventory,
launch dates, and marketing around the possibility of an unexplained "no."

Lesson 3: Support latency is a product feature (of theirs)

Both experiences taught me the same thing: platform support response time is
part of your product's real spec.
Your users don't care that a marketplace
hasn't answered your ticket in three weeks. They care that the feature works.

So the design rule I now build by: anything a platform can silently break,
delay, or revoke gets isolated behind an adapter, monitored, and given a manual
fallback. The automation is the selling point, but the fallback is what keeps
subscribers subscribed.

What GetDropFlow does today

GetDropFlow helps AliExpress dropshippers spend their hours on selling instead
of spreadsheet work:

  • Product sourcing — find and import products without the copy-paste dance.
  • Listing management — keep listings in sync instead of finding out about a price change from an angry customer.
  • Order fulfillment — push orders through with far fewer manual steps.

It's a subscription tool, built and run by an independent developer (me), and
it's very much alive: getdropflow.com

What's next

I'll keep writing here — practical dropshipping automation tutorials, honest
build-in-public notes, and the occasional platform horror story. If you sell on
AliExpress, Magento, or your own store and you're drowning in manual order
work, I'd genuinely like to hear what your worst task is. That's my roadmap
research.

— Jinguo, maker of GetDropFlow

dropshipping #ecommerce #AliExpress #indiehacker

Top comments (2)

Collapse
 
shashankrajurkar profile image
Shashank Rajurkar •

The most useful roadmap signal may be the task that's both frequent and expensive to recover from: price or stock sync, tracking updates, or manual order entry. I'd ask sellers to show the last time it broke and what it cost them, then prioritise that over whichever API integration is most technically interesting.

Collapse
 
getdropflow profile image
jinguo ren •

Thanks, Shashank — this is almost word-for-word how the roadmap got set. Price and stock sync was the one that kept coming up: a supplier changes a price overnight, the store keeps selling at the old price, and the seller finds out from the order itself — after the margin is already gone. That's why sync and pricing rules shipped ahead of the more "interesting" API work.

Your "show me the last time it broke and what it cost" is a better interview question than anything I was asking. Borrowing it.

Curious: of the three — sync, tracking, manual order entry — which one has cost you the most?