The gold Nota Paris signature beside an embossed treble clef on burgundy leather.

A DIGITAL FLAGSHIP, COMPOSED WITH PURPOSE

Shopify Plus Agency Brief

Working brief · 29 October 2026Begin the brief

Nota Paris translates emotion into scent. Our ecommerce flagship must carry that same identity into every digital encounter — from the first discovery to the moment a fragrance arrives.

The brand universe · An introduction for our agency partners

NOTA PARIS / 01 · SHOPIFY PLUS

A distinctive experience.
A dependable business.

Create a Shopify Plus store that brings Nota’s musical universe to life, helps customers find their note and supports a complete purchase and service journey.

A close study of Nota’s gold sculptural bottle frame.

THE MAISON

French artistic perfumery,
composed around music.

Nota Paris connects emotion, music and fragrance through sculptural bottles and a collection named Do, Ré, Mi, Fa, Sol, La and Si.

Founder: Hassan Abdelbaki.

The site should express craftsmanship, provenance and personality, then make the collection easy to shop.

Use approved founder, perfumer and Made in France copy. Confirm Si’s launch status and sellable assortment.

Audience

Who we want to reach

Proposed priority audiences, to validate with campaign and customer data.

AudienceCustomer needWebsite response
Niche fragrance enthusiastsUnderstand the scent and its character.Notes, perfumers, composition, credible reviews.
Luxury and design buyersDiscover a distinctive personal object.Bottle details, craftsmanship and editorial imagery.
First-time Nota customersChoose confidently without smelling online.Find Your Note, samples and redeemable sets.
Gift buyers and returning clientsChoose well and purchase with confidence.Gifting guidance, delivery clarity and easy reorder.

Prioritise intent and behaviour. Do not assume an age, gender split or customer acquisition cost without evidence.

Implementation notes & source context
Audience segmentation is a recommendation for agency planning, not validated research. Launch focus follows the UAE/GCC strategy in the 22 October kickoff.

Objectives

What success should look like

Agree numeric targets after the agency reviews traffic plans, margins and the operating model.

Business objectivePrimary measureImplication for the build
Profitable direct salesNet sales and contribution per orderReliable checkout, transparent charges, lean app costs.
Discovery that convertsSet-to-60 ml conversion at 30 / 60 / 90 daysTrack linked orders and redemption cohorts.
Confident mobile shoppingPurchase conversion and checkout completionFast pages, readable prices and fewer friction points.
Long-term customer valueRepeat purchase, retention and opt-in growthOwned customer data and relevant lifecycle journeys.
Reliable serviceOn-time delivery and support resolutionAccurate stock, tracking and operational alerts.

Paid media spend, revenue targets and contribution definitions require Nota approval. The agency must not promise conversion uplift.

Implementation notes & source context
Source: Nota_Paris_Ecommerce_Meeting_Minutes_22Oct2026.docx, 22 October 2026. The working launch target and operating model remain subject to final approval.
Contribution should be defined with Ganesh: sales net of discounts, refunds and tax less product, fulfilment, delivery subsidy, payment and acquisition costs. Reconcile credited purchases to avoid overstating revenue.

NOTA PARIS / 02 · SHOPIFY PLUS

UAE first.
Built to travel.

A GCC launch with one Nota-controlled brand experience and a clear path to France and Europe.

Markets & localisation

UAE first, built for expansion

One Nota-controlled brand experience and customer database.

StageCommercial modelAgency requirement
Launch: UAE serving GCCUAE, Saudi Arabia, Kuwait, Qatar, Bahrain and Oman, subject to readiness.Country rules for checkout, payments, delivery, taxes and product availability.
Next: France serving EuropeFrance operation and fulfilment subject to entity and logistics readiness.Compare one-store multi-entity eligibility with separate stores and shared standards.
Selective international salesOnly destinations approved for perfume shipment and service.Block unsupported destinations. Show full charges before order placement.

Recommended quote baseline: English + Arabic with RTL at launch. French is a separate Europe phase; final language approval remains open.

Implementation notes & source context
Source: Nota_Paris_Ecommerce_Meeting_Minutes_22Oct2026.docx, 22 October 2026. The working launch target and operating model remain subject to final approval.
Shopify Help, accessed 29 October 2026: https://help.shopify.com/en/manual/markets/customizations/local-currencies ; https://help.shopify.com/en/manual/international/payments ; https://help.shopify.com/en/manual/payments/shopify-payments/onboarding/selling-with-multiple-entities
Local language, tax, currency, stock and legal requirements require market-by-market configuration. Do not equate a currency converter with local-currency checkout. Domain, subfolder and canonical URL approach must form part of the agency recommendation.
ScopeLaunch scope and later phases

Agencies should price the launch scope as a complete working store.

PriorityIncluded capabilityQuotation treatment
Launch essentialsBranded responsive store, catalogue, discovery, samples, redemption, cart and checkout.Fixed scope with acceptance criteria.
Launch operationsPayments, shipping, tax setup, 3PL flow, service, CRM, analytics, consent and SEO.Name each integration and dependency.
Launch enrichmentFind Your Note quiz, verified reviews, gifting message, wishlist and store locator.Itemise delivery method and app cost.
Later phase / separate quoteFrance/EU operation, advanced loyalty, subscriptions, wholesale portal and POS.No implied inclusion. Quote only if proposed.

Paid acquisition management, ongoing content production and legal/tax advice require separate scope. Initial setup and handover remain in scope.

Implementation notes & source context
Priority classification is a proposed procurement baseline. Agencies must mark each requirement as included, optional, excluded or dependent on Nota approval. A discovery quiz can launch as a clear rule-based tool; AI recommendations are not required.

