Storefront, explained

As a client admin, I invite my finance team and they see money, not content.

Staff sign in with Merit ID. Access is by invitation, with one of the seven roles in section 04.

• An account that was not invited is refused before sign-in.
• An invitation link expires.
• One person can hold roles in several clients with one account.
• Password reset by email link.

As Merit Ops, I stand up a new client store without an engineer.

A client workspace with a name, a unique subdomain and a region. Logo, favicon, colours and an Arabic-capable font.

• A new workspace is ready in under 60 seconds and starts in DRAFT.
• Lifecycle: DRAFT, STAGING, LIVE, SUSPENDED.
• A custom domain goes through Pending DNS, DNS Verified, SSL Provisioning, Live.
• Tiers gate what a client can use: Small, Medium, Large, Enterprise.

As Merit commercial, I decide which products a client may choose from.

LiveOps holds an allow list per client, per variant. It never puts a product on sale by itself.

• Merit allocates or removes single variants or a whole category in one action.
• The client sees the allowed pool, filtered by in a collection or in none.
• Removing a variant takes it off the store within 60 seconds.
• Merit reads an unused-allocation report. There is no rejected list, because there is no reject.

As a client admin, I build the store navigation and put products on sale by adding them to collections.

Two types: standard collections for merchandising, and category collections that form the store category tree. Merit sets the type. A brand is an ordinary collection.

• Category collections nest one level, with English and Arabic names.
• Manual sort order from 1 to 999. Default 999. It overrides any computed order.
• Inside a collection a product is Visible, Hidden or Featured. Up to six featured per collection.
• Products are ordered by the automated ranking, plus featured, plus the collection sort. No manual product rank.
• The store owns no category tree of its own. PIM keeps the product structure.

As a client admin, I name a product the way my members know it, without touching the master record.

Per-client display names, thumbnails and descriptions, in both languages. Special terms per product.

• The PIM master is never changed.
• Special terms are audited and capped at 3,000 characters.
• Variant-level images come from PIM.

As a client admin, I change a banner or a policy page without an engineering ticket.

Home and module banners, FAQ, a knowledge base, static pages, deals, maintenance windows and a site-wide notification bar.

• Static pages keep a version history and publish on their own.
• An FAQ can be placed on Home, Order History, Order Details or Product Details.
• A maintenance window has a start and an end time.

As a client marketer, I launch a promo code campaign and finance sees what it cost.

The portal is the screen for the Promo Engine: campaigns, codes, redemptions, and a reconciliation statement.

• A campaign is locked after the first redemption, except its limits.
• Bulk single-use codes with an export trail.
• Scope by tier, category or module: gift cards, merchandise, or both.

As client customer care, I find an order, resend the confirmation, and download the tax invoice.

Orders of this client only, searchable by order id and member id, with transaction, notification, audit and fraud tabs. A review queue holds orders waiting for a check.

• Cancel and reprocess are Merit operator actions only.
• Client staff mark an item reviewed, resend confirmations and download tax invoices.
• Login as customer is Merit operator only, and every session is logged.
• Test orders are excluded from every count. The portal never disagrees with the order record.

As the client fraud team, I look up a member and block them with a reason.

Find a member by exact id, see their orders and live points balance, fraud evaluations and order risk level.

• A masked personal field is revealed one at a time, and each reveal is logged.
• Allow or deny a member id, with a mandatory reason.
• Fraud rules and model tuning stay outside the portal.

As client finance, I can see the float balance.

A read-only float balance. Top-ups happen in LiveOps only.

• The portal never writes float.
• Al Fursan runs the invoice model: Merit bills converted Miles at period end, so it has no low-float warning.

As a client admin, my Arabic store is laid out for Arabic, not mirrored.

Every configurable field has an English and an Arabic input. Changes can be drafted, previewed on a private link, published and rolled back.

• Arabic renders right to left natively. A broken Arabic layout is a P0.
• Missing Arabic falls back to English, with a warning.
• Every change to collections, publishing and content is in an audit log that cannot be edited.

As a member, I use my airline login, and my cart is still there after I sign in.

The member signs in through the client own login. Profile and live points balance come with it.

• No guest checkout. Sign-in is asked for at checkout, and the cart is kept.
• A member id allow list can gate the store, which is also how canary cohorts are routed.

As a member, I find the product and see how many points it costs.

Home, mega menu, collections, product lists with sort and filters, search, and product pages.

• The variant selector disables combinations that are out of stock.
• The product page shows the points needed to pay in full.
• Only variants in a published collection appear anywhere.

As a member without quite enough points, I pay the rest by card.

A persistent cart. Pay with points only, card and Apple Pay, or a split on a slider.

• The slider is hidden when the points balance is zero.
• Pay with points is disabled when the balance is too low, and the balance is shown.
• The address is filled from the profile. A new address is saved only if the member asks.
• A variant removed from sale while in the cart shows as unavailable. The rest of the cart stays.

As a member, I track my parcel and reveal my gift card code safely.

Order history, order detail with the payment split, tracking for shipped orders, and cancel of an order or a single item.

• A gift card code is revealed only after an OTP.
• During a cooling-off delay the member sees a message, not a code.

As a member in Jeddah, I see only the iPhones that can reach me.

First, availability is resolved for Riyadh only. Then a city selector at the Apple Store entry filters what is shown.

• The city is a browse filter. The delivery address still decides fulfilment.
• Supplier order: STC, then Aleph, then Almanea. The price the member saw holds.
• the city selector waits for client approval.OPEN

As a member, I save the exact colour and size I want for later.

A wishlist per member, at variant level.