eCommerce ERP Consultant, Oman

Delivering from Muscat to the rest of the country

Oman is a large country with a relatively spread-out population, and that shapes online selling more than most owners expect. An order inside the capital area can often go out the same day at a modest courier charge. An order to the interior, to Musandam or to Dhofar travels further, may pass through more than one courier hub, and is more likely to be delayed or refused. If every order is costed with one average delivery fee, profitable and unprofitable regions look identical.

I start by listing the delivery zones you actually use and the couriers that serve each one. Each order then carries its destination zone, and courier invoices are matched to orders rather than booked as a monthly lump sum. Failed attempts and return trips stay attached to the original sale. With that in place, you can decide on evidence whether to charge delivery by zone, set a minimum basket for distant areas or use a different courier for the south.

Some sellers also hold a second stock point, for example in Salalah, to shorten delivery in Dhofar. That turns stock allocation into a routing question: which location fulfills which order, and how transfers between them are recorded. The general eCommerce ERP page covers the broader order lifecycle.

VAT on every online order

VAT in the sultanate is run by the Oman Tax Authority, and an online business meets it on almost every transaction. Product sales, delivery charges, discount vouchers, store credit, refunds and the commission invoices that marketplaces send you can each have their own tax treatment. Your tax advisor decides that treatment. My job is to turn their guidance into a scenario list the ERP is configured and tested against, line by line.

The common failure I see is a storefront that calculates tax one way, an accounting package that recalculates it another way, and a VAT return built from a spreadsheet that reconciles neither. I fix the point of calculation: usually the store calculates for the customer, the ERP receives the tax amount per line, and a reconciliation report flags any order where the two differ. Marketplace fee invoices are posted with their input tax so it can be recovered where your advisor confirms that is allowed.

The authority is also introducing e-invoicing, and its scope for high-volume consumer sales is something to confirm with your advisor as details are published. During selection I ask each vendor and implementer how their platform will connect to that framework and how simplified consumer invoices would be handled, and I record the answers in the evaluation.

When a few baisa start to matter

The Omani rial is divided into one thousand baisa, so amounts carry three decimal places. Many storefront themes, plugins and gateways were built around two-decimal currencies. When one link in the chain rounds to two places and the next to three, every order picks up a tiny difference. Across thousands of orders, those differences stop the gateway settlement, the bank deposit and the sales ledger from ever agreeing exactly.

Before any connector goes live, I test the full chain with real examples: a discounted item with VAT, a bundle priced below the sum of its parts, a partial refund, and a delivery fee added at checkout. Each amount is followed from the store to the ERP order, the gateway report and the bank line. Where a component cannot handle three decimals, the decision is made early: replace it, round at a defined point, or post the difference to a named rounding account that finance reviews.

The same care applies to price lists. Prices shown to shoppers usually end in round baisa amounts, while cost prices from suppliers billed in dollars or euros do not. Keeping price and cost precision settings separate in the ERP avoids margin reports that look wrong for no real reason. The Oman ERP consulting page explains why I check currency precision on every project there.

Courier collections and gateway settlements

Cash on delivery is still a common choice for Omani shoppers, particularly outside the capital. That money passes through the courier before it reaches you, and couriers remit on their own cycle, net of their delivery and collection fees. The ERP should record a delivered cash order as an amount owed by that courier, not as cash in hand. Each remittance statement then settles a list of orders, books the fees, and shows any parcel the courier says it delivered but has not paid for.

Prepaid orders follow a parallel path. Card and wallet payments arrive from the gateway in batches with fees and refunds deducted, and marketplaces pay after commission and other charges. For each of these I define a clearing account that the sale fills and the payout empties, so leftovers point to a specific batch.

Returns need one rule across both payment types. A refused cash parcel must come back into stock through a recorded receipt, while a return on a prepaid order needs a refund through the original gateway or as store credit, each with its VAT credit note. Writing these steps down before configuration prevents most month-end surprises.

Selecting a platform and planning the move

Omani online businesses I speak with usually run a hosted storefront, seller portals for one or two marketplaces, a courier dashboard and an entry-level accounting tool or a legacy system shared with a physical retail or wholesale operation. The question is whether one ERP can serve both the online and offline sides, or whether an order layer should sit in front of it. Your order volume, number of SKUs and how much trading happens outside the web store decide that.

I build the evaluation on Omani scenarios: a cash order to Salalah refused at the door, a voucher sale with VAT and three-decimal rounding, a marketplace payout with commission and a refund, and an e-invoice question for each vendor. Implementers work through them on screen, and the same scripts carry into user acceptance testing.

The migration scope is live data only: products named in Arabic and English, quantities per stock point, orders not yet delivered, courier remittances still due, gateway batches not yet paid, store credit balances and customer VAT details where you hold them. I work remotely with your team through online workshops and shared trackers, and coordinate integration with the implementer. If you import your own stock, the Oman trading ERP page covers landed cost, and the Oman overview explains how I engage.