Unico Connect

Built the enterprise data layer connecting the ERP of a healthcare and pharma technology company in Singapore to its ecommerce marketplace

A data management middleware on Xano with supporting services hosted on GCP, sitting between MS Dynamics Business Central and a customer facing ecommerce platform, designed for the integration discipline that pharma operations require.

IndustryHealthcare / Pharma
Country🇸🇬 Singapore
IntegrationERP ↔ marketplace
ResilienceQueue backed

Key Takeaways

A healthcare and pharma technology company in Singapore came to Unico Connect to build the data management layer connecting its MS Dynamics Business Central ERP with its customer facing ecommerce marketplace. We designed and built the middleware on Xano, with compression and queue services hosted on GCP.

It is structured for the operational realities of pharma data, with resilience when the ERP is unavailable, efficient handling of large JSON payloads, and the audit posture pharma compliance requires. The platform now runs as the integration backbone between the two systems.

Customer and pharmacist at a pharmacy counter

The Challenge

The client is a healthcare and pharma technology company in Singapore, serving suppliers and customers through an ecommerce marketplace. The operational backbone runs on an ERP, MS Dynamics Business Central, and the customer facing surface is a separate ecommerce platform. The two systems were not designed to talk to each other directly, and the engineering work needed to make them work together had not been built.

The cost of this gap is significant in pharma. Suppliers and customers transacting on the marketplace need ERP grade data to act on, such as current inventory, accurate pricing, valid customer records and real time order state, but the marketplace was working with stale or incomplete copies. The result was operational pain on both sides. Customers saw inventory that did not match availability, suppliers did not see placed orders, and the operations team reconciled discrepancies that should never have arisen.

01ERP and marketplace did not talk directly
02Stale data drove reconciliation pain
03Pharma compliance and audit duty
04Resilience required when the ERP is down

Pharma data raises the bar further, with large data payloads and regulatory and audit obligations higher than adjacent categories. The team needed ERP to marketplace integration for the MVP with an architecture designed to extend, resilience for ERP downtime, efficient handling of large JSON payloads, and the audit posture pharma compliance requires. They came to Unico Connect specifically for the data middleware, the missing piece between two systems that already existed.

Our Approach

Designing the ERP to marketplace data layer

We engaged as a focused engineering partner, structured around the architecture, the integrations and the operational discipline the data layer would need to carry. The first phase was understanding the actual ERP to marketplace data flows. Every enterprise integration is shaped by the specific quirks of the systems involved, and the gap between them is always more interesting than the architecture diagram suggests.

Key decisions:

01.

Xano as the data management layer

API discipline, a Postgres backed model and operational primitives (Redis cache, REST endpoints), run as separate workspaces on a shared instance to keep ERP facing and marketplace facing flows cleanly separated while controlling cost.


02.

Queue backed resilience on GCP

A managed queue absorbs ERP requests during maintenance windows or outages and delivers them once the ERP returns, rather than dropping data when the back end is down.


03.

Cost aware sizing

Deployment in the Singapore region across Xano and GCP, with a Node.js compression service for the large JSON payloads pharma generates, chosen to stay right for the workload over years of operation.

The solution we built

The architecture sits between the MS Dynamics Business Central ERP of the customer and the existing ecommerce marketplace, with several integrated components doing the actual work. They fetch and serve ERP data, normalise and deliver marketplace data, and keep the system resilient and auditable for pharma operations.

Xano data management layer

Server, Postgres database and REST endpoints through which the marketplace talks to the ERP, with a Redis cache reducing repeated read load on the ERP.


Queue backed resilience

A GCP managed queue absorbs incoming requests when the ERP is unavailable and delivers them once it returns, so the marketplace keeps functioning during back end downtime.


JSON compression service

A Node.js service on GCP compresses the large JSON payloads that ERP to marketplace data produces, keeping storage and transfer costs proportionate to the data volumes.


Audit logging

Request failures and operational events captured with enough fidelity to defend a pharma compliance review, as evidence that things worked and that failures were handled.

Sample pharma data integration dashboard with a pipeline view and a drug name matching table
Sample data integration dashboard on a laptop, showing data sources feeding a unified data layer and a drug name matching panel

Tech stack

Outcomes & impact

Live backbone

ERP to marketplace integration in production

Queue backed

Marketplace stays up when the ERP is unavailable

Singapore

Region deployment across Xano and GCP

Trusted and verified by our clients

Reviewed on53 Reviews
Reviewed on31 Reviews

Have an enterprise data or integration challenge that needs the same kind of lift?

Talk to an Expert

Frequently Asked Questions

Related insights

View All

Let's Build Your Team

Tell us about your systems, the integration work you need and where you want the platform to be in twelve months. We reply within one business day with next steps.

For more information about how we handle your personal information, please visit our privacy policy.