1. The Brief: A Multi-Country GCC Motorcycle Group Outgrowing Spreadsheets

A leading GCC motorcycle retail, service, distribution and e-commerce group operates across three countries: the United Arab Emirates, the Kingdom of Saudi Arabia, and the State of Qatar, with a Kuwait rollout already in planning. The business runs as four operating companies, with four distinct go-to-market motions sharing the same customers, the same inventory pool, and the same workshop floor.

The retail side runs flagship showrooms moving premium motorcycles, riding gear, helmets, exhausts and performance parts across the counter every day, through multiple branches, multiple warehouses, and cashier shifts that open and close on a strict daily reconciliation.

The service side is brand-agnostic. The group’s workshops are equipped to service every major motorcycle marque on the road: BMW Motorrad, KTM, Ducati, Harley-Davidson, Triumph, MV Agusta, Aprilia, Honda, Yamaha, Kawasaki, Suzuki, Royal Enfield, plus the long tail of adventure, supermoto, classic and off-road builds that come through the bay doors.

The distribution side is brand-specific. The group is the authorized regional distributor for a portfolio of premium aftermarket marques: Akrapovič exhausts, Alpinestars riding gear, Arai helmets, Bonamici Racing CNC components, Denali Electronics auxiliary lighting, Antigravity and BS Battery power, Barkbusters handguards, ASV controls, DNA High Performance Filters, Daytona boots, Five Advanced Gloves, Chigee smart displays, Gilles Tooling rearsets, Grip Puppy ergonomics, and more.

The e-commerce side runs on Shopify for the consumer-facing storefront and Amazon Seller Central for marketplace listings, both pulling from the same inventory pool that serves the retail counter and the workshop.

Before QCS, the operation ran on a patchwork of spreadsheets, a legacy POS, and disconnected workshop tools. The mandate was clear: one ERP backbone covering retail, workshop, parts distribution, e-commerce, finance and country-by-country compliance, built once and replicated across the GCC.

2. The Five Pillars of QCS Automotive: Retail, Workshop, Distribution, E-commerce and Multi-Country Compliance

Retail and POS. Showroom and accessories-counter operations run a complete retail workflow built on top of ERPNext POS. Every cashier starts the day with a Retail Opening Entry that records the float, the POS profile, the cashier, and the branch. Every shift ends with a Retail Closing Entry that reconciles the period and rolls into finance automatically. Customer Tiering (Bronze, Silver, Gold, Platinum) is applied automatically by lifetime spend, surfaced at checkout so staff know who is standing in front of them. Barcode-driven Stock Entry and Stock Reconciliation make counter receipts and stock-takes a scan-and-go exercise. Tamara and Tabby Buy-Now-Pay-Later are integrated as native payment modes, and a Network International Payment Link can be generated from any Sales Invoice and sent to a customer’s phone for instant checkout. A customer can kit up in Alpinestars head-to-toe, walk out with a new Arai helmet, and finance the lot at the counter, auto-reconciled into the GL.

Workshop and After-Sales. The heart of the workshop is the Repair Order, a single document capturing chassis number, engine number, license plate, color, odometer-in and odometer-out, fuel level, walk-around damage notes, technician assignment, service bay, and service templates. A Ducati Panigale, a BMW R 1300 GS, a Harley Road Glide and a Honda Africa Twin all flow through the same workflow. Around it sits the after-sales suite: appointment scheduling, service bay tracking, technician break schedules, and vehicle issue classification.

Distribution and Parts Logistics. The distributor side is where ERPNext alone falls short. We added Advance Shipping Notices for inbound visibility on shipments coming from Slovenia, Italy, Japan, the United States, Germany, France and Greece. We added Consignment Billing for accurate supplier remittance on consignment stock. We added Brand Target Analytics so the group can track sell-through per marque, per country, per quarter. We added a warranty engine where each brand’s coverage rules attach automatically to every claim. Akrapovič warranty terms differ from Arai’s, which differ from KTM’s, and the system knows the difference.

