formerly Datos Operations
← All Projects
TypeIntegrationDevelopment
ToolsJobberSOS Inventoryn8n

Jobber to SOS Inventory Sync for Inventory Tracking in Jobber

Giovanni Segar
Giovanni SegarFounder

Inventory management is never fun, but it’s much worse to do it by hand. Sunset Docks Muskoka sells, installs, and services boat lifts, docks, and canopies for waterfront owners. Their team uses Jobber, a popular field service management tool, but Jobber currently has no inventory features.

They wanted Jobber synced to SOS Inventory so when they sold a product they stock, they could track it leaving their shelves. Timing makes it harder: much of their selling happens over the winter, and the installing happens in spring.

We offered two approaches in our initial consult. The first used n8n, an automation tool, with a Google Sheet for approvals and monitoring. The second was a custom sync system written in code, with its own interface for managing it. We thought both were viable, and we told them up front that Google Sheets isn’t great long-term because of its rate limits and the errors they cause in automations like this. They chose the n8n version, which was also the cheaper one. Their volume looked low, so we were confident n8n and a Google Sheet would be a decent starting point.

As it turns out, it wasn’t. Here’s what we learned in the process, and how we made things right with the client.

In JobberJob #1182ClientDana WhitlockInvoice #4471Job#1182n8n workflowOn eachJobber eventIn SOS InventorySales Order #612Reserves the stockShipment #588Takes it off the shelfGoogle SheetUnmatched itemJobResolvedCustom Cottage Bracket1190NDock Ladder, 4 Step1187NSwim Platform Kit1179YCanopy Cover, 20 ft1171YEmail to salesCustom Cottage Bracket onjob 1190 has no matchin SOS.In JobberJob #1182ClientDana WhitlockEditedLine itemsEvents2n8n workflowTwo events,same momentIn SOS InventorySales Order #612FromJob #1182ClientDana WhitlockLines3Sales Order #613FromJob #1182ClientDana WhitlockLines3Duplicate
Illustration. People and companies shown are fictional.
01

What we built with n8n and a Google Sheet

Each time a job or invoice changed, Jobber sent an event to an n8n workflow, which wrote the matching record in SOS. A job in Jobber synced to a sales order in SOS, which reserves the stock until the install. An invoice in Jobber became a shipment in SOS, which takes the stock off the shelf. Labor and other services stayed in Jobber.

Line items were matched to SOS products by exact name. A name with no match went to the Google Sheet, and the sales team got an email so someone could fix the name in Jobber or SOS.

We would have chosen a more durable ID-based match, but line items in invoices are frequently written ad hoc by the team and not always chosen from a product menu. We decided against fuzzy matching due to potential for mistakes on similar products that have different sizes.

02

Where it went wrong

The system seemed to work well at first, but the trouble came from edge cases we hadn’t anticipated. Jobber sometimes sent two events for the same job at the same moment, and the workflow created a sales order or shipment for each. Edits to old jobs created sales orders for work finished before SOS was in use, which threw off the counts. Our client noticed duplicate sales orders and shipments showing up in SOS.

We fixed each problem inside n8n as it came up, which meant more and more error handling. We were playing defensive whack-a-mole instead of being able to anticipate and monitor issues, which is not how we like to operate.

After a few weeks of back-and-forth and tweaks, we decided we needed a different approach entirely.

Proposing a rebuild

Their team had put time and money into the sync and still couldn’t trust their numbers. On a call to talk through where things stood, they asked us to tell them plainly whether it could get where they needed it to be.

We told them that we had misjudged the project from the beginning, and that it needed a more robust system. SOS Inventory was new to us, and its API had quirks that only showed up once we ran into edge cases.

We proposed the second option from the original proposal: a sync written in code, with a dashboard in place of the Google Sheet. We didn’t charge to rebuild the sync to the reliability bar we’d set in the original fixed price project. We only charged a small fee for the new dashboard feature that was genuinely new scope.

These types of double-backs are very uncommon, but it’s important to us to make things right for the client no matter what it takes.

Sync DashboardWorker runningTypeJobber #ClientSOS Sales OrderSOS ShipmentStatusJob #1182 edited: Sales Order #612 updatedJob#1182Dana Whitlock612syncedInvoice#4471Dana Whitlock588syncedJob#1190Marcus Lee618syncedInvoice#4480Marcus Lee592syncedInvoice#4483Priya Raman589syncedJob#1194Owen FraserNo SOS productsEvery 3 minAsks Jobberwhat changedEvery hourRe-checks everyjob and invoiceEvery updateTests pass beforeit goes liveIf a run failsOur team getsthe alertTest modeWriting nothing to SOSJobber recordOld automation wroteNew sync would writeMatchJob #1182Sales Order, 3 linesSales Order, 3 linesInvoice #4471Shipment, 3 linesShipment, 3 linesJob #1190Sales Order, 5 linesSales Order, 5 linesInvoice #4480Shipment, 4 linesShipment, 4 linesJob #1194Nothing, no productsNothing, no productsPick edge casesReal jobs and invoicesCheck togetherIn Jobber and SOSFix assumptionsThe ones that were wrongRe-testBefore the next sessionRetrospectiveprocessPackage linescan’t shipIn JobberInvoice #4483Job#1176, services onlyFloating Dock Starter PackagePackage · Qty 1Look up its partsParts list in SOSDock Section, 10 ft× 2Hinge Kit× 1Dock Cleat× 4In SOS InventoryShipment #589CommentJobber Invoice #4483Floating Dock Starter PackageDock Section, 10 ft2Hinge Kit1Dock Cleat4
Illustration. People and companies shown are fictional.
03