NOTA PARIS / 03 · SHOPIFY PLUS

Seven notes.
One composition.

A clear offer across full-size fragrances, individual discovery and sets. Working USD retail references; local price books require approval.

Nota Do sculptural fragrance bottle.
Do
Nota Ré sculptural fragrance bottle.
Ré
Nota Mi sculptural fragrance bottle.
Mi
Nota Fa sculptural fragrance bottle.
Fa
Nota Sol sculptural fragrance bottle.
Sol
Nota La sculptural fragrance bottle.
La
Nota Si sculptural fragrance bottle.
SiLaunch status to confirm

THE SIGNATURE COLLECTION

60 ml fragrance

$229Two complimentary 2 ml samples

Sol 7.5 ml discovery vial and ivory carton.

Individual discovery7.5 ml · No redemption credit

$29

Closed ivory discovery set and burgundy sample set.

Discovery set6 × 7.5 ml

$129

Sample set6 × 2 ml

$39

AssortmentThe ecommerce offer

Working USD retail reference from the latest pricing brief. Local price books need approval.

FormatWorking retail priceCommercial role
Signature fragrance, 60 ml$229Main purchase. Two complimentary 2 ml samples with each eligible bottle.
Individual discovery, 7.5 ml$29Accessible single-fragrance format. No redemption credit.
Discovery set, 6 × 7.5 ml$129Discovery and gifting. Full eligible set-price credit toward 60 ml.
Sample set, 6 × 2 ml$39First discovery of the collection. Full eligible set-price credit toward 60 ml.

Confirm exact set contents, Si availability and whether sets remain own-channel exclusive. Older design exports contain superseded prices.

Implementation notes & source context
Source: Nota_Paris_Price_Benchmark_and_Brief.pdf, 21 October 2026, pp. 2 and 14; Nota_Paris_Pricing_Benchmark.xlsx. Latest retrieved pricing recommendation supersedes the older $19/$20 discovery unit and $99 discovery set. Final commercial configuration requires approval.
The 22 October meeting records intended own-channel exclusivity for discovery and sample sets, while the pricing analysis also models wholesale. Resolve this policy before product channel publishing. Complimentary sample requirement follows Haidar's later ecommerce design direction. USD RRPs are reference values; do not automatically convert into final AED/SAR prices.
Nota sample vials and burgundy cartons arranged with sheet music on an ivory piano.
Every discovery begins with a first note.

NOTA PARIS / 04 · SHOPIFY PLUS

From discovery
to a signature scent.

Two mechanics should make the journey unmistakably Nota: complimentary samples with eligible bottles, and discovery-set credit toward a full-size fragrance.

Commercial mechanics

Two complimentary samples

A visible benefit.
A controlled stock movement.

Customers choose two 2 ml samples for each eligible 60 ml bottle.

Selection must remain clear in bag, checkout, order confirmation and warehouse instructions.

Sample stock must update like any other physical SKU.

Confirm duplicate scents, entitlement per quantity, selection defaults and the fallback when a sample is unavailable.

Implementation notes & source context
Requested mechanic: two complimentary 2 ml samples with every 60 ml. Technical acceptance: limits enforce server-side or with supported checkout/discount validation, not only theme JavaScript; removing or reducing a qualifying bottle removes excess free samples; express payment does not create an unexplained missing benefit. Paid sample sets and gifts must use distinct SKU/rules. Sample value remains zero only for eligible items. Confirm whether 60 ml orders using discovery redemption retain the sample benefit; recommended yes.

Commercial mechanics

Discovery-set redemption

Baseline from the pricing brief, subject to final commercial sign-off.

The customer promise

Credit equals the eligible set price actually paid, excluding shipping.

Redeem against one full-price 60 ml bottle within 60 days of delivery.

One unique code per redemption order. No promotional stacking or retail-partner redemption.

The operational rules

Link credit to the original order and customer; show value and expiry clearly.

Track issuance, use, cancellation and refund history.

Reject expired, reused, ineligible or duplicated claims with a useful explanation.

At reference prices: $39 set credit leaves $190 to pay; $129 credit leaves $100. Taxes and local price books require separate validation.

Implementation notes & source context
Source: Nota_Paris_Price_Benchmark_and_Brief.pdf, 21 October 2026, pp. 2 and 14; Nota_Paris_Pricing_Benchmark.xlsx. Latest retrieved pricing recommendation supersedes the older $19/$20 discovery unit and $99 discovery set. Final commercial configuration requires approval.
Agency must demonstrate delivery-event activation, resend and support controls, multi-currency treatment, multiple sets in one order, gift recipient transfer, order cancellation, partial refund and returned redeemed bottles. Approve whether code is per set or per initial order before build. If an eligible set was discounted, credit must equal the approved amount actually paid, not the RRP. Define refund/reinstatement policy with Finance; avoid double benefits.

SAMPLE SET → 60 ML

$229 − $39 = $190

DISCOVERY SET → 60 ML

$229 − $129 = $100

Reference-price examples. Credit is based on the eligible set amount actually paid. Taxes and local price books require validation.

Rules appendixCommercial cases the agency must demonstrate

A working demonstration is required for the rules that distinguish Nota from a standard store.

CaseExpected behaviourDecision / control
Two 60 ml bottlesCalculate the approved sample entitlement; recalculate after a bottle is removed.Confirm two samples per bottle, maximum quantities and duplicates.
Accelerated checkoutPreserve sample choices and redemption, or provide an explicit supported selection route.No hidden loss of the customer benefit.
Set bought as a giftCredit can follow the approved purchaser or recipient policy with an audit trail.Approve transfer and recipient verification.
Cancellation or returnInvalidate unused credit as applicable; calculate approved refund and restock.Finance signs off treatment when credit has already been spent.
Multiple markets / setsPrevent stacking, double use and incorrect currency value.Define code per set/order, market restriction and expiry event.

