HubSpot ecommerce integration without using the CRM as the books

The store already takes orders. HubSpot already holds contacts and the lifecycle. The gap is contacts, companies, and orders — or deals — on the CRM object APIs. We will tell you what HubSpot should store, and what still belongs in Xero or the warehouse.

Australian ecommerce team. We look at the store and the HubSpot portal before anyone talks about a connector.

Still running a store that needs HubSpot?

The store still takes orders. HubSpot still holds the contact. That is why the two have been left talking through a form embed, or through a native ecommerce app that only covers part of the catalogue.

HubSpot is a customer platform — CRM plus marketing, sales, and service. The vendor lists a Sydney office as Asia Pacific and Japan HQ: 123 Pitt Street, Angel Place, Level 30, Sydney NSW 2000, and a NZ phone line on the same contact page. That is regional presence, not an install-base. We will not invent an Australian portal count.

You might recognise one of these:

  • Checkout creates a customer marketing never sees
  • Deals are opened by hand after a B2B web order
  • A HubSpot ecommerce app covers Shopify and not the CMS you actually run
  • Line items never land, so revenue in HubSpot is a guess
  • Someone wants HubSpot to hold GST invoices because Commerce Hub has an Invoices object
  • Contacts duplicate every time a guest checks out

You do not need a new storefront, or a marketing-automation pitch. You need a clear read on the HubSpot portal you already have.

Why these connections stall

HubSpot has CRM object APIs. The stall is rarely “there is no API”. It is objects, OAuth, and asking HubSpot to be Xero.

CRM objects

OAuth sunset

Orders vs deals

Not the ledger

The official surface is REST CRM object APIs, date-versioned.

Current docs use /crm/objects/2026-03/{object}. OAuth 2.0 is required for multi-account and marketplace apps. The token endpoint family includes /oauth/2026-03/token. Legacy /oauth/v1/token is documented as heading to sunset on 16 February 2027. A private integration that still uses the legacy token path has a date. Standard objects that look like a store job: contacts, companies, deals, orders, line items, products, invoices, payments, quotes.

Contacts and companies are the first write, not a side effect.

Checkout should create or update a contact, and a company when the buyer is a business. Guest checkout without a match rule is how the portal fills with junk. Association between contact, company, and order (or deal) is the work. A plugin that only dumps an email address is why sales still live in the store admin.

Orders and deals are a portal choice.

Some portals want the Orders object and line items. Some still live on Deals. Products need a catalogue if line items are going to mean anything. Invoices and payments only belong here if Commerce Hub is actually in play — and even then HubSpot is not the GST ledger of record. Xero or MYOB still does the books.

HubSpot is CRM and marketing, not warehouse stock.

Do not sync “available qty” into HubSpot and expect operations to pick from it. Stock lives in Cin7, Unleashed, or an ERP. HubSpot can know that an order happened. It should not be asked to know what is on the shelf.

None of that makes the portal or the store worthless. It does mean “turn on the HubSpot ecommerce sync on Monday” is usually the wrong first move on a custom CMS.

How we work

We start with the portal and the store, not with a marketplace listing we do not have.

1

Look at what you have

Store platform, HubSpot hubs actually licensed (Marketing, Sales, Commerce), whether a native ecommerce app already runs, and where invoices and stock live. We will tell you whether the first object is a contact, an order, or a deal.

2

Decide the job

There are three honest outcomes. We recommend one, not all three.

3

Do the work in stages

Contacts and companies first, then products, then orders or deals plus line items. A HubSpot sandbox or a spare pipeline beats a Friday flood of guest contacts.

4

Hand it back so the next person can run it

Source, the app and scopes, and a short record of which object a web order becomes.

Three honest outcomes

  • Connect the store to HubSpot: create or update contacts and companies from checkout; log orders (or deals) plus line items; sync a products catalogue; optional invoices or payments only if Commerce Hub is in scope. Custom API work. No published CoSource HubSpot ecommerce case.
  • Fix a broken connector when a native app or custom job still almost works: move OAuth off the legacy token path before 16 February 2027, stop duplicate contacts, or stop treating deals as orders when the portal has moved on.
  • Decide not to connect when HubSpot’s own ecommerce app already covers this storefront, when the real job is Xero, or when marketing only needs a form and not the order book.

We will not tell you HubSpot replaces Xero or MYOB for GST. We will not invent an AU portal count. If HubSpot’s native app already covers your platform, that may be enough. If you want an honest fork in the road, talk to us.

What we need for the first call

A store URL and which HubSpot portal is enough to start.

  • Which store: nopCommerce, AbleCommerce, Shopify, or another CMS
  • Whether a HubSpot ecommerce app is already connected
  • Contacts and companies only, or orders / deals / line items as well
  • Whether Commerce Hub invoices or payments are actually in use
  • Where GST books and stock live today
  • What “done” looks like: a working sync, a repaired app, or a clear picture first

The first call is 30 minutes. You leave with a recommendation you can take to a manager, not a CRM estimate pulled from thin air.

Related work

We have not published a HubSpot ecommerce case. NESS is nopCommerce and Dynamics NAV 2018. Windsor is Peach and Xero. Neither is HubSpot.

CoSource is a Sydney software firm and a nopCommerce Gold Partner. Services include CRM & ERP integration on nopCommerce, AbleCommerce, and Shopify. That is a capability, not a HubSpot case study. A HubSpot portal still starts with its own assessment.

FAQ

Can checkout create a HubSpot contact and order?
Yes. Contacts and companies from checkout; orders (or deals) plus line items; products if you want those lines to mean something. Associations are part of the job.
Does HubSpot replace Xero or MYOB?
No. HubSpot is CRM and marketing. Invoices in Commerce Hub do not make it the GST ledger.
What is the OAuth date we should care about?
Legacy /oauth/v1/token is documented as heading to sunset on 16 February 2027. New work should use the current token family.
Do you have a HubSpot store case?
No. We will not invent one or an Australian portal count.
We already have the HubSpot Shopify app.
If the store is Shopify and that app does the objects you need, you may not need us. If the store is nopCommerce or another CMS, the marketplace app is not the answer.

Talk through the HubSpot connection you already need

Thirty minutes. Bring a store URL and which objects marketing actually uses. We will tell you whether to connect, fix the app, or leave HubSpot as CRM and the books where they are.

Book a free 30-minute discovery call