Prevent Biometrics · Sports technology and manufacturing
How Prevent Biometrics runs orders, shipping and invoicing from HubSpot.
Impact-sensing mouthguards made for teams and governing bodies such as World Rugby. We connected HubSpot to their inventory, shipping and invoicing tools, so every order runs from signed deal to sent invoice in one place.

- 4
- systems on one live record: HubSpot, SOS Inventory, Shippo, invoicestack
- 5
- teams working from the same order: finance, operations, sales, service, leadership
The challenge
Orders are large and ship in smaller batches, but they lived in SOS Inventory and Google Sheets, and each team saw only part of the picture.
- Shipments were created by hand, which put steady pressure on the finance team.
- Month-end invoicing stalled because shipments were often late. Finance didn’t see what had shipped until one to two weeks after month-end.
- Large orders were hard to reconcile. When one order shipped in several batches, it was hard to tell what had gone out against what was owed.
- Support tickets piled up around missing orders and shipping miscommunication.
An earlier fix built with Google Sheets and Apps Script closed some gaps, but struggled as order volumes and complexity grew.
What we built
HubSpot became the single source of truth. A deal now carries an order from contract to invoice, with every team seeing the same live record.
-
01
Deal to sales order
When a deal reaches contract signed, HubSpot creates the sales order in SOS Inventory, creating the customer first if needed.
- HubSpot
- SOS Inventory
-
02
Customer order to shipment
Each deal holds several customer orders, moving through a manufacturing pipeline in HubSpot. At Dispatch, HubSpot creates the shipment in SOS and writes the IDs back.
- HubSpot
- SOS Inventory
-
03
Rates, labels and tracking
From the same customer order, the team requests Shippo rates, picks a service and creates the label without leaving HubSpot.
- HubSpot
- Shippo
-
04
Shipped to invoiced
Shippo webhooks feed status back to each order and up to the deal, which waits for shipped before creating the invoice in invoicestack for finance.
- Shippo
- HubSpot
- invoicestack
The manufacturing team used to update shipping status and notes in Google Sheets. They now work entirely from custom views of customer orders in HubSpot, with all the context they need at a glance.
The volume of automation and the complexity of the workflows ruled out off-the-shelf connectors such as Zapier, and Data Hub on its own couldn’t handle it efficiently. Custom code actions in Data Hub kept everything in one place: easy to maintain in-house, with proper control and an audit trail for every data flow.
The details that made it work
Shipping choices, with the cost per unit
Before a label is created, Shippo returns five options, each a different mix of delivery time and price. The team picks one, and the price is stored on the customer order, so cost per unit can finally be reported on properly. Before, that meant combining data from several sources in Google Sheets and estimating. It only works if the order data is right: item details, HS codes and duty information have to be correct on every customer order, which is why the process is built around customer order tags and tightly controlled pipeline stages.
- Manufacturing
- Quality check
- Dispatch
- Shipped
Shipping options from Shippo
Example with illustrative values
Choosing reliability over a tidy reference
Prevent Biometrics originally wanted shipment references that followed their sales orders in sequence, such as SO1234A and SO1234B. When bulk orders triggered together, several shipments tried to claim the same reference, causing conflicts, errors and delays, and adding pauses and timing logic only made it worse. So we asked what the business really needed. Sequential naming wasn’t critical; reliability was. We switched to the inventory system’s automatic references, which give every shipment a unique ID. The conflicts disappeared, and so did the extra logic.
Built for bulk
Large batches of orders initially caused timeouts in custom code. We solved this with workflow branching and staggered enrolments, then moved to Data Hub’s native rate limiting so runs stay controlled.
How we delivered it, and keep it running
- MapMap the data and build manufacturing objects and pipelines in HubSpot
- ConnectConnect HubSpot to SOS Inventory
- TestTest in a sandbox: simulated bulk runs, rules such as “shipments only at Dispatch”, then real scenarios run by Prevent’s manufacturing lead
- Go liveOrders and shipments live in HubSpot, with shipping labels and automated invoicing following on the same foundation
A managed RevOps service after go-live
- Automated alerts flag failed workflow runs, missing data and records that fail to enrol.
- Reports and views surface orders that didn’t sync, and a daily review summarises integration activity.
- We triage and resolve errors, and Prevent’s team can re-trigger workflows themselves when an exception comes up.
- Reminders cover access token rotation, so an expired token never takes the integration down.
The results
Orders, shipments and invoices now run through one connected process, and each team works from the same live information.
- Finance
- Sees what has shipped against what’s outstanding as it happens, and invoices are created automatically once an order ships, so month-end no longer waits on late shipment records.
- Operations
- Creates shipments and labels from the order itself, instead of re-keying data between systems.
- Sales
- Knows straight away when an order has shipped, so account managers update customers without chasing operations.
- Customer service
- Creates orders, pulls shipping and tracking information from the order record, and sees where each order sits in the manufacturing backlog.
- Leadership
- Reports for the first time on shipped units, replacements versus new orders, and pipeline performance.
The outcome is a full customer journey in HubSpot, with shared visibility at every key milestone.
More of our work
Fortis Payment Systems · Embedded payments and merchant services (US)
How Fortis moved a sales team off Salesforce and runs merchant boarding from HubSpot.
Fortis Payment Systems is a US embedded payments provider. After it acquired Serve First Solutions, whose sales team ran on a heavily customised Salesforce, we migrated that team’s active data into Fortis’s HubSpot and ran the cutover over a single weekend, so reps were back in HubSpot on Monday morning with their full history. We also built a custom two-way integration with Fortis’s Partner API, so reps pick an office and agent and submit merchant boarding applications from the deal. Salesforce is retired, and every closed-won deal carries an office ID and an agent ID.
Read the case studyHawkin Dynamics · Sports technology
How Hawkin Dynamics runs lead generation, pipeline and billing from HubSpot.
Hawkin Dynamics sells hardware, accessories and multi-year subscriptions. We rebuilt their HubSpot around one revenue process: nine deal pipelines down to two, 25,000 contacts scored on engagement and fit, and six stages that hand over automatically from first score to renewal and invoice.
Read the case study