E-commerce, Omnichannel Across Shopify and Amazon. The group’s online sales run on Shopify for the consumer storefront and Amazon Seller Central for marketplace listings. Both are connected to ERPNext through a two-way synchronisation: ERPNext pushes products, prices and live stock outbound, the channels push orders, customers and fulfilment status inbound. The same Akrapovič exhaust, Alpinestars jacket or Arai helmet that sits on the distribution warehouse shelf appears with accurate availability on every channel, and drops from inventory the moment it sells, no matter where it sells. There is one inventory pool and one customer ledger across the showroom counter, the workshop, the website and the marketplace.

Finance and Multi-Country Compliance. Four operating companies, three currencies, three compliance regimes, all running on one ERPNext instance. UAE entities get full WPS payroll, gratuity per UAE Labor Law, visa and Emirates ID tracking. KSA entities get full ZATCA Phase 1 and Phase 2 e-invoicing with QR codes, XML signing and real-time invoice clearance. Qatar runs on the same platform with localization configured per company. Kuwait will slot in as a fourth country without re-architecting anything.

3. Multi-Warehouse Architecture for a Motorcycle Distribution Business

A motorcycle retail and distribution group does not have a warehouse. It has many, and each one behaves differently.

There are showroom warehouses holding live retail stock under the counter. There are distribution warehouses holding bulk aftermarket inventory bound for sub-dealer fulfilment. There are WIP (work-in-progress) warehouses where parts pulled for an active Repair Order sit physically segregated until they are installed on a bike. There are transit warehouses for stock moving between branches and across borders. Each branch in each country needs its own.

We built the platform around that reality:

• Per-company WIP warehouse mapping. Each operating company in each country has its own configured WIP warehouse. When a part is pulled for a Repair Order, it lands in that WIP warehouse, not in general retail stock, where it could accidentally be sold to a walk-in customer.
• Warehouse Priority Settings. A configurable priority list controls which warehouse the system reaches into first when reserving stock for a customer, so a Sales Order does not accidentally deplete distribution inventory when retail stock is available next door.
• Row-level warehouse permissions. A custom warehouse permission layer means each warehouse user only sees the warehouses they are authorized for. A Saudi branch user does not see UAE stock. A retail cashier does not see distribution-only SKUs.
• Branch-aware notifications. When a Material Request is raised against a specific warehouse, the system notifies the right operations team at the right branch automatically. No more broadcast emails, no more requests sitting in the wrong queue.
• MCS Stock Monitoring and Stock Balance for Sales reports. Custom reports give every showroom manager a real-time view of what is on their shelf, what is in transit, what is reserved for a customer, and what is available to sell, across every warehouse they are entitled to see.

4. Stock Reservation That Actually Holds Across Branches and Borders

ERPNext supports stock reservation out of the box. In a multi-warehouse, multi-branch distribution business, the standard behaviour is not enough. When stock moves from one warehouse to another, the reservation can silently break. When a Sales Order is part-fulfilled and the rest is transferred from another branch, the system needs to release and reapply the reservation atomically. When a Repair Order pulls parts into WIP and then issues some back, the reservation on what is left needs to survive.

We rebuilt the reservation flow around that:

• Re-reservation on stock transfer. A custom flag on Stock Entry instructs the system to un-reserve the source allocation before the transfer, then re-reserve the destination allocation immediately after. The customer’s claim on the stock survives the move.
• Paid Sales Order auto-reservation. When a Sales Order is paid up-front, the system reserves stock from the configured warehouse the moment the order is submitted, before anyone else can pull it. No more “we sold it twice” calls at end of day.
• Reservation aware of Repair Orders. Stock Reservation Entries are linked back to the originating Stock Entry, so the system can trace exactly why a piece of inventory is sitting in WIP and which Repair Order is going to consume it.
• Reserved Items Tracking report. A custom report tells operations exactly what is reserved, for whom, against which document, in which warehouse, at any moment in time.

The result is a stock ledger that retail, service, distribution and e-commerce can all trust. One source of truth for what is on the floor, what is promised, and what is free to sell.

5. The Appointment Calendar: A Live Operations Screen for the Motorcycle Workshop

Standard ERPNext list views are built for back-office users, not for the person running a workshop in real time. A service manager needs to see every bay, every technician, every booking, and every status in two seconds, without leaving the screen.

