Integrations
WooCommerce local delivery: connect your store's orders to Porch Routes
A WooCommerce order becomes a Porch Routes delivery as soon as it's processing or on hold — no plugin to install, just a private webhook link pasted into WooCommerce's own webhook settings. Porch Routes reads the shipping address, items and the order-meta key your delivery-date plugin writes, then plans the order onto a route with your other deliveries.
Last updated By Porch Routes
How a WooCommerce order becomes a delivery
Porch Routes reads a WooCommerce store's own order webhooks over a private link you paste into WooCommerce's webhook settings, signed the way WooCommerce signs every webhook — HMAC-SHA256 over the raw body, including the WordPress character-decoding step WooCommerce applies to the secret first, already handled on Porch Routes's side. Order created, Order updated and Order restored create or update a delivery; Order deleted cancels one.
What happens depends on the order's status: processing and on-hold create or update the delivery; completed updates one that already exists, since a completed order Porch Routes never saw is history, not new work; pending waits until WooCommerce marks it processing; cancelled, refunded, failed and trash cancel it. You can also limit the connector to orders whose shipping method name contains text you choose, so a store offering both local delivery and flat-rate shipping only imports the local orders.
What Porch Routes reads from the order
The connector maps a WooCommerce order onto a delivery field by field:
| Delivery detail | Where it comes from in WooCommerce |
|---|---|
| Customer | The shipping name, else the company name, else the billing name |
| Address | The shipping address — geocoded by Porch Routes, since WooCommerce carries no coordinates of its own |
| Items | Line items with a quantity above zero; WooCommerce carries no item weight, so load weight is always unknown, never assumed zero |
| Instructions | The customer note |
| Delivery date & window | Order meta under the key you name in settings — WooCommerce has no delivery-date field of its own, so this is whatever your delivery-date plugin writes |
| Temperature | One setting on the connector — every order from this store is planned on a vehicle that can carry it |
Connect your store
Setup happens once, split between the two systems:
Add a store connector
In Porch Routes, go to Integrations → Store connectors and choose “Connect a store”. Pick WooCommerce, give it a name, and choose “Connect store” — Porch Routes creates a private link for it.
Add three webhooks in WooCommerce
In WordPress, go to WooCommerce → Settings → Advanced → Webhooks and choose “Add webhook” three times, once each for Order created, Order updated and Order deleted. Set Status to Active, API version to WP REST API Integration v3, and Delivery URL to the link from step one.
Copy or set the secret
Copy the Secret WooCommerce shows on the webhook form — or type a long random one of your own — and use the same secret on all three webhooks. Paste it into the connector's Signing secret field and choose “Save secret”; nothing is imported until this is saved.
Tell Porch Routes what to expect
Optionally match orders by a shipping-method name, set the order-meta key your delivery-date plugin writes, and choose what temperature these orders need.
Planning and running the route
Once an order arrives, it waits with every other open order for its delivery date, ready to be built into a route the same way as an order added by hand, imported from a spreadsheet or sent through the API — the same solver, the same vehicle and temperature rules, the same driver app and customer texts. A later store update only applies what actually changed in WooCommerce, so a day the office re-planned or a pin it corrected survives, and a delivered, failed or cancelled order is never changed by a later store update.
A missing or unreadable delivery date doesn't stall the order — it's planned for the next open day in its zone, or the soonest open day in any zone, or tomorrow, whichever applies, and noted on the connector so the office can move it. Set the connector to skip those orders instead if you'd rather hold them back.
Write-back into the store isn't built for WooCommerce — outcomes reach your own systems through a webhook endpoint instead, the same way an order placed by hand or imported from a spreadsheet does. Add one in Settings → Integrations → Webhooks, or use the Zapier app, to hear when a stop is delivered, fails or is skipped.
A connector, not a plugin
There's nothing to install in WordPress. You connect the store from Porch Routes's side — Integrations → Store connectors — and finish in WooCommerce's own webhook settings; your theme, checkout and other plugins are untouched.
Questions
Do I need to install a WooCommerce plugin?
No. Connect the store from Porch Routes — Integrations → Store connectors — and add three webhooks in WooCommerce's own settings. You'll still need whichever plugin already writes your delivery date onto the order, so Porch Routes can read its meta key.
Which WooCommerce orders become deliveries?
Orders marked processing or on-hold create or update a delivery. Completed orders only update one that already exists; pending orders wait for payment; cancelled, refunded, failed and trashed orders are cancelled.
Where does the delivery date come from?
WooCommerce has no delivery-date field of its own, so it comes from order meta under the key your delivery-date plugin writes — type that key's name into the connector's settings.
Does this write anything back into WooCommerce?
Not yet. WooCommerce write-back isn't built the way Shopify's is — to hear a delivery's outcome in your own system, add a webhook endpoint or use the Zapier app.
What about order weight for vehicle capacity?
WooCommerce line items carry no weight, so a WooCommerce order's load weight is always unknown rather than zero, and capacity limits simply don't bind on it. Temperature is still a hard rule, set once on the connector for every order from the store.
WooCommerce is a trademark of Automattic Inc. Porch Routes isn't affiliated with or endorsed by WooCommerce.
Plan your next delivery day in a few minutes.
Add your vehicles and a day of orders — by hand, from a CSV or over the API — and build your first routes.
Free up to 150 orders a month · No credit card