Route Each Dropshipping Order to the Best Supplier by Rules

Resilience and optimization. Relying on one supplier means a stockout or a price hike hits every order. With two or three suppliers for your key products, you can always ship from whoever is cheapest, fastest to the customer's country, or actually in stock today. For a US customer, a US-based supplier may cost more but arrive in days; for a price-sensitive product, the cheapest source wins. Rules let you encode that judgment once and apply it to every order automatically.

In a supplier table: each product maps to several suppliers, each with a cost, a shipping-time estimate per region, and a live stock flag. You set a priority — for example 'prefer fastest to the destination country, break ties by cheapest'. A Code node scores the candidate suppliers per order line against that priority and picks the winner. Changing strategy is editing the rule, not the workflow.

Once a supplier is chosen, an HTTP Request submits the fulfillment to that supplier's API (or drops it into their order sheet/portal). Because each supplier has its own endpoint and format, the workflow branches to the right submission node per supplier. The routing decision and the submission are cleanly separated, so adding a new supplier is adding one branch.

The scoring step filters out out-of-stock suppliers first. If none remain, the order is flagged and routed to a Slack alert instead of being sent anywhere, so you can back-order, substitute, or refund proactively rather than confirming an order you can't fulfill — which is how stores get chargebacks and bad reviews.