dcommerce.io

Enterprise Case Study

A wholesaler captured orders in WooCommerce but re-keyed every one into a legacy ERP. dCommerce connected the storefront to the back office, added an order-management layer for review and edits, and automated the hand-off - on the Enterprise plan.

Overview

Industry context: Wholesale commerce with customer orders entering through a WooCommerce storefront.

Legacy process: Customer Service manually re-keyed WooCommerce orders into a legacy ERP with a circa-1980s interface.

Objective: Integrate WooCommerce with the ERP end to end, while allowing order data to be reviewed and adjusted before it is committed to fulfilment.

Solution framework: WooCommerce webhooks and REST APIs feed an order management system; once finalised, orders are submitted to the legacy ERP via its existing encrypted email integration, with confirmation polled and written back to WooCommerce.

Challenge

The client’s customers placed orders online through WooCommerce. There was no direct path from the website into the legacy ERP, so Customer Service re-entered every order by hand.

Data entry into the ERP was slow and error-prone. The interface dated from the 1980s era of the system, and the ERP itself could not be modified to speak modern e-commerce protocols. A prior custom integration accepted only an encrypted string of proprietary key-value field codes delivered by email - functional, but far from a standard API.

The result was a familiar wholesale bottleneck: digital order capture on the front end, manual transcription in the middle, and a rigid back office that could not absorb WooCommerce natively. Scaling order volume meant scaling re-keying effort - and with it, the risk of pricing mistakes, missed lines, and fulfilment delays.

The business also needed more than a dumb pipe. Wholesale orders often require sanitisation and customer consultation before they should hit the delivery schedule. Any integration had to preserve a controlled review step without sending staff back into WooCommerce for day-to-day processing.

Solution

dCommerce was introduced as the middle layer between the storefront and the ERP: automated ingest from WooCommerce, a dedicated order dashboard for Customer Service, and a structured submission path into the legacy system.

The WooCommerce site was connected via the standard REST API for Product, Customer, and User data, giving the dashboard a consistent commercial view of each order. Order events were integrated via webhooks for near-real-time processing. Once synchronised, Customer Service could work entirely in the dashboard - verifying details and, where needed, editing information in consultation with the customer - without logging into WooCommerce for routine processing.

WooCommerce remains the system of record for the original customer order. The dashboard is a separate workspace for reviewing and finalising what will be sent downstream. When an order is ready, the operator triggers submission to the ERP.

Because the ERP still only accepted its proprietary email format, the platform converts finalised order data into the required encrypted key-value message and delivers it by email. The ERP processes the message and returns a confirmation to a dedicated, secure inbox monitored by the order management system. The platform polls that inbox, extracts ERP order numbers, and follows data links to verify that processing succeeded.

When confirmation is received, dCommerce calls the WooCommerce REST API to close out the order and triggers the final confirmation email to the customer - completing the loop from website placement through ERP acceptance without manual re-keying.

Benefits

The wholesaler gained full order automation without a costly ERP replacement. WooCommerce stayed the customer-facing channel; the legacy ERP stayed the system of record for fulfilment; and Customer Service gained a purpose-built layer to sanitise orders before they committed to the schedule.

Elimination of manual data entry: Orders flow from WooCommerce into the dashboard and on to the ERP. Re-keying is removed from the critical path, reducing transcription errors and freeing Customer Service for higher-value work.

Controlled review before commit: Orders can be verified and adjusted with the customer before they enter the ERP - protecting the delivery schedule from incomplete or incorrect submissions that a straight-through integration would have locked in.

Extended legacy ERP lifespan: The company avoided the cost, risk, and disruption of an enterprise ERP upgrade. dCommerce gave the existing stack modern, API-driven capabilities at the ordering layer while the ERP continued to do what it already did well.

Faster, more predictable processing: Near-real-time webhook ingest and automated confirmation close the loop between storefront and back office, shortening the gap between customer checkout and ERP acceptance.

ERP kept authoritative - and untouched: Complexity stays upstream in the order management layer. The legacy system is not customised further for e-commerce; it continues to receive clean, pre-agreed payloads in the format it already understood.

A clear Enterprise plan fit: End-to-end ERP integration, third-party storefront synchronisation, and operational order management map directly to how Enterprise deployments are designed - automate the pipeline without forcing a rip-and-replace of the back office.


If you would like to discuss this or a similar solution, please contact us.