Creating one dependable path from order request to approval
PT Anugerah Pharmindo Lestari (APL) distributes pharmaceutical products to pharmacies, hospitals, clinics, and other healthcare institutions across Indonesia. In this environment, purchase orders are more than administrative documents. They connect customer demand, regulatory checks, inventory planning, internal approvals, and fulfillment.
Before this project, APL’s purchase order process depended heavily on paper documents, PDF attachments, email, messaging applications, and separate business systems. That made it difficult to track order status, preserve a complete history, and maintain one consistent view of transactions.
Suitmedia partnered with APL to develop the e-PO BRQA Portal, a centralized web platform for purchase order management and approval. The system was designed to replace fragmented manual workflows with a secure, traceable, and scalable process that could connect multiple order sources and support APL’s paperless transformation.
A complex order network was creating avoidable operational risk
1. Purchase orders were moving through too many disconnected channels
APL received purchase orders and approval requests from several sources, including eZRx+, Call Center, iDiscount, iJKN, and B2B/RPA systems. Each platform had its own workflow, data structure, and approval mechanism.
This meant that the Branch Regulatory Quality Assurance team, or BRQA, had to review orders arriving through different channels and manage them through processes that were not fully connected.
The operational challenge was not simply the number of systems. It was the lack of one shared view. Without centralized information, employees had to spend more time locating, comparing, and validating order details before a decision could be made.
2. Manual documents made status difficult to follow
Purchase orders were often shared as physical documents or PDF files through email and messaging applications. Once an order entered this flow, it could be difficult to determine its current status.
Employees might need to search through email threads, chat histories, folders, or personal records to understand whether an order had been submitted, reviewed, approved, returned, or completed.
This slowed the process and created uncertainty for everyone involved. A missing update could be mistaken for a delayed approval, while an outdated attachment could be confused with the latest version.
3. The process created a higher risk of document loss
Physical documents can be misplaced, damaged, or separated from the context in which they were created. Digital files sent through informal channels can also become difficult to retrieve when they are stored across multiple inboxes and conversations.
For a pharmaceutical distributor, this creates a serious operational concern. Purchase orders need to remain accessible and traceable because they support financial, regulatory, and fulfillment processes.
APL needed a system that preserved the order record and related documents in one controlled environment. The objective was not only to remove paper, but to protect the integrity of the information throughout its lifecycle.
4. Document formats were not standardized
When purchase orders are created or shared through different tools, the format and level of detail may vary.
Non-standard documents increase the work required to review them. BRQA staff may need to interpret different layouts, look for missing information, or request clarification before an order can proceed.
A centralized system could create greater consistency by providing a standard process for submitting, reviewing, and approving purchase orders.
5. Administrative records were still being managed manually
Even when purchase orders existed in digital form, supporting records and approval details still required manual handling.
This created repeated work for the teams responsible for monitoring transactions. They had to update records, check history, and reconcile information across systems.
Manual administration also creates the risk of inconsistent records. If one update is missed or entered incorrectly, the status shown in one place may not match the actual state of the order.
6. The BRQA team needed to review orders from multiple sources
BRQA was responsible for verifying and approving orders from different platforms. Its work required accuracy and consistency, but the existing process made it difficult to manage all orders through one workflow.
A team may be able to manage a fragmented process when order volume is limited. As the business grows, however, the effort required to monitor different sources increases quickly.
APL needed to give BRQA one portal where orders could be reviewed according to a consistent process, regardless of where the original request came from.
7. Data integration was limiting operational efficiency
The systems generating purchase orders were not fully integrated. This created gaps in the flow of information and increased the possibility of duplicated or inconsistent data.
When systems do not exchange information reliably, employees become the bridge between them. They may need to copy data, verify details manually, or follow up when one system has not been updated.
This reduces operational speed and takes attention away from decisions that require professional judgment.
8. Approval needed to be controlled and auditable
Purchase order approval is not only a workflow step. It is also a record of who reviewed the order, what decision was made, and when that decision occurred.
APL needed a system that could preserve this history through a reliable audit trail. Without it, the organization would have more difficulty reviewing past decisions, investigating exceptions, or demonstrating that the correct authorization process had been followed.
The platform had to make approval easier while also making accountability clearer.
9. The system needed to support future growth
APL’s objective was not to digitize one temporary process. It wanted a platform that could support a broader paperless culture and continue to work as business needs changed.
The system needed to be secure, scalable, and flexible enough to connect with internal and third-party platforms. It also needed to support new authorization rules, document requirements, and operational scenarios over time.
This made the project a foundation for process maturity, not only a replacement for email and paper.
Designing a centralized system around control, speed, and traceability
1. Start with the existing business process
Suitmedia began with comprehensive requirement gathering and an in-depth analysis of APL’s current purchase order processes.
The purpose was to understand how orders were created, where they originated, which teams reviewed them, what approvals were required, and where information was lost or delayed.
This prevented the team from simply digitizing the existing paperwork. The process analysis helped distinguish between steps that were necessary for control and steps that existed only because the old system was fragmented.
2. Map the integration requirements before building
The project required connections with multiple internal and third-party platforms, including SAP.
Suitmedia analyzed how data moved between these systems and what the e-PO portal needed to receive, validate, store, or return. This helped define the boundaries of the new platform and reduce the risk of building features that could not operate reliably with the existing technology landscape.
Integration planning was critical because the portal needed to become a central workflow without disrupting the systems that generated order data.
3. Design the architecture around one shared record
The e-PO BRQA Portal was designed as a centralized place for purchase order management and approval.
A shared record allowed APL to bring together order information from different sources and present it through one operational view. BRQA users could review orders in a consistent environment rather than switching between platforms.
Centralization also improved history. The organization could connect an order with its supporting documents, status changes, approval decisions, and related actions.
4. Use process flows to clarify responsibility
Suitmedia translated the business requirements into process flows showing how orders moved through submission, verification, approval, return, and completion.
These flows helped clarify which users were responsible for each stage and what should happen when an order required correction or additional information.
Clear process logic reduced ambiguity. Employees could understand what was expected of them and how their actions affected the next stage of the order.
5. Use wireframes to test the operational experience early
Wireframes were created as a foundation for development.
They allowed APL stakeholders and the project team to review the portal’s screens, navigation, and key actions before full implementation. This created an opportunity to identify confusing labels, missing information, or inefficient steps while changes were still easier to make.
The value of wireframing was not limited to interface design. It also helped stakeholders align on how the new process should work in practice.
6. Build the backend with .NET
The backend system was developed using .NET to support the portal’s requirements for security, reliability, and scalability.
The platform needed to manage complex business processes, integrate with other systems, store records, control access, and support future development.
The technology choice provided a structured foundation for those needs. More importantly, the backend architecture was connected to the operational purpose of the portal: make purchase order management more dependable at scale.
7. Integrate with SAP and other source platforms
API integrations connected the portal with SAP and relevant third-party platforms.
These integrations reduced the need for manual re-entry and helped bring order information into the centralized workflow. They also supported more reliable data exchange between the systems involved in purchasing and approval.
The objective was not to replace every existing platform. It was to make the relationship between those platforms more coordinated and transparent.
8. Use automated jobs for recurring system tasks
Automated processes through cron jobs were included to handle recurring activities within the system.
Automation can reduce the need for employees to perform routine updates manually. It also creates more predictable timing for tasks that need to occur regularly, such as synchronization, status updates, or scheduled processing.
This improved operational velocity while reducing the risk that a necessary administrative step would be forgotten.
9. Preserve a complete audit trail
Audit trail capabilities recorded important activity within the purchase order process.
This included the actions and status changes needed to understand how an order progressed through the workflow. A complete record made it easier to review decisions and identify where delays or exceptions occurred.
For BRQA and APL leadership, the audit trail strengthened accountability. Users could see not only the current status of an order, but also how it reached that status.
10. Add configurable authorization rules
The platform included a configurable authorization matrix.
This allowed APL to define who could review, approve, return, or manage different types of orders. Authorization could be structured around business rules rather than informal knowledge or manual routing.
Configurability was important because approval requirements can change. A system that requires code changes for every authorization update becomes slow to manage and difficult to adapt.
11. Use notifications to keep work moving
Email notifications were included to alert relevant users when action was required or when the status of an order changed.
Notifications reduced the need for BRQA staff or other users to repeatedly check for updates manually. They also helped make responsibilities more visible by directing attention to the next step.
The value of a notification depends on the workflow behind it. By connecting messages to specific order events, the system could make communication more timely and relevant.
12. Centralize document management
The portal included document management to keep purchase order files and supporting records connected to the relevant transaction.
This reduced the risk of documents being separated from the order they supported. It also made it easier for authorized users to find the information needed during review or audit.
Centralized document handling strengthened both efficiency and control. Users spent less time searching, while APL gained greater confidence that important records would remain available.
13. Create a consistent review experience for BRQA
The portal was designed around BRQA’s need to verify and approve orders from several sources.
A consistent review experience helped the team apply the same logic across orders, regardless of their origin. It reduced the need to learn a different workflow for every upstream platform.
This supported better focus. BRQA could spend more time reviewing the substance and compliance of orders and less time managing the mechanics of fragmented submission channels.
14. Design for responsive access
The e-PO BRQA Portal was developed as a responsive web platform.
This allowed users to access the system across different screen sizes and working contexts. Responsive design supported broader usability without requiring separate applications for every device.
For an operational system, flexibility can improve adoption. Users are more likely to update and review tasks when the portal fits the way they work.
15. Build security into the process
Purchase orders may contain commercial and customer-related information. Approval decisions also require controlled access.
The platform’s authorization matrix, structured user access, and centralized records helped create a more secure environment than informal document sharing through email or messaging applications.
Security was treated as part of operational design. The goal was to protect data while keeping the workflow practical for authorized users.
16. Validate the system against business requirements
The implementation process required coordination between APL stakeholders, BRQA users, technical teams, and connected systems.
Testing and review helped confirm that data integrations, approval rules, document handling, notifications, and status tracking worked together as intended.
This was important because failures in one part of the process could affect the entire purchase order journey. A portal may appear complete while still creating delays if integration or authorization logic is not reliable.
One portal made purchase order management more consistent and accountable
1. APL moved away from a primarily manual approval process
The e-PO BRQA Portal digitized the purchase order approval workflow that had previously relied on physical documents, PDFs, email, and messaging applications.
This created a more structured way to manage submissions, review, approval, and record keeping.
The shift reduced dependence on informal communication and gave APL a more dependable operational foundation.
2. BRQA gained a centralized view of orders
Orders from different sources could be brought into one portal for review and approval.
This made it easier for BRQA to manage its responsibilities without switching continuously between systems. A single view also reduced the risk that an order would be missed because it arrived through an unfamiliar channel.
Centralization improved visibility across the workflow and supported more consistent review.
3. Order status became easier to track
The portal provided a clearer way to monitor where each purchase order stood.
Users could distinguish between newly submitted, pending, returned, approved, or otherwise active orders according to the workflow configured by APL.
This reduced the need to search through messages or ask other teams for updates. Better status visibility helped employees focus on the orders that required attention.
4. Purchase order history became more reliable
The system preserved transaction and approval history in a structured form.
This gave APL a stronger record of past actions and decisions. Users could review what happened without reconstructing the order from scattered documents.
A reliable history also supported audits, internal reviews, dispute resolution, and operational learning.
5. Document loss risk was reduced
Centralized document management kept order files and supporting evidence within the system.
This reduced the possibility that a document would be misplaced, damaged, or separated from its related transaction.
The improvement supported continuity. Even when the original employee was unavailable, authorized users could access the relevant records through the portal.
6. Standardization improved review quality
The portal created a more consistent format and workflow for purchase orders.
Standardization reduced the effort required to interpret different document styles and helped users identify missing information more quickly.
It also created a stronger basis for comparison. APL could assess orders through a more uniform process rather than adapting to each source’s individual format.
7. Approvals became more transparent
The configurable authorization matrix and audit trail helped clarify who was responsible for each approval step.
This strengthened accountability and reduced ambiguity. Users could understand why an order was waiting and which role needed to act.
Transparency also supports better governance. Managers can review the flow of approvals and identify bottlenecks or recurring exceptions.
8. Notifications helped reduce avoidable delays
Email notifications made users more aware when a purchase order required action or had changed status.
This helped reduce the risk that tasks would remain inactive simply because the responsible person did not know an update had occurred.
More timely attention improved the movement of work through the system and reduced dependence on manual reminders.
9. Integration reduced repeated data entry
Connections with SAP and other systems helped reduce the need to manually copy order information between platforms.
This improved efficiency and reduced the risk of transcription errors. Employees could focus more on review and decision-making instead of repetitive administrative work.
The benefit was cumulative. Every avoided manual entry reduced effort and improved the consistency of the data moving through the process.
10. APL strengthened its paperless operating model
The portal supported APL’s goal of reducing dependency on physical documents and manual archiving.
A paperless process improved accessibility, reduced storage requirements, and made records easier to retrieve when needed.
The change also supported a broader cultural shift. Digital workflows became the normal way to manage purchase order activity rather than an optional alternative.
11. The system could scale with business needs
The e-PO BRQA Portal was designed to be secure, reliable, and scalable.
This gave APL a foundation that could support additional order sources, new approval rules, and future process improvements as the business evolved.
Scalability protected the initial investment. APL could expand the system rather than replace it when operational requirements changed.
12. Management gained stronger operational visibility
With centralized status, documents, approvals, and history, APL could better understand how purchase orders moved through the organization.
This visibility could help identify delays, recurring issues, and opportunities for process improvement.
The result was a shift from managing isolated transactions to managing the health of the overall workflow.
13. The platform improved coordination across teams
Purchase order management involved multiple parties, including customers, source systems, BRQA, approvers, and operational teams.
The portal gave these groups a shared process and common information source. This reduced the need to resolve basic differences between records and helped teams work from the same view.
Better coordination strengthened the reliability of the end-to-end order process.
14. APL gained a stronger foundation for future automation
Once purchase orders were centralized and structured, APL could consider further automation and analysis.
Future opportunities may include more advanced routing, exception detection, performance dashboards, or integration with additional business systems.
The current project created the data and workflow foundation required for those improvements. Digital transformation could continue from a more stable starting point.
The deeper lesson: operational efficiency begins with one trustworthy record
1. Digital transformation should remove handoffs, not only paper
Replacing paper with PDFs does not solve fragmentation if employees still move documents manually between email, messaging apps, and business systems.
The e-PO portal created value by connecting the workflow, not simply changing the file format. It reduced the number of uncontrolled handoffs between submission, review, approval, and archiving.
2. Integration is most valuable when it supports a decision
Data integration should not be pursued only because systems can be connected. It matters when it helps employees make faster, more accurate decisions.
For BRQA, bringing orders into one portal made verification and approval easier. The integration was valuable because it improved the work that followed.
3. Auditability should be built into everyday operations
An audit trail is more reliable when it is generated automatically as people use the system.
This is stronger than reconstructing evidence later from emails and files. Everyday process design can create a more complete and trustworthy record without adding a separate burden at audit time.
4. Standardization creates speed and control together
Standard formats and approval rules reduce interpretation effort, but they also strengthen governance.
The key is to standardize the parts of the process that need consistency while keeping enough flexibility for legitimate business differences.
5. Configurable systems protect future agility
Authorization rules, notifications, and document requirements may change as the organization evolves.
A configurable platform allows APL to respond without waiting for major redevelopment. This supports operational speed and reduces the cost of change.
6. Centralization should improve visibility without creating a bottleneck
A single portal can become a powerful source of truth, but it must be designed to support the people who use it.
The system should make work easier to route, review, and complete. Centralization creates value when it improves flow, not when it simply moves all activity into one crowded location.
7. Data quality is part of business performance
Inaccurate, incomplete, or duplicated order data can create delays and weaken decisions.
A connected e-PO process improves data quality by reducing repeated entry and standardizing how information is recorded. Better data supports better operations.
8. Paperless work is a cultural change as well as a system change
Employees may continue using old channels if the new platform is difficult or if the organization does not clearly establish it as the source of truth.
Adoption depends on usability, governance, training, and consistent expectations. A digital workflow becomes sustainable when the organization treats it as the normal way of working.
Strategic Insights for the C-Suite
- Create one trusted record for high-value operational processes. When documents, status, approvals, and history are scattered, efficiency and accountability suffer. A centralized workflow can improve both speed and control.
- Integrate systems around decisions, not technology for its own sake. The value of SAP and third-party connections lies in helping teams review, approve, and act with better information. Integration should reduce manual interpretation and re-entry.
- Build auditability into daily work. Automatic histories, approval records, and document trails are more reliable than reconstructing evidence after the fact. Good governance should be a normal outcome of the process.
- Make approval structures configurable. Businesses change, and authorization rules change with them. Systems that can adapt without major redevelopment protect operational agility and reduce long-term cost.
- Measure transformation by the work it removes. A successful paperless process does more than eliminate documents. It reduces searching, repeated entry, manual follow-up, uncertainty, and avoidable delays—giving skilled teams more time for judgment.
