QBISoftware Discuss your project
Open menu

Case studies

Real systems, fixed by engineers who know the books

Our work starts where data breaks: between a store and a ledger, or inside an old app. Each project here shows the starting point, the build and what we measure after launch.

A before and after view: scattered spreadsheets and a store feed into one connector, which writes clean rows into an accounting ledger.

Where it started

Our own connector is the first case study

For many years we have run a connector that imports orders, products and customers into QuickBooks Desktop. It works with osCommerce-family carts: osCommerce, Zen Cart, CRE Loaded and osCMax.

Building it taught us the hard parts. Product and attribute mapping. Inventory sync. Payments that split across accounts. Sales tax that must land on the right line. That know-how now shapes every custom project.

Explore the QuickBooks Connector

Project patterns

Six problems we solve again and again

Most requests fit one of these shapes. Each card shows where teams start, what we build and how we judge the result.

  • 01

    Store to accounting sync

    Starting point
    Staff retype web orders into QuickBooks by hand. Totals drift and tax lines break.
    What we build
    A connector that maps orders, payments and sales tax to the right accounts.
    What we measure
    Hours of entry per week, and mismatched totals at month end.
    Integrations & APIs
  • 02

    Spreadsheet to internal tool

    Starting point
    Orders, stock and approvals live in shared sheets. One bad paste costs a day.
    What we build
    A web tool with roles, audit history and one source of truth.
    What we measure
    Steps per task, and errors caught before they reach a customer.
    Internal Tools & Dashboards
  • 03

    Legacy PHP modernization

    Starting point
    An old PHP and MySQL app runs the business. Nobody wants to touch it.
    What we build
    A staged rebuild that keeps the data and every live integration.
    What we measure
    Downtime during cut-over, and records that match before and after.
    Legacy Modernization
  • 04

    Legacy cart migration

    Starting point
    A store on osCommerce or Zen Cart needs a modern platform.
    What we build
    A move to WooCommerce or Shopify with products, customers and history intact.
    What we measure
    Records moved without loss, and URLs that still resolve.
    E-commerce Development
  • 05

    Order and invoice automation

    Starting point
    Invoices, stock updates and reports wait for someone to press a button.
    What we build
    Scheduled jobs and rules that run the routine work on their own.
    What we measure
    Time from order to invoice, and manual touches per order.
    Business Process Automation
  • 06

    MVP for a new business line

    Starting point
    A team has an idea and a deadline, but no product yet.
    What we build
    A focused first version with the core flow and room to grow.
    What we measure
    Time to first real user, and the scope left for phase two.
    MVP Development

Inside a write-up

Every case study answers four questions

No vague promises. We report what changed in plain numbers your finance lead can check. If a figure can't be measured, we don't print it.

  1. 01

    Starting point

    What the team did by hand, and where data broke between systems.

  2. 02

    Systems and data

    Which carts, ledgers and apps were involved. How the data flowed.

  3. 03

    The build

    What we made, how we tested it on real data and how we shipped it.

  4. 04

    Measured result

    Hours removed, errors cut and what changed for the people doing the work.

Questions

Before you compare our work

Why are some projects shown without client names?

Many clients prefer to stay private. We sign an NDA on request. So we describe the problem and the build, not the company.

My setup looks like one of these. Where do I start?

Start with a free discovery call. We look at your systems and bottlenecks first. Then we suggest a scope.

Do you only work with QuickBooks?

No. QuickBooks is our deepest niche. We also connect Xero, CRMs, ERPs, shipping and payment systems.

Get a similar result

Tell us which systems you run and where time is lost. We'll map the data flow and suggest a clear first step.