Multiple suppliers Order splitting and tracking Returns and margin rules

Custom dropshipping webshop development

Building a webshop isn't the hard part. The hard part is keeping several suppliers reliable at the same time: stock that comes from different sources and goes out of date at different rates, orders that split into multiple shipments, returns that never pass through your warehouse, and margins that differ per supplier. Appfront builds the logic that makes all of that add up.

When you're on this page

This page is about webshops that sell what someone else ships, particularly the situation with more than one supplier. Your catalogue is then a combination of sources you don't control: one supplier delivers a CSV or XML file to an SFTP server overnight, another offers an API, a third a spreadsheet.

If that doesn't apply to you, a different page will be more useful. If you hold your own stock or work with a single supplier, look at webshop development. If you already run on WordPress, a WooCommerce webshop is often the quickest route. If you sell to business customers with their own price agreements and volume tiers, that belongs in a B2B e-commerce portal.

The distinction isn't cosmetic. With a standard webshop, stock is a number you keep track of; with dropshipping, it's an estimate of what a third party actually holds, with a shelf life that varies by supplier.

Combining sources into a single catalogue

Feeds, APIs and loose files are translated into one internal product model, matched on GTIN, so the same SKU from two suppliers remains a single item.

Splitting and routing orders

A single order is divided into purchase orders per supplier, each with its own confirmation, shipment and lead time, while the customer sees just one order.

A returns and credit flow that adds up

From cancellation notice through assessment, refund and credit note, with a record of where each return's costs land.

Four places where things go wrong in practice

These only become visible at volume, and they can't be fixed with a setting in the admin panel.

The gap between an overnight feed and a real-time API

Supplier A and B both carry the same SKU. A sends a stock file at 03:00, while B has an API you can query in real time. At 15:00, A sells its last unit to someone else. Your shop only finds out the next night and meanwhile shows the item as available when it isn't. If a customer orders within that gap, you get overselling: cancelling, refunding, explaining, and with some luck, not receiving a bad review.

Synchronising more often only moves the gap. What does work: record how fresh the data is for each source, set the buffer to match, and choose the preferred supplier per order line based on currency of stock rather than purchase price.

One order, three shipments, three expectations

A customer orders three items and receives three parcels from three suppliers, with three tracking codes and three delivery dates. Most platforms send three separate shipping emails. The customer reads the first, sees one item arriving and assumes the rest has gone missing. That generates WISMO enquiries, the messages from customers asking where their order is.

The difference lies in communication, not logistics: an order confirmation that states multiple delivery moments, a tracking page showing status per line, and a system that flags a missing shipment before the customer calls.

Returns that never pass through your warehouse

The most painful part, because it raises three questions at once, which are often only asked at the first return. Does the customer send it back to you or to the supplier? Who judges whether the product is as it should be, and therefore whether there has been a loss in value? And who credits whom: you refund the consumer, but when and how do you receive a credit note?

Without a system that links every return to a purchase order, supplier and credit note, your administration quietly goes out of balance: you refund consumers for goods you were never credited for.

Margins that differ by supplier and by region

Purchase prices change, sometimes with every feed. Supplier A charges shipping per consignment, supplier B per item, and supplier C adds a surcharge for the Wadden Islands. If you apply one mark-up percentage across the entire catalogue, you will sell part of your range below cost as soon as the purchase price rises, and you won't notice, because the order simply came in.

Pricing is therefore a logic layer of its own: rules per supplier, product group and shipping region, with a minimum margin that takes an item off sale rather than selling it at a loss.

From supplier feed to credit note

At its core, this is a chain of four operations, each with its own failure behaviour. That is the difference between a shop that quietly drifts out of line and one that corrects itself.

1
Importing and normalising

A separate translation layer per supplier into one internal model, matched on GTIN, with checks that hold back a partial or empty feed.

2
Determining availability

Decide per item what can be sold: buffers per source, a delivery time promise per supplier and a minimum margin as the lower limit.

3
Splitting and ordering

The order is divided into purchase orders per supplier, via API, EDI or feed. If a confirmation fails to arrive, it becomes a task.

4
Feedback and reconciliation

Shipping notifications, tracking codes, returns and credit notes are recorded against the original order line, so that sales, purchasing and accounts remain in agreement.

You remain the seller, whoever ships

That is the principle on which the design rests. To the consumer, you are the counterparty, even if the parcel comes from a warehouse you have never seen. The conformity requirement under Article 7:17 of the Dutch Civil Code and the statutory guarantee rest with you, and in a consumer sale you must deliver without undue delay and in any case within thirty days. The fourteen-day right of withdrawal after receipt applies in full; the consumer is liable for loss of value only if they handled the product beyond what was necessary to establish its nature, characteristics and functioning.

The ACM has a separate checklist for dropshipping and supervises it. Two points bear directly on your software: before purchase you must state the place or country of dispatch and that a third party delivers directly to the buyer, and a webshop established in the Netherlands must display a Dutch return address. Origin and return destination must therefore be known per order line.

