Marketplace Content Workflow Automation at JUMIA Group (Emerging Markets)

Context & Business Challenge

In 2018, as JUMIA prepared for its IPO on the NYSE, the organization operated under a two-tier country model:

• Big Five: Nigeria, Egypt, Morocco, Ivory Coast, and Kenya

• Emerging Markets: Senegal, Ghana, Cameroon, Uganda, Tanzania, Algeria, Tunisia

Most tooling and systems were optimized for the Big Five and rolled out to Emerging Markets with minimal customization.

Within Content & Production teams, Basecamp was being used to manage seller content requests, SKU image uploads, and photoshoot scheduling. The tool proved unintuitive and misaligned with increasing marketplace complexity. Key issues included:

• Fragmented and manually submitted content requests

• Poor visibility into task queues and ownership

• Limited tracking of SKU uploads and production progress

• Growing bottlenecks as seller volumes increased

Content production directly impacted product listing quality, seller satisfaction, and marketplace growth. The workflow inefficiencies were becoming a structural constraint.

Objective & Success Criteria

The initiative aimed to replace Basecamp with a more intuitive, automated, and scalable workflow , without allocated budget.

Key objectives

• Centralize seller content and production requests

• Automate task creation and routing

• Improve queue visibility and ownership

• Simplify coordination across Content & Production teams

• Deliver a zero-budget solution

Success was defined by

• Successful pilot in at least one market

• Adoption across all Emerging Markets

• Improved seller SKU and content handling

• Endorsement and rollout by Group Management

My Role & Ownership

As IT Representative for Uganda, I fully owned the solution design and implementation.

The initiative followed prior success in designing lightweight operational systems and was executed without:

• Dedicated team

• External vendor

• Approved budget

I was responsible for tool selection, workflow architecture, pilot execution, and regional rollout support.

Workflow Strategy & Execution

Tool Selection & Architecture

I evaluated multiple task management platforms and selected Trello based on:

1. Visual workflow model

2. Ease of adoption

3. Low friction for non-technical teams

4. Rapid deployment capability

To create structured intake, I designed a Google Form aligned with Content & Production team requirements. The solution stack included:

1. Google Forms - structured seller request intake

2. Zapier - workflow automation

3. Trello - visual task and queue management

Automated Workflow Logic

The workflow operated as follows:

1. Seller submits SKU and content request via Google Form

2. SKU data, images, and photoshoot schedules captured

3. Zapier automatically generates Trello cards

4. Cards entered predefined and broken-down workflow columns/Lists

5. Content & Production teams triage and process requests

6. Progress tracked visually and transparently

Boards were structured to separate queues, ownership, and workload visibility. The design emphasized simplicity, rapid adoption, and scalability across markets with varying team maturity levels.

Technical Capabilities

Core Components

• Google Forms (request capture)

• Zapier (automation and routing logic)

• Trello (queue management and progress tracking)

Capabilities Enabled

• Automated task creation

• Structured queue management

• Clear ownership assignment

• Visual workflow tracking

• Reduced manual coordination

Design Philosophy

• Lightweight and low-cost

• Rapid deployment

• Scalable across multiple markets

• Minimal training overhead

Results & Impact

Before

• Basecamp misaligned with workflow needs

• Fragmented request handling

• Limited queue visibility

• Manual coordination burden

• Increasing inefficiencies as seller volume grew

After

• Automated intake and card creation

• Clear queues and ownership structures

• Faster processing of seller content requests

• Improved coordination across Content & Production teams

• Adoption across all Emerging Markets

• Subsequent influence on Group-level tooling decisions

Strategic Impact: The solution demonstrated that Emerging Markets could design scalable operational systems under constraint and influenced broader group thinking around workflow tooling.

Key Challenges & Approach

1. Zero Budget Constraints: No initial approval for paid tools.

   • Approach: leveraged free tiers strategically, delivered measurable impact, and demonstrated value before budget discussions.

2. Platform Feature Limitations: Trello’s free version had constraints.

   • Approach: optimized workflow structure to work within limitations and proved usage growth that later supported enterprise tool evaluation.

3. Cross-Market Scaling: Different markets had varying seller volumes and operational maturity.

   • Approach: piloted in Uganda, refined the workflow, then executed gradual regional rollout with localized support.

What I Would Do Differently

• Formalize scalability thresholds earlier

• Introduce structured reporting dashboards sooner

• Accelerate transition to purpose-built or enterprise-grade tooling once scale justified it

• Push earlier for budget approval after proof of value