datawebotNoon product data: SKUs, offers and markets
Understand Noon NSKU and ZSKU identities, Partner SKUs, grouped variants, UAE/KSA/Egypt offers, FBN/FBP fulfillment, seller APIs, and current crawler rules.
Noon Catalog and Partner Catalog hold different product records
Noon uses catalog identifiers for content ownership and a separate seller catalog for each partner’s products and offers. An NSKU or ZSKU answers which product content is being referenced; a Partner SKU and PSKU Code identify a seller’s own catalog item.
Scroll to compare →
| Identifier or catalog | Noon seller guidance | How to keep it distinct |
|---|---|---|
| NSKU / Noon SKU | Noon-controlled catalog content, generally for Noon-controlled brands. New Noon SKUs follow this rule, but older NSKUs for other brands remain in circulation. | An N-prefixed page identifier is a useful source clue, not proof that an older SKU belongs to a currently Noon-controlled brand. |
| ZSKU / Seller SKU | Seller-controlled product content for products that are not Noon-controlled brands. The seller creates and can manage this content. | Keep the seller’s content and identifier with its seller account; do not merge similar seller-created records by title alone. |
| Partner SKU | The seller’s own product key, unique in that seller’s catalog. A seller can use it to make its own offer against an existing NSKU. | Keep it alongside seller identity and offer context, even when multiple sellers reference the same Noon catalog product. |
| PSKU Code | A unique identifier generated by Noon for each Partner SKU and available in catalog exports. | Store it separately from the seller-assigned Partner SKU; the two codes are not interchangeable. |
| Noon Catalog / Partner Catalog | Noon Catalog holds Noon catalog products. Partner Catalog contains a seller’s own products and offer details. | Do not treat a shared catalog page, seller catalog item, and market-specific offer as one record. |
A Noon seller offer adds market, stock, price and visibility
Noon’s Partner Catalog documentation describes seller-side offer fields that can change independently of shared product content. Keep market, seller, fulfillment model and observation time with each offer. The Seller Lab view is not a guarantee that every field appears to anonymous storefront visitors.
Scroll to compare →
| Seller-side field | What the documentation describes | Comparison boundary |
|---|---|---|
| Seller and market | The seller’s catalog and selected Noon marketplace/store. | Do not compare two offers as equivalent without retaining seller and market context. |
| Customer-visible price | Partner Catalog can show the product price visible to customers, described in the FAQ as inclusive of VAT, fees and commission. | Keep the observed storefront price and seller-side record separate from a calculator estimate, final checkout total, and later financial statement. |
| FBP and FBN stock | Partner Catalog can show the seller’s quantities for Fulfilled by Partner and Fulfilled by Noon. | A seller portal quantity is not an anonymous public stock feed or a promise that an order can be fulfilled. |
| Product visibility | The catalog tracks whether a seller product is visible to customers. | A visibility status is not the same as the product’s content identity or proof of current availability in every market. |
| Barcode and warranty | The Partner Catalog includes the seller product’s barcode and warranty information. | Keep these seller product fields with their source; do not silently copy them across sellers or catalog matches. |
| Estimated fees | The Fees and Revenue Calculator compares standard FBN/FBP fee and revenue estimates; the documented estimates exclude VAT and some exceptional charges. | Keep an estimate separate from actual fees in the seller’s statement and from the buyer-facing listed price. |
Size variants and attribute groups use different links
Noon seller guidance separates apparel/footwear size children from color and other attribute groups. A guide step that adds one size option at a time describes the listing workflow; it is not a universal rule that every kind of variation has one axis.
Scroll to compare →
| Variation relationship | Noon documentation | What to preserve |
|---|---|---|
| Size parent and child | Seller SKU products can use a parent and child relationship; the child represents a size option in the documented apparel/footwear workflow. | Keep the parent reference, child SKU, exact selected size label, and the source page or catalog evidence. |
| Seller Size and noon Size | Seller Size reflects the label on the physical product. noon Size is a separate normalized approximation used for apparel/footwear size discovery and filters. | Retain both values and label the normalized size as a mapping; do not replace the seller’s original size. |
| Color and other attributes | Colors or category-specific attributes can be organized into groups that link Partner SKUs. Attributes and eligibility depend on category and brand rules. | Keep group membership separate from the size parent/child link. Do not assume every attribute group is a variant family with interchangeable offers. |
| Price, stock and images | The variation guide says options can have different prices and stock; color variations can have their own images. | Associate each field with the specific Partner SKU/selected option when the source provides that relation. |
Market, fulfillment and cross-border destination affect comparison
Noon’s current seller onboarding FAQ names KSA, UAE and Egypt as operating seller markets. Fulfillment and cross-border eligibility add another layer: an eligible UAE offer can reach some GCC destinations, while KSA uses a separate cross-border lane. Record the selected seller market and buyer destination independently.
Scroll to compare →
| Context | Documented Noon model | Keep separate from |
|---|---|---|
| Seller market | KSA, UAE and Egypt are the markets named in the current onboarding FAQ. | A cross-border delivery destination or a seller’s eligibility to open another market store. |
| FBN | Fulfilled by Noon: Noon stores, picks, packs and ships the product from its fulfillment operation. | Seller-held FBP stock, public availability labels, or a specific delivery estimate. |
| FBP | Fulfilled by Partner: the seller holds and fulfills the product under the selected seller model. | FBN warehouse inventory or the details of another FBP shipping model. |
| UAE GCC lane | Current seller guidance describes eligible UAE offers reaching Bahrain, Qatar, Oman and Kuwait; eligible fulfillment models and product restrictions apply. | A separate Noon seller marketplace in each destination country or availability of every UAE listing. |
| KSA cross-border lane | The seller guide treats Saudi cross-border selling as a separate lane from the UAE GCC program. | The UAE GCC destination rules, a fixed delivery time, or a universal fee. |
| Price and delivery observation | Store the shown currency, market, destination, fulfillment wording and observation time when available. | A converted price, final landed cost or current delivery promise inferred from a different market or date. |
Noon’s API Platform documents seller and partner workflows
Noon describes its API Platform for integrations that work with catalogs, orders, fulfillment and event notifications. The help-center page is seller/integrator documentation; it does not establish an anonymous public API for querying all customer-facing product listings or competing sellers’ offers.
Scroll to compare →
| Documented workflow | What Noon’s page supports | What it does not establish |
|---|---|---|
| Catalog | A partner integration can work with catalog operations in Noon’s marketplace platform. | Unauthenticated search across the consumer catalog or unrestricted access to another seller’s data. |
| Orders and fulfillment | The platform documentation includes seller commerce and fulfillment workflows. | Access to orders without a partner relationship, account scope or permission. |
| Events | The API Platform documentation includes event notifications for integrations. | A public event feed for all Noon listings, sellers or customers. |
| Integration scope | The official help page introduces a common interface for sellers, integrators and developers working with Noon’s core commerce services. | Specific endpoint availability, credentials or scopes for an individual account unless documented and granted there. |
Noon’s robots.txt allows broad crawling by named AI agents
Checked on 30 September 2026 Singapore time (UTC+8); this page’s content review stamp uses the UTC date, 29 September 2026. Noon’s current robots file allows the site root for the wildcard group and explicitly allows several AI user agents. These crawl rules describe access for crawlers; they do not grant a license to extract or reuse site content.
Scroll to compare →
| Crawler signal | Current robots or program text | How to interpret it |
|---|---|---|
| Wildcard group | User-agent: * disallows /_svc/ and /_vs/, then allows /. | Most paths are crawl-allowed by robots, with those two restricted internal path prefixes. |
| Named AI user agents | GPTBot, ChatGPT-User, ClaudeBot and PerplexityBot each have an explicit Allow: / group. | This is a robots directive, not a guarantee of indexing, answer-engine citation, or content-reuse permission. |
| Other crawlers and sitemap | OAI-SearchBot and Google-Extended are not named and fall under the wildcard group. The file lists https://www.noon.com/sitemap-index.xml. | Apply wildcard path rules to unnamed agents; a sitemap helps discovery but does not guarantee indexing or citation. |
| Affiliate program terms | Noon Associates Terms §8.4 prohibit automated tools to scrape Site data under that affiliate-program agreement. | Keep this restriction scoped to the Associates program; do not generalize it to every Noon page or every user. |
| Consumer terms date | The UAE consumer Terms page inspected in this review shows Last updated: 11/11/2022. | Attribute that visible date. Do not infer current automated-collection permission or a blanket prohibition from the page’s age or from robots.txt. |
Content reviewed 2026-09-29.