HubSpot field service
HubSpot Orders Object for Field Service
HubSpot orders object for field service: what an order records, its pipeline and associations, and how it sits beside a FieldRanger job on the HubSpot deal.
The HubSpot orders object for field service work records a confirmed purchase and how it is fulfilled. HubSpot describes orders as the operational side of a purchase, not billing or revenue recognition, and makes them available on all plans. FieldRanger starts from the deal: a won deal becomes a job, and the order sits beside it.
A field business meets orders when it sells goods that ship: a replacement unit, a parts kit, a product bought through an online store. The HubSpot field service page covers the deal-to-job model. This page covers the orders object as HubSpot documents it, and how an order and a FieldRanger job share one deal.
The HubSpot orders object: definition and availability
HubSpot's orders article, last updated 12 October 2026 and checked in November 2026, sets out the object as follows.
- Purpose. Orders record the operational side of a purchase. Billing and revenue stay with deals, quotes, payments, subscriptions and invoices.
- Availability. The article lists all products and plans.
- Creation. An order can be created by hand from the orders index page, imported, synced from an integration such as Shopify or NetSuite, or created by a workflow action. Importing needs Super Admin or Import permissions.
- Line items. Line items cannot be added when an order is created by hand.
- Contracts. Accounts in the Connected CPQ, Billing and Payments beta can have orders created automatically when a contract is created, changed through a change quote, or terminated.
HubSpot's objects overview adds that order data from an ecommerce platform can be synced and reported on in custom reports. The developer documentation frames the same object the same way: the Orders API is for "data related to ecommerce purchases in HubSpot".
Order properties, pipeline and associations
The properties show what an order is built to hold. The Orders API documents, among others, hs_order_name, hs_currency_code, hs_source_store, hs_fulfillment_status, the shipping address fields such as hs_shipping_address_city, hs_shipping_tracking_number and hs_shipping_status_url, and the pipeline fields hs_pipeline and hs_pipeline_stage.
The default order pipeline has two stages, In Progress and Contract Signed, per HubSpot's pipelines article. A custom pipeline needs a Starter, Professional or Enterprise subscription. The same article caps custom pipelines, shared across all objects and not counting each default pipeline, at 15 on Starter, 100 or 350 on Professional depending on the pricing model, and 350 on Enterprise (checked November 2026).
The Orders API lists associations to contacts, companies, deals, line items, carts, quotes, invoices, payments, subscriptions, discounts, tasks and tickets. On associated records, the order appears on an Orders card that shows its pipeline stage.
Orders compared with deals, work orders and invoices
Four records describe one sale, and each answers a different question. The deal records the sale and its value. The order records the purchase and its fulfillment: what ships, where, and with which tracking number. The work order records the field work: the checklist, the photos and the customer's signature on site. The invoice bills the customer.
HubSpot's default order properties stop at shipping and fulfillment. Custom properties can be added, but none of the defaults names a technician, a visit date or a job site checklist. The HubSpot work orders page covers the record that carries the visit.
An order and a FieldRanger job on one deal, step by step
The sequence below covers a sale that needs both: equipment that ships, then a technician who installs it.
- The sale is made on a HubSpot deal. When the deal is marked won, FieldRanger creates the install job from it, with the deal's context carried over.
- The office creates the order in HubSpot: CRM > Orders > Create Order, with the deal selected under Associate Deal with. An order synced from Shopify or NetSuite arrives through that integration instead.
- The order moves through an order pipeline. A custom pipeline can carry fulfillment stages such as Ordered, Shipped and Received, and the fulfillment status and tracking number properties hold the shipping detail.
- The dispatcher reads the Orders card on the deal. Once the stage shows the equipment has arrived, the dispatcher schedules the install job on the FieldRanger calendar.
- The technician completes the job in the FieldRanger mobile app. FieldRanger logs the completion and notes to the HubSpot timeline and updates the job status on the deal.
- FieldRanger generates the invoice from the completed work order.
- Verification: the office opens the deal. The Orders card shows the order at its final stage, the job status shows the install as complete, and the completion entry is on the timeline.
HubSpot records a manager reads
The deal is where the order and the job meet. The Orders card shows the purchase, the job status shows the field work, and the timeline holds the completions, notes and updates that FieldRanger logs. Photos taken on the job sync to the customer's HubSpot record, and FieldRanger fields can be mapped to HubSpot custom properties.
Reporting follows the same split. HubSpot custom reports can include synced order data, and revenue can be followed from lead to completed job in HubSpot reports. The HubSpot Service Hub dashboard page covers how those reports come together on a HubSpot dashboard.
Limits
- FieldRanger's documented HubSpot connections are contacts and companies, won deals that become jobs, job status on the deal, the timeline, job photos, custom property mapping, workflow triggers and revenue reporting. Orders are not among them.
- HubSpot documents workflow actions that create orders, and a FieldRanger job status change can trigger a HubSpot workflow. Joining the two is a HubSpot workflow configuration, to be tested on a test record before it runs on live deals. HubSpot's workflows article lists Professional and Enterprise subscriptions, and the Sales Hub pricing page lists up to 50 workflows with restricted triggers and actions on Starter and up to 300 fully customizable workflows on Professional (checked November 2026).
- An order created by hand has no line items. Line items reach an order through an integration or the Orders API, which lists a line item association.
- Automatic orders from contracts depend on a HubSpot beta, and HubSpot notes that edits to an order associated with a contract do not reflect on the contract.
Frequently asked questions
What is the orders object in HubSpot?
Orders are a standard HubSpot object for confirmed purchases. HubSpot describes them as the operational side of a purchase, not billing or revenue recognition, with properties for fulfillment status, shipping address and tracking number.
Is the HubSpot orders object available on free plans?
Yes. HubSpot's orders article lists all products and plans. Creating a custom order pipeline needs a Starter, Professional or Enterprise subscription.
Can HubSpot orders be used as work orders?
The default order properties hold purchase and shipping details. None of them records a technician, a visit date, a checklist or a customer signature, which a field work order needs.
How are orders created in HubSpot?
By hand from the orders index page, by import, through integrations such as Shopify and NetSuite, by workflow actions, through the Orders API, or automatically from contracts for accounts in a HubSpot beta.
Does FieldRanger create HubSpot orders?
Orders are not among FieldRanger's documented HubSpot connections, which cover contacts, companies, deals, the timeline, photos, custom properties and workflow triggers. A HubSpot workflow configured in the account can create orders.
Orders and jobs on a HubSpot account
An order and a job can share a deal without either one doing the other's work. The HubSpot field service overview shows the job side in full, and the HubSpot work orders page covers what the technician records on site. The order pipeline is configured in HubSpot settings. The job side starts with a 14-day trial that needs no card: Start free trial, with plans on pricing.
FieldRanger runs field service inside HubSpot
Estimates, scheduling and dispatch, a technician app and invoicing on the HubSpot records sales already keeps. Every plan starts with a free trial.
Book a demo