Also test unavailable samples, no delivery event, voucher resend, failed payment retry and customer-service overrides.

Implementation notes & source context
Source: Nota_Paris_Price_Benchmark_and_Brief.pdf, 21 October 2026, pp. 2 and 14; Nota_Paris_Pricing_Benchmark.xlsx. Latest retrieved pricing recommendation supersedes the older $19/$20 discovery unit and $99 discovery set. Final commercial configuration requires approval.
This section makes edge cases visible rather than leaving them in notes. Apply technical validations beyond the browser. Track every override and restrict it to approved roles. Define whether multiple eligible sets generate multiple future entitlements; the source specifies one code per redemption order but does not settle every issuance scenario.

NOTA PARIS / 05 · SHOPIFY PLUS

Find your note.
Make it your own.

Keep direct shopping effortless while giving an undecided customer the confidence to choose.

Parisian stone facade with illuminated windows.
A pianist at a grand piano.
Curved wrought-iron railings on a Parisian staircase.
Soft light across piano keys.

Customer journey

A route for every purchase intention

Keep direct shopping easy while helping undecided customers discover the collection.

Discover

Campaign or search landing.

Understand the Maison and explore the notes.

Use Find Your Note or choose a discovery format.

Choose & purchase

Compare fragrances and formats.

Select complimentary samples, gifting and delivery.

Complete payment with clear costs.

Return & deepen

Track the order and experience the scent.

Redeem eligible set credit toward 60 ml.

Review, reorder or discover another note.

Measure each route separately: direct bottle purchase, discovery-to-bottle conversion, gifting and repeat purchase.

Implementation notes & source context
Proposed experience architecture. Do not force every visitor through a quiz or account creation. Discovery should never obscure a direct purchase.
Experience & art directionThe Nota design language

Editorial, tactile and unmistakably Nota

Burgundy, ivory, restrained gold and musical forms.

Use the actual bottle, packaging and founder assets. Preserve product proportions.

Refine the existing direction into complete responsive screens, with deliberate motion and immediate shopping access.

Benchmarks: Maison Francis Kurkdjian, Kilian and Ex Nihilo as experience references. Use Nota’s own identity and assets.

Implementation notes & source context
Visual reference: Nota_Paris_Distributor_Presentation.pdf, 24 pages. Original images extracted unchanged. The SVG design pack is a visual reference, not a complete Shopify build or final copy source.
Existing Figma/SVG files are direction, not approved final build specifications. Correct legacy founder and pricing copy. Complete missing pages, responsive states and component documentation. Use source-quality product photography, not placeholder product renders.
Information architecturePages the website must include

Provide desktop and mobile designs, empty states and transactional states for the full journey.

AreaRequired pages / templatesCritical detail
BoutiqueHomepage, collection, fragrance PDP, 7.5 ml, discovery set, sample set, gifts.Format selection, stock, prices, samples and recommendations.
Discovery & MaisonFind Your Note, results, La Maison, founder, perfumers, bottle craftsmanship.Approved story, scent descriptions and accessible video.
Editorial & retailJournal, article, campaign landing page, multi-country store locator.Editable content and verified store data.
Customer journeyBag, checkout, confirmation, accounts, order tracking, wishlist and search.Error, no-result and out-of-stock states.
Care & legalContact, FAQs, delivery, returns, privacy, cookies, terms and accessibility.Country-specific policy content.

Include 404, password/prelaunch page, newsletter states and translated transactional emails in the design inventory.

Implementation notes & source context
PDP means product detail page. Website content model should let Nota add products and campaigns without a developer. Store locator starting entries may include UAE and Ukraine, but addresses, logos, authorisation and availability require validation.
MerchandisingA product page that answers the questions

A customer should understand the fragrance, the format and the offer before adding to bag.

The fragrance

Name, olfactive family, notes and approved perfumer story.

Bottle, box and detail photography with zoom. Film with clear playback controls.

Ingredients, volume, provenance and verified reviews.

The purchase

Prominent local price and available formats.

Delivery estimate, returns summary, sample entitlement and gifting options.

Accessible quick view, mobile add-to-bag and relevant recommendations.

Bottle-to-box hover must also work by touch. Select the correct image, price, stock and URL when the format changes.

Implementation notes & source context
Include keyboard focus, variant errors, unavailable product, back-in-stock signup and review moderation. Ingredient/INCI data and product claims must come from Nota's approved master data. No invented performance, longevity or customer reviews.

NOTA PARIS / 06 · SHOPIFY PLUS

Every detail,
through to checkout.

A beautiful storefront must lead to a payment experience that works for the customer, the selling entity and the market.

Conversion

Bag and checkout

Provide a coherent branded experience from product selection to order confirmation.

Before payment

Editable quantities, sample choices, gift message and clear credit application.

Show currency, tax, shipping, duties and delivery promise before commitment.

Allow guest checkout and familiar address formats.

After payment

Order number, correct items and samples, payment status and delivery details.

Confirmation, tracking and support access.

Explain failures clearly. Retry without duplicate charges or orders.

Test mobile wallets and accelerated checkout with samples and redemption. Use supported Shopify Checkout Extensibility.

Implementation notes & source context
Shopify Help, accessed 29 October 2026: https://help.shopify.com/en/manual/checkout-settings/checkout-customization
Checkout UI extensions on information/shipping/payment pages require Shopify Plus. Use supported extension surfaces, Shopify Functions and official APIs; do not promise arbitrary checkout HTML changes. Agency must explain any limitation for Shop Pay or other express flows. Capture contact, country, delivery address and telephone only as needed. Recovery should preserve permitted basket information.