Rebuilding the sync in code

We started from the n8n workflow and rebuilt it in code, questioning each assumption the first version had made.

Every Jobber job and invoice now gets one record in the sync’s own database before anything is written to SOS, so a job can’t end up with two sales orders. The sync asks Jobber what changed every few minutes and works through the changes one at a time, so two events can’t race each other. Goodbye webhooks, we don’t miss you.

Once an hour it re-checks every job and invoice it tracks, because Jobber doesn’t flag every edit as a change (that was a fun one to find out via testing). If a sync still fails after its retries, our team gets an alert.

The Google Sheet was scrapped for a dashboard that lists every job and invoice next to its sales order and shipment, with a status, plus a page of unmatched item names with a button for each fix.

04

Testing it next to the old system

Their busy season was underway, and two systems writing to the same inventory would have created duplicates. So the new sync ran in test mode for nine days next to the n8n workflow. It read every change from Jobber and recorded what it would have written to SOS, without actually making any changes.

After 1k+ examples, we felt confident in the new system and switched over in one sitting. The goal of this stage was to reliably match the behavior of the n8n sync, but we still needed to improve on it.

05

Three review sessions on real jobs

This was the key to success in v2 of the project. After the switch, we held three working sessions with their team. Before each one, we picked real jobs and invoices that covered different situations, like a package, a return, a deleted invoice, and a walk-in sale. On the call we opened each one in Jobber and SOS side by side and asked whether it matched what happened in the yard.

The first two sessions turned up all kinds of discoveries and “Oh, I didn’t know it worked like that” from the client. We fixed each finding within a day and checked it in SOS before the next session. In the third session, every example checked out.

06

One example fix: packages billed without a job

Sunset sells packages, like a dock attachment package, made of several stocked parts. SOS breaks a package into its parts on a sales order, and it refuses package lines on a shipment. So when a package was billed on an invoice and the job didn’t include it, its parts never came off the shelf in SOS.

The team spotted one on a real invoice in the first session. The sync now reads the package’s parts list from SOS and ships the parts itself.

This shows the importance of retrospectives for systems like this, because APIs do not always work the way you’d expect, and documentation is often missing key details.

Biting the bullet: the recount

The second session also surfaced the biggest problem. SOS showed hundreds of products reserved on sales orders for jobs that were long finished.

The reason was simple: anything invoiced before the sync went live didn’t get a shipment (on purpose). The side-effect was that its sales order stayed open with nothing shipped. When version one launched, we had brought only open jobs into the sync, to avoid taking stock off the shelf for orders that were already delivered. That left old jobs half recorded, and an edit to one could pull stale data back in at any time.

We stopped trying to pick a safe cutoff. Instead, we processed every job and invoice in their Jobber history. We knew this would throw their inventory off, but it was already inaccurate and in need of a recount.

The team scheduled a full recount of the yard to set a clean starting point. From then on, every job and invoice updates SOS as it happens.

Sometimes you just need to bite the bullet and start from a clean slate.

What our client said about working with us

Nuance has been great to work with. They’ve helped us automate the integration between our CRM and inventory software, reducing a lot of manual work and making the process much more efficient and reliable. They’ve taken the time to understand how our business works, and their team has been knowledgeable, responsive, and easy to work with.
Mark Digiulio
Mark Digiulio
Co-owner, Sunset Docks Muskoka

Lessons learned

  1. 1

    n8n was underpowered for this sync

    It’s a good tool for workflows with a few steps and few ways to fail. A sync that has to remember what it already created, handle edits, deletions, and returns, and never write the same thing twice needs a database and tests. It’s possible to do in n8n, but much more difficult.

  2. 2

    Review it after launch

    Any system with complex business rules needs a review on real records with the people who know the business.

  3. 3

    The cheaper option isn’t always the best option

    Version one cost less to build and more to keep fixing.

  4. 4

    Own your mistakes

    Nobody gets every project right, especially one with a tool they haven’t used before. What matters is how you handle it. We told the client we had sized the project too small, rebuilt the core without charging for it, and kept going until their numbers made sense.

For field service businesses that keep stock outside Jobber

Jobber runs the quote, the schedule, and the invoice. If your stock lives in SOS Inventory or a similar system, we can help you build a sync so you don’t have to do it by hand.

If you’re weighing a no-code automation against a custom build for a sync like this, ask how each one handles duplicates, edits, deletions, and returns, and how correctness will be verified when it’s running.