QuickBooks Web Connector (QBWC) is a free tool from Intuit that lets a third-party application exchange data with a QuickBooks Desktop company file, using XML over a scheduled sync rather than a live, always-on connection. It's how a lot of older Desktop integrations, point-of-sale systems, e-commerce plugins, custom tools, talk to QuickBooks without someone manually exporting and importing files.
1. A third-party app provides a .qwc file. This is a small configuration file the app gives you, it tells Web Connector where the app's sync service lives and what it's allowed to request from QuickBooks.
2. You add that file to Web Connector. Open QuickBooks Web Connector (installed separately or alongside certain Desktop versions) and add the application using its .qwc file.
3. You set a password for the connection. This authenticates the third-party app's requests so random software can't just start pulling your company data.
4. You run or schedule a sync. Tick the checkbox next to the application and click Update Selected, or set an auto-run interval so it syncs on its own. During a sync, QBWC sends XML requests (built on the qbXML or QBXML SDK format) to QuickBooks and relays data back to the app.
5. QuickBooks has to be open on that machine. This is the part that catches people off guard: Web Connector talks to a local company file through the Desktop application, so the computer running QuickBooks Desktop needs to be on and the file accessible for a sync to happen.
Web Connector was built for a world of on-premise software talking to other on-premise software, batch syncs, not real-time events. That's fine for a nightly inventory update. It's a poor fit for something that needs to happen the moment an order comes in, since the sync only runs on whatever schedule you set, or whenever someone remembers to trigger it manually.
It also only works with QuickBooks Desktop, not QuickBooks Online, and it requires that specific computer with that specific company file to be reachable. A business running QuickBooks Online, or one that wants integrations to keep working even when nobody's logged into the Desktop machine, usually needs something built on QuickBooks' actual API instead of Web Connector's older XML sync model.
Instead of waiting for the next scheduled Web Connector run, data moves into or out of QuickBooks the moment the triggering event happens somewhere else, an order placed, a job completed, a payment received.
When a business moves off Desktop (and off Web Connector-based integrations with it), we rebuild the equivalent connections on QuickBooks Online's API so nothing that used to sync automatically goes back to being manual.
If something in your business waits for a nightly or manually-triggered sync to catch up, that's usually fixable. Tell us what it is and we'll tell you whether it can run the moment it actually needs to.
Tell us what's connected through it today and what you wish happened faster. We'll tell you whether it's worth rebuilding on a more current connection, or whether the real fix is somewhere else in your business entirely. Either way, Web Connector is just one example of the manual-sync pattern we fix.
Let's talk →Connecting third-party applications, point-of-sale systems, e-commerce platforms, custom integrations, to a QuickBooks Desktop company file so they can exchange data without someone manually exporting and importing files between them.
Get the .qwc configuration file from the third-party app you're connecting, add it in Web Connector, set a password, and run or schedule a sync. QuickBooks Desktop needs to be accessible on that machine for the sync to actually pull or push data.
No. Web Connector is specific to QuickBooks Desktop and its local company file model. QuickBooks Online integrations connect through QuickBooks' own API instead, which doesn't require a specific machine or company file to be open.