Payments

Payment methods to cover

Availability must be proven for the selling entity, customer country, currency and basket.

MethodBrief requirementAgency evidence
CardsVisa and Mastercard at launch. Other brands where supported.3D Secure, decline handling, capture, void and refund tests.
Mobile walletsApple Pay and Google Pay on eligible devices and gateways.Live device tests and order reconciliation.
Buy now, pay laterTabby and Tamara where merchant and customer eligibility allow.Contracts, eligible markets, fees, capture/refund workflow and fallback.
Country-specific methodsAssess mada for Saudi Arabia, KNET for Kuwait and relevant alternatives.Supported Shopify route and entity/currency conditions. Do not assume GCC-wide support.
Other optionsAssess Shop Pay / PayPal if relevant. Cash on delivery is not the launch baseline.Quote separately; Nota approves any added cost and operating burden.

Show payment logos and instalment messaging only where the live checkout can honour them.

Implementation notes & source context
Shopify Help, accessed 29 October 2026: https://help.shopify.com/en/manual/payments/shopify-payments/supported-countries/united-arab-emirates ; https://help.shopify.com/en/manual/payments/shopify-payments/supported-countries/united-arab-emirates/requirements ; https://help.shopify.com/en/manual/payments/shopify-payments/supported-countries/united-arab-emirates/payment-methods
Provider documentation, accessed 29 October 2026: https://tabby.sa/en-SA/help-business/selling-with-tabby/supported-ecommerce-platforms ; https://docs.tamara.co/docs/shopify
Current Shopify UAE documentation lists Visa, Mastercard and Maestro plus Apple Pay, Google Pay and Shop Pay. This is not an approval of Nota's merchant account. Mada/KNET are feasibility requirements, not verified provider recommendations. BNPL and alternative methods can have different currency and entity restrictions.
Payment architectureThe gateway and entity decision

Resolve this before checkout design and multi-market configuration.

Recommended evaluation

Assess Shopify Payments for the proposed UAE entity first.

Compare a supported alternative if eligibility or required methods create a gap.

Prove display currency, charge currency, refund currency and payout currency for each market.

Required commercial review

Confirm legal entity, licence, bank account and merchant approval.

Compare fees, FX, settlement, reserves, disputes and refund costs.

Document reconciliation and the later France entity model.

Shopify currently supports Payments in the UAE. Nota eligibility is unconfirmed; Shopify Plus alone does not secure gateway approval.

Implementation notes & source context
Shopify Help, accessed 29 October 2026: https://help.shopify.com/en/manual/payments/shopify-payments/supported-countries/united-arab-emirates ; https://help.shopify.com/en/manual/payments/shopify-payments/supported-countries/united-arab-emirates/requirements ; https://help.shopify.com/en/manual/payments/shopify-payments/supported-countries/united-arab-emirates/payment-methods
Shopify Help, accessed 29 October 2026: https://help.shopify.com/en/manual/markets/customizations/local-currencies ; https://help.shopify.com/en/manual/international/payments ; https://help.shopify.com/en/manual/payments/shopify-payments/onboarding/selling-with-multiple-entities
Shopify documentation says native multi-currency processing requires Shopify Payments or Adyen; other primary providers generally return checkout to the store currency. Validate this for every selected payment method. The UAE account requirements include company registration and a qualifying UAE bank account; the proposed entity is NotaParis DWC-LLC per prior discussions, to be verified by Hassan and Ganesh. For France, verify multi-entity eligibility and contract limits rather than assuming one-store support.

NOTA PARIS / 07 · SHOPIFY PLUS

A promise
we can deliver.

Connect the website to accurate stock, dependable fulfilment, clear returns and a considered service experience.

Delivery

A promise the operation can deliver

Configure only the countries, products and services approved by Operations.

DestinationWorking customer promiseDecision before launch
UAEFree shipping. 24-hour target.Service zones, cut-off, weekends, carrier capability and exceptions.
Other GCCFree shipping. 48–72-hour working range.Resolve the 48h website ambition versus up-to-72h kickoff assumption by country.
Outside GCCSelective activation. 5–7 days is an earlier design ambition only.Validate perfume shipping, price, taxes, duties and customs before enabling.
Every orderTracking and proactive delay communication.Confirm fulfilment origin, dispatch rule, delivery events and support ownership.

Finance must approve freight economics and the duties model. No unvalidated delivery guarantee should appear on the storefront.

Implementation notes & source context
Source: Nota_Paris_Ecommerce_Meeting_Minutes_22Oct2026.docx, 22 October 2026. The working launch target and operating model remain subject to final approval.
Earlier ecommerce design direction said UAE 24h, GCC 48h and rest of world 5–7 days. The kickoff records GCC up to 72h. This section preserves the discrepancy and assigns validation rather than silently promising either. Confirm perfume transport classification, carrier approvals, packaging, destination restrictions, insurance and loss procedures. Outside GCC, the kickoff intention was customer-borne shipping/duties/taxes, clearly disclosed; decide collected-at-checkout versus payable-on-arrival treatment.
OperationsStock, fulfilment and returns

A successful online order must become an accurate physical delivery and financial record.

Stock & warehouse

Dedicated ecommerce stock and safety stock by SKU, including samples.

Synchronise availability, reservations, cancellations and restocks.

Transmit bottles, set components, samples and gift instructions correctly.

Returns & exceptions

Approved rules for opened items, damage, leakage, failed delivery and loss.

Track return approval, receipt, inspection and refund.

Reconcile partial refunds, redemption and stock without double credit.

