This chapter is everything in front of the till, and everything it saves you from:
the shopper who cannot find the right abaya, the product page that leaves her questions
unanswered, the promotion nobody notices. It covers the homepage, browsing, search and filters,
the product page itself, and the content, popups and promotions you place around them, all
arranged by you from the admin.
The problem: a shop stitched together from disconnected
screens loses shoppers at every seam. Each time she has to guess where to go next, or falls out
of her language halfway through, she simply leaves.
From the first visit to a delivered order, the storefront is one continuous path. A
shopper lands on the homepage, browses or searches to find a piece, opens its product page, picks
their size and any add-ons, drops it in the bag, checks out, and then follows the order through to
delivery from their account. Every step works in the shopper's chosen language and currency.
In practice
Imagine a first-time visitor in Doha who saw one of your embroidered abayas on Instagram and lands on the shop to buy it as an Eid gift.
How Angelite handles it: she arrives on the homepage in Arabic with prices in Qatari riyals, taps into the abaya's product page, picks her size, adds it to the bag, and pays at checkout. Afterwards she opens her account to watch the order move from confirmed to shipped to delivered, never once leaving her language or currency. Every page along that path is one you arranged from the admin.
How to use it
Discover. The shopper arrives on the homepage and sees the hero, featured
collections and any promotions you have placed.
Browse and filter. They open the product listing, a category or a collection,
then narrow it down with the filter sidebar, sorting and search.
Open a product. A product page shows the gallery, description, price, sizes,
add-ons, size chart, reviews and "you may also like" suggestions.
Add to bag. They choose a size and any add-ons and add the item to the cart.
Check out. They review the bag, enter delivery details, and pay (covered in
Chapter 03).
Track the order. They follow the order from their account as it is confirmed,
shipped and delivered (covered in Chapters 05 and 06).
Where: the homepage, the shopper's first impression of the shop.Where: a product page, where the shopper chooses a size and adds to the bag.
Good to know: the storefront is the public shop. The pages and
promotions a shopper sees are all built and arranged by you from the admin, with no developer
needed.
Homepage
Customer
The problem: seasons move faster than a fixed homepage. If
refreshing your front door needs a developer, Ramadan arrives while the shop still leads with
last season's edit.
The shop's front door, composed from arrangeable content blocks: a hero, featured
collections and product picks, and any marketing bands you add. You control the whole layout from
the admin, so the homepage can change for a season or a sale on your own schedule, without any
code, and always looks freshly curated.
In practice
Say Ramadan is approaching and you want the homepage to lead with your gift-ready embroidered kaftans instead of the usual everyday abayas.
How Angelite handles it: from the admin you swap the hero image, point the featured collection block at your Ramadan gift edit, and add a promotional band announcing free gift wrapping. The moment you save, every shopper who opens the shop sees the new front door, and you switch it back the same way once the season ends, with no developer involved.
How to use it
The shopper opens the site and lands on the homepage.
They see the hero image, featured products and collections, and any promotional bands.
They click into a product, a collection or a banner link to start shopping.
Where: the homepage at the root of your store.
Related: the homepage is built from content blocks; see CMS pages
below and Chapter 10, Content & CMS, for the full block builder.
Product listing
Customer
The problem: a shopper who wants a black abaya in size 54
under 400 riyals will not scroll through three hundred products to find it. She gives up, and
you never even know she was there.
The main browse page where shoppers explore everything for sale. They can sort the
grid, page through results, and narrow it down with a filter sidebar covering categories,
collections, tags, colours, sizes, rating and price, so anyone lands on exactly what she wants
in a few taps.
In practice
A customer is hunting for a black abaya in size 54 under 400 riyals and does not want to scroll through the whole catalog to find it.
How Angelite handles it: on the products page she ticks black in the colour filter, 54 in the size filter, and drags the price slider to her budget, and the grid narrows to just the matching abayas. She sorts by lowest price and pages through the short list. Because the filters live in the web address, she can copy that link and send it to a friend, who opens the very same filtered view.
How to use it
The shopper opens the products page from the menu.
They tick filters in the sidebar (for example a colour, a size, or a price range) to narrow the grid.
They change the sort order (newest, price, name) and page through the results.
The chosen filters stay in the web address, so the filtered view can be bookmarked or shared.
Where: the products page, with the filter sidebar on the side.
Good to know: the sidebar only shows filters that actually exist in
your catalog, and paging through results keeps every active filter in place.
Product detail page
Customer
The problem: this page is where the sale is won or lost. If
the photos feel small, the fit is unclear or the stock position is vague, the shopper leaves to
find answers elsewhere and rarely comes back.
Where a shopper decides to buy. A swipeable photo gallery with a strip of thumbnails
lets her flick through every angle; on a computer, hovering over a photo zooms in for a closer
look at the detail, and tapping any photo opens a full-screen view she can page through with
arrows, a swipe, or the keyboard. Below the gallery sit the description and price, the size
selector and any optional add-ons, a size chart to help her choose, customer reviews, and a
"you may also like" set of related products. If the size or add-on she wants is out of stock, the
page says so plainly and the add-to-bag button stays disabled until she picks something available.
In practice
A customer loves one of your hand-embroidered abayas but wants a closer look at the beading before deciding on her size.
How Angelite handles it: on her phone she swipes through the gallery photo by photo; switching to her laptop later, she hovers over her favourite shot to zoom in on the beadwork's detail, then taps it to open a full-screen close-up she can page through. She checks the size chart, picks size 54, ticks the gift-box add-on, and watches the price update before adding the abaya to the bag. Below, she reads a few reviews and glances at the "you may also like" pieces before checking out, all on the one page.
How to use it
The shopper clicks a product anywhere on the storefront to open its page.
They swipe or hover through the gallery, and tap any photo to open a full-screen close-up.
They pick a size (checking the size chart if needed) and select any add-ons; the price updates. If their choice is out of stock, a clear notice appears and adding to the bag is blocked until they pick one that is available.
They add the item to the bag, and can scroll on to read reviews and explore recommended products.
Where: a product page, opened from any product link.
Good to know: only Active products have a public page. Drafts and
archived products are never reachable by shoppers.
Instagram in-app layout
CustomerOptional · Instagram In-App Layout
The problem: most taps on your story links open inside
Instagram's own cramped little browser, where a slow, cluttered page kills the impulse to buy
before the photos even load.
A simpler, faster version of the product page, shown automatically when a shopper
opens your shop from a link inside Instagram. It keeps just the essentials, the photos, the
price and add-to-bag, so the page loads quickly and fits comfortably in that small window.
In practice
Say you post a new ready-to-wear abaya to your Instagram story with a link, and most of the taps come from people still inside the Instagram app.
How Angelite handles it: when a follower taps that story link, the page opens inside Instagram's own narrow browser and the shop automatically shows the simpler page, with the photo, price and add-to-bag but without the full site's menus and extras. It loads quickly in that small window, so the impulse to buy is not lost to a slow or awkward page.
How to use it
A shopper taps a product link in your Instagram profile or a story.
The link opens inside Instagram's built-in browser.
They automatically see the simpler, faster product page, sized for that small window.
Optional feature: switch the Instagram layout on or off under
Settings → Features. When it is off, every shopper sees the standard product page.
Quick-add
CustomerOptional · Quick Add
The problem: a regular restocking three of her usual abayas
has to open every product page in turn, and each extra step is another chance for the order to
be abandoned halfway through.
Lets a shopper add a product to the bag straight from its card on a listing, without
opening the full product page. A small dialog lets them pick the size and any add-ons right there,
so a repeat buyer can fill a bag in a few taps.
In practice
A regular customer is restocking her favourite everyday house abayas and wants to grab three of her usual size quickly without clicking into each one.
How Angelite handles it: as she scans the listing she taps the quick-add control on each abaya card, and a small panel pops up where she picks the size and quantity right there. She confirms, the abaya drops into the bag, and the listing stays exactly where it was so she can move straight to the next card, building her order in a few taps.
How to use it
While browsing a listing, the shopper taps the quick-add control on a product card.
A small panel opens to pick size, quantity and any add-ons.
They confirm, and the item is added to the bag without leaving the listing.
Where: on product cards in any listing, when Quick-add is on.
Optional feature: switch Quick-add on or off under
Settings → Features. When it is off, the control simply does not appear.
Category & collection browsing
Customer
The problem: how a shopper arrives should decide what she
sees. A Ramadan banner that dumps her into a wall of unrelated products, or a menu with no way
to survey the whole range, both end in the back button.
Every category and every collection gets its own browsable page, showing just the
products that belong to it: the focused entry points shoppers reach from the menu, the
homepage, or a promotion. The storefront also has two automatic index pages, one listing every
department and one listing every collection, each as an elegant grid that updates itself the
moment you add or retire one, so there is nothing for you to maintain. Like every storefront
page, they are built from blocks, so their look can be restyled from the page templates without
code.
In practice
A customer only wants to see your embroidered abayas, another arrives from a homepage banner promoting your "Ramadan Edit" collection, and a third simply wants to see everything you group your abayas into.
How Angelite handles it: the first shopper picks Abayas, then the embroidered category from the menu and lands on a page showing only those pieces. The second clicks the banner and arrives on the Ramadan Edit collection page, which lists just the pieces you grouped into it. The third opens the "all categories" page and scans every department at a glance before choosing where to dive in. All three browse a tidy, focused page, and because the two index pages build themselves from your catalogue, the department you added yesterday is already listed, with nothing for you to update.
How to use it
The shopper picks a category from the navigation menu, a collection from the homepage, or opens the "all categories" / "all collections" page to browse the full list.
They land on a page listing only that group's products (or, on the "browse all" pages, every category or collection as a grid that keeps itself up to date).
They browse and click through to a product just as on the main listing.
Where: a category page, one per category in your catalog.Where: a collection page, one per collection in your catalog.Where: the browse-all page at /categories, which lists every department by itself; /collections does the same for collections.
Search
Customer
The problem: a shopper who knows exactly what she wants will
give the search box one chance. If it comes back empty or ignores her Arabic, her next search
happens on Google, on someone else's shop.
Lets a shopper type what they are looking for and get matching products instantly.
Search works in the shopper's own language, and the results can be narrowed with the same
filters as the listing, so she finds the piece in seconds.
In practice
A customer browsing in Arabic remembers seeing a chiffon evening kaftan and types the Arabic word for kaftan into the search box.
How Angelite handles it: she types the term in the header search box and a grid of matching kaftans appears at once, matched against the Arabic product names. She then ticks a price range in the same filter sidebar she would use on the main listing to trim the results, and clicks into the kaftan she had in mind, all without scrolling the full catalog.
How to use it
The shopper types a word or phrase into the search box.
Matching products appear in a results grid.
They refine the results with the filter sidebar and sorting, then click into a product.
Where: the search results page, reached from the header search box.
Recommendations
Customer
The problem: in the boutique you would mention the matching
hijab at the till. Online nobody makes that suggestion, so the abaya sells alone and the rest
of the set stays on the shelf.
Surfaces similar and frequently-bought-together products on the product page, so a
shopper discovers the right next item at the exact moment she is already reaching for her card.
Your hand-picked product relations always come first, topped up automatically when there are not
enough.
In practice
Say a shopper is about to buy a single black abaya, and you would love her to notice the matching hijab that completes the set.
How Angelite handles it: on the abaya's page she sees a "you may also like" row that leads with the matching hijab you hand-picked as a related product, followed by a few similar pieces the shop fills in automatically. She taps the hijab, adds it too, and her basket grows because the suggestion was right there at the point of decision.
How to use it
The shopper opens a product page.
Below the product they see a "you may also like" set of related items.
They click any suggestion to jump to that product.
Where: the "you may also like" area on a product page.
Related: you set the hand-picked links in the product editor; see
Product relations in Chapter 01, Catalog.
Submit a review
Customer
The problem: your buyers quietly learn that a style runs a
touch small, but that knowledge never reaches the next customer, so the same wrong-size order
keeps happening.
Lets a signed-in customer rate a product and write a review, with an optional note on
fit, the size they bought and their city, plus up to five photos. Reviews from a verified purchase
get a verified badge once published, so future customers order the right size the first time.
In practice
A customer in Kuwait who bought one of your ready-to-wear abayas last month wants to tell others it runs a touch small and share a photo of how it looks.
How Angelite handles it: signed in to her account, she opens the reviews area on that abaya's page, gives it four stars, writes a few lines, notes that the fit is snug and adds her city and the size she bought, then attaches two photos. She submits, and the review waits for your approval before going live, where it will carry a verified-purchase badge because she truly bought it.
How to use it
A signed-in customer opens the reviews area on a product page.
They give a star rating and write their review.
They can optionally add fit and size details, their city, and up to five photos.
They submit; the review goes to you for approval before it appears publicly.
Where: the reviews area on a product page.
Good to know: each customer can review a product once, and you approve
or reject reviews before they go live (see Reviews moderation in Chapter 01, Catalog).
Review feed
Customer
The problem: a hesitant shopper eyeing a higher-priced piece
wants proof from buyers like her. If she cannot find it on the page, she goes looking for
reassurance elsewhere and does not come back.
The published reviews shown on a product page: an at-a-glance summary plus a feed a
shopper can filter and sort, load more of, mark as helpful, and report if something looks off. It
lets other buyers' honest experience close the sales that doubt would otherwise lose you.
In practice
A cautious shopper deciding on a higher-priced made-to-order wedding abaya wants to read what real buyers say, especially anyone who flagged a problem.
How Angelite handles it: she scrolls to the reviews area, reads the star summary at the top, then filters to the lower ratings and sorts by newest to see recent concerns. She finds one review with photos especially useful and taps the helpful button, and when she spots a comment that looks like spam she reports it for your team to check, then buys with confidence.
How to use it
The shopper scrolls to the reviews area on a product page.
They read the rating summary, then filter and sort the feed and load more reviews.
They mark reviews as helpful, or report a review that breaks the rules.
Where: the reviews area on a product page.
Announcements
Customer
The problem: your free-delivery week ends Friday, but a notice
posted only on the homepage misses every shopper who lands straight on a product page from
Instagram.
Short text strips you can pin to the very top or the very bottom of every page, for
things like free-shipping notices or sale dates. When more than one is live, the strip gently rotates
through them, and shoppers can dismiss a strip you mark as dismissible, so your most time-sensitive
offer is seen no matter which page a shopper lands on first.
In practice
Say you are running free delivery across Qatar this week and also want to remind shoppers your Eid sale ends Friday.
How Angelite handles it: you create both messages as announcement strips and pin them to the top of every page. Because two are live, the strip quietly rotates between the free-delivery line and the Eid-sale countdown, so a shopper sees both as they browse. You mark the strips dismissible, so anyone who has read them can close them and keep shopping without the reminder following them around.
How to use it
The shopper sees the strip on every page, at the top or bottom of the screen.
If several are live, the strip rotates through them automatically.
They can close a dismissible strip, and it stays hidden for them.
Where: the announcement strip at the very top of the page.
Where to set it: create and schedule announcements under
Content → Announcements. Only live, in-schedule strips ever reach shoppers.
Pages & content
Popups
Customer
The problem: a visitor browses, hesitates and leaves, and you
are left with no email, no sale and no way to reach her again. Yet a popup that nags on every
visit drives away the shoppers who stayed.
An overlay you can show shoppers to promote an offer or capture signups. You control
where it appears, when it appears (as the page opens, after a few seconds, when she scrolls, or as
she is about to leave) and how often it may show again, so it never becomes a nuisance.
In practice
Imagine you want to offer first-time visitors ten percent off their first abaya in exchange for their email, but only catch them when they are about to leave.
How Angelite handles it: from the admin you build a popup with your image, the discount message and an email field, and set it to appear just as the shopper is about to leave the page. You cap it so it only shows once a week per person. A browsing visitor who drifts toward the close button sees the offer appear, drops in her email to claim the code, and is not pestered with it again on her next visit.
How to use it
The shopper browses the storefront as normal.
At the moment you chose, the popup appears with your image, message and optional button.
They act on it or close it; your frequency rule decides when (if ever) they see it again.
Where to set it: build and schedule popups under
Content → Popups. Only one live popup shows at a time, by priority.
Banners
Customer
The problem: your new bridal collection is live, but shoppers
only find it if they think to dig through the menu. A launch with no visual push might as well
be invisible.
Promotional image bands you place in fixed spots around the storefront: a strip above
the header, the homepage hero and content bands, and spots near the footer. Each banner can link to a
product or category, and every link is checked to be safe before it reaches shoppers.
In practice
Say you have a new bridal collection and want a striking image band across the homepage that sends shoppers straight to it.
How Angelite handles it: in the admin you upload a banner image, point its link at the bridal category, and place it in the homepage hero spot. You add a separate, smaller banner for the strip above the header too. Shoppers see the band as they browse and tap it to land on the bridal pieces, and you reorder or switch off any banner from the same screen, with every link checked to be safe before it goes live.
How to use it
The shopper sees the banner in its spot as they browse.
They click it to follow its link to a product or category.
You decide which banners are active and in what order from the admin.
Where to set it: manage banners, and where each one shows, under
Marketing → Banners. Each banner can carry a desktop, tablet and mobile image.
CMS pages
Customer
The problem: a marketing idea, a fabric guide, a campaign
page, arrives on Tuesday. If publishing it means briefing a developer, it ships next month or
never.
Custom content pages you build with a drag-and-drop block editor, for things like a
lookbook, a campaign page or a guide. Each page gets its own web address and is shown to shoppers once
you publish it, so an idea can go live the day you have it.
In practice
Imagine you want a "Fabric guide" page that explains the story behind each fabric you use, from crepe to silk-blend, to share on social media.
How Angelite handles it: in the admin you build the page by dragging in headings, paragraphs and a gallery of fabric close-up photos, then arranging them until it reads well. The page gets its own web address you can post anywhere. While you are still working it stays a hidden draft, and only when you hit publish does it appear to shoppers, all without touching any code.
How to use it
The shopper opens a content page from a menu link or a banner.
They read the page, which is laid out from headings, text, images, galleries and other blocks.
You build and publish these pages from the admin with no code.
Where: a published content page on the storefront.
Related: the full block builder is covered in Chapter 10, Content &
CMS. Drafts stay hidden until you publish.
Legal pages
Customer
The problem: the last question before paying is usually "can I
return it?". A shop where the returns policy is missing or unfindable answers that question with
silence, and the shopper does not pay.
A fixed set of policy pages every shop needs, such as privacy, terms, returns and
shipping. They use the same block editor as other pages, come pre-filled with starter text, and are
linked from the footer, so every shopper gets clear, in-language answers before she pays.
In practice
A customer about to buy a made-to-order embroidered abaya wants to check whether she can return it if the length is wrong before she pays.
How Angelite handles it: she clicks the Returns link in the footer and reads your returns policy on its own tidy page. You had already adjusted the starter wording in the admin to spell out your fourteen-day window for unworn pieces, so she sees clear terms in her own language. These policy pages always exist and cannot be deleted or renamed, so a shopper never hits a missing-policy dead end.
How to use it
The shopper clicks a policy link in the footer (for example Privacy or Returns).
They read the policy page, with the heading shown above your content.
You edit the wording from the admin; these pages cannot be deleted or renamed.
Where: a legal page, such as the privacy policy, linked from the footer.
Related: the home, about, contact, and legal pages are all edited from one
consolidated admin section; see "Front pages & legal pages" in Chapter 10, Content & CMS.
About page
Customer
The problem: to a first-time visitor you are just another shop
in an endless feed. With nowhere to meet the people and the story behind the label, trust has
nothing to grow on.
Your brand-story page, where shoppers learn who you are and what you stand for. It is
built from the same content blocks as any other page, so you can shape it however you like and turn
a first-time browser into a returning customer more often.
In practice
A customer who likes to know the maker behind her clothes wants to read how your boutique began and where your fabrics are sourced.
How Angelite handles it: she opens the About page from the footer and reads your story, which you laid out from the admin with a header image, a few paragraphs about the family workshop, and photos of the embroidery being stitched. Because it uses the same content blocks as any page, you can refresh the story or add a new founder photo whenever you like, helping her trust the brand before she buys.
How to use it
The shopper opens the About page from the menu or footer.
They read your story, laid out in your own content blocks.
You edit it from the admin under the Front Pages section.
Where: the About page on the storefront.
Sitemap page
Customer
The problem: somewhere on your site is the exact page a lost
shopper wants, and search engines need to find every page of your catalogue too. Without one
tidy directory, both wander.
A human-friendly navigation hub that lists the main shop links, all your categories and
collections, and your content pages in one place. It gives shoppers (and search engines) an easy
overview of everything on the site, so you never lose traffic to poor navigation.
In practice
A shopper knows you sell made-to-order kaftans somewhere but cannot find them in the menu, and you also want search engines to index every category.
How Angelite handles it: she opens the sitemap page from the footer and sees a clean directory of every shop link, category, collection and content page in one view. She spots the kaftans category in the list and clicks straight to it. The same tidy overview helps search engines find all your pages, so your abayas, collections and guides are easier to discover from a Google search too.
How to use it
The shopper opens the sitemap page, usually from a footer link.
They see a tidy directory of shop links, categories, collections and pages.
They click any entry to go straight there.
Where: the sitemap page on the storefront.
Contact form
Customer
The problem: a visitor with a pre-purchase question and no
account has no way to ask it, so the question, and the order that hung on the answer, walk
away.
A public contact form any visitor can use to message the store, no login needed. A
submission lands in your store inbox so staff can reply directly by email, and the form quietly
keeps automated junk out, so what reaches you is real questions.
In practice
A visitor wants custom embroidery placement on a made-to-order abaya for an anniversary and has a question before ordering, but she has no account.
How Angelite handles it: she opens the contact page, fills in her name, email, the subject "Custom embroidery" and her message, then submits. She sees an on-page thank-you, and the message lands in your store inbox so a staff member can reply straight to her email from their usual mail client. The form quietly turns away automated junk, so your inbox gets her real question and not a flood of spam.
How to use it
The visitor opens the contact page.
They fill in their name, email, an optional subject and their message, then submit.
They see an on-page confirmation, and the message lands in your store inbox.
Where: the contact page on the storefront.
Good to know: replies go straight to the visitor's email, so staff can
respond from their usual mail client.
Newsletter signup
Customer
The problem: a list padded with typos and throwaway addresses
quietly poisons your sender reputation, until the campaign you actually care about starts
landing in spam folders.
Lets shoppers subscribe to your marketing emails, with one safeguard: they click a
confirmation link in an email first, so only addresses that are real, and really theirs, ever join
your list. Every marketing email carries a one-click unsubscribe, and the whole newsletter can be
switched off site-wide.
In practice
A shopper loves your new-arrivals and wants an email whenever fresh abayas land, and you want to be sure the address she gives is really hers.
How Angelite handles it: she types her email into the newsletter form on the storefront and gets a confirmation email, then taps the link inside it to finish joining. Only after that confirming click is she added to your list, which keeps fake or mistyped addresses out and protects your sender reputation. Every newsletter she later receives carries a one-click unsubscribe, so she always feels in control.
How to use it
The shopper enters their email in the newsletter form.
They receive a confirmation email and click the link to confirm.
They are now subscribed, and can unsubscribe with one click from any email.
Good to know: no marketing email is ever sent to an address until it
has confirmed, which protects your sender reputation. The admin newsletter tools sit behind the
email system feature.
Bounce / complaint suppression
Customer
The problem: keep emailing an address that no longer exists,
or someone who marked you as spam, and the big mail providers start quietly treating everything
you send as junk.
Addresses that do not exist, or that complained about your mail, are taken off your
list automatically, so your emails keep landing in inboxes. Your email provider reports the
undeliverable address or the complaint back to the store, and that address is quietly skipped from
then on, with nothing for you to do.
In practice
Say one subscriber closed her old email account and another grew tired of your sale emails and marked one as spam.
How Angelite handles it: when your next campaign goes out, the closed account's email comes back undeliverable, and the annoyed shopper's complaint is reported back by your email provider. The shop takes both addresses off your list automatically, so future campaigns skip them and the emails that matter keep reaching real inboxes, with nothing for you to clean up by hand.
What it means for you
A subscriber's address comes back undeliverable, or they mark an email as spam.
Your email provider reports it back to the store.
That address is taken off your list automatically and skipped by future campaigns, with no action needed from you.
Good to know: this runs behind the scenes to keep your emails landing
in inboxes. Once an address is taken off the list it stays off marketing sends unless the person
subscribes again.
Locale & currency switchers
Customer
The problem: a visitor who must convert prices in her head, in
a language she reads slowly, is doing arithmetic instead of shopping, and unfamiliar money is
one of the quietest reasons a full bag gets abandoned.
Controls in the header that let a shopper switch the site language or the currency
prices are shown in. Both follow the shopper across the whole shop, and the prices recalculate
instantly to the chosen currency, so she browses and checks out in the language and money she
thinks in.
In practice
A visitor from Saudi Arabia prefers reading in Arabic and wants to see abaya prices in her own Saudi riyals rather than the Qatari riyals the shop shows by default.
How Angelite handles it: she opens the language control in the header and picks Arabic, and the whole shop reloads right-to-left in her language. She then opens the currency control and chooses Saudi riyals, and every price across the catalog instantly re-prices into her riyals. Both choices follow her from page to page, so the abaya she finally adds to the bag shows the same familiar language and currency all the way to checkout.
How to use it
The shopper opens the language or currency control in the header.
They pick a language or a currency from the list.
The shop reloads in that language, or re-prices everything in that currency.
Where: the language and currency controls in the header.
Where to set it: the available languages and currencies are managed
under Settings → Languages and Settings → Currencies.