The Appointment Calendar, built on FullCalendar 5 on top of the QCS Automotive data layer, is that screen. It shows every appointment as a draggable block across a daily, weekly, or monthly view. It shows every technician’s availability with auto-generated break slots. It shows every service bay’s status (Vacant, Occupied, Under Maintenance) alongside its current occupant. New bookings, customer check-ins, and bay reassignments happen in-place, without a single form submission.

Behind it sits the broader workshop layer: Service Bay tracking, Technician Break Schedules, Vehicle Issue Type and Severity classification, and a daily background job that auto-generates the next day’s break slots so no technician is ever double-booked against their own break.

This is the difference between an ERP that records what happened in the workshop and an ERP that runs the workshop.

6. A Consulting-Led Build: We Designed the Operating Model Before Writing Code

When this engagement started, the client did not have a documented operational playbook. There was no written process for how a Repair Order should route from advisor to technician to invoicing. No defined cashier shift discipline. No agreed structure for how multi-warehouse stock should be reserved across branches. The business was running on tribal knowledge, not a system.

This was not an implementation engagement. It was a consulting engagement that produced an implementation.

We walked the floor and designed the target operating model. We sat with service advisors as they took bookings, with technicians as they pulled parts, with retail managers as they closed shifts. Drawing on prior automotive, retail and distribution engagements across the GCC, we proposed the workflows the business should run on, not the ones it happened to be running on, and ran them past the operations and finance teams before encoding a single line.

We brought the patterns and codified the master data. Multi-warehouse reservation discipline, branch-level permission scoping, retail tiering, consignment ledger design, brand-linked Warranty Requirements, ZATCA-compliant invoice numbering, paid-Sales-Order auto-reservation: these are patterns refined across earlier engagements. The brand owners supplied warranty terms, service intervals and parts catalogues, and we turned them into a structure the system enforces automatically.

We translated regulation into system behaviour. UAE WPS payroll, gratuity, ZATCA Phase 1 and Phase 2 e-invoicing requirements are externally defined and non-negotiable. We translated them into ERPNext custom fields, validation logic, document event handlers and scheduled jobs so that compliance is a property of the system, not a checklist for an accountant to remember.

The system that shipped is not a digital copy of how the business used to run. It is an encoding of how the business should run. That is the difference between automating a workflow and improving one.

7. Why ERPNext for a Multi-Country Motorcycle Dealership

We chose ERPNext for three reasons.

First, ERPNext itself is open source. The client owns their data outright, runs on a platform with no per-seat licence trap, and avoids the lock-in of a proprietary DMS that can be sunset, repriced, or withdrawn from the Middle East at any time.

Second, ERPNext ships multi-company, multi-currency and multi-branch out of the box, which is exactly what a multi-country GCC group needs. Adding KSA after UAE, then Qatar, then Kuwait, is a configuration exercise, not a re-platforming exercise.

Third, custom Frappe applications extend ERPNext, they do not replace it. Every Repair Order touches the same stock ledger, accounting ledger, customer master and HR data as a regular Sales Invoice or Stock Entry. There are no parallel databases. No shadow systems. No nightly reconciliation between operations and finance. Operational data and financial data are the same data.

8. Integration Depth: One Inventory Ledger Across Retail, Workshop, Shopify and Amazon

The platform’s value is in how the modules talk to each other. The Repair Order is bidirectionally linked to Quotation, Sales Order, Sales Invoice, Material Request, Pick List, Stock Entry and Purchase Receipt. Every part, on every document, knows which repair it belongs to. WIP warehouse routing keeps parts physically segregated per job until installed on the bike.

Stock Reservation Entries are aware of repair orders, sales orders and inter-warehouse transfers, with custom logic that un-reserves and re-reserves stock automatically during transfers so allocations are never silently lost. Sales Invoices auto-generate Warranty Certificates per serial number, post to consignment ledgers where applicable, and route revenue to the correct GL account per customer group, per company.

