Instance · Ecommerce
Ecommerce Orders Introduction
Last updated 1 November 2026
Customer purchases: items, payments, statuses, shipping, PDFs and webhooks.
An order is a purchase a customer has made. It holds what they bought, what they paid, where it goes and how far it has got. You can follow an order from payment through to dispatch, add the freight supplier and tracking code, record payments, and print an invoice, a picking slip or a packaging label.
Where to find orders
In the admin, open Ecommerce and choose Orders. Each order has sections for its items, discounts, payments, shipping, PDFs, activities, notes and history.
What an order holds
| Part | Examples |
|---|---|
| Status | The order status, the payment status and the shipping status, tracked separately |
| Customer | The CRM contact and company, with a copy of their details |
| Addresses | Billing and shipping addresses, copied from the CRM or typed in |
| Money | Subtotal, tax, shipping, discounts, processing fee, total and amount paid |
| Shipping | Freight supplier, method, option, tracking code and link, dispatch and delivery dates |
| Links | The quote it came from, or a pipeline opportunity |
PDFs from an order
Three documents come built in: a tax invoice, a picking slip and a packaging label. They use your CMS globals, such as your logo and company details, for their header.
From code and other systems
The Ecommerce API manages orders at /ecommerce/api/v2/orders. It sends an order_created or order_updated webhook to the address set in Ecommerce webhooks. A payment record notes a payment against an order; it does not charge a card.
Note
The docs instance has no orders, so none was read. The fields come from the Ecommerce module reference in the Insites Logic Engine.
Common mistakes
- Changing the CRM contact and expecting the order to follow. The order keeps a copy of the details from when it was placed.
- Treating a payment record as a charge. Take the payment through Stripe; the record only notes it.
- Expecting more than one webhook address per event. The module uses one address for each event.