Unleashed ecommerce integration without guessing at stock

The store already takes orders. Unleashed already holds StockOnHand. The gap is warehouse-aware availability, sales orders, and the fact that a missing field on the Unleashed API can blank a product. We will tell you what to sync, and what Xero already does.

Book a free 30-minute discovery callTalk through your Unleashed connection

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

Still running a store that needs Unleashed?

The store still takes orders. Unleashed still holds the warehouse. That is why the two have been left talking through a morning export, or through a script that overwrites products because someone omitted a field.

Unleashed is cloud inventory, order, and production software for product businesses. It was founded in Auckland in 2009, later opened offices in Australia and the UK, and was acquired by The Access Group in November 2020. The vendor describes daily use for sales orders, inventory, and purchase orders. It is inventory software with features that overlap ERP. Unleashed itself does not claim to be a full ERP, and neither will we.

A common AU/NZ pattern is Unleashed for stock and Xero for the books — Unleashed’s own app integrations, not a CoSource product. That pattern is why a store connector has to decide who creates the invoice.

You might recognise one of these:

  • The site oversells because it reads a single stock number, not StockOnHand by warehouse
  • Sales orders are re-keyed into Unleashed after checkout
  • A sync “updated” a product and blanked fields that were not in the payload
  • Unleashed already posts to Xero, and someone wants the store to post too
  • Prices and products are right in Unleashed and wrong on the storefront by afternoon
  • You were told Unleashed would replace the ERP, and the finance team still lives in Xero

You do not need a new storefront, or an ERP replacement pitch. You need a clear read on the Unleashed account you already have.

Why these connections stall

Unleashed has a public REST API. The stall is rarely “there is no API”. It is warehouses, omitted fields, and a second poster into Xero.

StockOnHand

No partials

Orders not GL

Xero already

Stock is warehouse-aware, or it is a lie.

The API is REST at https://api.unleashedsoftware.com/{Endpoint}. JSON or XML, via Content-Type / Accept. Auth is API ID plus API Key from the account owner. Ecommerce-relevant resources include SalesOrders, Products, StockOnHand, Customers, Invoices, SalesShipments, Warehouses. StockOnHand is the read you want for a storefront, not a guess from the last product export. If you sell from one warehouse and manufacture in another, a single figure will oversell.

There are no partial updates.

Unleashed’s API does not do PATCH-style “only change these fields”. Omitted fields can be blanked. A store sync that sends SKU and price and forgets description, attributes, or supplier fields will look successful and still wreck the product. That is a design constraint, not a footnote.

The store job is orders and stock, not the GST ledger.

Push SalesOrders. Sync Products, prices, and Customers. Optionally invoices and SalesShipments if you have decided Unleashed is allowed to invoice. Do not treat Unleashed as the place the BAS is prepared. That is usually Xero, often through Unleashed’s native link.

Xero may already be connected.

Unleashed documents its own Xero integration. If that is on, the store should not also create the Xero invoice. Same sale, two invoices, a bookkeeper problem. Ask who posts financials before writing the second connector.

None of that makes the catalogue or the Unleashed file worthless. It does mean “push the product record on Monday” is how fields get wiped.

How we work

We start with the Unleashed account and the store, not with a generic inventory plugin.

1

Look at what you have

Store platform, warehouses the site may sell, whether Unleashed already talks to Xero, and which resources anyone already calls. We will tell you whether the first job is StockOnHand reads or SalesOrder writes — and we will not send a partial product update.

2

Decide the job

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

3

Do the work in stages

Warehouses and StockOnHand first, then Products and Customers with full payloads, then SalesOrders. A sandbox or a spare product beats a Friday blanking of the live catalogue.

4

Hand it back so the next person can run it

Source, the API ID identity, and a short record of which endpoint creates which document.

Three honest outcomes

  • Connect the store to Unleashed: pull StockOnHand (warehouse-aware), push SalesOrders, sync Products / prices / Customers, and only then invoices or shipments if that is the design. Custom API work. No published CoSource Unleashed case.
  • Fix a broken connector when a script still almost works: stop partial product writes, read the right warehouse, or remove a double-post into Xero.
  • Decide not to connect when Unleashed’s own ecommerce or Xero apps already own the job, when the site should not sell live qty yet, or when stock truth is about to move to another WMS.

We will not tell you Unleashed is a full ERP. We will not invent an Australian customer count. If Unleashed’s own Xero and store apps already do this, 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 Unleashed account is enough to start.

  • Which store: nopCommerce, AbleCommerce, Shopify, or another CMS
  • Which warehouses the storefront may sell
  • What should sync: StockOnHand, SalesOrders, Products, Customers, invoices, shipments
  • Whether Unleashed already posts to Xero
  • Who holds the API ID and API Key (account owner)
  • What “done” looks like: a working sync, a repaired script, or a clear picture first

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

Related work

We have not published an Unleashed ecommerce case. Windsor is nopCommerce plus Peach, with Peach syncing to Xero — related as “inventory next to a store and Xero”, not Unleashed. NESS is nopCommerce and Dynamics NAV 2018.

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 an Unleashed case study. An Unleashed account still starts with its own assessment.

FAQ

Can the store read live stock?
Yes, via StockOnHand, warehouse-aware. Do not flatten multiple warehouses into one number unless the business has chosen that lie on purpose.
Why did the last sync blank product fields?
Unleashed does not do partial updates. Omitted fields can be cleared. Full payloads, or do not write the product.
Is Unleashed our ERP?
It is inventory, orders, and production software with ERP-overlapping features. The books are often still Xero. We will not sell it as a full ERP replacement.
Do you have an Unleashed store case?
No. We will not invent one or an AU customer count.
Unleashed already talks to Xero. Should the store as well?
Usually not for invoices. Decide one poster. The store can still push SalesOrders into Unleashed and leave financials on the Unleashed↔Xero link.

Talk through the Unleashed connection you already need

Thirty minutes. Bring a store URL and which warehouses the site sells. We will tell you whether to connect, stop the blanking, or leave Xero to the link you already have.

Book a free 30-minute discovery call