Looking to replace QBO. These are the features I need. Recs?
I have a small online business (2 Etsy shops & 1 Shopify site). I'm a sole proprietorship. I don't need payroll or invoicing. I do use QBO to snap receipts and track mileage, but everything else is imported automatically (zillions of tiny daily transactions…
I have a small online business (2 Etsy shops & 1 Shopify site). I'm a sole proprietorship. I don't need payroll or invoicing. I do use QBO to snap receipts and track mileage, but everything else is imported automatically (zillions of tiny daily transactions on Etsy, mostly). It imports my bank account and I categorize purchases as personal or business. That's literally all I do with it. I don't need anything else. At tax time I turn it over to my CPA. But I hate it. For 5 months this year it refused to connect with my Etsy shops, which it has done just fine for the past many years. Every time I log in, I wonder what months of transactions I'll be missing this time. Customer service told me my subscription doesn't allow for Etsy connection and I'd need a different plan?! The next time I logged in, it connected to Etsy (mysteriously) and all of those 5 months of missing transactions were there. I'm so sick of it. What can I replace it with?
已收录讨论
Moderator Announcement Read More » Friendly Reminder r/smallbusiness is a question and answer subreddit. Ask a question about starting, owning, and growing a small business and the community answers. Posts that violate the rules listed in the sidebar will be removed. Please do not conduct market research on our community. We are not your focus group and asking us about our pain points, needs, what is hardest about X, etc. is not asking about how small business works or for real help with running your small business. These posts are subject to removal and given the community's disgust with the constant spamming of these posts you might just destroy your brand and contaminate your company search results. Seeing this message does not mean your post was automatically removed. If you asked about pain points or are directly or indirectly promoting a product please remove your post. Come back to post an honest question or give a knowledgeable response to someone else's question and leave your company name in your own profile. We can tell if you know what you're doing and the community can reach out if they need to. We welcome honest question posts, especially from newcomers. Thank you for your post. I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
second that. last-successful-sync is such a small field, but it changes the failure model because absence becomes visible. ideally it should also be compared against an expected interval. a timestamp alone still depends on somebody remembering to look at it. “last sync was Tuesday” is useful, but “this connection normally syncs hourly and is now six hours late” is what turns it into something actionable.
Yeah, that's the real version of it. A raw timestamp is a value you have to remember to go check; an expected-interval comparison turns it into a condition somebody (or something) can alert on. It's basically a dead man's switch - "this should have pinged by now and didn't" is a much stronger signal than "here's when it last pinged." The gap between those two is where most silent integration failures live for months before anyone notices.
The specific failure mode you're describing - a sync that goes quietly dark for months and then reappears "mysteriously" - is almost always an expired auth token, not a real connection problem. Etsy's API access uses OAuth tokens that expire and need periodic refresh; if the refresh silently fails (which happens more than it should), the integration doesn't error out, it just stops pulling new data and nobody's watching. It "fixing itself" is usually just the token finally getting refreshed, either by you logging in and re-triggering it or the vendor doing a bulk fix on their end. Whatever you replace QBO with, the actual thing to check isn't "does it connect to Etsy," almost everything claims that - it's whether it shows you a visible last-successful-sync timestamp per connection, so a silent failure is something you'd notice in days instead of months. That one small feature is the difference between "missing 5 months of transactions and finding out at tax time" and "noticed it stalled last Tuesday."
Checkout ambrook
I hate QBO too, but I (reluctantly) use it because it's pretty much industry standard and I can find CPAs/bookkeepers that know QBO versus some niche financial management platform.
I'd check before you fully cut over by pulling your own Etsy transaction history as a CSV directly from Etsy's shop stats, and reconcile that against whatever QBO or the new tool shows for the same date range, rather than trusting either side's import. Given QBO already went quiet on you for 5 months with zero error, there's no guarantee that's the only gap it's ever had, just the one you happened to notice. A one-time manual reconciliation against Etsy's own export closes that out properly before it goes to your CPA. Once you're on something new, the sync method matters less than what happens when it breaks. Ask before switching: does it show a visible last-successful-sync date, and does it actually alert you if a connection drops rather than just going quiet? That's the real feature you're missing here.