3
أجزاء سُلِّمت
API, admin dashboard, storefront
منصّة · 2025 · دون ذكر اسم العميل
متجر إلكتروني ولوحة إدارة وواجهة برمجية (API)، كلّها مبنية فوق نظام ERP الذي يستخدمه العميل أصلاً، ويبقى ذلك النظام هو المرجع الأساسي للبيانات.
3
أجزاء سُلِّمت
API, admin dashboard, storefront
ERP
مرجع البيانات
deliberately not replaced
المشكلة
A bookstore chain already ran products, stock and pricing in an established ERP. They needed a modern storefront and dashboard, but replacing the ERP was never on the table and duplicating its data would create two versions of the truth.
الحلّ المعتمد
Built the platform explicitly in front of the ERP rather than beside it. The ERP remains authoritative for catalogue, stock and price; the platform owns the customer experience, carts, orders and content. Three tiers shipped: the API, an admin dashboard, and a storefront.
بنية النظام
The ERP is upstream and authoritative. The platform reads catalogue and stock from it and pushes orders back, with the customer-facing layer owning everything the ERP has no opinion about.
ومع كل قرار ثمنه
القرار الذي لا يُذكر ثمنه مجرّد تفضيل شخصي.
01
السبب
The client staff already operate it daily. Migrating a working ERP to gain a storefront is a large project with no upside for the people doing the work.
الثمن
The platform inherits the ERP data model in places where a greenfield schema would be cleaner.
النتيجة
The client keeps running their business in the ERP their staff already know, and customers get a storefront that reflects it.