Cin7 reviews: what inventory businesses say after go-live, and what the reviews miss
Cin7 reviews on the Shopify App Store, Trustpilot, G2, and Capterra read like two different products. The gap between them usually opens after go-live, and it is mostly a configuration and governance story.

On this page
- What do Cin7 reviews say overall?
- Why do Cin7 reviews change after go-live?
- Is the problem Cin7 or the setup?
- What does Cin7 cost, and does the price show up in reviews?
- How do you read Cin7 reviews before you buy or renew?
- What should you do this week if your Cin7 setup is live but not working?
- When should you patch, rebuild, or bring in a specialist?
- Frequently asked questions
TL;DR
- Cin7 reviews skew positive, and the complaints cluster around support response, sync errors, and numbers that stop matching the accounting ledger after go-live. The Core listing on [Shopify's App Store](https://apps.shopify.com/dear-inventory/reviews) sits at 4.4 across 65 reviews.
- Praise tends to come from reviewers in the first weeks after onboarding, and the harder complaints come months later, once real order volume and exceptions hit the setup.
- Most post-go-live complaints trace to four setup patterns: lock date misalignment, an overpayment auto-apply loop, landed cost miscoding, and manual plug journals.
- A review tells you how one business's configuration performed, so test your own order flow (purchase, landed cost, sale, return) before trusting any star rating.
- Cin7 Core is listed at $349, $599, and $1,199 a month, so the bigger cost variable for a $1m to $100m inventory business is configuration and governance, not the plan price.
You read the reviews before you signed, picked the 4.4, and went live. Three months later the stock count is off, Shopify and Cin7 disagree, and the month-end close takes longer than it did on spreadsheets. Now you are back on the review sites, wondering whether the one-star reviews were describing you.
This post reads the Cin7 reviews the way an operator should: what the praise describes, what the complaints have in common, and where the gap between them comes from. It ends with a checklist you can run this week, whichever camp you are in.
What do Cin7 reviews say overall?
Cin7 reviews are mostly favourable, with a loud minority of detailed complaints. The Cin7 Core listing on the Shopify App Store sits at 4.4, with 38 of 65 reviews at five stars and 13 at one star.
That shape matters more than the average. A 58% five-star share and a 20% one-star share, with very little in between, looks like a platform that either fits the way a business operates or does not. Mid-range reviews are rare because a half-working inventory system tends to push people to one end or the other.
What the positive reviews have in common
The favourable reviews on the Shopify listing talk about onboarding and the people who handled it. Reviewers describe a solutions architect reviewing their manufacturing process, introducing assembly BOMs with landed costs, and working through a Shopify and 3PL fulfilment approach using locations. Others describe a faster go-live because someone handled setup, integrations, and troubleshooting.
Those reviews describe a well-run implementation. The praise attaches to configuration decisions made by people who understood the business, and Cin7 offers group, 1:1, and partner-led onboarding for exactly that reason.
What the negative reviews have in common
The critical reviews cluster around slow support, integrations that did not behave as expected, and implementations that ran shorter than the work required. One reviewer on Capterra describes being told to expect a 30-day implementation and finding that 90 days was closer to the norm. Others report Shopify sync problems with prices, costs, barcodes, and SKUs.
These are real experiences and deserve a fair reading. They also share a feature: most describe the period after go-live, when the system meets live volume, exceptions, and an accounting ledger that has to agree with it.
Why do Cin7 reviews change after go-live?
Cin7 reviews change after go-live because setup is tested under controlled conditions and live operations are not controlled. Once real users, order volume, returns, partial receipts, and finance timing arrive, the gaps in the configured setup become visible. The system was tested as a setup and has not yet been proven as an operating model.
That is why the same platform can earn a five-star review in week two and a one-star review in month five, sometimes from the same business. Order volume, returns, and exceptions grew past the original configuration, and nobody reset it.
A car that passed inspection on delivery day still needs its oil checked at 5,000 miles. Cin7 needs the same maintenance rhythm, and most reviews never mention who owned it.
Is the problem Cin7 or the setup?
In most of the post-go-live complaints Fiskal sees, the problem sits in the setup, and Cin7 is executing exactly what it was configured to do. Four patterns explain most recurring discrepancies, and genuine platform and marketplace limitations exist as a separate category that needs its own diagnosis.
The table below maps the symptoms that show up in negative reviews to the layer where Fiskal looks first. It is a starting point for a diagnostic, not a verdict on any one business.
| What the review says | Where the root cause often sits | First fix |
|---|---|---|
| Reconciliation differences that move from month to month | Lock date misalignment, or a prior reconciled transaction changed after the fact | Align lock dates across Cin7 and the accounting system, and stop retroactive edits |
| Margins look wrong | Landed cost coded to expenses instead of attached to the purchase order | Route freight, duties, and broker invoices through the purchasing workflow |
| Sync errors keep returning | Naming rules, tax mapping, or nobody owning the sync queue | Assign an owner and review the sync history weekly |
| Inventory value does not match the ledger | Account mapping, GRNI and GINR balances, shipment timing | Trace the gap to the ledger or the subledger before booking anything |
| Books are close enough because of manual journals | An operational workflow producing the difference upstream | Remove the plug journal and fix the workflow behind it |
The last row deserves attention. A manual journal that closes a gap hides the visible problem while the drift underneath continues, which is how a business ends up writing a one-star review nine months later.
A diagnostic pattern worth knowing
One of the most common sources of a month-to-month reconciliation difference is a Beginning Balance that has shifted because someone changed or deleted a prior reconciled transaction. The cause is a missing retroactive change policy, and the reconciliation is simply where it surfaces. Reconciling Cin7 Core and QuickBooks Online in the right order, with lock dates set once, removes most of that.
What does Cin7 cost, and does the price show up in reviews?
Cin7 Core is listed at $349 a month on Standard, $599 on Pro, and $1,199 on Advanced, in USD, excluding taxes, for new customers. Omni is quoted individually. Reviews that mention cost often describe the add-ons and services around the plan rather than the plan itself.
For a $1m to $100m inventory business, the plan price is the smaller number. The configuration, the accounting mapping, and the governance that keeps both intact after go-live decide whether the subscription earns its place. When the invoice looks higher than the plan you chose, the answer usually sits in what falls outside each tier, and Fiskal's breakdown of Cin7 pricing maps what sits inside and outside each plan.
How do you read Cin7 reviews before you buy or renew?
The star rating tells you less than the configuration a review implies. A five-star review that mentions a solutions architect, BOMs, and landed costs tells you someone designed the setup. A one-star review about a 30-day implementation tells you the scope was underestimated. Both describe how the implementation was run.
Run each review you read through four questions. What did the business sell, and through how many channels? Who configured the system? How long ago did they go live? Did they mention their accounting system? Reviews that answer none of these are weak evidence either way.
What should you do this week if your Cin7 setup is live but not working?
Start with a short diagnostic before deciding whether to patch, rebuild, or migrate. The steps below take an operator and their bookkeeper a few hours, and they separate a setup problem from a platform limitation. Fiskal runs the same sequence at the start of every stabilisation engagement, because it surfaces the real cause faster than any other starting point.
- Map one real order flow. Pick a single purchase, trace its landed cost, sell one unit, process one return, and check where each step lands in QuickBooks Online (QBO) or Xero. Every layer that fails here fails at volume too.
- Check your lock dates. Confirm the lock date in Cin7 and the lock date in your accounting system agree, because misalignment is one of the four most common causes of recurring variances.
- Audit landed cost entry. List every freight, duty, and broker invoice from the last quarter and confirm each one attached to a purchase order rather than posting to a general expense account. Landed cost miscoding is the quietest margin leak in the stack.
- Review the sync history. Read the last 30 days of sync errors, group them by cause, and name one person who owns clearing them. A sync queue with no owner always fills up.
- List your manual journals. For each plug journal booked to close a gap, write down the operational event that produced the gap. The journal is the symptom, and the event is the fix.
- Write a retroactive change policy. Decide who may edit a reconciled transaction, under what conditions, and how the change gets logged.
- Set a recurring review. Put a monthly 90-minute reconciliation and a quarterly configuration review in the calendar, owned by a named person.
The last two steps are the governance that stops the problem coming back. Systems drift after go-live when nobody owns the discipline, and a named owner with a review cadence keeps a system stable.
When should you patch, rebuild, or bring in a specialist?
Patch when one pattern explains the symptoms, rebuild when several layers disagree, and bring in a specialist when the team has already tried to fix it twice. A controlled rebuild of the Cin7 environment keeps your platform in place and is often the shorter route.
| Situation | Option | Signal |
|---|---|---|
| One mapping or lock date wrong, everything else reconciles | Patch | The variance has a single traceable cause |
| Stock, COGS, and sync all drift at once | Reconfigure | Three or more symptom rows apply to your business |
| Open orders, junk data, and unowned syncs everywhere | Rebuild | Cleanup would cost more than a fresh, documented setup |
The Fiskal Score measures a setup across People, Systems, and Finance, so it points at the exact part that needs work before you commit to any of the three. When a system is live but the numbers cannot be trusted, Cin7 Core stabilisation starts with a diagnosis, and Cin7 onboarding support covers the training and system ownership that keep it stable.
What a good outcome looks like
Play Pits, a consumer packaged goods brand running Shopify, Cin7 Core, and Xero, was spending three to four weeks a month closing its books. After Fiskal rebuilt the foundation, month-end close takes days. Three to four weeks became a handful of days, on the same software, with the configuration, the data flow, and the reporting rhythm changed. The founder's summary: "This is the first time in my business that I look at the numbers and I know that the numbers are real."
Frequently asked questions
Is Cin7 any good according to reviews?
Cin7 reviews are mostly positive, with the Core listing on the Shopify App Store at 4.4 across 65 reviews. The complaints that carry weight describe support response, sync errors, and numbers that diverge from the accounting ledger after go-live, and many of those trace back to how the system was configured.
What are the most common complaints about Cin7?
Reviewers raise slow support, Shopify sync problems with prices, costs, barcodes, and SKUs, and implementations that took longer than promised. Recurring setup patterns sit underneath those, including lock date misalignment, landed cost miscoding, and manual plug journals.
How much does Cin7 cost per month?
Cin7 Core is listed at $349 a month for Standard, $599 for Pro, and $1,199 for Advanced, in USD, excluding taxes, for new customers. Omni has no list price. Add-ons and onboarding are priced separately, so ask for a written quote.
Should I switch from Cin7 because of bad reviews?
Run a setup diagnostic first. If the same issues would follow you into another system, such as unmapped landed cost or an unowned sync queue, a migration repeats the problem at a higher cost. A switch makes sense when the diagnostic shows a genuine platform limitation.
Why does Cin7 work well for some businesses and badly for others?
Cin7 runs whatever workflow and accounting structure the business gives it. A clean order-to-cash flow and an aligned chart of accounts tend to produce accurate reporting, and informal workarounds tend to get amplified. Fit depends on configuration, ownership, and governance after go-live.


