Whether an Ariba implementation reaches its goal is rarely decided by the technology. What matters is that catalogue maintenance has a clear owner, that approval limits match the organisation, and that the purchase order looks the same in the backend as in the portal.

We introduced SAP Ariba Buying as a template and rolled it out to sites in Switzerland and the USA, including the ERP connection via the Cloud Integration Gateway. Most of what we know about rollout sequences, catalogue strategies and local special requests comes from that programme.

We take on a project from the start, or step into a running one that is not delivering the expected effect.

Why clients get in touch

Indirect purchasing runs on emailOrders are created in inboxes and spreadsheets, or placed directly in the supplier’s web shop. Approvals get bypassed along the way.
Catalogues go stalePrices are out of date and nobody in the organisation owns the maintenance.
Orders do not reach SAPThe integration fails regularly and the errors only surface at goods receipt.
Another site is due to joinThe template does not hold up against local requirements and the rollout slips.

Scope

What we cover

From process definition to operation, for a single site or an international organisation.

Template and rollout strategy

A core template that holds globally, with clearly defined and justified local deviations.

Guided buying

Buying guidance that requesters can operate without training, and therefore actually use.

Catalogue management

Punch-out, hosted catalogues, price maintenance and the question of who owns all of it in the end.

Supplier onboarding

Onboarding, master data alignment and order transmission to suppliers of very different sizes.

Integration into the SAP backend

Connection to SAP S/4HANA or ECC, including Cloud Integration Gateway and error handling that deserves the name.

Approvals and compliance

Value limits, deputies and traceability, aligned to your organisation rather than to a standard scheme.

How we work

How an Ariba rollout runs

Step 1

Process and template design

Buying channels, approval logic and catalogue strategy defined before the first customising is done.
Step 2

Pilot site

One site goes fully live, including backend integration. This is where you find out what the template cannot do yet.
Step 3

Rollout wave

Further sites follow a proven pattern, with local deviations documented rather than improvised.
Step 4

Handover to operations

Catalogue maintenance, supplier onboarding and support move to the organisation, with clear responsibilities.

What you get

What you get from us

Rollout experience across continents

Sites in Switzerland and the USA, with all the local particularities that come with them.

Integration from the start

We plan the backend connection together with the process, not as the last step before go-live.

Adoption as the goal

A portal that purchasing bypasses has missed its purpose. That is how we measure the result.

Questions

Frequently asked

Is Ariba worth it for a mid-sized company?

That depends less on company size than on indirect spend volume and the number of suppliers. Where many small orders pass through many hands, it usually pays off quickly. With a few large framework contracts, less so.

How long does a rollout take per site?

After the pilot, further sites typically take six to twelve weeks, provided the template is stable and local data arrives on time.

Can you take over an existing Ariba system?

Yes. We look at what was implemented, where it is stuck and what can be straightened out with reasonable effort. Not every problem needs a reimplementation.

Contact

Planning an Ariba implementation or rollout?

Tell us how your indirect purchasing works today. We will give you an honest view on whether the effort pays off.

Discuss your plans

SAP Ariba and procurement