CoreSync Review Independent controls review

Founding pilot · Australia · Cin7 Core + Shopify

A second set of eyes on your Cin7 Core–Shopify controls.

A fixed-scope monthly review of merchant-provided exports, designed to surface repeated discrepancies and process gaps — without taking over your live operations.

A$99

One month. One review.

Founding pilot price for a single point-in-time review of exports you generate and redact yourself. No credentials, no system access, no subscription implied.

Read this before you enquire: this is a retrospective review, not live monitoring. There are no alerts, no remediation, no changes to your stock or orders, no incident response and no response SLA. You remain responsible for your daily Cin7 Core and Shopify checks and for every operational decision.

Ask about the A$99 pilot See exactly what is excluded

Opens an email to marc@sitesimple.au. Enquiring costs nothing and commits nothing — nothing is accepted, scheduled or paid for on this page.

Cin7 Core and Shopify already give you the raw material: pending orders, order logs, integration operation logs, inventory and order CSVs. Those tools work.

What they don't do is sit down once a month, read across both systems at once, and tell you which discrepancies keep coming back. That reading is the whole service.

01 / What gets reviewed

Six checks, run across both systems at the same cut-off.

Each check compares merchant-supplied Cin7 Core exports against merchant-supplied Shopify exports for one agreed period. Every finding is written against the evidence rows you provided, so you can trace it back yourself.

  1. CHK·01

    SKU and location mapping integrity

    Unmapped, duplicate or blank SKUs, and gaps between your Core locations and Shopify locations — the mapping faults that quietly change which stock is sellable.

    Core stock exportShopify inventory CSV
  2. CHK·02

    Shopify available vs expected Core sync quantity

    Compared after your documented location, buffer, unit-of-measure and BOM/kit rules are applied — not against raw Core on-hand. A raw difference is not automatically an exception, and this review will not treat it as one.

    Baseline rules sheetBoth stock exports
  3. CHK·03

    Order record parity

    Shopify order IDs and counts against Core sales and log records for the period, including orders still sitting pending or unloaded beyond the tolerance you set.

    Shopify order CSVCore sale order details
  4. CHK·04

    Cancellation, refund, restock and fulfilment status

    Where the two systems disagree about what happened to an order after it was placed. These directions are not symmetrical between Core and Shopify, so mismatches accumulate quietly.

    Order status fieldsCore log view
  5. CHK·05

    Recurring log patterns

    Repeated operation-log errors, stale connection or update failures, and direct Shopify inventory adjustments that bypassed Core — read as a pattern across the period rather than as one-off entries.

    Operation log viewAdjustment history
  6. CHK·06

    Repetition and ageing

    Which exception types repeat, how old they are, and which SKUs and orders they touch. Reported as units exposed — never as a dollar loss, because this review does not hold your cost data or reconcile your accounts.

    All of the above

02 / What you receive

Two files. Nothing to log into.

Findings arrive by email as a one-page summary you can read in a few minutes and a register you can sort, filter and hand to whoever owns the fix.

Deliverable 01 — PDF

One-page traffic-light summary

Every exception grouped into one of three bands, with the evidence reference, how long it has been open and who inside your business owns it.

Review now

Open exposure you should look at against live data today. Yours to action — this review does not act on it.

Next business day

Worth checking soon, but unlikely to be doing damage in the next few hours.

Process improvement

A control or habit worth changing, so the same exception stops reappearing next period.

Deliverable 02 — CSV

Exception register

One row per exception, with the columns below. Plain CSV, so it opens in Sheets or Excel and can be filtered by whoever does the work.

columncontains
refStable reference for the exception
checkWhich of the six checks raised it
sku / order_idThe record involved, as supplied by you
locationMapped location, where relevant
observedWhat your Shopify export shows
expectedWhat your Core export and rules imply
age_daysHow long the discrepancy has persisted
bandReview now / next business day / process improvement
evidenceThe row or log entry it came from
ownerSuggested operational owner inside your team