Perfume shipping, 3PL selection, set assembly and return-policy approval remain launch dependencies.

Implementation notes & source context
Source: Nota_Paris_Ecommerce_Meeting_Minutes_22Oct2026.docx, 22 October 2026. The working launch target and operating model remain subject to final approval.
Agency must map system of record for stock, order, shipment and refund. Prevent overselling under concurrent checkout. Distinguish prepacked sets from component-built bundles and confirm inventory decrement logic. Payment capture and warehouse release must align. Validate consumer requirements with Nota's advisers; do not invent an absolute no-return rule. The 3% return/loss allowance in kickoff is unapproved financial planning, not a customer policy.
Nota burgundy gift box with fragrance, discovery vials and an oud necklace.

SERVICE & RETENTION

As considered
as the fragrance.

Contact form and customer-care email, with WhatsApp if staffed.

Order history, tracking, saved addresses and easy access to eligible credit.

Clear FAQs and service hours. Route delivery, payment and product questions to named owners.

Choose internal or outsourced support, languages and response SLAs before launch. Reviews must come from genuine customers.

Implementation notes & source context
Source: Nota_Paris_Ecommerce_Meeting_Minutes_22Oct2026.docx, 22 October 2026. The working launch target and operating model remain subject to final approval.
Support tooling should show order status, fulfilment, redemption history and payment status without exposing sensitive payment data. Quote helpdesk and WhatsApp integration separately if needed. Provide escalation paths and approved refund permissions. A wishlist must work on mobile and follow a clear guest-to-account merge policy.

NOTA PARIS / 08 · SHOPIFY PLUS

The first order
is only the beginning.

Build permission-based relationships, make discovery credit easy to use and measure what actually becomes a lasting customer relationship.

306090

Measure discovery-to-bottle conversion
by cohort, at 30, 60 and 90 days.

Lifecycle communications

CRM flows to include at launch

Nota owns the audience, accounts, templates and consent records.

JourneyTrigger and contentAcceptance requirement
Welcome & discoveryPermission-based signup, Maison story, fragrance guidance and next step.Locale, consent and unsubscribe tested.
Cart / checkout recoveryEligible abandonment with useful product and basket context.Suppress after purchase; avoid duplicates.
Order & deliveryConfirmation, dispatch, tracking, delay and cancellation updates.Correct data and language at each event.
Set-to-bottle conversionDelivery activation, how to discover, credit, expiry and reminder.Link to the original set; stop after use, refund or expiry.
Review & repeatAfter delivery: review invitation, care, reorder or complementary discovery.Approved timing, exclusions and segmentation.

Agency to recommend the CRM platform, included flows, editable templates, event mapping and recurring cost.

Implementation notes & source context
CRM platform is not selected. Klaviyo or an alternative may be proposed with evidence of integration, consent handling, volume pricing and ownership. Transactional and marketing messages require distinct treatment approved by Nota. Include back-in-stock only with valid consent and current product availability. SMS/WhatsApp campaigns are separate approval and cost items.
MeasurementA measurement plan before development

Build one agreed funnel and reconcile it with Shopify orders and refunds.

LayerRequired events / measuresQuality requirement
Commerce funnelview_item, add_to_cart, begin_checkout, purchase, refund and payment failure.Correct item, value and currency; no duplicate purchase events.
Fragrance discoveryQuiz start/result, sample selection, set purchase, credit issue/use/expiry.Connect a set cohort to a later 60 ml order.
AcquisitionCampaign UTMs, channels, consented ad-platform events and product feeds.GA4 and approved platform integrations; no personal data in analytics payloads.
Commercial reportingNet sales, AOV, new-customer CAC, repeat rate and contribution.Consistent definitions with Finance; separate gross sales, discounts and returns.
OperationsPayment success, stock errors, on-time delivery and service contacts.Market, device and payment-method views.

Agree baseline and targets during discovery. Compare discovery conversion at 30 / 60 / 90 days; do not treat unredeemed credit as repeat demand.

Implementation notes & source context
Proposed analytics specification. Define CAC as acquisition spend divided by attributed new customers under an agreed attribution model; avoid claiming deterministic attribution. Consent limits, browser restrictions and ad blockers affect measured funnel counts. Agency must provide a QA event log and reconciliation methodology. Any browser/server tracking needs deduplication and approved data use.

NOTA PARIS / 09 · SHOPIFY PLUS

A strong foundation.
Room to evolve.

Shopify Plus, a maintainable branded theme and supported integrations — with clear ownership and measurable quality.

STOREFRONT

Editorial freedom

Reusable theme sections, structured product content and Nota-owned merchandising controls.

COMMERCE

Reliable rules

Supported checkout extensions, validated samples and redemption, dependable integrations.

OPERATIONS

Lasting ownership

Documented data flows, source access, release controls and a lean, transparent app stack.

Technical approachA maintainable Shopify Plus build

Recommended baseline: a custom branded Online Store 2.0 theme with supported Shopify extensions.

LayerExpected approachAgency to explain
StorefrontReusable theme sections and templates; metafields/metaobjects for structured content.Theme licence, custom work, content controls and upgrade/support approach.
Checkout & rulesCheckout Extensibility and supported Functions/apps for commercial rules.Plus dependencies, express-flow limitations and server-side enforcement.
Apps & integrationsPrefer maintained native or official integrations with a limited app stack.Purpose, vendor, data access, fees, performance impact and replacement route.
Environments & releasesSeparate build/UAT environment, version control and controlled release.Access model, deployment, rollback, monitoring and defect handling.

Headless is not the baseline. Any alternative must justify the experience benefit, operating cost and maintenance burden.

