One integration layer across storefront, ERP, and every supplier

Learn more
A Alumio vivid purple arrow pointing to the right, a visual representation of how to access more page material when clicking on it.
Go back

Purchase order automation and the delivery date you promised

By
Saad Merchant
Published on
October 2, 2026
Updated on
October 2, 2026
IN CONVERSATION WITH
Email icon
Email icon

A customer orders a garden bench on Tuesday morning. The retailer has never held one in a warehouse, so the order has to reach the manufacturer who makes it. Purchase order automation sends it, turning the customer order into a supplier order the moment it is placed. Without it, a person reads the order and retypes it into an email or a supplier portal. At low volume that works, and most businesses start there. Retyping is only the visible problem. The harder work is keeping stock, prices, lead times, and shipment confirmations moving between two companies that use different systems and different product codes. Businesses connect those systems through an integration platform-as-a-service (iPaaS), so each supplier connects once rather than to every internal system separately. Orders then reach suppliers in minutes, and the delivery date on the confirmation email is one the supplier can actually meet.

What purchase order automation sends to the supplier

Supplier-direct fulfillment means the retailer sells an item it never physically holds. The customer buys from the retailer, and the supplier picks, packs, and ships. Drop-ship is the retail name for the same arrangement, and wholesalers call it supplier-direct.

The retailer still owns the promise. It took the money, it set the delivery date, and it answers the phone when the parcel is late. It does not own the stock, the warehouse, or the shipping system. Everything it tells the customer comes from data a supplier sent it.

One thing goes out to the supplier, and four come back:

  • The purchase order out: what to ship, to whom, at the agreed cost price, with the service level the customer paid for at checkout
  • Availability in: what the supplier can actually ship this week, which is the figure the storefront sells against
  • Lead times in: how long the supplier takes, which is what the delivery date at checkout is calculated from
  • Shipment confirmation in: what left, when, and with which carrier reference, so the customer gets tracking
  • Invoice lines in: what the supplier charged against what the retailer sold, line by line

The outbound direction is the easy one, and most businesses get it working. Everything that comes back is harder, because it changes at the supplier end. These flows sit alongside ERP, PIM, and payments among the essential e-commerce integrations.

Why does drop-ship break at the delivery promise?

The storefront quotes a delivery date at checkout. That date is calculated from stock the retailer does not hold and a lead time the supplier controls. If either number is stale, the promise is wrong before the order is placed.

Spreadsheets are how most of these relationships start. A supplier emails a stock file weekly, someone uploads it, and the storefront sells against last Tuesday's availability. It holds until the supplier has a busy week.

Product codes are the second problem. The retailer's SKU and the supplier's article number are different strings, mapped in a spreadsheet that one person maintains. Every new product is a manual mapping, and every unmapped product is an order that fails silently.

Several suppliers multiply both. A retailer running twenty drop-ship suppliers has twenty file formats, twenty lead-time conventions, and twenty people to email when something goes wrong.

Turn AI ambition into action

Portrait of Leonie Becher Merli, Business Development Manager at Alumio

Get a free assessment of your integration needs and next steps

Portrait of Leonie Becher Merli, Business Development Manager at Alumio

Automate purchase orders to every supplier from one integration platform

Automate purchase orders to every supplier from one integration platform

What manual supplier ordering costs

Drop-ship is sold internally as a way to expand the catalog without buying stock. The cost shows up somewhere else, in the gap between what the storefront says and what the supplier can do:

  • Orders that sit overnight: a customer buys at 18:00 and the purchase order reaches the supplier at 09:00 the next day, losing a full picking day on every order
  • Promises nobody can keep: a delivery date calculated from a lead time the supplier revised two weeks ago
  • Overselling into an empty supplier: a cancellation email the customer did not expect, because the stock file was five days old
  • Tracking that arrives by hand: a carrier reference copied from a supplier email into the order system, or not copied at all
  • Margin nobody can verify: supplier invoices that cannot be reconciled line by line against what was sold

None of these are supplier failures. The supplier shipped what it was told, when it was told. The retailer simply told it late, using numbers that had already changed.

How an integration platform automates purchase orders

An integration platform-as-a-service (iPaaS) gives a business one place where all its systems connect. Every system connects to it once instead of connecting directly to each other, and the platform moves and reshapes the data between them. Retailers already use it for ordinary work: pushing storefront orders into the ERP, returning stock figures to the sales channels, and sending shipments to a carrier.