Both files describe what your own exports show at one point in time. They are an opinion formed from evidence you supplied — not a warranty that your inventory is accurate, and not a substitute for your daily checks.

03 / How the pilot works

Four steps, all asynchronous, all by email.

The pilot is deliberately small. It is designed to find out whether an independent monthly read is worth A$99 to you — and if it is not, you should say so.

  1. 01

    Fit check

    A short email exchange. We confirm you are on Cin7 Core with the native Shopify connector already live (not Cin7 Omni), agree the review period, and put the scope and its exclusions in writing before anything is paid.

    Email only · no call required · no obligation

  2. 02

    Baseline and redacted exports

    You send a one-off context sheet — location mapping, buffer rules, consolidation mode, order-capture trigger, BOM/kit treatment and which system is source of truth — plus the period's exports from both systems. You generate and redact them; customer names and addresses are not needed and should be removed.

    No credentials · no API keys · no access to your systems

  3. 03

    The review

    The six checks are run against your files for the agreed period. Anything that turns out to be explained by your documented rules is discarded rather than reported — a long list of false exceptions would waste your time, not prove value.

    Point-in-time · retrospective · performed once

  4. 04

    You receive the findings

    The one-page summary and CSV register arrive by email, with a short note on which checks found nothing. If the review found nothing worth your attention, that is what it will say — and that is a legitimate outcome of the pilot.

    Delivered by email · yours to keep · no lock-in

Merchant effort is expected to be roughly an hour for the one-off baseline and 15–30 minutes for the export cycle. That is an estimate this pilot exists to test, not a measured figure from prior customers.

04 / Scope

What this is, and what this is not.

The second column matters more than the first. If any line on the right is what you actually need, this pilot is the wrong purchase and it is better to find that out now.

What this is

  • A retrospective, point-in-time review of exports you generate.
  • An independent cross-system read of Core and Shopify at one cut-off.
  • A written opinion, traceable to the evidence rows you supplied.
  • A fixed scope of six checks, agreed in writing before you pay.
  • A one-page summary and a CSV register, delivered by email.
  • A one-month pilot at A$99, with no subscription and no lock-in.
  • Work done without credentials or any access to your systems.

What this is not

  • Not live monitoring. Nothing is watched between reviews.
  • No alerts. You will not be notified when something breaks.
  • No remediation. No retries, re-mapping, re-authentication or configuration changes.
  • No changes to stock or orders. No adjustments, order edits, fulfilments, cancellations or refunds.
  • No incident response and no response SLA. Urgent issues are not owned here.
  • No warranty of inventory accuracy, no accounting or COGS reconciliation, and no loss estimate.
  • No vendor liaison or support ownership. Tickets with Cin7 or Shopify stay yours.

If something is going wrong right now — a stalled paid order, a failed stock update, a disconnected integration, an oversell — that needs your normal Cin7 Core and Shopify checks or a specialist who can act on your systems, today. A monthly retrospective review cannot be relied upon to catch it in time, and this page does not suggest otherwise.

05 / Fit

Who this pilot is built for.

A narrow fit is deliberate. The workflow is standardised, so businesses outside this profile will get less out of it than they pay for.

Likely a fit

  • Australian small wholesaler or ecommerce brand.
  • Running Cin7 Core with the native Shopify connector, already live.
  • One or two warehouses, roughly 100–5,000 active SKUs.
  • No dedicated integration engineer or operations analyst on staff.
  • Setup is basically correct — you want a check, not a rebuild.
  • Someone (owner, ops manager, inventory manager) can pull exports.
  • You want independent evidence, not someone to take over incidents.

Not a fit

  • You use Cin7 Omni — a different product with a different integration and error UI.
  • You want real-time alerts or same-day exception detection.
  • You want someone with API keys or admin access to your systems.
  • You want stock corrections, order rescue or vendor escalation.
  • You need a guaranteed response time.
  • You need accounting reconciliation, valuation or a loss figure.
  • Your integration is mid-implementation or substantially broken — that is remediation work, not a review.
  • Heavy batch, expiry or manufacturing rules sit at the centre of your stock logic. Those are out of scope for a first standardised pilot.

