An online business in Dubai needs more than a website and advertising. It needs a permitted activity, a clear offer, reliable payment handling and a way to deliver what the customer bought. This guide follows the order from the product page to delivery, support and reconciliation, so that growth does not conceal avoidable service problems or losses.
Define what you sell and confirm the permissions
Choose the customer, product or service, delivery geography and sales channel. Distinguish selling your own goods, operating a marketplace and providing professional services: the operating model determines which questions to ask the licensing authority. The UAE law on trading by modern technological means is a starting point, not confirmation that every online activity uses the same licence.
Do not assume all mainland businesses require a local majority shareholder or all free-zone businesses are tax-exempt. Verify ownership, activity permissions, sector approvals and trading arrangements for the actual model. The UAE business setup guide connects these decisions with launch readiness.
Make the product page and checkout agree
State what is included, important exclusions, total payable charges, availability, delivery area and the process for cancellation or returns. Use language customers can understand. Ensure that an Arabic page and its English counterpart describe the same product, conditions and commitments. Do not translate a delivery promise more generously in one language.
Test the full journey on a phone: find the product, select an option, understand the cost, enter an address and obtain confirmation. Check failed payments and unavailable items as carefully as successful purchases. Avoid accepting an order that the stock or delivery system cannot fulfil.
Separate payment success from order completion
Use an appropriate payment provider and check its onboarding, settlement, refund and dispute procedures. Authorisation confirms approval to proceed with a payment; capture submits the approved amount for collection. Settlement transfers funds to the merchant account under the provider’s arrangements. These are different events, and none proves that the order was delivered. Reconcile provider records with orders and bank receipts, including fees and refunds.
Restrict administrative access and protect customer information. Collect only the data needed for the defined purpose, publish an accurate privacy notice and review applicable data-protection obligations with qualified advice. Do not claim compliance with a named law merely because the website has encryption or a privacy page.
Give each order a traceable status
| Stage | Required evidence |
|---|---|
| Confirmed | Correct item or scope, price, address and customer confirmation |
| Prepared | Stock allocated or service resources scheduled |
| Dispatched | Carrier reference and evidence that the shipment was handed over |
| Delivered or completed | Evidence of customer delivery or completion of the agreed service |
| Return or refund in progress | Approved decision, responsible owner and current processing status |
| Closed | Resolution completed and relevant financial records reconciled |
These are suggested operating labels, not legal categories. Assign an owner to exceptions such as missing stock, a failed delivery or a disputed charge. Keep the customer informed using verified information rather than automatic promises the team cannot meet.
Check whether the order contributes to overheads
Contribution is revenue less variable costs: the amount available to cover fixed costs before any remaining profit. Hypothetical example for illustration: suppose net revenue is AED 200 and directly attributable variable costs are AED 150. The contribution is AED 50 before fixed overheads and other excluded items. This fictional calculation is not net profit. State whether product cost, payment fees, fulfilment, returns and acquisition costs are included before comparing orders.
Track completed orders, cancellations, returns and collection alongside visits and conversion rates. A campaign can increase sales while worsening contribution or service delays. Separate new and repeat customers when that distinction affects the decision, and avoid counting the same order twice across marketing platforms.
Rehearse an order that cannot be fulfilled
Hypothetical example for illustration: test a case in which a customer pays for an item that the warehouse cannot supply. Assign one order reference to the payment, stock exception, customer communication and resolution. The purpose is to expose gaps between teams before increasing order volume. A payment record alone must not cause the system to mark the item as dispatched. Keep the original order when creating corrective records so the reviewer can follow the full history.
First, verify the payment status with the provider and check whether alternative stock is actually available. Ask the authorised service owner to determine the available resolution under the applicable terms and requirements. Do not substitute a different product or promise an unconfirmed delivery date without the necessary customer agreement. Record the decision, unresolved questions and the person responsible for carrying it out. If that person is unavailable, use the agreed escalation route instead of leaving the order without an owner.
If a refund is approved, distinguish the request from provider processing and confirmed completion. Keep the customer informed with the status you can substantiate. Reconcile the amount, fees and any inventory adjustment; do not close the case merely because support has sent a message. A second reviewer should be able to follow the evidence without reconstructing the case from unrelated chat conversations.
After the test, identify the cause and a corrective action: stock synchronisation, an unclear handover or an unavailable decision owner. Repeat the affected step and record whether the correction worked. These are suggested operating controls, not a statement of a universal statutory refund period. Use the findings to decide which products and order volumes the team can support reliably. Recheck when the warehouse, payment provider or fulfilment method changes.
Launch a limited operation and learn from exceptions
Test a real permitted transaction end to end, including support and a controlled refund test where appropriate. Confirm that inventory, notifications and accounts agree. Review the reasons for failed orders before buying more traffic. Set realistic delivery commitments using demonstrated capacity.
ATMACSS business and operations modelling can help define responsibilities and handovers behind the storefront. The next step is an order walkthrough with the people responsible for payment, fulfilment and support, followed by a dated list of issues to resolve.

