Loading... Loading... Loading... Loading... Loading... United Arab Emirates, Dubai
Case Study

Microsoft Power Platform  |  SAP S/4HANA Integration

From Spreadsheets to a Real-Time
Apparel Fulfilment Platform

How we digitised the end-to-end kit request, reservation, collection and returns process for a national Olympic and Paralympic committee, with a bilingual Power Pages portal connected live to SAP.

Client
A national Olympic and Paralympic committee
Sector
Sports governance and major event delegations
Business area
Official team apparel: kit requests, warehouse fulfilment, collection and post-collection returns
Solution
Bilingual (Arabic / English) self-service fulfilment portal with real-time ERP integration
Technology
Microsoft Power Pages, Dataverse, Power Automate, Microsoft Entra ID, Microsoft Graph, Azure Key Vault, SAP S/4HANA OData APIs
30
automated business workflows
12
Dataverse tables in the data model
550+
portal components delivered
8
user roles, 41 permission rules
2
languages, full Arabic RTL and English
Live
two-way SAP S/4HANA reservations

01 · Overview

Executive summary

Dressing a national delegation is a logistics operation in its own right. Every athlete, coach, companion, delegate and VIP needs the right kit, in the right size, ahead of every Olympic, Paralympic, summer, winter and beach event, and every item that leaves the warehouse has to be accounted for in the ERP.

Our client was running this process through emails, spreadsheets and manual SAP entries. We replaced it with a single digital platform that covers the entire lifecycle: request, approval, size selection against live stock, SAP reservation, warehouse preparation, OTP-verified collection and a structured returns and replacement process.

The result is one source of truth for who is entitled to what, what has been reserved, what has been handed over and what has come back, shared in real time between requesters, the logistics team, programme administrators, recipients and SAP.

The Problem

The challenge

The committee equips delegations for a busy calendar of events, alongside its own operational and training-centre staff. Before the project, the process relied on people rather than systems, which created five recurring problems:

  • No live view of stock. Sizes were promised to recipients without knowing whether the warehouse actually held them, so shortages surfaced late, at preparation or collection.
  • Manual, error-prone data collection. Recipient lists and sizes arrived in spreadsheets and messages and had to be re-keyed, checked and chased.
  • Duplicate issuance. With no consolidated history per person, there was no reliable way to stop a recipient receiving the same item twice within a year.
  • Weak proof of handover. Collection had no verifiable confirmation that the right person received the right kit.
  • Unstructured returns. Damaged, missing or wrong-size items were handled case by case, without an audit trail and without the corresponding corrections in SAP.

The committee needed a platform that external recipients could use without training, that internal teams could run daily, and that kept SAP accurate without anyone typing a reservation by hand.

02 · The Solution

One connected journey

We designed and built a secure, bilingual web portal on Microsoft Power Pages, with Dataverse as the system of record and Power Automate as the process and integration engine. Each user group signs in to an experience tailored to its role, and every step of the kit journey is driven by the platform.

  1. Request

    Requester

    Authorised requesters raise a kit request through one of three guided paths: event delegations, operations teams or training-centre staff. Each path captures the event, federation, pickup location and SAP cost centre.

  2. Add recipients

    Requester

    Recipients are added one by one or uploaded in bulk from an Excel template. Every row is validated for required data and business rules, and the requester gets precise feedback on anything that needs fixing before a single record is created.

  3. Approve

    Administrator

    Programme administrators approve or reject requests directly in the portal, with safeguards against duplicate decisions.

  4. Invite and select sizes

    Recipient

    Recipients are onboarded automatically, receive a personal invitation in their language, and choose sizes from options that reflect live SAP availability, supported by built-in apparel and footwear size guides.

  5. Reserve

    Automatic

    Confirming sizes creates the reservation in SAP in real time. The warehouse immediately sees what to prepare.

  6. Prepare and collect

    Logistics

    Logistics prepares the kit, marks it ready and hands it over only after the recipient's one-time passcode is verified. A printable PDF summary accompanies each request.

  7. Resolve issues

    Recipient

    For 48 hours after collection, recipients can raise a discrepancy report. After that window the request closes automatically.

Workflow

Who does what: the fulfilment workflow

Each step is handled by the right role, with the platform and SAP doing the heavy lifting in between.

Fulfilment swimlane Requester · Administrator · Recipient · Portal automation · Logistics · SAP S/4HANA 11 steps

Swipe sideways to see the full diagram, or tap it to open full size.

Lifecycle

Request status lifecycle

One unified status model keeps every request, recipient and return in step.

Dataverse status model Shared by requests, recipients and returns Unified

Swipe sideways to see the full diagram, or tap it to open full size.

03 · Key Capabilities

Real-time SAP S/4HANA integration

The portal talks to SAP directly through its OData APIs. Dedicated integration flows handle authentication, CSRF token and session management, and batched write operations, so the ERP and the portal never drift apart.

  • Recipient opens size selection
    Two-way with SAP: Live stock availability returned
  • Sizes confirmed
    Sent to SAP: Reservation created against cost centre
  • Recipient removed or request cancelled
    Sent to SAP: Reservation items cancelled
  • Returned item accepted
    Sent to SAP: Reversal reservation posted
  • Administrator adds a catalogue item
    Two-way with SAP: SKU lookup auto-fills item details
  • Every day, automatically
    Two-way with SAP: New materials synchronised to the portal
  • Live availability checks before any size is offered or reserved.
  • Automatic reservation creation and update, posted against the correct cost centre and linked back to the request.
  • Reservation cancellation and reversal when recipients are removed, requests are cancelled or items are returned.
  • SKU lookup for administrators, which auto-fills item descriptions, emblem and gender from SAP when new catalogue items are defined.
  • Scheduled daily synchronisation of new SAP materials into the portal's stock catalogue.

