E-commerce
Ecommerce website development in Dubai: a shop people can finish.
You receive an online shop. The buyer sees the products, the price, the tax and the delivery, then pays. The server confirms the payment. The product in the window is an example of that counter. It is not for sale.
- The specimen is not for sale
- Card numbers stay with the provider
- The server confirms the payment
Specimen
North Yard
Linen set, sample 04
Shown so the counter has a shape. Not a Nexus product.
Price The price you list
In the bag
- Bag
- Pay
- Confirmed
- Receipt
Before the doors open
Six lines a checkout has to be able to say out loud
If any line below is still “we will decide later”, the shop is not ready. We write them in the quotation. A theme does not answer them.
The range
Which products are in, which are not, and who may add one. An empty catalogue with a placeholder price is not a launch.
The price
The amount on the product is the amount charged, unless a written rule says otherwise. A surprise at pay is a refund waiting to happen.
The tax
GST, VAT, or none — the treatment you already use, named before launch. We do not invent a rate, and we do not file the return for you.
The delivery
Where it ships, what it costs, and what the buyer is told when it cannot. A Gulf address and an Indian address are not the same rule unless you say they are.
The payment
The provider is named in the quotation. Card details stay there. This studio does not store card numbers. A browser “success” screen is not proof the money arrived.
The refund
Who may refund, in what window, and what happens to the stock. The rule is on the page the buyer can read, not only in a policy file nobody links.
What the buyer keeps
A receipt that matches the bag
After pay, the buyer should be able to point at one record: what they bought, the price, the tax line, the delivery, and that the server marked it paid. The slip below is a specimen of that shape. It is not a live charge.
Specimen receipt
Not a charge- Item
- Linen set, sample 04
- Price
- As listed on the product
- Tax
- The treatment in your brief
- Delivery
- The rule you signed
Paid when the server says so
Where the shop lives
Three honest shelves. Building is only one of them.
Some businesses need a catalogue on the site they already have. Some should stay on the platform they pay for. Some need a counter we build, because the tax, the delivery, or the stock will not fit that platform. The first note says which.
-
01
A catalogue, not a checkout
The buyer should see the range and then talk to you. WhatsApp or a form is the next step. Charging a card would be the wrong shop.
-
02
Keep the platform
You already pay for a shop that holds the catalogue and the pay button. The brief may be the theme, the tax line, or a connection — not a new store.
-
03
Build the counter
The range, the tax, or the delivery will not sit on the platform without a second copy of every product. Then the shop is the product. The quotation names the provider.
Indicative scope
Three briefs. The quotation is the only price.
A public rate would ignore your range, your tax, and whether the platform you already pay for should stay. These shapes help you brief. They are not a menu of store licences.
A catalogue
No card yet
The range, the prices, and a next step that is a conversation. Useful when charging a card would be premature.
Start with the rangeThe counter
The usual brief
Catalogue, bag, tax, delivery, a named payment provider, and a receipt the server can mark paid. Roles for who may edit a price.
Brief this scopeCounter and stock
After the first orders are real
The shop plus the stock book, so a sale and the shelf cannot disagree. Quoted after the counter has taken real orders, not before.
Brief this scopeBefore a price goes live
Questions that change the scope if the answer changes
Will you lock us to one shop platform?
No. The quotation names the platform you already pay for, or a counter we build. We do not hide a vendor behind our name, and we do not move you because a brochure looked tidy.
Do you store our customers’ card numbers?
No. Card details stay with the payment provider named in the quotation. Nexus Global Tech stores a payment reference when the brief asks for one, not the card number.
Is a thank-you page proof of payment?
No. The browser can show that page before the provider confirms the money. An order is marked paid when the server has checked the payment. That rule is written into the build.
Can the shop show GST or VAT?
Yes, when you tell us the treatment. We show the line you use. We do not choose a rate for you, and we do not file the return. The studio is in India. The primary market is the UAE and the Gulf, so both treatments come up in real briefs.
How is this different from a website?
A website explains the business and gives the visitor a next step. A shop lets that visitor take a product at a listed price, under a tax and delivery rule, and pay. If there is no pay button, the website page is the closer brief.
Can the shop be read in Arabic or Hindi?
Yes, when the brief asks. Product names can stay as you write them. The interface can be English, Arabic with right-to-left layout, and Hindi. Checkout labels are tested in those languages before the doors open.
Bring the range, not a wishlist of themes
A product list, the tax you use, and where you deliver is enough to start. You get a written note: this counter, this provider, this refund rule — or a recommendation to keep the platform, or to stay a catalogue.