Ival & Oska: Turning Magento Into the Backend for a Mobile-First Retail Business
Ival & Oska didn't need a storefront. They needed Magento to act as the engine behind native mobile apps, a SOAP-based ERP, four regional payment providers, and delivery rules specific enough to round prices to the nearest quarter riyal.
Real results. Not just projections.
Four jobs, one Magento build.
Ival & Oska's brief looked deceptively like a normal Magento project on paper. In practice, it needed Magento to do four genuinely different jobs at once: act as the backend for native iOS and Android apps, stay in lockstep with a SOAP-based ERP called SalesBuzz, orchestrate checkout across four different regional payment providers without customers noticing the complexity, and enforce delivery and pricing rules specific enough that a generic commerce platform simply doesn't have an opinion on them, like rounding prices to the nearest quarter riyal.
Headless mobile architecture meant Magento had to behave like a true app backend, not a website with an API bolted on. The project needed an API layer robust enough to power native iOS and Android experiences: custom workflows, rich content, full account functionality, and real commerce logic, not a thin wrapper around standard Magento REST endpoints.
ERP synchronization with SalesBuzz demanded real precision. Orders, customers, SAP IDs, wallet balances, invoices, and payments all needed to stay reliably in sync between Magento and a SOAP-based ERP environment, a genuinely less forgiving integration surface than a modern REST API.
Regional payment complexity meant orchestrating Checkout.com, Tamara, Tabby, and HyperPay, plus Apple Pay and other locally expected payment methods, behind what needed to feel like one seamless checkout, not four different systems stitched together with visible seams. And the operations layer was specialized in ways that only show up once you're actually running the business: geo-polygon delivery zones, automatic driver assignment, and SAR price rounding in precise 0.25 increments, business logic that extends well past what "standard" Magento commerce assumes.
The ERP backbone, and a delivery system built to hold up.
We built a custom SOAP-based integration between Magento and SalesBuzz that handles real-time order push through WCF services, keeps customer SAP IDs, wallet balances, and loyalty data synchronized, and reconciles invoices and payments rather than just passing data through blindly. Cookie-based SOAP authentication and detailed error logging keep the connection auditable, and a cron-driven sync with manual resync capability means recovery from a failure doesn't require an engineer to intervene by hand every time.
The delivery layer includes full driver management with assignment tracking, geo-polygon validation so delivery zones map to real operational boundaries rather than rough postal codes, and automatic driver assignment the moment a shipment is created. GraphQL endpoints expose tracking and operational data cleanly to the mobile apps, with feedback and monitoring built in to keep visibility into delivery performance.
57 custom GraphQL modules: the real engine behind the apps.
Checkout.com handles card payments and Apple Pay, Tamara and Tabby cover buy-now-pay-later, and HyperPay adds regional routing coverage, all unified behind a single checkout experience with vault management and mobile-friendly payment flows, so the complexity underneath never becomes the customer's problem to navigate.
The heart of this project is a 57-module custom GraphQL layer that turns Magento into a genuine backend for mobile-first retail. It covers advanced order management (modification, cancellation, duplicate prevention), payment gateway extensions across all four providers, customer experience features like social login and abandoned cart recovery, dynamic content and promotional logic for app merchandising, and the specific business rules, SAR rounding, QR codes, bilingual PDF generation in Arabic and English, that made this platform actually fit Ival & Oska's business rather than approximate it.
A real brand, not a demo storefront.
All of this runs behind a real, live consumer brand with real orders moving through it daily, not a staging environment built to demo well. The mobile-first architecture had to hold up under actual purchase volume from day one.
Built for a catalog that runs in two languages.
The catalog itself reflects the same bilingual, business-specific discipline as the backend: Arabic and English throughout, with pricing and packaging structured around how the business actually sells, individual customers on one side, bulk and institutional orders on the other.
“Ival & Oska needed a commerce engine that could serve apps, ERP workflows, payments, and operations all at once, without compromising customer experience.”
- SnapTec implementation team
What This Proves About Headless Commerce
Mobile apps don't succeed on generic APIs
They need purpose-built resolvers and modules that reflect exactly how the business sells, fulfills, and communicates, not a one-size-fits-all API layer.
ERP integration is a growth enabler, not just a backend chore
When orders, invoices, payments, and customer records stay synchronized in real time, the whole organization moves with more speed and confidence, not just the warehouse team.
Regional commerce needs orchestration, not just plug-ins
BNPL, Apple Pay, SMS providers, delivery rules, bilingual support, and custom pricing logic only feel seamless to a customer when they're engineered as one connected system.
Need Magento to Power Apps, ERP, and Regional Commerce at Once?
SnapTec builds mobile-first Magento ecosystems with custom GraphQL, real enterprise integrations, and operational logic designed for how your business actually runs, not a generic template.
Talk to Our Magento Team