An online store can look ready while its payment, delivery and stock processes are still unresolved. For a UAE ecommerce project, the most valuable work often happens before the design: agreeing how the business will actually accept and fulfil an order.
Start with the operating requirements. Confirm Arabic/English scope, currency and payment eligibility, shipping and returns, stock ownership, integration access and acceptance tests. Choose the platform after those decisions—not before them.
Use this checklist to brief an implementation partner or compare proposals. It is a technical planning guide, not legal, licensing or tax advice. No platform choice guarantees legal compliance or commercial results.
1. Establish the merchant and trading scope
Record which business will sell, where it is established, which products it will offer and which markets it will serve. A local retail launch, cross-border catalogue and business-to-business ordering portal have different requirements.
The UAE Government’s ecommerce guidance explains that online trading requires appropriate licences and approvals, together with responsibilities around accurate information, customer data and invoicing. Have qualified advisers confirm what applies to your business and products. Building a website does not obtain those approvals for you.
Before a quote, identify the person authorised to approve business information, policies and operational decisions. Do not leave these decisions to whoever is configuring the storefront.
2. Define the complete Arabic / English journey
“Bilingual website” should identify the exact coverage. List the pages, catalogue fields and customer messages that need both languages, including:
- Navigation, search and product information
- Variant names, units, care instructions and specifications
- Cart, checkout, validation messages and account screens
- Order confirmations, delivery updates and return instructions
- Policies, support information and language-specific search metadata
Right-to-left presentation needs review, not just a direction switch. Check mixed Arabic/English names, numbers, phone fields, icons, product images and long labels. Test on a narrow mobile screen as well as desktop.
Appoint a qualified Arabic reviewer to approve terminology and cultural suitability. State who maintains both versions when products or policies change. Do not assume the development team also supplies Arabic translation or Arabic-speaking customer support.
3. Validate payments, AED and the full transaction lifecycle
Displaying a price in AED does not establish that the merchant can process and settle that payment. Confirm the provider’s eligibility rules, merchant account, supported currency, settlement arrangements and integration with the selected platform.
Ask the implementer to test more than a successful checkout:
- Successful and declined payments
- Interrupted checkout and a safe retry
- Delayed or repeated payment notifications
- Cancellation, full refunds and partial refunds where required
- Order status, receipt information and reconciliation
Keep sensitive payment handling with the approved provider and architecture. Do not copy customer card details into a CRM or general-purpose application log.
For Zoho Commerce, consult the current gateway and supported-country documentation. Its third-party payment integration FAQ also makes clear that an API is not a blanket promise that every gateway can be added directly. Obtain confirmation for the exact provider and setup before committing to it.
4. Specify shipping, address handling and returns
Document the delivery area, excluded locations, shipping charges, handling times and customer communications. Test representative addresses and the information a courier actually requires; do not assume a form designed for another country will fit unchanged.
The brief should establish:
- Whether shipping is flat-rate, rule-based or calculated through a provider
- Who creates shipping labels and arranges collections
- How dispatch and delivery status reach the customer
- Whether cash on delivery is offered and how exceptions are reconciled
- Who authorises returns, records returned stock and triggers refunds
Carrier access, commercial agreements and API credentials are dependencies, not features automatically included in a store subscription. Verify unsupported cases before launch and agree a documented manual fallback where appropriate.
5. Decide where stock and product information are authoritative
If the business sells through a store, warehouse, marketplace and website, identify which system controls available quantities and product data. A storefront should not become an accidental second inventory master.
Scope variant identifiers, units, locations, reservations, cancelled orders, returns and reconciliation. For subscriptions or other repeated orders, establish when stock is allocated and what happens when an item becomes unavailable.
An integration brief should name the source, destination, direction of synchronisation, frequency and failure owner. “Connect to ERP” is not enough. Migration also requires field mapping, cleaning rules, test imports and agreement on how totals or records will be reconciled.
Explore our existing CRM/ERP and ERPNext implementation offering when the operating problem extends beyond the storefront.
6. Select a platform against the requirements
Shortlist based on how the team will run the business, not the longest feature list.
Shopify
Evaluate a managed storefront when the intended workflows fit its supported checkout, apps and operating model. Confirm required features against the proposed plan, country setup, providers and recurring app costs. Separate theme work from integrations and paid extensions in the quotation.
Medusa.js
Consider a custom implementation when business-specific commerce workflows justify development and operating responsibility. Include hosting, deployment, monitoring, security updates, backups and engineering ownership—not just the initial storefront build.
Zoho Commerce
Consider it when the merchant’s catalogue, payment options and wider business-tool requirements fit the supported setup. Validate the edition, integrations, language requirements and API limits. Do not assume that a connector for another Zoho application is automatically a supported Commerce checkout integration.
Our Shopify–Medusa comparison explains operating costs, maintenance, migration and ownership trade-offs. Our ecommerce services include scoped Zoho Commerce implementation and customisation; no certified-partner status is implied.
7. Build privacy and accessibility into the scope
Map what each form, account, analytics tool, support channel and integration collects. Assign purposes, access, retention, vendor responsibilities and deletion workflows. Have the appropriate adviser assess applicable UAE and cross-border requirements; an Indian DPDP implementation is not a substitute for that assessment.
Keep optional analytics behind the agreed privacy controls. Prevent personal customer information from entering ordinary analytics URLs or events. Use synthetic or suitably de-identified data for demonstrations and test orders.
For usability and accessibility, check keyboard operation, focus, labels, error recovery, contrast, zoom, reflow and language handling in the agreed journeys. A language selector and an accessibility badge do not establish that the checkout is usable.
8. Agree launch evidence and handover
Require a written acceptance checklist covering catalogue samples, both language journeys, payments, shipping, stock behaviour, enquiries and administrative access. Include recovery procedures and the owner of each unresolved issue.
Separate the implementation price from hosting, licences, gateway fees, translations, third-party APIs, maintenance and future upgrades. Source-code delivery, reuse rights and ownership depend on the accepted proposal, applicable third-party licences and payment terms.
A useful handover identifies accounts, deployment notes, authorised administrators, backup and recovery arrangements, support windows and training. Delivery dates depend on the approved scope, access, content readiness and timely decisions.
A practical next step
Create a one-page brief with the merchant, markets, languages, product structure, providers, existing systems and top three operational problems. Mark what is confirmed and what still needs investigation. That is a stronger starting point than asking for a generic “UAE ecommerce website price”.
eLan Technology delivers this work remotely from Nagpur, India. We do not claim a Dubai office or use unrelated projects as UAE client references. See our UAE implementation approach or request a scoped proposal.
Already running a store? Review four checkout checks before your next promotion before investing in more traffic.