Cin7 ecommerce integration — after we know Core from Omni

The store already takes orders. Cin7 already holds stock. Core and Omni are not one product and not one API. We will tell you which tenant you have, who is allowed to post the sale, and whether Xero is already in that path.

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

Australian ecommerce team. We look at the store and which Cin7 product you actually run before anyone talks about a connector.

Still running a store that needs Cin7?

The store still takes orders. Cin7 still holds availability. That is why the two have been left talking through a CSV, or through a connector written for the other Cin7.

Cin7 is inventory and order-management software, founded in New Zealand in 2012. After the 9 January 2023 rebrand there are two products: Cin7 Omni (the former Cin7) and Cin7 Core (the former DEAR Systems). DEAR is not the current product name. Cin7’s about page claims “over 8,500 customers” globally and “125+ million orders per year”. Those are vendor global figures, not Australian customer counts, and we will not restyle them as one.

You might recognise one of these:

  • You say “we’re on Cin7” and cannot say Core or Omni
  • Stock on the site is wrong because the last job hit the other product’s API
  • Cin7 already posts to Xero, and a store invoice connector would double the books
  • Products and prices live in Cin7; the store is supposed to follow, and it does not
  • Sales orders land in Cin7 twice — once from the plugin, once from a person
  • Someone still has DEAR credentials in a password manager and thinks that is “the Cin7 API”

You do not need a new storefront, or an accounting pitch. You need a clear read on which Cin7 you already have.

Why these connections stall

Both products have REST APIs. The stall is treating them as one door, and then posting financials a second time.

Core ≠ Omni

Two APIs

Orders not GL

Xero already

Cin7 Core and Cin7 Omni do not share an API.

Cin7 Core (DEAR) is REST. The app lives at https://inventory.dearsystems.com. Auth headers are api-auth-accountid and api-auth-applicationkey. The vendor recommends API V2 (https://dearinventory.docs.apiary.io). SaleList is an example resource. Cin7 Omni is a separate REST API, JSON, base https://api.cin7.com/api. The vendor documents products, pricing, stock, orders, payments, contacts — for example GET api/v1/Stock. A Core key will not open Omni. An Omni client will not speak Core’s headers. One page can cover both products only if the first question is which one you run.

The job is inventory and orders, not the general ledger.

Typical store work: products, availability, sales orders, customers, purchase or stock adjustments. Cin7 is where stock truth usually sits when it is in the picture. The store should read availability and write the sale. It should not invent a second stock figure and hope the warehouse agrees.

Accounting may already be Cin7 → Xero.

Cin7 ships its own accounting connectors to Xero and QuickBooks. That is a vendor product feature, not a CoSource case. If that link is live, the store must not also post the invoice into Xero. Two posters, one sale, a BAS problem. Design who creates the financial document before anyone writes a second connector.

Auth and product names still leak the old world.

Core still talks to a dearsystems host and DEAR API docs. Omni talks to api.cin7.com. People mix the two in a single “Cin7 integration” ticket. The rebrand did not merge the stacks. If the brief says DEAR, you are on a Core conversation — and you should still call the product Cin7 Core in the contract.

None of that makes the catalogue or the Cin7 tenant worthless. It does mean “use the Cin7 API on Monday” is not a specification.

How we work

We start with which Cin7, then the store, then who already posts to Xero.

1

Look at what you have

Store platform, Core or Omni (URL, keys, and what the UI is branded), which warehouses the store may sell, and whether Cin7 already syncs accounting. We will tell you which API the job is, and who must not create an invoice.

2

Decide the job

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

3

Do the work in stages

Products and stock reads first, then sales orders and customers. Do not add a Xero post unless nobody else owns it. A sandbox or spare branch beats a Friday stock write.

4

Hand it back so the next person can run it

Source, which product and which API version, and a short record of what creates a sale.

Three honest outcomes

  • Connect the store to the Cin7 you actually run: Core via API V2 and account/application keys, or Omni via api.cin7.com — products, stock, orders, contacts. Custom API work. No published CoSource Cin7 case or connector.
  • Fix a broken connector when a plugin still almost works: point it at the correct product API, stop the double sale, or stop the store from also posting to Xero.
  • Decide not to connect when Cin7’s own store or accounting connectors already own the job, when you are mid-move from DEAR-branded Core and the tenant is not stable, or when stock should stay in Cin7 and the site should not sell live qty yet.

We will not pretend Core and Omni are one API. We will not say DEAR is still the product name. If Cin7’s own channel connectors already do this storefront, 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 a Cin7 login screen is enough to start.

  • Which store: nopCommerce, AbleCommerce, Shopify, or another CMS
  • Core or Omni — or a screenshot of the URL bar if you are not sure
  • What should sync: products, stock, sales orders, customers
  • Whether Cin7 already posts to Xero or QuickBooks
  • How many warehouses the storefront is allowed to sell
  • What “done” looks like: a working sync, a repaired connector, or a clear picture first

The first call is 30 minutes. You leave with a recommendation you can take to a manager, not a “Cin7” estimate that named the wrong product.

Related work

We have not published a Cin7 Core or Cin7 Omni ecommerce case. Windsor is nopCommerce plus Peach, with Peach syncing to Xero — related as “inventory system next to a store and Xero”, not a Cin7 case. NESS is nopCommerce and Dynamics NAV 2018. Neither is Cin7.

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 Cin7 case study. A Core or Omni tenant still starts with its own assessment.

FAQ

Is this one Cin7 API?
No. Core (former DEAR) and Omni (former Cin7) are different products and different REST APIs after the January 2023 rebrand. Say which one you have in the first five minutes.
Does Cin7 replace Xero?
No. Cin7 is inventory and orders. Many tenants already use Cin7’s own Xero connector for the books. The store should not double-post invoices without a design.
Is DEAR still the product?
No. DEAR Systems was renamed Cin7 Core. Credentials and docs may still say DEAR. The current product name is Cin7 Core.
Do you have a Cin7 store case?
No. We will not invent one, and we will not turn “8,500 customers” into an Australian figure.
Can one project cover both if we might move?
Only as two scoped integrations. Do not budget a single connector that “just switches host”.

Talk through the Cin7 connection you already need

Thirty minutes. Bring a store URL and whether you are on Core or Omni. We will tell you which API the job is, whether to connect, or whether Xero is already spoken for.

Book a free 30-minute discovery call