Many employee-focused articles describe Merlin only in terms of HR, discounts, and training.
IHG’s current Procurement site shows a much broader operational use.
The environment is explicitly branded IHG Procurement – IHG Merlin and currently presents separate login routes for hotel users and suppliers.
That distinction matters because procurement is a business-to-business workflow, not an ordinary employee-benefit feature.
Hotel Users and Suppliers Are Different Identities
A person working at an IHG-branded hotel can need procurement access because the hotel participates in IHG programs.
A supplier needs access because it provides goods or services.
Those roles should not share one generic account simply because both use the procurement platform.
IHG’s current login experience visibly separates them.
Procurement Covers Several Hotel Lifecycle Stages
The current IHG Procurement site organizes services around areas including:
- hotel construction;
- opening and renovating hotels;
- hotel operations;
- market-specific programs.
That makes procurement relevant to owners, operators, property teams, and suppliers rather than only purchasing clerks.
Inn Code Is Part of the Hotel Context
A current Market Basket request form asks for an Inn Code along with brand, country, state, city, distributor information, and purchasing data.
The Inn Code helps establish which property the request concerns.
This is another example of why Merlin authorization can depend on hotel association as well as personal identity.
Purchasing Data Is Sensitive Business Information
The Market Basket process permits hotels to upload purchasing information for analysis.
That is operational business data.
It should not be sent to an independent “IHG procurement login” website.
Use the IHG-controlled procurement environment.
A Merlin ID Does Not Necessarily Create Procurement Permission
A hotel employee can have a valid Network ID without being responsible for purchasing.
Procurement access can therefore require a role entitlement separate from basic Merlin authentication.
This follows the same identity model seen elsewhere:
Network ID proves identity.
Application access proves authorization.
Suppliers Should Not Register as Hotel Employees
The current interface gives suppliers their own login path.
A supplier trying to obtain a hotel-user Network ID would create the wrong identity relationship.
Contractors and vendors have separate provisioning routes elsewhere in the IHG Network ID documentation as well.
Procurement Support Is Different From Employee Support
A user who can sign into Merlin but has a purchasing-program problem may need procurement or application support.
A user who cannot authenticate at all has a Network ID problem.
Keeping those support queues separate prevents hotel teams from resetting credentials for an application workflow issue.
This Is Why “Merlin Employee Portal” Is Too Narrow
Procurement demonstrates that Merlin supports the hotel business network as well as individual colleagues.
The audience can include:
hotel employees;
property managers;
owners/operators;
authorized contractors;
suppliers.
That is a broader digital-workplace model than a conventional HR portal.