Connect procurement processes to ServiceNow with NowConnect

Reading Time: 7 minutes

Picture the scene. An employee requests a laptop or software license in ServiceNow. The request is routed, reviewed and approved. The service management is working exactly as it should. That is until someone – or an procurement trained agent – has to make the purchase. They open an external supplier portal, place the order, wait for confirmation, track shipment separately and then copy the details back into ServiceNow.

It’s in that manual step that things start to slip. Order details get retyped. Serial numbers arrive late or never make it across. Shipment updates sit in an inbox. And the asset record gets rebuilt after the fact from an email trail or a spreadsheet.

Nothing looks broken because the laptop turns up, the request closes, and the employee is happy. But by the time that device is unboxed, three teams are already working from three different versions of the truth.

How much does disconnected procurement cost?

Most buyers want to focus on sourcing strategy or supplier negotiation. Instead, they spend their days wrangling portals. They place orders in one system, watch a second for confirmation, forward tracking numbers to whoever asked, and answer the same status question from the same requester three times before lunch.

SHI estimates that process takes roughly 35 minutes of manual effort per order, which translates to somewhere between 417 and 2,500 hours a year depending on volume. Larger buying programs lose close to a full headcount moving information between two systems that were never introduced to each other.

The cost of disconnected systems goes beyond reclaimed hours. When procurement activity sits outside the platform, leaders have less visibility into demand, cycle time, supplier performance, and spend under management. That makes it harder to identify savings opportunities, control off-contract buying, or prove the value procurement is creating at a time when SaaS, hardware, and services costs are all under pressure.

Without a single source of truth for orders, deliveries, and spend, procurement struggles to demonstrate results with confidence.

Why does disconnected procurement create inaccurate CMDB data?

CMDB owners inherit a problem not of their making. The business asks them to maintain an accurate picture of the estate from data that arrived incomplete, so they do the sensible thing and scan deeper, normalize more, and launch another reconciliation project.

Discovery does its job well. It tells you what runs on the network, and it keeps configuration items current. What it cannot tell you is whether you are licensed to run it, what the organization paid, who approved the spend, which contract covers it, or when the warranty clock started. That commercial detail belongs on the asset record rather than the configuration item, and it originates in the purchase. When the purchase happens outside of the system, the asset record starts life with holes in it.

That erosion works slowly but does real damage. Once people stop trusting the data, they stop using it and start keeping private spreadsheets instead.

Once people stop trusting the data, they stop using it and start keeping private spreadsheets instead.

 

Why do ITAM programs depend on accurate procurement data?

ITAM teams sit at the end of this chain and carry the hardest brief. They must produce a defensible license position, survive an audit, plan a refresh cycle, and evidence savings, all from records that somebody assembled after the fact from memory and email.

The market numbers bear that out. Flexera’s 2025 State of ITAM Report found organizations waste 30% of desktop software and 28% of data center software, and its 2026 edition shows complete IT asset visibility falling to 36%, down seven percentage points in a year. The same 2026 report shows that audit exposure has not eased either, with 48% of organizations audited in the past year and 44% spending more than $1 million on audits over three years. SHI’s ITAM practice sees what sits behind those numbers. Programs stall on foundational data quality far more often than on tooling.

Those figures have stayed stubborn for a reason. Organizations keep buying better instruments to measure data that was already flawed when it entered the system. Better tooling did not fix it. Cleaner intake might.

How do procurement gaps affect CMDB and ITAM teams?

Each team experiences this as their own problem. Procurement calls it an admin burden, the platform team calls it a data hygiene issue, and ITAM calls it a tooling gap. All three stand at different points along the same broken chain, and the organization pays three times for one root cause.

The chain runs in one direction. A purchase creates an asset, the asset becomes a configuration item, and that configuration item then informs every lifecycle, service, and financial decision that follows. Each handoff loses a little fidelity, so a gap introduced at the buying step travels downstream to everyone else and costs more to correct the further it goes.

The blame lands in the wrong places. Leadership challenges each team on the symptom it owns, budget goes into remediation projects that clean the same data twice a year, and nobody addresses the seemingly innocuous moment someone left the platform to place an order.

What is the business impact of inaccurate asset data?

This isn’t just an operational irritation. It surfaces as money and risk, and it does so in ways the business feels directly.

Organizations overbuy because nobody can say with confidence what already sits in a stockroom, and they keep paying maintenance on hardware that left the estate months ago. They walk into vendor audits without the evidence to push back and settle true-ups they could have avoided. Meanwhile new starters wait on devices that somebody ordered but nobody can trace, refresh planning turns into an educated guess, and security teams defend an estate that does not match the asset list in front of them.

Speed suffers alongside accuracy. SHI’s implementation data shows fulfilment cycles running at around 12 days in a disconnected process compress to roughly three once the buying step moves into the platform. Every employee waiting on a device feels that gap, and so does every leader explaining why onboarding takes as long as it does.

What happens when procurement runs inside ServiceNow?

Go back to that laptop request and run it again, this time with SHI NowConnect in place. NowConnect is a native integration that brings SHI procurement directly into your ServiceNow instance, so the buying step happens inside the platform rather than alongside it.

The employee raises the same request from the same service catalog, and procurement reviews and approves it exactly as before. The difference comes next. SHI receives the order without anyone leaving ServiceNow, and the information flows back on its own: order acknowledgement first, then shipment tracking and ship-to detail, then serial numbers and asset tags landing against the right asset record as the order confirms and ships rather than weeks later when somebody finds the paperwork.

Your team learns no new portal and maintains no parallel process. Approvals, routing, and workflows stay exactly where you built them, and NowConnect runs on the ServiceNow backbone, Service Exchange, alongside your ITSM procurement workflows.

Each team banks the gain in a different currency. SHI’s modelling puts the procurement benefit at around 70% fewer manual touchpoints per order and more than 30% off the cost per transaction. With NowConnect, organizations can reduce request-to-fulfillment cycles from 12 days to three, generate approximately $150,000 in annual savings, and increase spend under management from 61% to 92%.

The platform team gets asset records built from source data instead of from someone’s inbox. ITAM finally gets an intake process worth building a program on: hardware asset records created automatically at the source, complete with serial number, asset tag, and purchase detail, feeding ServiceNow ITAM, including HAM Pro, instead of a post-hoc spreadsheet.

What procurement data should flow into ServiceNow automatically?

A connected purchase should populate everything the business needs to manage that asset for the rest of its life:

• SHI catalog items synced into your service catalog
• Order acknowledgement and purchase order reference
• Shipment tracking and ship-to details
• Serial numbers and asset tags against the correct record
• Purchase and receipt data feeding ServiceNow ITAM (including HAM Pro)
• Visibility of stock held with SHI through Virtual Stockroom

Request a personalized demo and we’ll walk your procurement, platform, and ITAM teams through NowConnect, guiding you through the full path from request to order to asset record, using your own workflows. A twenty-minute demo is usually enough to know where your 35 minutes per order is going.

NEXT STEPS:

Request a personalized NowConnect demo!