Implementation notes & source context
Shopify Help, accessed 29 October 2026: https://help.shopify.com/en/manual/checkout-settings/checkout-customization
The user specified Shopify Plus. Request a clear account of which requirements need Plus and which use standard Shopify functionality, without silently changing the requested platform. No production credentials in code. API versions, integration ownership and app support arrangements must be documented. Native Shopify admin must remain usable by Nota.
Integration mapSystems, data and responsibilities

The agency must return a system diagram and an interface inventory with named owners.

ConnectionData that must flowMinimum acceptance evidence
Payments / FinanceOrders, captures, refunds, fees, payouts and tax invoice data.Order-to-payout reconciliation.
3PL / inventoryStock, reservations, order lines, samples, dispatch and tracking.Test order, cancellation and stock recovery.
CRM / serviceConsent, profile, orders, delivery and redemption status.Journey tests and controlled support access.
Analytics / advertisingConsent-aware events, campaign IDs and approved catalogue feeds.No duplicated purchases; valid feed data.
Accounting / ERPSales, tax, discounts and refunds; exact system to be confirmed.Agreed mapping and connector or export.

For every interface: specify source of truth, direction, frequency, retry logic, duplicate protection, monitoring, owner and recurring cost.

Implementation notes & source context
No existing ERP, 3PL, CRM or helpdesk has been verified as selected. Quote supported connector options after discovery. Critical interfaces must include safe retries and manual recovery, alert routing and reconciliation. Avoid reprocessing orders or refunds when events are delivered more than once. Identify access, documentation and sandbox dependencies.
QualityFast, findable and easy to use

Optimise the image-led experience while preserving product detail and brand quality.

Performance

Target good Core Web Vitals at the 75th percentile:
LCP ≤ 2.5s, INP ≤ 200ms, CLS ≤ 0.1.

Use responsive images, sensible video loading and restrained scripts.

Agree mobile lab tests before launch and field monitoring after launch.

Search & discoverability

Editable metadata, headings, canonical URLs, sitemap and redirects.

Product structured data, stock and price accuracy, image alt text and locale hreflang.

Search Console setup, product feeds and a clean crawl before launch.

Prioritise homepage, collection, product, discovery and bag. Lab scores alone do not establish real-user performance.

Implementation notes & source context
Google web.dev, accessed 29 October 2026: https://web.dev/articles/vitals
Performance thresholds sourced from Google web.dev. Use agreed device/network profiles for prelaunch laboratory checks, then real-user monitoring when enough traffic exists. Video poster frames, lazy loading below the fold, font loading and app budgets must be included. SEO is a technical delivery requirement; rankings and organic revenue are not guaranteed.
Trust & accessibilityPrivacy, access and customer confidence

Design these requirements into the store and integrations from the start.

Customer experience

WCAG 2.2 AA as the proposed build target.

Keyboard navigation, readable contrast, form errors, screen-reader labels and reduced motion.

Approved privacy, cookie, delivery, return and purchase terms for each active market.

Data & administration

Consent-aware tracking and communication, with retention and deletion processes.

Nota-owned accounts, least-privilege roles and multi-factor authentication.

Protected credentials, vendor access review and incident escalation.

Nota’s advisers approve legal and tax content. The agency implements, tests and documents the approved requirements.

Implementation notes & source context
W3C, accessed 29 October 2026: https://www.w3.org/TR/WCAG22/
WCAG 2.2 AA is a proposed procurement target, not a legal conclusion. Agency should disclose inaccessible third-party app surfaces and remediation plans. Country-specific privacy, consumer, tax and cross-border-data requirements require Nota's advisers. Use Shopify/provider payment handling; custom Nota code should not collect or store raw card data. Include consent audit, deletion requests and data export workflow.

NOTA PARIS / 10 · SHOPIFY PLUS

The route
to launch.

End-December 2026 is the working target. The agency must confirm feasibility, resourcing and the dependencies behind its commitment.

  1. 01

    Define

    Week 1

    Scope, merchant model & architecture
  2. 02

    Design

    Weeks 2–3

    Responsive screens & content
  3. 03

    Build

    Weeks 3–5

    Theme, checkout & integrations
  4. 04

    Validate

    Weeks 6–7

    Commercial & operational tests
  5. 05

    Launch

    Week 8

    Approval, release & hypercare

Proposed eight-week sequence from kickoff, subject to agency confirmation and timely approvals.

Delivery planA staged route to launch

End-December 2026 is the working target. The agency must confirm feasibility and dependencies.

Indicative timingMilestoneExit condition
Week 1Discovery and scope baselineApproved requirements, architecture, entity/payment path and delivery plan.
Weeks 2–3Responsive design and contentApproved key screens, commercial rules, product master and content responsibilities.
Weeks 3–5Theme, checkout and integrationsWorking end-to-end staging journeys; apps and recurring costs approved.
Weeks 6–7UAT, content and operational testsNo critical/high defects; payments, 3PL, invoices and refunds signed off.
Week 8 + after launchControlled launch and hypercareHassan approval, monitoring and rollback. Quote 30 days of launch support.

This is a proposed eight-week sequence from kickoff, not an agency commitment. Revalidate the earlier six-week development assumption.

Implementation notes & source context
Source: Nota_Paris_Ecommerce_Meeting_Minutes_22Oct2026.docx, 22 October 2026. The working launch target and operating model remain subject to final approval.
Design approval, content, merchant onboarding, 3PL access and translation can run in parallel but remain critical dependencies. Agency must show resourcing, review turnaround assumptions, holiday availability, launch coverage and consequences of missed inputs. Establish a final change freeze and go/no-go meeting.
Content & dataInputs, migration and launch content

