The UK retail buying centre: merchandising, store ops, IT, finance, ecommerce

Selling B2B into UK retailers means navigating a buying centre that's wider and more functionally distributed than typical SaaS-to-SaaS deals. Merchandising, store operations, IT, finance, and ecommerce each have legitimate veto rights on different categories of vendor purchase.

This piece is a practitioner walkthrough of who owns what.

Merchandising

Owns: range planning, supplier relationships, buy-in decisions, pricing architecture, stock allocation across stores. The function with the longest decision cycles, the largest financial commitments, and (often) the most influence at executive level.

What merchandising approves: anything affecting product range, supplier-data interchange, planogram design, pricing systems, demand forecasting.

How merchandising buys: relationship-led, slow, often tied to the seasonal calendar (range reviews happen on cycle; off-cycle change is hard).

What vendors get wrong: targeting merchandising leaders at the wrong moment in the cycle. Range-review windows are when they engage; mid-cycle they're focused on execution.

Store operations

Owns: physical store performance, in-store technology, store staff training, loss prevention, in-store customer experience, point-of-sale.

What store operations approves: anything affecting store-level processes, in-store hardware/software, store-staff workflows, customer-facing in-store technology.

How store operations buys: cautious about anything that could disrupt store running. Pilot-stores phase common before chain-wide rollout. Cycle: 6-12 months from interest to chain rollout for substantive operational change.

What vendors get wrong: pitching at central store-ops leadership without understanding the regional / district structure that does actual implementation. Central approval doesn't mean regional adoption; regional adoption requires regional-manager engagement.

IT

Owns: enterprise systems, integrations, security, infrastructure, vendor technical assessment.

What IT approves: any vendor purchase requiring integration, data exchange, or enterprise-system changes. In retail, this is most B2B SaaS purchases.

How IT buys: technical-evaluation-heavy, with formal architecture review, security questionnaires, integration testing. Cycle in retail similar to enterprise SaaS: 60-150 days for technical review, with gates including DSPT-equivalent retail-data-protection standards.

What vendors get wrong: assuming retail IT runs on the same procurement timelines as retail merchandising. Retail IT typically operates on enterprise-IT timelines, separate from the trading calendar; the same vendor's deal can hit retail-IT review and retail-merchandising review on different clocks.

Finance

Owns: capital allocation, ROI assessment, payment terms, contractual liability, vendor financial-stability review.

What finance approves: contracts above defined value thresholds (varies by retailer; typically 50-250k pounds annual contract value triggers explicit finance review).

How finance buys: increasingly metric-driven (GMROI for product-related decisions, payback-period for operational tooling, ROI calculation for transformation projects). Procurement-team-led review with finance signoff at value gates.

What vendors get wrong: failing to articulate the business case in retailer-relevant metrics. 'Reduces cost by 20 percent' is generic; 'improves GMROI by X points' or 'reduces shrinkage by Y percent' speaks the buyer's language.

Ecommerce

Owns: digital storefront, online-only product strategy, digital-first operational systems, omnichannel integration.

What ecommerce approves: anything affecting digital trading, online customer experience, fulfilment integration with online orders.

How ecommerce buys: faster than the rest of the retail buying centre. Smaller deal sizes typically; more iterative; more comfortable with newer-vendor products.

What vendors get wrong: assuming ecommerce buys at retail-IT pace. Ecommerce procurement often moves faster, but the deal must still pass retail-IT review at a defined gate. Vendors who land ecommerce-side enthusiasm without IT review face procurement delays they didn't plan for.

How to navigate the buying centre

Three habits:

Map the buying centre in early discovery. Ask explicitly: 'who else needs to weigh in on a decision like this?' Retail buying centres are wider than buyers initially disclose; multiple discovery conversations are typical to surface the full set.

Sequence engagement appropriately. Champion in one function builds enthusiasm; that function pulls in adjacent functions; gradually the deal coalesces. Vendors who pitch all five functions in parallel typically lose to vendors who sequence carefully.

Know which function has primary authority for which deal type. Stock-management software: merchandising primary, store-ops and IT secondary. Point-of-sale upgrade: store-ops primary, IT and finance secondary. Marketing-tech: merchandising or marketing primary, IT and finance secondary. Vendors who target the wrong primary function lose months convincing the wrong stakeholder.

This is editorial coverage of UK retail B2B buying-centre practice. Specific retailer organisational structures vary; the cross-functional veto-rights pattern is consistent.