The first time a company opens an office in a second country, procurement usually still feels manageable. Someone emails a local supplier, someone else approves the invoice, and the laptops turn up. By the fifth country, that same improvised habit has quietly become five purchasing cultures, five hardware standards, and a finance team that cannot say with confidence what the business spent on equipment last quarter. Standardizing procurement across borders is not about forcing every office to buy the identical machine from the identical vendor. Customs rules, power standards, keyboard layouts and local warranty coverage make that fantasy expensive. What it actually means is building one shared set of rules about how buying decisions get made, so the outcome stays predictable even when the supplier on the invoice does not. Done well, the result is boring in the best possible way. A new hire in Manila receives the same class of device as a new hire in Madrid, the approval takes a day rather than a fortnight, and nobody has to reconstruct the logic of a purchase eight months after the fact. Centralized Policy Beats Centralized Purchasing The instinct, when procurement gets messy, is to pull every purchase into headquarters. It rarely survives contact with reality. A regional manager who needs a replacement laptop on Thursday will not wait nine days for a committee in another time zone, so they buy one on a corporate card and the policy loses credibility the first week it exists. Centralizing the policy instead of the transaction solves the same problem without the bottleneck. The central team owns the specification, the approved supplier list, the spend thresholds and the record that has to exist afterwards. Local teams keep the authority to execute inside those rails, which is where their knowledge of local lead times and import paperwork is worth far more than any central process could be. Hardware Standards Work Better as Tiers Than as Model Numbers A standard that names one exact model breaks the moment that model goes out of stock in one market, which happens constantly. Tiers hold up better. Define three or four profiles by what the work demands: a light profile for sales and support, a standard profile for most knowledge workers, a heavy profile for engineering and design, and a shared or loaner pool for contractors and short assignments. Each tier gets minimum specifications rather than a part number: memory, storage, processor class, warranty length, encryption support and the management features your endpoint tooling needs to enroll the device. Now a buyer in São Paulo can satisfy the standard with whatever is genuinely available there, and the fleet stays coherent anyway. The secondary benefit is negotiating power, because tiered demand is forecastable demand, and suppliers discount volume they can predict. Supplier Databases Are the Piece Most Companies Skip Every multinational accumulates supplier knowledge, and almost all of it lives in individual inboxes. A supplier database is unglamorous insurance against that: one record per vendor, covering the countries they actually ship to, negotiated pricing, typical lead times, warranty terms and who last dealt with them. It is also where the regulatory detail belongs, because that detail varies enormously and nobody memorizes it. Importing communications equipment into Indonesia, for instance, requires local testing and a certificate from the national digital infrastructure authority, as the U.S. Commerce Department’s import documentation guidance sets out. Tariffs are a softer constraint than most teams assume, since the WTO’s Information Technology Agreement covers participants representing roughly 97 percent of world trade in IT products and commits them to eliminating duties on covered goods. Knowing which of those two worlds a given shipment sits in is the difference between a week and a month. Approval Workflows Should Turn on Thresholds The last piece is the one people overbuild. An approval workflow exists to catch the unusual purchase, not to re-examine the ordinary one. If a request matches an approved tier, comes from a listed supplier and falls under a set value, it should clear automatically with a record written and the budget holder notified. Anything outside those lines routes to a human, and because that queue is now small, the human can look at it properly. Workflows only stay honest if the record is automatic. Ask people to update a spreadsheet after the fact and you will have partial data within a month, which is worse than none, since partial data still gets used for budgeting. Running the process through a single global it procurement platform keeps the request, the approval, the order and the resulting device assignment attached to each other, which is exactly what auditors and finance ask for and exactly what scattered email threads cannot produce. Where the Groundwork Pays Off Standardization tends to get sold as a cost exercise, and it does save money, mostly by ending duplicate purchases and emergency retail buying at list price. The larger return is speed. A company that can equip a new office in three weeks instead of three months can open offices more willingly, and that changes what the business is able to attempt. Infrastructure choices compound the same way, which is why it helps to read procurement alongside the physical and hosted infrastructure decisions sitting underneath it. None of this has to land at once. Most teams get the largest gain from the first two steps alone, because a written policy and a tiered specification remove most of the ambiguity that makes cross-border buying slow. The supplier database and the workflow stop that gain from eroding as staff change and country count grows. The test is simple enough to run today. Pick a country you entered in the last two years and ask who approved the most recent hardware order there, what was bought, and where those machines are now. If answering takes more than a few minutes, the problem is not the people; it is that nothing in the process was ever designed to hold the answer.