The existing designs provide direction. They do not replace an approved content and product master.

InputNota provides / approvesAgency delivers
Brand & editorialLogo, imagery, films, founder/perfumer story, tone and usage rights.Optimisation, placement, CMS models and responsive presentation.
Product masterSKU, barcode, formats, notes, ingredients, prices, tax class, dimensions and stock.Structured import, validation and catalogue QA by market.
LocalisationApproved English and Arabic copy; French scope for the Europe phase.RTL layouts, translated templates, SEO and transactional QA.
Existing data & domainsCurrent store status, domain/DNS, customer consent, orders and reviews.Migration inventory, mapping, dry run, redirects and cutover plan if needed.
Policies & retailer dataApproved terms, care information, store addresses and contact details.Editable policy pages, locator and verified content publishing.

Resolve legacy founder and pricing text. Confirm Si, set contents and final photographs. No invented reviews, ingredient lists or brand claims.

Implementation notes & source context
Visual reference: Nota_Paris_Distributor_Presentation.pdf, 24 pages. Original images extracted unchanged. The SVG design pack is a visual reference, not a complete Shopify build or final copy source.
Figma/SVG package includes seven compositions and fonts, not an entire signed-off design system. Its README still contains EUR198 and Hassan Menhal, superseded by subsequent directions. Conduct a formal gap audit and maintain a content tracker. Existing store and migration volumes are unknown; agencies must quote assumptions and volume thresholds rather than quietly exclude migration.
GovernanceWho decides and who delivers

Working responsibility allocation from the ecommerce kickoff.

WorkstreamNota lead / approvalAgency responsibility
Final launch & budgetHassan approves.Evidence of readiness and budget status.
Digital & coordinationSanaa leads; Haidar coordinates.Named project manager, weekly status, demos and a shared decision log.
Commercial & assortmentHaidar leads; Hassan approves.Configure signed-off catalogue, prices, samples and redemption.
Operations & logisticsAbderrahim leads.Map and test warehouse, stock, shipping and return workflows.
Finance, entity & paymentsGanesh with Hassan; Abderrahim supports.Gateway, tax/invoice setup, refunds and reconciliation testing.
Brand content & designSanaa and Bashir; Hassan approves final direction.Responsive designs, asset gap list, content integration and design QA.

Maintain the delivery plan in monday.com. Confirm the final RACI and customer-service owner at kickoff.

Implementation notes & source context
Source: Nota_Paris_Ecommerce_Meeting_Minutes_22Oct2026.docx, 22 October 2026. The working launch target and operating model remain subject to final approval.
These are working roles, not a newly authorised allocation of employment duties. User acceptance is coordinated by Sanaa with agency, Operations and Finance participation. Haidar and Sanaa must remain informed across workstreams. Each workstream provides readiness evidence; Hassan gives launch approval.

NOTA PARIS / 11 · SHOPIFY PLUS

Ready for customers.
Owned by Nota.

Launch requires evidence across the full journey, followed by a handover that lets Nota operate and develop its store.

Acceptance

What must pass before go-live

Use a shared test register with evidence, owner and sign-off for every scenario.

Commercial journeys

Direct 60 ml, 7.5 ml and both sets.

Samples with multiple bottles, stock changes and express checkout.

Credit issuance, expiry, reuse, currency, cancellation and partial returns.

Cards, wallets and approved BNPL paths.

Operational readiness

Payment success, failure, timeout and duplicate notifications.

Correct stock, pick list, shipment, invoice, tracking and refund.

Mobile, Arabic RTL, accessibility, consent, analytics and SEO.

Rollback, alerts and support handover.

Launch gate: no open critical/high defects, signed operational checks and Hassan’s approval. Test each enabled market and payment method.

Implementation notes & source context
Source: Nota_Paris_Ecommerce_Meeting_Minutes_22Oct2026.docx, 22 October 2026. The working launch target and operating model remain subject to final approval.
Agency should define severity and evidence standards in the SOW. Test real representative iOS Safari, Android Chrome and desktop browsers plus devices that support selected wallets. Use provider-approved tests and an authorised low-value live order/refund where required. Launch approval must include product stock, price/tax accuracy, privacy policies, support readiness and marketing measurement.

Handover & ownership

What Nota must receive

The store should be operable by Nota and transferable to another qualified agency.

Delivery package

Editable Figma files and responsive component states.

Theme and custom app source, repository, release instructions and configuration records.

Integration map, test evidence, analytics plan and operating documentation.

Operational handover

Nota-owned Shopify, domains, apps and service accounts.

Admin access, licence register and customer data export route.

Recorded training for merchandising and operations.

30-day hypercare plus an optional support SLA.

Contract to specify IP, reusable agency components, third-party licences, source access, warranty, support coverage and exit assistance.

Implementation notes & source context
Proposed requirements. Training should cover adding products, editing content, prices, promotions, stock, orders, refunds, sample rules, redemption support, reports and incident escalation. Request two recorded training sessions and written runbooks in the quote. Define response and resolution targets by incident severity, coverage hours, weekend launch support and escalation.

NOTA PARIS / 12 · SHOPIFY PLUS

Let’s compose
the digital flagship.

Return a clear, itemised proposal: what is included, how it will work, who will deliver it, what it costs and how success will be verified.

Agency quotation

A transparent commercial proposal

Quote in AED, with taxes and exchange-rate assumptions stated. No project budget is yet approved.

