All case studies

Retail & E-commerce / Illustrative case study

One order workflow across WhatsApp, email and the online store

How a retailer could bring orders from different channels into a consistent process, with missing details and outstanding actions visible.

Illustrative scenarios showing proposed workflows and expected outcomes.

01 / The challenge

Where the work gets stuck.

An order in a message may omit a product variant or delivery address. Another may already exist in the online store. Staff copy information between channels and struggle to tell which orders are ready for the next step. Treating every message as a new order could introduce duplicates.

02 / How Wek would help

A defined process, with people in control.

Wek would begin by agreeing the scope, quality standards, systems access and approval rules with the retailer. The following steps illustrate how delivery could be organized.

  1. 01

    Agree intake and validation rules

    Define required fields, order identifiers, approved information sources and the statuses that determine whether an order can progress.

  2. 02

    Capture and check

    Wek would organize incoming requests into structured order records. Extraction and validation could highlight incomplete fields and possible duplicates, with a person reviewing ambiguous requests.

  3. 03

    Coordinate outstanding actions

    Follow up on missing information through approved channels. Route availability, pricing or payment questions to the retailer instead of treating them as confirmed.

  4. 04

    Maintain the handoff

    Enter approved orders into the designated system, record the next responsible team and maintain status updates. Report orders waiting on information or client decisions.

03 / The workflow

From input to a usable output.

Order intake & validationIllustrative workflow
WhatsAppEmailOnline store
One order queueMatch references · flag duplicates
Complete orderValidated for handoff
Missing detailsFollow up before release
Clarified information returns to validation
Approved order recordReady for the next responsible team

An exception in practice

A WhatsApp request resembles an existing store order but uses a different name. Wek would flag the possible duplicate and seek confirmation before creating another record.

04 / Expected outputs & benefits

What this approach would deliver.

  • Validated order records
  • A queue of incomplete orders and assigned actions
  • Order-status and exception reports

The intended benefit is a clearer handoff between order intake and fulfillment, with fewer requests lost between channels.

How a pilot could be measured

  • Orders complete at handoff
  • Duplicate and correction rates
  • Age of orders awaiting information

Measures and targets would be agreed against the retailer’s starting position. No performance results are claimed for this scenario.

Explore Order Operations

Explore another workflow.

Let’s put structure around the work.

What workflow is taking too much of your team’s time?

Show us the process. We’ll explore how to structure, operate or automate it more effectively.

Discuss a Workflow