The same integration depth extends out to the channels the business sells through. Shopify runs the consumer-facing storefront and is wired into ERPNext with a two-way sync that pushes product, price and live stock outbound, and pulls orders, customers and fulfilment status inbound, all drawing on the same inventory pool and the same warehouse priority rules as a counter sale. Amazon Seller Central is connected for listing management, inventory sync and order intake, so a sale on the marketplace depletes the same stock as a sale in the showroom. Network International Payment Links are generated from any Sales Invoice and sent straight to the customer’s phone for one-click payment. Tamara and Tabby sit alongside as native BNPL payment modes. A customer can kit up in Alpinestars on Shopify, buy an Arai helmet on Amazon, fit a Bonamici rearset at the workshop, and pay for the next service through a Network Payment Link sent over WhatsApp, with every cent reconciling cleanly into the GL.

9. Multi-Brand by Design: Servicing Every Marque, Distributing Every Brand

Across the service workshops, every major motorcycle marque on the road is supported. Across the distribution side, fifteen-plus premium aftermarket brands are managed end-to-end. The workflows had to be brand-aware without splintering into fifteen separate systems.

Brand-linked Warranty Requirements, brand-specific GL routing, brand-level supplier mapping and brand-target analytics are all configured per brand, while the underlying repair, billing and accounting flow stays identical. A customer who brings in a BMW R 1300 GS for service today, walks out with a new Alpinestars suit, and orders an Akrapovič exhaust for their KTM tomorrow is one customer, in one ledger, with one lifetime-value record.

10. Multi-Country by Architecture: UAE, Saudi Arabia, Qatar, Kuwait

UAE, KSA and Qatar are live in production today. Kuwait is in rollout planning. Each country operates as its own company entity inside a single ERPNext instance, with its own chart of accounts, its own cost centres, its own warehouses, and its own compliance posture. UAE WPS payroll on the Emirati entity, ZATCA Phase 2 e-invoicing on the Saudi entity, Qatar localization on the Qatari entity. Shared master data (customers, vehicles, parts, brands, warranty rules) lives once and serves all three.

The rollout pattern is repeatable. When Kuwait goes live, it slots in as a fourth company on the same instance, not a fourth instance to maintain.

11. Built Once, Designed to Replicate Across the GCC

The configuration playbook developed across the UAE, KSA and Qatar rollouts means each new country, branch or sub-dealer can be brought online in days, not months. Cost-centre and segment information propagates from every source document down to derived postings, so workshop activity, parts sales, distributor consignments, online orders and retail invoices all land on the right cost line automatically. Adding a new branch, a new brand, or a new repair type is a configuration task, not a development task. The system is built to be modified by the client’s own admin team after handover.

12. Tech Stack: Frappe, ERPNext, Python, FullCalendar 5

Frappe v15, ERPNext v15, Python, MariaDB, Redis Queue for background jobs, FullCalendar 5 for the Appointment Calendar UI. Four custom Frappe applications were built specifically for this client. QCS Automotive (workshop, repair orders, appointments, technicians, service bays). QCS Enterprise Suite (Advance Shipping Notices, Collection and Payment Runs, stock reservation re-reservation, permission audit logging). The OldTimer Vertical Pack (motorcycle catalogue, customer-motorcycle history, brand-aware warranty engine, retail POS, Tamara and Tabby BNPL, Network International Payment Links, Shopify and Amazon e-commerce connectors, consignment billing, warehouse priority settings). And the UAE QCS and KSA Compliance apps for regional payroll, WPS, gratuity, and ZATCA e-invoicing.

The build was iterative. Retail and POS went live first, against real cashier shifts and real customer transactions. Workshop and after-sales followed, validated against live repair orders. Distribution, ASN and consignment came online next. E-commerce channels and online payments wired in once the inventory and reservation discipline was proven on the floor. Country-by-country compliance rolled in alongside each new operating company. Each pillar was validated against real-world transactions before the next went live.

13. Implementation by the Numbers

14. Talk to Us About Your Motorcycle Dealership ERP

If you are building or scaling a motorcycle, powersports or automotive operation that needs an industry-specific ERP, across the GCC or anywhere ERPNext’s open architecture is a fit, Quark Cyber Systems can do more than implement. We consult, we design the operating model, and we build the system around it. Talk to us at quarkcs.com.