Cost lineRequired breakdownCommercial clarity
Discovery & designAudit, specification, UX/UI, responsive screens and revision rounds.Fixed fee, deliverables and approval points.
Build & integrationsTheme, checkout, samples, redemption, apps, gateway, 3PL and CRM.Native/app/custom split and dependencies.
Content & launchData import, localisation, migration, QA, training, cutover and hypercare.Volume assumptions and exclusions.
Recurring costsShopify Plus, apps, CRM, service tools, custom hosting and maintenance.Monthly and 12-month totals, usage tiers and renewal terms.
Transaction & change costsPayment/FX/BNPL fees, support options, change requests and additional phases.Separate estimates, rate card, payment milestones and warranty.

Provide first-year total cost of ownership, staffing, schedule, acceptance terms and a list of client-supplied inputs.

Implementation notes & source context
No agency or platform fee is estimated as fact. Request actual Shopify Plus contract pricing and payment-provider quotes for Nota's entity. Keep transaction fees and fulfilment outside fixed build fees but visible in operating economics. No unapproved app purchases. Require change-control process and signed scope acceptance before extra charges.
Decisions to closeOpen points before configuration

These do not prevent agencies from proposing a solution. They must be resolved before implementation locks.

DecisionOwnerRequired resolution
Merchant modelHassan + GaneshEntity, bank, gateway approval, settlement and France expansion model.
Commercial rulesHaidar + HassanLocal prices, Si, set contents/channel policy, sampling and redemption exceptions.
Delivery & stockAbderrahim + Finance3PL, perfume lanes, free-shipping economics, service times and inventory interface.
Languages & serviceSanaa + HassanEnglish/Arabic approval, French phase, care team, hours and escalation.
Content & migrationSanaa + BashirFinal design source, rights, copy, product data, existing-store scope and domain access.
Budget & timingHassan + Haidar + SanaaAgency, total budget, exact go-live date, review turnaround and support cover.

An open decision must have an owner, due date and effect on scope. Agencies should state the assumption used in their quote.

Implementation notes & source context
Source: Nota_Paris_Ecommerce_Meeting_Minutes_22Oct2026.docx, 22 October 2026. The working launch target and operating model remain subject to final approval.
Current internal status must be refreshed at the next kickoff. This brief does not approve expenditure, contracts, legal policies or a public launch.
Agency selectionHow proposals should be assessed

Proposed evaluation framework. Require a written response to every scope item.

CriterionWeightEvidence requested
Brand & mobile experience25%Relevant luxury/fragrance work and interpretation of the Nota design direction.
Shopify & commercial rules25%Plus expertise; sample, redemption, checkout and gateway demonstration.
Operations & integrations20%3PL, finance, CRM and reporting approach; recovery and support responsibilities.
Delivery team & support15%Named team, capacity, milestones, references and post-launch SLA.
Cost & ownership15%Transparent 12-month cost, source ownership and credible exclusions.

Response format: requirement, included/optional/excluded, solution, dependency, cost and acceptance test. Proposal deadline: to be agreed.

Implementation notes & source context
Proposed evaluation weights total 100%. They are not prior Nota policy. Ask for two relevant client references, proposed account team and subcontracting disclosure. Commercial scoring should reflect cost transparency and fitness, not price alone. Any exclusions affecting launch must be visible.
Reference packDesign and business references

Use the approved brand direction; confirm access and the latest design version at agency kickoff.

Reference links require the appropriate access. Export or share approved copies with the appointed agency.

Implementation notes & source context
Visual reference: Nota_Paris_Distributor_Presentation.pdf, 24 pages. Original images extracted unchanged. The SVG design pack is a visual reference, not a complete Shopify build or final copy source.
Figma URL retrieved from the prior ecommerce conversation. Its current completeness was not independently verified during this task; do not describe it as production-ready. The old SVG pack contains superseded copy/prices. This reference pack is private until Nota shares it; inclusion in the brief does not grant access.
Technical referencesPlatform checks behind the brief

Official documentation reviewed on 29 October 2026. Agency to reconfirm eligibility at implementation.

Provider availability does not equal Nota merchant approval. Reconfirm eligibility and platform capabilities before implementation.

Implementation notes & source context
Shopify Help, accessed 29 October 2026: https://help.shopify.com/en/manual/payments/shopify-payments/supported-countries/united-arab-emirates ; https://help.shopify.com/en/manual/payments/shopify-payments/supported-countries/united-arab-emirates/requirements ; https://help.shopify.com/en/manual/payments/shopify-payments/supported-countries/united-arab-emirates/payment-methods
Shopify Help, accessed 29 October 2026: https://help.shopify.com/en/manual/markets/customizations/local-currencies ; https://help.shopify.com/en/manual/international/payments ; https://help.shopify.com/en/manual/payments/shopify-payments/onboarding/selling-with-multiple-entities
Shopify Help, accessed 29 October 2026: https://help.shopify.com/en/manual/checkout-settings/checkout-customization
Provider documentation, accessed 29 October 2026: https://tabby.sa/en-SA/help-business/selling-with-tabby/supported-ecommerce-platforms ; https://docs.tamara.co/docs/shopify
Google web.dev, accessed 29 October 2026: https://web.dev/articles/vitals
W3C, accessed 29 October 2026: https://www.w3.org/TR/WCAG22/

THE RESPONSE WE NEED

Requirement · Included / optional / excluded · Solution
Dependency · Cost · Acceptance test

Proposal deadline and project budget: to be agreed.

NOTA PARIS / AGENCY BRIEF

The composition

  1. 00The agency brief
  2. 01The Maison & our ambition
  3. 02Markets & launch scope
  4. 03The ecommerce offer
  5. 04Discovery & commercial rules
  6. 05The customer experience
  7. 06Checkout & payments
  8. 07Delivery & customer care
  9. 08Relationships & measurement
  10. 09Technology & quality
  11. 10The route to launch
  12. 11Acceptance & ownership
  13. 12The agency response