← All projects

Business Software / Project 02

Syrian ERP

A locally oriented business management system concept for Syrian businesses, with Arabic and English in mind.

In DevelopmentPortfolio overview

Overview

Exploring how an offline-aware, multi-tenant business platform can bring core operations and reporting together.

Syrian ERP is an evolving product concept for connected business operations, with offline-first use and live synchronization as design goals.

The problem

Why this work matters

Businesses need management tools that reflect local operating conditions, language needs and variable connectivity.

Approach

From need to system

Syrian ERP is an evolving product concept for connected business operations, with offline-first use and live synchronization as design goals.

My role

Product concept development, workflow thinking and exploration of an appropriate digital architecture.

Architecture

How the pieces fit

  • Multi-tenant SaaS direction
  • Flutter mobile application direction
  • Offline-first records with synchronization as a design goal
  • Arabic and English interface requirements

Capabilities

Features & focus

  • Inventory, sales and purchasing
  • Customer and supplier management
  • Accounting and reporting
  • Operational dashboard and AI-assisted BI as future exploration

Data flow

01

Business users record operational activity

02

Records are stored locally when connectivity is unavailable

03

Synchronization updates the shared business workspace

04

Reporting brings activity into operational views

Visual documentation

Screenshots

No public screenshots are available yet. Future visuals will use sanitized or mock-data examples.

Challenges

  • Balancing offline workflows with data consistency
  • Designing a right-to-left Arabic experience alongside English
  • Scoping an extensible ERP without overbuilding

Lessons learned

  • Local needs should shape product choices from the start.
  • Offline support affects data modeling and workflows, not just connectivity code.

Next steps

Roadmap

  1. Validate priority workflows with prospective users
  2. Define a focused initial product scope
  3. Prototype inventory and sales workflows
  4. Assess synchronization and reporting architecture