06 / Questions

Fair questions, answered plainly.

How much work is this for me?

The one-off baseline — location mapping, buffer rules, consolidation mode, order-capture trigger, BOM/kit treatment, source of truth — is expected to take about an hour. Each export cycle is expected to take 15–30 minutes: a Core stock-level and sale-order export, a Shopify inventory CSV across all relevant locations and states, a Shopify order CSV for the period, plus a saved view or screenshot of your pending orders and operation logs.

Those figures are estimates, not measurements. Testing whether they hold in a real business is one of the reasons the pilot exists. Note that Shopify emails larger, date-ranged order exports rather than downloading them immediately, which adds a little friction.

Do you need my Cin7 or Shopify login?

No. The pilot deliberately runs on merchant-generated exports only — no passwords, no API keys, no staff account, no app install, no access of any kind to your systems.

That is a design choice, not a limitation to work around later. Cin7 Core's own documentation describes its Account ID and API Application Key as equivalent to a login and password, and the endpoint set includes write operations. Keeping this pilot to files you export yourself avoids that entire category of risk.

Customer names and addresses are not needed. Order ID, SKU, location, status and quantity are enough — please redact the rest before sending.

Is this monitoring? Will I get alerts?

No, on both counts. Nothing is watched between reviews and no alerting exists. The pilot is one review of one period, produced after the fact and delivered by email.

If you need something watching your integration continuously, you need either your own daily routine on the native logs, or middleware and a managed specialist. This is neither, and it should not be bought as a cheaper version of either.

What if the review finds something urgent?

Anything that looks like live exposure is flagged as Review now at the top of the summary, and if it is serious it will be called out in the covering email rather than left in a CSV row.

But be clear about what that promise is and is not. It is a courtesy in one direction only. There is no undertaking that an urgent problem will be found, no undertaking that it will be found in time, and no action taken on your systems either way. Acting on it is yours, and the fastest route is still your normal Cin7 and Shopify checks or a specialist who can access your systems.

Are you affiliated with Cin7 or Shopify?

No. This is an independent validation service with no affiliation, endorsement, sponsorship, partnership or certification from Cin7 or from Shopify. Both names are used here only to describe the systems being reviewed, and both are trademarks of their respective owners.

Nothing here is a criticism of either product. Both provide the logs and exports this review reads; the service is an independent interpretation of them, not a replacement for them.

What happens after the pilot month?

Nothing automatic. There is no subscription, no auto-renewal and no stored payment. The pilot is one month and one review, and it ends there unless you decide otherwise.

If the review was useful you can ask about a further month; if it was not, saying so is genuinely valuable — this is a validation pilot and a clear "no, this isn't worth A$99" is a real result. Any ongoing arrangement would be agreed separately, in writing, and nothing on this page commits either side to one.

Why should I trust a review with no customers behind it?

You shouldn't take it on reputation, because there isn't one to point at yet. This is a new, deliberately narrow service being tested with founding pilots, and this page makes no claim of existing customers, results, savings or testimonials.

What you can judge is the method: a fixed set of six checks, run against evidence you supply, with every finding traceable back to a row in your own exports. If a finding doesn't hold up against your data, it isn't a finding.

07 / Enquire

Worth a second set of eyes?

One email tells us both whether this is a fit. It opens pre-filled with four short questions — your business name, your website, confirmation that you run Cin7 Core with Shopify, and the reconciliation concern that made you read this far.

Ask about the A$99 pilot
Email
marc@sitesimple.au
Subject line
Cin7 Core–Shopify controls pilot
Pilot price
A$99 · one month · one review

Enquiring is not an application and not a booking. Nothing is accepted, scheduled or charged on this page — scope and price would be confirmed by email first, and you can stop at any point.