A supplier connects the same way. The supplier becomes one more connected system rather than an inbox. The purchase order becomes a message like any other, carrying the item, the quantity, the address, and the agreed cost price.

The Alumio integration platform provides features that can be configured to run supplier-direct fulfillment end to end. Four of them do most of the work:

  • A Route that raises the purchase order: a Route can be built between the storefront or ERP and the supplier's system, so a customer order becomes a supplier purchase order within minutes of checkout
  • A Transformer that handles product codes: a Transformer can be configured to map each supplier's article numbers and units onto the retailer's SKUs, so a new supplier is a mapping rather than a project
  • Availability and lead times flowing back: supplier stock and lead-time changes can be carried into the storefront as they happen, so checkout quotes what the supplier can actually do
  • Confirmations and costs recorded: shipment confirmations and invoice lines can be routed back into the order system and the ERP, which makes tracking automatic and margin checkable

Because the supplier connects to the platform rather than to each internal system, the twentieth supplier costs roughly what the second one did. The same pattern applies to B2B e-commerce features, where the storefront is a channel onto systems that already hold the answers.

AFL Groep is a Dutch wholesale logistics supplier running webshops across the Netherlands and Belgium. It implemented Alumio to automate day-to-day order processing and inventory management, connecting Kerridge, Adobe Commerce, and the Optiply replenishment system through one platform. Orders, stock, and prices now stay in sync across every shop.

What automated purchase orders give the business

Supplier-direct fulfillment is a commercial decision that gets implemented as an operational one. The commercial case is a wider catalog with no stock risk. The operational reality is that a retailer's reputation now depends on data it receives from companies it does not control.

An integration platform closes the distance between those two things. It raises the purchase order while the customer is still on the thank-you page, and keeps availability current enough to quote from. It also records what the supplier confirmed, so the retailer can answer a question without sending an email.

The business ends up being able to add suppliers without adding headcount, and to make a delivery promise it has some reason to believe.

No items found.

FAQ

Integration Platform-ipaas-slider-right
What is purchase order automation?

Purchase order automation turns a demand signal into a supplier purchase order without anyone retyping it. In supplier-direct fulfillment, the demand signal is a customer order on the storefront, and the purchase order goes to the supplier who holds the stock. It covers the order, the cost price, the delivery address, and the service level. It also depends on product codes being mapped between the two companies in advance.

Integration Platform-ipaas-slider-right
What is the difference between dropshipping and 3PL fulfillment?

With a third-party logistics provider, the retailer owns the stock and the provider holds and ships it. With drop-ship, the supplier owns the stock and ships it directly to the customer. The integration differs accordingly: a 3PL reports on the retailer's own inventory, while a supplier reports on inventory the retailer can see but not control.

Integration Platform-ipaas-slider-right
Why do drop-ship delivery dates go wrong?

The delivery date at checkout is calculated from supplier stock and supplier lead times, both of which change at the supplier's end. Where those arrive as a weekly file, the storefront quotes from data that can be several days old. Continuous exchange narrows the gap, and surfacing the supplier's own lead time rather than an internal average removes the second source of error.

Integration Platform-ipaas-slider-right
How does an integration platform support supplier-direct fulfillment?

An integration platform-as-a-service (iPaaS) can be configured to raise a supplier purchase order as soon as a customer order is placed, rather than in an overnight batch. It can map each supplier's article numbers and units onto the retailer's SKUs, carry availability and lead times back into the storefront, and record shipment confirmations and invoice lines. Each supplier connects to the platform once rather than to every internal system separately.

Integration Platform-ipaas-slider-right
How many suppliers can a retailer realistically drop-ship from?

The limit is usually integration effort rather than commercial appetite. Where each supplier is a separate file exchange and mapping spreadsheet, effort grows with every addition and caps the catalog. Where suppliers connect through a shared integration layer, adding one is a mapping exercise, which is what allows a retailer to run twenty or more.

Integration Platform-ipaas-slider-right
What should a drop-ship agreement specify about data?

How often stock and lead times are sent and by what method, and the format and identifier the supplier uses for products. It should also state how quickly a purchase order is acknowledged, and when shipment confirmation with carrier tracking is returned. Agreements negotiated on cost price and margin frequently leave these out, and they determine whether the arrangement works day to day.

Get a free assessment of your integration needs

Laptop screen displaying the Alumio iPaaS dashboard, alongside pop-up windows for generating cron expressions, selecting labels and route overview.