تحميل السيرة الذاتية
ENعربي
→ كل الأنظمة الخمسة والعشرين

منصّة · 2025 · دون ذكر اسم العميل

منصّة لبيع مواد البناء تتزامن مع نظام ERP

متجر إلكتروني وتطبيق ولوحة لإدارة العمليات، كلّها مبنية فوق نظام خارجي لإدارة موارد المؤسسة (ERP). البيانات تنتقل بين الطرفين في الاتجاهين وتبقى متطابقة.

124

مساراً في الواجهة البرمجية

17

نموذجاً للبيانات

6

Roles

customer, vendor, technician, sales, admin, superadmin

9

Written guides

المشكلة

A hardware and building-supplies retailer already ran their business on an external ERP platform. They wanted a customer app, a storefront and an operations dashboard, but the ERP had to stay the system of record for products, stock and pricing. Two systems both accepting writes is where retail data goes wrong, so the sync had to be genuinely bidirectional rather than a nightly export.

الحلّ المعتمد

Built the platform as a layer over the ERP rather than a replacement for it. Product, inventory and pricing flow in from the ERP; orders, customers and fulfilment events flow back out. Six roles including vendors and field technicians, bulk product import and export for catalogue operations, 124 endpoints across 17 collections. The integration itself was the coordination problem: I worked directly with the ERP vendor engineering team in another country, established what their system expected on each side of the exchange, and specified what they needed to build to meet ours.

بنية النظام

The ERP owns products, stock and pricing. The platform owns customers, carts, orders and fulfilment. Each side is authoritative in exactly one direction, which is what keeps a bidirectional sync from becoming a conflict engine.

قراران

ومع كل قرار ثمنه

القرار الذي لا يُذكر ثمنه مجرّد تفضيل شخصي.

01

يبقى نظام ERP هو المرجع الأساسي للبيانات

السبب

عمل العميل يعتمد عليه أصلاً. ونقل صلاحية تحديد الأسعار والمخزون إلى نظام جديد يعني وجود مرجعين مختلفين للبيانات، ومشكلة مطابقة بينهما لا يريد أحد أن يتحمّلها.

الثمن

تعتمد المنصّة على أن يكون نظام ERP متاحاً. لذلك تحتفظ عمليات القراءة بنسخة مؤقتة من البيانات، وصُمّمت عمليات الكتابة بحيث يمكن إعادة تنفيذها بأمان.

02

Bulk import and export as a first-class path

السبب

Catalogue operations at retail scale are not done one product at a time. The largest single controller in the codebase is the import and export handler, which is the correct place for that weight to sit.

الثمن

A bulk path needs its own validation and partial-failure reporting, separate from the single-record path.

النتيجة

The retailer keeps their ERP as source of truth and gets a full customer-facing platform in front of it. Nine written guides ship with the codebase, including dedicated integration documentation, because a two-system contract that only exists in one engineer head is a liability.