System auditfig. 00 · the inspection

Find out what your Cin7 Core is actually doing.

A System Audit is a full inspection of your setup, run by the people who configure these systems for a living. We pull the data, work out what is misconfigured and what it is costing you, then hand you a written report with recommendations you can act on. Whether we do the fixing is entirely your call.

Book a call What we inspect
at a glance
Flat rate, billed in advance
Eight areas of your setup inspected
Written findings, plus a review session
No obligation to have us do the fixing
The symptomsfig. 01 · signals

If any of this sounds familiar, the setup is telling you something.

These are the sentences we hear most often on a first call. Individually they look like small annoyances. Together they usually point at a handful of settings that were never quite right.

“Our customers are not mapping correctly.”heard on a first call
“We are being prompted to reorder goods we already have in stock.”heard on a first call
“Our COGS is frequently inaccurate.”heard on a first call
“Some purchase orders simply cannot be received.”heard on a first call

None of these are Cin7 Core being broken. In our experience they are almost always the result of a decision made early in a setup, then quietly built on top of for a year or two. An audit finds the decision, not just the symptom.

What we inspectfig. 02 · scope

Eight areas, pulled from your own data.

We take exports and reports from across your tenant rather than working from a conversation about how it is meant to run. What the data says is what goes in the report.

  1. 01CustomersDuplicate records, mapping into the accounting system, price tiers, credit terms and tax rules that no longer match how you actually sell.
  2. 02SuppliersLead times, default currencies, supplier product codes, and the settings that quietly drive your reorder recommendations.
  3. 03Products and inventoryCosting method, stock on hand accuracy, units of measure, bills of materials, and batch or serial tracking where you use it.
  4. 04Global settingsThe tenant-wide choices that are painful to change later, including costing, accounting periods, and permission structures.
  5. 05Reference booksLocations, carriers, payment terms, tax rules and account mappings, which is where a surprising number of month-end problems originate.
  6. 06Sales processHow orders come in from each channel, where they stall, what gets edited by hand, and whether the workflow matches your team’s reality.
  7. 07Purchase processReordering logic, landed costs, receipting, and the orders that cannot be closed off because something upstream is wrong.
  8. 08IntegrationsXero or QBO, A2X, Shopify, WooCommerce, 3PL and EDI connections: what is syncing, what is failing silently, and what is being patched by hand.
How it runsfig. 03 · the method

Inspect, document, then decide together.

Three stages, and you are not committed to the third one. Plenty of clients take the report and work through it with their own team.

stage 01

Inspect and analyse

We pull the exports and reports we need and go through them properly. Alongside that, we work from your notes on what is going wrong, so we review the system in the context of the problems you are actually feeling rather than in the abstract.

stage 02

Document the findings

You get a written report: what we found, what we think is causing it, and what we would recommend doing about it, prioritised. We then walk you through it in a review session so you can ask the awkward questions live.

stage 03

Fix it, or we do

We will agree whether the fixes are a “you” job or an “us” job, item by item. If you would rather we just got on with it, that work runs under an hourly agreement, quoted as an initial block of hours to get started.

What you getfig. 04 · the report

A document you can hand to your team on Monday.

The report is written to be read by the people running the business, not just by a systems person. Each finding says what is wrong, what it is likely costing you in time or accuracy, and what we would do about it. Recommendations are ordered so you can stop after the first three if that is all you have capacity for.

Where a finding touches on tax treatment or statutory reporting, we will flag it and point you to your accountant rather than advising on it ourselves.

Included in every audit

  • A preparation checklist so access is sorted before we start
  • A shared worksheet carrying your issues and our early notes
  • A written report of findings and prioritised recommendations
  • A review session to talk the findings through
  • A clear split of what is a “you” job and what is an “us” job
Why us for thisfig. 05 · the log

There is very little in a Cin7 Core tenant we have not seen go wrong.

An audit is only worth having if the person running it recognises the problem quickly. Ten years on this one platform is what makes that possible.

100+
Full Cin7 Core implementations delivered
#1
Most experienced Cin7 Core partner in the world
Xero
Preferred Cloud Integrator, the highest tier
10+
Years working with inventory businesses
The practical bitsfig. 06 · terms

How it works once you say yes.

What happens once we give you the go-ahead?

On acceptance of our engagement letter, we will:

  1. Bill for the audit through the payment source you nominate in our proposal platform.
  2. Send you a preparation checklist so we have the access and the data we need.
  3. Share our audit worksheet, with our preliminary notes, for you to add the issues you are seeing.
  4. Schedule your review session to talk through the findings and recommendations.
  5. Get to work on the fixes, if that is what you decide you want.
How will you bill us?

The audit is a flat-rate service, billed in advance. Any work you ask us to do afterwards runs under an hourly rate agreement, with an initial block of hours quoted to get things moving.

Hourly work is billed at the start of each month for the work done the month before. We send a proforma invoice summarising what we did, then bill your nominated payment source 14 days later.

Do we have to use you for the fixes?

No. The report is yours, written so your own team can work through it. Some clients hand it straight to an internal systems person and get on with it. Others would rather we just did it, which is fine too.

Once you are a client, you can come back at any point in the future and have us jump into the system with you when something new comes up.

How long does it take?

Most audits run over a couple of weeks from the point we have access, though it depends on how quickly the preparation checklist comes back and how large the tenant is. We will give you a realistic window before you commit, and we would rather set expectations wide than miss them.

Will this disrupt the team?

Very little. We work from exports and read-only review rather than changing anything, so day-to-day operations carry on as normal. The main call on your time is the preparation checklist at the start and the review session at the end.

Set a coursefig. 07 · next

Stop guessing at what is wrong.

Book a call and tell us what is going sideways. If an audit is the right answer we will say so, and if your problem is narrow enough to fix in an hour, we will tell you that instead.

Book a call Email us

please check your timezone and am/pm when booking

What to expect

  • A straight conversation, no scripted sales pitch
  • An honest view on whether an audit is worth it for you
  • A flat rate for the audit, quoted before you commit
  • No pressure to have us do the remediation work