The situation
Saudi Arabia operates one of the more demanding pharmaceutical track and trace regimes in the world. The Saudi Food and Drug Authority requires full end-to-end traceability for every medicine on the market, managed through the national Drug Track and Trace System. No movement through the supply chain goes unreported. Every pack must be serialised. For a European manufacturer with registered products in the country, this is not a future requirement to plan around. It is the condition for staying on the market.
A leading European medical device manufacturer distributing from a single warehouse in Saudi Arabia needed to bring its KSA operations into full compliance. Product moved from a production site to the in-country warehouse and then into the Saudi distribution network. Every step of that journey, from import through to final sale, had to be serialised and reported to the SFDA.
There was no existing process to build on. This was a greenfield engagement from the first conversation, running in parallel with the same client's broader European rollout programme, which Amalia was also managing.
Amalia was brought in as the team that would make it happen.
What was at stake
The timeline pressure was specific and unforgiving. Saudi Arabia allows only a short transition window after a product is registered before reporting to the national system becomes mandatory. Technical implementation and regulatory onboarding must both be complete before that window closes. Missing it does not mean a delayed go-live. It means non-compliance on a registered product, with the market access consequences that follow.
The client had to register products against a deadline. What they did not have was a process, a system configuration or a live regulatory connection.
What the engagement needed to be
On paper, the brief was to get TraceLink running for Saudi Arabia. The actual job was simpler to state and harder to deliver: the client needed to sell medicine in the Saudi market without interruption. The system was one part of making that possible. It was not the job itself.
Getting there required two things that were tightly interdependent. The first was process design. A greenfield implementation in a full track and trace country means there is no existing operational workflow to configure against.The KSA operation covered a range of transaction types, each carrying distinct reporting requirements under the SFDA framework: imports, domestic sales, procurement from local distributors, free sample distribution and returns.Before any configuration work could begin, each scenario had to be understood, documented and mapped to the regulatory events the national system expected to receive. That mapping is not a configuration task. It is a compliance exercise, and it requires holding the operational reality and the regulatory framework in view simultaneously.
The second was connectivity. Building and testing the interface to the Saudi national system meant working with a relatively recent regulatory platform. Documentation does not always reflect actual interface behaviour in systems that are still maturing. The only reliable way to build confidence in the connection was structured, iterative testing.
Both workstreams depended on each other. The interface could not be tested without defined processes behind it. The processes could not be finalised without knowing what the regulatory system expected to receive. In practice, that kind of interdependency, when handled by separate partners or siloed internal teams, produces delays at every handoff. A compliance team finishes its process design and passes it to a technical team that finds gaps.The technical team builds a configuration and passes it back for review. Weeks disappear between steps that could have been resolved in a conversation.
Amalia brought the full team to this engagement: project managers, CSA specialists and technical consultants working as a single unit rather than in sequence. When a process design decision had technical implications, the technical consultant was present. When a configuration choice raised a compliance question, the CSA specialist was already knowledgeable about the context. That proximity is not a soft benefit. On an engagement with a fixed registration deadline and two interdependent workstreams, this is what makes the timeline achievable.
The approach
Amalia started with the process work because there was no alternative.System configuration built on poorly defined processes produces a technically functional platform and operationally unreliable outcomes. Each transaction type was mapped in full: what triggers a serialisation event, what data the national system expects at each step, how the event should be reflected in the configuration and what the warehouse team would need to do in practice. The scope covered the full range of scenarios the Saudi operation would encounter, not just the straightforward import and sale path but the less frequent transaction types that are just as likely to generate compliance exposure if they are not handled correctly from the start.
With the process design confirmed, Amalia built the system configuration to reflect it and began developing the interface for the SFDA's national platform. Working with a regulatory system that is still evolving requires a different approach than integrating with a stable, well-documented target. One of the earliest challenges was simply getting a test environment in place. Standing up the test system required going through the platform's support channel, and that process moved slowly. Response times were unpredictable, and the available guidance did not always address what was needed. Amalia stayed with it, escalating where possible and working around gaps in the available support until the test environment was operational. Time spent here is invisible in the final deliverable, but it is one of the more reliable ways to lose weeks on an engagement with a fixed end date.
From there, Amalia approached the integration as structured discovery rather than a routine connectivity task. Building an accurate picture of the interface behaviour through systematic test cycles, rather than assuming alignment with published specifications, kept the subsequent testing phase on schedule and avoided late-stage surprises.
The regulatory acceptance cycle with the SFDA ran in parallel with the technical work. Amalia managed coordination with the authority, tracked each testing requirement through to sign-off, and kept the process moving at the pace required by the deadline. Regulatory onboarding in markets with active enforcement reflects the authority's own priorities and timelines. Keeping it on track required sustained engagement rather than periodic check-ins.
Documentation was built in parallel rather than assembled retrospectively at the end. SOPs for each operational scenario, interface specifications for the regulatory connections and the process documentation the local team would need to run the system independently after handover. Producing this as the work progressed, rather than as a closing deliverable, meant the handover was functional from day one, not a pile of documents to work through.
The engagement also ran concurrently with the same client's European serialisation rollout. Amalia held both programmes simultaneously, which required clear oversight of their dependencies, particularly at the production site where they converged. Managing that without one workstream blocking the other was a programme management challenge that sat alongside the technical and regulatory work throughout.
The outcome
The Saudi warehouse went live with full regulatory reporting operational within the product registration window. Import, warehousing and distribution processes ran as designed from the start. Serialisation events were reported to the SFDA at each required step without a gap.
The client entered the Saudi market compliantly and with the processes and documentation in place to sustain it. The local team could operate the system without ongoing external support.
What this illustrates
Entering a full track and trace market is a different undertaking from adding a country within an established framework. The regulatory systems are different, the interfaces require their own discovery work and the authorities run their onboarding processes on their own timelines. Companies that treat country compliance as a standard configuration exercise tend to encounter the real complexity during testing, at the point in the programme where timelines have the least capacity to absorb it.
The process design is not preparatory work for the real implementation.It is the real work. A serialisation system reflects the operational processes built into it. If those processes are incomplete, or if edge-case transaction types have not been considered, the gaps surface in production, not in testing.Getting the process design right in a market a client is entering for the first time, under a regulatory framework that enforces precision, determines whether the technical implementation actually holds up under operating conditions.
What made this possible was not any single capability but the combination of them, held by a team that moved as one. Process design, technical build, regulatory coordination, and programme oversight did not operate as separate workstreams reporting to a project manager. They ran together, with the people doing the work in direct contact throughout. In a market entry with a compliance deadline that does not move, that is the difference between an engagement that lands on time and one that is still resolving issues after the window has closed.
If your organisation is preparing to enter or expand in a market with full track and trace requirements, Amalia's TraceLink practice works with manufacturers and distributors on regulatory connectivity and in-market process design. Learn more about Amalia's TraceLink services and Country Compliance.
