Ecwid orders, dispatched to your own drivers.
Create a webhook in Ecwid’s control panel and every new order lands on the PrivateMile board with the customer, address and items attached — signed, verified and ready to dispatch.
How it connects
From a Ecwid order to a driver’s phone.
Nothing to install on your store and nothing to keep updated — the connection is a webhook you create once.
01
Create the Ecwid integration in PrivateMile
Settings → Integrations → Ecwid. PrivateMile generates a webhook URL and a secret for your store.
02
Add the webhook in Ecwid
Ecwid Control Panel → Apps → Custom Apps → create a webhook with the PrivateMile URL and the events order.created and order.updated. Ecwid signs each payload using the secret.
03
Dispatch as usual
Orders appear on the board as they are placed. Plan the route, assign or auto-dispatch, and the customer gets a tracking link when a driver is assigned.
What flows in
Every field the driver needs, already on the stop.
Orders arrive with the customer, address, items and notes attached — dispatch never retypes anything.
- Customer name, phone and email
- Shipping address, geocoded to a map pin
- Line items and quantities
- Ecwid order number as the reference
- Order comments from checkout
- Order updates, via the order.updated event
After the order lands
What your customers notice.
Tracking under your name
A live driver map, arrival window and notifications with your logo. Customers stop asking where the order is.
Signed payloads
Ecwid signs every webhook with the secret; PrivateMile verifies it before creating an order.
Proof on the order
Photo, signature and notes from the driver, attached to the order for the day a customer disputes a delivery.
How the Ecwid connection works
Ecwid can POST a JSON copy of an order to a URL of your choice on order.created and order.updated, and it signs those payloads with HMAC using your app secret. PrivateMile gives each Ecwid integration its own URL and secret, verifies every signature with a timing-safe comparison, and de-duplicates events so a retry never becomes a second order.
What dispatch sees
The order arrives with the customer, phone, geocoded shipping address, line items and checkout comments, with the Ecwid order number as reference. Plan it on the map, assign it or let auto-dispatch choose, and follow it to the door.
What the customer sees
A tracking link when a driver is assigned, on a page with your logo and colours — live map, arrival window, “arriving soon”, and proof of delivery when it lands. Nothing about PrivateMile appears.
More than one store
Each Ecwid store is its own integration and each depot its own warehouse with a zone. Orders route to the right site and reports break down by store.
Where in Ecwid do I add the webhook?
Control Panel → Apps → Custom Apps. Create a webhook with the URL PrivateMile gives you and subscribe to order.created and order.updated. The integration’s secret is what Ecwid uses to sign each payload.
Will an order update create a second delivery?
No. Updates arrive through the order.updated event and are matched to the existing order; PrivateMile de-duplicates so a resent event never creates a duplicate.
Does delivery status go back to Ecwid?
Delivery status goes to your customer through the tracking page, SMS and email. Every delivery event is available as an outbound webhook and a Zapier trigger for other systems.
Other integrations
Plugs into what you already run.
Connect Ecwid in an afternoon.
Create the integration on the trial, paste one webhook URL into your store, and watch the next order appear on the board.
Questions first? Tell us about your delivery day — or sign in.