Galaxy DigiLabsTechnology Solutions & Digital Systems

Case Study

Ecommerce & Retail2024

Ecommerce Orders That Stop Creating Manual Work

Orders arrived from multiple channels and were re-typed into the ERP, then handled through WhatsApp. We connected the storefront, the ERP and the operations channel so one order flows through the whole chain.

A multi-channel retail business

Outcome

Orders move from storefront to fulfillment without re-entry. Inventory stays aligned between the shop and the ERP, and order communication happens from inside the system.

Problem

Every online order had to be re-entered into the ERP by hand, then confirmed to the customer over WhatsApp. Stock levels drifted between the shop and the ERP, and nobody could say the true position of an order.

Business Context

The business sells across multiple channels and processes payments including COD. Speed of confirmation and accurate stock are direct drivers of customer trust and fewer failed fulfillments.

Constraints

  • The storefront and the ERP were both working — the problem was between them.
  • COD handling had to stay intact end to end.
  • The team is small; the system had to do the orchestration, not them.

Analysis

Following one order from checkout to dispatch showed three manual hand-offs: entry into the ERP, stock adjustment, and customer confirmation. Each hand-off created a delay and a chance for divergence.

Architecture

An integration layer watches new orders in the storefront, creates the ERP record, reserves stock, and triggers a WhatsApp confirmation. Status changes flow back in both directions with logging and retries.

Solution

A single order pipeline from storefront to fulfillment: no re-entry, synchronized inventory, and automatic customer communication at defined order states.

Technology

  • WooCommerce webhooks
  • ERPNext order and stock APIs
  • Frappe integration layer
  • WhatsApp Business API
  • Queue with retry

Implementation

The storefront-to-ERP sync was built and validated with test orders first, then inventory sync, then the customer communication layer. Each stage was measured before the next.

Challenges

Order edge cases — cancellations, out-of-stock at fulfillment time, and COD failures — needed explicit handling in the pipeline rather than being left to the operations team to catch manually.

Outcome

The manual re-entry is removed, stock reporting reflects both systems, and customers receive confirmations that come from live order state instead of a person typing the same data twice.

Lessons

The order is the unit of truth. Once every system orients around the order lifecycle, the manual steps disappear one by one.

Future Improvements

Automated fulfillment routing, returns handling in the same pipeline, and analytics on order-to-fulfillment time per channel.

Technology

WooCommerceERPNextFrappeWhatsApp Business APIInventory sync

Start With the Problem

Tell Us What's Not Working.

You don't need to know which framework, platform or technology you need. Start by explaining the problem — we'll design the system around it.

hello@galaxydigilabs.com