E-commerce Order Automation — From Payment to Shipping Label

Every e-commerce order travels the same road: the customer pays, someone picks and packs the parcel, hands it to a courier, updates the status, and notifies the buyer. With a handful of orders a day you do this by hand without even noticing. With dozens a day, the same repetitive work eats hours and multiplies mistakes: a wrong status, a notification that never went out, a parcel shipped late.

Order automation is not “a magic robot that runs the store for you”. It is the deliberate design of your process so that every repetitive step runs itself, triggered by an event. In this article we walk through the full order cycle and show where automation saves the most, and how to design that process for your own store.

The full order cycle in five steps

Before you automate anything, you need to see the process as a chain of consecutive stages. The classic e-commerce order cycle looks like this:

1. Payment — the order is paid (or cash on delivery is selected).
2. Picking — the warehouse gathers the products, packs them, marks them ready to ship.
3. Shipping — the parcel is dispatched, a label is generated, the courier takes over.
4. Status — the order moves to “shipped” and links to a tracking number.
5. Notification — the customer learns the order shipped, and later gets a review request.

Each transition between stages is an event, and every event can trigger an action. This is the foundation of automation: you don’t automate “the whole store”, you automate the individual transitions between steps.

Step 1: payment as a trigger, not the end of the work

In a non-automated store, a paid order is the moment a human’s work begins: someone has to notice the payment, change the status, and pass the order to the warehouse. In an automated process, payment is a trigger — an “order paid” event that pushes the order forward on its own.

Good practices at this stage:

• automatic status change from “new” to “paid / to fulfil”,
• stock reservation at the moment of payment, so you don’t sell the same item again in another channel,
• an immediate customer notification (“thank you, we’re preparing your order”),
• flagging orders that need attention (cash on delivery, pre-order, out of stock) — so a human handles only the exceptions.

The rule is simple: a human handles exceptions, automation handles the rule.

Step 2: picking — where automation shortens rather than replaces

You can’t automate the physical packing with software — but you can trim everything around it. The most time in picking is lost not on the packing itself, but on hunting for information: which orders are ready to pick, what exactly to pack, whether the stock adds up.

A central, normalised order view helps here: the warehouse works from a single queue instead of jumping between the Allegro panel, the store panel, and a spreadsheet. Add to that:

• shared inventory with consistent SKUs and variants (size, colour),
• filtering and search by order number or SKU,
• a clear “picking” status that automation assigns once the order enters fulfilment.

The fewer clicks a human needs to understand “what do I pack now”, the faster the whole stage.

Step 3: shipping and the courier label — the goal you build toward

This is the stage where automation delivers spectacular savings — and, at the same time, the one where you have to be honest about what works today. Ultimately the aim is that from the order data, with a single click (or no click at all), a courier label is produced, and the tracking number flows back into the system and links to the order.

What a well-designed shipping process looks like:

• the address and recipient details pulled straight from the order — no manual retyping,
• courier selection based on rules (weight, order value, country, customer preference),
• a label generated from the order data, and a tracking number stored against it,
• an automatic status change to “shipped” once the parcel is dispatched.

In Sellaro, courier integrations — such as InPost and others — and automatic labels are on the roadmap; we add them as modules on request within your plan. Today the platform centralises orders and lets you build rules around shipping events, and it is designed to reach full, hands-off dispatch over time. If you want a practical take on dispatching itself, see the post on automatic InPost labels for Allegro and WooCommerce.

Step 4: status and tracking — automation watches, not you

Statuses are where automation pays off fastest, because the “parcel dispatched” event is unambiguous. Instead of manually marking dozens of orders as shipped, you define the rule once: when a parcel is dispatched, then the status changes to “shipped” and the tracking number lands on the order.

It helps to think of this as WHEN → IF → THEN:

WHEN a new event fires (e.g. “order paid”) → IF a condition holds (e.g. “channel = Allegro and value > 200 PLN”) → THEN run an action (e.g. “send a notification and flag for priority shipping”).

Sellaro’s automation engine runs exactly on domain events (new order, status change) with conditions and actions. This lets you build your own paths instead of bending your store to a rigid tool template. We described how such a system carries orders through their life cycle in the piece on the Allegro order management system.

Step 5: notifications — the cheapest automation with the biggest effect

Notifications are usually the first automation step, because they’re cheap to implement yet sharply improve service quality. A customer who receives an email “your order has shipped, tracking number X” doesn’t write to ask “where is my parcel” — and that is a real saving in support time.

What is worth automating in communication:

• an order confirmation right after payment,
• a shipping notice with the tracking number,
• a review request a few days after delivery (important on Allegro, where ratings lift your listing),
• internal alerts (webhook, email) about an order that needs attention.

Sellaro’s notification layer covers email (SMTP) and SMS, and beyond that offers webhooks (HMAC-signed, with retries) for your own integrations plus a log entry. As a result, every event in the order cycle can trigger a message to the customer or a signal to another system.

How to design your own automation process

Don’t start with a tool — start with a map of your own process. A proven order:

1. Draw your order cycle with the real statuses you use (they may differ from the textbook).
2. Find the repetitive manual steps — these are candidates for automation (statuses, notices).
3. Start with the cheapest, most frequent ones — usually notifications and automatic statuses.
4. Leave exceptions to a human — cash on delivery, complaints, stock gaps; automation handles the rule.
5. Measure the effect — how many orders pass untouched by hand, and where the process stalls.

Treat invoices and courier labels as a goal you reach in stages, not a condition to start. The basic order — one view of orders, shared inventory, automatic statuses and notifications — delivers most of the savings before you even reach full shipping automation.

Frequently asked questions

Where should I start with order automation?

By mapping your own order cycle and pinpointing the repetitive, manual steps. The cheapest and most often worthwhile first moves are automatic statuses (e.g. “shipped” after dispatch) and email/SMS customer notifications. You add labels and invoices later.

Is order automation only for large stores?

No. The break-even point appears already at dozens of orders a day, or when a second sales channel arrives. The more repetitive work (statuses, notifications, retyping addresses), the faster automation pays off — regardless of store size.

Does Sellaro generate courier labels and invoices?

Courier integrations (including InPost) and accounting integrations are on the roadmap and we add them as modules on request within your plan. Today Sellaro centralises orders, maintains shared inventory, and lets you build event-based automations — and we are working toward full, hands-off dispatch.

What is a WHEN → IF → THEN rule?

It’s a way to describe automation: WHEN defines the event (e.g. “order paid”), IF adds a condition (e.g. “channel = Allegro”), and THEN runs an action (e.g. “send an SMS and flag for shipping”). Sellaro’s automation engine works exactly on this principle — domain events with conditions and actions.

Summary

Order automation isn’t a single switch, but the tidying of the whole cycle: payment becomes a trigger, picking gets one queue, statuses change themselves on events, and the customer is notified without human involvement. Courier labels and invoices are the natural goal at the end of that road — you reach them in stages, and you collect most of the savings earlier, on statuses and notifications.

Sellaro centralises orders from all channels and gives you an event-based automation engine; couriers and accounting are added as modules on request. See the Sellaro pricing — a flat fee with a generous limit, all integrations included, and 0% commission on sales value. And if an integration you need is missing — let us know, we’ll add it for free.