Building one operating view across a complex healthcare supply chain
PT Anugerah Pharmindo Lestari (APL) is one of Indonesia’s largest pharmaceutical distribution companies. It manages healthcare product discounts, customer and principal requests, procurement, inventory movement, and distribution to pharmacies, hospitals, clinics, and other healthcare institutions.
As these operations grew more complex, APL faced a familiar problem: the business had many processes, stakeholders, approval levels, and systems, but not one connected way to manage them. Discount submissions, product requests, procurement, and distribution were often difficult to monitor from end to end.
Suitmedia partnered with APL to develop three connected digital platforms: iDiscount, iPesta, and iJKN. Together, they were designed to make decisions faster, improve visibility, reduce administrative errors, and connect operational workflows with SAP. The goal was not simply to digitize individual tasks, but to create a more coordinated operating model for healthcare distribution.
A growing operation was being slowed by fragmented decisions
1. Discount programs involved too many moving parts
APL manages discount programs for healthcare products and works with multiple principals, each with potentially different commercial requirements and approval structures.
Before iDiscount, the submission and approval process involved several parties and multiple levels of review. A request could require input from commercial teams, principals, managers, and other stakeholders before it was accepted.
When these steps are managed through disconnected tools or informal communication, it becomes difficult to know which requests are waiting, who needs to act, and whether the latest information has been reviewed.
2. Approval status was not visible enough
Limited visibility into ongoing requests created coordination problems. Stakeholders could not always see the current status of a submission without asking another team or checking several sources.
This created delays that were not necessarily caused by poor decision-making. Sometimes the delay came from uncertainty: a person did not know whether a request was still under review, awaiting clarification, or already approved.
For a business managing many products and principals, this uncertainty accumulates. Small delays across multiple requests can affect commercial responsiveness and service quality.
3. Procurement and distribution required a complete view
Product requests did not end when an order was approved. APL also needed to manage procurement and distribution through several operational stages.
These stages could include Purchase Requisition, Purchase Order, Stock Transfer Order, Delivery Order, shipment, and Goods Receipt. If stakeholders could see only one stage at a time, they had limited understanding of where the product was and what needed to happen next.
The absence of end-to-end visibility made it harder to identify bottlenecks and communicate accurate updates to customers, principals, and healthcare facilities.
4. Stakeholders could not always approve work remotely
Some approval processes depended on people being available at the office or connected to a desktop system.
When decision-makers were traveling, working away from the office, or managing several locations, approvals could be delayed even when the information was ready.
This was an operational issue with commercial consequences. A slow approval can affect the timing of procurement, distribution, and service to healthcare customers.
5. Different workflows needed different levels of flexibility
APL’s business processes were not identical. Discount programs varied by principal. Product requests could follow different approval paths. Procurement could involve government systems or direct purchase orders.
A single rigid workflow would not fit these different conditions. The platforms needed configurable rules that could accommodate organizational structures and business variations without requiring a new system for every exception.
6. Manual work increased the risk of errors
When teams copy information between systems, update records manually, or track approvals through separate files, the risk of data entry errors increases.
An incorrect product reference, missing approval, or outdated status can create rework and affect downstream activities. In healthcare distribution, these issues can also affect service reliability.
APL needed a stronger connection between operational systems so that the same information could move through the process with fewer manual handoffs.
7. SAP data needed to remain consistent with operational activity
SAP played an important role in APL’s business operations. But if digital platforms and SAP are not connected properly, employees may work from different versions of the same information.
This creates a difficult question: which record is correct?
The new platforms needed to integrate with SAP so that operational processes could remain connected to the company’s enterprise data. Integration was essential for accuracy, but it also had to be designed around how teams actually made decisions.
8. Auditability was becoming more important
Discount approvals, product requests, procurement, and distribution all require accountability. APL needed to know who submitted a request, who approved it, what changed, and when each decision occurred.
Without a reliable audit trail, reviewing past activity becomes difficult. Teams may need to reconstruct events from emails, spreadsheets, and conversations.
The platforms needed to create a durable record as part of the normal workflow, not as a separate administrative exercise after the transaction was complete.
9. The business needed to scale without adding equal administrative effort
APL’s operations would continue to grow across products, principals, customers, and healthcare facilities.
If every new request required the same amount of manual coordination, the organization would eventually face a capacity problem. More volume would mean more follow-ups, more status checks, and more opportunities for error.
The strategic requirement was to create a system that could handle greater complexity while making the process easier to manage.
Designing three platforms around one connected operating model
1. Start with the work each platform needed to improve
Suitmedia developed three platforms because APL’s processes had different purposes:
- iDiscount for discount submission, approval, monitoring, and reporting.
- iPesta for healthcare product requests, approvals, procurement stages, and distribution tracking.
- iJKN for procurement and distribution processes involving different purchasing channels.
Each platform had its own workflow, but the design principles were shared. Information needed to be visible, approvals needed to be traceable, and system-to-system movement needed to be reliable.
This approach avoided forcing every business process into one generic application while still creating a consistent digital standard across APL.
2. Use iDiscount to centralize commercial requests
iDiscount brought discount submission, approval, monitoring, and reporting into one ecosystem.
Users could create discount proposals based on the relevant principal. This gave APL a structured way to manage proposals that might previously have followed different formats or communication paths.
The platform also helped stakeholders see what had been submitted, which requests were under review, and what required attention. This made the process easier to coordinate across APL and its principals.
3. Make approval workflows configurable
Because principals could have different organizational structures and requirements, iDiscount was designed around flexible approval workflows.
Configurable workflows allowed APL to adapt the path of a request according to the relevant business context. This was more sustainable than creating separate tools or manually handling exceptions outside the system.
The broader value was governance with flexibility. APL could maintain control over the process without making every request follow an unnecessarily rigid path.
4. Use dashboards to make decisions visible
iDiscount included an interactive dashboard showing discount requests and approval status.
A dashboard gave users a common view of activity. Instead of relying on individual records or asking colleagues for updates, stakeholders could see the state of requests directly.
This supported faster coordination. Managers could identify pending items, while operational users could prioritize the work requiring action.
5. Use notifications to keep requests moving
Real-time notifications helped stakeholders stay informed about new submissions, approvals, or actions required.
Notifications reduced dependence on manual follow-up. They also made the platform more responsive because users were alerted closer to the moment an event occurred.
This was especially valuable for multi-level approvals. When the next reviewer was notified promptly, the process was less likely to pause simply because a task was not visible.
6. Connect iDiscount with SAP
iDiscount was integrated with SAP to support data synchronization and reduce manual processes.
This helped align discount-related activity with APL’s enterprise data. The integration also reduced the need for users to enter or reconcile the same information in several places.
The design principle was to let each system perform the role it was best suited for while creating a more consistent flow between them.
7. Use iPesta to connect product requests with fulfillment
iPesta was designed to centralize healthcare product requests, approvals, enterprise system integration, and distribution tracking.
The platform included a website for daily operations and a mobile application for approval activities. This division reflected the needs of different users: operational teams required a detailed working environment, while approvers needed flexibility to review and act from mobile devices.
Together, the two access points created a more complete workflow without forcing every user into the same interface.
8. Give iPesta a clear request and approval structure
iPesta included an interactive dashboard, request module, multi-level approval workflows, and real-time notifications.
These features helped users understand where a product request stood and what needed to happen next. A requester could see progress, while approvers could review assigned decisions without relying on informal communication.
The result was greater transparency across the request lifecycle. Stakeholders could work from the same status information rather than maintaining separate personal records.
9. Track the full product movement journey
One of iPesta’s most important capabilities was end-to-end tracking across:
- Purchase Requisition, or PR.
- Purchase Order, or PO.
- Stock Transfer Order, or STO.
- Delivery Order, or DO.
- Shipment.
- Goods Receipt, or GR.
This sequence connected commercial approval with physical product movement. Users could understand not only whether a request had been approved, but also how far it had progressed toward delivery.
End-to-end visibility supports better communication. APL could provide more accurate updates to customers, principals, and healthcare facilities instead of relying on partial information from one stage.
10. Use mobile approval to reduce location-based delays
The iPesta mobile application allowed stakeholders to participate in approval processes while away from the office.
This improved decision speed by making approvals less dependent on access to a desktop environment. It also supported managers and decision-makers whose responsibilities required them to move between locations.
Mobile access was not simply a convenience feature. It helped remove a specific operational constraint that had been slowing down decisions.
11. Use iJKN to modernize procurement workflows
iJKN was developed to connect procurement workflows within one digital ecosystem.
The platform supported different procurement processes, including government systems and direct purchase orders. This flexibility was important because APL’s procurement work did not follow one uniform route.
By bringing these processes into a centralized environment, iJKN helped reduce fragmented tracking and improve coordination among the stakeholders involved.
12. Automate procurement data management
iJKN digitized manual processes and automated relevant data management activities.
Automation reduced the amount of repeated administrative work and helped make updates more consistent. It also improved the speed at which information could move between procurement and distribution activities.
The objective was not to remove human judgment from procurement. It was to ensure that people spent less time handling routine data and more time managing exceptions and decisions.
13. Create real-time procurement and distribution visibility
iJKN provided monitoring across procurement and distribution activities.
This helped stakeholders understand the current state of work and identify where attention was needed. It also supported more reliable coordination between teams responsible for purchasing, inventory, delivery, and receipt.
Visibility was especially important for healthcare products, where delays can affect facilities and patients further along the supply chain.
14. Preserve a clear audit trail
iJKN included audit trail capabilities to record key activity throughout the procurement process.
This strengthened accountability. APL could review who performed an action, when it occurred, and how the transaction progressed through the system.
An audit trail also supports organizational learning. By reviewing patterns in delays, approvals, or exceptions, APL can identify where the process can be improved.
15. Use automated notifications across the platforms
Notifications helped users remain informed about requests, approvals, status changes, and required actions.
This created a more active workflow. Users did not need to continuously check multiple systems to discover whether something had changed.
The value of notifications depended on good process design. Alerts needed to direct users toward meaningful action rather than create unnecessary noise.
16. Make the platforms accessible through web and mobile
The platforms were designed to support access through websites and mobile applications.
This enabled different users to work in the way most appropriate to their roles. Detailed operational work could be managed on the web, while approvals and time-sensitive decisions could be handled through mobile access.
The broader result was greater flexibility without sacrificing a shared process.
17. Use a common design language across the ecosystem
Suitmedia applied consistent user experience principles across iDiscount, iPesta, and iJKN.
This helped reduce the learning effort for users who interacted with more than one platform. Familiar layouts, navigation patterns, dashboards, and status indicators made the overall digital ecosystem easier to understand.
Consistency also strengthened APL’s digital identity. The platforms felt like parts of one operating environment rather than unrelated tools.
A connected set of platforms improved control across the operation
1. APL gained clearer control over discount programs
iDiscount centralized submission, approval, monitoring, and reporting for discount activities.
This improved visibility for APL and its principals. Stakeholders could understand the status of proposals and work through a more consistent approval process.
The platform also reduced dependence on manual tracking, creating more reliable commercial coordination.
2. Approval decisions became faster and more transparent
Configurable workflows, dashboards, notifications, and mobile access helped reduce avoidable waiting.
Approvers could see what required action, while requesters could monitor progress more clearly. The process became easier to follow and less dependent on repeated status inquiries.
Transparency also strengthened confidence. Stakeholders could understand how decisions were progressing rather than relying on assumptions.
3. Product requests became easier to monitor from start to finish
iPesta connected request creation, approval, procurement, and distribution tracking.
This gave APL a more complete view of how a product request moved through the business. Users could identify the stage reached and determine whether the next action was internal, supplier-related, or connected to delivery.
The result was stronger coordination across functions that had previously been easier to manage in isolation than as one chain.
4. Distribution information became more useful
Tracking from PR through GR gave stakeholders a clearer understanding of product movement.
This helped APL communicate more accurately with customers, principals, and healthcare facilities. It also made it easier to identify delays before they became larger service problems.
The second-order effect was greater operational resilience. The business could respond to exceptions with better information and less guesswork.
5. Procurement became more centralized and accountable
iJKN created a shared environment for different procurement routes and distribution activities.
This improved the organization’s ability to monitor transactions and maintain a reliable record of decisions. Different purchasing channels could be managed within one broader framework rather than through disconnected processes.
The platform supported both efficiency and governance. Procurement could move faster while remaining easier to review.
6. SAP integration improved data consistency
Integration across the platforms and SAP helped reduce repeated manual data entry and maintain greater alignment between systems.
This improved the reliability of operational information. Teams could make decisions with greater confidence that the data reflected the current state of the transaction.
Consistent data also reduced the need to reconcile conflicting records later.
7. APL improved cross-functional collaboration
The platforms connected commercial, procurement, quality, distribution, approval, and management activities.
Teams could work from shared records and status information, reducing the need to resolve basic differences between departments.
This supported a more coordinated operating culture. Each team could see its role in the wider transaction rather than treating its activity as an isolated task.
8. The platforms supported more consistent compliance
Configurable approval rules, audit trails, document histories, and centralized monitoring helped APL apply stronger control across its workflows.
Compliance became part of the system rather than something managed only through individual discipline or retrospective review.
This did not eliminate the need for oversight. It gave oversight better information and a more reliable operating record.
9. APL reduced administrative risk
The combination of automation, standardization, integration, and notifications reduced opportunities for errors caused by manual handling.
Users were less dependent on spreadsheets, personal files, email chains, and repeated data entry. This improved the integrity of the process and reduced the effort required to correct mistakes.
The benefit was especially important in a healthcare supply chain where operational errors can affect multiple downstream parties.
10. The ecosystem was built to scale
iDiscount, iPesta, and iJKN created a reusable digital foundation for APL’s growing operations.
The platforms could support additional principals, products, workflows, users, and procurement scenarios without requiring the organization to rebuild its operating model from the beginning.
This improved APL’s ability to grow while maintaining process discipline.
11. Decision-making became less dependent on physical location
Mobile approval capabilities allowed authorized stakeholders to act while away from the office.
This reduced one of the hidden constraints in the former process: decisions could be delayed simply because the right person was not physically available at the right time.
More flexible access helped APL maintain operational momentum without weakening approval controls.
12. The organization gained better information for future improvement
Centralized activity, status, and audit information created a stronger basis for analyzing operational performance.
APL could identify recurring delays, bottlenecks, and exception patterns across discount, request, procurement, and distribution workflows.
This turned the platforms into more than transaction tools. They became sources of insight for continuous process improvement.
The deeper lesson: complex operations need connected visibility
1. Separate platforms should still feel like one operating system
Different business processes may need different applications. The critical requirement is that users should not experience unnecessary fragmentation.
Shared design principles, integrated data, and consistent status logic help create one operating experience even when several platforms remain in place.
2. End-to-end tracking changes the quality of decisions
Knowing that an order exists is not enough. Teams need to know where it is, what has happened, and what should happen next.
Tracking the full journey from request to receipt allows organizations to act earlier and communicate more accurately.
3. Workflow flexibility and control can coexist
APL’s processes varied across principals and procurement channels. Configurable approval flows allowed the platforms to reflect these differences without abandoning governance.
The lesson is to standardize the principles—visibility, accountability, auditability—while allowing the workflow to adapt to legitimate business variation.
4. Mobile access is a productivity decision
When approvals depend on physical presence, organizational speed is constrained by location.
Mobile capabilities can remove that constraint while preserving authorization and audit rules. Access should be flexible, but decisions should remain controlled.
5. Integration improves more than efficiency
Connecting systems reduces repeated entry, but its deeper value is better coordination. When teams work from consistent information, they can make decisions faster and resolve issues earlier.
Integration is therefore a business design decision, not only an engineering task.
6. Notifications should be tied to responsibility
Alerts are useful when they tell the right person what requires action. Too many poorly designed notifications can create noise and reduce attention.
The strongest systems connect each notification to a clear owner, event, and next step.
7. Auditability protects both the company and its partners
A reliable record of submissions, approvals, procurement, and distribution helps APL demonstrate accountability.
It also protects teams by making decisions and responsibilities visible. Good audit trails support trust rather than functioning only as a compliance burden.
8. Digital ecosystems create value when they improve flow
The purpose of iDiscount, iPesta, and iJKN was not to create more software. It was to help information, decisions, products, and responsibilities move through APL with less friction.
That is the core test of digital transformation: whether the organization can operate with greater clarity, speed, and control.
Strategic Insights for the C-Suite
- Connect the full transaction lifecycle, not just individual tasks. Visibility from submission through approval, procurement, delivery, and receipt helps leaders identify bottlenecks and act before delays affect customers.
- Use separate platforms where business needs differ, but design them as one ecosystem. Shared data, navigation principles, status logic, and governance can prevent users from experiencing unnecessary fragmentation.
- Make approval flexible without making it uncontrolled. Configurable workflows can reflect different principals and procurement routes while preserving clear authorization, auditability, and accountability.
- Give decision-makers secure access wherever work happens. Mobile approval can reduce delays caused by location, provided that roles, permissions, and records remain properly controlled.
- Build digital operations as a source of continuous improvement. Centralized workflows generate information about delays, exceptions, and demand. Use that information to improve processes, not only to monitor them.
