Skip to content

Automation · Orders and fulfillment

From a WooCommerce order to an Aveonline shipping label

How an AI agent takes the paid orders from WooCommerce, creates them in Aveonline and confirms them so the shipping label is generated.

How do I move orders from my store into Aveonline without retyping them one by one?

A scheduled task checks the paid WooCommerce orders every so often, verifies that each product exists in the Aveonline catalog, creates the order there with the external reference of the original order and confirms it, which is the action that generates the shipping label with the carrier and returns the freight cost. The tracking number and the carrier go back into WooCommerce as an order note, so the buyer hears about it through the same channel where they bought, and nobody retypes an address.

What starts it

At a set time

A task on a recurring trigger that runs every so often over the orders in processing. It is scheduled rather than event driven because the orders live in WooCommerce, not in Meteor: the store is what you have to go and look at.

A task on a recurring (cron) or date and time trigger. It runs on its own, with nobody logged in.

Who runs it

Met for fulfillment operations

It is an internal Met: it does not talk to buyers, it works for whoever ships. It needs the store tools and the Aveonline tools at the same time, which is exactly what you cannot do with two browser tabs open without making a mistake.

What you need connected

6 steps · 13 tools

The procedure, step by step

Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.

  1. 1

    Pull the orders that are ready to ship

    WooCommerce's order listing filters by status and date range; what matters is what sits in processing and has not left yet. The detail of each order brings the line items with their SKU and quantity, the totals and the full shipping address, which is exactly the raw material of the dispatch order.

  2. 2

    Check that the product exists in Aveonline

    Aveonline keeps its own catalog and it is not managed from here: if the reference is not loaded there, the order cannot be created. The product listing searches by name or reference and the detail confirms variants, weight, dimensions and stock. Finding out beforehand is a warning; finding out while creating the order is a half built order.

  3. 3

    Create the order in Aveonline with your own reference

    The order is created with the buyer details, its line items and an external reference pointing at the original order number. That reference is what later lets you confirm or void it without depending on Aveonline's internal identifier. If you attribute sales by rep, the Aveonline sales rep listing returns who to assign it to.

  4. 4

    Confirm it so the label comes out

    Confirmation is the action that generates the shipping label with the carrier, and the response carries the carrier, the freight and the provider cost. You can confirm by external reference, which is the practical route when what you stored is the store order number and not Aveonline's internal identifier.

  5. 5

    Send the tracking number back to the store

    A WooCommerce order note can be marked as a note to the customer, and in that case the store emails them the text. That is where the carrier and the tracking number go. The order status only moves once the dispatch is genuinely confirmed, not before.

  6. 6

    Fix what went wrong, and know the limits

    While the order has no label you can edit it or move its internal status (preconfirmed, invoiced, dispatched). Once the label is generated, Aveonline rejects certain changes, and voiding fails if a shipment number is already attached: that is the point of no return, and it is better known beforehand than during.

Before you start

What you need ready

The Met solves none of these for you. If one is missing, the automation stops there.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

FAQ

Questions about this automation

Because in Aveonline they are two different things: creating registers the order, and confirming is what generates the label with the carrier. Splitting them lets you review before a transport document exists, which is what almost nobody wants happening unattended.

The order stays created but unconfirmed, and the case is reported so somebody can complete it. That beats generating a label with an address the carrier will send back as an exception three days later.

The shape of the automation is the same and Shopify's order tools exist, but the steps that reference the store change connector. It is not the same automation: it is its equivalent.

Keep going

Other automations built on the same tools

Want this automation running on your own data?

We will show it to you with your accounts connected, not with a canned demo.