WooCommerce to Onfleet setup guide: connect your store in 10 minutes

You already run your deliveries through Onfleet. The routing, the driver app, the live tracking: all of that works. The part that does not is getting each WooCommerce order into Onfleet in the first place. Right now that probably means opening every new order, copying the address, phone number and delivery notes, and pasting them into a new Onfleet task by hand. This guide walks you through connecting the two properly, so a paid order becomes an Onfleet task automatically. Budget about ten minutes.

What you'll need

This is a short list. If you are already selling on WooCommerce and dispatching through Onfleet, you have most of it already.

• A live WooCommerce store on WordPress, with admin access to install plugins.
• An active Onfleet account with an organization set up and at least one team, plus your Onfleet API key (we get this in Step 1).
• The FleetConnector WooCommerce → Onfleet plugin and its license key. You can grab both from the WooCommerce to Onfleet integration page.

Step-by-step setup

Follow these in order. Each step builds on the previous one, and by the end a test order placed in WooCommerce will show up as a task in your Onfleet dashboard.

Step 1: Get your Onfleet API key

Log in to your Onfleet dashboard and open Settings → API & Webhooks. Under the API keys section, create a new key (label it something like "FleetConnector" so you know what it is for later) and copy the value. Keep this tab open or paste the key somewhere safe for a moment, because you will need it in Step 3. Treat it like a password; anyone with this key can create and read tasks in your Onfleet organization.

Step 2: Install the FleetConnector plugin

In WordPress, go to Plugins → Add New → Upload Plugin, choose the FleetConnector .zip file you downloaded, and click Install Now. When it finishes, click Activate. A new FleetConnector item appears in your WordPress admin sidebar. That is where all of the configuration lives.

Step 3: Enter your Onfleet API key and license key

Open the FleetConnector settings page. Paste your Onfleet API key from Step 1 into the API key field, and enter your FleetConnector license key to activate the plugin. Save. The plugin validates the API key against Onfleet right away, so you will know immediately whether the connection is good rather than discovering a typo three orders later.

Step 4: Choose which orders sync and map your fields

This is where you decide when an order becomes an Onfleet task and what data travels with it. Two things to configure:

• Order statuses that trigger a sync. Most stores dispatch on Processing (paid, ready to fulfil) or a custom status like Out for delivery. Pick the status that means "this order is ready to hit the road" so you are not creating tasks for unpaid or on-hold orders.
• Field mapping. Match your WooCommerce order fields to Onfleet task fields: the shipping address, customer phone number (Onfleet uses this to text the recipient), order notes or a custom instructions field, and a delivery window if you collect one at checkout. Getting the phone number and address mapping right here is what makes Onfleet's recipient notifications and geocoding work downstream.

Step 5: Place a test order and confirm the task in Onfleet

Do not skip this. Create a real (or test) order in WooCommerce, move it into the status you configured in Step 4, and then open your Onfleet dashboard. Within a few seconds you should see a new task appear with the correct recipient name, address, and phone number. Confirm the address geocoded to the right spot on the map and that the notes came through. If anything is off, the FleetConnector logs in your WordPress admin will tell you exactly what happened so you can fix the mapping and retry.

Step 6: Bulk-dispatch your existing orders

New orders now flow through automatically, but you probably have a backlog already sitting in WooCommerce. From the FleetConnector orders view (or the WooCommerce orders list), select the orders you want to send, choose the bulk dispatch action, and FleetConnector creates an Onfleet task for each one in a single pass, without clicking into 40 orders one at a time. This is also handy the morning after a sale or a promo, when a batch of orders lands overnight.

Common setup gotchas

A handful of small things trip people up. Check these first if a task does not appear or looks wrong:

• Missing phone number. If the recipient phone field is empty, Onfleet cannot send delivery notifications and the task can look incomplete. Make phone a required checkout field and map it in Step 4.
• Order status filter too narrow. If nothing syncs at all, your trigger status probably does not match the status your orders actually reach. If you dispatch on Processing but your workflow jumps straight to Completed, no task is ever created. Line the two up.
• HPOS enabled. WooCommerce's High-Performance Order Storage changes where order data lives. FleetConnector supports HPOS, but if you are running an older plugin build alongside it, update to the current version so it reads orders from the right place.

If a task still will not sync after those checks, work through our dedicated WooCommerce to Onfleet troubleshooting guide, which covers API errors, geocoding failures, and retrying stuck orders step by step.

Why a native plugin beats Zapier or manual entry

You could wire WooCommerce to Onfleet with a general automation tool like Zapier, or keep copying orders by hand. Both work until they do not. Here is why a purpose-built plugin holds up better:

• Reliability. FleetConnector understands WooCommerce order data natively and logs every sync, so when something fails you can see it and retry from your dashboard. A generic Zap breaks silently when a field changes, and manual entry breaks whenever someone is busy.
• No task limits. Zapier-style tools meter you per task, so your automation bill climbs with every order, and a busy month can quietly push you into the next pricing tier. A native plugin does not care whether you dispatch 50 orders or 5,000.
• Flat, predictable price. FleetConnector is a flat €199/year, full stop. No per-order fees, no external dashboard to manage, no surprise overage. You can see exactly what it costs on the pricing page.

As an illustration: a store shipping a few hundred orders a month on a per-task automation tool can easily spend more in a single quarter than FleetConnector costs for the whole year, while doing more work to keep the automation from breaking. Your actual numbers will depend on your volume, but the shape of it holds: metered automation gets more expensive as you grow, a flat plugin does not.

That's it: your orders now dispatch themselves

Once the connection is live, a paid WooCommerce order becomes an Onfleet task on its own, with the address, phone, notes and delivery window already filled in. No copy-paste, no missed orders, no per-task meter running in the background. If you have not set it up yet, start on the WooCommerce to Onfleet integration page, or check the flat €199/year pricing first. Either way you can be dispatching automatically in about ten minutes.