Contact Info
What does an eCommerce ERP consultant do for a Kuwaiti business?
For a Kuwaiti business selling online, an eCommerce ERP consultant connects the web store, marketplace accounts and showroom stock to one ledger in dinars and fils. That means KNET and card settlements reconciled per batch, cash collected by drivers tracked as a courier balance, and online sales kept separate by brand and company within a family group. I define these requirements, compare platforms and guide delivery remotely.
Last reviewed by Vikas Saroj
In Kuwait, the online store is often one channel of a larger business rather than the whole business. A family group may sell the same agency brands through showrooms, co-operative societies, a web store and marketplace listings, all drawing on one warehouse. Online orders then compete for stock with every other channel, and their profit is hard to isolate.
I work remotely with Kuwaiti groups, retailers and online-first brands to define what the ERP must handle for eCommerce: stock shared with showrooms, KNET and card payouts, drivers collecting cash, and reporting by company and brand. I then help select a platform and oversee the implementer through go-live.
Kuwaiti businesses usually ask for help when online sales have grown large enough that the old way of sharing stock and reconciling payouts no longer holds.
Rules for which warehouse or showroom fulfills web orders, how much stock is protected for co-operative and retail customers, and how click and collect reserves an item in a specific showroom.
A clearing structure for KNET, card, wallet and marketplace payouts, so every settlement batch is broken into sales, fees and refunds and matched to the bank without a monthly spreadsheet.
Cash orders tracked from handover to remittance, whether a third-party courier or your own drivers collect them, with shortfalls and charges visible per order and per driver.
A decision on which legal company owns the online sale, how agency brands are reported, and how intercompany stock transfers post when the web store sells another group company's goods.
A requirements document drawn from your own order types and a scored comparison of Zoho, Odoo, ERPNext and Dynamics 365, with demos scripted on Kuwaiti payment and delivery cases.
Connector testing, catalog cleanup with Arabic names, a phased channel cutover and close support through the first settlement and month-end cycle after the new system goes live.
An ERP for ecommerce should make these numbers available without a spreadsheet. I design the data model and reports around them from the start.
Where online fits in the group
Ownership, rules and shortlist
Phased cutover with close support
Many Kuwaiti online stores are run by companies that also supply co-operative societies and other retailers and operate their own showrooms. The website is then competing for the same physical units as a co-op order due tomorrow and a showroom display. Without a clear policy, the store sells stock that was promised elsewhere, or the team hides stock from the web to be safe and loses sales.
I define availability for the web channel explicitly. Usually the ERP calculates it from selected warehouses, minus quantities reserved for open wholesale orders and a protected level per item for key retail customers. Showroom stock can be included for click and collect, where the customer reserves an item in a named showroom, but excluded for home delivery if the showroom cannot pack and dispatch parcels.
Bundles, promotional packs and gift sets need their own rule, because a set sold online consumes components that the co-op channel may also need. I document how kits are built, whether they are assembled in advance or at picking, and how a broken kit returns to stock. These rules sit within the wider order lifecycle described on the eCommerce ERP page, and they connect directly to the channel design on the Kuwait trading ERP page.
Kuwaiti shoppers commonly pay online with KNET debit cards through a payment gateway, alongside credit cards and digital wallets. Each method can settle on a different cycle and with different fees, and marketplaces pay their own net amounts after commission and promotional charges. The bank statement shows a few large deposits; finance needs to know which orders they cover.
For every gateway and marketplace I set up a clearing account in the ERP. Orders post their full value into it at the point of sale. The settlement report, imported rather than retyped, posts each fee, refund and chargeback to its own account. The bank deposit clears what remains. When the balance is not zero, it identifies a specific batch to follow up instead of a general difference spread over the month.
Precision matters here. The dinar is divided into one thousand fils, and a gateway file, storefront plugin or connector that works in two decimals will create small differences on many orders. I test the whole chain with discounted and refunded orders before go-live and, where a component cannot be changed, agree a single rounding account that finance reviews. Refunds follow their original route: back through the gateway for card orders, or as store credit where your policy allows it.
Plenty of Kuwaiti customers still choose to pay at the door. Some businesses use third-party couriers for this; others run their own drivers, especially for larger items, furniture or same-day delivery within the city. Both models create money that is collected but not yet banked, and both need a record that tells finance exactly where it is.
With a third-party courier, I treat the courier as a debtor. Proof of delivery moves the order value from the customer to the courier's account, and each remittance clears a list of orders, books the courier's fee and exposes anything delivered but unpaid. With in-house drivers, the design adds a daily handover: each driver's run sheet lists the orders delivered, the cash expected and the cash counted, and differences are posted to that driver for follow-up the same day.
Refused orders are the other half of the picture. A parcel that comes back must be received into stock with its condition noted, not just marked cancelled, and the cost of the failed trip should stay on the order. When the data is captured this way, owners can see which areas, products and order sizes generate refusals, which is usually more useful than a simple cancellation count.
In a multi-company group, the first question is which legal company sells online. Sometimes the web store sits in a separate company that buys from the agency-holding companies; sometimes each company sells its own brands through a shared site. The answer determines how orders are booked, how stock moves between companies and how intercompany balances are settled. I agree this with the group's finance team before any configuration, because changing it later means reworking every transaction.
Reporting then follows the structure: online sales by brand, by company and by channel, with returns and delivery costs allocated so a brand manager can see real online contribution next to showroom and wholesale results.
On tax, a local online sale in Kuwait carries no VAT today as far as I am aware, because the country has yet to bring a general VAT into effect. Ask your tax advisor to reconfirm this before design sign-off, since a GCC framework exists and the picture could shift. I still place a tax field on every order line, set to zero where nothing applies, so the system can adapt. Orders shipped to other GCC countries may involve destination customs and taxes; your courier and advisor confirm the treatment, and the ERP records the destination and related charges so cross-border margin is visible.
The system landscape behind a Kuwaiti online store is often mixed: a hosted storefront, marketplace portals, a point-of-sale system in the showrooms, a group accounting package and spreadsheets linking them. Selection is less about features than about which platform can hold all channels against one stock pool and one set of company books, with Arabic product names and fils-level precision.
I run demos with scripts built on your reality: a web order fulfilled from a showroom, a co-op order competing for the last cartons of a promoted item, a KNET payout including a refund from an earlier batch, and a driver handing over less cash than expected. Vendors demonstrate those cases live, and I reuse the scripts as acceptance cases during UAT.
Cutover is usually phased by channel, starting with the web store and adding marketplaces once stock sync is stable. Migration covers active SKUs with marketplace identifiers, stock per location, open orders, unpaid driver and courier balances, and store credit. I deliver all of this remotely with online workshops and a shared tracker, coordinating integration with your implementer. The Kuwait ERP consultant page and the Kuwait overview describe my wider approach.
Tell me about your business and current systems. I’ll suggest the most sensible first step.
Book a Consultation
Not sure which ERP you need?
Share your business requirements with me and I will help you understand the right process, architecture and platform before implementation.
It depends on whether showrooms can pick and dispatch reliably. Many groups include showroom stock for click and collect but keep home delivery on warehouse stock. The ERP should allow both rules and show availability per location, so the policy can change without reconfiguring the whole store.
Import each gateway settlement report into the ERP rather than posting bank deposits as lump sums. Orders fill a clearing account per gateway, the report posts fees and refunds, and the deposit clears the rest. Any balance left identifies a specific batch, which makes follow-up with the gateway quick.
There is no single right answer. A separate eCommerce company simplifies reporting but adds intercompany transactions; selling through each brand's own company avoids that but complicates the shared storefront. I lay out the consequences of each structure for finance, stock and reporting so your group can decide with its advisors.
No. I work remotely, through online workshops with finance, operations and eCommerce teams, short recordings from the warehouse and showrooms, and a shared tracker for decisions and test results. Travel for a single milestone is possible by arrangement, though rarely needed.
Every business is different. Share where you are today and what you want to fix, and I’ll tell you honestly whether and how I can help.
Book a Consultation
Book a consultation to talk through your processes, systems and goals. I’ll reply with practical next steps - no obligation.