365-day rule

An eligibility engine that prevents duplicate issuance

When a recipient is added, the platform compares the kit composition for their category with everything they have received in the previous 365 days. Items they already own are excluded automatically, so each person receives exactly what they are entitled to and nothing is issued twice. Historic records from the previous manual process were migrated so the rule worked from day one.

One-time passcode

OTP-verified collection

Every handover, whether a group request, an individual request or a replacement item, is confirmed with a one-time passcode sent to the recipient. The warehouse gets a simple confirmation step; the organisation gets verifiable proof of delivery.

Returns

Structured discrepancy and returns management

Recipients, or administrators acting on their behalf, can report damaged, missing, wrong-size or wrongly delivered items, with photo evidence where required. The workflow adapts to the report type:

  • Item-level review. Logistics approves or rejects each disputed item; wrong-size exchanges go straight to preparation.
  • Replacement collection with its own passcode, followed by an inspection of the returned items.
  • Automatic SAP corrections. Accepted returns trigger a reversal reservation; rejected ones release the replacement stock.
  • Full traceability. Every decision, remark and status change is recorded, and final sizes are written back to the recipient's record.
Returns and replacements workflow Recipient · Portal automation · Logistics · SAP S/4HANA Auditable

Swipe sideways to see the full diagram, or tap it to open full size.

Arabic & English

Bilingual by design

The portal, its navigation and every notification are delivered in Arabic and English. Requesters, representatives, recipients, logistics staff and administrators are kept informed at each stage through localised email notifications, with an SMS channel integrated and ready to activate.

No IT involvement

Self-service administration

Business administrators manage events, kits, the item catalogue, SAP materials and portal users from within the portal itself, without IT involvement. Creating a new kit automatically populates it with the matching catalogue items, and assigning a role to a user updates their access instantly.

Security

Enterprise-grade security

1

Single sign-on with Microsoft Entra ID. Local passwords are disabled, and external recipients are provisioned automatically through Microsoft Graph when invited.

2

Eight purpose-built roles govern what each user sees and does, from read-only logistics viewers to full administrators.

3

41 record-level permission rules ensure recipients see only their own requests and representatives only their own delegations.

4

Protected secrets and requests. API credentials are held outside the workflows, with secrets in Azure Key Vault, and all portal calls use anti-forgery tokens.

5

Mandatory terms and conditions acceptance before any user can work in the portal.

04 · Architecture

Solution architecture

Microsoft Power Platform + SAP S/4HANA Experience · Data · Process · Integrations Architecture

Experience layer

Microsoft Power Pages portal: 29 web pages, 27 forms and 19 role-filtered lists, with custom Liquid, JavaScript and CSS for stock-aware size selection, OTP dialogs, bulk upload and PDF generation.

Data layer

Microsoft Dataverse with 12 tables covering events, federations, kits, catalogue items, kit and recipient requests, recipient items, SAP stock, discrepancy reports and discrepancy items, on a unified 12-stage status model.

Process layer

30 Power Automate cloud flows for validation, eligibility, approvals, status orchestration, notifications, onboarding and OTP verification.

Integration layer

SAP S/4HANA OData services for stock, reservations, cancellations and reversals; Microsoft Graph for identity provisioning; Office 365 for email; SMS gateway API.

Identity and security

Microsoft Entra ID authentication, web roles, table permissions, Azure Key Vault.

Delivery

Packaged as a single Power Platform solution with environment variables, promoted through development, test and production.

Data Model

Data model

Twelve connected Dataverse tables form the single source of truth.

Dataverse entity relationships Master data · Requests · Returns · SAP stock 12 tables

Swipe sideways to see the full diagram, or tap it to open full size.

Operations

Built to be run, not just launched

1

Self-monitoring automation.

Every flow uses structured error handling and alerts the support team with diagnostics the moment something fails.

2

Configuration over code.

Endpoints, senders, recipients and credentials are environment variables, so deployments between environments need no rework.

3

Operational tooling.

One-click exports of issued items per event or request support reporting and audit.

4

Complete handover.

The platform was delivered with full technical documentation covering every page, form, flow, table and permission.

05 · The Impact

The impact

One platform now carries every kit from request to handover, and back again when something is wrong, with SAP updated at every step.
1

A single source of truth.

Requests, recipients, sizes, stock and status live in one place instead of across inboxes and spreadsheets.

2

No more promising stock that is not there.

Sizes are selected against live SAP availability and reserved on the spot.

3

Manual SAP entry removed from the reservation process.

Reservations, cancellations and reversals are created by the platform, cutting re-keying and the errors that come with it.

4

Entitlement enforced automatically.

The 365-day rule is applied consistently to every recipient, protecting inventory and budget.

5

Accountable handovers.

Every collection is passcode-verified and time-stamped.

6

Returns under control.

Discrepancies follow a time-boxed, auditable process with matching stock corrections in SAP.

7

A better experience for athletes and staff.

Recipients choose their own sizes, track their request and receive updates in their own language.

8

Independence for the business.

Administrators manage events, kits, catalogue and users themselves.

Roadmap

What comes next

The platform was designed to grow. The roadmap agreed with the client includes an embedded Power BI dashboard for live inventory insight, automated SAP goods issue at dispatch, and a dedicated mobile experience for athletes and staff on the move.

Voila Digital

Why us

This project brought together what we do best: understanding a complex operational process, modelling it cleanly on the Microsoft Power Platform, and connecting it to the systems the business already depends on. By building on low-code foundations and extending them with custom engineering where it mattered, we delivered an enterprise-grade, SAP-integrated platform that the client's own team can operate and evolve.

Have a process that still runs
on spreadsheets and email?

Talk to us about turning it into a secure, connected digital platform.