An e-procurement catalogue that lives inside SAP Ariba

Situation

The supplier who has to fit the customer's process

The client supplies Maintenance, Repair and Operations (MRO) items — the consumables and spares that keep a factory running — to large manufacturing organisations in India.

Buyers of that size do not purchase from a website and they do not purchase from a PDF price list. They purchase through an e-procurement platform, in this case SAP Ariba, because that is where their approval workflow, their budget controls and their audit trail live. A supplier who cannot be bought from inside that platform is, in practice, harder to buy from than one who can.

Problem

Every order was crossing a gap by hand

1. The catalogue was outside the buyer's process. Procurement staff had to leave their own system to find out what was available and what it cost.
2. Orders arrived as documents, not as data. Anything that has to be read by a person and re-entered into a system is a delay and a transcription risk on every single line item.
3. The vendor found out late. With no notification until an approved order emerged, nothing could be picked, packed or prepared during the approval window — which on MRO items is often the difference between same-week and next-week delivery.
4. Catalogue changes needed a developer. Product and price data that cannot be maintained by the business goes stale, and a stale catalogue inside a buyer's system is worse than no catalogue at all.

In B2B supply, being easy to buy from is a competitive position — not an IT detail.

Implication

What friction costs a supplier at this level

Large manufacturers consolidate suppliers. When a procurement department reviews who they buy MRO items from, the supplier whose catalogue is one click inside their existing workflow has an advantage the supplier outside it cannot answer on price alone — because the cost of the awkward supplier is paid in the buyer's own staff time, and they know it.

There is a lock-in effect too, and it runs in the supplier's favour. Once a vendor is properly integrated into a buyer's procurement environment, switching to a competitor is no longer a purchasing decision; it is an IT project. Getting integrated is therefore not just an efficiency exercise. It is a retention strategy.

What we built

A catalogue that lives inside the buyer's system

• Powerful product search and shopping cart designed for the buyer's procurement staff, not for retail shoppers
• Backend admin for catalogue management and full visibility of incoming orders
• Accessed through SAP Ariba with pre-agreed security key authentication
• Purchase orders posted back to the buyer's e-procurement system automatically on checkout
• Automated alert emails so pre-processing can start while the order is pending buyer approval

Result

An order path with no manual step in it

Procurement staff search and order from inside their own environment. Purchase orders arrive in the buyer's system as structured data on checkout. The vendor sees orders as they are raised, and the catalogue is maintained by the vendor's own team rather than by a developer.

Tech stack: PHP · MySQL · SAP Ariba API Integration