If a product comes from outside the EU, the General Product Safety Regulation, Regulation (EU) 2023/988, applicable since 13 December 2024, requires a responsible economic operator in the EU. If there is none, the role quickly falls to you. On the tax side, the exemption for small consignments was abolished on 1 July 2021; below the threshold, the Import One-Stop Shop (IOSS) scheme applies.

  • Country of dispatch recorded per order line
  • Return address and return costs per supplier
  • Delivery time promise per source, not store-wide
  • Withdrawal and loss of value as a separate process
  • VAT and import logic separate from the pricing rules
CSV, XML and JSON feeds SFTP import with validation REST and GraphQL APIs EDI: ORDERS, ORDRSP, DESADV PRICAT and INVRPT GTIN matching Webhooks and queues PostNL, DHL and DPD Sendcloud and MyParcel Mollie and Adyen Exact Online
Not yet sure about a large project?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.

Explore OneDayBuild →

When custom is not the answer

If you have a single supplier, a manageable range and shipping rates that don't vary by region, an existing platform with that supplier's dropship integration will get you live faster and cheaper than custom development. That applies to a good share of dropshipping webshops, and it is the right choice rather than a stopgap. We would rather say so in the first conversation than halfway through a project.

Custom development only starts to pay off with multiple suppliers carrying partly the same range, margin rules that differ by supplier or region, or a supplier without a ready-made integration. Being held back by an app provider's roadmap is also a real reason to take the logic into your own hands.

Be honest about the upkeep that comes with it: every integration you have built becomes your maintenance. The most sensible route is therefore often the hybrid approach: keep your existing webshop or WooCommerce store, and have only the stock, order and returns logic custom built behind it.

  • One supplier, standard rates: existing platform
  • Overlapping range across two or more suppliers: custom development
  • Margin or shipping rules per supplier or region: custom development
  • Supplier without a ready-made integration: custom development
  • Returns that must reconcile with the accounts: custom development
  • Business customers with their own terms: B2B portal

Frequently asked questions about a dropshipping webshop

The questions we most often receive just before someone makes a decision.

If you work with one supplier, a manageable range and standard shipping rates, an existing platform plus that supplier's integration will get you live faster and cheaper than custom development. For a good share of dropshipping webshops, that is the right choice. Custom development only makes sense with several suppliers carrying overlapping ranges, differing margin rules, or a supplier without a ready-made integration. Often the hybrid approach is the most sensible: custom only the logic behind your platform.

You are. To the consumer, you are the seller, regardless of who sends the parcel. The conformity requirement under Article 7:17 of the Dutch Civil Code and the statutory guarantee rest with you, and for a consumer sale you must deliver without undue delay and in any case within thirty days. The fact that you can later recover losses from your supplier changes nothing about your position towards the customer. Your system must therefore warn you early: a missing order confirmation is a signal to inform the customer.

No one can rule it out entirely: there is always a gap between your last stock update and the moment of ordering. What you can do is record, for each source, how up to date it is, and align the buffer accordingly. A supplier who sends a file once a night needs a wider margin than one with a real-time API. Whatever remains is handled with a clear message and an alternative, not a silent cancellation.

That requires an explicit choice in advance. The legal position is clear: the consumer has fourteen days to change their mind after receipt, notifies you of the withdrawal and is refunded by you. If your webshop is established in the Netherlands, the ACM requires you to provide a Dutch returns address. Operationally there are two routes: everything first comes to you, or the customer sends directly to the supplier, who reports receipt back. The first gives you visibility over any loss in value; with the second, everything depends on that report back.

Feed changes are the main recurring maintenance burden of a dropshipping webshop. That is why each supplier gets its own translation layer to a single internal model: if something changes on their side, only that one translation is affected, not your entire catalogue. There are checks on import, so that a partial or empty feed is blocked rather than applied. The delivered code, repository and documentation belong to you, so that another party can take over management.

Yes. The General Product Safety Regulation, Regulation (EU) 2023/988, has applied since 13 December 2024 and requires every product to have a responsible economic operator in the EU. If the manufacturer is based outside the EU and there is no authorised representative or importer, that role will quickly fall to you. On the tax side, the exemption for low-value consignments was abolished on 1 July 2021; below the threshold you can use the import scheme (IOSS).

Related services

If dropshipping does not suit your situation, one of these pages may be a better fit.

Webshop development

For those who hold their own stock or work with a single supplier: range, checkout and payments.

Building a WooCommerce webshop

For those on WordPress or wanting to move there, with room to add your own order logic behind it later.

Building a B2B e-commerce portal

For business customers with customer-specific pricing, tiered pricing and approval workflows.

If you combine your own stock with suppliers who ship directly, take a look at our dropshipment software for specialist retailers.

Getting your suppliers in order?

Tell us how many suppliers you work with, how they supply stock and prices, and where it hurts right now: overselling, split orders, returns or margins. In an initial conversation we'll work out together whether you need custom software for this.

Edit content